Fix format for linter (#231)

* Format linter fix

* Fix format for linter

Author: jarrodmillman

CONTRIBUTING.md

@@ -3,7 +3,7 @@
 We would love your help!
 
 Feel free to submit patches, issues, feature requests, and pull requests on the
-`GitHub repository <https://github.com/scientific-python/scientific-python.org>`_.
+[GitHub repository](https://github.com/scientific-python/scientific-python.org).
 
 ## How to submit an issue
 
@@ -56,7 +56,7 @@ Scientific Python projects using GitHub pull requests.
 
     - Go to GitHub. The new branch will show up with a green Pull Request (PR) button---click it.
 
-5.  Review process:
+4.  Review process:
 
     - Every PR update triggers a set of
       [continuous integration](https://en.wikipedia.org/wiki/Continuous_integration)
@@ -114,5 +114,5 @@ Once you've fixed all merge conflicts, do:
 
     git commit
 
-**_NOTE:_**  Advanced Git users may want to rebase instead of merge, but we squash
+**_NOTE:_** Advanced Git users may want to rebase instead of merge, but we squash
 and merge PRs either way.

README.md

@@ -38,7 +38,6 @@ export GH_TOKEN=<personal-access-token>
 
 Then run `make teams`.
 
-
 ## Analytics
 
 A self-hosted version of [Plausible.io](https://plausible.io) is used to gather simple

archetypes/default.md

@@ -3,4 +3,3 @@ title: "{{ replace .Name "-" " " | title }}"
 date: {{ .Date }}
 draft: true
 ---
-

calendars/matplotlib.yaml

@@ -1,5 +1,5 @@
 name: Matplotlib Community Calendar
-timezone:  Europe/Berlin
+timezone: Europe/Berlin
 events:
   - summary: Weekly Matplotlib Call
     description: |

config.yaml

@@ -1,5 +1,5 @@
 title: Scientific Python
-baseURL: 'https://scientific-python.org'
+baseURL: "https://scientific-python.org"
 languageCode: en-us
 theme: scientific-python-hugo-theme
 DefaultContentLanguage: en
@@ -13,7 +13,7 @@ params:
   description: Community developed and owned ecosystem for scientific computing
 
   images:
-  - /images/logo.svg
+    - /images/logo.svg
 
   plausible:
     dataDomain: scientific-python.org
@@ -24,8 +24,8 @@ params:
 
   style:
     vars:
-      highlightColor: '#004811'
-      menuHighlightColor: '#5ca038'
+      highlightColor: "#004811"
+      menuHighlightColor: "#5ca038"
 
   navbarlogo:
     image: logo.svg
@@ -59,41 +59,41 @@ params:
 
   keyfeatures:
     features:
-    - title: Built on Python
-      text: Python is a powerful, general-purpose programming language. The scientific Python ecosystem provides the tools that make Python the premier language for scientific computing.
-    - title: Open source
-      text: Distributed under unrestrictive open source licenses, projects are developed and maintained publicly and accessible to all.
-    - title: Community-driven
-      text: Projects are developed by open communities composed primarily of the users of the software.
-    - title: Extensive and high quality
-      text: The scientific Python ecosystem comprises performant, well-tested libraries providing tools for computing across all scientific domains.
-    - title: Broadly applicable
-      text: The ecosystem is widely used in scientific research and teaching.
-    - title: Coordinated, readable, reproducible
-      text: Projects in the ecosystem are completely interoperable, providing the basis for readable, reproducible scientific computation.
+      - title: Built on Python
+        text: Python is a powerful, general-purpose programming language. The scientific Python ecosystem provides the tools that make Python the premier language for scientific computing.
+      - title: Open source
+        text: Distributed under unrestrictive open source licenses, projects are developed and maintained publicly and accessible to all.
+      - title: Community-driven
+        text: Projects are developed by open communities composed primarily of the users of the software.
+      - title: Extensive and high quality
+        text: The scientific Python ecosystem comprises performant, well-tested libraries providing tools for computing across all scientific domains.
+      - title: Broadly applicable
+        text: The ecosystem is widely used in scientific research and teaching.
+      - title: Coordinated, readable, reproducible
+        text: Projects in the ecosystem are completely interoperable, providing the basis for readable, reproducible scientific computation.
 
   footer:
     logo: logo.svg
     socialmediatitle: ""
     socialmedia:
-    - link: https://scientific-python.org
-      icon: scientific-python
-    - link: https://github.com/scientific-python/
-      icon: github
-    - link: https://www.youtube.com/channel/UC2wKi87Wmy9C1OQMyD9fGxA
-      icon: youtube
-    - link: https://twitter.com/scientific_py
-      icon: twitter
-    - link: https://facebook.com/scientific.python
-      icon: facebook
-    - link: https://www.instagram.com/scientific.python/
-      icon: instagram
-    - link: https://www.tiktok.com/@scientific.python
-      icon: tiktok
-    - link: https://blog.scientific-python.org/atom.xml
-      icon: rss-feed
-    - link: https://discuss.scientific-python.org
-      icon: discourse
+      - link: https://scientific-python.org
+        icon: scientific-python
+      - link: https://github.com/scientific-python/
+        icon: github
+      - link: https://www.youtube.com/channel/UC2wKi87Wmy9C1OQMyD9fGxA
+        icon: youtube
+      - link: https://twitter.com/scientific_py
+        icon: twitter
+      - link: https://facebook.com/scientific.python
+        icon: facebook
+      - link: https://www.instagram.com/scientific.python/
+        icon: instagram
+      - link: https://www.tiktok.com/@scientific.python
+        icon: tiktok
+      - link: https://blog.scientific-python.org/atom.xml
+        icon: rss-feed
+      - link: https://discuss.scientific-python.org
+        icon: discourse
 
     quicklinks:
       column1:

content/about/governance.md

@@ -57,7 +57,7 @@ Decisions about the future of the project are made through discussion with all m
 All non-sensitive project management discussion takes place on the [public forum](https://discuss.scientific-python.org).
 Occasionally, sensitive discussion may occur on a private list.
 
-Scientific Python uses a *consensus seeking* process for making decisions.
+Scientific Python uses a _consensus seeking_ process for making decisions.
 The group tries to find a resolution that has no open objections among community managers.
 Community managers are expected to distinguish between fundamental objections to a proposal and minor perceived flaws that they can live with, and not hold up the decision making process for the latter.
 If no option can be found without an objection, the decision is escalated to the Community Leaders, who will themselves use consensus seeking to come to a resolution.

content/grants/inclusive_culture/_index.md

@@ -8,7 +8,6 @@ authors: ["Melissa Weber Mendonça"]
 date: 2021-08-21
 ---
 
-
 {{< page_gallery pages="." >}}
 
 We are happy to announce the Chan Zuckerberg Initiative has [awarded a grant](https://chanzuckerberg.com/newsroom/czi-awards-16-million-for-foundational-open-source-software-tools-essential-to-biomedicine/) to support the onboarding, inclusion, and retention of people from historically marginalized groups on scientific Python projects, and to structurally improve the community dynamics for NumPy, SciPy, Matplotlib, and Pandas.
@@ -20,5 +19,5 @@ This is an ambitious project aiming to discover and implement activities that sh
 By establishing these new cross-project roles, we hope to introduce a new collaboration model to the Scientific Python communities, allowing community-building work within the ecosystem to be done more efficiently and with greater outcomes.
 We also expect to develop a clearer picture of what works and what doesn't in our projects to engage and retain new contributors, especially from historically underrepresented groups.
 Finally, we plan on producing detailed reports on the actions executed, explaining how they have impacted our projects in terms of representation and interaction with our communities.
- 
+
 The two-year project is expected to start by November 2021, and we are excited to see the results from this work! [You can read the full proposal here](https://figshare.com/articles/online_resource/Advancing_an_inclusive_culture_in_the_scientific_Python_ecosystem/16548063).

content/news/_index.md

@@ -1,4 +1,3 @@
 ---
 title: "News"
 ---
-

content/news/specs-announced-scipy2021/video.md

@@ -8,22 +8,22 @@ Today, I am excited to introduce to you a new planning effort for
 better coordinating the Scientific Python ecosystem.
 
 So, unlike the other talks in this session, this talk is not about one
-specific tool, but rather about *all* the tools and how they work
+specific tool, but rather about _all_ the tools and how they work
 together.
 
 In the early days of the SciPy conference, we had fewer than 50
-attendees—and many of those were core library developers.  So, it was
+attendees—and many of those were core library developers. So, it was
 easy to get everyone around a table and to talk about important decisions
 that affected several projects.
 
-But that hasn't been possible for quite some time.  Unsurprisingly then, one of the
+But that hasn't been possible for quite some time. Unsurprisingly then, one of the
 concerns we've heard from users is that the ecosystem sometimes lacks
 coherence.
 
 And, to address that, we are launching an effort to get projects talking to
 one another again, to strategize about their joint future, and to make that future a reality.
 
------
+---
 
 Specifically, we have the following aims:
 
@@ -35,12 +35,12 @@ Specifically, we have the following aims:
 5. to help projects develop their own grant proposals and to get
    funded.
 
------
+---
 
 We have started work on the first aim of the project: a
 mechanism through which the community can establish cross-project policies.
 
------
+---
 
 These policy documents we call SPECs: Scientific Python Ecosystem
 Coordination documents.
@@ -51,21 +51,21 @@ any of the other enhancement proposals---except that they will be relevant to mu
 These documents will be recommendations written up by the community,
 and their authority will derive from endorsement by popular libraries.
 
------
+---
 
 A SPEC has the following lifecycle.
 
 First, it gets discussed on the Scientific Python Discussion Forum.
 We hope that this forum will eventually become a gathering place for
 many of the projects in the ecosystem.
 
------
+---
 
 Once it is clear that the idea has merit, it will become a Markdown
 document filed as a pull request on the scientific-python GitHub
 repository.
 
------
+---
 
 The SPEC will be guided through acceptance stages by community
 volunteers, known as the SPEC Steering Committee.
@@ -74,15 +74,15 @@ These are the current members of the committee, who have volunteered
 their time to help facilitate the SPEC process.
 
 It should be noted that the emphasis is specifically on facilitation,
-rather than gatekeeping.  Again, the SPECs will derive their authority
+rather than gatekeeping. Again, the SPECs will derive their authority
 from endorsement by projects in the ecosystem.
 
------
+---
 
 We thank these core projects who have agreed to serve as the
 initial SPEC endorsers.
 
------
+---
 
 If you have a great idea for improving the Scientific Python
 ecosystem, please don't hesitate to reach out!

content/press-kit.md

@@ -3,7 +3,7 @@ title: Press kit
 sidebar: false
 ---
 
-We would like to make it easy for you to include the Scientific Python project identity in your next academic paper, course materials, or presentation. 
+We would like to make it easy for you to include the Scientific Python project identity in your next academic paper, course materials, or presentation.
 
 You will find SVG versions of the Scientific Python logo [here](https://github.com/scientific-python/archive/tree/main/branding/logo).
 Note that by using the scientific-python.org resources, you accept the [Scientific Python Code of Conduct](/code_of_conduct).

content/roadmap.md

@@ -13,7 +13,7 @@ prepare scientific Python for the next decade of data science.
 We provide resources, planning, and coordination for the community.
 
 Our roadmap indicates the type of large, fundamental changes to individual projects
-and the ecosystem more generally that are likely to take months or years to realize. 
+and the ecosystem more generally that are likely to take months or years to realize.
 Given the distributed decision-making processes of the ecosystem, progress on the
 roadmap is dependent on support and agreement from the community.
 

content/summits/_index.md

@@ -2,4 +2,3 @@
 title: "Summits"
 date: 2020-12-17T20:14:42-08:00
 ---
-