Use markdown links (#624)

* Use markdown links

See <scientific-python/scientific-python-hugo-theme#568>.

* Apply suggestions from code review

---------

Co-authored-by: Jarrod Millman <[email protected]>

Author: alphapapa

content/_index.md

@@ -8,15 +8,15 @@ title:
 type = 'card'
 title = 'SPECs'
 body = '''
-[Scientific Python Ecosystem Coordination]({{% relref "/specs" %}}) documents are a mechanism by which practices are
+[Scientific Python Ecosystem Coordination](/specs) documents are a mechanism by which practices are
 discussed and propagated throughout the ecosystem.
 '''
 
 [[item]]
 type = 'card'
 title = 'Summits'
 body = '''
-At the [summits]({{% relref "/summits" %}}), we get together both virtually and in-person
+At the [summits](/summits), we get together both virtually and in-person
 to plan and do ecosystem work.
 '''
 
@@ -41,15 +41,15 @@ type = 'card'
 title = 'Sparse Arrays'
 body = '''
 One of our current focuses is on improving and maintaining the
-[sparse array]({{% relref "/grants/sparse_arrays" %}}) capabilities and
+[sparse array](/grants/sparse_arrays) capabilities and
 interoperability in the ecosystem.
 '''
 
 [[item]]
 type = 'card'
 title = 'Community'
 body = '''
-Our [community efforts]({{% relref "/community" %}}) focus
+Our [community efforts](/community) focus
 on broadening participation and better coordinating volunteer efforts.
 '''
 

content/about/_index.md

@@ -41,7 +41,7 @@ There are a numerous projects that use Python for computing, but we focus specif
 
 ## Who we are
 
-Learn more about the [community]({{< relref "/community" >}}) that
+Learn more about the [community](/community) that
 powers Scientific Python.
 
 ## What We Do
@@ -51,11 +51,11 @@ We release all our work openly. In particular, all our code is released under a
 and documentation is released under the [CC-BY](https://creativecommons.org/licenses/by/4.0/) license.
 
 - **SPECs**
-  [Scientific Python Ecosystem Coordination]({{< relref "/specs" >}})
+  [Scientific Python Ecosystem Coordination](/specs)
   documents are a mechanism by which practices are
   discussed and propagated throughout the ecosystem.
 - **Summits**
-  At the [summits]({{< relref "/summits" >}}), we get together both virtually and in-person
+  At the [summits](/summits), we get together both virtually and in-person
   to plan and do ecosystem work.
 - **Development Guide**
   Read this [community-maintained guide](https://learn.scientific-python.org/development/)
@@ -66,21 +66,21 @@ and documentation is released under the [CC-BY](https://creativecommons.org/lice
   One of our current focuses is on improving and maintaining the
   sparse array capabilities and interoperability in the ecosystem.
 - **Community**
-  Our [community efforts]({{< relref "/community" >}}) focus
+  Our [community efforts](/community) focus
   on broadening participation and better coordinating volunteer efforts.
 
 <!--
 - **Tools**
-  We maintain a collection of [tools]({{< relref "/tools" >}})
+  We maintain a collection of [tools](/tools)
   used across the ecosystem.
 -->
 
-Read about the [grants]({{< relref "/grants" >}}) that fund the work we do.
+Read about the [grants](/grants) that fund the work we do.
 
 ## Leadership
 
 The following people are involved with leading the overall project.
-For more information, see our [governance and decision making process]({{% relref "/about/governance" %}}).
+For more information, see our [governance and decision making process](/about/governance).
 
 ### Community Managers
 
@@ -98,4 +98,4 @@ For more information, see our [governance and decision making process]({{% relre
 
 As a coordinating effort, the Scientific Python project has several teams that operate across the ecosystem.
 Specific projects may have their own governance structures.
-For example, the SPEC Steering Committee governance model is described [here]({{% relref "/specs/steering-committee" %}}).
+For example, the SPEC Steering Committee governance model is described [here](/specs/steering-committee).

content/about/governance.md

@@ -22,7 +22,7 @@ The Scientific Python project has the following roles and responsibilities.
 ### Community Members
 
 The Scientific Python community consists of anyone working with the project.
-Community members must adhere to our [code of conduct]({{< relref "/code_of_conduct.md" >}}).
+Community members must adhere to our [code of conduct](/code_of_conduct).
 
 ### Community Managers
 
@@ -42,7 +42,7 @@ to allow existing members time to voice objections.
 Community Leaders are Community Managers who have additional responsibilities to ensure the smooth running of the Scientific Python project.
 Community Leaders are expected to participate in strategic planning, approve changes to the governance model, and make decisions about funding granted to the Scientific Python project.
 (Funding to community members/projects is theirs to pursue and manage.)
-Community Leaders should ensure smooth progress on the big-picture [roadmap]({{< relref "roadmap.md" >}}).
+Community Leaders should ensure smooth progress on the big-picture [roadmap](/roadmap).
 Changes that impact the full project require analysis informed by long experience with both the project and the larger ecosystem.
 When the Community Managers (including the Community Leaders) fail to reach such a consensus in a reasonable timeframe, the Community Leaders may resolve the issue.
 

content/code_of_conduct.md

@@ -110,7 +110,7 @@ Scientific Python Ecosystem Core Team directly, or ask the Team for advice, in
 confidence.
 
 You can report issues to the
-[Scientific Python Community Managers]({{% relref "/about#community-managers" %}}),
+[Scientific Python Community Managers](/about/#community-managers),
 at <[email protected]>.
 
 <!--

content/grants/planning_next_decade/_index.md

@@ -30,7 +30,7 @@ for the next decade of data science, we will:
 
 Our initial focus is on creating a recommendation infrastructure for
 community-wide policy and on improving common engineering infrastructure
-(see the [SPEC]({{< relref "specs" >}}) documents).
+(see the [SPEC](/specs) documents).
 
 Read the [full grant](../../doc/scientific-python-planning-grant-2020.pdf).
 

content/grants/sparse_arrays/_index.md

@@ -23,4 +23,4 @@ structures, as well as expanding on the existing scipy.sparse package.
 
 For more information, please see the
 [full grant](../../doc/sparse-arrays-grant-2022.pdf)
-and the [sparse data summits page]({{< relref "/summits/sparse" >}}).
+and the [sparse data summits page](/summits/sparse).

content/news.md

@@ -11,7 +11,7 @@ See [summit website]({{% relref "/summits/developer/2024" %}}).
 
 ## 2023--05--30: First Developer Summit held in Seattle
 
-See [summit website]({{% relref "/summits/developer/2023" %}}).
+See [summit website](/summits/developer/2023).
 
 ## 2021--04--21: SPECs announced at SciPy 2021