diff --git a/.circleci/config.yml b/.circleci/config.yml
deleted file mode 100644
index 4151fcd3..00000000
--- a/.circleci/config.yml
+++ /dev/null
@@ -1,24 +0,0 @@
-version: 2.1
-
-jobs:
-  build:
-    docker:
-      - image: cimg/ruby:3.2.2
-    steps:
-      - checkout
-      - run:
-          name: Install dependencies
-          command: bundle install
-      - run:
-          name: Jekyll build
-          command: |
-            bundle exec jekyll build --baseurl /output/job/$CIRCLE_WORKFLOW_JOB_ID/artifacts/0/_site
-      - store_artifacts:
-          path: _site
-          destination: _site
-
-workflows:
-  version: 2
-  build:
-    jobs:
-      - build
diff --git a/.github/workflows/build-site.yml b/.github/workflows/build-site.yml
index 71a1b522..05e3a280 100644
--- a/.github/workflows/build-site.yml
+++ b/.github/workflows/build-site.yml
@@ -1,4 +1,4 @@
-name: Build and Jekyll site and run htmlproofer
+name: Build Hugo site and run htmlproofer
 
 on:
   pull_request:
@@ -17,20 +17,25 @@ jobs:
       - name: Check out the code
         uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
 
-      - name: Fetch main
-        run: |
-          git fetch origin main --depth 1
-          git branch
+      - name: Setup Node.js
+        uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4
+        with:
+          node-version: "20"
+          cache: npm
+
+      - name: Install npm dependencies
+        run: npm ci
 
-      - name: Setup Ruby
-        uses: ruby/setup-ruby@6aaa311d81eba98ae12eaffbcb63296ace0efcde # v1.307.0
+      - name: Setup Hugo
+        uses: peaceiris/actions-hugo@2752ce1d29631191ea3f27c23495fa06139a5b78 # v3
         with:
-          bundler-cache: true # runs 'bundle install' and caches installed gems automatically
+          hugo-version: "0.139.4"
+          extended: true
 
-      - name: Build with Jekyll
-        run: bundle exec jekyll build
+      - name: Build with Hugo
+        run: hugo --gc --minify
         env:
-          JEKYLL_ENV: production
+          HUGO_ENV: production
 
       - name: Restore lychee cache
         uses: actions/cache@27d5ce7f107fe9357f9df03efb73ab90386fccae # v5.0.5
@@ -43,18 +48,17 @@ jobs:
 
       - name: Check links with lychee
         id: lychee
-        uses: lycheeverse/lychee-action@8646ba30535128ac92d33dfc9133794bfdd9b411 #v2.8.0
+        uses: lycheeverse/lychee-action@8646ba30535128ac92d33dfc9133794bfdd9b411 # v2.8.0
         with:
           fail: true
-          args: --root-dir _site _site
+          args: --root-dir public public
         env:
-          GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 
       - name: Check HTML using htmlproofer
-        uses: chabad360/htmlproofer@c2750eb7eb937599ac859517e7dd23a29f1b3ed7 #v2
+        uses: chabad360/htmlproofer@c2750eb7eb937599ac859517e7dd23a29f1b3ed7 # v2
         with:
-          directory: "_site"
+          directory: "public"
           arguments: |
-            --ignore-files "/.+\/_posts\/README.md"
             --ignore-urls "/^https?:\/\/(www\.)?pyopensci\.org\//"
             --checks "Images,Scripts"
diff --git a/.github/workflows/circleci-artifact-redirector.yml b/.github/workflows/circleci-artifact-redirector.yml
deleted file mode 100644
index 85186117..00000000
--- a/.github/workflows/circleci-artifact-redirector.yml
+++ /dev/null
@@ -1,27 +0,0 @@
-name: CircleCI artifacts redirector
-on: [status]
-
-# Restrict the permissions granted to the use of secrets.GITHUB_TOKEN in this
-# github actions workflow:
-# https://docs.github.com/en/actions/security-guides/automatic-token-authentication
-permissions:
-  statuses: write
-
-jobs:
-  circleci_artifacts_redirector_job:
-    runs-on: ubuntu-latest
-    # For testing this action on a fork, remove the "github.repository =="" condition.
-    if: "github.repository == 'pyOpenSci/pyopensci.github.io' && github.event.context == 'ci/circleci: build'"
-    permissions:
-      statuses: write
-    name: Run CircleCI artifacts redirector
-    steps:
-      - name: GitHub Action step
-        id: step1
-        uses: larsoner/circleci-artifacts-redirector-action@master
-        with:
-          repo-token: ${{ secrets.GITHUB_TOKEN }}
-          api-token: ${{ secrets.CIRCLECI_TOKEN }}
-          artifact-path: 0/_site/index.html
-          circleci-jobs: build
-          job-title: Check the rendered website build here!
diff --git a/.gitignore b/.gitignore
index 8b5bb863..bf9b000d 100644
--- a/.gitignore
+++ b/.gitignore
@@ -17,3 +17,8 @@ node_modules/*
 public/
 resources/
 .lycheecache
+
+# site redesign
+.cursor/*
+_law_tests/*
+jekyll/*
diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
index 8ef7e925..99f636d0 100644
--- a/.pre-commit-config.yaml
+++ b/.pre-commit-config.yaml
@@ -35,6 +35,7 @@ repos:
     hooks:
       - id: codespell
         exclude_types:
+          - css
           - javascript
           - scss
           - yaml
diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md
new file mode 100644
index 00000000..11df6d9d
--- /dev/null
+++ b/DEVELOPMENT.md
@@ -0,0 +1,186 @@
+# Hugo site development notes
+
+Temporary reference for the pyOpenSci Hugo migration. Focus: how CSS is
+organized and built. See also `README.md` for install and serve commands.
+
+## Quick start
+
+From the repository root:
+
+```bash
+npm ci
+hugo server --disableFastRender
+```
+
+Hugo Extended is required (SCSS + PostCSS). The first run needs `npm ci` so
+PostCSS can run during the asset pipeline.
+
+Do **not** commit build output: `public/`, `resources/`, and `.hugo_build.lock`
+are gitignored.
+
+## Two CSS locations (do not confuse them)
+
+Hugo treats `assets/` and `static/` differently.
+
+| Location | Role | Committed? | Built on deploy? |
+|----------|------|------------|------------------|
+| `themes/clean-hugo/assets/css/` | Main site SCSS source | Yes (source) | Yes → compiled CSS |
+| `themes/clean-hugo/static/css/syntax.css` | Code-block highlighting only | Yes (as-is) | No — copied to site |
+
+There is no `static/scss/` folder. All authored styles live under
+`assets/css/` as SCSS partials.
+
+### `assets/css/` — main styling (SCSS)
+
+* Entry file: `themes/clean-hugo/assets/css/site.scss` (see **Jekyll coexistence**
+  below — normally this would be `main.scss`)
+* Partials: `_footer.scss`, `_blog.scss`, `_events.scss`, etc.
+* Hugo compiles this at **build time** (local `hugo server` or Netlify).
+* Output goes to `public/css/site.min.<hash>.css` — never commit that file.
+
+### `static/css/syntax.css` — code highlighting only
+
+* One pre-generated file for Chroma/monokai highlighting in fenced code blocks.
+* Served as `/css/syntax.css` with no processing.
+* Originally generated with:
+  `hugo gen chromastyles --style=monokai`
+* Not related to layout, footer, blog cards, or brand colors.
+
+## Build pipeline (what happens on `hugo server` / Netlify)
+
+Defined in `themes/clean-hugo/layouts/_default/baseof.html`:
+
+1. **Inline brand colors** — CSS custom properties from `hugo.toml`
+   `[params.theme.colors]` (injected in a `<style>` block in `<head>`).
+2. **Main stylesheet** — Hugo Pipes pipeline:
+
+   ```go
+   {{ $styles := resources.Get "css/site.scss" | toCSS | postCSS | minify | fingerprint }}
+   ```
+
+   Steps: SCSS → CSS → PostCSS (autoprefixer) → minify → fingerprinted URL.
+
+3. **Syntax CSS** — plain link to `/css/syntax.css` from theme `static/`.
+
+Root `package.json` and `postcss.config.js` exist **for step 2 only**. They are
+not used by Jekyll.
+
+## SCSS file map
+
+`site.scss` imports partials in this order (simplified):
+
+| Partial | Purpose |
+|---------|---------|
+| `_variables.scss` | Breakpoints, spacing, shadows, typography tokens |
+| `_mixins.scss` | Shared SCSS mixins |
+| `_buttons.scss` | Button tiers |
+| `_utilities.scss` | Skip links, a11y helpers |
+| *(base rules in site.scss)* | Box-sizing, body, headings |
+| `_navigation.scss` | Header, nav, mobile menu |
+| `_content.scss` | Prose / page content |
+| `_blog.scss` | Single post layout |
+| `_blog-listing.scss` | Blog index, cards, filters |
+| `_events.scss` | Events listing and detail |
+| `_footer.scss` | Site footer |
+| `_hero.scss` | Hero sections |
+| `_cards.scss` | Card grids |
+| `_shortcodes.scss` | Shortcode markup (admonitions, cards, etc.) |
+| `_admonition.scss` | Callout blocks |
+| `_code.scss` | Inline code styling (not syntax colors) |
+| `_figure.scss` | Figures and captions |
+| Other partials | Gallery, packages, people, docs, swoosh, filters, … |
+
+When adding styles, prefer the partial that matches the component. Extend
+existing partials before adding new files.
+
+## Colors and typography
+
+**Brand colors** — set in `hugo.toml` under `[params.theme.colors]`. These
+become CSS variables (e.g. `--color-primary`) at build time. Prefer changing
+colors there for site-wide brand updates.
+
+**SCSS variables** — in `_variables.scss` (`$spacing-md`, `$breakpoint-lg`,
+etc.). Use for layout, spacing, and component structure inside the theme.
+
+**Fonts** — loaded via `@font-face` in `site.scss` from
+`themes/clean-hugo/static/fonts/`. Font family names are configured in
+`hugo.toml` `[params.theme.fonts]`.
+
+## Site `static/` vs theme `static/`
+
+Two different `static/` trees:
+
+| Path | Contents |
+|------|----------|
+| `static/` (repo root) | Site images (`static/images/`), favicons, `CNAME` → published as `/images/...`, `/favicon.ico`, etc. |
+| `themes/clean-hugo/static/` | Theme assets: fonts, JS, `css/syntax.css` → bundled with theme |
+
+Do not move site images into the theme unless they are truly theme-only.
+
+## Local workflow for CSS changes
+
+1. Edit SCSS under `themes/clean-hugo/assets/css/`.
+2. Save — `hugo server --disableFastRender` rebuilds automatically.
+3. If PostCSS errors mention `npx` or `postcss-cli`, run `npm ci` at repo root.
+4. Commit **SCSS changes only** — not `public/` or `resources/`.
+
+To regenerate syntax highlighting after changing `hugo.toml`
+`[markup.highlight]` style:
+
+```bash
+hugo gen chromastyles --style=monokai > themes/clean-hugo/static/css/syntax.css
+```
+
+Then commit the updated `syntax.css`.
+
+## Jekyll coexistence (temporary — revert at cutover)
+
+While Jekyll and Hugo share this repo, **root** `assets/css/main.scss` remains
+on `main`. That file is Jekyll’s Minimal Mistakes entry point and starts with
+YAML front matter (`---`), which Hugo’s SCSS compiler cannot parse.
+
+Hugo’s `resources.Get "css/main.scss"` resolves **site `assets/` before theme
+`assets/`**, so the Jekyll file shadows the theme stylesheet and Netlify builds
+fail.
+
+**Workaround (current):**
+
+* Theme entry SCSS is named `site.scss` (not `main.scss`).
+* Layouts load `resources.Get "css/site.scss"` in `baseof.html` and `404.html`.
+
+**Revert when Jekyll is retired** (after root Jekyll assets are removed or
+moved under `jekyll/`):
+
+1. Rename `themes/clean-hugo/assets/css/site.scss` → `main.scss`.
+2. Update `baseof.html` and `404.html` to `resources.Get "css/main.scss"`.
+3. Remove this section from `DEVELOPMENT.md`.
+
+## Netlify
+
+`netlify.toml` runs `npm ci && hugo --gc --minify`. CSS is built on Netlify the
+same way as locally. No separate CSS build step or committed compiled bundle is
+required for the main stylesheet.
+
+## GitHub Actions (CI)
+
+On pull requests and pushes to `main`, `.github/workflows/build-site.yml` runs
+the same Hugo build as Netlify, then validates the output:
+
+1. **Setup** — `npm ci` (PostCSS deps), Hugo Extended **0.139.4** (matches
+   `netlify.toml` `HUGO_VERSION`).
+2. **Build** — `hugo --gc --minify` with `HUGO_ENV=production` → output in
+   `public/`.
+3. **Link check** — [lychee](https://github.com/lycheeverse/lychee) against
+   `public/` (config in `lychee.toml`, domain skips in `.lycheeignore`).
+4. **HTML check** — [htmlproofer](https://github.com/gjtorikian/html-proofer) on
+   `public/` (images and scripts; skips live pyopensci.org URLs that lag deploy).
+
+CircleCI and the CircleCI artifact redirector were removed during the Hugo
+migration.
+
+**Still on Jekyll (migrate later):**
+
+| Workflow | Purpose |
+|----------|---------|
+| `.github/workflows/linkcheck.yml` | Weekly scheduled link check |
+| `.github/workflows/deploy-gh-pages.yml` | GitHub Pages deploy badge in README |
diff --git a/_data/packages.yml b/_data/packages.yml
index 9aa96c46..b00ec872 100644
--- a/_data/packages.yml
+++ b/_data/packages.yml
@@ -1724,7 +1724,7 @@
       github_username: '2023-12-13'
   archive:
   version_accepted: TBD
-  date_accepted: missing
+  date_accepted: '2026-03-11'
   created_at: 2023-11-17 20:39:40+00:00
   updated_at: 2026-05-07 15:36:30+00:00
   closed_at:
diff --git a/content/_index.md b/content/_index.md
new file mode 100644
index 00000000..b3c76091
--- /dev/null
+++ b/content/_index.md
@@ -0,0 +1,109 @@
+---
+title: "Strengthening Scientific Open Source, Together"
+date: 2025-04-30
+draft: false
+layout: splash
+cards_layout: wide
+description: "We support the open source contributors and developers who fuel scientific discovery."
+hero:
+  title: "Strengthening Scientific Open Source, Together"
+  excerpt: "We support the open source contributors and developers who fuel scientific discovery."
+  color: "#33205C"
+  square_image: true
+  buttons:
+    - label: "Learn to Create a Python Package"
+      url: "https://www.pyopensci.org/python-package-guide/tutorials/create-python-package.html"
+    - label: "Submit a Package For Review"
+      url: "https://www.pyopensci.org/how-to-submit-a-package-to-pyopensci.html"
+training_feature:
+  eyebrow: "Training"
+  badge: "New cohort coming fall 2026"
+  title: "Ship It: Python Packaging in the Era of AI"
+  excerpt: |
+    A 10-day online course for researchers, academics, and RSEs — from working
+    code to a published package.
+  button_label: "Learn more"
+  button_url: "/events/shipit-python-package-gen-ai-april-2026.html"
+  image:
+    src: "images/landing-pages/scipy-sprint-2026.png"
+    alt: "Python packaging guide graphic with a laptop and hands over keyboard."
+cards:
+  - title: "We run software peer review"
+    image:
+      src: "images/landing-pages/scipy-sprint-working.png"
+      alt: "Illustration for software peer review — person at a laptop with pyOpenSci branding."
+    excerpt: |
+      We review Python packages with the goal of helping scientists build better, discoverable, and usable software. Accepted packages can be published in **JOSS** through our review process.
+    url: "https://www.pyopensci.org/about-peer-review/index.html"
+    cta: "About peer review →"
+  - title: "We connect researchers, contributors, and developers"
+    image:
+      src: "images/landing-pages/scipy-bof-working.png"
+      alt: "Illustration for community partnerships — diverse figures collaborating."
+    excerpt: |
+      pyOpenSci brings together researchers, core Python and conda developers, and data scientists from industry and universities to strengthen scientific open source. We partner with communities to share resources, knowledge, and processes like peer review.
+    url: "https://www.pyopensci.org/software-peer-review/partners/scientific-communities.html"
+    cta: "Community partnerships →"
+  - title: "We break down Python packaging pain points"
+    image:
+      src: "images/landing-pages/scipy-sprint-2026.png"
+      alt: "Python packaging guide graphic with a laptop and hands over keyboard."
+    excerpt: |
+      Beginner-friendly tutorials and a community **Python packaging guide**, co-developed with the broader Python ecosystem so the material stays accessible at every level.
+    url: "https://www.pyopensci.org/python-package-guide/"
+    cta: "Python packaging guide →"
+  - modifier: "card--white"
+    icon: "fa-solid fa-paper-plane"
+    title: "Submit your package"
+    excerpt: "Ready for review? Learn what we look for and how to submit your scientific Python package."
+    url: "https://www.pyopensci.org/software-peer-review/how-to/author-guide.html"
+    cta: "Author guide →"
+  - modifier: "card--white"
+    icon: "fa-solid fa-people-group"
+    title: "Become a reviewer"
+    excerpt: "Join reviewers who care about usability, docs, and maintainability — mentorship is available for your first review."
+    url: "https://www.pyopensci.org/software-peer-review/how-to/reviewer-guide.html"
+    cta: "Reviewer guide →"
+  - modifier: "card--white"
+    icon: "fa-solid fa-calendar-days"
+    title: "Events & training"
+    excerpt: "Workshops, cohort courses, sprints, and community calls — online and at conferences."
+    url: "/events/"
+    cta: "Browse events →"
+---
+
+
+{{< home-programs-full >}}
+
+{{< training-feature >}}
+
+## Upcoming events
+
+{{< upcoming-events limit="3" view_all="true" >}}
+
+## Broadening participation in scientific open source
+
+![People working at computers during a pyCon USA sprint.](/images/people/pyopensci-sprint-pycon-2023.png)
+
+### You don't need to be an expert to get involved
+
+Are you new to software peer review but you want to get involved? We've got you!
+We offer support and mentorship to new reviewers completing their first review.
+
+Reviewers do not need to be Python packaging experts. We welcome reviewers who
+focus on software accessibility and usability.
+
+Are you new to peer review? We offer a
+[mentorship program](https://www.pyopensci.org/software-peer-review/how-to/reviewer-guide.html#a-guide-for-new-reviewers)
+for anyone interested in participating in peer review but who might like a bit
+of support.
+
+## New pyOpenSci contributors
+
+*(Placeholder: Jekyll home listed five people from `site.data.contributors`.
+Port `people-grid` or the theme people partial when `data/contributors.yml` is
+mounted or copied for Hugo.)*
+
+{{< blog-list title="Recent blog posts & updates" limit="3" >}}
+
+{{< recent-packages limit="3" >}}
diff --git a/content/about-peer-review.md b/content/about-peer-review.md
new file mode 100644
index 00000000..b0e76758
--- /dev/null
+++ b/content/about-peer-review.md
@@ -0,0 +1,190 @@
+---
+title: "pyOpenSci makes Python software better and easier to find through peer review"
+layout: splash
+url: /about-peer-review/
+aliases:
+  - /partners.html
+description: >-
+  Our open peer review process makes scientific software better and easier to
+  discover. Volunteer editors and reviewers support maintainers across the
+  Python scientific ecosystem.
+hero:
+  title: "pyOpenSci makes Python software better and easier to find through peer review"
+  excerpt: >-
+    Our open peer review process makes scientific software better and easier to
+    discover.
+  image:
+    src: images/headers/pyos-peer-review-header.png
+    alt: "Illustration representing pyOpenSci software peer review."
+intro_section:
+  text: >-
+    Our open peer review process makes scientific software better and easier to
+    discover. [Check out our accepted packages.](/python-packages/)
+---
+
+{{< intro-section >}}
+
+{{< admonition type="info" title="Volunteer editors needed" >}}
+pyOpenSci is growing, and we need volunteer editors to keep supporting
+scientists building open source software. Editors oversee reviews, find
+reviewers, and help authors through the process — mentorship is available if
+you are new to the role.
+
+[Apply to join the editorial board](https://docs.google.com/forms/d/e/1FAIpQLScRQHQ7NKVEAG3BKAphiUdVFvQ5nkez0IpyXBMZDzXjuBPloQ/viewform)
+or read the [Editor Guide](https://www.pyopensci.org/software-peer-review/how-to/editors-guide.html).
+{{< /admonition >}}
+
+{{< swoosh_section background="purple" swoosh="bottom" >}}
+
+## How Python software peer review works
+
+Software peer review, similar to the review of scientific papers, is a process
+where scientists vet software code, documentation, and infrastructure. pyOpenSci
+leads an [open peer review process](https://www.pyopensci.org/software-peer-review/our-process/how-review-works.html)
+run by a community of dedicated volunteers. Reviews are supportive and fully
+transparent with the shared goal of improving the quality, usability, and
+maintainability of the software that is driving open science.
+
+Diverse teams lead each review, enhancing the overall feedback quality.
+
+{{< figure src="/images/landing-pages/peer-review-people.png" alt="A pencil sketch of people from different backgrounds working together at a round table." caption="Peer review is led by volunteer editors and reviewers from across the scientific Python community." >}}
+
+{{< button href="https://www.pyopensci.org/software-peer-review/our-process/review-timeline.html" variant="dark-purple" target="_blank" >}}
+Learn about the peer review timeline and roles
+{{< /button >}}
+
+{{< figure src="/images/landing-pages/pyopensci-joss-partners.png" alt="Diagram showing pyOpenSci and JOSS partnership." caption="Our partnership with JOSS means you do not have to choose between pyOpenSci and JOSS." >}}
+
+{{< button href="https://www.pyopensci.org/software-peer-review/partners/joss.html" variant="dark-purple" target="_blank" >}}
+Learn more about our JOSS partnership
+{{< /button >}}
+
+{{< /swoosh_section >}}
+
+<div class="container">
+
+## Scientists need trusted and vetted software
+
+Through our partnerships with domain-specific communities, our catalog of
+trusted tools for scientists across domains continues to grow.
+
+{{< figure src="/images/landing-pages/trusted-python-software.png" alt="Illustration of scientists collaborating around trusted Python tools." >}}
+
+{{< button href="#community-partners" variant="dark-purple" >}}
+Learn more about scientific Python community partnerships
+{{< /button >}}
+
+## Peer review benefits open source maintainers
+
+The pyOpenSci peer review process multiplies shared knowledge, making it easier
+for Pythonistas of all levels to accomplish challenging tasks, such as navigating
+the Python packaging ecosystem. Our diverse community supports scientific
+package maintainers in their efforts to develop and build robust software.
+
+{{< figure src="/images/landing-pages/peer-review-supports-maintainers.png" alt="Illustration of maintainers supported through peer review." >}}
+
+{{< button href="https://www.pyopensci.org/software-peer-review/about/benefits.html" variant="dark-purple" target="_blank" >}}
+Learn more about the benefits of peer review
+{{< /button >}}
+
+</div>
+
+{{< swoosh_section background="purple" swoosh="top" >}}
+
+## Get involved with software peer review
+
+{{< two-card-row >}}
+{{< card title="Become a pyOpenSci reviewer" icon="fa-solid fa-user-pen" >}}
+We could use your help! Fill out our reviewer form. We will contact you if we
+have a package that needs reviewers. It is OK if you have never reviewed a
+package before — we will walk you through it.
+
+{{< button href="https://forms.gle/GHfxvmS47nQFDcBM6" variant="green" target="_blank" >}}
+Sign up now (Google Form)
+{{< /button >}}
+{{< /card >}}
+
+{{< card title="See our review process in action" icon="fa-brands fa-github" >}}
+Our software review process is run using GitHub issues. Anyone can check in on
+any part of any review and read the full conversation.
+
+{{< button href="https://github.com/pyOpenSci/software-submission" variant="green" target="_blank" >}}
+See open reviews
+{{< /button >}}
+{{< /card >}}
+{{< /two-card-row >}}
+
+{{< single-card-wide title="Ready to submit a package for review?" icon="fa-solid fa-rocket" >}}
+To submit a package, [open an issue in our peer review GitHub repository](https://github.com/pyOpenSci/software-submission/issues/new/choose).
+Learn about the steps in our guidebook or on our [submit a package](/how-to-submit-a-package-to-pyopensci/) page.
+
+{{< button href="/how-to-submit-a-package-to-pyopensci/" variant="dark-purple" >}}
+How to submit a package
+{{< /button >}}
+{{< /single-card-wide >}}
+
+{{< /swoosh_section >}}
+
+{{< editorial-board >}}
+
+{{< recent-packages limit="3" >}}
+
+{{< swoosh_section background="purple" swoosh="bottom" >}}
+
+## Community partners {#community-partners}
+
+Domain-specific communities can partner with pyOpenSci to leverage our peer
+review process and Python packaging guidelines — without building a separate
+review program from scratch.
+
+{{< figure src="/images/peer-review/peer-review-partners-process.png" alt="Diagram showing submit, review, and accepted steps for community-affiliated packages." caption="Community partnerships add a domain-specific layer to our open peer review process." >}}
+
+{{< button href="https://www.pyopensci.org/software-peer-review/partners/scientific-communities.html" variant="dark-purple" target="_blank" >}}
+Learn how community partnerships work
+{{< /button >}}
+
+{{< figure src="/images/peer-review/pyos-partnerships-peer-review.png" alt="Diagram showing pyOpenSci acceptance leading to JOSS publication and community affiliation." >}}
+
+Through a single review process, community maintainers can have their package
+accepted into the pyOpenSci ecosystem, [published in JOSS (if in scope)](https://www.pyopensci.org/software-peer-review/partners/joss.html),
+and affiliated with your community following your guidelines.
+
+{{< /swoosh_section >}}
+
+<div class="container">
+
+## Partnering with pyOpenSci increases visibility for your community's tools
+
+We will:
+
+* Promote your community and its packages on our website.
+* Post about affiliated packages on our social media channels.
+* List packages on our [packages page](/python-packages/).
+* Provide a feed allowing you to cross-list affiliated packages on your website.
+* Keep in touch with maintainers to ensure packages are actively maintained.
+
+## Leverage our peer review process
+
+Your domain-specific community can use our documented peer review process,
+including:
+
+* **A growing team of editors** from diverse scientific and technical backgrounds.
+  Partner communities typically have at least two members on our editorial team.
+* **Community reviewers** whose expertise spans numerous scientific domains.
+* **Community-driven packaging resources** that drive the peer review process.
+
+{{< button href="https://www.pyopensci.org/software-peer-review/partners/scientific-communities.html" variant="dark-purple" target="_blank" >}}
+Learn more about our partnerships
+{{< /button >}}
+
+{{< figure src="/images/landing-pages/women-collaborating.png" alt="A pencil sketch of women collaborating around a laptop." >}}
+
+Partnering with pyOpenSci connects you to packaging experts, open science
+enthusiasts, and Pythonistas who can help with maintenance transitions when
+needed.
+
+{{< button href="/our-community/" variant="outline" >}}
+Explore our community contributors
+{{< /button >}}
+
+</div>
diff --git a/content/blog/2019-10-25-welcome-to-pyopensci.md b/content/blog/2019-10-25-welcome-to-pyopensci.md
new file mode 100644
index 00000000..9cfc4373
--- /dev/null
+++ b/content/blog/2019-10-25-welcome-to-pyopensci.md
@@ -0,0 +1,22 @@
+---
+title: Welcome to the pyOpenSci Blog!
+date: '2019-10-25'
+type: blog
+excerpt: pyOpenSci is a community organization devoted to the development of robust
+  open source Python software to support science.
+author: Leah Wasser
+blog_topic: updates
+url: blog/welcome-to-pyopensci/
+---
+
+## Welcome To PyOpenSci!
+
+This is just a short post to let everyone know that we are starting a community blog post. Here we will write about many things including:
+
+1. Packages that have gone through the review process.
+2. Challenges that PyOpenSci is confronting in the open source Python community
+3. Activities and events going on
+
+and more.
+
+Stay tuned for more in the upcoming months!
diff --git a/content/blog/2019-10-26-pyos-min-mistakes-theme.md b/content/blog/2019-10-26-pyos-min-mistakes-theme.md
new file mode 100644
index 00000000..fe949a91
--- /dev/null
+++ b/content/blog/2019-10-26-pyos-min-mistakes-theme.md
@@ -0,0 +1,23 @@
+---
+title: pyOS Website Theme Docs
+date: '2019-10-26'
+type: blog
+excerpt: pyOpenSci minimal mistakes theme documentation.
+author: pyopensci
+blog_topic: community
+toc: true
+url: docs/pyos-website/
+lastmod: '2025-03-24'
+---
+
+## Text alignment
+
+Align text blocks with the following classes.
+
+Left aligned text `.text-left`
+{: .text-left}
+
+```markdown
+Left aligned text
+{: .text-left}
+```
diff --git a/content/blog/2019-11-18-pandera-dataframe-validation.md b/content/blog/2019-11-18-pandera-dataframe-validation.md
new file mode 100644
index 00000000..329e9e5a
--- /dev/null
+++ b/content/blog/2019-11-18-pandera-dataframe-validation.md
@@ -0,0 +1,260 @@
+---
+title: 'Pandera: A Statistical Data Validation Toolkit for Pandas'
+date: '2019-11-18'
+type: blog
+excerpt: Pandera is a a flexible and expressive toolkit for performing statistical
+  validation checks on pandas data structures that was recently accepted into the
+  pyOpenSci ecosystem. Learn more about Pandera.
+author: Niels Bantilan
+blog_topic: software
+comments: true
+url: "/blog/pandera-python-pandas-dataframe-validation.html"
+image:
+  src: images/blog/headers/pandas.png
+  alt: 'Pandera: A Statistical Data Validation Toolkit for Pandas'
+---
+
+Modern data engineering and analysis workflows will often involve using data
+manipulation libraries, which, in the Python universe, would be tools like
+[pandas](https://pandas.pydata.org/). One problem you may have encountered with
+this powerful data manipulation tool is that the dataframe can be an opaque
+object that's hard to reason about in terms of its contents, data types, and
+other properties.
+
+One tool that may help you with this problem is
+[pandera](https://pandera.readthedocs.io/en/latest/index.html), which was
+accepted by pyOpenSci as part of its ecosystem of packages on September 2019.
+Pandera provides a flexible and expressive data validation toolkit that helps
+users make statistical assertions about pandas data structures.
+
+## A Statistical Data Validation Toolkit for Pandas
+
+<img src="https://github.com/unionai-oss/pandera/tree/master/docs/source/_static/pandera-logo.png"
+width="250px" alt="Image showing pandera package logo.">
+
+To illustrate `pandera`'s capabilities let's use a small toy example. Suppose
+you're analyzing data for some insights in the context of a mission-critical
+project, where it’s vital to ensure the quality of the datasets that you're
+looking at.
+
+Each row in the dataset is uniquely identified by a `person_id`, and each
+column describes that person's `height_in_cm`s and `age_category`.
+
+
+```python
+import pandas as pd
+
+dataset = pd.DataFrame(
+    data={
+        "height_in_cm": [150, 145, 122, 176, 137, 151],
+        "age_category": ["20-30", "10-20", "10-20", "20-30", "10-20", "20-30"],
+    },
+    index=pd.Series([100, 101, 102, 103, 104, 105], name="person_id"),
+)
+print(dataset)
+```
+
+```
+           height_in_cm age_category
+person_id
+100                 150        20-30
+101                 145        10-20
+102                 122        10-20
+103                 176        20-30
+104                 137        10-20
+105                 151        20-30
+```
+
+You want to ensure that some columns have the correct data type, or that the
+dataset fulfills certain statistical properties. Pandera allows you to validate
+a DataFrame to ensure that these conditions are met. It allows you to spend
+less time worrying about the correctness of a DataFrame's data so you can make
+the right assumptions in analyzing it.
+
+
+### Column Presence and Type Checking
+
+The most basic type of schema is one that simply checks that specific columns
+exist with specific datatypes.
+
+```python
+import pandera as pa
+
+schema = pa.DataFrameSchema(
+    columns={
+        "height_in_cm": pa.Column(pa.Int),
+        "age_category": pa.Column(pa.String),
+    },
+    index=pa.Index(pa.Int, name="person_id"),
+)
+
+schema(dataset)
+```
+
+The `schema` object is callable, so you can validate the dataset by passing
+it in as an argument to the `schema` call. If the dataframe passes schema
+validation, `schema` simply returns the dataframe.
+
+If not, it'll provide useful error messages:
+
+
+```python
+invalid_dataframe = pd.DataFrame({
+    "weight_in_kg": [44, 31, 55, 61, 55, 62],
+    "age_category": ["20-30", "10-20", "10-20", "20-30", "10-20", "20-30"],
+})
+
+schema(invalid_dataframe)
+```
+
+```
+SchemaError: column 'height_in_cm' not in dataframe
+   weight_in_kg age_category
+0            44        20-30
+1            31        10-20
+2            55        10-20
+3            61        20-30
+4            55        10-20
+```
+
+### Basic Statistical Checks
+
+If you want to make stricter assertions about the empirical properties of the
+dataset, we can supply the `checks` keyword argument to the
+[`Column`](https://pandera.readthedocs.io/en/latest/dataframe_schemas.html#column-validation)
+and [`Index`](https://pandera.readthedocs.io/en/latest/dataframe_schemas.html#index-validation)
+constructors with a [`Check`](https://pandera.readthedocs.io/en/latest/checks.html#)
+or list of `Check`s.
+
+```python
+schema = pa.DataFrameSchema(
+    columns={
+        "height_in_cm": pa.Column(
+            pa.Int,
+            # height in centimeters should be between 100 and 300
+            checks=pa.Check(lambda s: (100 < s) & (s < 300)),
+        ),
+        "age_category": pa.Column(
+            pa.String,
+            # check allowable age categories
+            checks=pa.Check(lambda s: s.isin(["10-20", "20-30"]))
+        ),
+    },
+    index=pa.Index(
+        pa.Int,
+        name="person_id",
+        checks=[
+            # id is a positive integer
+            pa.Check(lambda s: s > 0),
+
+            # id is unique
+            pa.Check(lambda s: s.duplicated().sum() == 0),
+        ]
+    ),
+)
+
+schema(dataset)
+```
+
+A `Check` object specifies the exact implementation of how to validate a
+column or index. The first positional argument in its constructor is a callable
+with the signature:
+
+```
+Callable[ pd.Series, Union[ bool, pd.Series[bool] ] ]
+```
+
+Notice that the only constraint to the callable is that takes a `Series` as
+input and returns a boolean or a boolean Series. By design, checks have access
+to the entire pandas `Series` API to make assertions about the properties of a
+particular column or index.
+
+### Indexed Error Messages
+
+In cases where the `Check` returns a boolean `Series`, violations of the
+schema are reported by the index location of failure cases.
+
+```python
+invalid_data = pd.DataFrame(
+    data={
+        "height_in_cm": [91, 105, 87, 87],
+        "age_category": ["10-20", "10-20", "10-20", "10-20"]
+    },
+    index=pd.Series([200, 201, 202, 203], name="person_id")
+)
+
+schema(invalid_data)
+```
+
+```
+pandera.errors.SchemaError: <Schema Column: 'height_in_cm' type=int64> failed element-wise validator 0:
+<lambda>
+failure cases:
+               person_id  count
+failure_case
+87            [202, 203]      2
+91                 [200]      1
+```
+
+The error is reported as a stringified dataframe where the `failure_case` index
+enumerates instances of `height_in_cm` values that failed data validation, the
+`person_id` column is the index location of the failure case, and `count`
+column displays the number of instances of a particular failure case.
+
+
+### Statistical Hypothesis Tests
+
+What if we wanted to test the hypothesis that older people tend to be taller?
+We can achieve this with the [`Hypothesis`](https://pandera.readthedocs.io/en/latest/hypothesis.html)
+check:
+
+```python
+schema = pa.DataFrameSchema(
+    columns={
+        "height_in_cm": pa.Column(
+            # perform a one-sided two-sample t-test of
+            # the distribution of heights by age category,
+            # with an alpha value of 5%
+            checks=pa.Hypothesis.two_sample_ttest(
+                groupby="age_category",
+                sample1="20-30",
+                relationship="greater_than",
+                sample2="10-20",
+                alpha=0.05,
+                equal_var=True,
+            )
+        ),
+        "age_category": pa.Column(
+            pa.String,
+            checks=pa.Check(lambda s: s.isin(["10-20", "20-30"])),
+        )
+    }
+)
+
+schema(dataset)
+```
+
+## Validate your Pandas Dataframes Today!
+
+Whether you use this tool in Jupyter notebooks, one-off scripts, ETL
+pipeline code, or unit tests, `pandera` enables you to make pandas code more
+readable and robust by enforcing the deterministic and statistical properties
+of pandas data structures at runtime.
+
+Hopefully this post has given you a flavor of what `pandera` can do. It
+offers a few more features that you may find useful:
+
+- [Series schema validation](https://pandera.readthedocs.io/en/latest/series_schemas.html)
+- [Coercing column data types](https://pandera.readthedocs.io/en/latest/dataframe_schemas.html#coercing-types-on-columns)
+- [Multi-index validation](https://pandera.readthedocs.io/en/latest/dataframe_schemas.html#multiindex-validation)
+- [Vectorized vs. element-wise checks](https://pandera.readthedocs.io/en/latest/checks.html#vectorized-vs-element-wise-checks)
+- [Wide checks](https://pandera.readthedocs.io/en/latest/checks.html#wide-checks)
+- [Groupby Column Checks](https://pandera.readthedocs.io/en/latest/checks.html#column-check-groups)
+- [Check input/output decorators](https://pandera.readthedocs.io/en/latest/decorators.html)
+
+## What's Next?
+
+I'm actively developing this project and have some exciting features coming
+up soon, such as [built-in checks](https://github.com/pandera-dev/pandera/issues/74), [first-class Dask support](https://docs.dask.org/en/latest/dataframe.html),
+and [yaml schema specification](https://github.com/pandera-dev/pandera/issues/91). If you'd like to contribute to this
+project, you're welcome to head on over to the [github repo](https://github.com/pandera-dev/pandera)!
diff --git a/content/blog/2019-12-03-agu-2019-pyopensci-events.md b/content/blog/2019-12-03-agu-2019-pyopensci-events.md
new file mode 100644
index 00000000..e8d73e43
--- /dev/null
+++ b/content/blog/2019-12-03-agu-2019-pyopensci-events.md
@@ -0,0 +1,42 @@
+---
+title: 'PyOpenSci at AGU 2019: Join Us'
+date: '2019-12-03'
+type: blog
+excerpt: Several pyOpenSci and Open Source Software events will occur at AGU 2019.
+  Come learn more about open source Python tools for science.
+author: Leah Wasser
+blog_topic: community
+url: "/blog/pyopensci-at-agu-2019-python.html"
+---
+
+Hey all! I'm a part of the pyOpenSci Leadership team and Director of the Earth Analytics Education Initiative at Earth Lab, University of
+Colorado, Boulder. There are several open source software events that you may
+want to consider if you plan to be at AGU 2019 this year in San Francisco.
+Please join us to learn more about pyOpenSci and to help shape what pyOpenSci
+becomes.
+
+All are welcome!!
+
+## pyOpenSci Ignite Talk: Tuesday Dec 10, 2019 8am in Moscone West - 2010, L2
+
+I will giving an <a href="https://agu.confex.com/agu/fm19/meetingapp.cgi/Paper/541546" target="_blank">invited ignite talk: pyOpenSci Promoting Open Source Python Software To Support Open Reproducible Science</a>. This talk is a part of a larger open source software initiative organized by pyOpenSci collaborators
+Leonardo Uieda  and Lindsey Heagy.
+
+
+## pyOpenSci Town Hall: Wed Dec 11, 2019 12:30-1:30pm in Moscone West - 2002
+
+Please join us for a town hall dedicated to pyOpenSci: Data FAIR: pyOpenSci: Building a Community Around Open Source Python Software for Science.
+We expect a strong presence from the rOpenSci community at this event as well!
+pyOpenSci is being modeled after rOpenSci, but focused on the Python
+programming language!
+
+<div class="notice--warning" markdown="1">
+### AGU Event Resources - Sign Up To Be A Reviewer & Townhall Presentation
+
+Here are a few resources shared at the town hall:
+1. The <a href="https://docs.google.com/presentation/d/1emWah0WC9Or5uSH5IYyf0FfiPinLgqCr/edit?usp=sharing&ouid=112367566823345023071&rtpof=true&sd=true" target="_blank">pyopensci ignite talk </a>from the open source ignite session
+
+### Signing Off For Now
+I look forward to meeting you at AGU 2019!! Connect with my on twitter if you have questions at AGU! <a href="https://twitter.com/leahawasser" target="_blank">@leahawasser</a>. I will be tweeting during the event!
+
+~leah
diff --git a/content/blog/2020-04-29-movingpandas-movement-data-analysis.md b/content/blog/2020-04-29-movingpandas-movement-data-analysis.md
new file mode 100644
index 00000000..ec12dbcd
--- /dev/null
+++ b/content/blog/2020-04-29-movingpandas-movement-data-analysis.md
@@ -0,0 +1,104 @@
+---
+title: 'MovingPandas: Data Structures and Methods for Movement Data Analysis'
+date: '2020-04-29'
+type: blog
+excerpt: MovingPandas is an easy to use toolkit for exploring movement data that has
+  recently passed the PyOpenSci review.
+author: Anita Graser
+blog_topic: software
+comments: true
+url: "/blog/movingpandas-movement-data-analysis.html"
+image:
+  src: images/blog/headers/pandas.png
+  alt: 'MovingPandas: Data Structures and Methods for Movement Data Analysis'
+---
+
+Movement data is everywhere: from tracking apps that record human or vehicle movement to ecologists monitoring wildlife behavior. Movement data analysis is challenging since movement data combines time series and spatial data analyses questions. Existing spatial analysis libraries, such as GeoPandas, are great at handling spatial data but they don't support moving objects.
+
+MovingPandas aims to fill the gap of missing tools for exploring movement data. It provides data structures and methods for dealing with data of moving objects. MovingPandas has been accepted by pyOpenSci as part of its ecosystem in March 2020.
+
+## A Toolkit for Movement Data Analysis
+
+The MovingPandas repository contains multiple tutorials in the form of Jupyter notebooks that illustrate diverse analysis capabilities using different datasets, including: tracking data of ships, migration of birds, and tracks from a horse's GPS collar.
+
+MovingPandas Trajectory objects are created from GeoPandas GeoDataFrames. A minimal example would be:
+
+```python
+import pandas as pd
+import geopandas as gpd
+import movingpandas as mpd
+from shapely.geometry import Point
+from datetime import datetime
+from pyproj import CRS
+
+df = pd.DataFrame([
+  {'geometry':Point(0,0), 't':datetime(2018,1,1,12,0,0)},
+  {'geometry':Point(6,0), 't':datetime(2018,1,1,12,6,0)},
+  {'geometry':Point(6,6), 't':datetime(2018,1,1,12,10,0)},
+  {'geometry':Point(9,9), 't':datetime(2018,1,1,12,15,0)}
+]).set_index('t')
+gdf = gpd.GeoDataFrame(df, crs=CRS(31256))
+traj = mpd.Trajectory(gdf, 1)
+```
+
+MovingPandas provides static plots using Matplotlib and interactive plots using hvplot:
+
+```python
+traj.plot()
+```
+
+![The trajectory is plotted as a blue line on a white background with latitude and longitude values labeled on the axes.]({{ site.url }}/images/movingpandas/mp_fig1.png)
+
+Matplotlib and hvplot parameters are passed along to the underlying libraries to enable extensive customization of plots:
+
+```python
+traj.hvplot(geo=True, tiles='OSM', line_width=5, frame_width=300, frame_height=300)
+```
+
+![The trajectory is plotted as a wide blue line on an OpenStreetMap background with latitude and longitude values labeled on the axes.]({{ site.url }}/images/movingpandas/mp_fig2.png)
+
+### Exploring Movement Characteristics
+
+MovingPandas makes it straightforward to compute movement characteristics, such as trajectory length and duration, as well as movement speed and direction.
+
+For example, we can explore the daily travelled distance as recorded by a GPS tracker:
+
+```python
+df = read_file('tracker.gpkg')
+df = df.set_index('t')
+tc = mpd.TrajectoryCollection(df, 'CollarID')
+
+daily = tc.split_by_date(mode='day')
+daily_lengths = [traj.get_length() for traj in daily.trajectories]
+daily_t = [traj.get_start_time() for traj in daily.trajectories]
+daily_lengths = pd.DataFrame(daily_lengths, index=daily_t, columns=['length'])
+daily_lengths.hvplot(title='Daily trajectory length')
+```
+
+![The evolution of the length of the daily trajectories is plotted over the whole obseration period.]({{ site.url }}/images/movingpandas/mp_fig3.png)
+
+In this case, the movement data, which comes from a GPS collar of a horse, reveals that the animal tends to travel farther during summer days than during shorter winter days.
+
+Other functions deal with trajectory generalization, splitting trajectories into subtrajectories, clipping trajectories to an area of interest, and extracting trajectory start and end times and locations.
+
+### Standing on the Shoulders of Giants
+
+By leveraging existing functionality within the Python data analysis ecosystem, such as, for example:
+time series handling by Pandas,
+spatial data analysis by GeoPandas, and
+interactive plotting by HoloViews,
+MovingPandas can focus on its core functionality dealing with challenges that are specific to movement data.
+
+For example, the close integration with HoloViews makes it possible to create
+[interactive dashboards](https://holoviews.org/user_guide/Dashboards.html) to explore the effect of different trajectory generalization methods:
+
+![The animated map and speed histogram show that speeds increase when the generalization tolerance value is increased.]({{ site.url }}/images/movingpandas/mp_fig4.gif)
+
+## Test Your Movement Data Anylsis Skills Today!
+
+You can [try MovingPandas in a MyBinder notebook - no installation required](https://mybinder.org/v2/gh/movingpandas/movingpandas-examples/main?filepath=1-tutorials/1-getting-started.ipynb)
+
+## What's next?
+
+MovingPandas is under active development and there are some exciting features coming up.
+If you’d like to contribute to this project, you’re welcome to head on over to the [Github repo](https://github.com/anitagraser/movingpandas)!
diff --git a/content/blog/2022-09-10-executive-director-pyopensci-leah-wasser-updates.md b/content/blog/2022-09-10-executive-director-pyopensci-leah-wasser-updates.md
new file mode 100644
index 00000000..0141d14a
--- /dev/null
+++ b/content/blog/2022-09-10-executive-director-pyopensci-leah-wasser-updates.md
@@ -0,0 +1,122 @@
+---
+title: 'Big Changes for pyOpenSci: an update from the new Executive Director, Leah
+  Wasser'
+date: '2022-09-10'
+type: blog
+excerpt: pyOpenSci has recently transitioned to a fiscal sponsor and has a new executive
+  director - Leah Wasser. Learn more about our goals over the next few years and how
+  to get involved with the community.
+author: Leah Wasser
+blog_topic: updates
+comments: true
+url: "/blog/new-executive-director-leah-wasser.html"
+---
+
+## pyOpenSci is now an independent community organization
+
+I am thrilled to announce that pyOpenSci is now a fiscally sponsored project of
+[Community Initiatives](https://communityin.org/our-projects/support-a-project/)! This means that pyOpenSci now serves the community of
+scientific Python users and open source software maintainers. pyOpenSci is not
+affiliated with any specific organization. I (Leah) will now be devoting ALL of my
+(work :grin: ) time to the pyOpenSci project full time as the official Executive Director.
+
+## pyOpenSci’s current funding and structure
+
+I am grateful for two years of funding from the Sloan Foundation to
+support this effort. Once I acquire additional funding, I
+will be able to hire more staff to grow the organization. I am working with a
+board of two right now: Tracy Teal (chair) and [Karen Cranston](https://karencranston.ca/). They both bring
+tremendous experience building and supporting The Carpentries, among other
+efforts; Tracy and Karen will guide me in propelling pyOpenSci forward. I also am
+working with two incredible editors that have been crucial in supporting peer
+review: [David Nicholson](https://nicholdav.info/) and [Ivan Ogasawara](https://xmnlab.github.io/).
+In the upcoming months we will recruit more editors to support our open source software review process.
+Finally, I am also continuing to coordinate with and learn from the
+well-established and successful [rOpenSci](https://www.ropensci.org).
+rOpenSci has a strong precedent for open, community-driven peer review. Our
+community has a lot to learn from rOpenSci. I am grateful for their
+continued support.
+
+## pyOpenSci is not just peer review of open source software
+Peer review is critical to the pyOpenSci mission. But I have pyOpenSci  bigger
+and broader aspirations for pyOpenSci, too. There are several organizational
+goals supported by the Sloan Foundation grant that we will be working on over
+the next few years:
+* Create and grow a diverse and supportive community around a dynamic and
+open peer review process and Python open science skills. Diversity is important and we plan to bake diversity focused programs into all of pyOpenSci activities from the beginning.
+* Streamline and improve the quality of smaller Python Scientific Open Source software tools that support scientific workflows: think api wrappers, spatial data tools and domain specific tools rather than Numpy and Pandas.
+  * We do this through peer review which not only assess code quality, testing infrastructure and CI setup. Our peer review also evaluates tool usability, documentation clarity and ensures alignment with community accepted standards for Python packaging.
+  * One way our peer review process fosters usability of the tools is by ensuring documentation includes vignettes that showcase tool functionality and provide easy quickstarts for users.
+  * Once tools are accepted into our ecosystem, we will track tool maintenance and find new maintainers, or support sunsetting as it makes sense to ensure users aren't left hanging.
+  * Through peer review we will also address redundancy in tool functionality across the scientific Python ecosystem.
+* Create a model to support peer review within domain specific subcommunities. We will begin our work here with the Pangeo community. Here, we will support a peer review process with community-specific standards applied on top of ours to ensure tool consistency.
+* Provide training and mentorship in skills needed to contribute to open source. These skills are not just for open source. They are also fundamental to good open science practices and will support career trajectories in open science too.
+* Grow support for maintainers. A critical component of this effort will be a communication campaign around the importance of open source to science.
+
+### We will also continue to curate our partnership with the Journal of Open Source Software (JOSS).
+Package maintainers can still submit a package to us if they wish to publish with
+[the Journal of Open Source Software (JOSS)](https://joss.theoj.org/). Our partnership supports a "fast track" review in JOSS if its functionality
+fits their scope and requirements. Once a package is accepted by pyOpenSci, if
+the package fits into the JOSS scope our review will be accepted by JOSS. A package
+author then only needs to write a paper for JOSS, and they will be "dual"
+published with us and JOSS. This, friends, is a win-win!
+
+## Who does pyOpenSci serve?
+pyOpenSci supports software tools for open science and domain specific
+scientific projects. These tools and packages can act as glue that holds a
+research community together, but they haven't always received as much support
+as the foundational frameworks that are widely used (e.g. Pandas, numpy, scipy).
+We also support scientists using these tools and will empower folks like you
+with the skills needed to both contribute to Open Source and improve your open
+science workflows! In the long term these skills will be invaluable in your
+data intensive career trajectory!
+
+## pyOpenSci is about collaboration - not reinventing the wheel
+Collaborations with existing efforts are critical. I welcome any feedback from
+you regarding groups that we should be engaging with! I will also need help
+finding reviewers and editors, mentors to support training efforts and voices to
+spread the word about the project.
+
+## And… what's the timeline?
+Unless I figure out how to create numerous robot clones of myself, please know
+that all of the above won’t happen immediately. I am currently the sole
+employee of the organization and this is my second week. But never fear - we
+will accomplish a lot in the next two years and look forward to and will greatly
+value support from some of you along the way!
+
+## Stay in touch!
+Once I have a road map for activities developed, I will communicate this here on our
+[website](https://www.pyopensci.org/).
+
+## What can you do now?
+There are a few ways to get involved with us now.
+
+1. [You can sign up to be a reviewer by filling out our reviewer form](https://forms.gle/B6zAukLCvJot5nws6). If you do this, we will reach out to you if a package is submitted that suits your background and interests!
+  * We will also be growing our editorial board in the upcoming months. Once you have reviewed for us you are eligible to be considered as an editor. We will be posting more about this process in the upcoming months.
+1. Our open peer review process is running! If you have a package that you are working on, [you can submit it to our peer review process](https://github.com/pyOpenSci/software-review/issues).
+  * You can learn more about our review process here in our [community guide (which will be updated in the upcoming months so that it is more clear)](https://www.pyopensci.org/software-peer-review/about/package-scope.html).
+  * If you have a package that you wish to submit but need some guidance, you can also submit a presubmission inquiry or a request for help here.
+2. You can [follow us on twitter](https://www.twitter.com/pyopensci) to keep tabs on our progress.
+
+If you want to stay in touch with me, feel free to follow me on
+([twitter: @leahawasser](https://www.twitter.com/leahawasser)). Or connect with
+me on [GitHub](https://www.github.com/lwasser).
+
+## pyOpenSci was built with support from numerous community members
+I would be remiss if I didn't take a moment to thank the huge suite of community
+members who participated in early meetings and discussions surrounding pyOpenSci.
+Please note that this list is not comprehensive and likely misses folks who
+attended discussions held at the SciPy Conference a few years prior to my involvement and those
+whose names I am missing on meeting notes. Feel free to reach out and ask for
+corrections as needed!  Max Joseph, Jenny Palomino, Kylen Solvik, Chris Holdgraf,
+Paige Bailey, Luiz Irber,
+Arfon Smith, Leonardo Uieda, Filipe Fernandes, Carson Farmer, Neil Chue Hong,
+Joe Hamman, Ryan Abernathy, Lindsey Heagy, Mike Trizna, Noam Ross, Karthik Ram,
+Martin Skarzynski, Levi Wolf, Daniel Chen, Ivan Ogsawara, David Nicholson, Tania Allard,
+Kirstie Whitaker, Sander van Rijn, Philip Meier, Moritz Lurig ... and so many
+more!
+
+I am so excited to be leading this effort and look forward to keeping in touch
+with everyone and supporting the community as pyOpenSci grows.
+
+More to come... soon!
diff --git a/content/blog/2022-09-27-call-for-python-software-review-editors.md b/content/blog/2022-09-27-call-for-python-software-review-editors.md
new file mode 100644
index 00000000..4a353ccd
--- /dev/null
+++ b/content/blog/2022-09-27-call-for-python-software-review-editors.md
@@ -0,0 +1,89 @@
+---
+title: pyOpenSci Editorial Process - New Editor in Chief and a Call For Editors
+date: '2022-09-27'
+type: blog
+excerpt: pyOpenSci is developing its open peer review process for Python scientific
+  software. Learn about our structure and if you are interested, apply to be on our
+  editorial board.
+author: Leah Wasser
+blog_topic: software
+comments: true
+url: "/blog/python-software-review-process-editor-in-chief.html"
+---
+
+## An update on pyOpenSci's review process
+
+Hey there! I just wanted to update everyone about where pyOpenSci is with
+its peer review process. We are currently hard at work updating [our peer review guides](https://www.pyopensci.org/software-peer-review/) to
+streamline the peer review process. For the next 2 months (October & November 2022)
+we will prioritize setting up an editorial board to support new reviews as they
+come in.
+
+With that below you will find a few updates.
+
+## A Warm welcome to our first Editor in Chief, David Nicholson!
+
+[David Nicholson](https://github.com/NickleDave), who has been working with pyOpenSci for the past few years as
+an editor will take on the Editor in Chief role! [You can learn more about that
+role here](https://www.pyopensci.org/software-peer-review/how-to/editor-in-chief-guide.html) in our peer review guide. This position will rotate once we have our editorial board setup.
+
+As Editor in Chief, David will:
+
+* Be the first person to reach out to anyone submitting a new review or a pre-submission.
+* Perform initial software checks to ensure your package is ready for
+* Facilitate kicking off the peer review process by finding an editor for your package
+
+David has a background in behavioral / neuro / cognitive science and is a machine learning guru.
+Of course, he's a Pythonista through and through. We are lucky to have David as a
+part of our pyOpenSci team.
+
+*Stay tuned for a blog post from David introducing himself.*
+
+## We are creating an editorial board!
+
+To support our open peer review, we want to bring on a few people (like yourself?!)
+to serve as guest editors / editors. Here's how this works:
+
+If you are new to our organization, we start you as a guest editor. What this
+means is that you will review one package and we will support you in that
+process to ensure you learn the ropes. Then if you are happy and work well
+with our editorial team we will bring you on officially as an editor.
+
+Editors at pyOpenSci make a minimum of a 1-year commitment with a possibility of
+longer given mutual consent. You will be responsible for handling 3-4 package
+reviews during that year. We may also bring on guest editors in other
+instances, e.g., because of their familiarity with a specific domain.
+
+You can read more about the [roles and responsibilities of an editor here](https://www.pyopensci.org/software-peer-review/how-to/editors-guide.html).
+
+We currently have a package in the queue that is spatial / remote sensing related
+that we'd love to have an editor onboard to review. But we are in need of editors
+from other domain backgrounds too.
+{: .notice }
+
+### What background do I need to be an editor for pyOpenSci?
+
+We welcome applications from potential editors with significant experience in
+one or more of the following areas:
+* open source software,
+* open science
+* software engineering
+* peer-review
+
+Members of the pyOpenSci editorial team have diverse backgrounds. We welcome
+editors from academia, government, and industry. We especially welcome
+applications from prospective editors who will contribute to the diversity
+(ethnic, gender, disciplinary, and geographical) of our board. We also value
+having a range of junior and senior editors.
+
+
+### How do I apply?
+
+To sign up to be considered as an editor for pyOpenSci, please fill out the
+form below:
+
+[Click here to apply to be an editor <i class="fa fa-4 fa-arrow-circle-right" aria-hidden="true"></i>](https://forms.gle/YH4kTeDFoYjDtefh7){: .btn .btn--info .btn--large}
+
+## Questions?
+If you have any questions, please reach out to me at leah at pyopensci.org or on
+twitter at [@LeahAWasser](https://twitter.com/LeahAWasser).
diff --git a/content/blog/2022-10-24-why-should-python-open-source-matter-science.md b/content/blog/2022-10-24-why-should-python-open-source-matter-science.md
new file mode 100644
index 00000000..3be778e6
--- /dev/null
+++ b/content/blog/2022-10-24-why-should-python-open-source-matter-science.md
@@ -0,0 +1,243 @@
+---
+title: Why should Python open source package health matter to scientists? (and to
+  you!)
+date: '2022-10-24'
+type: blog
+excerpt: Free and open source software tools are the foundation for thousands if not
+  millions of scientific workflows. Yet, it is rare that users fully understand it's
+  importance in moving science forward. Here, I discuss the value of free and open
+  source software for science; why you as a scientist should care; and what pyOpenSci
+  is doing to try to support Python scientific tools for science.
+author: Leah Wasser
+blog_topic: software
+toc: false
+comments: true
+url: "/blog/why-python-open-source-software-matters-for-scientists.html"
+lastmod: '2024-08-29'
+---
+
+<div class="notice" markdown="1">
+## Part 1/3: Blog series on package health
+
+This blog post is part 1 of a 3 part series on open source package health.
+The series was inspired by a conversation
+held on twitter. This blog post is not a comprehensive perspective on what pyOpenSci
+plans to track as an organization. Rather it's a summary of thoughts collect during
+the conversation on twitter that we can use to inform our final metrics.
+* [In blog 2/3 I will discuss
+why free and open source package metrics matter and which categories of metrics we at pyOpenSci are thinking about tracking.](/blog/why-python-package-health-metrics-matter.html)
+* [In blog 3/3, I'll recap a conversation held on
+twitter around package health metrics](/blog/what-makes-open-source-python-package-healthy.html).
+
+</div>
+
+## Why Python open source package health should matter to you as a scientist
+
+If you are a scientist, the health of a scientific python package may not be something that
+you care about. What might seem more important is doing your science, and processing
+your data to get to that coveted scientific inquiry and exploration stage.
+
+In actuality, package health is incredibly important to science, especially open,
+data-intensive science. It should be important to you too!
+
+Why? Let me provide a few reasons below:
+
+#### 1. Free and open source tools (FOSS) make your code simpler.
+
+Free and open source tools provide commonly needed functionality wrapped up in simple tested functions and objects that you don't need to recreate yourself.
+
+If you are creating open workflows to process your data, you are likely using free-to-download (and use) tools - software. These tools make it easier for you to access, open, process and visualize your data. These free and open tools allow
+allow you to write less (complicated) code to process your data. Code that
+someone else (a package maintainer) maintains (often in their spare time but we'll
+get to that in another blog post!).
+
+#### 2. Open source software provides centralized maintenance of commonly used workflows
+
+Imagine 1,000 scientists accessing climate data. They all need to download the
+data and plot it. However they made download different types of climate data,
+different models, different variables. The base code that all 1,000 scientists
+write to download and open the data is the same. Similarly the base code for
+plotting is also the same.
+
+Isn't it better that one person writes great code and
+updates it as things like the download API change? Or they update plotting
+functionality?
+
+* This central maintenance avoids you and many other people needing to write code that
+does the same thing. It makes it easier for you to process your climate data and get
+to the science. Your code is simpler.
+
+* This centralization of tools that perform tasks that many
+people need to do avoids the problem of 1,000 people trying to create the same workflow and creating different and potentially problematic code.
+
+* This avoids everyone reinventing the scientific wheel.
+
+#### 3. Free and open source software reduces the barrier of needing a paid license to build upon your work.
+
+Free and open source software removes the barrier a paid license to run your code. This makes your work more accessible.
+
+There is a lot more to say about the value of open source here but i'll leave
+that to another blog post.
+
+{{< figure src="images/foss-free-open-source-software/why-scientists-should-care-open-source.png" alt="Image with a blue computer keyboard background with the text: why scientists should care about open source software on top." caption="If you are a scientist using open science approaches, then your workflow likely depends upon open source tools. These tools are critical to our work and yet are often not supported or consider as integral components of open science." >}}
+
+## Creating and maintaining open source software is hard work
+
+Creating these open source tools to work with data is not a trivial task. Often
+the people (who may be developers or scientists) who develop the tools:
+
+* Aren't paid to do the work
+* Burn out from all of the effort associated with supporting the tools
+* Aren't acknowledged for their effort
+* Have to deal with users who are frustrated by bugs, but aren't able to communicate that frustration kindly or effectively to help the maintainer get it fixed while also acknowledging their effort (which again is often volunteer)
+
+Maintainers also get new jobs, and need to step away from maintaining that tool.
+
+All of the above causes a challenge where once-maintained tools are now left
+unmaintained and vulnerable to new bugs as other packages that tool depends on
+are updated, or as the Python language itself is updated.
+
+### Package usability is also important but not always considered by maintainers
+
+Not all developers focus on usability when designing a new tool. Some do.
+Maintainers often start,
+as expected, with trying to get a job done. Documenting a package well enough
+so that a beginner can get started with using it, is not always an immediate goal.
+
+Yet usability is critical to developing a user base. To making a tool accessible
+to more people which could in turn help grow community around it that
+supports that tool.
+
+This can be frustrating for scientists who are trying to find the right tool
+to use to support their analysis. And as such another area that we definitely
+want to consider when building pyOpenSci.
+
+
+## Maintainers do a lot of hard work and rarely get credit for it
+
+Before I say anything else here:
+
+> Please - cite software in your work if you use it! And also if you need to report a bug, please do so in a kind and thoughtful way!
+
+Maintainers work hard on their packages. One package may be the foundation for
+data processing and analysis across hundreds to thousands (or more) scientific
+papers. But unlike scientific papers, work on the package continues long after a
+paper is published. A package is a living thing that needs continual work and love.
+
+So, what happens to that package that you are using in your workflow,
+when the developer gets a new job or finds they no longer have the time to
+maintain it? What happens when you need to update your workflow to support a paper review OR when you want to
+build upon it for another analysis if that tool no longer
+is maintained?
+
+{{< figure src="images/foss-free-open-source-software/orphan-python-open-source-packages.png" alt="Image showing girl crying with text orphan python packages are breaking my open workflows." caption="Your workflow likely depends upon tools that are being developed by volunteers. Supporting these tools is critical to supporting open science. And open science is critical to accelerating scientific discovery Source: Meme created by yours truly. :)" >}}
+
+This, my friend, is why you should care about, and support, open source software!
+
+## pyOpenSci is designed to create diverse community for and to support the open source Python tools that you as a scientist are using in your workflows.
+
+The issues discussed above around maintenance, usability and quality of software,
+are the types of issues that pyOpenSci will address.
+
+{{< figure src="images/foss-free-open-source-software/xkcd-open-source-dependency.png" alt="Image showing xkcd comic with a robotic type of image representing a scientific workflow and pointing to the small open source package maintained by one person that is a major dependency of the workflow." caption="Critical scientific workflows and projects often have dependencies that are maintained by volunteers. Source: XKCD" >}}
+
+But we (pyOpenSci) need to track package use, and maintenance, collect data and
+quantify outcomes to determine if we are making the impact that we want to. To
+determine if we are truly helping you, as a scientist in selecting the tool that
+will help you in your workflow and also be maintained over time and documented
+enough that you can get started using it quickly.
+
+We also want to ensure that we are supporting maintainers as well. To help them
+with the hard job of showing up each day to maintain a package that maybe hundreds
+to thousands of scientists are using.
+
+### pyOpenSci needs to collect data around metrics to track all of these issues
+
+pyOpenSci needs to do more than just open peer review of scientific Python
+packages. We need to collect data to better understand the issues and how we
+impact those issues over time.
+
+A few package-related goals of pyOpenSci include:
+
+* Ensure that package quality is better after the review than before
+* Inspire maintainers to develop more robust package infrastructure including testing
+* Improve the usability of packages through documentation and vignettes (short tutorials showing users how to get started with the package)
+* Ensure that packages are maintained over time; If they aren't maintained, ensure that they are archived or sunsetted in a way that users know they are no longer maintained. (no more dark orphan repositories!)
+
+
+To make sure we reach our goals, we have to collect metrics on packages
+submitted to our open peer review process to track quality and health over time.
+And hopefully, through our review process and support of
+maintainers, we will help to improve the overall quality of packages being created
+to support scientific workflows.
+
+> We want to help the community.
+
+
+## How pyOpenSci hopes to improve the usability and quality of smaller open source software packages that support science
+
+These, my friend are lofty goals. But our mission is to help
+scientists build better software. And to ensure that the community understands the
+maintenance level of that software before they adopt using it.
+
+We also want scientists to understand how hard maintainers work to create the
+tools that they use. And to cite that work if they use the tools in the same
+way they might cite a peer reviewed article. But that is another blog to be written.
+
+So how do we track open source tool health (for science)?
+
+### Peer review is actually the second step in our process.
+
+We won't begin to review a package [without bare minimum checks](https://www.pyopensci.org/software-peer-review/how-to/author-guide.html#does-your-package-meet-packaging-requirements).
+We hope that these bare minimal checks help maintainers as they try to decide
+what is good enough infrastructure for their package.
+
+We hope that these checks will also help new maintainers that are creating
+new packages even if they never submit their package to us for peer review.
+
+## Goals for package metrics
+
+These metrics will help us quantify several of our goals:
+
+We hope that:
+
+* Peer review improves Python package structure and usability.
+* Peer review in some way supports maintenance and/or responsible archiving when a package comes to life-end.
+* Over time, the package is improved and maintained with possible contributions for those other than the maintainer.
+
+We need metrics to understand things like
+
+* Community adoption of the package (are scientists using it?)
+* Maintenance level of the package (are maintainers still working on it and fixing bugs?)
+* Infrastructure (are tests setup to help identify if contributions break things? )
+* Usability (is the package documented in a way that helps users quickly get started)
+
+### A discussion about package health on twitter
+
+A few weeks ago, I posted on twitter to see what the community
+thought about "*what constitutes package health*".
+
+<blockquote class="twitter-tweet" data-partner="tweetdeck"><p lang="en" dir="ltr">controversial topic: How do we measure the &quot;health&quot; of a <a href="https://twitter.com/hashtag/science?src=hash&amp;ref_src=twsrc%5Etfw">#science</a> <a href="https://twitter.com/hashtag/python?src=hash&amp;ref_src=twsrc%5Etfw">#python</a> package? GitHub stars? downloads, date of latest commit? # of commits a month / quarter? Spread of commits? Thoughts? <a href="https://twitter.com/hashtag/opensource?src=hash&amp;ref_src=twsrc%5Etfw">#opensource</a> <a href="https://twitter.com/hashtag/OpenScience?src=hash&amp;ref_src=twsrc%5Etfw">#OpenScience</a> <a href="https://twitter.com/pyOpenSci?ref_src=twsrc%5Etfw">@pyOpenSci</a></p>&mdash; Leah Wasser 🦉 (@LeahAWasser) <a href="https://twitter.com/LeahAWasser/status/1577730887818498049?ref_src=twsrc%5Etfw">October 5, 2022</a></blockquote>
+<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+The twitter convo made me realize that there are
+many different perspectives that we can consider when addressing this question.
+
+More specifically, pyOpenSci is interested in the health of packages that
+support science. So we may need to build upon already existing
+efforts that determine metrics and customize them to our needs.
+
+## Continue reading the blog series on package health
+
+This blog post is part 1 of a 3-part series.
+
+[<i class="fas fa-hand-point-right"></i> Click here to proceed to the part 2/3, where I discuss why free and open source package metrics matter.](/blog/what-makes-open-source-python-package-healthy.html){: .btn .btn--info .btn--large}
+
+In the [final post of this three part blog series](/blog/what-makes-open-source-python-package-healthy.html), I'll recap a conversation held on
+twitter around package health metrics. This conversation will be used to define the
+types of metrics that we will collect as an organization.
+
+## Feedback? Leave it below
+
+If you have any thoughts on pyOpenSci metrics and goals or questions, please
+leave them in the comments below!
diff --git a/content/blog/2022-11-07-why-python-package-health-metrics-matter.md b/content/blog/2022-11-07-why-python-package-health-metrics-matter.md
new file mode 100644
index 00000000..538b327a
--- /dev/null
+++ b/content/blog/2022-11-07-why-python-package-health-metrics-matter.md
@@ -0,0 +1,125 @@
+---
+title: Why Python package health metrics are a priority for pyOpenSci and other open
+  source communities
+date: '2022-11-07'
+type: blog
+excerpt: Collecting baseline data that aligns with the goals and outcomes of your
+  project, program or organization is critical to do at the beginning. Here I briefly
+  explain why Python package health metrics are so important to the long-term success
+  of pyOpenSci.
+author: Leah Wasser
+blog_topic: software
+toc: false
+comments: true
+url: "/blog/why-python-package-health-metrics-matter.html"
+lastmod: '2024-08-29'
+---
+
+<div class="notice" markdown="1">
+## Part 2/3: Blog series on package health
+This blog is the second in a 3 part series. [In the previous blog post,](/blog/why-python-open-source-software-matters-for-scientists.html)
+I discussed why the health of (Python) open source
+packages should matter to you as a scientist (and as a person who values and
+uses free and open source tools in your workflow). In this post, I'll talk
+more about why collecting metrics are critical to both program development success
+and to the success of open source tools. I'll wrap up this series
+[with a discussion on what types of package metrics pyOpenSci should be collecting
+around the free and open source Python packages that you use.](/blog/what-makes-open-source-python-package-healthy.html).
+
+NOTE: all of this is in the context of a conversation on Twitter. It is not a
+comprehensive perspective on the final metrics that pyOpenSci plans to collect.
+</div>
+
+## Metrics are critical to the development of any program
+
+I've created a few open science focused programs now from the ground up. One at
+NEON and another at CU Boulder. When building a new program, one of the first
+things that I do (after defining the mission and goals) is to define the metrics
+that constitute success.
+
+These metrics are critical to define early because:
+
+* They drive everything that you do.
+* And often they take time to develop
+* It's critical to have solid baseline data. This baseline data needs to be collected from the start of your program as often, it can't be collected later, retrospectively.
+
+If you have evaluation or education in your professional background like I do,
+you may even
+[create a logic model](https://thecompassforsbc.org/how-to-guide/how-develop-logic-model-0) to map activities to outcomes and goals. This logic
+model helps you define how
+to collect the data that you need to track outcome success.
+
+## Baseline data are critical to collect at the start of building a program or organization
+
+As I am building the pyOpenSci program, I find myself thinking about what metrics
+around Python scientific open source software we want to track to better understand:
+
+1. The outcomes of our activities
+2. The overall health of packages in our growing pyOpenSci ecosystem (specific to our organization)
+3. How/if we contributed to improving the health of packages in our ecosystem
+4. How we are impacting the broader scientific python, open source community
+
+### Baseline metrics collected from the start will help your future self when running or working in an organization
+
+As mentioned above, collecting metrics from the start
+of your efforts allows you to get off the ground running with data that you can use to compare to future data. Thus while it may not be the work that you want to do, it will
+help your future self.
+
+For pyOpenSci, collecting metrics allows us in the future
+to evaluate our programs and adaptively change things to
+make sure we are getting the outcomes that we want.
+
+Outcomes such as
+* Scientists being better able to find packages that are maintained to support their workflows
+* Improved documentation in packages as a result of our reviews
+
+### But what metrics should we collect about scientific Python packages?
+
+[In a previous post,](/blog/why-python-open-source-software-matters-for-scientists.html) I spoke
+generally about why open source should matter to you as a scientist and as a
+developer or package maintainer.
+
+To better understand what data we should be collecting to track our packages'
+health over time, I went to Twitter to see what my colleagues around the world
+had to say. That conversation resulted in some really interesting insights.
+
+[In my next blog post, I will summarize the discussion that happened on twitter.](/blog/what-makes-open-source-python-package-healthy.html)
+{: .notice }
+
+Most importantly, it allowed me to begin to break down and group metrics in
+terms of pyOpenSci goals.
+
+### Goals for package metrics
+
+We hope that:
+
+* Peer review improves Python package structure and usability.
+* Peer review in some way supports maintenance and/or responsible archiving when a package comes to life-end.
+* Over time, the package is improved and maintained.
+* Over time we hope to facilitate outside contributions to these packages.
+
+We need metrics to understand things like
+
+* Community adoption of the package (are scientists using it?)
+* Maintenance level of the package (are maintainers still working on it and fixing bugs?)
+* Infrastructure (are tests set up to help identify if contributions break things? )
+* Usability (is the package documented in a way that helps users quickly get started)
+
+## Four metric categories that pyOpenSci cares about
+
+Based on all of the feedback on twitter, which is summarized in the next post, and what I *think* might be a start at what pyOpenSci
+needs to consider, I organized the conversation into four broad categories:
+
+1. Infrastructure
+2. Maintenance
+3. Community adoption (and usability??)
+4. Diversity, Equity, Inclusion, and Accessibility (DEIA) - discussed less on twitter but integral to pyOpenSci goals.
+
+These four categories, at not by any means mutually exclusive. They are merely a way
+to begin to organize an engaging and diverse conversation. All of the categories are priorities of pyOpenSci.
+
+[<i class="fas fa-hand-point-right"></i> Click here to read more about how these metric categories  evolved within the conversation on Twitter!](/blog/what-makes-open-source-python-package-healthy.html){: .btn .btn--info .btn--large}
+
+## Thoughts?
+
+Leave any feedback that you have in the comments section below.
diff --git a/content/blog/2022-11-21-what-makes-a-python-package-healthy.md b/content/blog/2022-11-21-what-makes-a-python-package-healthy.md
new file mode 100644
index 00000000..9bad0f95
--- /dev/null
+++ b/content/blog/2022-11-21-what-makes-a-python-package-healthy.md
@@ -0,0 +1,495 @@
+---
+title: What Makes a Python Open Source Package Healthy? A Conversation on Twitter.
+date: '2022-11-21'
+type: blog
+excerpt: How should pyOpenSci measure Python open source package health and level
+  of maintenance and usability? Here I summarize a conversation held on twitter around
+  this very topic. Feedback is welcome!
+author: Leah Wasser
+blog_topic: software
+toc: false
+comments: true
+url: "/blog/what-makes-open-source-python-package-healthy.html"
+lastmod: '2024-08-29'
+---
+
+<div class="notice" markdown="1">
+## Part 3/3: Blog series on package health
+
+This blog post is part 3 of a 3 part series on open source package health.
+The series was inspired by a conversation
+held on twitter. This blog post is not a comprehensive perspective on what pyOpenSci
+plans to track as an organization. Rather it's a summary of thoughts collect during
+the conversation on twitter that we can use to inform our final metrics.
+
+- [In blog 1/3 I discussed why Python open source software matters to scientists (and package maintainers too)](/blog/why-python-open-source-software-matters-for-scientists.html)
+- [In blog 2/3 I discussed
+  why free and open source package metrics matter and which categories of metrics we at pyOpenSci are thinking about tracking.](/blog/why-python-package-health-metrics-matter.html)
+
+In this post, I'll summarize a conversation that was held on twitter that gaged
+what the community thought about metrics to track the health of scientific
+Python open source packages.
+
+</div>
+
+## Packages and open source software, a few terms to clarify
+
+- When I say Python package or Python open source software, I'm referring to a
+  tool that anyone can install to use in their Python environment.
+- When I say open source or free and open source software I'm referring to Python tools that are free to download and and their code is openly available for anyone to see (open source).
+
+## What is package health anyway?
+
+There are many different ways to think about and evaluate open source
+Python package health.
+
+Below is what I posted on Twitter to spur a conversation about what makes a
+package healthy. And more specifically what metrics should we (pyOpenSci) collect
+to evaluate health.
+
+**My goal:** to see what the community thought about "_what constitutes package health_".
+
+<blockquote class="twitter-tweet" data-partner="tweetdeck"><p lang="en" dir="ltr">controversial topic: How do we measure the &quot;health&quot; of a <a href="https://twitter.com/hashtag/science?src=hash&amp;ref_src=twsrc%5Etfw">#science</a> <a href="https://twitter.com/hashtag/python?src=hash&amp;ref_src=twsrc%5Etfw">#python</a> package? GitHub stars? downloads, date of latest commit? # of commits a month / quarter? Spread of commits? Thoughts? <a href="https://twitter.com/hashtag/opensource?src=hash&amp;ref_src=twsrc%5Etfw">#opensource</a> <a href="https://twitter.com/hashtag/OpenScience?src=hash&amp;ref_src=twsrc%5Etfw">#OpenScience</a> <a href="https://twitter.com/pyOpenSci?ref_src=twsrc%5Etfw">@pyOpenSci</a></p>&mdash; Leah Wasser 🦉 (@LeahAWasser) <a href="https://twitter.com/LeahAWasser/status/1577730887818498049?ref_src=twsrc%5Etfw">October 5, 2022</a></blockquote>
+<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+The twitter convo made me realize that there are
+many different perspectives that we can consider when addressing this question.
+
+More specifically, pyOpenSci is interested in the health of packages that
+support science. So we may need to build upon existing
+efforts that have determined what metrics to use to quantify package health and customize them to our needs.
+
+<div class="notice" markdown="1">
+### A note about our pyOpenSci packages
+
+pyOpenSci does not focus on foundational scientific Python packages like Xarray
+Dask, or Pandas. Those packages are stable and already have a large user base
+and maintenance team. Rather we focus on packages that are higher up in the
+ecosystem. These packages tend to have smaller user bases, and smaller maintainer
+teams (or often are maintained by one volunteer person).
+
+{{< figure src="images/python-packaging/python-ecosystem-jake-vanderploss-pycon-2017.png" alt="Image used by Jake Vanderploss in the 2017 pycon conference that shows the ecosystem of scientific python packages starting with foundational packages and moving out to the wealth of smaller, domain specific packages." caption="Image used by Jake Vanderploss in the 2017 pycon conference that shows the ecosystem of scientific python packages starting with foundational packages and moving out to the wealth of smaller, domain specific packages. pyOpenSci focuses on the packages that are higher up in the ecosystem that often could benefit from more support." >}}
+
+Our package maintainers:
+
+- Often don't have the resources to build community
+- Often are keen to build their user base and to contribute
+to the broader scientific python ecosystem.
+</div>
+
+## Existing efforts on health metrics: Chaoss project and the Software Sustainability Institute (neil)
+
+I'd be remiss if I didn't mention that there are several projects out there that
+are deeply evaluating open source package health metrics.
+
+Several people including: Nic Weber, Karthik Ram and Matthew Turk mentioned the
+value and thought put into the [Chaoss project](https://chaoss.community/).
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Is this something that the <a href="https://twitter.com/CHAOSSproj?ref_src=twsrc%5Etfw">@CHAOSSproj</a> work could be specialized and applied to scientific software?</p>&mdash; Matthew Turk (@powersoffour) <a href="https://twitter.com/powersoffour/status/1577755607540580354?ref_src=twsrc%5Etfw">October 5, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">CHAOSS (<a href="https://t.co/moiMUeDuS3">https://t.co/moiMUeDuS3</a>) has been thinking about this more generally, but it&#39;s interesting to think about some of the more &quot;science&quot; aspects.<br><br>I&#39;ve wondered about &quot;frequency of API changes&quot; - for use in research is it healthier to be &quot;stable&quot; or &quot;move fast/break things&quot;?</p>&mdash; Neil P Chue Hong (he/him｜they/them) (@npch) <a href="https://twitter.com/npch/status/1577952873568239618?ref_src=twsrc%5Etfw">October 6, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Not that controversial! Have you looked into the rich body of work that the <a href="https://twitter.com/CHAOSSproj?ref_src=twsrc%5Etfw">@CHAOSSproj</a> community has done? Each metric has been explored in great detail</p>&mdash; Karthik Ram (@_inundata) <a href="https://twitter.com/_inundata/status/1578061660706975744?ref_src=twsrc%5Etfw">October 6, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+The Software Sustainability Institute lead by Neil P Chue Hong has also
+thought about package health extensively and pulled together some data accordingly. Neil was also
+a critical guiding member of the earlier pyOpenSci community meetings that were
+held in 2018.
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">We also did some initial work on this in 2017 (see slide 12 of this presentation): <a href="https://t.co/1F0iMwfT5g">https://t.co/1F0iMwfT5g</a></p>&mdash; Neil P Chue Hong (he/him｜they/them) (@npch) <a href="https://twitter.com/npch/status/1577959663408218114?ref_src=twsrc%5Etfw">October 6, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+### Snyk and security (which aren't discussed in this post)
+
+One topic that I am not delving into in this post is security issues. Snyk
+is definitely a leader in this space and was mentioned at least once in
+the conversation.
+
+### Some existing metric examples
+
+Below are some of the metrics that you can easily access via Snyk's website.
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">This might be helpful. This website collects various metrics. And here is the example for numpy. <a href="https://t.co/YNsRoMgks4">https://t.co/YNsRoMgks4</a></p>&mdash; Kevin Wang (@KevinWangStats) <a href="https://twitter.com/KevinWangStats/status/1577999823911161856?ref_src=twsrc%5Etfw">October 6, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+#### [Pandera python package metrics on Snyk](https://snyk.io/advisor/python/pandera)
+
+{{< figure src="images/pyopensci-packages/snyk-pandera-python-package-metrics.png" alt="Image showing the metrics from the Snyk website for the `pandera` package in our ecosystem." caption="Here you can see what a Snyk report looks like for pandera, a package accepted into our ecosystem a few years ago. Pandera gets a very healthy report because it's heavily used among other metrics." >}}
+
+#### Now let's look at [pyGMT package statistics on Snyk](https://snyk.io/advisor/python/pygmt)
+
+{{< figure src="images/pyopensci-packages/snyk-pygmt-python-package-metrics.png" alt="Image showing the metrics from the snyk website for the pyGMT package in our ecosystem." caption="In comparison to pandera, pyGMT gets a lower, but still good, health score. I suspect this is due to lower community adoption and use. pyGMT is a much newer package. We'd argue however that pyGMT has a very healthy level of maintenance and even healthier package structure." >}}
+
+And of course the [scientific Python project has also been tracking the larger packages](https://devstats.scientific-python.org/):
+
+## What metrics should pyOpenSci track for their Python scientific open source packages?
+
+So back to the question at hand, what should pyOpenSci be tracking for [packages
+in our ecosystem](/python-packages/)?
+Hao Ye (and a few others) nailed it - health metrics are multi-dimensional.
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">I think, much like &quot;ecological stability&quot; - <a href="https://t.co/lJe2Fa0ycR">https://t.co/lJe2Fa0ycR</a> - , &quot;health&quot; here is multi-dimensional and different metrics will capture different facets, such as growth, transparency in governance, stability / backwards compatibility, etc.</p>&mdash; Hao Ye will haunt you for bad keming (@Hao_and_Y) <a href="https://twitter.com/Hao_and_Y/status/1577739685841059842?ref_src=twsrc%5Etfw">October 5, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+> I may be a bit biased here considering I have a degree in ecology BUT... I definitely support the ecological perspective always and forever :)
+
+As Justin Kiggins from Napari and CZI points out, metrics are also perspective based.
+We need to think carefully about the
+organization's goals and what we need to measure as a marker of success and as a
+flag of potential issues.
+
+See insightful thoughts below:
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">I think that relevant metrics really depend on who is evaluating &quot;health&quot; and what their needs are.</p>&mdash; Justin Kiggins (@neuromusic) <a href="https://twitter.com/neuromusic/status/1577743299531534336?ref_src=twsrc%5Etfw">October 5, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">From UXR work led by <a href="https://twitter.com/ObusLucy?ref_src=twsrc%5Etfw">@ObusLucy</a>, we found that what users of open source bioimaging plugins are looking for depends on whether they are looking at plugins for general purpose analyses or niche/emerging analyses.</p>&mdash; Justin Kiggins (@neuromusic) <a href="https://twitter.com/neuromusic/status/1577743480352169984?ref_src=twsrc%5Etfw">October 5, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">In the former case, they look for signals of usage (downloads, citations) and in the latter, signals of maintenance and support (commits, comments by dev on issues, etc).</p>&mdash; Justin Kiggins (@neuromusic) <a href="https://twitter.com/neuromusic/status/1577744011707621376?ref_src=twsrc%5Etfw">October 5, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">I suspect this is different from what a funder who is interested in sustainability or a corporation who is interested in their software supply chain would look for to define &quot;health&quot;</p>&mdash; Justin Kiggins (@neuromusic) <a href="https://twitter.com/neuromusic/status/1577744568203632640?ref_src=twsrc%5Etfw">October 5, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+Alas it is true that metrics designed for reporting that a funder requires
+for a grant may differ metrics designed for internal evaluation that
+informs program development. pyOpenSci has a lot to unpack there over the
+upcoming months!
+
+### Three open source software healthy metric "buckets"
+
+Based on all of the Twitter feedback (below), and what I _think_ might be a
+start at what pyOpenSci needs, I organized the Twitter conversation into three
+buckets:
+
+1. Infrastructure
+2. Maintenance
+3. Community adoption (and usability??)
+
+These three buckets are all priorities of pyOpenSci.
+
+<i class="far fa-sticky-note"></i> DEIA is another critical concern for pyOpenSci but I won't discuss that in this blog post.
+{: .notice }
+
+## Infrastructure in a Python open source GitHub repository as a measure of package health
+
+So here I start with Python package infrastructure found in a GitHub repository
+as a preliminary measure of package health.
+When think of infrastructure I think about the files and "things" available in a
+repository that support its use. I know that no bucket is perfectly isolated
+from the others but i'm taking a stab at this here.
+
+<i class="fas fa-info-circle"></i> The code for many open source software packages can be found on [GitHub](https://www.github.com). GitHub is a free-to-use website that runs `git` which is a version control system. Version control allows developers to track historical changes to code and files. As a platform built on top of git, GitHub allows developers to communicate openly, review new code changes and update content in a structured way.
+{: .notice }
+
+### What does GitHub (and Ivan) think about health checks for Python open source software?
+
+Ivan Ogasawara is a long time advisor, editor and member of the pyOpenSci community. He's also a generally a great human being who is growing open science efforts such as
+[Open Science Labs](https://opensciencelabs.org/); which is a global community devoted to education efforts and tools that support open science.
+
+Ivan was quick to point out some basic metrics offered by GitHub which follow their
+[community standards online guidebook here](https://opensource.guide/).
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Maybe not totally related, but github has a section called community standards that could be used as reference, for example: <a href="https://t.co/wmu1bDdcQR">https://t.co/wmu1bDdcQR</a></p>&mdash; XMN (@xmnlab) <a href="https://twitter.com/xmnlab/status/1578745372880429057?ref_src=twsrc%5Etfw">October 8, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+Actually it's totally related, Ivan! Let's have a look look at the [pyOpenSci contributing-guide GitHub repository](https://www.github.com/pyopensci/software-peer-review/community) to see how we are
+doing as an organization.
+
+Note that we are missing some important components:
+
+- A code of conduct
+- A contributing file that helps people understand how to contribute
+- Issue template for people opening issues
+- Pull request templates to guide people through opening pull requests
+- Repository admins accepting content reporting
+
+> Um.... we've got some real work to do, y'all on our guides and repos. We need to set a better example here don't we? We welcome help welcome if you are reading this and wanna contribute. Just sayin...
+
+### GitHub bare minimum requirements are a great start!
+
+The GitHub minimum requirements for what a software repository should contain
+are a great start towards assessing package health. In fact I've created a `TODO`
+to add this url of checks to our pre-submission and submission templates as
+these are things we want to see too; and also to update our repos accordingly.
+
+> Health check #1: are all GitHub community checks green?
+
+Looking at these checks more closely you can begin to think about different categories
+of checks that broadly look at package usability (readme, description), community engagement (code of conduct,
+templates), etc.
+
+<div class="notice" markdown="1">
+The GitHub list includes:
+
+- Description
+- README.md file ((but what's in that))
+- Code of conduct (but what's in that file?!)
+- License (OSI approved)
+- Issue templates (great for community building)
+- Pull request templates
+
+</div>
+
+#### These checks are great but don't look at content and quality
+
+But these checks don't look at what's in that README, or how the issue templates
+are designed to invite contributions that are useful to the maintainers (and that
+guide new potential contributors).
+
+In short, GitHub checks are excellent but mostly exterior infrastructure focused.
+They don't check content of those files and items.
+
+#### So what do content checks look like?
+
+As Chris mentions below, things like having a clearly stated goal and intention,
+likely articulated in the **README** file is a sign of a healthy project. This goal was
+ideally developed prior to development beginning. Further, if well-written,
+it helps keep the scope of the project management.
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">To this point - i think that an example of a healthy project behavior is that it explicitly states its technical and organizational goals and intentions</p>&mdash; Chris Holdgraf (@choldgraf) <a href="https://twitter.com/choldgraf/status/1577971815305060354?ref_src=twsrc%5Etfw">October 6, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+### Test suites and Python versions
+
+Another topic that came up in the discussion was testing and test suites. Evan,
+who has been helping me improve our website navigation suggested looking at test suites
+and what version of Python those suites are testing against.
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">My initial reaction is that it should have to do with the presence and quality of automated tests, and the versions of Python those tests are run against.<br><br>I can imagine a small, mature package needs little more than minor updates to run on newer versions of Python.</p>&mdash; Evan (he/him) (@darth_mall) <a href="https://twitter.com/darth_mall/status/1577736476053250048?ref_src=twsrc%5Etfw">October 5, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+Test suites are critical not only to ensure the package functionality works as expected
+(if tests are designed well). They also make it easier for contributors to check
+if changes they made to the code
+in a GitHub pull request don't break things unexpectedly.
+
+Tests can also be created
+in a Continuous Integration (CI) workflow to ensure code syntax is consistent
+(e.g. linting tools such as `Black`) and to test documentation builds for broken
+links and other potential errors.
+
+> <i class="fas fa-question-circle"></i> How should pyOpenSci handle Python versions supported in our review process?
+
+In fact the website that you are on [RIGHT NOW has a set of checks that run to test links](https://github.com/pyOpenSci/pyopensci.github.io/actions) throughout the site and to check for alt tags in support of accessibility (Alt tags support people using screen readers to navigate a website).
+
+{{< figure src="images/python-software-health/html-proofer-pyopensci-website-checks.png" alt="Image showing the output of htmlproofer for a website. You can see that it tells you when and where there are broken links or missing alt tags." caption="Notice in this output from htmlproofer on GitHub actions (continuous integration) that every page with a broken link or image with a missing alt tag will be flagged. Any flags will result in a broken build on GitHub - the dreaded red x." >}}
+
+### Infrastructure: Is it easily installable?
+
+How the package is installed is another critical factor to consider. While
+these days most packages do seem to be uploaded to PyPI, some still aren't. And
+there are other package managers to consider too such as `Conda`.
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Lots of thoughts on this... 😂<br>One aspect is definitely whether or not the package is published through PyPI, whether it follows standard packaging practices, has a test suite or well documented simple examples of how to use it, etc.</p>&mdash; Kenneth Hoste (@kehoste) <a href="https://twitter.com/kehoste/status/1578107988715671555?ref_src=twsrc%5Etfw">October 6, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+## Maintenance activity as a metric of health
+
+The second topic that came up frequently on Twitter was the issue of maintenance.
+
+Jed Brown had some nice overarching insight here for things they look at that are
+indicators of both maintenance and bus factor (risk factor, mentioned below as a measure
+of how many people / institutions support maintenance). More people and more institutions
+equals lower risk, fewer people and fewer institutions supporting the package equates
+to a higher maintenance risk (or risk of the package becoming a sad orphan with no
+family to take care of it.
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">CI (multi-platform, coverage, static analysis), promptness of reviews, number of distinct institutions who have committed in past 6 months, ditto who have reviewed PRs in past 6 months, promptness of reviews, quality of commit messages and PR discussion.</p>&mdash; Jed Brown (@five9a2) <a href="https://twitter.com/five9a2/status/1577746418906714112?ref_src=twsrc%5Etfw">October 5, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+How many times have you tried to figure out what Python package you should use
+to process or download data, and you found 4 different packages on PyPI all in
+varying states of maintenance?
+
+I've certainty been there. So has RenéKat it seems:
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">I look to see if issues are being resolved. If it’s not being maintained I’m not going to waste my time installing it.</p>&mdash; RenéKat (@renekat14) <a href="https://twitter.com/renekat14/status/1577745550803451918?ref_src=twsrc%5Etfw">October 5, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+It's true. For a scientist (or anyone) it's a waste of time to install something
+that won't be fixed as bugs arise. It's also not a good use of their time to have to dig into a package repository to see if it's being maintained or not.
+
+pyOpenSci does hope to help with this issue through a curated catalog of tools
+which will be developed over time.
+
+### But what constitutes maintenance?
+
+How do we measure degree of maintenance? Number of issues being addressed and closed? Average commits each month, quarter or year?
+
+This could be a relative metrics too. Some package maintainers
+may spend lots of time on issues or have too many to handle quickly as Melissa
+points out replying to a comment about evaluating maintenance by looking
+at issues being closed:
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Would that apply to large established projects such as NumPy? My guess is it wouldn&#39;t 😉</p>&mdash; Ax=13!!! (@melissawm) <a href="https://twitter.com/melissawm/status/1577776605220454403?ref_src=twsrc%5Etfw">October 5, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+But alas I think there are ways around that. We can look at commits, pull requests and such
+just to see if there's any activity happening in the repository. Or if it's gone dark
+(dark referring to no long being maintained, answer to issues, fixing bugs, etc).
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Well, one should look beyond the number of open issues. A lot of them get closed very fast, many prs are merged on a short timescale too. So if you go into a well established repo and see larger numbers, those may still be just the leftover corner cases of decades of usage.</p>&mdash; Brigitta Sipőcz (@AstroBrigi) <a href="https://twitter.com/AstroBrigi/status/1577786476523589633?ref_src=twsrc%5Etfw">October 5, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+Greg, interestingly suggested one might be able to model expected future lifetime of a package
+based upon current (and past?) GitHub activity.
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Would you accept &quot;expected future lifetime of package&quot; (where &quot;lifetime&quot; means &quot;period of active maintenance&quot;) as a measure of health? That feels like something a model could plausibly be trained to predict...</p>&mdash; Greg Wilson (@gvwilson) <a href="https://twitter.com/gvwilson/status/1577780995293601792?ref_src=twsrc%5Etfw">October 5, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+Uh oh! But are commits enough, Kurt asks? Is there such a thing as a perfect project?
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Could a project with no recent commits be healthy? What if it needed no commits?</p>&mdash; Kurt Schwehr, PhD (@kurtschwehr) <a href="https://twitter.com/kurtschwehr/status/1578022419926683650?ref_src=twsrc%5Etfw">October 6, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+Koen had a more broadly profound thought that would be ideal to consider when
+creating a new package; especially a small package that supports specific
+scientific workflows.
+
+> Does it do one thing, well? Really well?
+
+Yes, please.
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">My experience from R. None apply if packages stick to the Unix philosophy of doing one thing really well. This will lead to packages with considerable uptake but little development. Base code of {snotelr} is mostly unchanged since inception (12K users).<a href="https://t.co/3oKwmeBaA8">https://t.co/3oKwmeBaA8</a></p>&mdash; Koen Hufkens, PhD (@koen_hufkens) <a href="https://twitter.com/koen_hufkens/status/1577753313482866688?ref_src=twsrc%5Etfw">October 5, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+While this might be challenging to enforce in peer review, it is a
+compelling suggestion.
+
+### How do developers evaluate package maintenance?
+
+There is a developer perspective to consider here too. Yuvi Panda pointed out a few
+items that they look for:
+
+1. Frequency of merged commits
+2. [Bus factor](https://www.michaelbromley.co.uk/blog/but-what-about-the-bus-factor/)
+3. Release cadence (a topic brought up a few times throughout the discussion)
+
+Remember, _bus factor_ has nothing to do with buses, but there is some truth to the
+analogy of what happens when the wheels fall off.
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Without being specific to open science, I always look at: 1. how frequently are commits being merged? 2. what does bus factor look like (is it just 1 person?), 3. What is cadence of release</p>&mdash; Yuvi Panda (@yuvipanda) <a href="https://twitter.com/yuvipanda/status/1578094184040321024?ref_src=twsrc%5Etfw">October 6, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+One thought I had here was to look at commits from the maintainer relative to
+total commits to get a sense of community contribution (if any).
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">thanks Yuvi! i hadn&#39;t heard of the term bus factor before but was thinking that it would be interesting to look at how many commits do NOT belong to the maintainer in a ratio type of form. Since we have the maintainer information from our reviews we could potentially do that.</p>&mdash; Leah Wasser 🦉 (@LeahAWasser) <a href="https://twitter.com/LeahAWasser/status/1578157415526150144?ref_src=twsrc%5Etfw">October 6, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+> The CHAOSS project has an entire working group devoted to risk.
+
+Or perhaps pyOpenSci asks their maintainers what their perceived risk is?
+IE: how long do you think the package might remain maintained. They will obviously
+know better than anyone what their funding environment and support it like.
+
+Erik suggested that metrics can be dangerous and somewhat subjective at times.
+Akin to the whole - maps can lie; data can lie too . Ok it's our interpretation that is
+the risk or lie not the data but ... you follow me, yea?
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Ask developers how comfortable they would be to depend on the package for a new project. I think &quot;health&quot; is largely subjective and I don&#39;t trust metrics without context.</p>&mdash; Erik Welch (@eriknwelch) <a href="https://twitter.com/eriknwelch/status/1577775776719585280?ref_src=twsrc%5Etfw">October 5, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+Some including Pierre brought up the idea of consistent releases. Not necessarily
+frequency but just some consistency to demonstrate that the package was being
+updated.
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Yes. Regular releases is a sign of good health. But given the fact that many scientific projects are often maintained by few people I would avoid any normalization. I&#39;m usually super happy with 1 or 2 releases per year.</p>&mdash; Pierre Poulain (@pierrepo) <a href="https://twitter.com/pierrepo/status/1577758919392362496?ref_src=twsrc%5Etfw">October 5, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+Other discussions evolved around semantic versioning and release
+roadmaps.
+
+## Community adoption of an open source Python tool
+
+Community adoption of an scientific Python package was another broad category seen over and over throughout the Twitter conversation.
+
+- How many users are using the tool?
+- How many stars does the package have?
+- How often is is the package cited?
+
+### Is the package cited?
+
+While we'd love to quantify citations, the reality of this is that most people
+don't cite software. But some do, and we hope you are one of them!
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Citations, naturally! 😉</p>&mdash; Jacob Deppen (@jacob_deppen) <a href="https://twitter.com/jacob_deppen/status/1577996604883312643?ref_src=twsrc%5Etfw">October 6, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+### What about stars (and commits) as a metrics of adoption (and maintenance)?
+
+The tweeter below looks at stars and commit date as signs of community
+adoption and maintenance.
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Derivative of 🌟 with respect to ⏲️ plus date of last commit!!</p>&mdash; MLinHydro (@MLinHydro) <a href="https://twitter.com/MLinHydro/status/1577826311250509824?ref_src=twsrc%5Etfw">October 6, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+As Chris Holdgraf mentions below, a package can reach a point where the same
+type of activity can have varying impacts of
+perceived level of maintenance. Many users opening issues,
+can represent community interest and perhaps even community adoption. And massive
+volumes of unaddressed
+issues _might_ represent unresponsive maintainers.
+
+> Or perhaps the maintainers are just overwhelmed by _catastrophic success_.
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">I think a steady stream of issues implies a lot of user interest, though I can tell you from first-hand experience that it does not mean a project is healthy :-)<br><br>I think it misses one of the most stressful anti-patterns for OS projects: Catastrophic Success<br><br>h/t <a href="https://twitter.com/fperez_org?ref_src=twsrc%5Etfw">@fperez_org</a> :-D</p>&mdash; Chris Holdgraf (@choldgraf) <a href="https://twitter.com/choldgraf/status/1578304871530631168?ref_src=twsrc%5Etfw">October 7, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+Yup
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">it is the equivalent of when a small bakery gets written up in the New York Times, has a huge influx of customers, and collapses under the weight of demand. I think it&#39;s an outcome we don&#39;t think about enough ahead of time</p>&mdash; Chris Holdgraf (@choldgraf) <a href="https://twitter.com/choldgraf/status/1578305233611915264?ref_src=twsrc%5Etfw">October 7, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+> But I need at least 5 (thousand) croissants, now. ANDDDD so does my friend.
+
+Juan agrees that a steady stream of issues suggests adoption. Especially since
+opening issues on GitHub suggests that the users have some technical literacy.
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">As others have said, it’s multidimensional, but this article argues that a steady stream of issues = a community of active and engaged users — often somewhat programming-literate since it’s GH. I find that argument compelling.<a href="https://t.co/X2vY2QxRfV">https://t.co/X2vY2QxRfV</a></p>&mdash; Juan Nunez-Iglesias (@jnuneziglesias) <a href="https://twitter.com/jnuneziglesias/status/1578290475017981953?ref_src=twsrc%5Etfw">October 7, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+## Metrics quantifying community around tools
+
+I'd be remiss if i didn't at least mention that some of the discussion steered
+towards community around tools. For instance, Evan brought up community governance
+being a priority.
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Governance was another aspect I was going to suggest. The “benevolent dictator for life” model is… risky</p>&mdash; Evan (he/him) (@darth_mall) <a href="https://twitter.com/darth_mall/status/1577741937544609793?ref_src=twsrc%5Etfw">October 5, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+But the reality of our users was summarized well here by Tania. Most scientists
+developing tools are trying to simplify workflows with repeated code. Workflows
+that others may be trying to develop to do the same thing. They aren't necessarily
+focused on community, at least not yet.
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Also note - a lot of folks developing scientific software are more interested in the pragmatic side of open source (i.e availability, making the codebase public and accessible) rather than building a community around it.</p>&mdash; ✨Tania Allard 💀🇲🇽 🇬🇧 she/her (@ixek) <a href="https://twitter.com/ixek/status/1577914450505601024?ref_src=twsrc%5Etfw">October 6, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+Further, capturing metrics around community is hard as Melissa points out. Most
+of the above resources don't capture these types of items. And also, how would one
+capture the work on a community manager quantitatively?
+
+ <blockquote class="twitter-tweet"><p lang="en" dir="ltr">Depends on what is &quot;health&quot;. Sustainability? Funding? Maintainability? Culture? I think most metrics are proxies to some other thing we want to measure, but are not representative. For ex looking at github, a bunch of the work done by community managers is not captured at all.</p>&mdash; Ax=13!!! (@melissawm) <a href="https://twitter.com/melissawm/status/1577776074863288324?ref_src=twsrc%5Etfw">October 5, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+## Are some things missing here? Yes, of course.
+
+But it's a great start!
+
+- Some other items that didn't come up in the conversation included downloads.
+- Packages found as dependencies or in environments on GitHub
+
+Joel rightfully noted that my original tweet seemed less concerned with package
+quality and more concerned with community and use. I think they are right.
+We are hopeful that peer review metrics and recommended guidelines for packaging
+will get at package quality.
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">I guess that depends on whether you&#39;re concerned about the quality of the package or the popularity of the package.<br><br>Most of your proposed metrics seem to be about size and activity of the COMMUNITY using the package rather than quality or reliability of the package itself.</p>&mdash; Joel Bennett (@Jaykul) <a href="https://twitter.com/Jaykul/status/1577739823154094080?ref_src=twsrc%5Etfw">October 5, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+## Summarizing it all will be a WIP (Work In Progress)
+
+There is a lot of work to do in this area. And a lot of work that has already
+been done to learn from. It's clear to me that we should start by looking at
+what's been done and what people are already collecting in this area. And then
+customize to our needs.
+
+A few items that stand out to me that we could begin collecting now surrounding
+package maintenance and community adoption are below.
+This list will grow but it's just a start.
+
+### Package Maintenance and Community Adoption
+
+- Date of last commit
+- Date of last release
+- Annual frequency of releases
+- Number of open issues / quarter
+- Issues opened by maintainers vs non maintainers
+- Number of commits made by non maintainers / year
+
+### Package quality & infrastructure
+
+- GitHub core checks for README, Contributing guide, etc
+- Documentation & associated documentation quality (vignettes and quick start)
+- Defined scope and intent of package maintenance
+- Testing and CI setup
+
+I will share a more comprehensive list once we pull that together as an organization
+in another blog post. Stay tuned for more!
+
+## Thoughts?
+
+If you have any additional thoughts on this topic or if I missed important
+parts of the conversation please share in the comment section below.
diff --git a/content/blog/2023-03-22-demystifying-python-packaging.md b/content/blog/2023-03-22-demystifying-python-packaging.md
new file mode 100644
index 00000000..a55e048a
--- /dev/null
+++ b/content/blog/2023-03-22-demystifying-python-packaging.md
@@ -0,0 +1,168 @@
+---
+title: 'Demystifying the Python packaging ecosystem '
+date: '2023-03-22'
+type: blog
+excerpt: 'pyOpenSci has published the packaging structure and tool section of it''s
+  guide. This chapter has been reviewed by dozens of core community members to ensure
+  accuracy and is community-driven. '
+author: Leah Wasser
+blog_topic: learn
+toc: false
+comments: true
+url: "/blog/demystifying-python-packaging.html"
+lastmod: '2024-08-29'
+---
+
+## A guide to make Python packaging easier for scientists
+
+I've spent the last few months working on creating a Python packaging guide. This guide seeks to help those creating new scientific Python packages select a packaging tool and workflow. This guide also supports the [pyOpenSci peer review process](https://www.pyopensci.org/about-peer-review/).
+
+Below, I provide a brief overview of our content development process given the [packaging tool guide chapter has been published](https://www.pyopensci.org/python-package-guide/package-structure-code/intro.html)! Yay!
+
+# TL;DR
+
+There are a few key takeaways from this post:
+
+1. Many learn how to create a Python package by copying the structure of other packages built by maintainers they respect. While this is an OK approach, it doesn't help people better understand the ecosystem. And in some cases it can cause more confusion given the many different options and approaches.
+2. Much of the existing Python packaging blog post and guidebook content online is dated. The community needs dependable, maintained resources that they can rely on!
+3. Much of the existing packaging resources assumes some base technical knowledge about packaging making it difficult for beginners to work through and understand the content.
+4. pyOpenSci is [creating a Python packaging guidebook](https://www.pyopensci.org/python-package-guide/) driven by significant community input from packaging maintainers, scientists and others in the community. The guide's goal is to help people understand best practices for packaging that follow current standards and use current tools.
+5. We will also be creating some tutorials in the near future.
+
+The [packaging chapter of our guide](https://www.pyopensci.org/python-package-guide/package-structure-code/intro.html) is online now! Stay tuned for more content on environments, CI and testing!
+
+{{< figure src="images/python-package-tools-decision-tree.png" alt="Diagram showing a decision tree with the tools flit, hatch, pdm and poetry highlighted. The diagram is called Pick a Packaging Tool." caption="An diagram from our packaging guide that shows the core packaging tools that scientists may need to decide between. For a pure python package you can use any tool that you wish based on the features that you want in a tool. However, if you have a more complex build you may want to use PDM or the PyPA's build tool with a powerful back-end like meson-python." >}}
+
+## My jump into packaging
+
+In the Fall of 2022, in support of my [new role as Executive Director of pyOpenSci](/blog/new-executive-director-leah-wasser.html), I began to explore Python packaging tools in an effort to update our guidebook in support of our [package peer review program](https://www.pyopensci.org/software-peer-review/about/our-goals.html).
+
+I saw significant community confusion around how to create a Python package. But, in my mind, it wouldn't be that big of a challenge to create a guidebook.
+
+- There are a bunch of tools out there.
+- There are a bunch of Python standards that people should follow
+
+I just needed to find the combination of tools and standards that we could recommend to people in an attempt to demystify the packaging ecosystem.
+
+No problem, right?
+
+At the same time I noticed that many did not want to talk about
+Python packaging. And I wondered, why?
+
+{{< figure src="images/python-packaging/lion-meme-pyopensci.jpeg" alt="A meme showing a mountain lion with it's little paw up like an italian mobster. the meme text says - so you want to talk about python packaging.." caption="People didn't want to talk about Python packaging. It was such a painful, sore topic." >}}
+
+### My approach to learning how to create a Python package
+
+I've worked on the development of 3 other Python packages. Each time my approach to create a package was asking the question:
+
+- What would [GeoPandas](https://geopandas.org/en/stable/) do?
+
+GeoPandas is a spatial library that supports working with vector data (think points, lines and polygons). I decided to follow their structure, because I respected the Geopandas maintainers greatly, and I had [contributed to the package.](https://github.com/geopandas/geopandas/pull/1128)
+
+My approach to packaging was: "monkey see, monkey do". I was the monkey.
+
+I also munched on some bananas. It worked out alright.
+
+## The monkey approach to packaging is not ideal
+
+Copying a package's structure is like copying code from stack overflow and pasting it into your workflow in hopes it runs. If it doesn't run, you don't know enough to fix it! Frustration sets in.
+
+However, at least in Stack Overflow you can see when the post was published and know that it might be dated. I found it hard to find updated information on Python packaging tools. I found this particularly challenging considering I found so many tool options. And each tool had a level of documentation that assumed some depth of knowledge around Python packaging.
+
+Where does the authoritative and complete guide to packaging live and who maintains it? Further, is it helpful enough for a begineer to dig into and get started quickly?
+
+## In education, early wins are key
+
+I've taught data intensive science for almost 20 years. If there is one thing I know about teaching those new to technical areas, it is that early wins are critical. Whether the win is creating a simple data plot within the first 20 minutes of a workshop, or using an `init` method in PDM to create a package structure, early wins can motivate a beginner mind as:
+
+1. It builds confidence that they can do it
+2. That confidence allows a learner to continue even when it gets more complicated
+
+I struggled to find any resources that provided users of Python packaging tools with early wins. Rather, I found that I needed to increase my technical knowledge of packaging to even understand many of the resources out there.
+
+### How could pyOpenSci help?
+
+To support pyOpenSci's goals of making packaging easier for scientists while also improving package quality I knew we needed to create a guide that would help others navigate the packaging ecosystem. At a minimum, helping users understand the tool landscape and how to pick a tool was a good start.
+
+### Python packaging is not bad. It's just not well documented
+
+From all of the above I came to a conclusion that Python packaging is not bad. It's just not well documented. If people understood what all of the tools did and how to pick one, it might be akin to shopping for a car\*.
+
+_\*But without the annoying sales person who might assume you know nothing about cars if you are a women..._
+
+## A Python packaging guide for scientists
+
+In creating this guide, I talked with scientific Python tool maintainers, folks from [PYPA](https://www.pypa.io/en/latest/), [scientific python](https://scientific-python.org/) and maintainers of core packages (such as Flit, Hatch, Poetry and PDM) to get insights into common workflows, common challenges and tools that folks are using. This guide has been a true example of community-driven content. [If you are curious, you can see the contributor list here.](https://github.com/pyOpenSci/python-package-guide#contributors-)
+
+The packaging chapter alone had over [200 comments to address in round 1](https://github.com/pyOpenSci/python-package-guide/pull/55) of reviews. And another [200+ in round 2 of review](https://github.com/pyOpenSci/python-package-guide/pull/55). All of the chapters in our guide go through community review however this particular chapter elicited a LOT of strong response regarding which tools do what, and how they should be described.
+
+Sometimes, the discussions got tense. People have strong opinions about packaging approaches. Also, not everyone agrees on the best technical approaches. But even more interesting is that many involved knew something about some of the tools but often that was based on word of mouth or a quick glance at documentation. (this is largely because tools are evolving quickly). The people that knew the most were also the most technical, and often involved in the actual development of the tools.
+
+## An assessment of python packaging tools
+
+My take away from all of this:
+
+After hundreds of comments and conversations;
+
+After testing each one of the tools in our guide with a start to end workflow;
+
+My takeaway is that Python doesn't have a packaging problem (if you are a user creating a pure Python package).
+
+Python has a much more human problem where approaches to packaging are simply unclear, not well documented and often debated - heavily.
+
+Further, the standards created for Python packaging while important, live on a website that is not intended for the broader public to use.
+
+Sure, there are many tricky parts to packaging. And understanding the standards can be even trickier. This is certainly not a perfect system.
+
+However, we **can** create packages using the given existing tools -- now! I promise, this is true.
+
+It's just (extremely) hard to figure out:
+
+1. how do you create a package,
+2. which tool should we use, and
+3. why use that tool over the others?
+
+The Python ecosystem is evolving rapidly. Approaches evolve and it's hard to know which approaches are the most current. Those who deeply understand the packaging challenges represent a small subset of the community and also are technically proficient.
+
+In general, users want to use the simplest approach to publish their packages online.
+
+Remember - early wins go a long way.
+
+{{< figure src="images/python-packaging/dont-talk-about-peps-pyopensci.jpeg" alt="A meme from the movie flight flub showing brad pitt with his arms crossed in a black tshirt. The text says - the first rul of peps is do not talk about peps." caption="At one point, I was trying to link to Python standards - known as PEPS (Python Enhancement Protocols) given everyone was sharing the various PEPs that tools follow. I was then told that we should avoid linking to these pages as they weren't intended for public consumption. If that is the case then how does the public get current information about standards? While I understood the goal, My mind was a bit blown. This was one of many points of confusion that I had to sort through. :)" >}}
+
+## Assessment of packaging tools functionality
+
+At the same time there is no good assessment that i've seen of the tools
+that do exist to help users in the ecosystem. I had questions about:
+
+- what each tool does
+- what each tool could do better.
+- And how I should pick a tool for my packaging needs.
+
+It was clear that people want that guidance.
+
+## A few spoilers regarding what is to come
+
+With this all said, i'll now set the stage for what's to come from
+pyOpenSci in the upcoming months. And what i've learned so far.
+
+- There are a few great packaging tools that support comprehensive build workflows.
+- Many of the packing tools out there only have one core maintainer (a low bus factor). What would happen if a few of them just teamed up and worked together (and with the community) to move forward? Or could we somehow change that to add stability to the ecosystem?
+- We need better documentation with clear beginning to end quick-start tutorials that help new users get started. If the tools were better documented more people would use them.
+
+Right now, Poetry is the most common (modern) packaging tool being used. Have a look at its documentation and you'll see why! PDM, however, has numerous features that are be ideal for the scientific ecosystem's needs.
+
+Specifically it allows you to use [different build back ends](https://www.pyopensci.org/python-package-guide/package-structure-code/python-package-build-tools.html#build-front-end-vs-build-back-end-tools), which is good news if you are creating either a pure python package OR a package with some C/C++ extensions.
+
+_Poetry can't (yet) be a single solution to packaging because right now it's support of non pure python builds is not documented (and might not ever be). But it could be a great solution for those creating pure Python package._
+
+## What's next?
+
+In the next few blog posts i'm going to present each Python build workflow tool including:
+
+- Flit
+- PDM
+- Hatch and
+- Poetry.
+
+I'll break down the pros and cons of using each tool. I will also provide examples of what using the tool looks like. In the meantime, [check out our shiny new packaging chapter here to see the overview of packaging tools and approaches for scientists creating pure Python packages](https://www.pyopensci.org/python-package-guide/package-structure-code/intro.html).
diff --git a/content/blog/2023-06-13-pycon2023-peer-review-david-nicholson-crowsetta.md b/content/blog/2023-06-13-pycon2023-peer-review-david-nicholson-crowsetta.md
new file mode 100644
index 00000000..70007ad0
--- /dev/null
+++ b/content/blog/2023-06-13-pycon2023-peer-review-david-nicholson-crowsetta.md
@@ -0,0 +1,48 @@
+---
+title: 'Sorry This Talk Doesn''t Have any ChatGPT in It: pyOpenSci peer review of
+  Crowsetta '
+date: '2023-06-13'
+type: blog
+excerpt: David Nicholson gave a lightning talk about his experience going through
+  the pyOpenSci peer review process with his Python package called Crowsetta. Learn
+  more about the people involved in peer review and watch the 5 minute video here.
+author: Leah Wasser
+blog_topic: software
+toc: false
+comments: true
+url: "/blog/pycon2023-crowsetta-peer-review.html"
+lastmod: '2024-08-29'
+image:
+  src: images/blog/headers/david-nicholson-2023-header.png
+  alt: 'Sorry This Talk Doesn''t Have any ChatGPT in It: pyOpenSci peer review of
+    Crowsetta '
+---
+
+# pyCon 2023 US -David Nicholson Lightning Talk on pyOpenSci Peer Review
+
+David Nicholson, our pyOpenSci Editor in Chief, gave a fantastic lightning talk this year at [pyCon US 2023](https://us.pycon.org/2023/). This year's pyCon was held in Salt Lake City, Utah in April. David braved the expansive keynote room stage - talking to a gigantic room full of Pythonistas. He spoke about his experience going through our scientific Python software peer review process.
+
+<iframe width="560" height="315" src="https://www.youtube.com/embed/54q_cPCNNS8?start=1083" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>
+
+## Submitting Crowsetta to pyOpenSci for peer review
+
+Just a few months prior, David had submitted a package he's been developing called Crowsetta, that helps scientists work with annotations for animal vocalization and bioacoustics data. Given he is the Editor in Chief of our peer review process, we had wonderful volunteers from our editorial team step in to run the review to ensure it wasn't in any way biased.
+
+{{< figure src="images/talks/intro-slide-david-nicholson-crowsetta-lightning-pycon2023.png" alt="Image showing the title slide of David's talk. At the top is says - Sorry this talk doesn't have any ChatGPT. It then says my experience submitting to pyOpenSci. At the bottom you can see david's website (nicholdav.info), github NickleDave, Twitter nicholdav and mastodon account nicholdav@fosstodon.org" caption="Intro slide for David's Lightning talk at pyCon 2023 US." >}}
+
+[crowsetta](https://github.com/vocalpy/crowsetta)
+
+In his talk (which was NOT about ChatGPT in case you were wondering :) ), David talked about who was involved and what the process and his experience was like. Check out the video below to learn more!
+
+The talk itself is about 5 minutes long but you can always keep it running to see the other lightning talks posted by the pyCon organizers. All of the pyCon 2023 US talks are online if you want to check out some of the others! [You can also check out our
+pyOpenSci presentation about Python Packaging and experiences with the sprints here if you'd like.](/blog/pycon-2023-packaging-presentation-sprints-leah-wasser.html)
+
+## About the pyOpenSci peer review process
+
+Crowsetta went through our [pyOpenSci peer review process](https://www.pyopensci.org/about-peer-review/) in the Spring 2023. [If you want to check out the review for Crowsetta, click here.](https://github.com/pyOpenSci/software-submission/issues/68). David also took advantage of our [partnership with the Journal of Open Source Software (JOSS)](https://www.pyopensci.org/software-peer-review/partners/joss.html) which allowed the Crowsetta to become both a vetted pyOpenSci tool and also to get a cross-ref enabled citation from JOSS. Through this partnership JOSS accepts our review as theirs and only reviews the submitted paper.
+
+## Learn More
+
+David's talk can be found in our [pyOpenSci Zenodo community](https://zenodo.org/communities/pyopensci/?page=1&size=20), [here](https://zenodo.org/record/8033167).
+
+[![zenodo doi citation for David's lighting talk](https://zenodo.org/badge/DOI/10.5281/zenodo.8033167.svg)](https://doi.org/10.5281/zenodo.8033167)
diff --git a/content/blog/2023-06-14-pycon-maintainers-summit-python-packaging-talk-leah-wasser.md b/content/blog/2023-06-14-pycon-maintainers-summit-python-packaging-talk-leah-wasser.md
new file mode 100644
index 00000000..6a3d7728
--- /dev/null
+++ b/content/blog/2023-06-14-pycon-maintainers-summit-python-packaging-talk-leah-wasser.md
@@ -0,0 +1,212 @@
+---
+title: My First Time Attending PyCon - A Tale of Sprints and Python Packaging
+date: '2023-06-14'
+type: blog
+excerpt: This year I attended by first PyCon US meeting representing pyOpenSci. In
+  this blog I talk about my experience, highlighting the sprints we lead and talks
+  on packaging.
+author: Leah Wasser
+blog_topic: learn
+toc: false
+comments: true
+url: "/blog/pycon-2023-packaging-presentation-sprints-leah-wasser.html"
+lastmod: '2024-08-29'
+---
+
+## How it all went down - PyCON US 2023, Salt Lake City, Utah
+
+This year was my first time attending pyCon US! I was intimidated to attend such
+a big Python meeting. For years i've attended science meetings such as
+AGU (American Geophysical Union), ESRI (GIS) users conferences and ESA (Ecological
+Society of America). I've been to and lead data science hackathons and been to
+the annual SciPy meeting. But i've never been to a pure tech conference.
+
+Even after teaching data science using R and Python for the past 10 years I
+_STILL_ feel like an imposter sometimes.
+
+_What's up with that?_
+
+But I went and had a fantastic time. Getting to talk to people all day, every
+day about all things Python felt like how I might imagine a trip to Disneyworld
+feels for an 8 year-old... (minus the cotton candy, costumes and the upside down
+rides).
+
+I felt energized, excited. I learned so much and met SO MANY incredible people.
+
+A few highlights of the meeting are below.
+
+## Python packaging, packaging, packaging
+
+Did I mention packaging? No?
+
+Ok well I spent a lot of the meeting talking to people about Python packaging.
+
+I even got to present in the maintainers summit (see the video below) on...
+guess what?
+
+PYTHON PACKAGING!
+
+It was my first time recording myself talking formally about packaging and using
+OBS studio. And I have to say I have some sort of shifty eye syndrome going on.
+I think I still have a bit to learn from those YouTubers on video creation!
+
+<iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/Qxy7bxW72iA" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>
+
+This presentation echoed the sentiment that I shared in this [blog post about
+Python packaging.](/blog/demystifying-python-packaging.html)
+
+### TLDR breakdown
+
+If you're short on time, the take-aways of the talk were:
+
+- Our [pyOpenSci packaging guide](https://www.pyopensci.org/python-package-guide/) is community-driven. It is created via a heavily-moderated review process that consisted of several rounds of reviews.
+- Guidebook reviews were heavily moderated. This ensured that we formed consensus on packaging recommendations.
+- Packaging might seem "messy" but really it's just a matter of knowing what tools to use and how to use them. While this is not a simple task. We believe that these community-driven resources will help the scientific Python community by demystifying the packaging ecosystem!
+
+### Creating our packaging guide
+
+I spent a bit of time in that video talking about how we create our guides.
+
+- Every part of our guides are reviewed by lots of people.
+- Reviews for just a few pages of the guide could have 200 or more comments.
+- Our process is normally several steps including an initial writing of content that is reviewed by experts. Followed by 2 rounds of open reviews of the content. The image below describes that process.
+
+{{< figure src="images/python-packaging/pycon-packaging-review-process.png" alt="Graphic that has a large purple thick arrow. The title says Python Packaging Guide - Our Process. The sections in the arrow include Talk with core experts (write a section of the guide), semi-closed review (core experts review), Open Review 1 (ping tool developers and maintainers and welcome broad community feedback) and Open Review 2 (welcome broad community feedback)." caption="Image from my talk that shows our packaging guide review process. Our packaging guide is community-driven. This means that every page of the guide has been reviewed by dozens of people with expertise in the packaging space. While this meant that it is taking extra time to create the guide, it also means the community supports it. We value community knowledge and input at pyOpenSci." >}}
+
+Another part of our packaging guide review process is getting input from packaging
+experts in the community. These experts come from the core python community,
+the packaging community, the scientific community and even maintainers of core
+packaging tools.
+
+_Leave no stone unturned_ (my motto when doing most things).
+
+{{< figure src="images/python-packaging/pyOS-package-guide-contributors.png" alt=".sdf" caption="Image from my talk that shows our packaging guide review process. Our packaging guide is community-driven. This means that every page of the guide has been reviewed by dozens of people with expertise in the packaging space. While this meant that it is taking extra time to create the guide, it also means the community supports it. We value community knowledge and input at pyOpenSci." >}}
+
+### Why I LOVE peer review
+
+If you haven't already guessed, I have a deep seeded love for peer review. In my
+mind, anything that is produced that requires a lot of technical knowledge will
+only be improved when vetted by lots of people.
+
+Sure, it takes a lot of extra work to produce a guide that way. And it slows down
+the process. But, the end product will be worth it.
+
+As such we not only review Python packages at pyOpenSci. We also make sure that
+all of our content is heavily reviewed too.
+
+## The only (woman) in the room
+
+So I have to say this. While pyCon was the most wonderful experience, I did have
+a few awkward moments. For one, I was often one of
+the few female identifying people in the room. This was particularly true are the packaging summit where I gave a small presentation related to PyPA and packaging tools!
+
+I did feel welcomed and included. BUT, I can say that it is interesting to walk
+into a room and _know_ that you are different. I noted the
+things that made me feel super welcome and comfortable.
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">My 1st <a href="https://twitter.com/hashtag/PyCon2023?src=hash&amp;ref_src=twsrc%5Etfw">#PyCon2023</a> is FUN. As a female in STEM, tech &amp; <a href="https://twitter.com/hashtag/opensource?src=hash&amp;ref_src=twsrc%5Etfw">#opensource</a> i&#39;m walking into &amp; presenting in rooms full of men. it&#39;s been supportive but i&#39;ve found comfort in ppl actively welcoming me. taking notes 3 developing <a href="https://twitter.com/pyOpenSci?ref_src=twsrc%5Etfw">@pyopensci</a> how 2 implement inclusion strategies <a href="https://twitter.com/hashtag/PyConUS2023?src=hash&amp;ref_src=twsrc%5Etfw">#PyConUS2023</a></p>&mdash; Leah Wasser @leahawasser@fosstodon.org 🦉 (@LeahAWasser) <a href="https://twitter.com/LeahAWasser/status/1649795095414145025?ref_src=twsrc%5Etfw">April 22, 2023</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+## pyCon was more about (freakin amazing) people than code
+
+I can't even begin to highlight ALL OF THE AMAZING PEOPLE I met at pyCon. In some
+cases I met folks who I had been interacting with online Such as C.A.M. from the
+Python core team who I "met" on the Python Discourse. Or [Pradyun](https://github.com/pradyunsg) another Python core dev who has been
+involved with pyOpenSci providing guidance on the packaging space for months. Pradyun is also a part of our advisory council. His expertise is really invaluable to our organization.
+
+I got to meet [Erik](https://github.com/eriknw) who's Python package - [python-graphblas is going through our
+peer review process right now.](https://github.com/pyOpenSci/software-submission/issues/81)
+
+I met Chase, CEO of a really cool company called [Million Concepts](https://millionconcepts.com/about.html) and some of the folks from the [Python Heliophysics community](https://heliopython.org/).
+
+Finally, I got to meet and hang out with the amazing [Inessa Pawson](https://github.com/InessaPawson). If you haven't heard of
+Inessa's work it's extraordinary. Inessa has been working as a contributor lead
+for the Numpy project and is also a project manager for Open Teams.
+
+There are so many other people who I got to know and build working relationships
+at this meeting.
+
+## pyOpenSci Sprints at PyCON
+
+pyOpenSci also lead 2 sprints at pyCon! On Sunday we lead a [mentored sprint](https://www.mentored-sprints.dev/). If you haven't heard of mentored sprints, they are an
+amazing format that allows those who are newer to contributing to open source
+to get support in the contribution process.
+
+At the mentored sprints I was grateful to have [Luiz Irber](https://github.com/luizirber) and [David Nicholson](https://github.com/NickleDave) supporting
+the (larger-than-expected) group! Luiz served as editor for pyOpenSci years ago
+during one of our very first reviews. And David is now our editor in chief of
+pyOpenSci.
+
+We had a full table plus an overflow table of
+people who wanted to contribute! And each of them was able to contribute (many
+for their very first time!!). It was awesome.
+
+{{< figure src="images/people/pycon-2023-mentored-sprints-pyopensci.png" alt="Image showing people at laptops sitting around a round table wearing masks during our PyCon 2023 mentored sprint." caption="Contributors working together in small groups during our mentored sprints at PyCon 2023. People worked together on issues in pairs and had help from dedicated mentors. Most of the contributors had Python experience but also most had never contributed to open source before." >}}
+
+
+The people at the sprint were not the people who I expected.
+Many of them had significant technical skills and backgrounds. But many of them
+also had never committed to an open source project. Perhaps they had used subversion
+but not git / GitHub. Perhaps they knew python well but didn't know where to start
+in terms of contributing.
+
+In total we ended up with 8 pull requests submitted during the sprints and 2
+others submitted after. Every pull request was from a new contributor to
+pyOpenSci. And also they were mostly made by those new to contributing in general.
+
+If you want to check any of them out - please click on any of the links below!
+
+<div class="notice" markdown="1">
+
+## Contributions from the pyOpenSci mentored and regular sprints at PyCon US 2023
+
+Contributions to open source tools and communities can come in all shapes and
+sizes. Note that some of the items below are small fixes (which are a huge help).
+And others are a bit more involved.
+
+### More technical pr's
+
+- [This pr was a bit more involved and included some changes to how we handle tokens in our metrics package.](https://github.com/pyOpenSci/update-web-metadata/pull/24)
+- [This Python code update fixed the format that we were using to manage authentication tokens](https://github.com/pyOpenSci/update-web-metadata/pull/23)
+- [This is a more technical PR by Austin that updated some of our typing and cleaned up some of our API request calls](https://github.com/pyOpenSci/update-web-metadata/pull/19)
+- [This pr by Tiffany updated parsing our review issues. It ensured that we grabbed all maintainers from a review issue so we can list them in our package list once the package is accepted.](https://github.com/pyOpenSci/update-web-metadata/pull/14)
+- [This pr was another technical one submitted by Austin to fix how we were authenticating with the GitHub API](https://github.com/pyOpenSci/update-web-metadata/pull/11)
+- [Barnabas submitted this PR. It fixes a glitch in the website to ensure all maintainers are listed there (building on top of tiffany's PR above that fixed the code that actually collected maintainer names). ](https://github.com/pyOpenSci/pyopensci.github.io/pull/172)
+
+### Less Technical PR's
+
+These pr's are highlighted here because it's important to know that not all contributions
+need to be highlight technical. They can be text fixes that are equally important to projects.
+
+- Not all pr's need to be huge and technical. This one was actually done using only the GitHub interface! [This is a much less technical pr that updated the repos that we were using to grab contributors from. We wanted to grab all contributors so we can recognize them on our website.](https://github.com/pyOpenSci/update-web-metadata/pull/13)
+- [This was a less technical but equally important issue opened that suggested we add some more information to our guidebook. Not all contributions need to be code!](https://github.com/pyOpenSci/pyopensci.github.io/issues/168)
+- [This is another example of a pr that has no code involved! It was an update to our guidebook simplifying text that was redundant! Submitted by Mahe](https://github.com/pyOpenSci/software-peer-review/pull/210)
+
+### Packaging Guide pull requests
+
+In the spirit of understanding that not all contributions need to be code! The pr's
+below, submitted by Jeremy, identified lots of typos in our packaging guide! This
+was SO SO helpful to us!!
+
+- [Packaging guide typo fixes.](https://github.com/pyOpenSci/python-package-guide/pull/82)
+- [Second pr fixing typos.](https://github.com/pyOpenSci/python-package-guide/pull/81)
+
+</div>
+
+All of the contributors are now listed on our website. And we are grateful for
+each and every one of them!
+
+## Would I attend pycon again?
+
+I'm sure I don't have to tell you the answer to that question.
+
+heck-yea I would!
+
+The people I met at that meeting even sitting in the lunch room were incredible.
+And many of them have become colleagues that I am still in touch with and who
+are now involved with pyOpenSci.
+
+## A final highlight of the meeting - David Nicholson's Lightnight talk
+
+One of the other highlights of the meeting that I can't forget to mention is
+David getting up on the ginormous speaker stage in the main ballroom and
+giving a lightning talk about his experience submitting Crowsetta, a Python package, to pyOpenSci. [Check out a blog on his talk and watch the 5 minute presentation here.](/blog/pycon2023-crowsetta-peer-review.html) It was awesome!
diff --git a/content/blog/2023-07-18-pyopensci-scipy-2023.md b/content/blog/2023-07-18-pyopensci-scipy-2023.md
new file mode 100644
index 00000000..c6f04ec1
--- /dev/null
+++ b/content/blog/2023-07-18-pyopensci-scipy-2023.md
@@ -0,0 +1,208 @@
+---
+title: Shark Attacks and Open Science - pyOpenSci @ SciPy 2023 Meeting
+date: '2023-07-18'
+type: blog
+excerpt: The SciPy 2023 meeting did not disappoint this year. We have a whole new
+  group of contributors helping to build this vibrant and diverse Python open science
+  community. Learn about my experience there.
+author: Leah Wasser
+blog_topic: community
+toc: false
+comments: true
+url: "/blog/scipy-2023-community.html"
+lastmod: '2024-08-29'
+---
+
+## <i class="fa-solid fa-fish-fins"></i> Shark attack - pyOpenSci at SciPy
+
+I was so excited for SciPy this year.
+
+I wanted to spread the word about pyOpenSci's core mission - supporting
+the scientific open source Python community. I wanted to get more people
+involved.
+
+pyOpenSci represents everything that matters most to me:
+
+- 🌱 Community & People
+- 🎓 Education
+- 🔓 Open Science and Open Source
+- 🌈 Diversity, Equity and Inclusion
+
+## Unplanned is often best
+
+I am not used to going into a meeting with no specific plans and obligations.
+While pyOpenSci didn't get a talk or a community session / BoF this year, we
+did get a lightning talk! It was a randomized selection, and I threw my name
+into the bucket (literally) with fingers crossed that i'd get a lightning talk.
+
+And on the final day of the meeting, I was selected to present!
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr"><a href="https://twitter.com/pyOpenSci?ref_src=twsrc%5Etfw">@pyOpenSci</a> got the cutest slides at the lighting talk @SciPyCon <a href="https://twitter.com/hashtag/SciPy2023?src=hash&amp;ref_src=twsrc%5Etfw">#SciPy2023</a> <a href="https://t.co/ZXleLpdkqB">pic.twitter.com/ZXleLpdkqB</a></p>&mdash; Cheuk Ting Ho (@cheukting_ho) <a href="https://twitter.com/cheukting_ho/status/1679962465508147200?ref_src=twsrc%5Etfw">July 14, 2023</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+## The shark attack - my lightning talk about pyOpenSci
+
+Let me give you the backstory on lightning talks at SciPy. It's known that
+moderators will often "play" with those presenting.
+
+Puns are always pervasive and community embraced!
+
+This year there was a "sea" theme featuring sharks and crab claws. 😂 Watch
+below as the session is started with a crab claw pun by Paul followed up with
+a shark attack on yours truly from [Madicken](https://github.com/munkm/). You will also learn about the
+pyOpenSci mission and vision.
+
+<iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/vJpH-ctvPoU" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>
+
+## Sprints - my new favorite part of every meeting
+
+A sprint, in the tech world, is a short time period where people on a team work
+together to complete something on a technical project. At conferences, there are
+often open sprints. The idea here is that people, often some of whom are new
+to a project, get together in person and work on things that the project needs.
+
+### Mentored sprints make open source more inclusive
+
+In our open source world we also have [mentored sprints](https://www.mentored-sprints.dev/).
+The term mentored sprints was coined by an [amazing team of people](https://www.mentored-sprints.dev/team/) including [Tania Allard (who's passion for open source and open data resonates with my own)](https://www.trallard.dev/).
+It focuses on supporting those who are new to sprinting and using platforms such as
+GitHub in making their first contribution to open source.
+
+Given pyOpenSci's core values around diversity equity and inclusion, every
+sprint we hold is a mentored sprint as far as i'm concerned!
+
+This was the second sprint that i've lead with the [first being at pyCon US 2023](https://www.pyopensci.org/blog/pycon-2023-packaging-presentation-sprints-leah-wasser.html).
+
+### An organized list of tasks is key for any sprint
+
+My friend, colleague and [esteemed pyOpenSci advisory council member,](https://www.pyopensci.org/our-community/index.html#pyopensci-advisory-council) [Inessa Pawson](https://github.com/InessaPawson) taught me
+that:
+
+1. It's best to go into a sprint with an organized set of help-wanted issues.
+1. Identifying issues that could be completed in a few hours to a day is ideal.
+1. And tagging issues as beginner friendly helps those who are newer to sprints
+
+{{< figure src="images/github/pyopensci-github-help-board.png" alt="An image with a black background showing all of the issues that we could use help with at pyOpenSci. The caption for this image contains a link to the board which will allow you to hear and read through each issue listed on the board." caption="Our pyOpenSci help-wanted issue board has a list of things that we could use help with. Issues that could be done during a sprint are tagged 'sprintable'. Issues that are ideal for beginners are also tagged - beginner friendly. <a href = 'https://github.com/orgs/pyOpenSci/projects/3'>View the board here.</a>" >}}
+
+I went into our SciPy 2023 sprint with a [more organized pyOpenSci help-wanted board.](https://github.com/orgs/pyOpenSci/projects/3)
+This board has been a great way to keep track of things
+that we need help with.
+
+**<i class="fa-solid fa-circle-info"></i> GitHub PROTIP:** I struggled at PyCon with assigning people who didn't belong
+to a repository or our organization to specific issues. Now, I know that
+if someone comments on an issue first, I can then assign it to them
+(many thanks to [Thomas Fan](https://github.com/thomasjpfan) for the tip!!).
+{: .notice .info}
+
+## So many helpful contributions to pyOpenSci!
+
+I am absolutely blown away by and profoundly grateful for the
+support that pyOpenSci received at this year's SciPy sprints!
+
+We had over 20 pull requests emerge from this sprint - WOW! Two sprinters also
+submitted their first ever contributions!!
+
+**<i class="fa-solid fa-circle-info"></i> Info:** a pull request, known as a "pr", represents a set of suggested changes to a set of code or text. In the GitHub.com interface you can view the suggested changes and comment on them - in the same way that you might comment on suggested changes in a Google doc.
+{: .notice }
+
+Some of the contributions included:
+
+- Updating our website workflow to allow for site preview on every pr. This means that no one needs to setup a ruby environment locally in order to view website changes. And the less ruby environments contributors need to deal with, the better as far as I am concerned :) !!
+- Updating and enhancing our contributor package metadata workflow to be more efficient and effective
+- _A first contribution ever!!_ Grace helped us by fixing typos in our throughout our peer review guide! She called these fixes trivial but there is NO SUCH THING as a trivial pull request. We need fresh sets of eyes on all of our guides and appreciate any and all fixes that pr's bring big or small!
+
+In case you are curious, most of the pull requests submitted during the sprint this year are listed below:
+
+<div class="notice" markdown="1">
+## Pull requests submitted to pyOpenSci the 2023 SciPy sprints
+- **Thomas:** Thomas submitted a [set of pr's that allow us to preview our website after every pull request](https://github.com/pyOpenSci/pyopensci.github.io/pulls/thomasjpfan) is submitted.
+- **Mike:** Mike tackled our automated workflow that tracks contributors across our GitHub repositories and also that tracks packages, reviewers and editors in our review process.
+- **ruoxi** Ruoxi submitted an issue surrounding a rendering issue with our packaging guide in the Safari browser. And also a [pull request updating text around our partnership](https://github.com/pyOpenSci/software-peer-review/pull/232/files) with the Journal of Open Source Software (JOSS) where they accept our review as theirs and only review your paper.
+- **Grace:** [Grace made her first, second, third ...seventh!! pull requests ever fixing typos in our peer review guide](https://github.com/pyOpenSci/software-peer-review/pulls/g-patlewicz)
+- **Ricky:** [Url redirect fixes on website](https://github.com/pyOpenSci/pyopensci.github.io/pull/235)
+- **Kerry:** [Fixed the packages order so that newest was at the top of the page not the bottom](https://github.com/pyOpenSci/pyopensci.github.io/pull/234)
+
+</div>
+
+### People kept sprinting without me!
+
+I left before day two of the sprints. However, that did not stop
+the community from continuing to sprint and contribute to
+pyOpenSci! People continued to work additional
+website fixes that were still open our project board.
+
+### Lessons learned from SciPy 2023
+
+I learned a lot this year from SciPy.
+
+Sometimes the best moments are the unexpected ones. I had the
+chance to connect with amazing individuals and share pyOpenSci's
+impactful mission that I care about so deeply.
+
+And the best part? Our pyOpenSci community continues to grow, attracting more
+wonderful Pythonistas who share our vision. Together, I'm confident that we
+will make a positive impact on scientific open source Python community.
+
+That's what truly matters.
+
+And I gave out a lot of pyOpenSci stickers too!
+
+{{< figure src="images/pyopensci-stickers.png" alt="Two pyOpenSci sticker designs. the one is a light purple flower with white stamen and the letters pr and O as the center of the sticker. The S is a snake. The econd sticker is a darker and lighter purpler that says pyOPenSci and has the top half of a flower above the O in open." caption="Fresh off the press - pyOpenSci stickers!" >}}
+
+## For all of you introverts - a few tips that helped me this year
+
+My approach to participating in SciPy was so much better than that at pyCon.
+
+I learned some valuable lessons about taking care of
+both my work and my mental well-being. As an introvert in a busy meeting filled
+with awesome colleagues, it's easy to get burnt out.
+
+Here's what I did to make sure I left the meeting feeling refreshed and energized:
+
+- 🌟 I prioritized mental health: It's all about balance. I put as much effort into taking care of myself as I did into my work during the meeting.
+- 🌟 Embraced breaks: During the meeting, I consciously took short breaks to unwind. Whether it was chilling in my hotel room or going for a stroll outside, giving my brain a breather made a world of difference. And guess what? I slept better at night too!
+
+* 🌟 Me time matters: While I didn't participate in every social activity, I didn't feel like I was missing out. Instead, I used that time to recharge solo and get some extra sleep. And let me tell you, it worked wonders!
+* 🌟 Balanced work and recovery: To avoid getting run down, I allowed myself to miss the second day of the sprints. This allowed me to travel home on Sunday and recover in the afternoon with my furry friend, Juno.
+
+In the end, I may have missed a bit of the action, but the payoff was totally worth it. I left the meeting feeling way better than I did after PyCon.
+
+So, fellow introverts, remember this little secret weapon called
+"recovery time" at your next big event! It's a game-changer!
+
+## A personal note - flying solo in the open source world is never truly solo
+
+Back in March 2023, I made a bold decision to leave a toxic academic
+environment and fully dedicate myself to building and growing pyOpenSci—an
+amazing, community-focused organization.
+
+Let me tell you, taking that leap of faith was pretty intimidating. The academic
+setting had taken a toll on me, shattering my confidence and even affecting my
+health. But I knew in my heart that I wanted to channel all my energy into
+community work, collaborating with people who respected and appreciated me as
+much as I respected them.
+
+And guess what? This journey has been beyond my wildest dreams! Not only has
+the pyOpenSci community thrived and made a remarkable impact in just its first
+year, but it has also turned out to be the kind of inclusive, supportive
+community I always envisioned.
+
+It's incredible how not only is pyOpenSci helping others, but it's also been a
+source of support and healing for me. I couldn't be more grateful for this
+vibrant and uplifting environment that we've created together.
+
+I'll keep pushing forward, knowing that this beautiful journey is just the
+beginning.
+
+Thank you, SciPy for supporting me and reinforcing the fact that I made the right decision! And i'd be remiss if I didn't also thank the pyOpenSci community
+that is truly bring pyOpenSci's vision to life.
+
+## Wrapping up
+
+And that is all I have to say about SciPy 2023! It was an incredible experience.
+If you are reading this and we connected at SciPy this year or if you contributed
+to pyOpensci this year, I just want to say thank you.
+
+From the bottom of my heart. I see change coming in the upcoming years.
+pyOpenSci wants to be a part of and to drive that change!!
+
+We can't achieve that without your help!
diff --git a/content/blog/2023-09-11-community-manager-job-available.md b/content/blog/2023-09-11-community-manager-job-available.md
new file mode 100644
index 00000000..986dacd3
--- /dev/null
+++ b/content/blog/2023-09-11-community-manager-job-available.md
@@ -0,0 +1,172 @@
+---
+title: 'CLOSED: pyOpenSci is Hiring a Community Manager'
+date: '2023-09-11'
+type: blog
+excerpt: This position has been filled. pyOpenSci is hiring a community manager. This
+  position will oversee numerous aspects of pyOpenSci's community building efforts
+  including managing social media, our slack organization and writing blog posts.
+  It will also be heavily involved in our DEIA related activities.
+author: Leah Wasser
+blog_topic: updates
+toc: true
+comments: true
+url: "/blog/pyOpenSci-hiring-community-manager-fall-2023.html"
+lastmod: '2024-08-29'
+---
+
+<div class="notice" markdown="1">
+**IMPORTANT:** we are no longer accepting applications for this position.
+Thank you for your interest.
+</div>
+
+## Job Posting: pyOpenSci Community Manager
+
+pyOpenSci is accepting applications for a Community Manager. The Community
+Manager supports growth and development of an inclusive pyOpenSci community. Our vibrant community is
+dedicated to supporting high quality Python open source software that drives open science.
+
+While our organization is global we can only accept applications from candidates who are eligible for employment in the United States.
+
+## About pyOpenSci
+
+pyOpenSci is a diverse scientific open source / open science community that:
+
+1. Develops processes, guidelines, and training around the creation and maintenance of scientific Python packages.
+2. Leads a community-driven peer review process of Python scientific software
+
+pyOpenSci’s core program is open peer review of scientific Python software.
+Through peer-review we enforce community-defined packaging standards while
+improving usability, documentation and package quality. Further, we are creating a catalog of vetted scientific [Python tools](https://www.pyopensci.org/python-packages.html) that have ongoing
+maintenance for scientists to use.
+
+Core to our mission is increasing participation
+of groups that have historically underrepresented / excluded from the open
+source and open science community. We do this through mentorship, training and
+strategic partnerships with existing organizations
+such as [MetaDocencia](https://www.metadocencia.org/), [Open Science Labs](https://opensciencelabs.org/) and other
+organizations.
+
+pyOpenSci is a community-owned organization, fiscally sponsored by Community
+Initiatives. We are grateful to be funded by the [Sloan foundation](https://sloan.org/).
+
+## About the role / what we are looking for
+
+We are looking for someone with experience managing, engaging with and inspiring large,
+diverse, online communities. This person will promote pyOpenSci's mission to the broader scientific and tech communities. They will also help develop educational content around Python packaging and open science workflows.
+
+We are looking for someone that is excited about:
+
+1. facilitating outreach activities
+2. developing community partnerships
+3. promoting our organization at online and in-person events
+4. engaging with our vibrant community to encourage participation
+5. developing and teaching open source and open science content
+6. writing blog posts and social media content to promote the organization
+7. developing educational content around open science and Python packaging
+8. getting the word out about pyOpenSci!
+
+We are also looking for someone that is both committed to DEIA work and also has experience working on programs that target increasing diversity in the scientific open source software community. Ideally, we'd like someone who is familiar with both the Python programming
+language and the goals of open science.
+
+This position provides the opportunity for someone to drive the pyOpenSci
+mission of building a diverse and supportive community forward.
+
+### Hiring overview
+
+This is a full-time position with benefits with an ideal start date around November 2023 but no later than January 1, 2024. This position will report
+to the pyOpenSci Executive Director. Applicants must be eligible for employment in the United States.
+
+Review of applications will begin on September 1, 2023 and will be ongoing until the
+position is filled. All positions in our organization are
+grant funded. We currently have funding for this position through at least June 2025. Assuming continued project
+success, we will continue to seek additional funding to extend
+the work beyond June 2025.
+
+## Work environment & hiring requirements
+
+This position is fully remote. We also prefer that you live in the United States to simplify asynchronous remote work.
+**IMPORTANT:** While our reach is global, we can only hire someone who is either a resident / citizen in the United states or a resident with a valid work permit.
+
+All work that you do should exemplify our community [Code of Conduct](https://www.pyopensci.org/handbook/CODE_OF_CONDUCT.html)
+
+## What Your Key Responsibilities Will Be:
+
+### Community Management
+
+- Build and manage an active, diverse, and inclusive online pyOpenSci community by engaging with the community, staying informed of the needs and motivations of current and prospective members and responding with programming that meets these needs
+- Manage community conflict and [enforce our Code of Conduct](https://www.pyopensci.org/handbook/CODE_OF_CONDUCT.html) as a driving member of the Code of Conduct team.
+- Facilitate regular communication with pyOpenSci community members.
+- Organize, plan, and drive participation at community building events, both virtual and in-person, that provide positive and valuable interactions for members, consistent with pyOpenSci’s mission
+- Lead diversity, equity, and inclusion (DEIA) efforts to ensure that pyOpenSci members from all backgrounds are supported and empowered to participate. This will include the development of a mentorship program for underrepresented groups in open source
+- Solicit new packages for review as well as identify and facilitate the resolution of potential hold ups in the review process.
+- Help maintain databases of community members, maintainers and packages for pyOpenSci
+
+### External Communications
+
+- Cultivate strategic relationships with new and existing partner organizations Current partners include [JOSS](https://joss.theoj.org/),
+  [rOpenSci](https://ropensci.org/), [Pangeo](https://pangeo.io/), [The Carpentries](https://carpentries.org/), [MetaDocencia](https://www.metadocencia.org/) and [2i2c](https://2i2c.org/), [astropy](https://www.astropy.org)
+- Travel to meetings to represent pyOpenSci and build awareness of pyOpenSci's mission and programs.
+
+### Content Creation
+
+- Grow pyOpenSci’s online presence through content creation and management for multiple platforms (e.g. social media, discussion forums, Slack, blogs, and GitHub)
+- Identify and fill gaps in pyOpenSci’s web resources, including our peer review and Python packaging guide
+- Development of training resources around open source and open science skills
+
+## About You - What experience you need for this position
+
+- Outgoing personality that is driven by community work
+- Experience working in a relevant discipline such as science communication, science, math, engineering, or computer science (or a bachelors degree in this space). We strongly prefer someone who understands the scientific community.
+- Fluency speaking english
+- 2+ years of experience working with, promoting and managing communities that support open source projects; alternatively demonstrated experience in the scientific data science space as an evangelist or advocate
+- Experience creating strategic content for social media platforms and tools (specifically Mastodon and LinkedIn) and fostering online engagement
+- Strong desire to deepen your knowledge of best practices for DEIA efforts and demonstrated experience working in the DEIA space
+- Ability to work in a distributed, collaborative team environment - including managing ambiguity, concurrent projects, and work taking place across multiple time zones
+- Experience using git/GitHub or willingness to learn
+- Excellent time and project management skills
+- Excellent oral and written communication skills. These skills will be applied to various areas including website and blog content creation, conflict resolution, technical writing, and external communication at conferences including presentations.
+- Strong interpersonal skills. Ideally you have experience cultivating trust through active listening and responsive dialogue to support members in feeling welcome and supported in joining and actively participating in the community
+- Creative, motivated problem-solver, with an ability to bring forth new ideas for engagement, create systems from scratch, and find new partners
+
+## About You - Other expertise that will be useful but not required
+
+- Fluency speaking Spanish
+- Experience developing or contributing to open source software
+- Experience or familiarity with Python programming
+- Bachelors degree in STEM or communications and/or demonstrated experience working in the open science / open source space.
+
+## What to expect
+
+### Within 1 month, you will…
+
+- Meet and interact with the pyOpenSci community on Slack and begin to regularly communicate with members answering questions and facilitating conversations.
+- Contribute to the pyOpenSci documentation for peer review and python packaging
+- Have reviewed pull requests that update our python packaging guide, peer review guide and website content
+- Written a blog on pyopensci.org introducing yourself
+- Setup and be managing pyOpenSci social media accounts on Mastodon, LinkedIn
+
+### Within 3 months, you will be…
+
+- Updating our database of people and packages reviewed
+- Growing our social media following and support community meetings and events
+- Working with the community to develop new blog posts on packages in our ecosystem
+- Developing and contributing to a mentorship program to support new contributors to open source
+- Curating and contributing content to our online community on [social media](https://fosstodon.org/@pyOpenSci), Slack and other platforms as needed.
+
+### Within 6 months, you will be…
+
+- Planning a community unconference online event
+- Be building relationships with core organizations in the open source and DEIA open science space
+- Be working with the executive director to secure funding for pyOpenSci
+- Be working with the executive director to develop a training program and content that teaches scientists how to create python packages and implement open science workflows.
+
+## Equal Employment Opportunity
+
+Community Initiatives is an equal opportunity employer and gives consideration
+for employment to qualified applicants without regard to age, race, color,
+religion, creed, sex, sexual orientation, gender identity or expression,
+national origin, marital status, disability or protected veteran status, or
+any other status or characteristic protected by federal, state, or local law
+Posting Contact Information
+
+For questions about the job, please email: admin at pyopensci.org
diff --git a/content/blog/2023-10-18-rse-2023-pyopensci-bof.md b/content/blog/2023-10-18-rse-2023-pyopensci-bof.md
new file mode 100644
index 00000000..49c9e552
--- /dev/null
+++ b/content/blog/2023-10-18-rse-2023-pyopensci-bof.md
@@ -0,0 +1,197 @@
+---
+title: pyOpenSci Python packaging discussion at the Research Software Engineering
+  meeting 2023
+date: '2023-10-18'
+type: blog
+excerpt: pyOpenSci held a community birds of a feather session at the 2023 RSE meeting
+  in Chicago where we discussed peer review and packaging pain points. Learn about
+  the packaging pain points that they RSE-Python community experiences and how pyOpenSci
+  is addressing Python packaging pain points.
+author: Leah Wasser
+blog_topic: learn
+toc: true
+comments: true
+url: "/blog/pyOpenSci-research-software-2023.html"
+lastmod: '2024-08-29'
+---
+
+## Intro
+
+In October 2023, the United States Research Software Engineering (US-RSE),
+funded by the Sloan foundation, held its very first ever
+[meeting](https://us-rse.org/usrse23/).
+
+I attended this meeting and lead a community session around our peer review
+process and Python packaging. Key TL&DR takeaways were:
+
+1. Many RSE's use Python (the show of hands in the main conference room on day 2 suggested 60-70% of them use it in their daily work)
+1. Most feel like the packaging ecosystem can be confusing to navigate given there are numerous ways of creating a Python package
+1. RSE's are using a suite of different packaging tools and approaches in their Python work.
+
+The good news take away is that the exact pain points described to me at this
+meeting are the ones that pyOpenSci is taking on. We are currently working on
+an end-to-end packaging tutorial that hopefully will shed light on and demystify
+a complex but vibrant ecosystem of Python packaging tools and options.
+
+## What is a Research Software Engineer?
+
+So, what is an Research Software Engineer (RSE)? While the position has existed for some time, an RSE can be [loosely defined](https://us-rse.org/about/what-is-an-rse/) as someone who uses code regularly to do research. Many RSE's also work on developing
+software, in Python.
+
+As a side note this is a position that hasn't been traditionally
+supported by default academic environments even though this work is critical
+to research in the open science space. The RSE position should be a clearly
+defined, funded, respected and supported career path in all academic
+institutions that want to embrace open science as a way of doing research.
+My opinion is: academia needs to extend the definition of academic products to
+including not only publications but other output that is equally valuable and
+even more critically important such as software. RSE roles should be associated
+with clear academic career paths.
+
+Why? Because software is DRIVING open science. Without open source code, you
+can't make a workflow truly open and reproducible. This is why peer review is so
+important to pyOpenSci. We want to support maintainers in both developing and
+maintaining the critical software that is driving science. We also want them
+to get credit for their work which is why we partner with the Journal of
+Open Source software.
+
+{{< figure src="images/pyopensci-open-source-foundation-open-science.png" alt="AN image that shows a house with a chimney blowing smoke out that says scientific discovery. Below the house is open source as the foundation for open science. At the top of the slide is says open source == foundation" caption="To be truly open, code that drives scientific inquiry needs to have an open license. Thus open science depends upon open source software. As such it makes sense that academia value open source software in the same way they value publications that are derived from using such software." >}}
+
+> The RSE position should be a clearly
+> defined, funded, respected and supported career path in all academic institutions
+> that want to embrace open science as a way of doing research.
+
+Ok i'll casually step off my soap box now... back to regular scheduled
+programming we go...
+
+## pyOpenSci as the Chicago RSE meeting
+
+I lead a pyOpenSci Birds of a Feather (BoF) session at the Chicago RSE meeting.
+BoF sessions are informal community gatherings around a specific topic. BoF's provide a chance for the community to engage with each other, ask questions, provide input and even get involved in an effort.
+
+I spent most of my time in this 1.5 hour session talking about pyOpenSci and the work we are doing related to:
+
+1. [peer review of scientific Python software](https://www.pyopensci.org/about-peer-review/index.html)
+2. the community-driven [Python packaging resources](https://www.pyopensci.org/python-package-guide/) that pyOpenSci is developing
+3. [Community peer review partnerships that we are developing](https://www.pyopensci.org/partners.html) and
+4. the training and mentorship program that we are building both support scientists and diversify who is participating in open source
+
+We had a lively discussion around packaging - more on that below.
+
+## pyOpenSci BoF by the numbers
+
+I used Mentimeter to drive an engaging and interactive session. You can check out the slides below:
+
+<div style='position: relative; padding-bottom: 56.25%; padding-top: 35px; height: 0; overflow: hidden;'><iframe sandbox='allow-scripts allow-same-origin allow-presentation' allowfullscreen='true' allowtransparency='true' frameborder='0' height='315' src='https://www.mentimeter.com/app/presentation/alscm41q425ntc16f4ontr4p4qvg2ii6/embed' style='position: absolute; top: 0; left: 0; width: 100%; height: 100%;' width='420'></iframe></div>
+
+Mentimeter allowed me to capture audience feedback in several forms both verbal and via phones and computer through mentimeter.
+
+I'll try to summarize if all for you here.
+
+- We had approximately 50 people attend our 1.5 hour BoF
+- I spent ~1 hour after the BoF answering questions and talking to folks about all things Python open source - with a strong emphasis on packaging challenges.
+- Some of that discussion bled into dinner after where I spoke with one of our community partners, Nabil from [sunpy](https://www.sunpy.org)
+
+In our BoF, I introduced the three core programs that pyOpenSci currently runs which are:
+
+1. Open peer review of scientific Python software
+2. Community-driven packaging resources
+3. Mentorship and training to diversify our ecosystem
+
+{{< figure src="images/pyopensci-programs.png" alt="A flower image with three petals - software peer review, community partnerships and packaging resources. at the center of the flower it says diverse, inclusive community" caption="pyOpenSci has three core programs related to Python scientific software. We spent a lot of time talking about software peer review and also packaging challenges in our BoF session." >}}
+
+### Days since your last Python environment broke
+
+One of our community members, Isabel, suggested a great icebreaker question : how long has it been since you had a broken Python environment.
+
+It is no surprise that most pythonistas regularly deal with
+environment challenges.
+
+So if you've been in this boat too, you are are not alone!
+
+{{< figure src="images/pyos-days-python-environment-failed.png" alt="A mentimeter slide. at the top it says days since your last failed python environment. To the right is a picture of people from the Office - a tv show. They are holding a chalk board that says 0 days since last ruined Python environment. On the left is 6 sections with purple circles representing peoples votes for 0 days, 1-7 days, 8-14 days, 15-30 days and > 30 days. No one voted for never. But 12 voted for 1-7 days, 9 for 8-14, 8 for 15-30 and 9 for > 30" caption="Above each of the purple dots represent a vote for a specific number of days. For 12 people, it had only been 1-7 days since their environment had broken. For 9 other lucky people, it had been more than 30 days. A great followup question regarding this might be whether they used containerized environments, or pinned environments that didn't need modifications." >}}
+
+Full disclosure the one person who voted for 0 days, admitted to the fact that they hadn't used Python in the past month. :)
+
+## RSE's experience with Python packaging
+
+In the BoF i asked some questions related to Python packaging so we could have a
+discussion around some of the challenges. This is useful to pyOpenSci as we
+developing our packaging guide and associated resources to guide the scientific
+community through the process of creating a package.
+
+Below you can see a word cloud generated from the question
+
+"What Python packaging tools have you used?"
+
+{{< figure src="images/rse-2023-packaging-tools.png" alt="This is a word cloud with many different words representing tools that scientists use to create packages. Amongst the words the biggest - which represent tools that multiple people selected - were pip, conda, pytest, mamba, pypi, github actions, setuptools and poetry." caption="From this word cloud you can begin to see that there are many different tools in the python ecosystem that scientists use to create packages. The sheer volume of options can be great for some who know a lot about the ecosystem. However, for many others it can be overwhelming to have to chose between tools and approaches. This is a pain point that pyOpenSci is addressing." >}}
+
+A few things that popped out to me included:
+
+- unsurprisingly **setuptools** is still heavily used in our ecosystem even with the wealth of other build tools available
+- **mamba** is definitely growing traction in this space. we love mamba given how fast it is in resolving scientific environments.
+- people know about **grayskull**! If you don't know about it, you should! it's a great way to create the yml file that you need to submit your package to the conda-forge channel of conda. At the Scipy 2023 packaging BoF most in the room seemed unaware of this tool.
+- **mkdocs** seems to be giving sphinx a run for it's money! it sure does create beautiful docs. And quarto is also gaining traction. However with that said Sphinx is still the most popular packaging tool (at least in that room at that moment).
+
+### How many is too many Python packaging tools?
+
+The broad take away from this graphic is that there are a LOT of tools
+available for scientists to use. And becoming familiar with all of these is a big ask for a scientist who just wanted their code to be reusable by others.
+
+We have some work to do at pyOpenSci to [demystify this ecosystem](/blog/demystifying-python-packaging.html)!
+
+## Challenges in the ecosystem
+
+The other telling question was "what are your biggest challenges in the Python packaging ecosystem?
+
+The responses were varied but can be grouped into several
+
+### Too many packaging options and no one clear best practice
+
+It's no surprise that there were a handful of responses related to the volume of packaging options which make it hard to figure out which
+path to take when creating a package. Not only that but the options have changed over time as standards have evolved in the ecosystem
+
+I think the comment below summarizes this well:
+
+> too many options, and tutorials feel like consensus documents rather than making strong recommendations for One Best Way
+
+The good news is that this is exactly the pain point that pyOpenSci is working on. You can check out our [community-driven packaging guide](https://www.pyopensci.org/python-package-guide/) which presents an overview
+of the ecosystem with recommendations for best practices. This guide has been reviewed by dozens of Pythonistas in our ecosystem including those who built and maintain core packaging tools.
+
+Currently, we are developing packaging tutorials that answer
+the most fundamental question:
+
+> How do I create a (pure) python package?
+
+All of our packaging content is community driven, created using a robust
+community review process for packaging experts across our ecosystem. We
+feel confident that we will be able to shed some light on this complex
+and evolving ecosystem.
+
+## Other questions about pyOpenSci
+
+Admittedly many of the questions that I received in this session were about packaging. The community generally frustrated sometimes turning to tools
+such as ChatGPT to ask questions about packaging.
+
+As someone who has spent a large amount of time testing ChatGPT with packaging questions, I can tell you with certainty that it will lead you in a confusing direction as it doesn't have it's packaging facts straight.
+
+Proceed with caution!!
+
+We also got some other questions about our peer review process, how we
+interact with JOSS (Journal of Open Source Software) and how our [partnership programs](/partners.html) work.
+
+I'll save those questions for a followup post on pyOpenSci programs.
+
+## pyOpenSci has work to do!
+
+My key takeaways from the US-RSE meeting is:
+
+1. It's great that support is forming for this academic critical role that is required if we truly want to embrace open science. If you want to learn more visit about the US RSE effort, visit the [US-RSE website](https://us-rse.org/) website.
+2. The US RSE community is facing the same Python packaging challenges that we've seen across other communities. pyOpenSci's is committed to continuing it's work in the peer review and packaging space. Key an eye out for our tutorials in the upcoming months and check out our packaging guide in the meantime for an overview of the ecosystem.
+3. If you are interested in getting involved with pyOpenSci there are a few different ways:
+
+- you can [review a pull request](https://github.com/pyOpenSci/python-package-guide/pulls) on our packaging guide. Or open and issue if you have a problem with the guide.
+- You can [sign up to be a reviewer for pyOpenSci here](https://docs.google.com/forms/d/e/1FAIpQLSeVf-L_1-jYeO84OvEE8UemEoCmIiD5ddP_aO8S90vb7srADQ/viewform)
+
+As for me, I hope to attend the 2024 RSE meeting and to continue this important
+conversation around Python packaging and peer review of software.
diff --git a/content/blog/2023-11-29-welcome-jesse-pyos-community-manager.md b/content/blog/2023-11-29-welcome-jesse-pyos-community-manager.md
new file mode 100644
index 00000000..8f19cc64
--- /dev/null
+++ b/content/blog/2023-11-29-welcome-jesse-pyos-community-manager.md
@@ -0,0 +1,31 @@
+---
+title: "\U0001F44B Hello, world! Greetings from the new pyOS Community Manager"
+date: '2023-11-29'
+type: blog
+excerpt: Learn more about our new pyOpenSci Community Manager, Jesse Mostipak, in
+  her first pyOpenSci blog post!
+author: Jesse Mostipak
+blog_topic: community
+toc: true
+comments: true
+url: "/blog/pyOpenSci-new-community-manager.html"
+lastmod: '2024-08-29'
+---
+
+## Chicago, cats, and community
+
+I’m thrilled to be joining pyOpenSci (pyOS) as the Community Manager, and bringing my experiences as a researcher, educator, and developer advocate to support the creation and maintenance of free and open Python tools for processing scientific data. I’ve spent most of my adult life building online communities, from video games to programming to data science, and it’s exciting to see so many familiar faces in my first weeks at pyOS.
+
+One of the things I’m most excited to bring to pyOS is the creation of engaging, approachable, and accessible technical content around some of the thornier Python issues, like [packaging](https://www.pyopensci.org/python-packages.html)! Whether it’s blog posts, social media content, or videos, I want to ensure that our educational materials are available to everyone, regardless of geography.
+
+Another area that I’ll be particularly focused on is the [pyOS Peer Review program](https://www.pyopensci.org/about-peer-review/index.html). The Peer Review program with pyOS supports scientists in getting credit for the efforts they’ve invested in open source Python tools, while also supporting the standardization of packaging and improved package visibility. And as the pyOS Community Manager, I want to help celebrate all of the hard work that authors, maintainers, and editors put into package development by sharing behind-the-scenes stories, package announcements, and the contributions of every individual with the broader community.
+
+When I’m not helping build equitable, diverse, and accessible technical communities, I’m chilling with my two cats, Jinx and Luna, or riding my bike on the incredible gravel trails in the Chicago area.
+
+{{< figure src="images/jinx-and-luna.png" alt="A close-up photo of two cats sitting side-by-side on a blanket. Jinx, an orange and white tabby with a medium-length coat sits on the left, gazing directly into the camera. Luna, a short-haired black cat, sits on the right, looking at something past the camera" caption="World's greatest co-workers Jinx (left) and Luna (right)." >}}
+
+## Why pyOpenSci
+
+I first got started in scientific programming during my time as a graduate student in Immunology and Infectious Diseases. Learning R opened up a world of possibility for me, and I eventually used that early experience to build a career in data science. And out of all the learning materials available, I found the community to be the most critical in my success. While I’m no longer spending my days coding, I wanted to continue working with supportive, welcoming, and educational online communities that were focused on helping its members solve technical challenges.
+
+pyOpenSci meets all of those criteria, and the more I learned about its philosophy around community building, as well as all of the ways for people of all levels of technical knowledge to get involved, the more I knew I wanted to be a part of things. I’m still within my first month at the organization, but I can already tell that it’s a special place to be. Keep an eye out, because I’ve already started planning content and activities to help grow our community!
diff --git a/content/blog/2024-01-03-czi-funds-pyopensci-2024.md b/content/blog/2024-01-03-czi-funds-pyopensci-2024.md
new file mode 100644
index 00000000..71526ffa
--- /dev/null
+++ b/content/blog/2024-01-03-czi-funds-pyopensci-2024.md
@@ -0,0 +1,68 @@
+---
+title: CZI Funds pyOpenSci
+date: '2024-01-03'
+type: blog
+excerpt: CZI has received funding from the Chan Zuckerberg Foundation. Learn more
+  about how this funding will support pyOpenSci over the next 2 years.
+author: Leah Wasser
+blog_topic: community
+toc: true
+comments: true
+url: "/blog/czi-funds-pyOpenSci-2024.html"
+lastmod: '2024-08-29'
+---
+
+## A bright 2024 is ahead for pyOpenSci
+
+We are thrilled to announce that pyOpenSci has received 2 years of funding to cover core operations from the [Chan Zuckerberg Initiative (CZI)](https://chanzuckerberg.com/). These CZI funds will be used to continue critical pyOpenSci work that:
+
+* supports Python open source maintainers in developing the usable and maintainable scientific software the enables open science;
+* helps scientists navigate a complex Python packaging ecosystem;
+* diversifies the scientific Python open source community.
+
+
+## Open science builds trust and enables more people to participate
+
+Open and reproducible science builds trust and accelerates research and
+discovery. Open science supports scientific research that is both transparent and
+reusable. Free and open source software is critical to open science as it ensures that
+the analyses of research data are broadly accessible. To build truly open research workflows, scientists need to use free and open source software (FOSS). FOSS removes the barriers that licenses and other fees may create making diverse participation more accessible.
+
+### Broad inclusion is critical for both open source and open science
+
+Broad inclusion of underrepresented and historically excluded individuals is critical to pyOpenSci's mission. The open source ecosystem has been found to be [even less diverse then the broader tech community](https://www.wired.com/2017/06/diversity-open-source-even-worse-tech-overall/). To help remedy this, pyOpenSci empowers everyone to participate in both the development and use of open source software. This
+empowerment enables open science to reach its full potential.
+
+### Open source maintainers need support
+Despite the importance of open source software to fundamental
+open science principles, open source maintainers do not get the support they
+need. Maintainers need both institutional and community support in learning
+and engaging in open source software development, maintaining tools and engaging
+with the broad user base that may begin to use their tools in support of open science.
+
+## pyOpenSci is pushing for change
+
+pyOpenSci is pushing for change. We envision a world where:
+
+* The scientific Python open source ecosystem is diverse and inclusive;
+* Individuals developing open software are supported;
+* Scientists have the skills needed to both contribute to open source and also develop collaborative open science workflows; these skills have significant overlap.
+
+## pyOpenSci builds a supportive and inclusive world through three programs
+
+{{< figure src="images/pyopensci-pillars-flower.png" alt="A flower petal image with 3 flower petals and a flower center. In each petal there is text. The first says software peer review, the second community partnerships and the third packaging resources and recommendations. The center circle of the flower says diverse inclusive community." caption="pyOpenSci supports scientists developing open source software through three programs: 1) peer review of scientific software, 2) community partnerships and 3) packaging resources and recommendations. These three programs are supported by a diverse and inclusive community that cares about the open source software that is needed for open science." >}}
+
+The three programs pyOpenSci runs are:
+
+* [Peer review of scientific Python software](https://www.pyopensci.org/about-peer-review/index.html) - The pyOpenSci software peer review process helps scientists find the vetted and trusted tools they need to build reproducible open science workflows. We also empower our community with critical open science skills that support contributing to open source software.
+
+* [Community partnerships with domain-specific scientific Python communities](https://www.pyopensci.org/partners.html). Domain-specific communities partner with PyOpenSci to leverage pyOpenSci's peer review process as a way to track vetted, high quality tools. Communities also support the development of Python packaging packaging guidelines in an effort to streamline the development of packaging recommendations across the scientific Python ecosystem.
+
+* Training and resources to help scientists develop and maintain high-quality, accessible, open source software. Our community developed the [Python packaging guide](https://www.pyopensci.org/python-package-guide/), which provides resources and tutorials that help scientists navigate a complex Python packaging ecosystem. The Python packaging guide also makes recommendations for community accepted best practices.
+
+## Looking forward to 2024
+
+pyOpenSci is excited to grow a more inclusive and supportive scientific Python community in 2024!
+
+We are always looking for volunteers to support our community programs.
+If you are interested in getting involved with pyOpenSci, [learn more here](/get-involved-contact.html).
diff --git a/content/blog/2024-03-01-pyos-newsletter-march-2024.md b/content/blog/2024-03-01-pyos-newsletter-march-2024.md
new file mode 100644
index 00000000..8cd3207d
--- /dev/null
+++ b/content/blog/2024-03-01-pyos-newsletter-march-2024.md
@@ -0,0 +1,52 @@
+---
+title: 'pyOpenSci Newsletter: March 2024'
+date: '2024-03-01'
+type: blog
+excerpt: New partnerships, packages, and conference announcements!
+author: Jesse Mostipak
+blog_topic: updates
+toc: true
+comments: true
+url: "/blog/pyos-newsletter-march-2024.html"
+lastmod: '2024-08-29'
+---
+
+## <i class="fa-solid fa-rocket"></i> Welcome, AstroPy
+pyOpenSci has officially partnered with the [AstroPy Project](https://www.astropy.org/) through our [Community Partnership program](https://www.pyopensci.org/partners.html). AstroPy is a Community Python Library for Astronomy, and the AstroPy Project is a community effort to develop a single core package for Astronomy in Python, while also fostering interoperability between Python astronomy packages. We're thrilled to be partnering with the AstroPy project, and can't wait to share more!
+{{< figure src="images/newsletter/04-2024-newsletter/peer-review-partners-process.png" alt="Three sequential arrows, with the first reading 'submit your package', the second reading 'Review, pyOpenSci standards', and the third reading 'Accepted, pyOpenSci + Community Affiliated'. Below the arrows is a box beneath 'Review' that says 'Your Community Standards', with an input arrow reading 'Customized review'." caption="pyOpenSci adds an extra layer of community-specific review to our established open peer review process. This allows domain-specific scientific Python communities to vet affiliated tools through our robust peer review process. Communities then don't have to develop and maintain their own review processes and software guidelines." >}}
+
+## <i class="fa-regular fa-sun"></i> Hello, sunPy
+
+[sunPy](https://sunpy.org/), a Python package that provides fundamental tools for accessing, loading, and interacting with solar physics data in Python, has successfully gone through the pyOpenSci open peer review process, which is the first step in our budding partnership with the heliophysics community!
+
+You can read more about sunPy and pyOpenSci in [this lovely blog post](https://sunpy.org/posts/2024/2024-01-24-pyopensci.html) from Nabil Friej.
+
+## <i class="fa-regular fa-face-smile"></i> Say hi to sciform
+
+[Justin Gerber](https://github.com/jagerber48) has developed the [sciform package](https://sciform.readthedocs.io/en/stable/), which is used to convert Python numbers into strings according to a variety of user-selected scientific formatting options, was accepted into the pyOpenSci ecosystem! sciform, like all of the pyOpenSci packages, completed the [pyOpenSci open peer review process](https://www.pyopensci.org/about-peer-review/index.html). And the community support around getting the sciform package review-ready was amazing to see!
+
+Have a package you’ve developed, but aren’t sure it’s in scope for pyOpenSci? Complete a [pre-submission inquiry](https://github.com/pyOpenSci/software-submission/issues/new?assignees=&labels=presubmission&projects=&template=presubmission-inquiry.md&title=) and one of our editors will be in touch!
+
+## <i class="fa-solid fa-plane-departure"></i> We're going to [PyCon US](https://us.pycon.org/2024/)
+Will we see you there? Our Executive Director and Founder, [Leah Wasser](https://github.com/lwasser), had her talk. [Friends don't let friends package alone](https://us.pycon.org/2024/schedule/presentation/34/), all about Python packaging for scientists, accepted for this May's conference. We've seen a sneak peek of her talk, and guarantee that you won't want to miss it! Be sure to [register today](https://us.pycon.org/2024/)!
+
+## <i class="fa-regular fa-heart"></i> Congratulations, Leah!
+
+Leah Wasser also received a [Better Scientific Software (BSSw) fellowship](https://bssw.io/pages/bssw-fellowship-program) to create lessons around collaborative open science using GitHub. We plan to turn the lessons into online workshops. We'll be sure to let you know once they're ready for registration!
+
+[BSSw](https://bssw.io/) provides a central hub for the community to address pressing challenges in software productivity, quality, and sustainability.
+
+## <i class="fa-solid fa-chalkboard-user"></i> New lessons are LIVE!
+pyOpenSci released new and updated lessons in our [Python Packaging Guide](https://www.pyopensci.org/python-package-guide/tutorials/intro.html), designed to help scientists both make their Python code more shareable, as well as how to create a Python package. Be sure to check them out and let us know what you think!
+
+## <i class="fa-solid fa-atom"></i> Upcoming Python Events for Scientists
+### PyCon US 2024
+The [PyCon US 2024 Maintainers Summit Call for Proposals](https://us.pycon.org/2024/events/maintainers-summit/) is LIVE until March 25th! Share your insights and experiences on best practices, developing sustainable projects, and nurturing thriving communities in a 10--15 minute talk.
+
+### PyConDE & PyData Berlin
+Registration is still live for [PyConDE & PyData Berlin](https://2024.pycon.de/), so be sure to grab your tickets while they still last!
+
+The event is scheduled for April 22nd--24th, _**with Inessa Pawson delivering the keynote address,**_ titled, "The Art and Science of Tending Open Source Orchards".
+
+## <i class="fa-regular fa-paper-plane"></i> Get the pyOpenSci monthly newsletter delivered directly to your inbox!
+In addition to catching our newsletter on Fosstodon, LinkedIn, and the pyOpenSci website, you can also [sign up to have the newsletter delivered to your inbox every month](https://eepurl.com/iM7SOM)!
diff --git a/content/blog/2024-04-01-pyos-newsletter-april-2024.md b/content/blog/2024-04-01-pyos-newsletter-april-2024.md
new file mode 100644
index 00000000..b24b5327
--- /dev/null
+++ b/content/blog/2024-04-01-pyos-newsletter-april-2024.md
@@ -0,0 +1,60 @@
+---
+title: 'pyOpenSci Newsletter: April 2024'
+date: '2024-04-01'
+type: blog
+excerpt: New contributors, a new package, and a few new social campaigns, all to keep
+  you connected with the pyOpenSci community!
+author: Jesse Mostipak
+blog_topic: updates
+toc: true
+comments: true
+url: "/blog/pyos-newsletter-april-2024.html"
+lastmod: '2024-08-29'
+---
+
+## <i class="fa-solid fa-heart"></i> To 200 and beyond!
+
+This past month, pyOpenSci reached a major milestone: [200 contributors](https://www.pyopensci.org/our-community/index.html)! We have a diverse and vibrant community of Pythonistas, and are thrilled that 200 (and counting) wonderful people have contributed to pyOpenSci. Will you be next? [Learn more about getting involved](https://www.pyopensci.org/volunteer.html).
+
+
+## <i class="fa-solid fa-camera"></i> Launched: editor spotlight
+
+pyOpenSci editors are volunteers who fulfill a critical role within pyOpenSci. Editors lead the open peer review process for three to four Python packages a year, and also weigh in on group editorial decisions. With everything they do for pyOpenSci, we wanted to celebrate them! In March we kicked off our pyOpenSci editor spotlight, where every Wednesday we share a short interview with one of our editors. You can catch up with previous spotlights, and stay tuned for more, on both our [Fosstodon](https://fosstodon.org/@pyOpenSci) and [LinkedIn](https://www.linkedin.com/company/pyopensci) pages.
+
+## <i class="fa-solid fa-computer"></i> PyCon US 2024 Maintainers Summit
+
+We’ve been talking (a lot) about the [PyCon Maintainers Summit](https://us.pycon.org/2024/events/maintainers-summit/) (which is now full, but [you can sign up for the waitlist](https://us.pycon.org/2024/events/maintainers-summit/)), happening this May in Pittsburgh. The Maintainers Summit, included in your [PyCon registration](https://us.pycon.org/2024/), is where we come together to discuss and foster best practices on how to develop sustainable projects and nurture thriving communities. And thanks to [Mariatta Wijaya](https://mariatta.ca/), we’ve got an inside look into everything you can expect in [this incredible video](https://www.youtube.com/watch?v=L-Ok_89QJOM) featuring Kara Sowles, Inessa Pawson, and our Executive Director, Leah Wasser!
+
+<a href="https://www.youtube.com/watch?v=L-Ok_89QJOM" target="_blank">
+ <img src="/images/newsletter/04-2024-newsletter/ms-pycon-2024.png" alt="Watch the video" width="720" height="540" border="10" />
+</a>
+
+## <i class="fa-regular fa-map"></i> Welcome, EOmaps!
+{{< figure src="images/newsletter/04-2024-newsletter/eomapslogo.png" alt="The EOmaps logo, which spells out EOmaps in white letters on a black background. In place of the letter 'O' is a grey globe with white meridian lines, and a red arrow pointing to the globe." caption="Welcome to pyOpenSci, EOmaps!" >}}
+[EOmaps](https://eomaps.readthedocs.io/en/latest/) has joined the pyOpenSci ecosystem! Developed by [Raphael Quast](https://github.com/raphaelquast), EOmaps is built on top of matplotlib and cartopy and integrates well with the scientific python infrastructure (e.g., numpy, pandas, geopandas, xarray etc.), allowing you to visualize point-, raster- or vector-datasets provided in almost any format you can imagine, no matter if you're dealing with just a few unsorted data points or multi-dimensional stacks of global high-resolution datasets.
+
+Learn more about pyOpenSci’s open peer review process by reading through the [EOmaps submission](https://github.com/pyOpenSci/software-submission/issues/138) or checking out our [peer review page](https://www.pyopensci.org/about-peer-review/).
+
+## <i class="fa-solid fa-rocket"></i> Launched: pyOpenSci package showcase
+
+pyOpenSci currently has [28 packages](https://www.pyopensci.org/python-packages.html) that have been accepted through our open peer review process, and we want you to get to know them better! This is why we’ve launched our pyOpenSci package showcase, which highlights an accepted package and its author(s) every Tuesday and Thursday on our [Fosstodon](https://fosstodon.org/@pyOpenSci) and [LinkedIn](https://www.linkedin.com/company/pyopensci) pages.
+
+Have a package you’ve developed, but aren’t sure it’s in scope for pyOpenSci? Complete a [pre-submission inquiry](https://github.com/pyOpenSci/software-submission/issues/new?assignees=&labels=presubmission&projects=&template=presubmission-inquiry.md&title=) and one of our editors will be in touch!
+
+## <i class="fa-brands fa-python"></i> Upcoming Python Events for Scientists
+### PyConDE & PyData Berlin
+Online tickets are still available for [PyConDE & PyData Berlin](https://2024.pycon.de/), so be sure to grab them while they still last! The event is scheduled for April 22nd-24th, **with [Inessa Pawson](https://github.com/InessaPawson) delivering the keynote, titled “The Art and Science of Tending Open Source Orchards”**. You definitely don’t want to miss out!
+
+### PyCon US 2024
+[Registration is still open](https://us.pycon.org/2024/) for [PyCon US 2024](https://us.pycon.org/2024/), happening May 15th–23rd in Pittsburgh, PA. There’s also an online component for folks who can’t be there in person. It’s shaping up to be a stacked event, and you can view the schedule [here](https://us.pycon.org/2024/schedule/).
+
+### GeoPython
+Registration is live for [GeoPython](https://geo-python-site.readthedocs.io/en/2024.0/), THE event for Python- and Geo-Enthusiasts. There are online and in-person options, and the event is scheduled for May 27th–29th in Basel, Switzerland.
+
+### SciPy–early bird ends soon!
+Happening July 8th–14th in Tacoma, WA, [SciPy registration is live](https://www.scipy2024.scipy.org/), and you can grab your early bird tickets until April 30th.
+
+Have an upcoming scientific Python event that’s open to the public? Email us at [media@pyopensci.org](mailto:media@pyopensci.org) with the details to have your event listed.
+
+## <i class="fa-regular fa-paper-plane"></i> Get the pyOpenSci monthly newsletter delivered directly to your inbox!
+In addition to catching our newsletter on Fosstodon, LinkedIn, and the pyOpenSci website, you can also [sign up to have the newsletter delivered to your inbox every month](https://eepurl.com/iM7SOM)!
diff --git a/content/blog/2024-04-16-pyos-open-education-resources-announcement.md b/content/blog/2024-04-16-pyos-open-education-resources-announcement.md
new file mode 100644
index 00000000..824f5474
--- /dev/null
+++ b/content/blog/2024-04-16-pyos-open-education-resources-announcement.md
@@ -0,0 +1,69 @@
+---
+title: pyOpenSci launches open, accessible, online educational trainings for scientists
+date: '2024-04-16'
+type: blog
+excerpt: We're excited to share information about the pyOpenSci approach to education,
+  open education resources, and announce an upcoming workshop focused on Python packaging
+author: Jesse Mostipak
+blog_topic: learn
+toc: true
+comments: true
+url: "/blog/pyos-education-announcement.html"
+lastmod: '2024-08-29'
+---
+
+## The three petals of pyOpenSci
+{{< figure src="images/pyopensci-pillars-flower.png" alt="The three petals of pyOpenSci, a purple flower with a center and three petals. The center reads 'Diverse, Inclusive Community' while the petals, from left to right, read 'Software Peer Review', 'Community Partnerships', 'Community Driven Training & Open Education'." caption="The three petals of pyOpenSci" >}}
+pyOpenSci was founded with the mission to build diverse community that supports free and open Python tools for processing scientific data. We also build the technical skills needed to contribute to open source and that support open science. While a diverse, inclusive community is at our core, radiating out from it are the three petals–how we accomplish our community goals–of pyOpenSci. Those are: open peer review, community partnerships, and training and open educational resources.
+
+### Peer review
+The pyOpenSci open peer review process facilitates scientists getting credit and recognition for the work they’ve invested in developing scientific Python tools. The peer review process also supports scientists in finding vetted and maintained software, which drives their open science workflows.
+
+Software peer review, similar to the review of scientific papers, is a process where scientists vet software code, documentation and infrastructure. pyOpenSci leads an [open peer review process](https://www.pyopensci.org/software-peer-review/our-process/how-review-works.html) run by a community of dedicated volunteers. Reviews are supportive and fully transparent with the shared goal of improving the quality, usability and maintainability of the software that is driving open science.
+
+[Learn more about the peer review timeline and roles.](https://www.pyopensci.org/software-peer-review/our-process/review-timeline.html)
+
+### Community partnerships
+pyOpenSci adds an [extra layer of community-specific review](https://www.pyopensci.org/software-peer-review/partners/scientific-communities.html) to our established open peer review process. This allows domain-specific scientific Python communities to vet affiliated tools through our robust peer review process. Communities then don’t have to develop and maintain their own review processes and software guidelines.
+
+Our catalog of vetted open source tools makes it easier for scientists to find the trusted tools that they need to develop their open science workflows.
+
+[View our growing list of accepted scientific Python packages.](https://www.pyopensci.org/python-packages.html)
+
+### Education
+pyOpenSci creates resources to help you navigate the Python packaging ecosystem with ease. Our materials are community-developed and go through extensive technical and pedagogical review. Keep reading to learn more about our approach to education!
+
+## pyOpenSci believes in open education resources (OER)
+  {{< figure src="images/learn-graphics/community-created.png" alt="Multiple hands of various skin tones reaching up to a speech bubble that reads 'Community Developed'." caption="pyOpenSci's open education resources are community-developed" >}}
+When pyOpenSci publishes community-developed Python tutorials for scientists, it goes through a rigorous process of review and evaluation. ​​All of our tutorials are created through a multi-stage community review process–where tutorials are first developed by the pyOpenSci team or community members–before being  reviewed by tool maintainers to ensure ideas and concepts are accurate. Tutorials then go through several rounds of community review for accuracy, usability and accessibility before being published as part of pyOpenSci’s open education resources..
+
+All of our written content is available on the [Learn section of our website](https://www.pyopensci.org/learn.html), where you’ll find resources such as our [Python Packaging Tutorial](https://www.pyopensci.org/python-package-guide/tutorials/intro.html#), as well as in-depth guides on [Python packaging](https://www.pyopensci.org/python-package-guide/package-structure-code/intro.html), [documentation](https://www.pyopensci.org/python-package-guide/documentation/index.html), and [testing](https://www.pyopensci.org/python-package-guide/tests/index.html).
+
+### Free, online, asynchronous training
+
+{{< figure src="images/learn-graphics/github-collaboration.png" alt="A woman and a man sitting across from each other at a high table. They are smiling and working on their laptops. The text reads 'Essential Collaboration Skills for Scientists'." caption="Essential Collaboration Skills for Scientists is just one of the many free, online trainings we're excited to develop and deliver!" >}}
+
+Our vision for our free, online trainings is for the curriculum to be added to our library of open education resources, making them free, accessible, and published for anyone to use. And we intend to experiment with delivering this curriculum in an asynchronous, cohort-based manner that allows learners from all over the world to come together for a period of time to work through the curriculum together. If you were part of one of the original cohorts of the <a href="https://dslc.io/">R for Data Science Online Learning Community</a> created by our Community Manager, [Jesse Mostipak](https://github.com/kierisi), then you know that these asynchronous trainings will be thoughtfully crafted, a fantastic learning experience, and a ton of fun!
+
+pyOpenSci is the recipient of the [Better Software for Science Fellowship](https://bssw.io/fellows/leah-wasser), which will help fund the creation of these open educational resources.
+
+These asynchronous trainings will be free, online, and center around community building and collaborative learning with larger cohort sizes. Part of the intention of these trainings is to foster a vibrant learning community where participants are empowered to learn from one another.
+
+### Paid, online, real-time training
+pyOpenSci is also developing paid trainings that will be offered online to a smaller cohort of learners, using a customized curriculum. While these will be online, we guarantee they won’t be your typical Zoom workshop! For us, it’s all about conversation, collaborative learning, and engagement. These instructor-led workshops will have a high instructor to student ratio to ensure that all participants receive personalized feedback and guidance on the workshop material. Although these will be paid trainings, we hope to offer scholarships where feasible.
+
+## Enroll in pyOpenSci’s upcoming workshop: From Python Code to Module
+{{< figure src="images/blog/2024/april/pyos-code-to-mod.png" alt="A line art robot standing in a field of purple flowers. The text reads 'From Python Code to Module, a live, online workshop with pyOpenSci, Thursday, April 25th 2024'." caption="Tickets for our 'From Python Code to Module' workshop are selling fast - get yours today!" >}}
+If you’re interested in participating in our first paid, online, real-time training, sign up for our upcoming workshop: [“From Python Code to Module”](https://www.eventbrite.com/e/879586546037?aff=oddtdtcreator). This three hour course is intended for individuals who have experience writing Python code and Python functions, and will be taught by pyOpenSci’s Executive Director and founder, [Leah Wasser](https://github.com/lwasser). Leah has over 20 years of experience teaching data-intensive science with an emphasis helping scientists work through the pain points of working with different types of data, and puts an incredible amount of care and attention into ensuring each learner is successful in their educational goals. This is definitely a workshop you don’t want to miss!
+
+In this workshop, Leah will cover:
+- How to identify and explain the use of the basic components of a Python package: (a specific directory structure, an __init__.py file, a pyroject.toml file and some code).
+- Creating a basic python package that allows you to install your code into a local Python environment.
+- Installing your package in editable mode into a Python environment.
+
+She will also briefly discuss how LLM’s can be used to support tasks such as documenting and formatting your code to improve usability and maintainability. While also considering the ethical and logistical challenges, pitfalls and concerns associated with using AI-based tools in software development.
+
+The course will take place on Thursday, April 25th, from 10AM–1PM Mountain time, and use the Spatial Chat platform. Tickets are $10, and can be purchased on [the workshop’s Eventbrite page](https://www.eventbrite.com/e/from-python-code-to-module-tickets-879586546037?aff=oddtdtcreator). The class size is capped at 35, and tickets are selling fast–we hope to see you there!
+
+## Connect with us!
+You can stay up-to-date with all things pyOpenSci by following us on [LinkedIn](https://www.linkedin.com/company/pyopensci) and [Fosstodon](https://fosstodon.org/@pyOpenSci).
diff --git a/content/blog/2024-04-18-rdata-read-r-datasets.md b/content/blog/2024-04-18-rdata-read-r-datasets.md
new file mode 100644
index 00000000..59956166
--- /dev/null
+++ b/content/blog/2024-04-18-rdata-read-r-datasets.md
@@ -0,0 +1,127 @@
+---
+title: 'rdata: Read R datasets from Python'
+date: '2024-04-18'
+type: blog
+excerpt: rdata is a library for reading R datasets and converting them to Python objects
+  that was recently accepted into the pyOpenSci ecosystem. Learn more about rdata.
+author: Carlos Ramos Carreño
+blog_topic: software
+comments: true
+url: "/blog/read-r-datasets-from-python.html"
+lastmod: '2024-08-29'
+image:
+  src: images/blog/headers/pandas.png
+  alt: 'rdata: Read R datasets from Python'
+---
+
+In the last years Python has solidified itself as the main language for data science and machine learning.
+However, the R programming language is also a widely used language in statistics, offering thousands of specialized software packages in this field.
+As it is common in the R community, many of these packages include accompanying data, often stored as R objects in the .rds and .rda formats.
+
+This variety of datasets is normally inaccessible directly from Python programs.
+Instead, programmers typically have to open the data in R and manually convert it to another format, such as CSV, which can be understood by Python libraries.
+This process requires an R interpreter, it is not fast, nor easy, and may even be impossible to do without information loss.
+In particular, for nested structures and complex or custom R types there is no common file exchange format for Python and R that can be used to this purpose.
+
+The Python package [rdata](https://rdata.readthedocs.io) allows Python programmers to read R datasets in the .rds and .rda formats directly, facilitating the sharing of examples and results between the two languages.
+It is a small, pure Python solution that does not require an R interpreter to work, nor external libraries in other languages.
+This makes it suitable to be used in most contexts where Python can be found, including the web using Pyodide.
+The package rdata has been accepted by pyOpenSci as part of its ecosystem in March 2024.
+
+# A library for reading R datasets
+
+To illustrate rdata capabilities, lets take the role of a Python developer implementing new statistical techniques.
+In order to compare her results with prior approaches, she needs to use the same data as them.
+Unfortunately for her, the people who implemented the original techniques do not have the data in a format directly readable by Python, as they were all statisticians using the R programming language.
+They are eager to share their data with her, in the form of a .rda file called `dataset.rda`.
+
+A cursory inspection of the file in R shows the following:
+
+![Data: frame (10 obs. of 3 variables), Values: (freq (1200), model ("NovTech200"))]({{ site.url }}/images/rdata/dataset.png "The contents of `dataset.rda`")
+
+The dataset contains 3 variables, of which just one is a dataframe.
+Moreover the dataframe contains a column with instances of a custom R class, and a boolean column with some NA values.
+Thus, converting this data to a format such as CSV to read it in Python would be a difficult endeavor.
+Luckily, this Python programmer has heard of the rdata Python package, which could be useful to solve this task.
+
+Our programmer quickly installs rdata with pip or conda, and executes the following command in the Python interpreter:
+
+```python
+dataset = rdata.read_rda("dataset.rda")
+```
+
+This loads the file into a Python dictionary that she can now explore.
+She now starts by checking the "model" and "freq" variables:
+
+```python
+>>> dataset["model"]
+array(['NovTech200'], dtype='<U10')
+
+>>> dataset["freq"]
+array([1200.])
+```
+
+The original R vectors have been now converted to equivalent NumPy objects with their corresponding dtype.
+Then, she checks the default conversion of the dataframe itself:
+```python
+>>> dataset["frame"]
+    level                                            subject  control
+1       8  namespace(name=array(['Louis'], dtype='<U5'), ...    False
+2       4  namespace(name=array(['Martin'], dtype='<U6'),...     <NA>
+3       6  namespace(name=array(['Miriam'], dtype='<U6'),...     True
+4       3  namespace(name=array(['Yoshi'], dtype='<U5'), ...    False
+5       9  namespace(name=array(['John'], dtype='<U4'), a...     True
+6       2  namespace(name=array(['Karl'], dtype='<U4'), a...    False
+7       7  namespace(name=array(['Eusebio'], dtype='<U7')...    False
+8      10  namespace(name=array(['Rosa'], dtype='<U4'), a...    False
+9       1  namespace(name=array(['Lilly'], dtype='<U5'), ...     <NA>
+10      5  namespace(name=array(['Mark'], dtype='<U4'), a...     <NA>
+```
+
+## Support for custom classes
+
+The dataframe has been converted by default to a Pandas dataframe, and the NA have been preserved.
+However, there is a problem with the subject column: as it contains instances of a custom R class, the default conversion did not know to which class it should be mapped in Python, returning a `SimpleNamespace` instead.
+
+Our programmer has developed a Python class, `Person`, which she plans to use in her code.
+Instead of modifying the dataframe to manually convert the instances, she uses the following code to load the data applying the desired transformations:
+
+```python
+def person_constructor(obj, attrs):
+	return Person(name=str(obj.name[0]), age=int(obj.age[0]))
+
+constructor_dict = {
+    **rdata.conversion.DEFAULT_CLASS_MAP,
+    "Person": person_constructor,
+}
+
+dataset = rdata.read_rda(
+    "dataset.rda",
+    constructor_dict=constructor_dict,
+)
+```
+
+This code defines a "constructor" of a Python object and assigns it to a dictionary of constructors, using "Person" as the key.
+During the R to Python conversion process, whenever an object is found with a class attribute of "Person", the constructor function will be called with the partially converted object and its attributes, and the return value will be used as the converted value of that object.
+The mapping `rdata.conversion.DEFAULT_CLASS_MAP` contains a default set of constructors, including the one for converting R dataframes into Pandas dataframes.
+Now, showing the dataset again, we can verify that every instance of the original custom class has been replaced with its Python counterpart:
+
+```python
+>>> dataset["frame"]
+    level                         subject  control
+1       8    Person(name='Louis', age=57)    False
+2       4   Person(name='Martin', age=22)     <NA>
+3       6   Person(name='Miriam', age=41)     True
+4       3    Person(name='Yoshi', age=29)    False
+5       9     Person(name='John', age=63)     True
+6       2     Person(name='Karl', age=34)    False
+7       7  Person(name='Eusebio', age=77)    False
+8      10     Person(name='Rosa', age=33)    False
+9       1    Person(name='Lilly', age=28)     <NA>
+10      5     Person(name='Mark', age=30)     <NA>
+```
+
+## What's next?
+
+rdata is under active development, and new functionalities will be added as users need them.
+Contributions are welcome in the [Github repository](https://github.com/vnmabus/rdata)!
diff --git a/content/blog/2024-04-29-pyos-newsletter-may-2024.md b/content/blog/2024-04-29-pyos-newsletter-may-2024.md
new file mode 100644
index 00000000..a339b7d1
--- /dev/null
+++ b/content/blog/2024-04-29-pyos-newsletter-may-2024.md
@@ -0,0 +1,89 @@
+---
+title: 'pyOpenSci Newsletter: May 2024'
+date: '2024-04-29'
+type: blog
+excerpt: May has brought two new packages, the first (of many!) pyOpenSci workshops,
+  all things pyOpenSci and PyCon, and several incredible speaking opportunities. Read
+  on to learn more!
+author: Jesse Mostipak
+blog_topic: updates
+toc: true
+comments: true
+url: "/blog/pyos-newsletter-may-2024.html"
+lastmod: '2024-08-29'
+---
+
+## <i class="fa-solid fa-seedling"></i> Spring is in the Air
+For those of us in the Northern Hemisphere, spring seems to have finally sprung. It’s a lovely time of year, filled with growth, opportunity, and new beginnings. And for all of us here in the pyOpenSci it’s brought new packages, new opportunities, and new projects that we can’t wait to share with you!
+
+## <i class="fa-solid fa-chalkboard-user"></i> pyOpenSci’s first workshop was a success!
+{{< figure src="images/blog/2024/may/april-workshop.png" alt="Purple line art of a robot standing in a field of solid purple flowers. The text reads 'Build Your First Python Package! a live, online workshop with pyOpenSci. Thursday, April 25th, 2024." caption="Thank you to everyone who made our first workshop such a fun experience!" >}}
+On Thursday, April 25th, pyOpenSci held its first-ever workshop, titled: [Build Your First Python Package!](https://www.eventbrite.com/e/build-your-first-python-package-tickets-879586546037). With eight countries represented, we had 28 learners create and install their first Python package using [Hatch](https://hatch.pypa.io/latest/), all in the course of three hours.
+
+This workshop was the first of many online educational events that we plan on hosting, and was a great opportunity for us to put [our educational philosophy](https://www.pyopensci.org/blog/pyos-education-announcement.html) into practice. All of the pyOpenSci educational materials are community-developed and go through extensive technical and pedagogical review. While the workshop will *not* be available as a recording, the written content is available on the [Learn section of our website](https://www.pyopensci.org/learn.html), where you’ll find resources such as our [Python Packaging Tutorial](https://www.pyopensci.org/python-package-guide/tutorials/intro.html#), as well as in-depth guides on [Python packaging](https://www.pyopensci.org/python-package-guide/package-structure-code/intro.html), [documentation](https://www.pyopensci.org/python-package-guide/documentation/index.html), and [testing](https://www.pyopensci.org/python-package-guide/tests/index.html).
+
+## <i class="fa-solid fa-table"></i> Hello, rdata!
+[rdata](https://rdata.readthedocs.io/en/latest/), a Python package that offers a lightweight way to import R datasets/objects stored in the `.rda` and `.rds` formats into Python, has been accepted into [the pyOpenSci ecosystem](https://www.pyopensci.org/python-packages.html). Created by [Carlos Ramos Carreño](https://github.com/vnmabus), rdata has several key advantages:
+
+* rdata is a pure Python implementation, with no dependencies on the R language or related libraries. Thus, it can be used anywhere where Python is supported, including the web using [Pyodide](https://pyodide.org/en/stable/).
+* rdata attempts to support all R objects that can be meaningfully translated. As opposed to other solutions, you are not limited to import dataframes or data with a particular structure.
+* rdata allows users to easily customize the conversion of R classes to Python ones. Does your data use custom R classes? Worry no longer, as it is possible to define custom conversions to the Python classes of your choosing.
+* rdata has a permissive license (MIT). As opposed to other packages that depend on R libraries and thus need to adhere to the GPL license, you can use rdata as a dependency on MIT, BSD or even closed source projects.
+
+If you’d like to learn more about rdata, we recommend [this guest blog post](https://www.pyopensci.org/blog/read-r-datasets-from-python.html) from Carlos!
+
+### Write a guest blog post for pyOpenSci
+Interested in writing a guest blog post for pyOpenSci? Reach out to [media@pyopensci.org](mailto:media@pyopensci.org) to get started! We’re always looking for volunteers to write about all things open source and open science, whether that’s a package you’ve created or something new you’ve learned in Python, or anything in between!
+
+## <i class="fa-regular fa-handshake"></i> Welcome, ZodiPy
+{{< figure src="images/blog/2024/may/zodipy.png" alt="Screenshot of the ZodiPy GitHub repository, showing the ZodiPy logo and simulated data output." caption="Welcome, ZodiPy! We're so happy you're here." >}}
+
+[ZodiPy](https://github.com/Cosmoglobe/zodipy) is an open source, [Astropy affiliated](https://www.astropy.org/affiliated/), Python tool for simulating the zodiacal emission that a solar system observer is predicted to see given an interplanetary dust model. ZodiPy attempts to make zodiacal emission simulations more accessible by providing the community with a simple interface to existing models, and is also a new member of the pyOpenSci community!
+
+## <i class="fa-solid fa-bolt"></i> pyOpenSci will be at PyCon 2024!
+Not only will be *be* at PyCon US 2024, we've got a lot going on while we're there, and we want you to be a part of it! This year's PyCon US will be held in Pittsburgh, PA, from May 15th - May 23rd.
+
+### pyOpenSci at the PyCon Maintainers Summit
+The [PyCon Maintainers Summit](https://us.pycon.org/2024/events/maintainers-summit/) is where the Python community comes together to discuss and foster best practices on how to develop sustainable projects and nurture thriving communities. Organized by Inessa Pawson (NumPy, Albus Code, OpenTeams), Chris Rose (PyHamcrest, GitHub), Kara Sowles (GitHub), and Leah Wasser (pyOpenSci), the Summit is a must-attend event, where you can hear talks from two pyOpenSci community members:
+
+* [Carol Willing](https://github.com/willingc) (pyOpenSci Advisory Council) will be giving a talk titled: Team Compass: Setting a course for a dynamic project.
+* [Tracy Teal](https://github.com/tracykteal) (pyOpenSci Board Chair) will be giving a talk titled: Documentation: how you can build it so they will come
+
+### Leah's PyCon Packaging Talk
+On Saturday, May 18th, pyOpenSci's Executive Director and Founder, Leah Wasser, will be giving a talk titled ["Friends Don't Let Friends Package Alone"](https://us.pycon.org/2024/schedule/presentation/34/). As she helps us see how packaging doesn't have to be a thorny topic, she'll also share:
+* Why consensus-building and user-focused content development is critical for tackling thorny topics such as packaging.
+* How to decide which packaging tools satisfy your packaging needs.
+* Where to find more information and support around packaging.
+
+### pyOpenSci-led sprints at PyCon
+[PyCon US Development Sprints](https://us.pycon.org/2024/events/dev-sprints/) are four days of intensive learning and development on an open source project of your choice, in a team environment. It's a time to come together with colleagues, old and new, to share what you've learned and apply it to an open source project. Leah will be running a pyOpenSci sprint on Monday, May 20th, and would love to see you there! pyOpenSci is committed to diversity and inclusion, and Pythonistas of all backgrounds and skill levels are invited to participate.
+
+### Get your pyOpenSci swag at PyCon
+We saved the best for last, because we know everyone loves swag! We'll have a fresh batch of stickers and postcards that we want to put in your hands, so be sure to find Leah to say hello and learn more about all things pyOpenSci. Not sure where to find Leah? If you can't make it to her talk, sprints, or the Maintainers Summit, [follow her on Fosstodon](https://fosstodon.org/@leahawasser), and keep an eye on [the pyOpenSci Fosstodon account](https://fosstodon.org/@pyOpenSci) as well!
+
+## <i class="fa-regular fa-message"></i> Listen to Leah at SciPy
+We’ve received the exciting news that our Executive Director and Founder, [Leah Wasser](https://github.com/lwasser), will be speaking as well as running a Python packaging workshop at [SciPy](https://www.scipy2024.scipy.org/) this year! We’ll be sharing more about Leah’s work as the conference gets closer, but consider this your reminder to grab your tickets!
+
+## <i class="fa-solid fa-apple-whole"></i> Congratulations on an amazing keynote, Inessa!
+<iframe width="560" height="315" src="https://www.youtube.com/embed/5Bjo6pWj-88?si=fUu5zYPrVCgmPEZF&amp;start=711" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
+
+If you weren’t able to attend PyConDE & PyData Berlin 2024 to hear [Inessa Pawson’s](https://github.com/InessaPawson) keynote, [Tending Open Source Orchards](https://2024.pycon.de/program/7TEYDQ/), never fear! You can [watch her phenomenal talk,](https://www.youtube.com/live/5Bjo6pWj-88?feature=shared&t=711) where she dives into the resilient contributor communities behind every large open source project, and shares her insights on the art and science of fostering resilient open source communities.
+
+## <i class="fa-brands fa-python"></i> Upcoming Python events for scientists
+### PyCon US
+[Registration is still open](https://us.pycon.org/2024/) for [PyCon US 2024](https://us.pycon.org/2024/), happening May 15th–23rd in Pittsburgh, PA. There’s also an online component for folks who can’t be there in person. It’s shaping up to be a stacked event, and you can [view the schedule here](https://us.pycon.org/2024/schedule/).
+
+### PyCon Italia
+Fancy a trip to Florence? Then grab your tickets for PyCon Italia! The conference runs Wednesday, May 22nd through Saturday, May 25th, and has a stacked list of [keynote speakers](https://2024.pycon.it/en/schedule/2024-05-22?view=grid).
+
+### PyData London
+Happening June 14–16, [PyData London](https://pydata.org/london2024/) tickets are available now! With tutorials on Friday, June 14th, and talks Saturday and Sunday, this is shaping up to be a phenomenal event for the international community of data scientists, data engineers, and developers of data analysis tools to share ideas and learn from each other.
+
+### SciPy
+Happening July 8th–14th in Tacoma, WA, [SciPy](https://www.scipy2024.scipy.org/) registration is live! Early bird pricing has ended, but it’s not too late to grab a standard ticket.
+
+### Tell us about your event!
+Have an upcoming scientific Python event that’s open to the public? Email us at [media@pyopensci.org](mailto:media@pyopensci.org) with the details to have your event listed.
+
+## <i class="fa-regular fa-paper-plane"></i> Connect with us
+Stay up-to-date with all things pyOpenSci by following us on [LinkedIn](https://www.linkedin.com/company/pyopensci) and [Fosstodon](https://fosstodon.org/@pyOpenSci). And if you’re interested in our weekly newsletter where we share news, blog posts, and monthly updates, [subscribe on LinkedIn](https://www.linkedin.com/build-relation/newsletter-follow?entityUrn=7179551305344933888). We also send out a monthly recap newsletter to [our mailing list](https://eepurl.com/iM7SOM)!
diff --git a/content/blog/2024-05-14-pyos-guide-to-pyconus-2024.md b/content/blog/2024-05-14-pyos-guide-to-pyconus-2024.md
new file mode 100644
index 00000000..8f8fa8e6
--- /dev/null
+++ b/content/blog/2024-05-14-pyos-guide-to-pyconus-2024.md
@@ -0,0 +1,95 @@
+---
+title: The pyOpenSci Guide to PyCon 2024
+date: '2024-05-14'
+type: blog
+excerpt: PyCon US 2024 is finally here, and we can't wait to connect with you! This
+  post has all of the talks, panels, summits, and keynotes where pyOpenSci community
+  members (and friends!) will be speaking.
+author: Jesse Mostipak
+blog_topic: learn
+toc: true
+comments: true
+url: "/blog/pyos-guide-to-pyconus-2024.html"
+lastmod: '2024-08-29'
+image:
+  src: images/blog/2024/may/pycon-us-2024.png
+  alt: The pyOpenSci Guide to PyCon 2024
+---
+
+## <i class="fa-solid fa-heart"></i> Connect with the pyOpenSci community at PyCon US 2024!
+We know there are a million things to do and see while at [PyCon US 2024](https://us.pycon.org/2024/) in beautiful Pittsburgh this weekend, so we wanted to compile a list of every talk, keynote, summit, and panel where you can expect to meet some of the fantastic pyOpenSci community members as well as hear from some friends of pyOpenSci!
+
+## <i class="fa-regular fa-calendar"></i> Friday, May 17th
+### <i class="fa-solid fa-users-between-lines"></i> 11:00--4:30 PM: Maintainers Summit
+*Room 402, David L. Lawrence Convention Center*\
+The [Maintainers Summit](https://us.pycon.org/2024/events/maintainers-summit/), organized by [Inessa Pawson](https://github.com/InessaPawson), [Chris Rose](https://github.com/offbyone), [Kara Sowles](https://github.com/karasowles), and [Leah Wasser](https://github.com/lwasser), is where the Python community comes together to discuss and foster best practices on how to develop sustainable projects and nurture thriving communities. Check out the video below about what to expect at this year's Maintainers Summit produced by PyCon US 2024 Conference Chair [Mariatta Wijaya](https://github.com/readme/stories/mariatta-wijaya):
+
+<a href="https://www.youtube.com/watch?v=L-Ok_89QJOM" target="_blank">
+ <img src="/images/newsletter/04-2024-newsletter/ms-pycon-2024.png" alt="Watch the video" width="720" height="540" border="10" />
+</a>
+
+Be sure you're at the Maintainers Summit not only for the opening remarks at 11:00 AM, but also so that you don't miss [Carol Willing's](https://github.com/willingc) 11:15 AM talk: Team Compass: Setting a course for a dynamic project!
+
+### <i class="fa-solid fa-comment"></i> 11:45--12:15 PM: Making Beautiful, Publication Quality Tables in Python is Possible in 2024
+*Ballroom BC*\
+**[Rich Iannone](https://github.com/rich-iannone) & [Michael Chow](https://github.com/machow)**\
+We couldn't agree more with Rich and Michael when they say that "The display of tables can be beautiful. Tables can convey information effectively, just as plots do and, sometimes, it’s the better way to present data. Truly, the time has come to bridge the divide between raw DataFrame output and wondrously-structured tables suitable for publication." In this talk they'll go over which table components make for effective displays of information, and which combinations of Python packages that fit together to make this important task possible.
+
+### <i class="fa-solid fa-comment"></i> 1:45--2:30 PM: Modern binary build systems
+*Ballroom A*\
+**[Henry Fredrick Schreiner III](https://github.com/henryiii)**\
+Henry will be guiding attendees through how easy it is now to set up a binary extension using CMake, Meson, or Maturin (Rust only). It can be done with only three files each containing only a handful of lines of code. Unlike the previous solutions, this covers cross-compilation,multithreaded builds, modern C++ standards, and other features that would each require custom code in a classic setup.py. Combined with cibuildwheel for building wheels and good support from modern binding tools like pybind11 and nanobind, the barrier for entry to reliable compiled extensions has dropped dramatically.
+
+### <i class="fa-solid fa-comment"></i> 2:45--3:15 PM: Hatch: The only tool you need
+*Ballroom A*\
+**[Ofek Lev](https://github.com/ofek)**\
+It's no secret that we're big fans of Hatch---we even [taught a Python Packaging Workshop](https://www.pyopensci.org/blog/pyos-education-announcement.html) using [Hatch](https://hatch.pypa.io/latest/)! With an ever-growing set of tools used in Python packaging, Ofek will be presenting on how Hatch can be used as a unifying tool for Python packaging.
+
+## <i class="fa-regular fa-calendar"></i> Saturday, May 18th
+### <i class="fa-solid fa-people-group"></i> 9:00--9:25 AM: Diversity & Inclusion Panel
+*Expo Hall B*\
+Diversity and inclusion is core to the pyOpenSci mission, and we can't wait for this panel. The line-up is incredible, with [Débora Azevedo](https://github.com/deboraazevedo), [Dima Dinama](https://github.com/dmaharika), [Jessica Greene](https://github.com/sleepypioneer), Jules, [Mason Egger](https://github.com/MasonEgger), and [Abigail Dogbe](https://github.com/mesrenyamedogbe) all speaking. We know we'll be walking away from this panel inspired!
+
+### <i class="fa-solid fa-comment"></i> 10:30--11:00 AM: Friends don't let friends package alone
+*Hall C*\
+**[Leah Wasser](https://github.com/lwasser)**
+{{< figure src="images/python-packaging/lion-meme-pyopensci.jpeg" alt="A puma leaning against a rock and flexing a front arm. Overlaid on the photo in meme text is the phrase 'so you want to talk about Python packaging.'" >}}
+We couldn't talk about PyCon US without talking about our Executive Director and Founder, Leah Wasser, who will be talking all things Python packaging! Python packaging can be a scary and confusing endeavor. The ecosystem can be thorny and filled with many decisions around which tool or approach to use. You’re also likely to get pricked by an approach or tutorial that doesn't work as expected. However, the packaging journey doesn’t have to be prickly - particularly for pure Python packages. By building community consensus around user goals and moderating healthy discussion, pyOpenSci is paving a smooth, thorn-free path for successful packaging.
+
+### <i class="fa-solid fa-users-between-lines"></i> 1:45--5:45 PM: Packaging Summit
+*David L. Lawrence Convention Center*\
+The goal of the [Packaging Summit](https://us.pycon.org/2024/events/packaging-summit/) is to try to take advantage of the fact that, at PyCon, we can get a high concentration of these stakeholders in one room at the same time. This allows us to sync up on current and future best practices and to quickly come to agreements that would take months or even years over higher-latency media of discussion (e.g. mailing lists, forums, issue tickets).
+
+### <i class="fa-solid fa-comment"></i> 2:30--3:00 PM: NetworkX is Fast Now: Graph Analytics Unleashed
+*Hall C*\
+**[Mridul Seth](https://github.com/MridulS) & [Erik Welch](https://github.com/eriknw)**\
+Have you ever wondered how to find connections in your data and to gain insights from them? Come discover how NetworkX makes this easy (and fast!).
+
+This talk is broadly divided into two parts. First we will talk about the power of graph analytics and how you can use tools like NetworkX to extract information from your data, and then we will talk about how we made the machinery behind NetworkX work with heterogeneous backends like GraphBLAS (CPU optimized) and cuGraph (GPU optimized).
+
+### <i class="fa-solid fa-comment"></i> 2:30--3:00 PM: Eternal sunshine of the spotless development environment
+*Room 301--305*\
+**[Sarah Kaiser](https://github.com/crazy4pi314)**\
+In this talk, Sarah will briefly cover why setting up container infrastructure, which can be useful for isolating your project environments and dig into how you can extend that with Dev Containers to configure a complete development experience using VS Code. She'll also look at two common OSS project situations, onboarding and workshops, to see how workflows for using Dev Containers and other supporting tools make things easier. No container experience required, and while a brief familiarity with VS Code is helpful, it's not necessary.
+
+## <i class="fa-regular fa-calendar"></i> Sunday, May 19th
+### <i class="fa-solid fa-users-between-lines"></i> 10:00--3:15 PM: Documentation Summit
+The [Documentation Summit](https://us.pycon.org/2024/events/hatchery/docs-summit/) will be a full-day summit including talks and panel sessions inviting leaders in documentation to share their experience in how to make good documentation, discussion about documentation tools such as sphinx, mkdocs, themes etc, what are the common mistakes and how to avoid them.
+
+And at 1:00 PM you can catch [Carol Willing](https://github.com/willingc) and [Ned Batchelder](https://github.com/nedbat) giving an update from the Python Docs Editorial Board!
+
+### <i class="fa-solid fa-key"></i> 3:15--4:00 PM: Keynote
+*Expo Hall B*\
+**[Sumana Harihareswara](https://github.com/brainwane)**\
+[Sumana Harihareswara](https://www.harihareswara.net/) is an open source contributor and leader who has managed work on pip, PyPI, GNOME, MediaWiki, HTTPS Everywhere, autoconf, GNU Mailman, and other projects---and who is working on a book to teach what she's learned along the way. Between 2016 and 2021, Harihareswara led fundraising for and managed the next-generation overhauls of PyPI and of pip's dependency resolver and user experience. Her work has earned her an Open Source Citizen Award and a Google Open Source Peer Bonus.
+
+
+## <i class="fa-regular fa-paper-plane"></i> Connect with us
+### pyOpenSci at PyCon US 2024
+{{< figure src="images/blog/2024/may/juno-stickers.png" alt="A close-up photo of Juno, a black lab mix, chewing on sticks. In front of Juno is a collection of pyOpenSci stickers." caption="Juno enjoying some sticks while showing off the latest pyOpenSci swag!" >}}
+While there will be a whole host of pyOpenSci community members at PyCon US this year, be sure to make time to say hello to our Executive Director and Founder, Leah Wasser. Not only would she love to chat with you about Python, open source, and open science, she's got a whole new set of stickers (including holographic stickers!) to give away. And for those lucky few, she's also got a limited edition run of postcards to hand out!
+
+And we'd love to hear about your PyCon experience! Be sure to tag us on [LinkedIn](https://www.linkedin.com/company/pyopensci) and/or [Fosstodon](https://fosstodon.org/@pyOpenSci)!
+
+### pyOpenSci around the web
+Stay up-to-date with all things pyOpenSci by following us on [LinkedIn](https://www.linkedin.com/company/pyopensci) and [Fosstodon](https://fosstodon.org/@pyOpenSci). And if you’re interested in our weekly newsletter where we share news, blog posts, and monthly updates, [subscribe on LinkedIn](https://www.linkedin.com/build-relation/newsletter-follow?entityUrn=7179551305344933888). We also send out a monthly recap newsletter to [our mailing list](https://eepurl.com/iM7SOM)!
diff --git a/content/blog/2024-05-23-pyos-call-for-editors.md b/content/blog/2024-05-23-pyos-call-for-editors.md
new file mode 100644
index 00000000..736bd621
--- /dev/null
+++ b/content/blog/2024-05-23-pyos-call-for-editors.md
@@ -0,0 +1,52 @@
+---
+title: 'Volunteers needed: pyOpenSci Editorial Board'
+date: '2024-05-23'
+type: blog
+excerpt: pyOpenSci is looking for volunteers from a wide array of scientific backgrounds
+  to join our Editorial Board.
+author: Jesse Mostipak
+blog_topic: software
+toc: true
+comments: true
+url: "/blog/pyos-call-for-editors-may-2024.html"
+lastmod: '2024-08-29'
+image:
+  src: images/blog/headers/call-for-editors.png
+  alt: 'Volunteers needed: pyOpenSci Editorial Board'
+---
+
+## Join the pyOpenSci Editorial Board
+### We're currently in need of editors with domain expertise in climatology and/or energy, and also accepting applications from all scientific domains
+Thanks to the efforts of our incredible team of volunteers, pyOpenSci is growing! As a result, we're currently seeing a large number of package submissions to [our open peer review process](https://www.pyopensci.org/about-peer-review/index.html). In order to continue supporting scientists in the development of open source scientific software, we're looking to add volunteer editors to our Editorial Board.
+
+Learn more about the Volunteer Editor role in our [Editor Guide](https://www.pyopensci.org/software-peer-review/how-to/editors-guide.html).
+{: .notice}
+
+The pyOpenSci Editorial Board is comprised of a diverse group of volunteers, with each editor being responsible for the following tasks:
+
+* Finding reviewers from diverse backgrounds who have a mixture of scientific domain, software usability and Python experience.
+* Overseeing the entire review process for a package ensuring it runs in a timely and efficient manner.
+* Supporting the submitting authors and reviewers in answering questions related to the review.
+* Determining whether that package should be accepted into the pyOpenSci ecosystem once the review has wrapped up.
+
+We often find that people interested in joining our Editorial Board are more than capable of performing the role, but sometimes doubt themselves. We want to strongly encourage you to apply if you're interested in the role. Not only do we offer support and guidance in your role as an Editor, we also have a warm, welcoming community that is always happy to help. Everyone starts somewhere, and we'd love for you to join us!
+
+It's also critical to the pyOpenSci mission that our Editorial Board have a combined expertise in various scientific domains, technical expertise in Python packaging, awareness of the importance of documentation in package usability, and awareness of the importance of CI/test suites in order to ensure robust software development.
+
+**IMPORTANT:** We do not expect any single editor to be an expert in all of these areas!
+
+We also appreciate when editors have experience working with or in the Python open source software community be it maintaining packages, contributing to packages, previously reviewing a pyOpenSci package, or supporting the community. This is certainly not a requirement, however, if you are interested in getting involved with pyOpenSci!
+
+If you're new to the pyOpenSci review process, we do also have Guest Editor volunteer roles, where you'll have more guidance or mentorship in order to complete the review.
+{: .notice}
+
+### Apply to be a pyOpenSci editor
+We're currently looking for editors from a wide variety of scientific backgrounds, with a current focus on climatology and energy. If you feel you'd be a good fit for the pyOpenSci Editorial Board, please fill out [this form](https://docs.google.com/forms/d/e/1FAIpQLScRQHQ7NKVEAG3BKAphiUdVFvQ5nkez0IpyXBMZDzXjuBPloQ/viewform).
+
+If you're interested in joining our Editorial Board, but have questions or would like to chat with someone from pyOpenSci about volunteering to be an editor, please email us at [media@pyopensci.org](mailto:media@pyopensci.org).
+
+## Meet our current Editorial Board
+You can explore [our current directory of pyOpenSci editors](https://www.pyopensci.org/about-peer-review/index.html#meet-our-editorial-board) on our website, and also read [a series of short interviews](https://www.linkedin.com/pulse/meet-pyopensci-editorial-team-pyopensci-robpc/?trackingId=gE1IVxw%2BRX6P6NGP%2B%2BbM4Q%3D%3D) with many of our editors in a recent issue of [our weekly newsletter](https://www.linkedin.com/build-relation/newsletter-follow?entityUrn=7179551305344933888).
+
+## Connect with pyOpenSci
+Stay up-to-date with all things pyOpenSci by following us on [LinkedIn](https://www.linkedin.com/company/pyopensci) and [Fosstodon](https://fosstodon.org/@pyOpenSci). Interested in our newsletters? We share news, blog posts, and monthly updates [in our LinkedIn newsletter](https://www.linkedin.com/build-relation/newsletter-follow?entityUrn=7179551305344933888), and a monthly recap newsletter to [our mailing list](https://eepurl.com/iM7SOM)!
diff --git a/content/blog/2024-05-24-oss-fall-festival-save-the-date-2024.md b/content/blog/2024-05-24-oss-fall-festival-save-the-date-2024.md
new file mode 100644
index 00000000..2a0cd711
--- /dev/null
+++ b/content/blog/2024-05-24-oss-fall-festival-save-the-date-2024.md
@@ -0,0 +1,23 @@
+---
+title: 'Save the Date: pyOpenSci''s 2024 Open Science Fall Festival'
+date: '2024-05-24'
+type: blog
+excerpt: Shake off those post-PyCon blues by adding our Open Science Fall Festival
+  to your calendar!
+author: Jesse Mostipak
+blog_topic: community
+toc: true
+comments: true
+url: "/blog/save-the-date-oss-fall-festival-2024.html"
+lastmod: '2024-08-29'
+---
+
+## You're invited: pyOpenSci's Open Science Fall Festival 2024
+Happening ~~September 28--29th, 2024,~~ October 28th through November 1st, 2024, the pyOpenSci Open Science Fall Festival will be held entirely online, and be a fantastic opportunity to bring together members of the Python community that create open source, open science tools with the members of the Python community who use these tools. In building this festival, our focus is on a grassroots, community-led event with some big unconference vibes.
+
+While we're still ironing out some of the details, we know it'll be a combination of talks, trainings, and opportunities to connect with the community through networking and social events. And we're working hard to keep ticket costs as accessible as we possibly can.
+
+> UPDATE: Our [pyOpenSci Fall Festival event page](/events/pyopensci-2024-fall-festival.html) is LIVE! We'll continuously be updating this page with event news and details.
+
+## Connect with pyOpenSci
+Stay up-to-date with all things pyOpenSci and our Open Source Fall Festival by following us on [LinkedIn](https://www.linkedin.com/company/pyopensci) and [Fosstodon](https://fosstodon.org/@pyOpenSci). And if you’re interested in our weekly newsletter where we share news, blog posts, and monthly updates, [subscribe on LinkedIn](https://www.linkedin.com/build-relation/newsletter-follow?entityUrn=7179551305344933888).
diff --git a/content/blog/2024-05-28-pyos-newsletter-june-2024.md b/content/blog/2024-05-28-pyos-newsletter-june-2024.md
new file mode 100644
index 00000000..02b9dbb6
--- /dev/null
+++ b/content/blog/2024-05-28-pyos-newsletter-june-2024.md
@@ -0,0 +1,142 @@
+---
+title: 'pyOpenSci Newsletter: June 2024'
+date: '2024-05-28'
+type: blog
+excerpt: We're starting June with a record number of Python package submissions, a
+  call for editors, a PyCon US reflection, and some SciPy meeting news!
+author: Jesse Mostipak
+blog_topic: updates
+toc: true
+comments: true
+url: "/blog/pyos-newsletter-june-2024.html"
+lastmod: '2024-08-29'
+image:
+  src: images/headers/scipy-2024-workshop.png
+  alt: 'pyOpenSci Newsletter: June 2024'
+---
+
+## <i class="fa-regular fa-comments"></i> PyCon was incredible!
+We feel so incredibly fortunate to have connected with so many of you at PyCon US! While we're still recovering from a week of summits, talks, and sprints, we wanted to share this sentiment from our Executive Director and Founder, [Leah Wasser](https://github.com/lwasser), which she shared on [her Fosstodon account](https://fosstodon.org/@leahawasser):
+{{< figure src="images/blog/2024/may/leah-pycon.png" alt="Screenshot of a Fosstodon post from Leah Wasser, reading: In my first few moments at pycon I ran into some of my conda friends & was quickly reminded of why this conference is so powerful. Python is more than a programming language. It's a community of people who I can geek out with about the most obscure topics. I belong. People care. They care a lot about their work. They care about helping each other learn. While this is a tech conference, it's really people that make python the vibrant community that it is." >}}
+
+### pyOpenSci's PyCon US Open Space
+This year, pyOpenSci's first Open Space brought together 17 attendees from various organizations, including Anaconda, NVIDIA, CPython, and more. The discussions focused on interoperability, scientific data workflows, and Python packaging for science, emphasizing the need for consistent tools and data formats to reduce cognitive load for scientists. A key topic was the gap between exploratory scripts and fully packaged code, highlighting the need for "in between" options for sharing code and outputs. These insights will guide pyOpenSci's efforts, with more discussions planned for the Fall Festival, scheduled for September 28-29, 2024.
+
+### pyOpenSci's PyCon US Sprint
+This year we had a tremendous turnout of over 20 people from several countries for our 1-day pyConUS sprint. At last count this resulted in about [30 issues and pull requests](https://github.com/orgs/pyOpenSci/projects/12/views/1) where volunteers who were there to support scientists, helped us fix issues on our website, in our tutorials and our [packaging](https://www.pyopensci.org/python-package-guide/) and [peer review](https://www.pyopensci.org/software-peer-review/index.html) guidebooks. So many long-standing issues and bugs were fixed thanks to this wonderful Python community.
+
+## <i class="fa-solid fa-handshake-simple"></i> See you at SciPy
+[SciPy 2024](https://www.scipy2024.scipy.org/) is just around the corner, and we can't wait to see you there! We're pulling together our pyOpenSci Guide to SciPy, similar to the guide we did for [PyCon 2024](https://www.pyopensci.org/blog/pyos-guide-to-pyconus-2024.html), and wanted to give you a preview of some of the tutorials and talks being given by pyOpenSci Community members!
+
+### Tutorials
+#### [Interactive data visualizations with Bokeh (in 2024)](https://cfp.scipy.org/2024/talk/JRLMLD/)
+Along with Timo Metzger and Bryan Van de Ven, pyOpenSci community member [Pavithra Eswaramoorthy]() will be covering everything you need to know to create beautiful and powerful interactive plots from scratch using Bokeh’s latest features. Starting with a quick introduction of Bokeh’s core concepts, the team will cover creating and customizing simple static plots like line and bar charts before introducing layers of interactivity, creating specialized plotting features like geographic maps, contour plots, Mathematical Text, and discussing new additions to Bokeh like ImageStacks. By the end, you will be able to create a complete interactive dashboard using Bokeh.
+
+#### [3D Visualization with PyVista](https://cfp.scipy.org/2024/talk/GKGRWE/)
+Led by Tetsuo Koyama, Alexander Kaszynski, Bill Little, and Bane Sullivan, this tutorial demonstrates [PyVista's](https://github.com/pyvista/pyvista) latest capabilities and bring a wide range of users to the forefront of 3D visualization in Python, including:
+
+* Use PyVista to create 3D visualizations from a variety of datasets in common formats.
+* Overview the classes and data structures of PyVista with real-world examples.
+* Be familiar of the various filters and features of PyVista.
+* Know which Python libraries are used and can be used by PyVista (meshio, trimesh etc).
+* We see this tutorial catering to anyone who wants to visualize data in any domain, and this ranges from basic Python users to advanced power users.
+
+#### [From RAGS to riches: Build an AI document inquiry web-app](https://cfp.scipy.org/2024/talk/W3ZJWG/)
+Pavithra Eswaramoorthy, a Developer Advocate at [Quansight](https://quansight.com/), is teaming up with Dharhas Pothina and Andrew Huang to cover how to use RAG to build document-inquiry chat systems using different commercial and locally running LLMs. The topics we’ll cover include:
+
+* **Introduction to RAG**, how it works and interacts with LLMs, and Ragna - a framework for RAG orchestration
+* **Creating and optimizing a basic chat function** that uses popular LLMs (like GPT) answers questions about your documents, using a Python API in Jupyter Notebooks
+* **Running a local LLM on GPUs** on the provided platform, and comparing its performance to commercial LLMs
+* **Introduction to Panel**, by creating a basic chat UI for Ragna using Panel’s ChatBox widget
+* **Building and deploying a Panel-based web-app**, which extends the basic chat UI and includes more application components
+
+By the end of this tutorial, you will have an understanding of the fundamental components that form a RAG model, and practical knowledge of open source tools that can help you or your organization explore and build on your own applications. This tutorial is designed to enable enthusiasts in our community to explore an interesting topic using some beginner-friendly Python libraries.
+
+#### [Create Your First Python Package: Make Your Python Code Easier to Share and Use](https://cfp.scipy.org/2024/talk/QT9GBY/)
+Led by pyOpenSci's Executive Director and Founder, [Leah Wasser](https://github.com/lwasser), in this tutorial session you'll learn how to:
+
+* Create code that can be installed into different environments
+* Use [Hatch](https://hatch.pypa.io/latest/) as a workflow tool, making setup and installation of your code easier
+* Use Hatch to publish your package to (test) PyPI
+
+Creating code that can be shared and reused is the gold-standard of open science. But tools and skills to share your code can be tricky to learn. In this hands-on tutorial, you’ll learn how to turn your code into an installable Python module ( a file containing Python code that defines functions, classes, and variables), that can be shared with others. We will provide pre-built code and module examples for each step of the tutorial to make it more beginner-friendly. However, to get the most out of this tutorial, you should be familiar with writing Python code, writing and using functions and you should understand the concept of Python environments. You should also have Python and Hatch installed on your computer prior to attending. If you are newer to environments and don’t have a preferred tool, then we recommend that you use conda. However, any environment tool that you prefer works well.
+
+Interested in helping out with our Packaging workshop? Reach out to us at [media@pyopensci.org](mailto:media@pyopensci.org). We're looking for volunteers to assist learners throughout the workshop.
+{: .notice}
+
+#### [Data of an Unusual Size (2024 edition): A practical guide to analysis and interactive visualization of massive datasets](https://cfp.scipy.org/2024/talk/UKLNLQ/)
+Pavithra Eswaramoorthy, and Dharhas Pothina, both from [Quansight](https://quansight.com/), will help you learn the fundamentals of analyzing massive datasets with real-world examples on actual powerful machines on a public cloud provided by the presenters – starting from how the data is stored and read, to how it is processed and visualized.
+
+### Talks
+#### [The power of community in solving scientific Python’s most challenging problems](https://cfp.scipy.org/2024/talk/AMTLJ7/)
+This talk from our Executive Director and Founder, [Leah Wasser](https://github.com/lwasser), shares pyOpenSci’s knowledge in building a constructive open peer review process that supports maintainers, and also resources that make Python packaging more accessible and easier-to-navigate. Our insights are based on five years of experience working with over 200 community members, who have evaluated 58 packages developed by over 56 package maintainers.
+
+Leah's talk is about writing the [pyOpenSci Python Packaging Guide](https://www.pyopensci.org/python-package-guide/) via community!
+{: .notice}
+
+#### [Great Tables for Everyone](https://cfp.scipy.org/2024/talk/BRMQRW/)
+This talk from Rich Iannone, whose package [Great Tables](https://github.com/pyOpenSci/software-submission/issues/184) is currently under review with pyOpenSci, will provide a demonstration of Great Tables, showing how data can come alive in when in tabular form. We’ll use data from the fields of meteorology, chemistry, and the atmospheric sciences within our table-making examples. We’ll learn how the different components of a table (e.g., the column labels, the header, etc.) can be manipulated to best convey the data. We believe tables are worthy of being deemed data visualizations and we hope that Great Tables can become an indispensable tool in your data analysis workflow.
+
+#### [From Code to Clarity: Using Quarto for Python Documentation](https://cfp.scipy.org/2024/talk/GFGSTS/)
+Isabel Zimmerman, a member of our triage team and an Emeritus Editor in Chief, will be speaking from her experiences as an open source developer who works with multilingual tools, and how Quarto + quartodoc helped to fill those gaps. This talk is intended for anyone who might have to communicate with stakeholders through code using a web-based format. She'll be focusing on Python package documentation websites, but the stories and examples expose the difficulties in many types of technical communication. The intent is to have a lighthearted talk filled with examples of how to make technical communication and publishing easier and more accessible.
+
+#### [Vector space embeddings and data maps for cyber defense](https://cfp.scipy.org/2024/talk/STUXTH/)
+pyOpenSci community member Benoit Hamelin will cover how the vast amounts of information of interest to cyber defense organizations comes in the form of unstructured data; from host-based telemetry and malware binaries, to phishing emails and network packet sequences. All of this data is extremely challenging to analyze. In recent years there have been huge advances in the methodology for converting unstructured media into vectors. However, leveraging such techniques for cyber defense data remains a challenge.
+
+Imposing structure on unstructured data allows us to leverage powerful data science and machine learning tools. Structure can be imposed in multiple ways, but vector space representations, with a meaningful distance measure, have proven to be one of the most fruitful.
+
+In this talk, he will demonstrate a number of techniques for embedding cyber defense data into vector spaces, as well as discuss how to leverage manifold learning techniques, clustering, and interactive data visualization to broaden our understanding of the data and enrich it with expert feedback.
+
+### Sprints
+We'll also be holding a pyOpenSci sprint at SciPy 2024! Be sure to follow us on [LinkedIn](https://www.linkedin.com/company/pyopensci) and [Fosstodon](https://fosstodon.org/@pyOpenSci) for more details!
+
+## <i class="fa-solid fa-envelope-open"></i> Save the Date: pyOpenSci's Open Source Fall Festival
+{{< figure src="images/blog/2024/may/oss-fall-festival.png" alt="Abstract shapes on a white background with the text: Save the Date. pyOpenSci Open Source Fall Festival. September 28 & 29, 2024. Entirely online! Follow us on socials for more info. fosstodon.org/@pyOpenSci linkedin.com/company/pyopensci pyopensci.org." >}}
+We love a good get-together, and our Open Source Fall Festival is no exception! Held entirely online using Spatial Chat, our goals is to bring together members of the Python community that create open source tools with the members of the Python community who use the tools. In building this festival, our focus is on a grassroots, community-led event with some big unconference vibes. So mark your calendars, and save the date for September 28--29th, 2024!
+
+## <i class="fa-solid fa-hand-holding-heart"></i> Python packages for everyone!
+pyOpenSci's [Open Peer Review process](https://www.pyopensci.org/about-peer-review/index.html) is experiencing an [unprecedented number of Python package submissions](https://github.com/pyOpenSci/software-submission/issues)! We're excited to see so many wonderful packages that are helping scientists help make the world a better place being submitted for review. Our open peer review process facilitates scientists getting credit and recognition for the work they’ve invested in developing scientific Python tools while also supporting them in building better software. The peer review process also supports scientists in finding vetted and maintained software, which drives their open science workflows.
+
+You can submit your package for review (or pre-submission inquiry to determine if it's in scope) by [submitting an issue](https://github.com/pyOpenSci/software-submission/issues/new/choose) to [our software-submission repository](https://github.com/pyOpenSci/software-submission). And because all of our reviews are open, [you can see our review process in action](https://github.com/pyOpenSci/software-submission).
+
+We're also accepting applications for [package reviewers](https://docs.google.com/forms/d/e/1FAIpQLSeVf-L_1-jYeO84OvEE8UemEoCmIiD5ddP_aO8S90vb7srADQ/viewform). We welcome reviewers from a diversity of background and with varying levels of Python technical expertise.
+
+Some of the basic things that we look for in a review include:
+* Familiarity with using the Python programming language.
+* Ability to evaluate a Python package for usability and documentation quality.
+* Ability to provide a technical review of Python package structure and code quality / approach to solving the problems that the package seeks to address.
+
+We like to have a mix of technical and usability focus in our reviews so it’s ok if you don’t have all of the above skills! Not sure if you're ready to review on your own? Check out the [pyOpenSci mentorship program](https://www.pyopensci.org/software-peer-review/how-to/reviewer-guide.html#a-guide-for-new-reviewers)!
+
+## <i class="fa-solid fa-bullhorn"></i> Get involved with pyOpenSci: call for editors
+{{< figure src="images/blog/2024/may/pyos-call-for-editors.png" alt="Off-white square on a purple floral background with text that reads: Get involved with pyOpenSci! We're growing out editorial team, and are seeking volunteers from a wide variety of scientific backgrounds. Editors: lead the review process for 3-4 packages a year and assist with editorial and peer review policies. People from diverse backgrounds are especially encouraged to apply! Questions? Email media@pyopensci.org. Apply: bit.ly/pyOSEditor" >}}
+
+If you're looking to give back to the broader Python community, consider joining our Editorial Board! The pyOpenSci Editorial Board is comprised of a diverse group of volunteer editors, each one responsible for the following tasks:
+
+* Finding reviewers from diverse backgrounds who have a mixture of scientific domain and Python experience.
+* Overseeing the entire review process for a package ensuring it runs in a timely and efficient manner.
+* Supporting the submitting authors and reviewers in answering questions related to the review.
+* Determining whether that package should be accepted into the pyOpenSci ecosystem once the review has wrapped up.
+
+While we have a current need for editors with expertise in climatology and/or energy, we're also recruiting editors from all scientific disciplines. If you feel you'd be a good fit for the pyOpenSci Editorial Board, please fill out [this form](https://docs.google.com/forms/d/e/1FAIpQLScRQHQ7NKVEAG3BKAphiUdVFvQ5nkez0IpyXBMZDzXjuBPloQ/viewform).
+
+If you're interested in joining our Editorial Board, but have questions or would like to chat with someone from pyOpenSci about volunteering to be an editor, please email us at [media@pyopensci.org](mailto:media@pyopensci.org).
+
+## <i class="fa-brands fa-python"></i> Upcoming Python events for scientists
+### SciPy
+With keynotes from [Julia Silge](https://juliasilge.com/), [Dr. Elizabeth (Libby) Barnes](https://sites.google.com/view/barnesgroup-csu/prof-barnes), and [Kyle Cranmer](https://www.physics.wisc.edu/directory/cranmer-kyle/), [SciPy 2024](https://www.scipy2024.scipy.org/) is going to be yet another conference you don't want to miss! Held at the Tacoma Convention Center, July 8-14, 2024, [tickets are still available](https://ti.to/scipy/scipy2024)!
+
+### PyData Eindhoven
+With 14 captivating talks lined up, [PyData Eindhoven](https://pydata.org/eindhoven2024/)  offers a diverse range of topics to expand your knowledge and inspire innovative thinking. From cutting-edge data analysis techniques to machine learning applications, our expert speakers will cover it all. Co-hosted with Day 2 of [JuliaCon](https://juliacon.org/2024/), [grab your tickets](https://pydata.org/eindhoven2024/) and join your peers in the Netherlands this July 11th!
+
+### BioC 2024
+Taking place Wednesday July 24 - Friday July 26 at the Van Andel Institute in Grand Rapids, MI,the BioC 2024: Where Software and Biology Connect hybrid conference still has tickets available. And what's more, all proceeds go to helping underrepresented minorities and individuals from low to middle-income countries, including students, fellows, and early career investigators.
+
+### PyData Vermont
+[PyData Vermont 2024](https://pydata.org/vermont2024/) is a two day in-person event for the international community of data scientists, data engineers, and developers of data analysis tools to share ideas and learn from each other. The event will be in-person at the Main Street Landing Performing Arts Center, July 29 to July 30, 2024. [Register today](https://pydata.org/vermont2024/tickets)!
+
+### Tell us about your event!
+Have an upcoming scientific Python event that’s open to the public? Email us at [media@pyopensci.org](mailto:media@pyopensci.org) with the details to have your event listed.
+
+## <i class="fa-regular fa-paper-plane"></i> Connect with us
+Stay up-to-date with all things pyOpenSci by following us on [LinkedIn](https://www.linkedin.com/company/pyopensci) and [Fosstodon](https://fosstodon.org/@pyOpenSci). And if you’re interested in our weekly newsletter where we share news, blog posts, and monthly updates, [subscribe on LinkedIn](https://www.linkedin.com/build-relation/newsletter-follow?entityUrn=7179551305344933888). We also send out a monthly recap newsletter to [our mailing list](https://eepurl.com/iM7SOM)!
diff --git a/content/blog/2024-05-30-pyos-pyconus-2024-recap.md b/content/blog/2024-05-30-pyos-pyconus-2024-recap.md
new file mode 100644
index 00000000..80533ef7
--- /dev/null
+++ b/content/blog/2024-05-30-pyos-pyconus-2024-recap.md
@@ -0,0 +1,219 @@
+---
+title: pyOpenSci at PyCon US 2024 - Python packaging and community
+date: '2024-05-30'
+type: blog
+excerpt: Learn about  pyOpenSci's experience at PyCon US 2024, how pyOpenSci is making
+  Python packaging more accessible and beginner friendly and how the Python community
+  is helping us get there.
+author: Leah Wasser
+blog_topic: community
+toc: true
+comments: true
+url: "/blog/recap-pyos-pyconus-2024.html"
+lastmod: '2024-08-29'
+image:
+  src: images/blog/headers/pycon-us-2024-header.png
+  alt: pyOpenSci at PyCon US 2024 - Python packaging and community
+---
+
+<div class="notice" markdown = "1">
+## TL;DR
+
+* pyOpenSci had a strong presence at [PyCon US](https://us.pycon.org/2024/) this year. I hope this continues for years to come! We held an open space, helped run the [Maintainers Summit](https://us.pycon.org/2024/events/maintainers-summit/) (lead by [Inessa Pawson](https://github.com/InessaPawson) for 5 years and counting), gave [a talk on Python packaging](https://us.pycon.org/2024/schedule/presentation/34/) and ran a 1 day sprint where over 16 people contributed to our efforts.
+* pyOpenSci’s theme this year for PyConUS was people first: people first when trying to make technical concepts easier to understand, people first when trying to write good tutorials or documentation and people first when you are trying to solve the world’s hardest problems.
+* Giving a talk on packaging at pyConUS triggered every ounce of the imposter in me. But in the end it was a rewarding experience. Having friends in the audience made a world of difference. It was calming to focus on people who I know support both me and this vibrant organization. Friends really should never let friends…package…or use Python…or do anything technical…alone.
+
+</div>
+
+## Another year, another incredible PyCon
+
+Wow! I wasn’t sure it would be possible to top [last year’s PyCon US 2023 experience](https://www.pyopensci.org/blog/pycon-2023-packaging-presentation-sprints-leah-wasser.html)
+in Salt Lake City, but this year's [PyConUS 2024](https://us.pycon.org/2024/) *was even better*. People are learning about [pyOpenSci](https://www.pyopensci.org/). The community is excited to support our mission to **help
+scientists create better software and make their science more open and
+reproducible** so they can tackle the world's greatest challenges.
+
+PyCon US, run by the [Python Software
+Foundation,](https://www.python.org/psf-landing/) is one of the biggest Python meetings in the world, with a record 2,700 registrations this year.
+{: .notice }
+
+I also knew that I'd get to see a bunch of the friends who I met last year. I was returning to
+this inclusive community, filled with Pythonistas like me
+who care, who want to learn, and most importantly who want to help each other.
+
+And...thanks to our incredible Community Manager,
+[Jesse (@kiersi on GitHub)](https://github.com/kiersi), we now have
+a [pyOpenSci](https://www.pyopensci.org) visual brand -- and stickers galore.
+
+{{< figure src="images/blog/2024/may/juno-stickers.png" alt="Image of a flat coated retriever chewing on a stick with a bunch of pyOpenSci stickers in front of her cut face. ' style='width: 70%;" caption="<i class='fa-solid fa-heart-pulse'></i> My rescue pup Juno prefers sticks, but also loves pyOpenSci <i class='fa-solid fa-heart-pulse'></i>." >}}
+
+### So different from last year
+
+My experience last year was a bit different. I walked into my first PyCon
+US having no idea how I'd fit in at the meeting. I didn’t know
+many people. I had never led a [mentored sprint](https://www.mentored-sprints.dev/).
+And I wasn't sure how my packaging talk, [Friends Don't Let Friends Package Alone](https://us.pycon.org/2024/schedule/presentation/34/) would be received; you see, packaging is a notoriously thorny
+topic.
+
+[Last year turned out pretty great - read more here.](/blog/pycon-2023-packaging-presentation-sprints-leah-wasser.html)
+
+However, rather than feeling like an outsider, I met a lot of new people
+who became new Python friends and colleagues. I learned about a lot of cool
+projects and organizations and our sprints were awesome with many new contributions. Yaas! <i class="fa-solid fa-rocket"></i>
+
+My takeaway: if you are considering going to PyCon but are worried about not knowing
+people YOU SHOULD STILL GO! You can feel the true spirit of open source (and open science) at PyCon US. No judgement. All "levels" of Pythonistas welcome.
+
+## My first main track PyCon US talk: Friends don't let friends package alone
+
+This year, I gave my first main track talk at PyCon, titled “Friends Don’t Let
+Friends Package Alone.” Getting a main track slot means presenting on a big
+stage to a huge room of people! It was real - headset mic, incredible
+tech support, and even an “escort” from the speaker room to the main stage. Wow!
+
+You can check it out on youtube below:
+
+Speaking of friends, it was my friends who got me through this talk. I saw them sitting in
+the front rows, smiling and supporting me. They both empowered me and gave me calm.
+
+As someone who often battles imposter syndrome, giving a talk on the "big" stage of a tech meeting
+was unforgettable.
+
+{{< figure src="images/blog/2024/may/leah-talking-pyconus-2024.jpg" alt="Image of a woman on a big stage wearing a red tank top talking. On the side is a slide that says pyOpenSci - Save the Date. Open science fall festival september 28-29 2024' style='width: 70%;" caption="<i class='fa-solid fa-heart-pulse'></i> Me talking on the stage! I was so nervous before but once I got up there, everything calmed in my mind. <i class='fa-solid fa-heart-pulse'></i>." >}}
+
+### A talk about making Python packaging more beginner friendly
+
+My talk focused on how pyOpenSci helps beginners by breaking down
+complex packaging concepts into simple, digestible pieces. I leaned into decades of
+experience and study of teaching data science to various audiences, from big-ten university students
+to students at under-resourced and under-served tribal colleges. The essence of my talk was about the importance of
+community and collaboration in the thorny Python packaging ecosystem, and also why documentation should focus on fundamental concepts that users need to understand, rather than tools.
+
+Our pyOpenSci community has created a comprehensive, [beginner-friendly Python
+package guide](https://www.pyopensci.org/python-package-guide/) with contributions from over 50 community members. Key takeaways
+from my talk:
+
+* leverage community support,
+* create early wins for users, focus on
+fundamental concepts, and
+* avoid “Too Many Options and Opinions” (TMO) to keep things simple
+for beginners.
+
+{{< figure src="images/blog/2024/may/pyopensci-too-many-python-packaging-options-pycon-talk-2024.png" alt="A cute image of a black flat coated retriever laying on the floor with a purple ice pack on it's head looking right at you." caption="Whether it's too many options or too many opinions, TMO will push beginner users away. Too many options create cognitive load that prevent users from having successful experiences." >}}
+
+<!-- [I break this all down in more detail here if you want to read more.](#addlink) -->
+
+Giving a talk at PyConUS experience reinforced my belief in the power of community to tackle complex
+problems and support each other in our scientific journeys.
+
+<!--
+Or you can check out the talk itself on youtube below:
+
+TODO: embed video - they are slowly being posted - 145 are in draft state....
+
+2023 talk --
+https://www.youtube.com/watch?v=Qxy7bxW72iA
+-->
+
+## <i class="fa-solid fa-rocket"></i> The PyCon US maintainers Summit <i class="fa-solid fa-rocket"></i>
+
+This year, I had the honor of helping [Inessa Pawson](https://github.com/InessaPawson) and [Kara Sowles](https://github.com/karasowles) organize the
+[PyCon US Maintainers Summit 2024](https://us.pycon.org/2024/events/maintainers-summit/), an event that has grown from an experimental
+“hatchery” to its 6th year at PyCon US. Last year, I had the [privilege of giving
+a talk at the summit](https://www.youtube.com/watch?v=Qxy7bxW72iA). This year, I co-organized, learning the ropes of proposal
+calls, speaker selection, and navigating a summit that filled a room of 80
+people within a conference boasting 2,700 registrations. The prep leading up to
+the summit was manageable, but the days before and the day of were quite the
+adventure!
+
+The summit featured amazing speakers, including:
+
+* [Leonard Richardson](https://www.linkedin.com/in/leonardr/), who shared
+insights on maintaining core tools like [Beautiful Soup](https://pypi.org/project/beautifulsoup4/) for 20 years and tips on
+handling burnout.
+* [Jessica Tegner](https://github.com/JessicaTegner). Jessica became a maintainer of one of the top 1% of all downloaded packages on PyPI - [pypandoc](https://github.com/JessicaTegner/pypandoc). She talked about her experiences taking over a package with over 3 million monthly downloads. Oh and did I mention that Jessica does all this while being visually challenged? The backgrounds (and dedication) of the maintainers in our open source ecosystem always blows my mind.
+
+Working alongside Inessa Pawson, Kara Sowles and Chris Rose who are all also rockstars in the open source world was a fantastic
+experience. Despite some logistical challenges, like the summit filling up
+quickly and a waitlist, the event was a success. Next year (if we are invited back), will be even better as we try to open the doors to include aspiring maintainers and contributors!
+
+Also if you were wondering, yes that Monstera Deliciosa (plant) in the background is real! AND YES it is ginormous! <i class="fa-solid fa-leaf"></i>
+
+## <i class="fa-solid fa-users-gear"></i> Our second pyOpenSci sprint <i class="fa-solid fa-users-gear"></i>
+
+This year we had a tremendous turnout of over 20 people from several countries for our 1-day pyConUS sprint. At last count this resulted in about [30 issues and pull requests](https://github.com/orgs/pyOpenSci/projects/12/views/1) where volunteers who were there to support scientists, helped us fix issues on our website, in our tutorials and our [packaging](https://www.pyopensci.org/python-package-guide/) and [peer review](https://www.pyopensci.org/software-peer-review/index.html) guidebooks. So many long-standing issues and bugs were fixed thanks to this wonderful Python community.
+
+<figure class="half">
+  <img src="/images/blog/2024/may/pycon-us-24-pyopensci-sprints-juno.png" alt="Image of the puycon us sprint board where projects signed up for different rooms." />
+  <img src="/images/blog/2024/may/pycon-24-sprints-pyopensci.png" alt="Image of the puycon us sprint board where projects signed up for different rooms." />
+  <figcaption>The pyConUS sprint sign-up board had lots of projects. Because the rooms are large, projects tend to share spaces. We ended up in the packaging room which was great as it allowed us to do some more difficult work around Python packages with C extensions!</figcaption>
+If you haven’t been to a sprint before, it’s an experience that every open source enthusiast should have. Sprints are where a bunch of people come together to work on a project. If you are running sprints that support software development in a professional environment (i.e. at a company) this might mean a team of people working together on releasing a new software feature. But for the open source community, sprints can also mean volunteers coming to a space to help maintainers work on various parts of a project that they care about - like pyOpenSci!
+
+pyOpenSci supports other people's software through it's [open community-lead peer review process](https://www.pyopensci.org/about-peer-review/index.html) and it's online, free [packaging resources](https://www.pyopensci.org/python-package-guide/). But it also has it's own software too. We have tools that help us keep track of our review process and volunteer contributions so we can acknowledge everyone for their effort.
+
+Acknowledging contributions is so so so (did I mention SO?) important. And we value them so much.
+
+{{< figure src="images/blog/2024/may/pycon-24-sprints-table-pyopensci.png" alt="Image of a round table of people talking and working at computers during our sprints." caption="We had people working at multiple tables on pyOpenSci issues. A handful of people worked through our Create Your First Python Package tutorials and provided input and found issues! Included in this image is Jeremiah Paige who is making our packaging guide so much better by adding actual package examples (including on that has C extensions!) using Hatch!" >}}
+
+### How to run a sprint
+
+I've learned a lot about running sprints over the past 2 years. At pyOpenSci, we have a [help-wanted project board](https://github.com/orgs/pyOpenSci/projects/3) where we add issues and things that we could use help with across our organization. Some of the tasks that we need help with are beginner friendly. For example it's useful for beginners to test drive our [online packaging tutorials](https://www.pyopensci.org/python-package-guide/tutorials/intro.html) and then report bugs as GitHub issues. Your feedback might be errors in a lesson, typos or things that were confusing / didn’t work.
+
+Some of our help-wanted issues are more technical too. pyOpenSci is a non-profit organization whose heart is a community of volunteers. We have infrastructure that any other open source project would have, and as such we need technical help working on CI (continuous integration) workflows, guidebook infrastructure, our website and more.
+
+As an Executive Director and Founder of pyOpenSci, I created most of this infrastructure to support our mission myself, early on. This means that sometimes, its not the prettiest code <i class="fa-regular fa-face-grin-squint-tears"></i>. But it works.
+
+While I cherish times when I have bandwidth to work on technical things, it’s hard to keep up. So I really appreciate when community members can help us tick off open issues - big and small.
+
+## <i class="fa-solid fa-user-group"></i> Our first pyOpenSci PyCon Open Space <i class="fa-solid fa-user-group"></i>
+
+{{< figure src="images/blog/2024/may/pyconus-2024-pyopensci-openspace.png" alt="Image showing a room with round tables and people working at each table most of who have laptops sitting in front of them.' style='width: 100%;" caption="I was new to leading open spaces but learned a lot for next year. We had 3 tables of people talking about different science related pain points in the Python ecosystem." >}}
+
+This year, we ran our first pyOpenSci Open Space, bringing together 17 attendees
+from organizations like Anaconda, NVIDIA, CPython, PyPA, Million Concepts,
+CapitalOne, Moderna, and MongoDB. Our discussions spanned interoperability,
+scientific data workflows, and Python packaging for science. We focused on the
+importance of consistent tools and data formats, reducing cognitive load for
+scientists, and maintaining backwards compatibility. Key takeaways included the
+need for shared data formats, simple reproducibility practices, and opinionated
+packaging guides.
+
+A topic that came up a lot was the gap between exploratory code / scripts and
+fully packaged / published code. There is a need for more "in between" options that support scientists sharing their code and code outputs.
+
+The discussions in this year’s open space gave pyOpenSci much to consider moving
+forward. The complexity and diversity of tools in scientific computing can
+create significant cognitive load.
+
+We need consistent and straightforward tools and
+workflows that allow allowing scientists to focus on their research
+rather than tools. We plan to tackle some of these and other topics during our Fall festival on September 28-29,
+2024 so save the date and come ready to learn and share!
+
+## <i class="fa-solid fa-box-open"></i> Packaging summit
+
+Last but not least, pyOpenSci had a strong presence at the PyConUS packaging summit this year. The summit was organization by [Pradyun Gedam](https://github.com/pradyunsg), [Jannis Leidel](https://github.com/jezdez), [CAM Gerlach](https://github.com/CAM-Gerlach), [Filipe Laínes](https://github.com/FFY00). As I have mentioned several times, packaging is one of the more thorny topics in our Python ecosystem. However, this year, things felt different compared to last.
+
+For one, there were a lot more people in the room, and people with different perspectives. For starters, last year I was 1 of 3? female-identifying people in the room - this year there were people from many backgrounds and identities in the room! Last year also felt more technical whereas this year was a perfect mix of  discussing technical topics combined with a strong theme of considering user experience in both installing Python and creating packages. PLUS - documentation - yes PLEASE!
+
+The Executive Director of the Python Software Foundation was in the room and shared that there could be financial support in the future to make packaging better!
+
+I'm hopeful.
+
+From my perspective, the biggest challenges in our ecosystem revolve around:
+
+* too much focus on tools and not enough focus on user experience and documentation, and
+* too many options and opinions that prevent users from have early success.
+
+There is a path forward. And people who are working on tools in the ecosystem really do care -- a lot. So please thank them - thank the maintainers and people who work on the tools that you use - or might use in the future. It's all volunteer time.
+
+A few other highlights for me included meeting Ofek, the maintainer of [Hatch](https://ofek.dev/projects/hatch/). It was a big deal for Ofek to attend this meeting in person! He also gave a talk on his end-to-end packaging tool Hatch.
+
+## <i class="fa-brands fa-python"></i> Wrap up
+
+{{< figure src="images/blog/2024/may/pyopensci-pyconus-2024-juno-thankyou.png" alt="Image of Juno a black dog that looks like a flat coated retriever border collie mix with the PyCon US swag thank you bag and a pyOpenSci sticker on it with the name Leah Wasser Maintainers Summit.' style='width: 60%;" caption="Image of Juno my pup with my PyConUS thank you gifts. PyCon provides letters and gifts for people who either give talks or lead / organize events. This year I did both and got a pint glass to remember it all - #rescuedogapproved." >}}
+
+I left pyCon US 2024 overwhelmed by the support that pyOpenSci received. People at pyCon generally care a lot and are invested in making scientists' experience in the Python ecosystem better. I also needed a week to recover. I am an introvert by nature so even the best days of interacting with friends makes me tired!
+
+I look forward to attending the meeting again next year - once again in Pittsburgh, Pennsylvania, USA. And I look forward to seeing my newly expanded Python family again too.
+
+See you there!
diff --git a/content/blog/2024-06-03-sleplet-slepian-wavelets.md b/content/blog/2024-06-03-sleplet-slepian-wavelets.md
new file mode 100644
index 00000000..d0710eb1
--- /dev/null
+++ b/content/blog/2024-06-03-sleplet-slepian-wavelets.md
@@ -0,0 +1,163 @@
+---
+title: 'SLEPLET: Slepian Scale-Discretised Wavelets in Python'
+date: '2024-06-03'
+type: blog
+excerpt: SLEPLET is a tool to create Slepian scale-discretised wavelets that has recently
+  passed the PyOpenSci review.
+author: Patrick J. Roddy
+blog_topic: software
+comments: true
+url: "/blog/sleplet-slepian-wavelets.html"
+lastmod: '2024-08-29'
+image:
+  src: images/blog/headers/sleptlet-header.png
+  alt: 'SLEPLET: Slepian Scale-Discretised Wavelets in Python'
+---
+
+[SLEPLET](https://github.com/astro-informatics/sleplet) is a Python package for
+the construction of Slepian wavelets in the spherical and manifold (via meshes)
+settings. In contrast to other codes, `SLEPLET` handles any spherical region as
+well as the general manifold setting. The API is documented and easily
+extendible, designed in an object-orientated manner. Upon installation,
+`SLEPLET` comes with two command line interfaces - `sphere` and `mesh` - that
+allow one to easily generate plots on the sphere and a set of meshes using
+[plotly](https://github.com/plotly/plotly.py). Whilst these scripts are the
+primary intended use, `SLEPLET` may be used directly to generate the Slepian
+coefficients in the spherical/manifold setting and use methods to convert these
+into real space for visualisation or other intended purposes. The construction
+of the sifting convolution was required to create Slepian wavelets. As a result,
+there are also many examples of functions on the sphere in harmonic space
+(rather than Slepian) that were used to demonstrate its effectiveness. `SLEPLET`
+has been used in the development of several papers.
+
+## Background
+
+Wavelets are widely used in various disciplines to analyse signals both in space
+and scale. Whilst many fields measure data on manifolds (i.e. the sphere),
+often data are only observed on a partial region of the manifold. Wavelets are a
+typical approach to data of this form, but the wavelet coefficients that overlap
+with the boundary become contaminated and must be removed for accurate analysis.
+Another approach is to estimate the region of missing data and to use existing
+whole-manifold methods for analysis. However, both approaches introduce
+uncertainty into any analysis. Slepian wavelets enable one to work directly with
+only the data present, thus avoiding the problems discussed above. Applications
+of Slepian wavelets to areas of research measuring data on the partial sphere
+include gravitational/magnetic fields in geodesy, ground-based measurements in
+astronomy, measurements of whole-planet properties in planetary science,
+geomagnetism of the Earth, and cosmic microwave background analyses.
+
+## Statement of Need
+
+Many fields in science and engineering measure data that inherently live on
+non-Euclidean geometries, such as the sphere. Techniques developed in the
+Euclidean setting must be extended to other geometries. Due to recent interest
+in geometric deep learning, analogues of Euclidean techniques must also handle
+general manifolds or graphs. Often, data are only observed over partial regions
+of manifolds, and thus standard whole-manifold techniques may not yield accurate
+predictions. Slepian wavelets are designed for datasets like these. Slepian
+wavelets are built upon the eigenfunctions of the Slepian concentration problem
+of the manifold: a set of bandlimited functions that are maximally concentrated
+within a given region. Wavelets are constructed through a tiling of the Slepian
+harmonic line by leveraging the existing scale-discretised framework. Whilst
+these wavelets were inspired by spherical datasets, like in cosmology, the
+wavelet construction may be utilised for manifold or graph data.
+
+To the author's knowledge, there is no public software that allows one to
+compute Slepian wavelets (or a similar approach) on the sphere or general
+manifolds/meshes. [SHTools](https://github.com/SHTOOLS/SHTOOLS) is a `Python`
+code used for spherical harmonic transforms, which allows one to compute the
+Slepian functions of the spherical polar cap. A series of `MATLAB` scripts exist
+in [slepian_alpha](https://github.com/csdms-contrib/slepian_alpha), which
+permits the calculation of the Slepian functions on the sphere. However, these
+scripts are very specialised and hard to generalise.
+
+Whilst Slepian wavelets may be trivially computed from a set of Slepian
+functions, the computation of the spherical Slepian functions themselves are
+computationally complex, where the matrix scales as 𝒪(𝐿⁴). Although symmetries
+of this matrix and the spherical harmonics have been exploited, filling in this
+matrix is inherently slow due to the many integrals performed. The matrix is
+filled in parallel in `Python` using
+[concurrent.futures](https://docs.python.org/3/library/concurrent.futures.html),
+and the spherical harmonic transforms are computed in `C` using
+[SSHT](https://github.com/astro-informatics/ssht). This may be sped up further
+by utilising the new [ducc0](https://github.com/mreineck/ducc) backend for
+`SSHT`, which may allow for a multithreaded solution. Ultimately, the
+eigenproblem must be solved to compute the Slepian functions, requiring
+sophisticated algorithms to balance speed and accuracy. Therefore, to work with
+high-resolution data such as these, one requires high-performance computing
+methods on supercomputers with massive memory and storage. To this end, Slepian
+wavelets may be exploited at present at low resolutions, but further work is
+required for them to be fully scalable.
+
+## Example Usage
+
+`SLEPLET` may be interacted with via the API or the CLIs.
+
+### API Usage
+
+The following demonstrates the first wavelet (ignoring the scaling function) of
+the South America region on the sphere.
+
+```python
+import sleplet
+
+B, J, J_MIN, L = 3, 0, 2, 128
+
+region = sleplet.slepian.Region(mask_name="south_america")
+f = sleplet.functions.SlepianWavelets(L, region=region, B=B, j_min=J_MIN, j=J)
+f_sphere = sleplet.slepian_methods.slepian_inverse(f.coefficients, f.L, f.slepian)
+sleplet.plotting.PlotSphere(
+    f_sphere,
+    f.L,
+    f"slepian_wavelets_south_america_{B}B_{J_MIN}jmin_{J_MIN+J}j_L{L}",
+    normalise=False,
+    region=f.region,
+).execute()
+```
+
+![Slepian Wavelet j=2]({{ site.url }}/images/sleplet/slepian_wavelets_south_america_3B_2jmin_2j_L128_res512_real.png)
+
+### CLI Usage
+
+The demonstrates the first wavelet (ignoring the scaling function) of the head
+region of a Homer Simpson mesh for a per-vertex normals field.
+
+```sh
+mesh homer -e 3 2 0 -m slepian_wavelet_coefficients -u -z
+```
+
+![Slepian Mesh Wavelet Coefficients j=2]({{ site.url }}/images/sleplet/slepian_wavelet_coefficients_homer_3B_2jmin_2j_zoom.png)
+
+## Citing
+
+If you use `SLEPLET` in your research, please cite the paper.
+
+```bibtex
+@article{Roddy2023,
+  title   = {%raw%}{{SLEPLET: Slepian Scale-Discretised Wavelets in Python}}{%endraw%},
+  author  = {Roddy, Patrick J.},
+  year    = 2023,
+  journal = {Journal of Open Source Software},
+  volume  = 8,
+  number  = 84,
+  pages   = 5221,
+  doi     = {10.21105/joss.05221},
+}
+```
+
+Please also cite [S2LET](https://doi.org/10.1051/0004-6361/201220729) upon which
+`SLEPLET` is built, along with [SSHT](https://doi.org/10.1109/TSP.2011.2166394)
+in the spherical setting or [libigl](https://doi.org/10.1145/3134472.3134497) in
+the mesh setting.
+
+## Acknowledgements
+
+The author would like to thank Jason D. McEwen for his advice and guidance on
+the mathematics behind `SLEPLET`. Further, the author would like to thank Zubair
+Khalid for providing his `MATLAB` implementation to compute the Slepian
+functions of a polar cap region, as well as the formulation for a limited
+colatitude-longitude region. `SLEPLET` makes use of several libraries the author
+would like to acknowledge, in particular,
+[libigl](https://github.com/libigl/libigl-python-bindings),
+[NumPy](https://github.com/numpy/numpy), `plotly`, `SSHT`,
+[S2LET](https://github.com/astro-informatics/s2let).
diff --git a/content/blog/2024-06-05-friends-dont-let-friends-package-alone-pyconus-24.md b/content/blog/2024-06-05-friends-dont-let-friends-package-alone-pyconus-24.md
new file mode 100644
index 00000000..f2ee5510
--- /dev/null
+++ b/content/blog/2024-06-05-friends-dont-let-friends-package-alone-pyconus-24.md
@@ -0,0 +1,258 @@
+---
+title: Friends don't let friends package alone- my Python packaging talk at PyCon
+  2024
+date: '2024-06-05'
+type: blog
+excerpt: A blog post from the Executive Director of pyOpenSci on Python packaging,
+  technical things and imposter syndrome in data science.
+author: Leah Wasser
+blog_topic: learn
+toc: true
+comments: true
+url: "/blog/python-packaging-friends-dont-let-friends-package-alone.html"
+lastmod: '2024-08-29'
+---
+
+## <i class="fa-solid fa-heart"></i>  Python packaging and community: my first talk at PyCon US 2024
+
+This year I gave my first talk in the [PyCon US](https://us.pycon.org/2024/) main track! For context, PyCon US is a big meeting—with over 2,700 registrations this year—a record for the event! My talk was about my experiences navigating the packaging ecosystem from a few perspectives:
+
+* Teaching scientists how to share their code,
+* As a maintainer of a smaller Python package—stravalib and
+* Founder and Executive Director of a non profit organization - pyOpenSci - which strives to support scientists in tackling the world's greatest challenges using open software and workflows.
+
+The irony of these three  different perspectives is that the challenges that users face in each category are similar! Below I explore my experiences pulling together the talk.
+
+You can also watch the talk here:
+
+### My early experiences with Python packaging
+
+I started thinking about Python packaging in 2018 during our [early pyOpenSci
+community meetings](https://www.pyopensci.org/handbook/reference/index.html). In these meetings, we were trying to create an [open peer
+review process for scientific Python software](https://www.pyopensci.org/about-peer-review/index.html). A process that is running today
+with 17 scientific Python packages currently [in some state of review](https://github.com/pyOpenSci/software-submission/issues) as write
+this post.
+
+As someone who was teaching Python to beginners and dabbling in creating
+and maintaining packages to support teaching, packaging was this somewhat
+undefined space. I wasn’t sure where to begin or what sources were truly
+authoritative. Generally, my approach to packaging was copying the
+infrastructure that other package maintainers I trusted used—mainly GeoPandas.
+
+*I am a spatial data nerd at heart.*
+
+{{< figure src="images/blog/2024/june/pycon-python-packaging-confusion.png" alt="Image that says have you ever felt confused about python packaging. Below is the pyopensci flower logo. And the graphic shows a bunch of different cartoon like hands being raised.' style='width: 90%;" caption="Every time I ask this question, a majority of people in the room raise their hand." >}}
+
+But as I thought about creating pyOpenSci's open peer review process, I knew
+scientists would need a process that:
+
+* Enforced “good enough” practices in scientific Python packaging
+* Was not overly-binding, but also set users up for success
+
+I also knew that:
+
+* We needed to create some sort of packaging guide that set up expectations for our pyOpenSci open peer review of software process, and that
+* I wasn't the lead expert in the room. Thus, we needed people from across the (scientific) Python ecosystem and beyond to build consensus and define what
+were “good enough” practices.
+
+But how could pyOpenSci in these early years, as a not-yet-created community, empower people to
+navigate a tricky, if not complex, ecosystem empowered by choice?
+
+## Choice is a value in the Python ecosystem
+
+In the Python ecosystem, choice is a value.
+
+Why?
+
+Because the Python language is used across many different domains and for lots of different reasons. And further, Python is a “glue” language. This means that it can wrap around other languages like C—making it even more flexible.
+
+This flexibility warrants choice. It’s almost by design.
+
+And I value choice too.
+
+## Too much of a good thing? Too many choices?
+
+**Choice is great but it's not necessarily beginner friendly.** Choice leaves too much room for uncertainty as a beginner. And uncertainty just makes learning more stressful.
+
+As my mentor and colleague Carol likes to say:
+
+> choice is an opportunity for someone to make the wrong decision
+
+So if you think about that "opportunity to make a wrong decision", imagine what happens if you have multiple choices that lead you down a terrifying path of uncertainty! <i class="fa-solid fa-ghost"></i>
+
+{{< figure src="images/blog/2024/june/pycon-python-packaging-too-many-options.png" alt="Image of a flat coated retriever lying down with a purple ice bag on its head looking sad.' style='width: 90%;" caption="Too many choices can lead to frustration for many users that are learning a new technical thing. More biscuits—or early wins—are more empowering for a learner and set them up for success." >}}
+
+### The evolution of the pyOpenSci Python packaging guide
+
+Years later, what started out as a generic Python development guide, was
+transformed into what’s now the [pyOpenSci Python package guide](https://www.pyopensci.org/python-package-guide/).
+
+* A guidebook that has 58 contributors as I’m writing this post today.
+* A guidebook that has color and graphics and that leads Pythonistas down a
+  singular, opinionated path to Python packaging success.
+* A guidebook that breaks down pieces and processes into their fundamentals and
+  explains them using digestible words.
+
+The pyOpenSci path is not the only path. It is just a path that works and
+enables early wins for scientists and others using Python.
+
+If you're reading this and you have your own path, that's OK too. But if you
+want to worry less about decisions and have a definitive way of doing things
+that follows modern standards -
+
+we've got you.
+
+### A packaging guidebook created by community
+
+This guidebook was created by a community of people with beginner to expert packaging experience with the goal of building consensus
+around a single approach to pure Python packaging that would **yield user success**.
+
+Together we created a guidebook that acknowledges a suite of fantastic tools across the ecosystem, while
+still leading users down a streamlined path.
+
+{{< figure src="images/blog/2024/june/pyopensci-packaging-guide-overview.png" alt="Image with the pyOpenSci flower logo in the upper right hand corner. The image shows the packaging lifecycle. The graphic shows a high level overview of the elements of a Python package. the inside circle has 5 items - user documentation, code/api, test suite, contributor documentation, project metadata / license / readme. In the middle of the circle is says maintainers and has a small icon with people. on the outside circle there is an arrow and it says infrastructure.' style='width: 70%;" caption="<i class='fa-solid fa-heart-pulse'></i> The generalized scientific Python package development process. <i class='fa-solid fa-heart-pulse'></i>." >}}
+
+## Getting accepted to talk about packaging...  <i class="fa-solid fa-ghost"></i>
+
+I was thrilled and terrified to be accepted to give a talk at [PyCon US](https://us.pycon.org/2024/), in Pittsburgh, Pennsylvania, on the process of creating the pyOpenSci Python packaging guidebook . My talk was called:
+
+“Friends don’t let friends package alone”
+
+It was all about the process of navigating the Python packaging ecosystem and
+then creating the guide. While you might assume such a talk about be technical,
+in reality, it was all about people.
+
+### Me and the child-like imposter inside
+
+Giving this talk was a big deal for me. Imposter syndrome—the feeling that I
+didn't belong, that I wasn't technical enough to build pyOpenSci—has always been
+my reality. As a trained Landscape Architect, I spent most of my college and early graduate years
+practicing perfect lettering, using markers, fancy pens and colored pencils  to bring creative
+landscape visions to life. I think moved on to get an advanced degree in ecology.
+
+I remember vividly almost crying when I tried to read and understand my first scientific paper.
+
+...talk about jargon and technical terms!
+
+Now, I consider myself a Pythonista, coder, data scientist, and tech
+geek. I've bounced around across different data science languages.
+
+AND, I’m very aware of how much more others know than I do about lots of
+different topics—including packaging.
+
+I wasn’t sure what it would be like to be on that big pyCon US presentation stage, in that big room full of chairs. Would they be empty? Luckily, I was able to focus on my friends sitting in the front rows.
+
+Carol, Hugo, Jeremiah, and Inessa—they were all there.
+
+Carol told me to lean into the teacher inside of me. I know that teacher best. My body calmed as I remembered why I was there. To help the community move forward.
+
+And similar to how we created our packaging guide—my friends got me through it.
+
+## The core messages in my talk
+
+In my talk, I shared my experiences as a maintainer of [stravalib](https://github.com/stravalib/stravalib). How
+challenging it was to figure out the best packaging infrastructure for our team.
+However, that experience of rebuilding stravalib also empowered me to better understand the pain points
+in the ecosystem from a "beginner and real world application lens." From a lens of "I just need to create a
+package and publish / release it to PyPI regularly."
+
+From a lens of—I am technical but I need to learn new-to-me packaging tools
+and workflows.
+
+{{< figure src="images/blog/2024/june/pyopensci-maintainer-python-packaging-frustration.png" alt="Image of a stressed out looing stick figure typing at a computer. On the left is says Maintainers Perspective.' style='width: 80%;" caption="<i class='fa-solid fa-heart-pulse'></i> Even as technical maintainers, the folks on the stravalib team weren't packaging experts. Why would they be? They are focused on writing good usable code (and tests). <i class='fa-solid fa-heart-pulse'></i>." >}}
+
+## Fundamental first—How to make a technical ecosystem beginner accessible
+
+How do we collectively support and empower people who don't want to become
+packaging gurus to be successful?
+
+My approach to helping beginners tackle hard technical problems has always been
+about breaking things down into their simplest forms first.
+
+I thrive on those “ah ha” moments when a tough concept clicks.
+
+And someone gets it.
+
+Sometimes, that someone is me — before I can teach the topic to others!
+
+## So what about packaging with friends?
+
+The essence of my Python packaging talk was the work that I have lead alongside the pyOpenSci community to demystify and help *people* navigate the complex Python packaging ecosystem.
+
+This work was really about people helping people tackle challenging things.
+
+Python packaging matters because scientists need open software to create open and reproducible workflows to build upon each other's work, and to tackle the world's hardest challenges more efficiently and effectively.
+
+Among other things, pyOpenSci reviews software <link> as a constructive way to help scientists both create better software and get credit for the important work they are doing.
+
+The pyOpenSci community has created a Python package guide that harnesses the expertise, opinions, and experiences of 61+ people.
+
+This guide provides:
+
+* A beginner-friendly overview of the packaging ecosystem combined with a
+* Start-to-finish tutorial that uses [Hatch](https://hatch.pypa.io/) to create a Python package.
+
+Python is known for its incredible community, so it only made sense to leverage that collective knowledge and experience to create a packaging guide. Packaging doesn’t have to be complex. Friends can help.
+
+The talk can be broken down into 4 takeaways:
+
+### People can help (*surprise*!)
+
+When tackling some of the most thorny technical Python problems, people can help. This might mean:
+
+* Learning together by working in a small supportive group to create your first Python package;
+* Bringing in experts to review and vet online resources to ensure they are accurate and accessible that support scientists worldwide in their packaging journey.
+* Also including beginners to ensure the content is accessible, understandable and usable.
+* Running a constructive peer review process where people volunteer their time to provide feedback on a package’s usability, function, and structure.
+
+In creating the guide, we knew we were tackling hard, complex technical problems. But also there is a tremendous amount of collective knowledge in this community that can be harnessed and focused on the problem at hand. By focusing people on the users of the guide first, rather than tools, we were able to build consensus.
+
+We were able to move forward together.
+
+{{< figure src="images/blog/2024/june/pyopensci-python-packaging-people-can-help.png" alt="Image on a dark purple background that says—people can help. below are two people stick figure like loking at each other and smiling while chatting.' style='width: 70%;" caption="<i class='fa-solid fa-heart-pulse'></i> When tackling Python's thorniest challenges, people can help. <i class='fa-solid fa-heart-pulse'></i>." >}}
+
+### Create early wins for users
+
+As an educator, I’ve always known that the best way to empower someone new to any topic is to create a learning environment where they quickly make progress. I’ve [collected data on what approaches work better than others](https://osf.io/preprints/osf/xdj4z). I’ve explored how certain presentations of information empower, while others break people down, triggering imposter syndrome and even isolation within a science field.
+
+The key is early wins.
+
+Early wins empower users to:
+
+* Want to do more
+* Feel like they belong and can be successful learning the skill at hand
+* Try again and expand their knowledge
+* Even help their colleagues, which is the biggest win of all.
+
+High quality documentation (or tutorials) helps users achieve this by providing quickstarts and resources that ensure they can get up and running quickly and have early positive experiences.
+
+{{< figure src="images/blog/2024/june/pyopensci-python-packaging-create-early-wins.png" alt="Image on a dark purple background that says Create Early Wins in your docs. on the left is a stressed out stick figure typing at a computer. on the right is a relaxed stick figure typing away. ' style='width: 70%;" caption="<i class='fa-solid fa-heart-pulse'></i> By creating get-start workflows, tutorials and resources that users can easily reproduce and make progress using quickly, you are empowering beginners to stick with the task at hand. And you are building user confidence in the ecosystem. <i class='fa-solid fa-heart-pulse'></i>." >}}
+
+### Fundamentals First
+
+When teaching beginners, break things down to their fundamental concepts. In the case of packaging, this means explaining pure Python packaging in its most basic form, without immediately discussing tools. Notice that the diagram below doesn’t discuss tools at all!
+
+{{< figure src="images/blog/2024/june/pyopensci-python-packaging-fundamentals-first.png" alt="Dark purple image that says Fundamentals First. Below are 4 steps in the packaging process that say 1 create package structure, 2 add code, 3 add metadata to pyproject toml file and 4 pip install package. ' style='width: 70%;" caption="<i class='fa-solid fa-heart-pulse'></i> By breaking down packaging in to it's most basic steps you are making the concepts immediately more digestable to users. Once they understand the basics you can slowly layer in additional complexity. <i class='fa-solid fa-heart-pulse'></i>." >}}
+
+While some may think that this approach is over simplified, it’s not. The idea here is that you begin with digestible information that empowers a learner. You help them understand that they can do this! And then, and only then, you add more complexity when they are ready to absorb it.
+
+This also opens the door wide to early wins.
+
+### Just say no to TMO
+
+Avoid TMO—Too Many Options or Too Many Opinions at all costs when teaching beginners. Options are great, but when someone is new to a topic, it’s best to give them a straightforward path to success.
+
+Early on in creating our packaging guide, we found contributors, often quite expert in the packaging ecosystem, arguing about the best tools and best practices. Since we invited many people with different levels of experience to review our content, these arguments pushed some people away and created an unhealthy environment. Moderating these conversations to focus on the users and their needs, rather than debating tools, was critical. This approach helped create a truly beginner-friendly guide and fostered a review environment that was safe and inclusive, where both beginners and experts could contribute.
+
+{{< figure src="images/blog/2024/june/pyopensci-python-packaging-tmo.png" alt="Dark purple background image that says no TMO. Below is a yellow lab retriever with a purple ice bag on it's head looking sad and directly at you.' style='width: 100%;" caption="<i class='fa-solid fa-heart-pulse'></i> When it comes to packaging, too many options and too many opinions get in the way of a positive user experience. We need to work towards breaking things down and providing opinionated paths for those who want and need them. <i class='fa-solid fa-heart-pulse'></i>." >}}
+
+### Friends don’t let friends package alone
+
+When I finished my talk, I felt this sense of relief but also I felt love, support and deep passion for this topic and the community. It’s more than just packaging. It is about empowering people with skills that will help them tackle the biggest scientific challenges that we face as humans. Science is about data. And to process data we need tools - open tools that are accessible for scientists to learn and use. It’s about carving out space for scientists to build and use these tools. And also to make space for people who may feel like outsiders, because of who they are, to participate.
+
+I’m excited to have the privilege of moving the pyOpenSci mission forward, and of getting to connect with so many amazing people. I’m excited to continue to facilitate and support better science through better software and to empower more people with skills. And maybe, through this talk, a little piece of that child-like imposter within me has been chipped away!
+
+I’m human too. I need friends too.
+
+<!--
+You can watch the talk here: [Link to video]. -->
diff --git a/content/blog/2024-06-06-get-involved-with-pyos.md b/content/blog/2024-06-06-get-involved-with-pyos.md
new file mode 100644
index 00000000..ada9b397
--- /dev/null
+++ b/content/blog/2024-06-06-get-involved-with-pyos.md
@@ -0,0 +1,90 @@
+---
+title: Get Involved with pyOpenSci
+date: '2024-06-06'
+type: blog
+excerpt: 'Fun fact: there are a multitude of ways for you to get involved with pyOpenSci!
+  From social media to in-person events to joining our editoral team, this guide walks
+  you through every opportunity available.'
+author: Jesse Mostipak
+blog_topic: community
+toc: true
+comments: true
+url: "/blog/get-involved-with-pyos.html"
+lastmod: '2024-08-29'
+---
+
+## <i class="fa-regular fa-heart"></i> The pyOpenSci mission
+Founded in 2018 by our Executive Director, [Leah Wasser](https://github.com/lwasser), pyOpenSci builds diverse community that supports free and open Python tools for processing scientific data. We also build technical skills needed to contribute to open source and that support open science. While a diverse, inclusive community is at our core, radiating out from it are the three petals–how we accomplish our community goals–of pyOpenSci. These are:
+
+1. [Open peer review of scientific software](https://www.pyopensci.org/about-peer-review/index.html)
+2. [Community partnerships](https://www.pyopensci.org/partners.html)
+3. [Training and open educational resources](https://www.pyopensci.org/blog/pyos-education-announcement.html)
+
+## <i class="fa-solid fa-bullhorn"></i> Promote pyOpenSci online and in-person
+pyOpenSci is active on both [LinkedIn](https://www.linkedin.com/company/pyopensci) and [Fosstodon](https://fosstodon.org/@pyOpenSci), and you’re welcome to tag us on social media, as well as to [reach out with questions](mailto:media@pyopensci.org)! We also have [a series of brand assets and guidelines](https://docs.google.com/presentation/d/1glwf3BEPxo5H6pOHp6d55r2sbw8x-8kQZ9GzoLXwEDc/edit?usp=drive_link) if you need a copy of our logo, information on our fonts, and/or access to various illustrations we use.
+
+Are you attending a large, recognized, Python meeting that we will be unable to attend? Reach out to us! Dependent on timing, cost, and location, we’d also be more than happy to send you a set of pyOpenSci stickers to share! You can email us at [media@pyopensci.org](mailto:media@pyopensci.org) to inquire about the event you'll be attending.
+
+Please feel free to use any information from [our website](https://www.pyopensci.org/) to share about the work pyOpenSci is doing, and to reach out via [email](mailto:media@pyopensci.org) or on [LinkedIn](https://linkedin.com/company/pyopensci
+) or [Fosstodon](https://fosstodon.org/@pyOpenSci) with any questions. And don’t forget to share your personal experiences with pyOpenSci as well!
+
+## <i class="fa-solid fa-handshake-angle"></i> Volunteer with pyOpenSci
+If you're looking to be more hands-on with pyOpenSci, consider joining our [Review Team](https://www.pyopensci.org/software-peer-review/how-to/reviewer-guide.html) or [Editorial Board](https://www.pyopensci.org/software-peer-review/how-to/editors-guide.html), digging into some code and working from our Help Wanted board, or writing a guest blog post!
+
+### pyOpenSci's Review Team
+pyOpenSci welcomes reviewers from a diversity of backgrounds and with varying levels of Python technical expertise. Some of the basic things that we look for in a reviewer include:
+
+* Familiarity with using the Python programming language.
+* Ability to evaluate a Python package for usability and documentation quality.
+* Ability to provide a technical review of Python package structure and code quality/approach to solving the problems that the package seeks to address.
+
+We like to have a mix of technical and usability focus in our reviews so it’s ok if you don’t have all of the above skills! Reviewing code is an important skill, especially if you are working in a collaborative team environment (professionally or in academia). And if you are interested in peer review but have never reviewed before, we offer a [mentorship program](https://www.pyopensci.org/software-peer-review/how-to/reviewer-guide.html#a-guide-for-new-reviewers), where we will pair you up with someone who has more experience reviewing code. From this experience you can learn more and empower yourself with code review skills. Software review skills are generally useful in data science, so they are skills worth investing in!
+
+To join our review team, [fill out our reviewer form](https://docs.google.com/forms/d/e/1FAIpQLSeVf-L_1-jYeO84OvEE8UemEoCmIiD5ddP_aO8S90vb7srADQ/viewform). We will contact you if we have a package that we need reviewers for. It’s OK if you’ve never reviewed a package before! We’ll walk you through it.
+
+### pyOpenSci's Editorial Team
+The pyOpenSci [Editorial Board](https://www.pyopensci.org/about-peer-review/index.html#meet-our-editorial-board) is comprised of a diverse group of volunteers, with each editor being responsible for the following tasks:
+
+* Finding reviewers from diverse backgrounds who have a mixture of scientific domain and Python experience.
+* Overseeing the entire review process for a package ensuring it runs in a timely and efficient manner.
+* Supporting the submitting authors and reviewers in answering questions related to the review.
+* Determining whether that package should be accepted into the pyOpenSci ecosystem once the review has wrapped up.
+
+It's critical to our mission that our Editorial Board have a combined expertise in various scientific domains, technical expertise in Python packaging, awareness of the importance of documentation in package usability, and awareness of the importance of CI/test suites in order to ensure robust software development. We do not expect any single editor to be an expert in all of these areas!
+
+### Apply to be a pyOpenSci editor
+As of May 2024, pyOpenSci looking for editors from a wide variety of scientific backgrounds due to an increased number of package submissions. If you feel you'd be a good fit for the pyOpenSci Editorial Board, please fill out [this form](https://docs.google.com/forms/d/e/1FAIpQLScRQHQ7NKVEAG3BKAphiUdVFvQ5nkez0IpyXBMZDzXjuBPloQ/viewform). We're looking to fill several volunteer spots, and will be accepting applications through June and July.
+
+If you're interested in joining our Editorial Board, but have questions or would like to chat with someone from pyOpenSci about volunteering to be an editor, please email us at [media@pyopensci.org](mailto:media@pyopensci.org).
+
+### Contribute to pyOpenSci
+do you want to contribute to an open source project that is supporting other open science projects? We need your help! Check out our [GitHub Help Wanted board](https://github.com/orgs/pyOpenSci/projects/3), where we have a wide variety of issues, ranging from highly technical to beginner-friendly. The status column makes it easy to identify the issue category, and the label column helps to further clarify any needs around the issue.
+
+All contributors are credited and recognized on the [pyOpenSci website](https://www.pyopensci.org/).
+
+### Write a guest blog post for pyOpenSci
+We are always looking for guest bloggers on [the pyOpenSci blog](https://www.pyopensci.org/blog/index.html)! If you’d like to write about a pyOpenSci package that has been accepted into our ecosystem, your experiences with pyOpenSci, or how you’re using free and open Python tools in your scientific endeavors, we’d love to hear from you! Email our Community team at [media@pyopensci.org](mailto:media@pyopensci.org) for more information.
+
+## <i class="fa-solid fa-circle-chevron-down"></i> Submit a package to pyOpenSci
+pyOpenSci’s suite of packages are contributed by community members with a great diversity of skills and backgrounds. This diversity of developer backgrounds enables us to vet and promote a broad ecosystem of high quality tools that supports scientists across domains with a suite of different data types and structures.
+
+pyOpenSci packages are reviewed for quality, fit, scope, documentation and usability. The review process is similar to a manuscript review, however it has a stronger focus on Python packaging best practices.
+
+Unlike a manuscript review, our peer review process is an ongoing conversation. Once all major issues and questions are addressed, the review editor package will make a decision to accept, hold, or reject the package.
+
+Rejections are usually done early in the process, before the review process begins. In rare cases a package may also not be on-boarded into the pyOpenSci ecosystem after review & revision.
+
+To submit a package to pyOpenSci, [open an issue in our peer review GitHub repository](https://github.com/pyOpenSci/software-submission/issues/new/choose). Not sure if your package is in-scope? Then submit a [pre-submission inquiry](https://github.com/pyOpenSci/software-submission/issues/new/choose), and an editor will be in touch!
+
+Learn more about our Open Peer Review process in our [Peer Review Guide!](https://www.pyopensci.org/software-peer-review/about/intro.html)
+
+## <i class="fa-solid fa-person-running"></i> Run a pyOpenSci sprint
+Consider hosting a sprint, which is a time to come together with colleagues to collaborate on contributing to pyOpenSci.
+
+Get in touch with us at least two weeks in advance so we know when the sprint is happening, and can support you in holding it! You can contact us at [media@pyopensci.org](mailto:media@pyopensci.org).
+
+We'll be sharing more information in a separate post with more details on how to run a pyOpenSci sprint, either online or in-person!
+
+## <i class="fa-solid fa-link"></i> Connect with pyOpenSci
+​​We are thrilled, honored, and humbled that you’re interested in getting involved with pyOpenSci, and created this guide with the intention of providing a resource on all the ways available to get involved with us. You can stay up-to-date with all things pyOpenSci by following us on [LinkedIn](https://linkedin.com/company/pyopensci
+) and [Fosstodon](https://fosstodon.org/@pyOpenSci). And if you’re interested in our weekly newsletter where we share news, blog posts, and monthly updates, [subscribe on LinkedIn](https://www.bit.ly/pyOSNewsletter).
diff --git a/content/blog/2024-06-20-pyos-guide-to-scipy.md b/content/blog/2024-06-20-pyos-guide-to-scipy.md
new file mode 100644
index 00000000..ab1a4d38
--- /dev/null
+++ b/content/blog/2024-06-20-pyos-guide-to-scipy.md
@@ -0,0 +1,82 @@
+---
+title: pyOpenSci's Guide to SciPy
+date: '2024-06-20'
+type: blog
+excerpt: We've got another incredible conference on the horizon, and wanted to share
+  the talks, workshops, and sprints where you can find members of the pyOpenSci community!
+author: Jesse Mostipak
+blog_topic: learn
+toc: true
+comments: true
+url: "/blog/pyos-guide-to-scipy-2024.html"
+lastmod: '2024-08-29'
+---
+
+## <i class="fa-regular fa-handshake"></i> See you at SciPy!
+
+[SciPy 2024](https://www.scipy2024.scipy.org/) is just around the corner. We can’t wait to see you there! We’re pulling together our pyOpenSci Guide to SciPy, similar to the guide we did for [PyCon 2024](https://www.pyopensci.org/blog/pyos-guide-to-pyconus-2024.html), and wanted to give you a preview of some of the tutorials and talks being given by pyOpenSci Community members!
+
+## <i class="fa-solid fa-chalkboard-user"></i> Tutorials
+
+### [Interactive data visualizations with Bokeh (in 2024)](https://cfp.scipy.org/2024/talk/JRLMLD/)
+Along with Timo Metzger and Bryan Van de Ven, pyOpenSci community member [Pavithra Eswaramoorthy](https://www.linkedin.com/in/pavithraes/) will be covering everything you need to know to create beautiful and powerful interactive plots from scratch using Bokeh’s latest features. Starting with a quick introduction of Bokeh’s core concepts, the team will cover creating and customizing simple static plots like line and bar charts before introducing layers of interactivity, creating specialized plotting features like geographic maps, contour plots, Mathematical Text, and discussing new additions to Bokeh like ImageStacks. By the end, you will be able to create a complete interactive dashboard using Bokeh.
+
+### [3D Visualization with PyVista](https://cfp.scipy.org/2024/talk/GKGRWE/)
+Led by Tetsuo Koyama, Alexander Kaszynski, Bill Little, and pyOpenSci peer review spatial editor [Bane Sullivan](https://www.linkedin.com/in/bane-sullivan/), this tutorial demonstrates [PyVista’s](https://github.com/pyvista/pyvista) latest capabilities and bring a wide range of users to the forefront of 3D visualization in Python, including:
+* Use PyVista to create 3D visualizations from a variety of datasets in common formats.
+* Overview the classes and data structures of PyVista with real-world examples.
+* Be familiar of the various filters and features of PyVista.
+* Know which Python libraries are used and can be used by PyVista (meshio, trimesh etc).
+* We see this tutorial catering to anyone who wants to visualize data in any domain, and this ranges from basic Python users to advanced power users.
+
+### [From RAGS to riches: Build an AI document inquiry web-app](https://cfp.scipy.org/2024/talk/W3ZJWG/)
+Pavithra Eswaramoorthy, a Developer Advocate at [Quansight](https://quansight.com/), is teaming up with Dharhas Pothina and Andrew Huang to cover how to use RAG to build document-inquiry chat systems using different commercial and locally running LLMs. The topics we’ll cover include:
+* **Introduction to RAG**, how it works and interacts with LLMs, and Ragna - a framework for RAG orchestration
+* **Creating and optimizing a basic chat function** that uses popular LLMs (like GPT) answers questions about your documents, using a Python API in Jupyter Notebooks
+* **Running a local LLM on GPUs** on the provided platform, and comparing its performance to commercial LLMs
+* **Introduction to Panel**, by creating a basic chat UI for Ragna using Panel’s ChatBox widget
+* **Building and deploying a Panel-based web-app**, which extends the basic chat UI and includes more application components
+
+By the end of this tutorial, you will have an understanding of the fundamental components that form a RAG model, and practical knowledge of open source tools that can help you or your organization explore and build on your own applications. This tutorial is designed to enable enthusiasts in our community to explore an interesting topic using some beginner-friendly Python libraries.
+
+By the end of this tutorial, you will have an understanding of the fundamental components that form a RAG model, and practical knowledge of open source tools that can help you or your organization explore and build on your own applications. This tutorial is designed to enable enthusiasts in our community to explore an interesting topic using some beginner-friendly Python libraries.
+
+### [Create Your First Python Package: Make Your Python Code Easier to Share and Use](https://cfp.scipy.org/2024/talk/QT9GBY/)
+Led by pyOpenSci’s Executive Director and Founder, [Leah Wasser](https://github.com/lwasser), along with pyOpenSci editor Isabel Zimmerman and Jeremiah Page, who leads work on the [pyOpenSci packaging guide](https://www.pyopensci.org/python-package-guide/index.html), this tutorial session will teach you how to:
+* Create code that can be installed into different environments
+* Use [Hatch](https://hatch.pypa.io/latest/) as a workflow tool, making setup and installation of your code easier
+* Use Hatch to publish your package to (test) PyPI
+
+Creating code that can be shared and reused is the gold-standard of open science. But tools and skills to share your code can be tricky to learn. In this hands-on tutorial, you’ll learn how to turn your code into an installable Python module ( a file containing Python code that defines functions, classes, and variables), that can be shared with others. We will provide pre-built code and module examples for each step of the tutorial to make it more beginner-friendly. However, to get the most out of this tutorial, you should be familiar with writing Python code, writing and using functions and you should understand the concept of Python environments. You should also have Python and Hatch installed on your computer prior to attending. If you are newer to environments and don’t have a preferred tool, then we recommend that you use conda. However, any environment tool that you prefer works well.
+
+> Interested in helping out with our Packaging workshop? Reach out to us at [media@pyopensci.org](mailto:media@pyopensci.org). We’re looking for volunteers to assist learners throughout the workshop.
+
+### [Data of an Unusual Size (2024 edition): A practical guide to analysis and interactive visualization of massive datasets](https://cfp.scipy.org/2024/talk/UKLNLQ/)
+
+Pavithra Eswaramoorthy and Dharhas Pothina, both from [Quansight](https://quansight.com/), will help you learn the fundamentals of analyzing massive datasets with real-world examples on actual powerful machines on a public cloud provided by the presenters – starting from how the data is stored and read, to how it is processed and visualized.
+
+## <i class="fa-regular fa-comments"></i> Talks
+
+### [The power of community in solving scientific Python’s most challenging problems](https://cfp.scipy.org/2024/talk/AMTLJ7/)
+This talk from our Executive Director and Founder, [Leah Wasser](https://github.com/lwasser), shares pyOpenSci’s knowledge in building a constructive open peer review process that supports maintainers, and also resources that make Python packaging more accessible and easier-to-navigate. Our insights are based on five years of experience working with over 200 community members, who have evaluated 58 packages developed by over 56 package maintainers.
+
+> Leah’s talk is about writing the [pyOpenSci Python Packaging Guide](https://www.pyopensci.org/python-package-guide/) via community!
+
+### [Great Tables for Everyone](https://cfp.scipy.org/2024/talk/BRMQRW/)
+This talk from [Richard Iannone](https://www.linkedin.com/in/richard-iannone-a5640017/), whose package [Great Tables](https://posit-dev.github.io/great-tables/articles/intro.html) is currently [under review with pyOpenSci](https://github.com/pyOpenSci/software-submission/issues/202), will provide a demonstration of Great Tables, showing how data can come alive in when in tabular form. We’ll use data from the fields of meteorology, chemistry, and the atmospheric sciences within our table-making examples. We’ll learn how the different components of a table (e.g., the column labels, the header, etc.) can be manipulated to best convey the data. We believe tables are worthy of being deemed data visualizations and we hope that Great Tables can become an indispensable tool in your data analysis workflow.
+
+### [From Code to Clarity: Using Quarto for Python Documentation](https://cfp.scipy.org/2024/talk/GFGSTS/)
+[Isabel Zimmerman](https://www.linkedin.com/in/isabel-zimmerman/), a member of our triage team, editor, and an Emeritus Editor in Chief, will be speaking from her experiences as an open source developer who works with multilingual tools, and how Quarto + quartodoc helped to fill those gaps. This talk is intended for anyone who might have to communicate with stakeholders through code using a web-based format. She’ll be focusing on Python package documentation websites, but the stories and examples expose the difficulties in many types of technical communication. The intent is to have a lighthearted talk filled with examples of how to make technical communication and publishing easier and more accessible.
+
+### [Vector space embeddings and data maps for cyber defense](https://cfp.scipy.org/2024/talk/STUXTH/)
+pyOpenSci community member [Benoit Hamelin](https://www.linkedin.com/in/benoit-hamelin-43a44668/) will cover how the vast amounts of information of interest to cyber defense organizations comes in the form of unstructured data; from host-based telemetry and malware binaries, to phishing emails and network packet sequences. All of this data is extremely challenging to analyze. In recent years there have been huge advances in the methodology for converting unstructured media into vectors. However, leveraging such techniques for cyber defense data remains a challenge.
+Imposing structure on unstructured data allows us to leverage powerful data science and machine learning tools. Structure can be imposed in multiple ways, but vector space representations, with a meaningful distance measure, have proven to be one of the most fruitful.
+In this talk, he will demonstrate a number of techniques for embedding cyber defense data into vector spaces, as well as discuss how to leverage manifold learning techniques, clustering, and interactive data visualization to broaden our understanding of the data and enrich it with expert feedback.
+
+## <i class="fa-solid fa-person-running"></i> Sprints
+We’ll also be holding a pyOpenSci sprint at SciPy 2024! Be sure to follow us on [LinkedIn](https://www.linkedin.com/company/pyopensci) and [Fosstodon](https://fosstodon.org/@pyOpenSci) for more details!
+
+## <i class="fa-solid fa-link"></i> Connect with pyOpenSci
+
+Stay up-to-date with all things pyOpenSci by following us on [LinkedIn](https://linkedin.com/company/pyopensci
+) and [Fosstodon](https://fosstodon.org/@pyOpenSci). If you’re interested in our weekly newsletter where we share news, blog posts, and monthly updates, [subscribe on LinkedIn](https://www.bit.ly/pyOSNewsletter).
diff --git a/content/blog/2024-07-10-automata.md b/content/blog/2024-07-10-automata.md
new file mode 100644
index 00000000..8228b2e8
--- /dev/null
+++ b/content/blog/2024-07-10-automata.md
@@ -0,0 +1,123 @@
+---
+title: 'automata: Simulation and manipulation'
+date: '2024-07-10'
+type: blog
+excerpt: automata is a package implementing structures and algorithms for manipulating
+  finite automata, pushdown automata, and Turing machines, that was recently accepted
+  into the pyOpenSci ecosystem.
+author: Eliot W. Robson
+blog_topic: software
+comments: true
+url: "/blog/automata.html"
+lastmod: '2024-08-29'
+image:
+  src: images/blog/headers/automata-header.png
+  alt: 'automata: Simulation and manipulation'
+---
+
+Automata are abstract machines used to represent models of computation, and are a central object of study in theoretical computer science. Given an input string of characters over a fixed alphabet, these machines either accept or reject the string. A language corresponding to an automaton is
+the set of all strings it accepts. Three important families of automata in increasing order of generality are the following:
+
+1. Finite-state automata
+2. Pushdown automata
+3. Turing machines
+
+The [`automata`](https://caleb531.github.io/automata/) package facilitates working with these families by allowing simulation of reading input and higher-level manipulation
+of the corresponding languages using specialized algorithms. For an overview on automata theory, see [this Wikipedia article](https://en.wikipedia.org/wiki/Automata_theory), and
+for a more comprehensive introduction to each of these topics, see [these lecture notes](https://jeffe.cs.illinois.edu/teaching/algorithms/#models).
+
+## Statement of need
+
+Automata are a core component of both computer science education and research, seeing further theoretical work
+and applications in a wide variety of areas such as computational biology and networking.
+Consequently, the manipulation of automata with software packages has seen significant attention from
+researchers in the past. The similarly named Mathematica package [`Automata`](https://www.cs.cmu.edu/~sutner/automata.html) implements a number of
+algorithms for use with finite-state automata, including regular expression conversion and binary set operations.
+In Java, the [Brics package](https://www.brics.dk/automaton/) implements similar algorithms, while the [JFLAP package](https://www.jflap.org/) places an emphasis
+on interactivity and simulation of more general families of automata.
+
+[`automata`](https://caleb531.github.io/automata/) serves the demand for such a package in the Python software ecosystem, implementing algorithms and allowing for
+simulation of automata in a manner comparable to the packages described previously. As a popular high-level language, Python enables
+significant flexibility and ease of use that directly benefits many users. The package includes a comprehensive test suite,
+support for modern language features (including type annotations), and has a large number of different automata,
+meeting the demands of users across a wide variety of use cases. In particular, the target audience
+is both researchers that wish to manipulate automata, and for those in educational contexts to reinforce understanding about how these
+models of computation function.
+
+## Package features
+
+The API of the package is designed to mimic the formal mathematical description of each automaton using built-in Python data structures
+(such as sets and dicts). This is for ease of use by those that are unfamiliar with these models of computation, while also providing performance
+suitable for tasks arising in research. In particular, algorithms in the package have been written for tackling
+performance on large inputs, incorporating optimizations such as only exploring the reachable set of states
+in the construction of a new finite-state automaton. The package also has native display integration with Jupyter
+notebooks, enabling easy visualization that allows students to interact with [`automata`](https://caleb531.github.io/automata/) in an exploratory manner.
+
+Of note are some commonly used and technical algorithms implemented in the package for finite-state automata:
+
+- An optimized version of the Hopcroft-Karp algorithm to determine whether two deterministic finite automata (DFA) are equivalent.
+
+- The product construction algorithm for binary set operations (union, intersection, etc.) on the languages corresponding to two input DFAs.
+
+- Thompson's algorithm for converting regular expressions to equivalent nondeterministic finite automata (NFA).
+
+- Hopcroft's algorithm for DFA minimization.
+
+- A specialized algorithm for directly constructing a state-minimal DFA accepting a given finite language.
+
+- A specialized algorithm for directly constructing a minimal DFA recognizing strings containing a given substring.
+
+To the authors' knowledge, this is the only Python package implementing all of the automata manipulation algorithms stated above.
+
+## Example usage
+
+![A visualization of `target_words_dfa`. Transitions on characters leading to immediate rejections are omitted.]({{ site.url }}/images/automata/finite_language_dfa.png)
+
+The following example is inspired by the use case described in [this blog post](http://blog.notdot.net/2010/07/Damn-Cool-Algorithms-Levenshtein-Automata).
+We wish to determine which strings in a given set are within the target edit distance
+to a reference string. We will first initialize a DFA corresponding to a fixed set of target words
+over the alphabet of all lowercase ascii characters.
+
+```python
+from automata.fa.dfa import DFA
+from automata.fa.nfa import NFA
+import string
+
+target_words_dfa = DFA.from_finite_language(
+  input_symbols=set(string.ascii_lowercase),
+  language={'these', 'are', 'target', 'words', 'them', 'those'},
+)
+```
+
+Next, we construct an NFA recognizing all strings within a target edit distance of a fixed
+reference string, and then immediately convert this to an equivalent DFA. The package provides
+builtin functions to make this construction easy, and we use the same alphabet as the DFA that was just created.
+
+```python
+words_within_edit_distance_dfa = DFA.from_nfa(
+  NFA.edit_distance(
+    input_symbols=set(string.ascii_lowercase),
+    reference_str='they',
+    max_edit_distance=2,
+  )
+)
+```
+
+Finally, we take the intersection of the two DFAs we have constructed and read all of
+the words in the output DFA into a list. The library makes this straightforward and idiomatic.
+
+```python
+found_words_dfa = target_words_dfa & words_within_edit_distance_dfa
+found_words = list(found_words_dfa)
+```
+
+The DFA `found_words_dfa` accepts strings in the intersection of the languages of the
+DFAs given as input, and `found_words` is a list containing this language. Note the power of this
+technique is that the DFA `words_within_edit_distance_dfa`
+has an infinite language, meaning we could not do this same computation just using the builtin
+sets in Python directly (as they always represent a finite collection), although the
+syntax used by [`automata`](https://caleb531.github.io/automata/) is very similar to promote intuition.
+
+## Citing
+
+This post is adapted from [our JOSS paper](https://joss.theoj.org/papers/10.21105/joss.05759), which should be used for citations.
diff --git a/content/blog/2024-07-31-pyconus-pyopensci-sprints.md b/content/blog/2024-07-31-pyconus-pyopensci-sprints.md
new file mode 100644
index 00000000..5351be34
--- /dev/null
+++ b/content/blog/2024-07-31-pyconus-pyopensci-sprints.md
@@ -0,0 +1,364 @@
+---
+title: pyOpenSci beginner-friendly sprints at PyCon US 2024
+date: '2024-07-31'
+type: blog
+excerpt: pyOpenSci holds beginner-friendly sprints with the goal of making new contributors
+  feel welcome. Learn about our latest sprint at PyCon US 2024, and tips we use to
+  make sprints accessible to more people.
+author: Leah Wasser
+blog_topic: community
+toc: true
+comments: true
+url: "/blog/pyopensci-pyconus-2024-sprints.html"
+lastmod: '2024-08-29'
+image:
+  src: images/blog/headers/pycon-us-2024-header.png
+  alt: pyOpenSci beginner-friendly sprints at PyCon US 2024
+---
+
+## pyOpenSci's approach to beginner-friendly sprints
+
+In previous posts, I talked about:
+
+* Our [incredible experience at PyCon US 2024](/blog/recap-pyos-pyconus-2024.html).
+* My [personal experiences with the Python packaging ecosystem and building consensus
+  within the scientific Python community](/blog/python-packaging-friends-dont-let-friends-package-alone.html).
+
+Here, I will share with you what we have learned at pyOpenSci through holding
+beginner-friendly sprints over the past two years.
+Specifically, I want to
+explore the varied motivations and barriers associated with contributions to
+open source, and how pyOpenSci is addressing them.
+
+<div class="notice--success" markdown="1">
+
+## TL;DR
+
+* I believe that we can get more people involved in Open Source if it's done
+  the right way. Despite the word "open" in the name, open source is not
+  necessarily open to all people.
+* By setting up infrastructure such as project boards and tagging issues as
+  beginner-friendly, you are on your way towards a beginner-friendly sprint.
+* Be prepared to support people who are newer to Git and GitHub.
+* Create opportunities for beginners to contribute to documentation. The
+  beginner lens reviewing your docs is critical to ensuring the documentation
+  is usable! Documentation contributions can also be implemented entirely on
+  GitHub without needing to use the command line.
+
+
+
+</div>
+
+## PyOpenSci's [PyCon US 2024](https://us.pycon.org/2024/) sprint
+
+I've been running pyOpenSci sprints for about two years now. This year was my
+second year leading a PyCon US sprint for pyOpenSci. I've learned a lot! While
+last year we had two sprinters, this year we had a tremendous turnout of 18
+people from several countries and across the United States for our 1-day
+sprint. This resulted in over 35 issues and pull requests, where volunteers
+helped fix issues on our website, in our tutorials, and in our packaging and
+peer review guidebooks. Many long-standing issues and bugs were fixed thanks to
+this wonderful Python community.
+
+We had so much activity that I'm still working on closing up issues and pull
+requests now—weeks after the sprint ended!
+
+After such a tremendous experience this year, I wanted to share with you the
+things that we've learned at pyOpenSci about running beginner-friendly sprints.
+
+
+## What is a sprint like?
+
+If you haven’t been to a sprint before, it’s an experience every open source
+enthusiast should have. Sprints are where people come together to work on a
+project. The word sprint can also be used in a professional development setting. This might describe a team of developers working
+together to release a new feature. For the volunteer open source community, sprints often mean volunteers
+helping maintainers work on various parts of a project. And it's important to keep in mind that often the maintainers are
+also volunteers themselves.
+
+### What do people sprint on for pyOpenSci?
+
+pyOpenSci is a nonprofit organization that is devoted to building diverse and
+inclusive community that supports making science more open and collaborative.
+Among other things that we do, we run [open peer review of scientific Python software](/about-peer-review/index.html).
+
+Running an volunteer-lead open peer review process for software is a challenge. As we grow,
+it requires infrastructure to support tracking the process. We also create
+community driven beginner-friendly
+ [Python packaging resources](https://www.pyopensci.org/python-package-guide/) and
+ [tutorials](https://www.pyopensci.org/python-package-guide/tutorials/intro.html).
+High quality learning resources also require maintenance and review.
+As such, we always need a mixture of packaging experts and those newer to packaging
+to help catch errors and identify points of confusion.
+
+As the Executive Director and Founder of pyOpenSci, I created most of our
+pyOpenSci GitHub infrastructure to support our mission. While I cherish times
+when I can work on technical things, it’s hard to keep up.
+Mission, vision and community work will always come first.
+
+I really appreciate when community members help us tick off open issues,
+big and small. These contributions propel the pyOpenSci mission of making science
+more open and collaborative forward.
+
+### Contribution opportunities
+
+While barriers to contribution are abundant and hard, there are also many opportunities,
+including:
+
+* Learning and growing skills that may not be accessible in your day job.
+* Connecting with other developers, data scientists, and scientists in the community.
+* Engaging and being part of an online community or maintainer team.
+* Growing your professional network.
+* Learning about a new project.
+
+Or, maybe you're like me —- an Executive Director of a community organization.
+Coding and development aren't in my job description, but to teach these topics,
+I need to keep my skills fresh. And, I love to code. That's where open source
+comes into my life!
+
+{{< figure src="images/blog/2024/june/pyos-sprint-blog-learning.png" alt="A graphic that at the top says - Why people attend sprints. Below are a series of boxes with text in them and white stick figures standing or sitting on top or to the side of the boxes as decoration. The boxes say Learn new technical skills, connect with the community, help a project they care about, build their network, learn about a new tool, build confidence, +many other motivations. The graphic is on a dark purple background with the pyOpenSci logo on it.' style='width: 80%;" caption="People have many different motivations for attending sprints. Understanding those motivations can go a long way in the sprinter and the sprint leader(s) having a collectively successful experience." >}}
+
+## Barriers in contributing to open source
+
+While sprints are a great way to engage the community in supporting an
+organization's (or a project's) mission, there are many contributor barriers
+that sprint organizers need to consider.
+
+These barriers include:
+
+* Time to contribute.
+* Skills to contribute.
+* Confidence in skills / fear of contributing the wrong thing.
+* Privilege: This is a loaded one. Open source can't be diverse if it requires privilege.
+  to participate.
+
+And last but not least:
+
+* GitHub: Using Git and GitHub is always one of the biggest technical barriers
+that contributors encounter in their open source and data science journeys.
+
+
+### Challenges vs opportunities
+
+So how do we align the challenges that contributors face with the potential opportunities?
+
+While new contributor sprints are not for everyone, and assume some level of privilege
+in having the time and bandwidth to participate, they can be great for many.
+
+But a sprint will only be a good experience if the contributor's needs and goals are also considered. Contributors need to gain something
+from contributing, and this requires:
+
+* time and care in designing the sprint, and
+* time spent with newcomers during the sprint.
+
+It's also important to note that the time required to participate is also a privilege for
+many, if not most, maintainers who are already volunteering their time to maintain
+a project! As such we can't expect all open source packages to be able to
+support beginner contributions in a comprehensive way.
+
+However, if you do have the bandwidth to hold a sprint that embraces, empowers and uplifts those who are newer to open source, there
+is a lot to be learned from understanding learner motivations and types. And a few good experiences might mean that a beginner decides to stick around.
+
+## Contributing vs learning
+
+The educator inside of me can't help but align my experience in open source with
+learner motivations. For me personally, contributing to open source met two of my goals
+and interests:
+
+* **Applied (project-based) learning:** I love to learn. Coding and data science are my
+  happy places. But the learning needs to be directly applicable. If it isn't, I get bored. Moreover, if I can't see the application of the skill, I have little motivation to learn that skill!
+* **Student-directed learning:** I love to learn on my own time, following my own
+  processes that work for me. Open source allows me to do just that (and without the
+  pressures of a specific deadline in most cases).
+
+If you read the education literature, you will find both project-based learning and student-directed learning to be
+a commonly discussed topic—especially as it relates to empowering people who are underrepresented in a space.
+
+More on that next...
+
+### The power of project-based learning
+
+[Project-based learning](https://www.wpi.edu/project-based-learning/why-pbl) is
+founded on the idea that meaningful, applied projects are the best way to teach
+a topic. This works especially well in the data science space and has been found
+to be particularly effective with underrepresented groups. In fact, I implemented
+and collected data on this in a previous project
+that I designed and ran when I was in academia.
+
+The idea behind project-based learning is that students select a topic they are
+personally interested in. If they are learning data science, they can find data
+to analyze and support their project. For underrepresented groups in STEM (and
+most learners), applied learning resonates because it involves a topic they care
+about and are motivated to pursue. Skills are learned in the process of achieving
+a meaningful outcome.
+
+It's similar to how you can immediately engage a diverse audience in GIS
+(spatial data) with Google Earth by asking them to zoom into the area where they
+live (place-based learning).
+
+As a volunteer maintainer of [Stravalib](https://github.com/stravalib/stravalib),
+I am motivated to work on Stravalib because I learn in a very applied way.
+
+Sure, a sprint does not have the powerful outcome of a student understanding the
+impacts of climate change on their local tribal lands. But the concept is the same:
+
+> The learning motivation comes from a meaningful outcome that a student wants or
+> cares about.
+
+In leading a sprint, asking the question of "what are your goals for today?" will
+help you as a sprint leader to direct sprinter efforts down a successful path.
+
+
+### The power of student-directed learning
+
+Every person has different learning preferences. For many years, educators
+taught people the same way: in a classroom, using the same books and approaches.
+However, alternatives to this model allow learners to adapt their environment to
+their personal and learning goal needs.
+Student-directed learning
+is based on the idea that people learn differently and have different needs. By
+creating a hybrid learning environment where students are allowed to pick their
+learning path and approach, you empower them to own their experience.
+
+Some learners benefit from hands-on demos, whether in a classroom or at the
+sprint table. They may pick things up quickly or need to watch and digest the
+demo. Others prefer reading quietly on their own, absorbing information, and
+trying things out until they figure it out.
+
+If a sprint is set up correctly, learners can parse through available issues.
+Carefully tagged issues direct them to ones that are beginner-friendly. These
+issues should not require extensive Git and GitHub expertise, ensuring a good
+first experience and an early win to build confidence.
+
+Contributors at the sprint can decide if they need direction, mentorship, or
+just a short tutorial/guidebook for making their first contribution using the
+GitHub interface.
+
+
+### Collaborative Git and GitHub lessons
+
+This past year, I was awarded the [Better Scientific Software (BSSw)
+Fellowship](https://bssw.io/pages/bssw-fellowship-program), in which I proposed
+lessons on these lesser-known collaborative Git and GitHub skills—the same skills
+that will support people attending sprints! I am looking forward to having these
+lessons on hand for next year's sprints, in order to support those who are still
+fighting to learn Git and GitHub (it can be an uphill process!).
+
+## The anatomy of a pyOpenSci sprint
+
+Based on my understanding of the learning motivations and challenges that new
+contributors face, I've developed a pyOpenSci sprint approach that I've found to
+be successful in empowering new contributors to make their first contributions.
+
+### Create opportunities for first-time contributors
+
+When someone joins your sprint, start by asking:
+
+1. What are you looking to achieve today?
+2. How comfortable are you with Git and GitHub?
+
+If the contributor is new to Git and GitHub, it can be empowering to direct them
+to review documentation with a fresh perspective. In our pyOpenSci sprints,
+beginners often find bugs and issues in our online packaging tutorials. Fixing
+these bugs is empowering for new contributors and helps pyOpenSci curate useful,
+current, and beginner-friendly content.
+
+If you have a package, let the user review your tutorials or docs. They can then
+either open issues or pull requests to address the issues.
+
+The beauty of documentation reviews is that any issues and PRs submitted can be
+done entirely using the GitHub interface. This is a true win/win for both the
+maintainer and the contributor.
+
+### Write useful constructive issues
+
+{{< figure src="images/blog/2024/june/pyopensci-issue-specific.png" alt="Image that says 'have you ever felt confused about python packaging.' Below is the pyopensci flower logo. And the graphic shows a bunch of different cartoon like hands being raised.' style='width: 80%;" caption="This is an issue opened in our pyConUS 2024 sprint that could be addressed in a future sprint. Often before a sprint, our team will go into the existing issues and add more information related to next steps associated with the sprint. In this case - a beginner could take on testing out the Hatch installation instructions. They could also add a note that Hatch installs Python for a user if they don't already have it installed." >}}
+
+A good sprint begins with useful, labeled issues. The information in the body of
+an issue is critical. Be sure to include the specific details of the issue to be
+addressed with the lens of someone who is new to your project. Give potential
+contributors everything they need to start working, which helps reduce
+administrative questions during the sprint. For a table of 10-20 people sprinting
+for pyOpenSci, this means the sprint leader will have fewer questions to answer
+during the sprint event.
+
+### Label issues as help-wanted and/or sprintable
+
+{{< figure src="images/blog/2024/june/pyopensci-sprint-label-issues.png" alt="Graphic says Label issues with help-wanted / sprintable. Below it is a list of issues from the GitHub interface. One of the issues in the list is well labeled. It has 3 labels that say beginner-friendly, help wanted and then sprintable. Each has a different color.' style='width: 80%;" caption="We like to label issues as help-wanted and sprintable. A sprintable issue is a discrete issue that could be tackled (and ideally completed) during a sprint. A sprint's duration can span from a half day to multiple full days depending on the event. What is most important is that the issue is confined in some way so a single person could tackle it in a reasonable amount of time." >}}
+
+You never know when a contributor might be looking for a data science project to
+work on. It's always helpful to tag issues that could be completed or started
+during a sprint as `sprintable` and `help-wanted` if you think someone outside
+of your team could tackle the issue. This tip came from
+[Inessa Pawson](https://github.com/InessaPawson), who has extensive experience
+with contributors through her work on the
+[Contributor Experience Project](https://contributor-experience.org/).
+
+### Collect issues in a single place—the help-wanted board
+
+{{< figure src="images/blog/2024/june/pyopensci-sprint-project-board.png" alt="A graphic that shows the pyOpenSci GitHub project board. The graphic shows two columns of the project board. The first is Python Packaging and it has 7 issues in that column. The second column says Beginner-friendly / non technical. The point of this graphic is just to show a user that a project board is a nice way to organize issues that contributors might want to challenge during a sprint. At the bottom there is text that says includes a beginner-friendly column and should have easy-to-understand issue titles.' style='width: 80%;" caption="Project boards help you organize your sprintable tasks into categories that might help a contributor find something that interests them. Here we have a beginner-friendly column for beginners, but we also include columns that are topical such as Python programming, CI / DevOps and Sphinx. Also notice that the issues are generally clearly titled." >}}
+
+Curate a `help-wanted` board that contains all the issues that could be completed
+by an outside community member in one place.
+
+Our pyOpenSci `help-wanted` board is a
+[GitHub project board](https://github.com/orgs/pyOpenSci/projects/3/views/2)
+that allows us to organize issues that we think others could work on by type,
+including:
+
+* Beginner-friendly
+* Python
+* DevOps / CI
+
+### Infrastructure and automation of issues
+
+PyOpenSci has many GitHub repositories where people might label an issue as
+`help-wanted` and forget to add it to our sprint help-wanted project board. To
+address this, we set up
+a [CI workflow](https://github.com/pyOpenSci/pyopensci.github.io/blob/main/.github/workflows/add-help-wanted.yml)
+that can be added to any repository. This workflow moves any issue labeled
+`sprintable` or `help-wanted` to our help-wanted GitHub project board.
+
+**GitHub project boards support project workflows** that auto-add issues to a
+project board with a specific label. However, our GitHub organization's open source
+subscription only allows for one project workflow of this kind associated with one
+repository, which is why we set up the GitHub action. We also have things setup so an issue is removed / archived from the GitHub project board once it is closed.
+{: .notice}
+
+
+### Make it truly beginner-friendly
+
+To support beginners contributing to open source, consider having one or two
+helpers (depending on the size of your sprint) who can assist with:
+
+1. Understanding the issues
+2. Using Git/GitHub
+3. Directing novice sprinters to beginner-friendly items
+
+In all of our sprints to date, we have had a mixture of people who:
+
+1. Know Git and GitHub but haven't contributed to open source before. Sometimes
+   these people are developers and can tackle coding challenges!
+2. Are seasoned and just need enough information in the issue to be successful
+   (see above section on issue content).
+
+Other times, you have people who really want to contribute but are uncomfortable
+with Git and GitHub and have never contributed to open source. These people will
+be incredibly empowered if you can create a smooth path to their first
+contributions.
+
+## Wrap up
+
+Well-led sprints offer both new and seasoned contributors an opportunity to
+contribute to a project, while also learning new skills, connecting with new
+people, and learning about new projects. If you plan to support new
+contributors in your sprint, then it's ideal to do some legwork before the
+sprint begins to ensure sprint attendees feel supported and have the help that
+they need when they get stuck.
+
+pyOpenSci is looking forward to our next sprint—to be held at the [SciPy 2024
+meeting](https://www.scipy2024.scipy.org/) in Tacoma, Washington. Last year we
+had three people make their first contributions to open source in our SciPy
+2023 sprint. I'm hoping that this year is even better!
+
+Come join us if you are there!
diff --git a/content/blog/2024-08-02-community-news-august-2024.md b/content/blog/2024-08-02-community-news-august-2024.md
new file mode 100644
index 00000000..66965ef1
--- /dev/null
+++ b/content/blog/2024-08-02-community-news-august-2024.md
@@ -0,0 +1,67 @@
+---
+title: 'pyOpenSci Community News: August 2024'
+date: '2024-08-02'
+type: blog
+excerpt: Welcome to the first edition of pyOpenSci's Community News newsletter, where
+  we summarize and share conversations, contributions, and news related to our diverse
+  and vibrant community! Read on for insights into running pyOpenSci sprints, Python
+  packaging guide Spanish translation efforts, and using Hatch to create and maintain
+  Python.
+author: Jesse Mostipak
+blog_topic: updates
+toc: true
+comments: true
+url: "/blog/pyos-community-news-aug-2024.html"
+lastmod: '2024-08-29'
+image:
+  src: images/blog/headers/pycon-us-2024-header.png
+  alt: 'pyOpenSci Community News: August 2024'
+---
+
+## <i class="fa-regular fa-heart"></i> pyOpenSci community news
+
+As the pyOpenSci community has continued to grow, we wanted to dedicate at least one newsletter issue a month to sharing conversations, contributions, and news related to our diverse and vibrant community! This month we’re celebrating everyone who’s participated in a pyOpenSci sprint, sharing the exciting news around the Spanish translation of our Python Packaging Guide, and elevating a discussion from GitHub around the use of Hatch for Python package creation.
+
+## <i class="fa-solid fa-egg"></i> Hello, Hatch!
+
+Education is one of the [three petals of pyOpenSci](https://www.pyopensci.org/blog/pyos-education-announcement.html), and to that end we strive to create resources that help learners navigate the Python packaging ecosystem with ease. This means that when we find our community members and scientists encountering consistent issues with trying to make their workflows more open and reproducible, or trying to build a Python package, we look for ways to lower (or ideally remove!) the barrier for learners. And this was exactly the scenario we were faced with in our beginner-friendly packaging tutorials. We decided that Hatch is a great user-friendly tool that scientists can use to package and share their code. However, in developing and teaching our [Get to know Hatch tutorial](https://www.pyopensci.org/python-package-guide/tutorials/get-to-know-hatch.html), we found scientists struggling to install a tool called [`pipx`](https://github.com/pypa/pipx) that can be used to install Hatch globally, rather than in a Python environment. This was causing a host of problems (in large part because `pipx` can be tricky to install on Windows machines!)
+
+{{< figure src="images/pyopensci-pillars-flower.png" alt="a circle and three petals representing the pillars of pyOpenSci. The circle at the center represents a diverse, inclusive community, and radiating out from it are the three petals–how pyOpenSci accomplishes its community goals. Those are: open peer review, community partnerships, and training and open educational resources.' style='width: 70%;" caption="<i class='fa-solid fa-heart-pulse'></i>The three petals of pyOpenSci<i class='fa-solid fa-heart-pulse'></i>." >}}
+
+We know that it can be challenging to wrap your head around packaging, but what it boils down to is that packaging is really just a process of making your code installable so that it can be reused in different places. And while we decided to use Hatch because it makes packaging life easier, it turns out that Hatch has its own nuanced pain points that we’re still filing down! And we want to share this, because we firmly believe that even someone who is brand new to packaging can get value out of our materials.
+
+> ...packaging is really just a process of making your code installable so that it can be reused in different places.
+
+If you’d like to dig into the details of our Hatch installation adventures, we recommend reading through the discussions in the associated issue and PR:
+
+* [Fix: update hatch install instructions to use the hatch installers rather than pipx in our tutorial #301](https://github.com/pyOpenSci/python-package-guide/issues/301)
+* [All Hatch PRs: [Tuesday july 2 merge] Fix: update hatch install instructions](https://github.com/pyOpenSci/python-package-guide/pull/308)
+
+And for those of you who are interested in the end result, after a robust and lively community discussion, we’ve updated our Get to know Hatch tutorial with the following changes:
+
+1. Suggest users default to the Hatch installers rather than `pipx`.
+2. Suggest Linux users use `pipx` as the install there is simpler.
+
+It’s important to us to elevate this conversation, because all of our materials are community–developed and go through extensive technical review not only before they’re published for the first time, but also for the entire lifetime of the content! We value openness and transparency, and because of the open discussions with community members, we’ve been able to make it even easier to get started with Python packaging!
+
+## <i class="fa-solid fa-earth-americas"></i> Coming soon: a Spanish translation of the pyOpenSci Python Package Guide
+
+This past May, during our [PyCon US sprints](https://www.pyopensci.org/blog/pyopensci-pyconus-2024-sprints.html), pyOpenSci community member [Felipe Moreno](https://github.com/flpm) submitted [an issue to our Python Package Guide GitHub repository](https://github.com/pyOpenSci/python-package-guide/issues/287), asking if we had considered translating the guide to Spanish. Felipe is an experienced security engineering manager with a strong background in Python software development, data science and user-centered design, who leads the Security Data Science team in the CISO Office at [Bloomberg](https://www.bloomberg.com/company/). Felipe has worked with other projects, setting up infrastructure support through [Sphinx](https://www.sphinx-doc.org/en/master/) for this kind of work. We were, of course, immediately thrilled with the idea, and took Felipe up on the offer! From there, Felipe built a PR that created a [translation guide for contributors](https://github.com/pyOpenSci/python-package-guide/pull/304), along with another PR that [provides internationalization support](https://github.com/pyOpenSci/python-package-guide/pull/298).
+
+Following Felipe’s initial efforts, several of our SciPy sprint attendees continued to work on translation of the pyOpenSci Python Packaging Guide, and you can see their progress in the [guide repository on GitHub](https://github.com/pyOpenSci/python-package-guide/issues?q=is%3Aopen+is%3Aissue+label%3Ascipy-24). This has resulted in 13 PRs to our packaging guide. Our next steps are to create an editorial team composed of members who are fluent in Spanish/native speakers. This team will be  responsible for reviewing and merging these contributions. Stay tuned for updates on this incredible community-driven project!
+
+> Following Felipe’s initial efforts, several of our SciPy sprint attendees continued to work on translation of the pyOpenSci Python Packaging Guide...resulting in 13 PRs to our packaging guide.
+
+If you have questions about how to get involved with pyOpenSci, please reach out to [media@pyopensci.org](media@pyopensci.org) so that we can connect you with the right people!
+
+## <i class="fa-solid fa-rainbow"></i> All the credit for our contributors
+
+We have been absolutely floored by the community involvement with pyOpenSci over the last few months, and wanted to take a moment to recognize everyone who has been a part of our sprints at both [PyCon US](https://us.pycon.org/2024/) and [SciPy](https://www.scipy2024.scipy.org/)! In total we’ve had over 30 contributors submit 65 issues to six different pyOpenSci repos between the two events, which is incredible.
+
+### Props to all of our PyCon contributors, including:
+Jesse Bobish, [Patrick Byers](https://github.com/pb-413), [Sarah Kaiser](http://github.com/crazy4pi314), [Ryan Keith](https://github.com/ryanskeith), [Jon Kiparsky](https://github.com/jonkiparsky), [Filipe Laíns](https://github.com/FFY00), [Cheng Lee](https://github.com/chenghlee), [Felipe Moreno](https://github.com/flpm), [Matthew Ngoy](https://github.com/Vaunty), [Jeremy Paige](https://github.com/ucodery), [Ken Seehart](https://github.com/kenseehart), [Steven Silvester](https://github.com/blink1073), [Megan Sosey](https://github.com/sosey), [Zack Weinberg](https://github.com/zackw), [Brianne Wilhelmi](https://github.com/BSuperbad), [Carol Willing](https://github.com/willingc), [Sneha Yadav](https://github.com/sn3hay), and [Bradon Zhang](https://github.com/BradonZhang).
+
+> In total we’ve had over 30 contributors submit 65 issues to six different pyOpenSci repos between the two events, which is incredible.
+
+### Shout out to all of our SciPy contributors, including:
+[Naty Clementi](https://github.com/ncclementi), [Geoff Cureton](https://github.com/gpcureton), [John Drake](https://github.com/John-Drake), [Han](https://github.com/ayhanxian), [Elise Hinman](https://github.com/ehinman), [hpodzorski-USGS](https://github.com/hpodzorski-USGS), [Sarah Kaiser](https://github.com/crazy4pi314), [kaiyamag](https://github.com/kaiyamag), [Felipe Moreno](https://github.com/flpm), [Roberto Pastor Muela](https://github.com/RobPasMue), [Olek](https://github.com/yardasol), [Santiago Soler](https://github.com/santisoler), and [Revathy Venugopal](https://github.com/Revathyvenugopal162).
diff --git a/content/blog/2024-08-02-pyopensci-at-scipy-2024.md b/content/blog/2024-08-02-pyopensci-at-scipy-2024.md
new file mode 100644
index 00000000..aa0a11a2
--- /dev/null
+++ b/content/blog/2024-08-02-pyopensci-at-scipy-2024.md
@@ -0,0 +1,429 @@
+---
+title: 'pyOpenSci @ SciPy 2024 - Python Packaging Tutorials, Talks and Community :heart:'
+date: '2024-08-02'
+type: blog
+excerpt: pyOpenSci had an incredibly impactful SciPy conference this year in Tacoma
+  Washingon. I gave a talk and we lead a workshop on Python packaging and we had 39
+  issues and pull requests submitted during our sprints. Learn more about both the
+  SciPy meeting and my expeirence SciPy in Tacoma, Washington this year.
+author: Leah Wasser
+blog_topic: community
+toc: true
+comments: true
+url: "/blog/pyos-scipy-2024-recap.html"
+lastmod: '2024-08-29'
+---
+
+<div class="notice" markdown = "1">
+## TL;DR
+
+* pyOpenSci lead 3 incredibly successful events at [SciPy](https://www.scipy2024.scipy.org/) this year: A tutorial,
+a talk and a 1.5 day sprint.
+* During our SciPy 2024 meeting sprint we had over 35 GitHub issues and pull requests submitted by XX new contributors.
+* Our tutorial had over 30 attendees. Almost all of the learners had never created a Python package before, and most of them were successful creating their first Python package.
+* I thoroughly enjoyed connecting with new and old colleagues and friends.
+
+</div>
+
+## pyOpenSci's fourth year attending SciPy - my experience
+
+This year was my fourth time attending the annual SciPy meeting—a meeting
+organized by [NumFocus](https://www.numfocus.org) that celebrates the scientific
+Python ecosystem. My first experience was in 2019, where we held the very first
+pyOpenSci Birds of a Feather (BoF) session.
+
+A Birds of a Feather session, also known as a BoF, is a community-organized
+event where people lead a discussion around a specific topic. Our 2019 SciPy BoF was about
+our peer review process, which we had just launched that year.
+{: .notice }
+
+One of the biggest differences this year has been how much pyOpenSci has grown, which means we saw many familiar faces, including:
+
+* Maintainers of packages that we have reviewed and accepted through our
+  [scientific Python software peer review process](/about-peer-review/index.html),
+* Colleagues who I have met at other meetings, such as [PyCon](https://pycon.org/),
+* Reviewers and editors from our community,
+* Members of our advisory council, contributors, and
+* Friends—so many friends.
+
+This year, I was busy at SciPy, and spent my days:
+
+1. Running an in-person tutorial: [Create Your First Python Package](https://cfp.scipy.org/2024/talk/QT9GBY/).
+2. Giving a talk, [The power of community in solving scientific Python’s most challenging problems](https://cfp.scipy.org/2024/talk/AMTLJ7/), in the Maintainers Track (what an honor!).
+3. Working the hallway track.
+4. Running a 1.5-day sprint that resulted in over 35 issues and pull requests.
+   Wow.
+
+Admittedly, I started off this conference behind and frazzled. You see, pyOpenSci
+has been growing in recent months. With that growth comes more wonderful people
+to support and engage with! More people getting involved does mean more work for
+pyOpenSci. However, the time is worth it, as all of this effort is moving
+pyOpenSci's mission of supporting open science forward.
+
+{{< figure src="images/blog/2024/july/scipy-24-pyopensci-package-submission-growth.png" alt="A bar plot with purple bars titled - number of submissions by quarter per year. The plot shows the number of submissions that pyOS has received since it started peer review in 2019. We started with only a few submissions per quarter but the numbers have grown to about 13 per quarter on average in the 2024. ' style='width: 100%;" caption="<i class='fa-solid fa-heart-pulse'></i> pyOpenSci runs an open software peer review process. Above you can see how submissions have increased since we started in 2019. I started full time on pyOpenSci in late 2022. <i class='fa-solid fa-heart-pulse'></i>." >}}
+
+In the end, even though I wasn't quite as prepared as I wanted to be, my talk
+and the workshop went great! This was a lesson for me in understanding that
+things can be less than perfect and still go well.
+
+More on all of that below. But first--what is the SciPy Conference?
+
+## A brief history of the annual SciPy conference
+
+If you haven't attended this meeting before, let me give you the rundown. The
+SciPy Conference is an annual event dedicated to celebrating and learning more
+about scientific computing, all using the Python programming language. The meeting
+started back in [~2002](https://web.archive.org/web/20021030003450/http://www.scipy.org/site_content/scipy02/). The early meetings were run by EnThought and
+were smaller in size and scope. Over the years, SciPy has evolved significantly,
+mirroring the [🚀 explosive growth of the Python ecosystem 🚀](https://stackoverflow.blog/2023/01/26/comparing-tag-trends-with-our-most-loved-programming-languages/)
+in scientific computing and data science.
+
+Today the SciPy Conference, hosted by [NumFocus](https://numfocus.org/),
+attracts over 700 attendees from diverse scientific fields such as astronomy,
+biology, geophysics, and more. SciPy is much more than just a meeting.
+
+SciPy features:
+
+* Incredible keynote speakers, such as the inspirational
+  [Carol Willing](https://www.youtube.com/watch?v=s-W-UvGgDco).
+* Talks from the community about tools and approaches.
+* Poster sessions that allow presenters to directly engage and discuss cool
+  work with the meeting attendees.
+* Tutorials led by community members (including pyOpenSci) that cover important
+  scientific data processing and analysis-related Python skills.
+* Sprints: collaborative coding sessions where people come to contribute to
+  and learn about open-source projects.
+
+I'd be remiss if I didn't mention the lightning talk sessions. During lightning
+talks, people throw their names into a literal bucket. If their name is selected,
+they are given 5 minutes (or less if the dice are rolled) to talk about a topic
+they love. Last year the talks featured a large stuffed dice that you would roll. the number that was rolled determined how much time you have to present and what distractions the moderators would apply to you. :laughing:
+
+You see, at SciPy, there are often off-beat distractions from the moderators
+along the way, such as the infamous grab claw (see below). Yes, it is as
+ridiculously hilarious as it sounds.
+
+{{< figure src="images/blog/2024/july/scipy-24-lobster-claw.jpeg" alt="Photograph showing a man with a beard holding a red lobster claw - while deviously looking at a blonde woman at a podium who is smirking at him. She is wearing a blue top and beige pants' style='width: 90%;" caption="<i class='fa-solid fa-heart-pulse'></i> It's well-known that lightning talk organizers enjoy heckling presenters. Sometimes they do so using props, such as the lobster claw seen here <i class='fa-solid fa-heart-pulse'></i>. Photo Credit: SciPyConf Fosstodon" >}}
+
+[Did someone mention sharks? More here on my experience last year giving a SciPy lighting talk.](/blog/scipy-2023-community.html)
+{: .notice }
+
+Another cool thing about SciPy is that the entire meeting is community-driven. The scientific Python community really
+shows up to make this meeting what it is. All of the sessions are volunteer
+organized and run. Volunteers also spend considerable time engaging with
+presenters, ensuring there are social activities that everyone is invited to in
+the evenings, and generally making sure that everyone feels included.
+
+Since the pandemic, the SciPy meeting has adapted to support virtual/hybrid
+participation, which has further increased its reach. In fact, some remote
+attendees also helped organize the meeting!
+
+If you are a Pythonista who loves science, this meeting is for you!
+
+## pyOpenSci's first SciPy tutorial was a huge success: Create your first Python package
+
+My adventure at the SciPy meeting kicked off with a 4-hour tutorial entitled:
+_[Create Your First Python Package: From Code to Module](https://cfp.scipy.org/2024/talk/QT9GBY/)_.
+
+I have to start by saying the tutorial went great. Here is what one person
+had to say about it:
+
+> The content and the crew! The team was so kind, patient and approachable. I appreciate the amount of support and reassurance given during this tutorial. The content of the tutorial was also spot on. Everything we covered felt relevant and useful, and gave me the confidence to feel capable of creating my own packages.
+
+This tutorial was an
+expanded version of the [Create Your First Python Package tutorial that
+pyOpenSci ran in April 2024](/blog/pyos-education-announcement.html). In our first
+workshop, we had over 20 people create their first Python package. We had
+similar success in our SciPy tutorial.
+
+I realized when I got to SciPy that I hadn't actually taught in person since
+2020! I vividly remember the last in-person class that I led for the [Professional
+Graduate Program in Earth Data Analytics that I created at CU
+Boulder](https://catalog.colorado.edu/graduate/colleges-schools/interdisciplinary-programs/earth-data-analytics-foundations-graduate-certificate/).
+That class happened on the Wednesday before the pandemic lockdown started in the
+United States. It was a sad day to say "goodbye for now" to in-person teaching
+and to my students. Teaching and working with learners is, after all, one of my
+favorite things. However, luckily we had been running the program using a
+hybrid online and in-person approach, so the transition was sad, but didn't
+impact our learners too much.
+
+But back to SciPy, it was a rush to be back in the "classroom" at SciPy 2024!
+
+### A pyOpenSci tutorial room full of eager learners and tech that worked
+
+Our workshop room was full of people eager to better understand Python packaging.
+We also had great helpers, and all the tech in the room just worked seamlessly.
+The SciPy tutorial organizers did an amazing job of ensuring everything ran
+smoothly.
+
+After a really tricky internet situation at PyCon this past May, I truly
+appreciated the smooth setup of the room.
+
+A special shout-out to pyOpenSci community members
+[Jeremiah](https://www.github.com/ucodery) and
+[Isabel Zimmerman](https://github.com/isabelizimm), who were committed to
+helping all the learners have a successful experience. Their support and
+expertise were invaluable.
+
+{{< figure src="images/blog/2024/july/pyos-tutorial-scipy-24.jpeg" alt="A photograph showing a large open and well-lit meeting room with two rows of horizontal tables. People are working at laptops in the room. An instructor is at the front with their laptop screen projected on the screen' style='width: 90%;" caption="<i class='fa-solid fa-heart-pulse'></i> This image was taken about halfway into the workshop. We had lost a few folks to other conference activities, but most were still engaged! <i class='fa-solid fa-heart-pulse'></i> Source: SciPyConf Fosstodon." >}}
+
+### pyOpenSci is helping the community navigate Python packaging challenges together
+
+Of course, there were a few challenges, too.
+
+1. Many participants came without working through the setup instructions. This
+   was particularly problematic for those with government-issued laptops, where
+   they couldn't install software.
+
+1. While most workshops could use the Jupyter-Hub cloud platform called Nebari, hosted by
+   Quansight Labs, it didn't support our development use case. Thus, we didn't
+   have a "backup" platform for participants who couldn't get things set up.
+   However, I later worked with [Sarah Kaiser](https://github.com/crazy4pi314)
+   from GitHub, who set us up with a [Codespace](https://github.com/features/codespaces)
+   that we can use for future workshops.
+
+1. Because we practiced publishing to (test) PyPI, we should have suggested that participants create an account in advance!
+
+1. Installing things across operating systems (Linux, Mac and windows) is always
+   tricky. In this workshop, we switched from suggesting
+   [pipx](https://pipxproject.github.io/pipx/) to using
+   [Hatch installers](https://hatch.pypa.io/latest/install/) for Mac and
+   Windows users. We made this change because Windows users previously had
+   significant issues installing `pipx` both during our previous workshop, and
+   during our [PyCon 2024](https://us.pycon.org/2024/) sprint.
+
+   The glitch we encountered this time with the installers was that [Hatch](https://hatch.pypa.io/latest/) would
+   initiate an update on some computers that already had it installed when users
+   ran `hatch --version` for the first time. This is something we need to
+   address in the future, or at least warn users about.
+
+### Our pyOpenSci tutorial at SciPy 2024 was hugely successful
+
+Challenges aside, we also had a lot of successes to celebrate!
+
+Similar to our online workshop in April, many attendees created their
+first Python package!
+
+<!-- TODO: add link to april workshop once the event page is online -->
+
+<figure class="half">
+    <a href="/images/blog/2024/july/pyopensci-have-you-created-package.png"><img src="/images/blog/2024/july/pyopensci-have-you-created-package.png" alt="An image showing a question: 'Have you created a Python package before?' Below is a bar plot with 3 colored bars. 3 people answered Yes, 10 people answered No, and 4 answered 'I struggled trying.'"></a>
+    <a href="/images/blog/2024/july/pyopensci-workshop-successful-package.png"> <img src="/images/blog/2024/july/pyopensci-workshop-successful-package.png" alt="An image showing a question: 'Were you able to create a package during this workshop?' 10 people answered Yes, 1 person answered No, and no one answered 'I am not sure.'"></a>
+    <figcaption>We used Mentimeter during the workshop to get feedback from participants along the way. Next workshop, I think I will use this tool more to gather feedback. Feedback is crucial for iteratively improving any event, especially when teaching, as it allows you to address pain points dynamically, improving both online lessons and in-person trainings.</figcaption>
+The verbal feedback from participants was overwhelmingly positive. Comments like
+
+> "One of the best workshops I've been to"
+
+and
+
+> "I'm always behind in workshops like this. This was the first workshop where I could actually
+  keep up"
+
+made all the effort worthwhile.
+
+Needless to say, I left the event with a full heart. 🫶
+
+Several participants enjoyed the process so much that they joined our sprint
+afterwards to help build out the packaging guide. More on that below.
+
+## pyOpenSci, Python packaging and community--my talk at SciPy 2024
+
+The day after the workshop discussed above, and the first day of the conference,
+I gave my first-ever talk, [The power of community in solving scientific Python’s most challenging problems](https://cfp.scipy.org/2024/talk/AMTLJ7/), in the maintainers track at SciPy. <i class="fa-solid fa-gift"></i>
+
+What an honor to be selected as a speaker.
+
+This year, the SciPy maintainers track was organized and hosted by
+[Inessa Pawson](https://github.com/InessaPawson),
+[Brigitta Sipőcz](https://github.com/bsipocz),
+[Matt Craig](https://github.com/mwcraig), and
+[Mridul Seth](https://github.com/MridulS). It kicked off with a fantastic talk
+by [Eric Mah](https://github.com/ericmjl). Eric discussed how he has been
+bringing open-source values and workflows to the corporate environment at
+Moderna (yes, the same company that makes one of the more popular COVID
+vaccines). Eric's talk carefully navigated both the benefits of open source for
+corporate teams while also acknowledging some of the tensions.
+
+My talk closed out the session.
+
+{{< figure src="images/blog/2024/july/pyopensci-talk-leah-wasser-scipy24.jpg" alt="Image of a room of round tables with black covers filled with people listening to my talk. At the front is a speaker wearing a red tank top. On the screen is a slide that says 'The Power of Community Review.'' style='width: 90%;" caption="<i class='fa-solid fa-heart-pulse'></i> Me, giving my talk about community, packaging, and peer review at SciPy 2024. The coolest part of the talk was meeting people afterwards who I hadn't met in real life before. <i class='fa-solid fa-heart-pulse'></i> Photo Credit: Inessa Pawson" >}}
+
+### pyOpenSci is leveraging and working with the community to solve scientific Python's challenges
+
+My talk was about how pyOpenSci has been carving out space and coordinating
+community efforts to address several core challenges in our scientific Python
+ecosystem. These include:
+
+1. Helping scientists find and use the right open-source tools.
+2. Encouraging scientists to write better code, share their code, and build better software.
+3. Ensuring scientists get credit for their open-source work.
+4. Addressing the ongoing challenges of packaging in the Python ecosystem-—a topic
+   I discussed in my [PyCon talk in April](/blog/python-packaging-friends-dont-let-friends-package-alone.html),
+   which was also available on YouTube (video/playlist may have been moved). I'd love for you to check out the [SciPy 2024 conference site](https://www.scipy2024.scipy.org/) for current talks and tutorials.
+
+### pyOpenSci's Python packaging guidebook is having a positive impact on the scientific Python ecosystem
+
+During my talk, I addressed critical pain points I've experienced as an
+educator teaching spatial and earth data science, and as a maintainer of
+[stravalib](https://stravalib.readthedocs.io/en/latest/)—a package that supports
+my pre-getting-COVID obsession with ultra mountain
+running.
+
+Things kicked off with a bang, thanks to the best meme ever, created by
+[Filipe Fernandes](https://github.com/ocefpaf). Filipe, a conda-forge
+maintainer, introduced me to conda environments when I was struggling with
+creating consistent spatial data environments for my students. Anyone who's
+spent time wrestling with GDAL in a Python environment knows the struggle.
+Thanks to folks like Filipe and the conda-forge community, managing spatial
+environments has become much easier for everyone!
+
+{{< figure src="images/blog/2024/july/pyopensci-leah-talk-pip-install-gdal.jpg" alt="Image of me with my eyes closed chuckling as people laugh at the meme on the screen. The meme has Boromir, played by Sean Bean in the Lord of the Rings Trilogy, making a circle with his right hand with the words 'One does not simply pip install GDAL overlaid on the image.'' style='width: 90%;" caption="<i class='fa-solid fa-heart-pulse'></i> Filipe's meme is always a hit. Thinking about pip installing GDAL is not for the faint of heart. In the early years of using Python for spatial data, it was incredibly challenging to create a successful environment that contained spatial libraries (which often depend on GDAL)... <i class='fa-solid fa-heart-pulse'></i> Photo Credit: Luis López" >}}
+
+I discussed how pyOpenSci is working to make things easier for
+scientists by improving access to the right packages, maintaining community-vetted
+tools in one place, helping maintainers step down and transition out, and making documentation
+more beginner-friendly.
+
+{{< figure src="images/blog/2024/july/pyopensci-what-if.png" alt="A slide on a dark purple background that says - What If... finding the right package was easier. Community vetted tools were maintained in one place? We could help maintainers step down? Docs were more beginner friendly. At the bottom, there are two stick figures at computers - one is frustrated, one is happily typing away.' style='width: 100%;" caption="<i class='fa-solid fa-heart-pulse'></i> pyOpenSci asks and addresses the questions - what would happen if things were easier for scientists? <i class='fa-solid fa-heart-pulse'></i>." >}}
+
+### pyOpenSci is running community-led inclusive, open software peer review
+
+I also talked about how pyOpenSci is using an inclusive,
+[community-led peer review process](/about-peer-review/index.html) to achieve
+several goals:
+
+* Helping scientists find vetted, trusted, and maintained software.
+* Helping scientists build better software.
+* Providing maintainers with credit for the important work they do to support open
+  science.
+
+{{< figure src="images/blog/2024/july/pyopensci-community-lead-software-peer-review.png" alt="Slide from my talk. It says 'The Power of Constructive Community Review' at the top. Below is a graphic showing the 4 core steps from left to right: submit your package, pre-review checks, review, and then accepted. The pyOpenSci accepted badge is below the accepted box. At the end of the row is a box that says 'Maintenance checks and stats.'' style='width: 90%;" caption="<i class='fa-solid fa-heart-pulse'></i> pyOpenSci runs an open, community-led software peer review process. The process is overseen by a volunteer editor-in-chief, a rotating position, and includes an editor who leads the review and at least two reviewers. pyOpenSci cares about the long-term maintenance of software, so packages in our ecosystem undergo checks to ensure they are still actively maintained. The review itself is constructive and designed to support the maintainer(s) in improving the quality and usability of their package. <i class='fa-solid fa-heart-pulse'></i>" >}}
+
+I also discussed how pyOpenSci [partners with communities](https://www.pyopensci.org/partners.html) like the [Journal of Open Source Software](https://joss.theoj.org/) and [Astropy](https://www.astropy.org/) to leverage resources. In the spirit of open source, our goal is to learn as much as we can from other communities.
+
+Where ever we can, pyOpenSci partners with other communities and leverages their
+work. Building on top of and leveraging each other's work IS the true spirit of
+open source and open science. By working together, we can move forward together.
+
+{{< figure src="images/blog/2024/july/pyopensci-partnerships-joss-astropy.png" alt="A diagram on a light purple background showing the three peer review steps: prereview checks, review, and pyOpenSci acceptance. Below the review box, it says 'Your community standards,' indicating that a partner community can add their own affiliated package standards to our review process. To the right of this process is an arrow leading to three boxes: 'JOSS Published,' 'community affiliated,' and 'maintenance checks and stats.'' style='width: 90%;" caption="Through our partnership with the Journal of Open Source Software (JOSS), a package submitted to us can also be published by JOSS if it's in scope. JOSS accepts our review and only reviews the paper, providing a huge benefit to the maintainer team. We also partner with communities such as Astropy. Through the Astropy partnership, an Astropy-related package can also become Astropy-affiliated. Members of the Astropy community volunteer on our editorial board and support these reviews." >}}
+
+### pyOpenSci and how we created a truly community-driven Python packaging guidebook
+
+I also discussed our work in the Python packaging ecosystem, specifically around
+making packaging more beginner-accessible and friendly. pyOpenSci leans into
+community expertise and review as a way to leverage community expertise when
+making packaging decisions. People who have reviewed our packaging content
+include both those in the scientific Python ecosystem and those working on core
+Python challenges. These people include:
+
+* Python Packaging Authority members (PyPA)
+* Packaging tools maintainers
+* Packaging experts
+* Scientists
+* People new to packaging
+
+All of these people have helped pyOpenSci create a [Python packaging guide](https://www.pyopensci.org/python-package-guide/index.html) that is both
+accurate and beginner-friendly.
+
+{{< figure src="images/blog/2024/july/pyopensci-package-guide-review.png" alt="Image of the pyOpenSci package guide review process. There are three main boxes on the slide labeled 'expert feedback,' 'community review,' and 'sprints and bug bashes.' The top of the image is titled 'The Power of Community Review.'" caption="pyOpenSci engages people from all parts of the Python community, with all levels of expertise, in our packaging guide review process. This engagement ensures a high-quality and beginner-friendly guidebook." >}}
+
+One of the decisions we made as a community early on was to use Hatch as an
+end-to-end packaging tool. We believe Hatch is user-friendly and supports many
+of the use cases scientists have when sharing their code.
+
+{{< figure src="images/blog/2024/july/pyopensci-packaging-hatch.png" alt="Image titled 'Creating an Opinionated Tutorial.' Below it lists four bullet points about Hatch: 1. Responsive maintainer, 2. User friendly, 3. Adheres to standards, 4. Doesn't lock you in.' style='width: 80%;" caption="pyOpenSci is teaching with Hatch now because we have had good success with using Hatch and engaging with its forward-thinking maintainer." >}}
+
+I met some great people and had good discussions about peer review and Python
+packaging. The presentation will be on YouTube at some point, and I will update
+this post with the link when it's live. In the meantime, my slides are available
+on [pyOpenSci's Zenodo community](https://zenodo.org/records/8045448).
+
+## pyOpenSci and reconnecting with the scientific Python community--the hallway track
+
+It seems like this year has been the year of the hallway track. The hallway
+track refers to the time spent in the hallways of a meeting, talking to people
+you don't normally get to work with in person. Sometimes, the hallway track can
+be even more valuable than attending the talks. You can always watch the talks
+later on YouTube, but you can't always collaborate in real life like you can at
+a meeting like SciPy, which attracts people from around the world.
+
+I spent a lot of time talking with colleagues, friends, and community members
+about all things Python, open source, and open science.
+
+* I worked with Sarah Kaiser on our new GitHub container to support workshops.
+* I had an _ad hoc_ sprint with [Angus](https://github.com/agoose77) and [Rowan](https://github.com/rowanc1) from the [MyST Markdown](https://mystmd.org/) community
+  to develop our [pyOpenSci peer review metrics dashboard](https://www.pyopensci.org/metrics/).
+
+Additionally, I caught up with colleagues, chatting about packaging and scientific Python.
+
+
+## pyOpenSci sprints at SciPy--over 39 pull requests and issues <i class="fa-solid fa-rocket"></i>
+
+Every year at SciPy, we spend the last two days of the meeting sprinting.
+This year was the first time I stayed for both days of the sprints.
+
+### A brief overview of open-source sprints
+
+If you haven't been to an open-source sprint before, a sprint is an open
+session where contributors join a project and help address specific issues and
+tasks that the project needs help with. I wrote [more about how pyOpenSci runs
+beginner-friendly sprints here](/blog/pyopensci-pyconus-2024-sprints.html).
+
+Sprints are a lot of fun because,
+given enough time, you can make significant progress on a project and support
+first-time and new contributors in making their first contributions!
+
+This is what the second sprint room looked like this year at SciPy. There was a
+scramble to find a new location for our sprints due to some power issues
+stemming from an unexpected accident in Tacoma. Our space was much smaller
+than usual, but we made it work!
+
+{{< figure src="images/blog/2024/july/pyopensci-scipy-24-sprints.jpeg" alt="Photograph showing a tan room filled with long tables and people sitting in front of laptops working together on specific projects or tasks." caption="The sprint setup isn't always perfect at meetings, but we made it work! This year, the rooms were full with little space to spread out. However, we made the best of it. The pyOpenSci sprint table is in the middle row, closest to the camera." >}}
+
+We had a great group this year who worked on a variety of tasks, including:
+
+* Tackling a longstanding issue to sync our labels across all repositories. We
+  have many labels, and they vary across repositories. The work is now done, and
+  next, we will implement a GitHub action to clean up labels across all of our
+  GitHub repos.
+* Working on our [Python Packaging Guide](https://www.pyopensci.org/python-package-guide/),
+  which is now being translated into Spanish!
+* Someone enthusiastic about Sphinx worked on our [pyos-sphinx-theme](https://github.com/pyOpenSci/pyos-sphinx-theme).
+  pyOpenSci has several online "books" that would benefit from using the same
+  theme and colors that follow the pyOpenSci brand.
+* A handful of people contributed to our MyST Markdown [peer review metrics dashboard](https://www.pyopensci.org/metrics/).
+
+<figure class="half">
+    <a href="/images/blog/2024/july/pyopensci-sprints-day-1.png">
+    <img src="/images/blog/2024/july/pyopensci-sprints-day-1.png"
+    alt="An image of about 10 people sitting at a long table working on laptops."></a>
+    <a href="/images/blog/2024/july/pyopensci-sprints-day-2.png">
+    <img src="/images/blog/2024/july/pyopensci-sprints-day-2.png"
+    alt="Another image similar to the above, but from the other side of the table
+    on the second day."></a>
+    <figcaption>People sitting at the pyOpenSci sprint table. We had a slightly
+    different group each day, but the energy was equally enthusiastic both days.
+    </figcaption>
+Several people made their first-ever contributions to open source during our
+pyOpenSci sprints, which was fantastic. We had a lot of great people get
+involved and support us. The positive vibes were contagious!
+
+## pyOpenSci's most successful SciPy meeting yet, and we're just getting started
+
+It's amazing to think about how far pyOpenSci has come in the past five years.
+In 2019, pyOpenSci was just kicking off its peer review process, and only a
+small number of people knew about us. By 2023, we had some funding to begin
+traveling and spreading the word about our work, but we were still somewhat
+unknown in the community. Fast forward to 2024, and people not only know about
+us but are also excited to contribute and support our mission. We aim to help
+scientists find and build better software and develop better open science skills.
+
+After this spectacular year, I can't wait to see what 2025 brings!
+
+### Get involved with pyOpenSci
+
+If you are interested in getting involved with us, there are many ways to do so!
+Check out our [volunteer](/volunteer.html) page as a starting place. Or shoot
+an email to [media at pyopensci.org](mailto:media@pyopensci.org).
+
+I can't wait to see you next year at PyCon US and SciPy 2025!
diff --git a/content/blog/2024-08-30-pyopensci-monumental-growth-2024.md b/content/blog/2024-08-30-pyopensci-monumental-growth-2024.md
new file mode 100644
index 00000000..ff4b8a5f
--- /dev/null
+++ b/content/blog/2024-08-30-pyopensci-monumental-growth-2024.md
@@ -0,0 +1,415 @@
+---
+title: 'It''s Been a Long Short Road: The Monumental Past 2 Years of pyOpenSci'
+date: '2024-08-30'
+type: blog
+excerpt: Learn about what pyOpenSci has accomplished in the last two years, including
+  the evolution of our packaging guide, the expansion of our peer review process,
+  and the vibrant community we've built.
+author: Leah Wasser
+blog_topic: community
+toc: true
+comments: true
+url: "/blog/what-pyopensci-accomplished-with-two-years-of-funding.html"
+lastmod: '2024-09-08'
+image:
+  src: images/blog/headers/pyos-two-years.png
+  alt: 'It''s Been a Long Short Road: The Monumental Past 2 Years of pyOpenSci'
+---
+
+## It's been two years since I started working full-time on pyOpenSci
+
+I have been working full-time building pyOpenSci for two years now, thanks to funding from the [Sloan Foundation](https://sloan.org/) and [CZI (Chan Zuckerberg Initiative)](https://chanzuckerberg.com/). pyOpenSci has come SO FAR in two years.
+
+It's time to take a breath and celebrate everything the pyOpenSci community has accomplished. Before we move on to the next big thing—[our pyOpenSci Fall Festival](/events/pyopensci-2024-fall-festival.html) (more on that below)—I want to take a moment to reflect on:
+
+* where we've been,
+* what we've accomplished, and
+* the incredible community of practice that we've built.
+
+I'll wrap up by discussing what's next for pyOpenSci.
+
+## A brief history of pyOpenSci
+
+I founded pyOpenSci in 2018 because I saw the pain points that scientists were
+facing in creating open, reproducible workflows using Python. My experience
+inspired me to establish a vibrant, inclusive pyOpenSci community of practice
+fueled by making open science best practices more accessible to scientists.
+
+pyOpenSci makes open science more accessible by [developing educational resources](/learn.html), [running training events](/events/), running an [open software peer review process](/about-peer-review/index.html) and [partnering with other communities](/partners.html). From humble beginnings characterized by small community meetings, pyOpenSci has blossomed into a thriving community marked by:
+
+* a robust editorial team,
+* hundreds of contributors, and
+* numerous valuable community partners and friends.
+
+Our software peer review program has seen **over 50 packages**; we've [accepted 35 scientific Python packages into our growing library of trusted scientific Python packages](https://www.pyopensci.org/python-packages.html) and have **17 packages** in [active stages of review](https://github.com/orgs/pyOpenSci/projects/7) as I write this post.
+
+<!-- [<i class="fa-solid fa-wand-magic-sparkles"></i> Learn more about how pyOpenSci started <i class="fa-solid fa-wand-magic-sparkles"></i>](/blog/how-pyopensci-got-started.html)
+{: .button } -->
+
+{{< figure src="images/pyopensci-general/pyopensci-flower-pillars.png" alt="A flower petal image with three flower petals and a flower center. In each petal, there is text. The first petal says software peer review; the second says community partnerships; the third says education & training. The center circle of the flower says diverse, inclusive community." caption="pyOpenSci supports scientists developing open-source software through three programs: 1) peer review of scientific software, 2) community partnerships, and 3) education & training. A diverse and inclusive community that cares about the open-source software that drives open science supports all three of these programs." >}}
+
+### pyOpenSci and iterative, data-driven program design
+
+pyOpenSci's development and design is data-driven. I collected survey data
+from scientists and Pythonistas at meetings and conferences to identify community pain points and needs. I used this data to inform the iterative development of pyOpenSci programs, events, and resources and to define pyOpenSci's mission, vision, values, and structure.
+
+The survey data I've collected shows what I've seen in the classroom-- scientists face many challenges when
+processing, analyzing, and sharing their workflows. While reproducible
+science is critical to accelerating science, sharing and publishing code is hard.
+
+This blog post includes quotes and data I've collected over the past 5+ years; these data have shaped the vibrant community of practice that pyOpenSci is today.
+
+{{< figure src="images/pyopensci-general/pyopensci-iterative-evaluation-program-design.png" alt="A round graphic that shows the cycle of iterative program development. The pyOpenSci logo is at the top left. The graphic title reads iterative program development. The first step says, 'A good idea gets better and better', the second says 'survey community needs,' the third says, 'evaluation based program design,' and the fourth says, 'evaluate results and make iterative improvements'. In the center is th" caption="Iterative data-driven program design is a fusion of evaluation and program development that utilizes community feedback to build a program using an iterative and community-responsive approach. You test approaches and collect data about the program's effectiveness. This type of development allows an organization to grow dynamically, following community needs." >}}
+
+<div class="notice" markdown ="1">
+
+### Responses to the question: *How could pyOpenSci help you with your science, code, and software?*
+{: .not_toc}
+
+
+> [*I want to know...*] What are the best practices for sharing the code?
+>
+> — Anonymous
+
+
+
+> [*I want to... *] Streamline the development of good quality, socially responsible, and easily shareable software.
+>
+> — Anonymous
+
+
+
+> [*I want more *] Bullet-proof, well-documented packages for Earth science.
+>
+> — Anonymous
+
+
+Many earth scientists attend AGU. It's a different crowd than who you meet
+at the SciPy meetings.
+</div>
+
+### Why pyOpenSci tackled Python packaging
+
+pyOpenSci's design is also based on our experiences developing software peer review guidelines for Python packages. According to our surveys, 80% of our maintainers and reviewers identify strongly as scientists.
+
+As we developed our [peer review guide](https://www.pyopensci.org/software-peer-review/), it became clear that a beginner-friendly packaging guide was essential to support scientists in sharing their code because:
+
+1. [Our pre-review software checks](https://www.pyopensci.org/software-peer-review/how-to/editor-in-chief-guide.html#editor-checklist-template) require basic package infrastructure. Scientists must be clear about the core elements of a Python package.
+2. We want to help scientists make their packages more maintainable over time by adding tests and [continuous integration (CI)](https://www.pyopensci.org/python-package-guide/tests/tests-ci.html#run-tests-with-continuous-integration) checks that run when someone submits a suggested change (or a pull request). We want to set scientists up for success.
+3. We realize that Python packaging is a thorny ecosystem to navigate. I knew that pyOpenSci could help file down those thorns.
+
+<div class="notice" markdown ="1">
+### *"How could pyOpenSci help you with your science, code, and software?"*
+
+
+> Training for people who can code for themselves but want to start developing software for others. Topics include style, documentation, testing, git, etc.
+>
+> — Anonymous
+
+
+</div>
+
+#### Helping scientists navigate a complex and difficult-to-understand Python packaging ecosystem
+
+The packaging ecosystem has evolved rapidly. Numerous tools and approaches are available to create Python packages. Further, recent changes to ecosystem standards have led to an explosion of packaging tools like [Hatch](https://hatch.pypa.io/latest/), [Flit](https://flit.pypa.io/en/stable/), [PDM](https://pdm.fming.dev/latest/), and [Poetry](https://python-poetry.org/); other tools like Pixi and Rye are also on the horizon. Scientists often feel overwhelmed by the sheer number of options and have begged for clear guidance for years.
+
+<div class="notice" markdown ="1">
+
+<h3 class="no-toc"> QUESTION: "How could pyOpenSci help you with your science, code, and software?"</h3>
+
+
+
+> [*I want pyOpenSci to*] clarify Python packaging. There are too many different mechanisms floating around...
+>
+> —
+
+
+</div>
+
+{{< figure src="images/python-packaging/pyopensci-python-package-tools-word-cloud-2024.png" alt="This is a giant word cloud with dozens of words. The biggest words are Build, Poetry, Conda, Setuptools, Sphinx, pip, Hatch, Mamba, Twine PyPI, venv, and GitHub Actions." caption="This word cloud represents around 100 responses to the question: What Python packaging tools do you most often use? It demonstrates both 1) how many tools there are to choose from and 2) how divided the ecosystem is in terms of which tools they are using. Yes, a few tools there aren't explicitly Python packaging tools. :)" >}}
+
+There are some excellent, more advanced guides and tutorials available now, such as [PyPA's packaging tutorial](https://packaging.python.org/tutorials/) and the [scientific Python development guide](https://learn.scientific-python.org/development/). However, our resources serve a different audience.
+
+1. The people using our resources are often folks who find the packaging ecosystem to be overwhelming.
+1. Scientists are also only sometimes familiar with various terms. For example, it's easy to confuse a build backend with a build frontend, especially when both have the word "hatch" in them (e.g., Hatch vs. Hatchling).
+1. Scientists often want to avoid deciding what tools to use. pyOpenSci intends to alleviate this burden and provide a robust and practical approach.
+
+From a beginner's perspective, every decision is a potential opportunity to go down the wrong path, adding cognitive load. Armed with a clear understanding of the packaging pain points, I knew that pyOpenSci could simplify the packaging journey for scientists.
+
+If you want to learn more, my [talk at PyCon dove into the Python packaging challenges of too many options and cognitive overload.](/blog/python-packaging-friends-dont-let-friends-package-alone.html)
+
+### pyOpenSci guided the community towards a single way to create a Python package in under a year
+
+In just under a year, pyOpenSci created a [comprehensive packaging guide](https://www.pyopensci.org/python-package-guide/) that includes an end-to-end Python packaging / share your code tutorial that walks scientists through creating a package and publishing it to both [PyPI](https://www.pyopensci.org/python-package-guide/tutorials/publish-pypi.html) and [conda-forge](https://www.pyopensci.org/python-package-guide/tutorials/publish-conda-forge.html) using [Hatch](https://www.pyopensci.org/python-package-guide/tutorials/get-to-know-hatch.html). Together, the pyOpenSci community built consensus around which packaging approaches should be adopted as best practices. Building consensus around packaging decisions was challenging, but we were successful because we focused on our users first. We decided on which tools we thought would create the best packaging experience for scientists creating pure Python packages.
+
+[Check out the GitHub pull requests for packaging guide pages](https://github.com/pyOpenSci/python-package-guide/pulls?q=is%3Apr+sort%3Acomments-desc+is%3Aclosed) if you're curious about the feedback and discussions that we had when writing the packaging guide. Notice the number of comments on the most popular PRs. The sheer volume of comments on some of the early PRs associated with packaging build tools speaks to the various issues, complexity, and decisions we needed to make.
+
+## **Building Python packaging consensus and developing the pyOpenSci Python Packaging Guide**
+
+The success of our Python Packaging Guide is due to extensive community input.
+We directed Python Packaging Guide contributors towards the objective of simplifying Python packaging for beginners. Focusing on a specific audience allowed contributors to make decisions about the content in the Guidebook more easily. It also ensured that the outcome text is easy to understand for beginners and for scientists who prefer to avoid delving into packaging nuances. In each review, we made sure to include a diverse group of reviewers, including:
+
+* **packaging tool maintainers:** We asked each maintainer from Flit, PDM, Hatch, and Poetry to provide feedback on our overviews of their tools,
+* **[PyPA](https://www.pypa.io/en/latest/) members** who have already developed packaging resources that serve the broader Python community,
+* **core scientific Python community members** who are maintaining tools like Matplotlib, Numpy, and Pandas that require more technical complex builds, and
+* **scientists with varying levels of packaging expertise:** This group is most important as packaging beginners provide the lens of what is confusing and ensure that the technical content is more beginner-friendly.
+The truly collaborative effort of creating the Python Packaging Guide resulted in a beginner-friendly and accurate guide that the pyOpenSci community now maintains and continuously updates.
+
+It was essential to have a mix of content reviewers with a range of packaging expertise to make the guide accurate and accessible. Some were packaging experts building packaging tools, and others were beginners, the audience for whom we wrote the guide.
+
+### What's in the pyOpenSci Python Packaging Guide?
+
+The pyOpenSci packaging guide provides an overview of the Python packaging ecosystem to support users who want to understand the packaging landscape. These users may want to decide on their own which tools best serve their needs. The guide also defines core packaging terms that can make the ecosystem seem more complex than it is, such as:
+
+* [build backend](https://www.pyopensci.org/python-package-guide/package-structure-code/python-package-build-tools.html#build-back-ends),
+* [build frontend](https://www.pyopensci.org/python-package-guide/package-structure-code/python-package-build-tools.html#python-package-build-front-ends),
+* [wheel](https://www.pyopensci.org/python-package-guide/package-structure-code/python-package-distribution-files-sdist-wheel.html), and
+* [sdist](https://www.pyopensci.org/python-package-guide/package-structure-code/python-package-distribution-files-sdist-wheel.html).
+
+Our Python Packaging Guide aims to translate the technical jargon that gets in the way of new users having a successful packaging experience. Over time, we
+hope that this will make packaging less confusing and more accessible to more people.
+
+{{< figure src="images/python-packaging/publish-python-package-pypi-conda.png" alt="Diagram that has the pyOpenSci logo in the upper left-hand corner with the pyOS flower. The diagram has four steps for making a package: create package structure, add code, add metadata to pyproject.toml, and finally, pip install package. The four steps are within arrows that point to two building shapes representing the PyPI and conda-forge warehouses. Below each of those steps, represented as storage houses, the code instructions for installing using a package from that warehouse is written out--python -m pip install yourpackage and conda install -c conda-forge yourpackage." caption="Our opinionated Python packaging tutorials demonstrate one way to create a Python package using modern packaging best practices. Through these tutorials, pyOpenSci has reduced the cognitive load for scientists who want to share their code. This graphic represents the steps a user needs to understand to make their code installable and create a basic Python package." >}}
+
+
+### Creating opinionated Python packaging tutorials
+
+{{< figure src="images/python-packaging/have-you-created-python-package-scipy-24.png" alt="This is a graphic that shows the results to a survey question. The question is--have you created a Python package before? The three options are Yes (18%), no (59%), and I struggled trying (24%)" caption="This response ratio of most people either struggling to create a package or never having created a Python package before is common when I ask this questions at events. More often than not, people want help learning packaging." >}}
+
+In addition to the ecosystem overview provided in the guide, I knew that we needed to have opinionated, complete Python packaging tutorials that guided users through the entire packaging process including:
+
+* [creating a package](https://www.pyopensci.org/python-package-guide/tutorials/create-python-package.html),
+* publishing it on [PyPI](https://www.pyopensci.org/python-package-guide/tutorials/publish-pypi.html), and
+* [conda-forge](https://www.pyopensci.org/python-package-guide/tutorials/publish-conda-forge.html).
+
+Most scientists (and packaging beginners) want to get the job done; they don't want to become packaging experts. A community presenter made this statement directly at the PyCon US 2023 Python packaging summit:
+
+> I just want to create a Python package. Where is the tutorial or
+> documentation that teaches me how to do that?
+{: .highlight-quote }
+
+Our Python packaging tutorials went through the same community development and review process as the rest of our Python Packaging Guide. We have also begun teaching the lessons; most workshop attendees have successfully created their first Python packages!
+
+{{< figure src="images/python-packaging/successfully-created-python-package-scipy-24.png" alt="Another survey result image. The question is: were you able to create a package? 91% responded yes (10 people), 9% (1 person) said no; no one responded 'I'm not sure'" caption="It's always hard to collect data at the end of a long workshop. Here, 11 out of 30+ people responded. Most people in our workshop were successful. We worked with the one person who responded 'no' after the survey at the end of the workshop. They successfully made their first package with our support! This feedback was similar to the success rates at our <a href='https://www.pyopensci.org/events/april-2024-create-python-package-pyopensci-online-workshop.html'>first online workshop</a>, held in May 2024." >}}
+
+
+### Teaching online lessons is the best way to ensure they stay current
+
+I have created hundreds of open online lessons both for ecologists [NEON](https://www.neonscience.org/resources/learning-hub/teaching-modules/quantifying-drivers-and-impacts-natural-disturbance-events) and earth and environmental scientists (formally earthdatascience.org). One of the biggest challenges is that it's easy for data science lessons to become dated quickly --especially in the rapidly evolving data science space. By teaching the lessons, we can update them regularly as the ecosystem evolves. We also often have users review the lessons at our [annual sprint events](/blog/pyopensci-pyconus-2024-sprints.html) to test them out; more on pyOpenSci beginner-friendly sprints below.
+
+<i class="fa-solid fa-heart-pulse" style="color: #B197FC;"></i><i class="fa-solid fa-heart-pulse" style="color: #B197FC;"></i><i class="fa-solid fa-heart-pulse" style="color: #B197FC;"></i><i class="fa-solid fa-heart-pulse" style="color: #B197FC;"></i><i class="fa-solid fa-heart-pulse" style="color: #B197FC;"></i><i class="fa-solid fa-heart-pulse" style="color: #B197FC;"></i>
+
+
+
+> Hi Leah. Thanks for the course today. I really enjoyed it. I heard about it from your post here in the Python channel so I'm glad you shared it here. I'll keep my eye out for more coming up and will be referring to the tutorials and guides on your site. Hopefully you work out the spatial chat because that seemed to have a lot of potential! I also want to let you know that I got a ton of value out of your materials on the CU Open Earth data analytics site, and it's still my go-to resource to point people to when they ask me how to get started learning the open source spatial stack. So thank you!
+>
+> — Michael Harty, Software Underground Community
+
+
+
+<i class="fa-solid fa-heart-pulse" style="color: #B197FC;"></i><i class="fa-solid fa-heart-pulse" style="color: #B197FC;"></i><i class="fa-solid fa-heart-pulse" style="color: #B197FC;"></i><i class="fa-solid fa-heart-pulse" style="color: #B197FC;"></i><i class="fa-solid fa-heart-pulse" style="color: #B197FC;"></i><i class="fa-solid fa-heart-pulse" style="color: #B197FC;"></i>
+
+In addition to the valuable feedback we receive from our community, the data we collect through [Matomo web analytics](https://matomo.org/) shows our guide's usage and growth.
+I will leave web and social media growth, which have also shown extraordinary growth for future posts!
+
+### The power of community: Translating the guide & tutorials to other languages
+
+The success of our packaging guide has been remarkable, thanks to the tremendous input and feedback from the community. What began as a simple guide has evolved into a collaborative project, with enthusiastic participation from contributors worldwide.
+
+
+> @leahawasser @pyOpenSci clicking through and eventually found myself looking at 'what is a Python package' and involuntarily performed a standing ovation. bookmarked it as an example of great docs for an incredibly complex subject with many meanings in many different contexts
+>
+> — Mastodon Toot
+
+
+[View toot on mastodon](https://circumstances.run/@hipsterelectron/112557545629456885)
+
+At our last PyCon sprint, a then-new contributor, [Felipe Moreno](https://www.github.com/flpm), set up translation infrastructure for our guide. The translation infrastructure uses a Sphinx extension that allows contributors to translate as much or as little of the guide as they wish. This process supports
+small iterative pull requests that any contributor with little time can make.
+
+```markdown
+#: ../../documentation/hosting-tools/intro.md:3
+msgid ""
+"The most common tool for building documentation in the Python ecosystem "
+"currently is Sphinx. However, some maintainers are using tools like "
+"[mkdocs](https://www.mkdocs.org/) for documentation. It is up to you to "
+"use the platform that you prefer for your documentation!"
+msgstr ""
+"Sphinx es la herramienta más común para construir documentación en el "
+"ecosistema de Python. Sin embargo, algunos mantenedores están usando "
+"herramientas como [mkdocs](https://www.mkdocs.org/) para generar la "
+"documentación. ¡Es tu decisión usar la herramienta que prefieras para tu "
+"documentación!"
+```
+
+Felipe's translation infrastructure contribution has sparked significant community momentum. As I write this, pyOpenSci contributors are actively translating our Python Packaging Guide into Spanish and Japanese; we have had dozens of pull requests. One contributor may even teach the pyOpenSci Python packaging lessons at [PyCon Japan](https://2024.pycon.jp/en) next year! This entire effort underscores the power of community when guided in the right direction.
+
+Our guide is becoming a global resource!
+
+You may be wondering where all of these new contributors are
+coming from. We get many new active contributors when we lead events at core meetings.
+
+I'll talk about that next.
+
+## pyOpenSci at PyCon and SciPy 2024 -- sprints, talks and new contributors
+
+Sprints are one of my most favorite types of events to hold because they involve this [cool mix of learning, helping and community](/blog/pyopensci-pyconus-2024-sprints.html).
+
+### pyOpenSci sprints at Python meetings
+
+We started holding sprints at PyCon US in 2023.
+Engagement at pyOpenSci sprints has grown significantly since we started leading these events. This year alone, we engaged with over 50 contributors at sprints who have submitted 86 issues and pull requests!
+
+What is most impressive is many of our sprint participants have continued to contribute to pyOpenSci after our in-person sprint events.
+
+While pyOpenSci operates mainly as an online community, I find there is no better way to build a core community than by holding in-person events at large meetings. While we get plenty of expert Pythonistas at our sprints, our sprint events are always beginner-friendly. Many first-time contributors help pyOpenSci with various open issues on our [help-wanted GitHub project board](https://github.com/orgs/pyOpenSci/projects/3) while submitting their first pull requests and issues to GitHub.
+
+### pyOpenSci beginner-friendly sprints help us and also the community
+
+Beginner-friendly sprints represent a true win-win for both contributors and pyOpenSci. Contributors learn new skills, and pyOpenSci gets help with the vital work that we are doing.
+
+<div class="notice" markdown="1">
+
+### What is a community sprint?
+{: .no-toc}
+
+Community sprints are collaborative coding and documentation update sessions where new and experienced contributors work together on open-source projects. These sprints provide a supportive environment with guidance from project maintainers or experienced developers, helping participants contribute effectively. They are an excellent opportunity for learning, networking, and making meaningful contributions to the open-source community. [You can read more about that here.](https://www.pyopensci.org/blog/pyopensci-pyconus-2024-sprints.html)
+</div>
+
+
+| Year  | PRs & Issues | Contributors |
+|----------|----------|----------|
+| 2023 | 41  |  12 |
+| 2024 | 86  | 39   |
+
+
+### My talks at SciPy and PyCon US 2024
+
+Last year, I gave a talk at PyCon US at the [Maintainers Summit](https://www.pyopensci.org/blog/pycon-2023-packaging-presentation-sprints-leah-wasser.html#python-packaging-packaging-packaging).
+This year, I gave talks about both [SciPy's Maintainers Summit](https://www.youtube.com/watch?v=uCLlshkTBM0) and at [PyCon US - in the main track](https://www.youtube.com/watch?v=uCLlshkTBM0)! At PyCon, I spoke about how pyOpenSci is leveraging the community and building consensus on the thorniest topic: Python packaging. At SciPy, I focused on bringing the scientific community together to help solve Python packaging. I also overviewed our community-run scientific Python software peer review program and the success that we've
+had collaborating with [other partner communities, such as Astropy](https://www.pyopensci.org/software-peer-review/partners/astropy.html).
+
+Here is my SciPy video if you want to check it out now. :)
+
+## pyOpenSci's software peer review program is growing, too
+
+Funding has propelled pyOpenSci's peer review process forward. While pyOpenSci has run peer review since 2019, funding allowed us to document, formalize, and make the peer review program more sustainable and scalable. The [peer review guide](https://www.pyopensci.org/software-peer-review/) was one of the first things I worked on in the Fall of 2022. The goal of this guide was to
+define each role in the software peer review process,
+define policies around our review package scope, how we review, how we determine what is in scope, and more.
+The guide also documents our [community partnership program](https://www.pyopensci.org/partners.html), which we launched in 2024 through our collaboration with [Astropy](https://www.pyopensci.org/software-peer-review/partners/astropy.html).
+
+In four months, we published a shiny new peer review guide. In January 2023, we re-launched peer review again. Peer review submissions increased dramatically starting in January 2024 (see below).
+
+{{< figure src="images/peer-review/pyopensci-python-software-peer-review-growth.png" alt="A cumulative sum plot with months on the x-axis and number of review issues submitted on the y-axis. The curve starts with a small slope in 2019. Then, around January 2023, the slope becomes significantly steeper, indicating a dramatic increase in submissions when we reopened the peer review. At that point in the plot, there is a label that says 'Full-time funding'." caption="It is clear the impact that 1) working on our peer review guide and governance plus 2) funding, which allowed me to devote all of my professional time to pyOpenSci, had on our peer review program. It has been incredibly successful in the past year! And true success lies in the hands of the community that leads the review process. Today, on average, pyOpenSci has 10-14 packages in our software review queue." >}}
+
+<!-- TODO: rename  repo to "guide" (rename it to be metrics and then link to it) -->
+
+You can see more of our [peer review metrics on our MyST Markdown metrics dashboard here](https://www.pyopensci.org/metrics/peer-review/peer-review-status-dashboard.html)
+{: .button }
+
+
+### Is pyOpenSci's peer review program diverse?
+
+Diversity, equity, inclusion, and accessibility (DEIA) are core to everything that pyOpenSci does. But how do we know that we are aligning with that core value?
+
+Data can help us here, too. Here are a few insights from 93 people who have participated in our peer review program survey over the past two years. Our peer review participants represent a healthy mix of students, industry professionals, and academics.
+
+Almost half of the participants identify as having some computer science application in their work; 80% self-identify as scientists (as mentioned above).
+
+About 40% of our peer review participants identify as female, non binary, or non conforming.
+
+####  Open Source metrics
+
+Some of the open-source responses surprised me:
+
+* **60% of people maintainers have funding** to do their work! (*This number surprised me given the challenges I have seen in funding open source work.*), and
+* **70% of maintainers** report that outside contributors contribute to their projects through issues and pull requests.
+
+I'll dedicate another blog post to examining this data more thoroughly. Still, you can get the gist from the above summary: We have a strong representation of people from different career stages. However, we still need to do more to support increased gender and identity diversity.
+
+## A thoughtful, kind, and supportive community is what makes pyOpenSci special
+
+Every morning, I wake up and am excited to begin my work. It doesn't matter if I'm working on budgets and other Executive Director-type tasks or developing educational content and teaching (my two favorite things); I can't wait to see what messages pop up in my inbox, be it email or GitHub. I love my job because the pyOpenSci community is extraordinary.
+
+<i class="fa-solid fa-circle-check" style="color: #63E6BE;"></i> People care about our organization's mission to help scientists make their science more open and collaborative. So they can solve the world's greatest challenges.
+
+<i class="fa-solid fa-circle-check" style="color: #63E6BE;"></i> The community wants to help--be it each other or pyOpenSci as an organization.
+
+<i class="fa-solid fa-circle-check" style="color: #63E6BE;"></i> The community is kind; the discussions are engaging and people help each other.
+
+
+> I love the friendliness and positive energy around the combination of science+computing (in Python, too)! It's a lovely community of practice!
+>
+> — Titus Brown, Faculty - University of California, Davis
+
+
+The community also cares a lot about the scientific Python ecosystem and wants to see more robust software.
+
+
+> As maintainers of the Scientific Python library, we see great potential in pyOpenSci. Test, code, documentation, and internationalization. These are things we have gradually accumulated know-how for in order to create a robust library on GitHub. Now, these are about to be integrated by the pyOpenSci project.
+>
+> — Tetsuo Koyama - PyVista maintainer
+
+
+They care about the packaging guidelines we have worked so hard to co-create and the impact those guidelines and online resources have on scientists who are just trying to get their jobs done.
+
+
+> I'm hopeful that the standards established by pyOpenSci will help alleviate the reproducibility crisis, increasing public trust in science, accelerating progress, and making all our jobs a little bit easier!
+>
+> — Jackson Burns, MIT
+
+
+And, like me, the community cares deeply about education. The community wants to help
+eliminate the packaging and open science thorns. They want to make packaging (and using Python) more
+accessible to more people.
+
+
+> I love the educational aspect of pyOpenSci and how it focuses on removing the technical friction that prevents people from contributing to open source and open science. The community makes a conscious effort to create a welcoming culture and provide a safe place to learn for beginners. It helps prepare people for even bigger future contributions to the open science and open source movements.
+>
+> — Felipe Moreno  - Tech Industry Professional
+
+
+Carol below was more than just a participant! She also helped many students
+in their workshop learning experience.
+
+
+> As a participant in the first packaging workshop, I found that individual attention and focus on success were outstanding. The organization and approach to teaching a scientist how to create a package helped build skills and ongoing productivity.
+>
+> — Carol Willing - Open Source & Open Science Leader, Project Jupyter, Python Core Dev
+
+
+## Building a sustainability model for pyOpenSci so we can continue to thrive - what's next
+
+There’s a strong demand for the work pyOpenSci is doing. Still, every nonprofit or fiscally sponsored project has to ask:
+
+*How do we keep this going long-term?*
+
+Writing grants to bring in funding is essential, but I need to do more than just write grants. Writing grants takes tremendous energy, with only a ~10-20% chance of success. Also, grant calls usually focus on innovation. They do not often support project maintenance and daily operations.
+
+To ensure that pyOpenSci is sustainable, we’re rolling out paid online training events. Paid events are a revenue model used by other nonprofits in our ecosystem:
+
+NumFocus runs PyData and SciPy meetings
+The Python Software Foundation runs PyCon as a significant fundraising event.
+These paid events will support the low-cost training, event scholarships, free online tutorials, and resources we will continue to create and publish online.
+
+## What's next for pyOpenSci - The Road Ahead
+Our next training event is the inaugural pyOpenSci Fall Festival--a week-long event that teaches skills needed to:
+
+* write cleaner, more modular code,
+* package and share code,
+* publish and cite code, and
+* create reproducible reports that connect code, data, and outputs into a dynamically produced interactive publication.
+
+We also will develop collaborative GitHub lessons following the BSSw fellowship I received this year.
+
+<div class = "notice" markdown="1">
+## About Me
+My name is Leah, and I'm the executive director and founder of pyOpenSci. I have over 20 years of experience in both academic and nonprofit spaces and have dedicated my career to helping scientists overcome the challenges of open science. I've built and led two successful data science programs:
+
+1. **NEON Data Skills Program** at NEON, and
+2. **Earth Analytics Program** at CU Boulder.
+
+I'm now building  **pyOpenSci**--a vibrant, active, and diverse community of practice that supports open science and the open-source software that drives that science.
+
+The programs I build have consistently stayed at the cutting edge of technology through continual evaluation and a data-driven approach. Throughout my career, I've observed significant gaps between the innovative tools being developed and the training scientists receive, which has driven my work in bridging these gaps.
+</div>
diff --git a/content/blog/2024-09-17-pyopensci-sustainability-plan-2024.md b/content/blog/2024-09-17-pyopensci-sustainability-plan-2024.md
new file mode 100644
index 00000000..170f1d7b
--- /dev/null
+++ b/content/blog/2024-09-17-pyopensci-sustainability-plan-2024.md
@@ -0,0 +1,163 @@
+---
+title: 'A Blueprint for the Future: pyOpenSci''s Sustainability Model'
+date: '2024-09-17'
+type: blog
+excerpt: pyOpenSci is exploring various sustainability methods to supplement our valued
+  grant funding. Learn more about what we are exploring.
+author: Leah Wasser
+blog_topic: community
+toc: true
+comments: true
+url: "/blog/pyopensci-funding-sustainability.html"
+lastmod: '2024-10-15'
+image:
+  src: images/blog/headers/pyopensci-sustainability.png
+  alt: 'A Blueprint for the Future: pyOpenSci''s Sustainability Model'
+---
+
+## Introduction
+
+Funding is critical to the success of any nonprofit organization. In this blog post, I'll outline pyOpenSci's sustainability plan. We define sustainability as building a diverse funding "portfolio" that includes grants and internally generated revenue sources to support our mission, growth, and core activities.
+
+## How funding has propelled pyOpenSci forward
+
+Funding from [Sloan Foundation](https://sloan.org/) catalyzed pyOpenSci's growth by enabling me to dedicate full-time effort to growing the organization's impact in September 2022. This full-time commitment, paired with support from a fiscal sponsor, [catalyzed pyOpenSci's recent growth and success](/blog/what-pyopensci-accomplished-with-two-years-of-funding.html).
+
+{{< figure src="images/pyopensci-general/pyopensci-timeline2019-2024.png" alt="An image titled pyOpenSci timeline. showing key milestones from 2018 to 2024. The timeline is marked with flower icons and a small rocket to represent significant events. Key points include: 2018: Community Meetings Begin, 2019: Software Peer Review Launch,2021-2022: Sloan Funding, Fall 2022: Packaging Guide Rewrite Begins, January 2023: Peer Review Relaunched, Fall 2023: CZI funds pyOpenSci, Spring 2024: pyOpenSci launches training and tutorials. The timeline progresses diagonally from the bottom left to the top right, with a rocket heading toward a bright light in the top right corner." caption="I founded pyOpenSci in 2018. It was mostly a side effort at the time driven forward by small community meetings and a pilot of a scientific Python peer review process." >}}
+
+For example, our scientific Python [software peer review program](https://www.pyopensci.org/software-peer-review/) significantly expanded after we reopened it in early 2023, following our governance and documentation improvements. Today, we average 10-14 packages in our review queue at any given time and have 18 volunteer editors and dozens of reviewers who drive peer review forward.
+
+You can see this profound impact in the plot below.
+
+
+{{< figure src="images/peer-review/pyopensci-python-software-peer-review-growth.png" alt="A cumulative sum plot with months on the x-axis and number of review issues submitted on the y-axis. The curve starts with a small slope in 2019. Around January 2023, the slope becomes significantly steeper, indicating a dramatic increase in submissions when we reopened the peer review. At that point in the plot, there is a label that says 'Full-time funding'." caption="It is clear the impact that 1) working on our peer review guide and governance plus 2) funding, which allowed me to devote all of my professional time to pyOpenSci, had on our peer review program. It has been incredibly successful in the past year! And true success lies in the hands of the community that leads the review process. Today, on average, pyOpenSci has 10-14 packages in our software review queue." >}}
+
+
+<!-- CSS FIX quote is 2 diff colors -->
+
+
+
+Today, the results of this momentum are clear. pyOpenSci has over **250 contributors** and runs a vibrant global Python software peer review process led by [**18 volunteer editors**](https://www.pyopensci.org/about-peer-review/index.html#meet-our-editorial-board), 74 reviewers, and 78 open source maintainers.
+
+### Funding supports beginner-friendly open source sprints
+
+Funding has also allowed us to run events. In the past year, over 51 people have participated in our beginner-friendly sprints, submitting 39 issues and 88 pull requests to pyOpenSci. Many of these pull requests and issues are first-time contributions from scientists and researchers who were excited about and nervous about contributing to an open source repository.
+
+Contributions to pyOpenSci have also skyrocketed in the past two years.
+
+{{< figure src="images/open-source/pyopensci-contributions-by-quarter.png" alt="Bar chart titled 'Staff vs. Volunteer Contributor by Quarter.' The chart shows counts of contributions made by staff and volunteers from 2018 Q4 through 2024 Q3. Contributions are stacked, with purple representing staff and green representing volunteers. The chart reveals a significant growth in contributions over time, particularly from 2022 onward, with a notable increase in both staff and volunteer contributions in 2023 and 2024. The pyOpenSci logo is in the bottom-right corner." caption="A bar plot showing staff vs volunteer contributions on GitHub over time. Funding has allowed us to support more volunteer activity over the past 2 years." >}}
+
+
+### Our Python packaging guide is making a splash
+
+One of our most impactful activities has been developing our community-vetted [Python packaging guide](https://www.pyopensci.org/python-package-guide/index.html), which includes beginning-to-end Python [packaging tutorials using Hatch](https://www.pyopensci.org/python-package-guide/tutorials/get-to-know-hatch.html). Developing our packaging guide has been a genuinely collaborative effort. We have built consensus around critical packaging decisions with numerous opinions on what is "best." In just under a year, our packaging guide's use has doubled, with ~20,000 unique page views in 2024.
+
+
+>  @leahawasser @pyOpenSci clicking through and eventually found myself looking at 'what is a Python package' and involuntarily performed a standing ovation. bookmarked it as an example of great docs for an incredibly complex subject with many meanings in many different contexts
+>
+> —  Mastodon Toot
+
+
+Our work around Python packaging has led pyOpenSci to take a more active role in broader Python packaging discussions, contributing to conversations at events like the annual [PyCon US packaging summit ](https://us.pycon.org/2024/events/packaging-summit/) and the [PyCon US maintainers summit](https://www.pyopensci.org/blog/pycon-2023-packaging-presentation-sprints-leah-wasser.html#python-packaging-packaging-packaging).
+
+Our work has not only made packaging more accessible to more scientists and researchers but also fostered a collaborative and inclusive community of practice where scientists, software maintainers, and Pythonistas engage, chat about open source and open science challenges, and support each other.
+
+
+## Diversification of funding sources
+
+Diversifying our funding sources is essential to pyOpenSci's success. We've been fortunate enough to receive two grants.
+This runway has given us ~three years to grow and demonstrate impact. As of September 2024, we are ~two years into that runway. We now need funding to become sustainable.
+
+Grant-based funding is tricky as it rarely supports project operations or "maintenance." Our long-term plan is to combine grant funding with paid training and events to support pyOpenSci's operations.
+
+In the short term, we need funding to develop our paid training model while continuing to develop the governance that allows our free programs, such as software peer review and development and maintenance of open education resources, to continue.
+
+More on that below.
+
+## Building sustainability: pyOpenSci's training program
+
+pyOpenSci is building a paid training event program that supports sustainability. This training will be delivered predominately online, but we will also continue to hold in-person events such as the [packaging workshop that we taught at SciPy 2024](/blog/pyos-scipy-2024-recap.html#pyopenscis-first-scipy-tutorial-was-a-huge-success-create-your-first-python-package).
+
+While we will charge for some training, access is integral to our training program. We will continue to develop ways to support broad participation and engagement in our programs, which is core to the pyOpenSci mission.
+
+We offer scholarships to ensure that our events are inclusive. Scholarships worked well for our [first successful online packaging training event](/events/april-2024-create-python-package-pyopensci-online-workshop.html) and allowed five people to attend our training at no cost. For our upcoming [Fall Festival](/events/pyopensci-2024-fall-festival.html) (more on that below), we are also developing a sponsorship program that will allow companies, organizations, and individuals to support scholarships directly.
+
+### Open education will always be a priority for pyOpenSci
+
+We will also continue to offer free, community-vetted, open education resources. If you know me, you also know that I am deeply committed to creating high-quality open education resources. Open education has been a part of every program that I've built (for example, www.earthdatascience.org) and NEON Data Skills.
+
+Our [Python packaging guide](https://www.pyopensci.org/python-package-guide/), which has ~80 contributors as I write this, is one successful example of community-vetted open education resources that the pyOpenSci community has co-created. It now has thousands of users.
+
+## With growth comes a need for governance
+
+As pyOpenSci's growth welcomes new contributors and community members, we must create space by creating processes, governance, and documentation around our programs to support continued community engagement. Doing this well requires require time and resources.
+
+Reflecting on these accomplishments, I am committed to ensuring that pyOpenSci's core programs and vibrant community of practice continues to thrive. The longevity of our mission hinges on developing a durable sustainability model that enables pyOpenSci to:
+
+* continue supporting the vibrant pyOpenSci community of practice, and
+* expand our programs to develop education resources that teach open science, reproducibility, and packaging topics.
+
+
+### How pyOpenSci allocates funds to support efficient growth
+
+I like to think of pyOpenSc as a scrappy, efficient organization. Scrappy means we are deeply committed to managing our resources as efficiently as possible. Our small, core paid team optimizes our time and online infrastructure to reduce costs and maximize impact.
+
+We minimize overhead costs by:
+
+* leveraging & building open source tools,
+* focusing funds on automating workflows using tools like CI (continuous integration) to reduce manual effort, and
+* prioritizing support for essential, high-impact activities that drive our mission forward.
+
+Looking to the future, we will only grow our core team as it aligns with our core budget. This strategic approach enables pyOpenSci to maintain the quality and reach of pyOpenSci programs while building a sustainable future.
+
+### Other nonprofits have done this well
+
+I am inspired by other organizations that have found their sustainability balance such as NumFOCUS and the Python Software Foundation. These organizations use events such as:
+
+* SciPy meetings,
+* PyData meetings, and
+* PyCon US
+
+These meetings are all community-driven. Each event funds the organization's core mission, vision, and values.
+
+I am further inspired by the membership model that The Carpentries has successfully employed to build core sustainability.
+
+pyOpenSci will experiment to find the balance between freedom, openness, and sustainability in our training program. I'm confident that we will succeed. I'm excited to pilot new approaches and continue evaluating how each approach impacts our sustainability goals while further developing and maintaining a diverse and inclusive community.
+
+As always, we want to hear from you. Your feedback helps shape our programs and ensures the long-term success of pyOpenSci.
+
+## What's next for pyOpenSci - The Road Ahead
+
+So, what's next for pyOpenSci's training program? We will continue to run different types of pilot training events, experimenting with various platforms, scales and approaches. These events will include both larger event like our upcoming Fall Festival and smaller workshops like the [packaging workshop that we taught in the Spring 2024](https://www.pyopensci.org/events/april-2024-create-python-package-pyopensci-online-workshop.html).
+
+We will experiment with a suite of training opportunities held at various price points using different types of sponsorship and scholarship models.
+
+Along the way, we want to hear from you! We know you want pyOpenSci to succeed too. We want to understand:
+
+* what's working well,
+* what could be better,
+* what topics should we cover,
+* where do you see opportunities to combine sustainability and training?
+
+As always, we'll collect your feedback as a part of each event. Your feedback and ideas are critical to iteratively improving upon and building out pyOpenSci so we can better serve the community. We look forward to embarking on this training program path with you.
+
+### Our next event - Fall Festival
+
+The next pilot event in our training series is our [virtual Open Science Fall Festival](/events/pyopensci-2024-fall-festival.html), October 28 - November 1 2024. This event is a combination of free talks, paid workshops, community engagement, and different sponsorship and scholarships models to ensure broad participation.
+
+We've wrapped a lot together into one event!
+
+Our goals for the Fall Festival are to:
+
+* empower you with technically-relevant open science skills,
+* call attention to and celebrate new and upcoming tools that support open reproducible science
+* build community, and
+* help raise funds for pyOpenSci operations that allow us to continue supporting community work.
+
+We're excited for this event! I'm excited to continue to test out these different approaches. And i'm excited about building and learning together with you and the broader scientific Python open science community.
+
+You can learn more about the [Open Science Fall Festival, here](/events/pyopensci-2024-fall-festival.html). Please reach out if you have any questions.
+
+We look forward to seeing you there!
+
+~ Leah with support from the [pyOpenSci Executive Council - Tracy Teal & Karen Cranston](/our-community/index.html#executive-council-leadership--staff)
diff --git a/content/blog/2024-10-10-pyOpenSci-celebrates-Inessa-pawson.md b/content/blog/2024-10-10-pyOpenSci-celebrates-Inessa-pawson.md
new file mode 100644
index 00000000..c85a14a1
--- /dev/null
+++ b/content/blog/2024-10-10-pyOpenSci-celebrates-Inessa-pawson.md
@@ -0,0 +1,60 @@
+---
+title: pyOpenSci celebrates Inessa Pawson
+date: '2024-10-10'
+type: blog
+excerpt: Inessa’s leadership and dedication have profoundly shaped the open source
+  community, from NumPy to NumFOCUS. Learn more about her contributions and impact.
+author: Leah Wasser
+blog_topic: community
+toc: true
+comments: true
+url: "/blog/pyopensci-celebrates-inessa-pawson.html"
+lastmod: '2024-12-05'
+image:
+  src: images/headers/pyopensci-floral.png
+  alt: pyOpenSci celebrates Inessa Pawson
+---
+
+# pyOpenSci Celebrates Inessa
+
+Today, I want to take a moment to celebrate a devoted pyOpenSci community member, colleague, and friend, [Inessa](https://github.com/InessaPawson/InessaPawson),
+who was just awarded the NumFOCUS Community Leadership award. In my opinion, no one is more deserving of recognition for their contributions and dedication
+to the open source community. Inessa's day job at [OpenTeams](https://otincubator.com/team.html) is devoted to open source, where she serves as the Open Source Program
+Manager. But her open source work extends far beyond her professional role!
+
+{{< figure src="images/people/Inessa-NumFocus-award-fall-2024.png" alt="Portrait of Inessa Pawson, recipient of the NumFOCUS Community Leadership Award 2024. In the image, Inessa has light skin, blue eyes, and is wearing red lipstick. Her hair is styled up, and she is dressed in a black blazer with a professional, confident expression. The background on the right side of the image is purple with the pyOpenSci logo at the top and a headline that reads: pyOpenSci Celebrates Inessa. Below this, there is text that announces her award. The image of the award certificate is shown next to her name. The text on the image highlights Inessa's leadership in the scientific Python community, including her involvement with the SciPy US,PyCon US, NumPy, and NumFOCUS." caption="Inessa receives the 2024 NumFOCUS Community Leadership award." >}}
+
+"Inessa Pawson receives the NumFOCUS Community Leadership Award 2024. Inessa, a pyOpenSci Advisory Council member, is celebrated for her impact in the scientific Python
+community, including co-organizing the SciPy US and PyCon US Maintainers Summits, serving on the NumPy Steering Council, and leading a number of contributor
+experience projects."
+
+I have tremendous admiration for Inessa's commitment to supporting the open source community, particularly in the scientific Python ecosystem. Her efforts reach
+far beyond pyOpenSci, impacting the broader open science and Python landscapes.
+
+## Inessa's open source contributions
+
+To foster opportunities for cross-project collaboration in open source and open science, Inessa has co-organized the [SciPy US conference](https://www.scipy2024.scipy.org)
+since 2020, establishing and serving on several committees (Maintainers Track, Teen Track, Tutorials, Social Activities, Mentorship Program, Hybrid Committee). She has
+also organized the NumFOCUS Project Summit for the past two years (2023 and 2024) and serves on the Scientific Python Project SPEC Steering Committee.
+
+Inessa has championed the NumFOCUS Code of Conduct (CoC) reform and the creation of the NumFOCUS CoC Working Group.
+
+Inessa is also a core contributor to the scientific Python community. Amongst many commitments within the scientific Python ecosystem, she has been serving
+on the **NumPy Steering Council** since 2021 and co-leading the **scikit-learn survey team** since early 2024. Inessa is a recipient of the 2019 NumPy
+New Contributor Award.
+
+What truly sets Inessa apart is her relentless commitment to community building. She is a founder and organizer of the CHAOSS Scientific Research Working Group,
+Tech Alliance of SWFL, PyLadies South Florida, and PySWFL (Python user group in SWFL). Inessa doesn’t just participate; she builds frameworks and fosters connections
+to ensure the sustainability of the communities that fuel scientific progress.
+
+## Inessa cares about DEIA - deeply
+
+Inessa’s leadership and passion for fostering inclusive, supportive communities also extend to her role on the pyOpenSci Advisory Council. She has always been
+there to talk through challenges as pyOpenSci has grown over the years. I see her as a key advisor behind pyOpenSci's success.
+
+## Inessa is also a devoted mom
+
+On top of all these accomplishments, Inessa is a dedicated mother to two wonderful, bright children who you may have run into at a PyCon US or SciPy US conference!
+And, on a personal note, Inessa is a wonderful friend and an incredible human being. I can't think of anyone more deserving of recognition.
+
+Her wide-ranging contributions make her a true leader in the open source community. I’m so happy to be able to take a moment to celebrate her impact.
diff --git a/content/blog/2024-10-28-human-dimension-data-science.md b/content/blog/2024-10-28-human-dimension-data-science.md
new file mode 100644
index 00000000..f2c8b7df
--- /dev/null
+++ b/content/blog/2024-10-28-human-dimension-data-science.md
@@ -0,0 +1,554 @@
+---
+title: The Human Dimension to Clean, Distributable, and Documented Data Science Code
+date: '2024-10-28'
+type: blog
+excerpt: Discover how to create clean, accessible, and impactful data science code
+  by focusing on the human side of coding practices. Here, Eric Ma shares insights
+  from his talk at the 2024 pyOpenSci Fall Festival. Learn key open science principles,
+  including readability, cognitive load, and the toolmaker’s mindset, and explore
+  practical strategies to enhance your work
+author: Eric J. Ma
+blog_topic: learn
+toc: true
+comments: true
+url: "/blog/human-dimension-clean-documented-data-science-code.html"
+lastmod: '2025-01-07'
+image:
+  src: images/blog/headers/eric-ma-header.png
+  alt: The Human Dimension to Clean, Distributable, and Documented Data Science Code
+---
+
+This post was originally posted on [Eric's blog](https://ericmjl.github.io/blog/2024/10/25/the-human-dimension-to-clean-distributable-and-documented-data-science-code/) in support of the [2024 pyOpenSci Open Science Fall Festival](/events/pyopensci-2024-fall-festival.html).
+
+<figure class="align-center">
+<picture>
+  <source srcset="/images/blog/2024/eric-ma-blog-post-header.webp" type="image/webp">
+  <img src="/images/blog/2024/eric-ma-blog-post-header.png" alt="An illustration of a diverse group of people collaboratively analyzing and discussing code displayed on a large transparent screen, surrounded by books, plants, and abstract symbols, set against a vibrant gradient background." />
+</picture>
+## Introduction
+
+Since 2016 (8 years now!),
+I've been advocating for data scientists
+to apply basic software development practices in their work.
+This means making sure that one's work is well-documented -- and thus easily understandable,
+working in a way that is portable across machines -- and thus easily accessible,
+making sure that one's code is modular -- and thus easy to reuse,
+and ensuring that one's code is well-tested -- and thus reliable. (Table 1)
+In this post,
+we'll dive deeper into why it is crucial for making your work impactful
+to consider the psychology of people
+who read, install, and use your work.
+We'll explore the "why" behind the "what"
+that will be covered in the upcoming pyOpenSci training course.
+This training course will be teaching you a lot of valuable skills - the "what to do" -
+and I'd like to help reinforce the "why" behind all of these.
+By understanding the reasoning and motivation behind these practices,
+you'll be better equipped to apply them effectively
+and adapt them to your specific needs in data science projects.
+
+| Practice                 | Benefit               |
+|--------------------------|-----------------------|
+| Well-documented          | Easily understandable |
+| Portable across machines | Easily accessible     |
+| Modular code             | Easy to reuse         |
+| Well-tested code         | Reliable              |
+
+_Table 1: Key practices and their benefits in data science code development._
+
+## Key concept 1: readability and cognitive load
+
+When we write code,
+it's easy to forget that we're not just communicating with machines,
+but with other humans as well - including our future selves.
+This principle is deeply ingrained in Python's philosophy,
+as expressed in "The Zen of Python" which states,
+"Readability counts."
+Python's emphasis on readability over performance
+underscores the importance of human-friendly code.
+Readability is crucial because it directly impacts the cognitive load
+placed on anyone trying to understand or use your code.
+
+### The importance of readability
+
+Readable code offers several significant benefits.
+
+First and foremost, it enables faster comprehension.
+When code is clean and well-structured,
+readers can quickly grasp its purpose and functionality,
+allowing them to understand the logic and flow more efficiently.
+
+This leads to the second advantage: easier maintenance.
+Code that is easy to read is also easier to debug, update, and extend,
+saving valuable time and resources in the long run.
+
+Furthermore, readable code greatly improves collaboration!
+When team members can easily understand each other's code,
+it fosters better teamwork and enables them to build upon each other's work more effectively.
+This synergy can lead to more innovative solutions and faster project completion.
+
+Lastly, clear and readable code reduces the likelihood of errors.
+When code is easy to interpret,
+there's less chance of misunderstanding its intent or functionality.
+This clarity minimizes the risk of introducing bugs during modifications
+or when integrating with other parts of the system,
+ultimately leading to more robust and reliable software.
+
+### A cautionary tale from my graduate school days
+
+During my graduate studies,
+I developed a complex data analysis project
+for identifying putative reassortant influenza viruses
+from the Influenza Research Database (IRD).
+While the algorithm was scientifically sound and potentially valuable,
+its implementation left much to be desired
+from a software engineering perspective.
+
+The project consisted of more than 10 separate Python scripts
+that had to be executed in a specific order.
+There was little to no documentation,
+and the code itself was not written with readability or maintainability in mind.
+You can find the original code repository [here](https://github.com/ericmjl/influenza-reassortment-detector)
+to see an example of what **not** to do.
+
+The project had several significant drawbacks:
+
+- **Lack of modularity**: The scripts were tightly coupled, making it difficult to reuse or modify individual components.
+- **Poor documentation**: Without clear documentation, understanding the purpose and workflow of each script was challenging.
+- **Difficult deployment**: The complex execution order and tight coupling to a GridEngine HPC cluster made it nearly impossible for others to deploy or use the tool effectively.
+
+The consequences of this poor code quality
+became apparent when the IRD team
+expressed interest in incorporating my algorithm into their database.
+I remember being engaged with them in discussion,
+and was excited to see my work potentially being used
+by researchers around the world.
+However, the barrier to deployment was immense
+due to the scrappy implementation and lack of documentation.
+While I never knew what the real reasons were behind-the-scenes,
+I can only imagine that the lack of a well-documented,
+modular, and easily deployable solution
+was a major barrier to the adoption of my work.
+
+This experience taught me a valuable lesson
+about the importance of writing clean, well-documented, and easily deployable code,
+even in academic settings.
+Had I invested more time in proper software development practices,
+my work could have had a much broader impact
+and been more easily adopted by the scientific community.
+
+### The impact of readability
+
+By prioritizing readability,
+we can significantly enhance the overall quality and impact of our data science projects.
+Readable code:
+
+1. Reduces the cognitive load on users, making it easier for them to understand and use your code.
+2. Encourages collaboration and knowledge sharing within the data science community.
+3. Improves the maintainability and longevity of your codebase.
+4. Enhances the overall credibility and professionalism of your work.
+
+Remember, the goal is to create tools and analyses
+that others can easily access, understand, and build upon.
+By embracing the human dimension of our code,
+we not only improve our individual projects
+but also contribute to the growth and accessibility
+of the entire field of data science.
+
+## Key concept 2: User-friendly installation and setup
+
+The ease of installation and setup
+can make or break the adoption of your data science package.
+Even the most brilliant code is useless
+if users can't get it running on their systems.
+Let's explore the psychological barriers users face
+and how to overcome them.
+
+### The psychology of installation friction
+
+When users encounter complex installation processes,
+they often face several psychological barriers.
+
+**Barrier 1 - Complexity**:
+First, the sheer complexity can be overwhelming,
+causing users to abandon the installation before they even begin.
+This initial hurdle can be particularly daunting
+for those who are less technically inclined
+or new to the field.
+
+**Barrier 2 - Frustration**:
+Secondly,
+users may experience frustration when installations fail
+or when they encounter unclear error messages.
+These setbacks can be discouraging,
+potentially leading users to give up on further attempts to install and use the software.
+I remember the early days of installing SciPy!
+Nowadays, it's so easy:
+`pip install scipy` or `conda install scipy` and you've got it installed.
+But back then, I was wrangling C compilers and linker flags at the terminal...
+as a 3 month old programmer!
+Anyways, the negative emotions associated with these experiences
+can create a lasting impression,
+deterring users from trying again in the future.
+
+**Barrier 3 - Time Pressure**:
+Many users, particularly those in professional settings,
+have limited time to experiment with new tools.
+If the installation process is time-consuming or requires multiple attempts,
+your potential users may decide that the potential benefits of the tool
+are not worth the time investment required to get it up and running.
+Your impact, as a result, is diminished --
+especially because your users missed the opportunity
+to leverage what you've built!
+
+**Barrier 4 - Imposter Syndrome**:
+Difficulties in the setup process
+can trigger feelings of imposter syndrome.
+When users struggle to install or configure a tool
+that they believe should be straightforward,
+they may begin to question their own competence.
+This self-doubt can be a powerful deterrent to adoption,
+as users may avoid tools
+that make them feel inadequate or out of their depth.
+
+### Two perspectives on setup: User vs. Developer
+
+When we talk about "getting set up" with a data science package or project,
+it's important to recognize that this can mean two distinct things,
+depending on the user's intentions:
+
+**Installing a tool for use**:
+This is the perspective of an end-user who wants to leverage your package as a tool in their own work.
+They're primarily concerned with getting the package installed and running quickly,
+without needing to understand or modify the underlying code.
+
+**Installing to contribute**:
+This is the perspective of a developer or contributor
+who wants to explore, modify, or contribute to your project's code.
+They need to set up a full development environment,
+which often involves more steps and a deeper understanding of the project structure.
+
+Each of these scenarios presents its own set of challenges and psychological barriers:
+
+For tool users, the focus is on simplicity and speed.
+They want a straightforward installation process,
+ideally with a single command like `pip install your-package`.
+Complex dependencies or platform-specific instructions can be major deterrents.
+
+For developers, the process is inherently more involved.
+They need to clone the repository,
+set up a virtual environment,
+install development dependencies,
+and possibly configure additional tools like linters or test runners.
+While they may be more technically inclined,
+a clear and well-documented setup process is still crucial to encourage contributions.
+
+By recognizing and addressing both of these perspectives in your documentation and setup process,
+you can create a more inclusive and user-friendly experience for all potential users of your project,
+whether they're simply using it as a tool or diving deep into the code.
+
+### The impact of user-friendly setup
+
+By prioritizing a smooth installation and setup process:
+
+1. You lower the barrier to entry for potential users.
+2. You increase the likelihood of adoption and continued use.
+3. You create a positive first impression, encouraging users to explore your package further.
+4. You reduce the support burden, as fewer users encounter installation issues.
+
+Think back to the moment that you picked up someone else's Python package
+and it _just worked_... wasn't that a magical feeling?
+When you build a tool, you'll want to get users to the "aha!" moment
+of using your package as quickly and painlessly as possible.
+Every step you can eliminate or simplify in the setup process
+is a win for user adoption and satisfaction.
+
+## Key concept 3: Documentation as a bridge to understanding
+
+Documentation is often treated as an afterthought in data science projects,
+but it's a crucial bridge between your code and its users.
+Good documentation can make the difference
+between a project that gathers dust
+and one that becomes widely adopted and built upon.
+The Diataxis framework,
+developed by Daniele Procida,
+provides an excellent structure
+for thinking about and organizing documentation.
+
+### The role of documentation
+
+The Diataxis framework identifies four distinct types of documentation, each serving a specific purpose:
+
+1. **Tutorials**: Learning-oriented guides that help new users get started quickly.
+2. **How-To Guides**: Problem-oriented instructions for completing specific tasks.
+3. **Explanation**: Understanding-oriented discussions that provide background and context.
+4. **Reference**: Information-oriented technical descriptions of the code.
+
+These four types of documentation serve different roles in a user's journey:
+
+1. **Onboarding**: Tutorials help new users quickly understand and start using your code.
+2. **Problem-Solving**: How-To Guides assist users in accomplishing specific tasks.
+3. **Deep Understanding**: Explanation sections provide insight into the why and how of your project.
+4. **Detailed Information**: Reference documentation offers a reliable source of information for all features and functions.
+
+### Types of documentation artifacts
+
+Within these four categories, you might create various documentation artifacts:
+
+1. **README**: The first point of contact for users, providing an overview and quick start guide.
+2. **API Documentation**: Detailed explanations of functions, classes, and modules (part of the Reference quadrant).
+3. **Tutorials**: Step-by-step guides for common use cases (part of the Tutorials quadrant).
+4. **Examples**: Practical demonstrations of how to use the code in real-world scenarios (often part of How-To Guides).
+5. **Inline Comments**: Explanations within the code itself for complex logic or algorithms (can feed into Reference documentation).
+
+By structuring your documentation according to the Diataxis framework,
+you can ensure that you're meeting the diverse needs of your users,
+from newcomers to experienced developers looking for specific information.
+
+### Best practices for effective documentation
+
+When it comes to creating effective documentation,
+there are several key practices to keep in mind.
+
+**Contemporaneous documentation**:
+First and foremost,
+it's crucial to write documentation as you code,
+rather than leaving it as an afterthought!
+Leaving just-in-time comments
+can help you preserve critical details that may be handy
+for future readers of your code.
+This approach ensures that your documentation remains accurate and complete,
+reflecting the most up-to-date state of your project.
+
+**Clear language**:
+Clear language is paramount in documentation.
+Avoid using jargon or overly technical terms without explanation.
+Instead, strive to explain complex concepts in simple, accessible language
+that a wide range of users can understand.
+This clarity helps reduce the learning curve for new users
+and makes your project more approachable.
+If you use tools like Quarto or MyST,
+you can use pop-ups, sidebars, and callouts
+to help ~~disambiguate~~ explain terms.
+
+**Examples**:
+Examples are a powerful tool in documentation.
+Whenever possible,
+include code snippets and use cases
+that illustrate how to use your package.
+These practical demonstrations can help users
+quickly grasp how to apply your code to real-world scenarios,
+bridging the gap between theory and practice.
+
+**Regular updates**:
+As your project evolves,
+so should your documentation.
+Regularly reviewing and updating your documentation
+is essential to ensure it remains relevant and accurate.
+This ongoing maintenance helps prevent confusion and frustration
+that can arise from outdated or incorrect information.
+
+Personally,
+I've been building GenAI tooling
+to help me identify out-of-date documentation
+as my codebase evolves,
+as well as update the documentation directly.
+I've been prototyping this in LlamaBot,
+and if you're interested in talking about it,
+I'm more than happy to chat!
+
+**Tooling**:
+Finally, consider leveraging documentation tools
+to enhance the presentation and organization of your content.
+Documentation systems, such as Quarto and MkDocs
+can help you create professional-looking documentation
+that's easy to navigate and visually appealing.
+These tools can significantly improve the user experience,
+making your documentation more engaging and effective.
+Additionally, use LLMs to help you draft documentation!
+It'll help you get over writer's block.
+
+### The impact of good documentation
+
+Investing in quality documentation yields far-reaching benefits for your data science project:
+
+1. It increases user adoption and satisfaction
+2. It reduces support burden on maintainers
+3. It fosters a vibrant community by encouraging contributions
+4. It enhances project credibility and professionalism
+5. It maximizes code's potential and impact
+
+Remember, even the most brilliant code
+is only as valuable as users' ability to understand and implement it.
+High-quality documentation is the key that unlocks your code's full potential,
+amplifying its reach and influence in the field.
+By creating and maintaining excellent documentation,
+you're not just explaining your code –
+you're expanding its impact within the data science community and beyond.
+
+## How we operationalize these ideas at work
+
+At Moderna, where I work,
+I've been fortunate to be an early member of
+the Data Science and Artificial Intelligence teams.
+This gave me the opportunity to influence the ways of working
+of a team that was still figuring out how to operationalize these ideas in practice.
+We've implemented several concrete practices
+that bring these concepts to life in our daily work.
+
+### Code reviews
+
+One of our key practices is the consistent use of code reviews.
+Except for rapid prototyping that needs to be completed within an afternoon,
+we always conduct code reviews.
+While this process may slow us down in the short term,
+typically adding a day or two of waiting for colleagues to review,
+it pays off significantly in the long run.
+(Moreover, we use AI-assisted coding to speed up our code writing anyway,
+so not much is lost!)
+We move faster overall because of the growing shared knowledge across the team.
+Code reviews are particularly crucial
+for ensuring both the correctness and maintainability of our code.
+They also serve as an excellent way for team members
+to learn coding patterns from each other and maintain high code quality.
+It's worth noting that a hallmark of an experienced programmer
+is their ability to deploy effective patterns in their codebase.
+
+### Docathons and AI-assisted documentation
+
+We also emphasize the habit of writing documentation through regular "docathons."
+Every quarter, we set aside two days specifically for working on documentation.
+During these events, we focus on updating documentation for our various projects.
+These docathons serve a dual purpose:
+they are not only productive work sessions but also great team-building exercises.
+We find that newcomers to the team are particularly helpful during these events,
+as they assist in keeping our onboarding documentation up to date,
+providing fresh perspectives on what new team members need to know.
+
+In addition, we use AI to help us draft documentation.
+Modeling after [documentation tooling that I built for LlamaBot](https://github.com/ericmjl/llamabot/blob/main/docs/cli/docs.md),
+we use the same pattern at work to help us draft documentation,
+especially for routine, templated, and tedious-to-write documentation.
+Humans are still responsible for checking the drafted documentation,
+but at least we use AI tools to help us get started.
+
+### Standard project templates and automation
+
+To streamline our development process,
+we have implemented standard project templates and automation tools.
+Our approach is similar to Cookiecutter Data Science-templated projects,
+but with additional automation and customization specific to Moderna's needs.
+We make extensive use of pre-commit hooks and GitHub Actions
+to automatically check our code with every commit.
+This automation significantly alleviates
+the mental burden associated with manual checking.
+By leveraging these tools,
+we have effectively removed much of the human burden
+typically associated with nitpicking another person's code.
+Instead, we let the automated systems handle these checks,
+and we simply respond to what the "robots" tell us needs attention.
+
+### The impact of these practices
+
+Through these practices,
+we have created an environment where clean, distributable,
+and well-documented code is not just an ideal,
+but a daily reality.
+This approach has significantly enhanced our team's efficiency,
+collaboration, and the overall quality of our data science projects at Moderna.
+We engage in long-term research partnerships with our colleagues
+and can reliably take code from prototype to production with minimal overhead.
+We easily onboard new people onto projects
+thanks to the high-quality documentation provided.
+
+## Conclusion
+
+Throughout this keynote blog post,
+we've explored the critical human dimension of data science code,
+focusing on three key concepts:
+readability, user-friendly installation, and documentation.
+These elements,
+often overlooked in favor of algorithmic efficiency or cutting-edge techniques,
+are fundamental to the success and impact of your data science projects.
+
+**Readability** reduces cognitive load and fosters collaboration,
+inviting others to build upon our work.
+This openness drives scientific progress in data science.
+
+**User-friendly installation** lowers barriers to entry,
+encouraging wider adoption and increasing impact.
+A brilliant but unusable algorithm is effectively useless.
+
+**Documentation** bridges code and users,
+serving as a form of communication and teaching.
+Good documentation can transform users into contributors,
+fostering a community around your project.
+
+These practices are fundamental to open science and reproducible research.
+By making our code accessible and understandable,
+we enable verification, replication, and advancement of scientific work.
+This approach addresses the reproducibility crisis in many fields.
+Ultimately, we contribute to a more transparent and robust scientific ecosystem,
+not just improving individual projects.
+
+As data scientists, our goals are to create tools and analyses that make a real-world impact.
+By considering the human dimension to how our code gets used,
+we dramatically increase the chances of our work being used,
+understood, and built upon by others.
+As you go forward, be other-centered in your work,
+and treat your customers as you would want them to treat you!
+
+### Call to action
+
+As you embark on your next data science project, challenge yourself to:
+
+1. Prioritize readability from the start.
+2. Create a smooth installation process.
+3. Document as you go, not as an afterthought.
+4. Seek early user feedback.
+5. Contribute to open-source projects, focusing on documentation and user experience.
+
+Impactful data science isn't just about clever algorithms or big data.
+By adopting a toolmaker's mindset,
+we create knowledge that others can easily access, understand, and build upon.
+This approach enhances our ability to solve real-world problems creatively.
+
+Let's commit to writing code that's both computationally efficient and human-friendly.
+In doing so, we'll foster a more collaborative, innovative, and impactful data science community.
+Thank you for reading!
+
+## Additional Resources
+
+| Resource                                                           | Description                                                                                  |
+|--------------------------------------------------------------------|----------------------------------------------------------------------------------------------|
+| [The Hitchhiker's Guide to Python](https://docs.python-guide.org/) | An excellent resource for Python best practices, including code style and project structure. |
+| [Python Packaging User Guide](https://packaging.python.org/)       | Comprehensive guide on distributing Python packages.                                         |
+| [Write the Docs](https://www.writethedocs.org/)                    | A global community of people who care about documentation, with many resources and guides.   |
+| [Diataxis Framework](https://diataxis.fr/)                         | Detailed explanation of the documentation framework mentioned in this post.                  |
+
+
+## FAQ
+
+**Should I be using AI tools to help me code?**
+Yes! And make sure you are ready to defend every line of code that is produced by an AI tool.
+My personal conviction is that humans who write with AI assistance
+will be the ones who are able to turbocharge their effectiveness.
+At the same time, humans are the ones who are responsible for the end product.
+So, let AI assist you, but don't relinquish your responsibility!
+
+**Should I be using AI tools to help me write my documentation?**
+Yes! And just like with code,
+make sure you are ready to defend every line of documentation that is produced by an AI tool.
+In fact, I wrote this blog post with the help of Claude 3.5 Sonnet,
+in which I drafted out my ideas in bullet point format
+and then asked Claude to help me flesh out each section one at a time
+into a cohesive written piece.
+And I'm ready to defend every line that's in this blog post
+or else be willingly corrected!
+
+**What if I don't have time to write documentation?**
+Use AI tools to help!
+But if you're in an airgapped environment with no access to AI tools over an API,
+see if you're able to procure hardware to run local LLMs on your own machine.
+It turns out that we have supercomputers (by 1980s standards) in our pockets,
+on our laps, and on our desks,
+and the total amount of compute capacity that just runs idle is staggering.
diff --git a/content/blog/2024-12-13-pyOpenSci-job-communications.md b/content/blog/2024-12-13-pyOpenSci-job-communications.md
new file mode 100644
index 00000000..170384fd
--- /dev/null
+++ b/content/blog/2024-12-13-pyOpenSci-job-communications.md
@@ -0,0 +1,96 @@
+---
+title: CLOSED pyOpenSci is hiring a Communications Lead
+date: '2024-12-13'
+type: blog
+excerpt: pyOpenSci is hiring a part-time Writer and Social Media Specialist to enhance
+  communication and engagement within the scientific Python community. This flexible,
+  remote role involves creating social media content, newsletters, and blogs and fostering
+  community interaction on social media to support open source and open science. Join
+  us to make a meaningful impact on the open source ecosystem!
+author: Leah Wasser
+blog_topic: updates
+toc: true
+comments: true
+url: "/blog/pyopensci-job-communications.html"
+lastmod: '2025-05-14'
+image:
+  src: images/headers/pyopensci-floral.png
+  alt: CLOSED pyOpenSci is hiring a Communications Lead
+---
+
+**We are no longer accepting applications for this position. Thank you for your interest.**
+
+## CLOSED Job: writer & social media specialist
+
+*Last Updated: {{ page.last_modified}}*
+
+### About the role
+
+pyOpenSci seeks a talented Writer and Social Media Specialist to enhance our communications and engagement with the scientific Python community. This position involves crafting engaging content highlighting our [online learning content](https://www.pyopensci.org/lessons/), [tutorials](https://www.pyopensci.org/python-package-guide/tutorials/intro.html), [events](https://www.pyopensci.org/events/), and [package ecosystem](https://www.pyopensci.org/python-packages.html) for our social media channels, newsletters, and blog to keep our community informed and inspired. It also involved reviewing and editing educational content. This is an excellent opportunity for someone passionate about open science and skilled in clear, impactful communication. The position requires 10-15 hours per week at a rate of 25-40$/hour based on experience, with the flexibility of remote, part-time work. There is some flexibility in this position week-to-week based on pyOpenSci's deadlines. This is a non-regular, part-time, remote, non-exempt position. This position will report
+to the pyOpenSci Executive Director. Applicants must be eligible for employment in the United States.
+
+### About pyOpenSci
+
+[pyOpenSci](https://www.pyopensci.org/) is a vibrant and diverse scientific open source community that develops processes and guidelines for creating and maintaining scientific Python packages and develops educational content around creating Python packages, sharing code, and engaging in open science practices. Our mission is to help make science more open and collaborative while also increasing the participation of groups that have been traditionally underrepresented in the open source community.
+
+pyOpenSci runs an [open peer review process for scientific Python software.](https://www.pyopensci.org/about-peer-review/index.html) Through this program, we reinforce community-defined packaging guidelines while improving usability, documentation, and package quality. Further, we are curating a database of vetted scientific Python tools that are actively maintained.
+
+A core part of our mission is to increase the participation of historically underrepresented groups in open science and open source. We achieve this by providing mentorship, translating resources, offering training scholarships, and partnering with global organizations.
+
+pyOpenSci is a fiscally sponsored project of Community Initiatives.
+
+## Key responsibilities
+
+* **Social Media Management:** Create and schedule posts on platforms including Mastodon, LinkedIn, BlueSky, and YouTube. Ensure our content is engaging, consistent, and aligns with pyOpenSci’s mission.
+    * LinkedIn is currently our most active platform. As such, you will spend time writing our[ LinkedIn newsletters](https://www.pyopensci.org/handbook/community/social.html#social-accounts) and developing graphic and text content for posts that keep the community up-to-date and engaged with our efforts.
+    * pyOpenSci currently uses [Buffer](https://www.buffer.com) to manage scheduled posts and associated analytics.
+* **Content Creation:** Write and edit newsletters, [blog posts,](https://www.pyopensci.org/blog/) and other materials to update our community on pyOpenSci’s programs, new resources, and events.
+    * Create supporting graphics to enhance engagement.
+    * Contribute to and review online lessons being developed by pyOpenSci
+* **Community Engagement:** Interact with our online community to foster engagement, respond to questions, and keep conversations aligned with our goals.
+* **Content Planning:** Work with the pyOpenSci team to develop a content calendar that supports key events, initiatives, and outreach goals.
+
+pyOpenSci also has plans to launch a YouTube channel. Video editing skills are not required for this position but are a bonus.
+{: .notice }
+
+### What we’re looking for
+
+* **Communication Skills:** Excellent written communication skills with experience creating strategic content for social media, blogs, and newsletters.
+* **Community-Oriented:** Passion for engaging with the scientific community and supporting our open science mission.
+* **Attention to Detail:** Strong proofreading skills and a knack for creating polished, professional, engaging content.
+* **Organized and Reliable:** Ability to work independently, manage time effectively, and meet deadlines in a remote environment.
+* **Visual Content Creation Skills:** Proficiency in creating visually appealing social media graphics with an eye for design and aesthetics, ensuring content is engaging and on-brand.
+
+## About You
+
+* Broadly familiar with open science and open source principles and excited about developing content that promotes these principles.
+* Experienced in science communication, writing, or a related field.
+* Fluent in written and spoken English.
+
+### Preferred but not required qualifications
+
+* Experience using Python and Git/GitHub.
+* Familiarity with video content creation or editing.
+
+### What you can expect
+
+In this role, you’ll work closely with our executive director and engage with the pyOpenSci community to amplify our message and increase our visibility. You’ll be able to contribute creatively to our communications and make a tangible impact on the open science movement.
+
+## Equal employment opportunity
+
+Community Initiatives is an equal opportunity employer and considers applicants for employment regardless of age, race, color, religion, creed, sex, sexual orientation, gender identity or expression, national origin, marital status, disability, or protected veteran status.
+
+## How to apply
+
+We encourage applications from candidates of all backgrounds, especially those traditionally underrepresented in open science and open source communities.
+To apply, please email admin@pyopensci.org with the following:
+
+* A current resume.
+* A cover letter that discusses your experience developing social content. In that cover letter, please include at least one link, image, or example of each of the following:
+    * Social posts that you have created (ideally with graphics you have created),
+    * A blog post that you have written that you are proud of
+    * Optional: If you have created video content before, please include an example.
+
+Please submit example materials as links or attachments as you see fit.
+
+Applications will be reviewed on a rolling basis.
diff --git a/content/blog/2025-01-17-quadratik.md b/content/blog/2025-01-17-quadratik.md
new file mode 100644
index 00000000..3bf3ce8e
--- /dev/null
+++ b/content/blog/2025-01-17-quadratik.md
@@ -0,0 +1,367 @@
+---
+title: 'QuadratiK: Collection of Methods Constructed using Kernel-Based Quadratic
+  Distances'
+date: '2025-01-17'
+type: blog
+excerpt: QuadratiK provides a set of goodness-of-fit tests, a clustering technique
+  using kernel-based quadratic distances, and algorithms for generating random samples
+  from Poisson kernel-based distributions (PKBD). QuadratiK has recently been accepted
+  into the pyOpenSci ecosystem.
+author: Raktim Mukhopadhyay
+blog_topic: software
+toc: true
+comments: true
+url: "/blog/quadratik.html"
+lastmod: '2025-02-06'
+image:
+  src: images/headers/pyopensci-quadratik.png
+  alt: 'QuadratiK: Collection of Methods Constructed using Kernel-Based Quadratic
+    Distances'
+---
+
+## Introduction
+
+`QuadratiK` provides a suite of methods based on kernel-based quadratic distances, and hence the name!
+
+`QuadratiK` contains several goodness of Fit (GoF) tests such as normality tests and two and k-sample tests. It also includes tests for uniformity on the d-dimensional sphere, a clustering algorithm using Poisson kernel densities, and algorithms for generating random samples from PKBD. `QuadratiK` offers graphical functions that enhance user experience by facilitating the validation, visualization, and interpretation of clustering results. Furthermore, it provides methods for meaningful analyses and reproducible inference across diverse fields. A dashboard application with a user-friendly interface is also a part of `QuadratiK` to enhance accessibility for practitioners beyond the domain of statistical sciences.
+
+**This package is joint work with Dr. Marianthi Markatou, SUNY Distinguished Professor, University at Buffalo and Dr. Giovanni Saraceno, Assistant Professor, University of Padova.**
+
+
+## Goodness-of-Fit (GoF) Tests
+
+Goodness-of-Fit (GoF) tests are classical tools for assessing the compatibility of data with a given probability model. GoF tests typically compute a distance-like metric between the null distribution and observations, rejecting the null hypothesis if the distance exceeds a critical value.
+
+The methods for normality, two-sample, and k-sample test use a bandwidth parameter `h`. We have also provided an algorithm for determining the optimal value of `h` based on the mid-power analysis (please see Markatou and Saraceno (2024)). You can find more details on algorithm in our [manual](https://quadratik.readthedocs.io/en/latest/user_guide/hselect.html).
+
+In this section, the various GoF tests are shown with corresponding examples.
+
+### Normality Test
+
+Normality tests are used to determine if the sample data is well-modeled by a normal distribution. In our case, this is done by measuring the distance between the sample data and the target distribution, where the target distribution in this case is the d-dimensional normal distribution.
+
+In our case, this is done by measuring the distance between the empirical cumulative distribution function of the sample data and the target distribution, where the target distribution in our case is the d-dimensional normal distribution.
+
+```python
+iimport numpy as np
+
+np.random.seed(0)
+from QuadratiK.kernel_test import KernelTest
+
+# data generation
+data_norm = np.random.multivariate_normal(mean=np.zeros(4), cov=np.eye(4), size=500)
+
+# performing the normality test
+normality_test = KernelTest(
+    h=0.4, num_iter=150, method="subsampling", random_state=42
+).test(data_norm)
+
+# printing the summary for normality test
+print(normality_test.summary(print_fmt="grid"))
+```
+
+The results of this test is shown below.
+<figure style="float: center;">
+<picture>
+  <source srcset="images/quadratik/normality-test-results.webp" type="image/webp">
+  <img src="images/quadratik/normality-test-results.png" alt="Results for the Normality Test." />
+</picture>
+The test rightly fails to reject the null hypothesis, as the samples have been generated from a standard normal distribution.
+
+### Two-Sample Test
+The two-sample GoF test is used to  determine whether two separate samples are likely drawn from the same population distribution.
+
+To illustrate the two sample test, we generate n = 200 random samples from a multivariate standard normal distribution and a skewed normal distribution with value of skewness parameter lambda = 0.1.
+
+```python
+import numpy as np
+
+np.random.seed(0)
+from scipy.stats import skewnorm
+
+from QuadratiK.kernel_test import KernelTest
+
+# data generation
+X_2 = np.random.multivariate_normal(mean=np.zeros(4), cov=np.eye(4), size=200)
+Y_2 = skewnorm.rvs(
+    size=(200, 4),
+    loc=np.zeros(4),
+    scale=np.ones(4),
+    a=np.repeat(0.1, 4),
+    random_state=20,
+)
+# performing the two sample test
+two_sample_test = KernelTest(h=2, num_iter=150, random_state=42).test(X_2, Y_2)
+
+# printing the summary for the two sample test
+print(two_sample_test.summary(print_fmt = "grid"))
+```
+
+The results of the test is shown below.
+<figure style="float: center;">
+<picture>
+  <source srcset= "images/quadratik/two-sample-test-results.webp" type="image/webp">
+  <img src= "images/quadratik/two-sample-test-results.png" alt="Results for the Two Sample Test." />
+</picture>
+The test rejects the null hypothesis, as the samples have been generated from two different distributions.
+
+### K-Sample Test
+
+Similar to the two-sample test, the k-sample test examines whether k groups of samples are obtained from the same distribution.
+
+For illustrating the k-sample test, we use the glass identification dataset from the [UCI ML repository](https://archive.ics.uci.edu/dataset/42/glass+identification). We use the first three classes of glass types to illustrate the working of the k-sample test.
+
+```python
+# Importing required libraries
+from ucimlrepo import fetch_ucirepo
+import numpy as np
+from QuadratiK.kernel_test import KernelTest
+
+# Fetching the dataset
+glass_identification = fetch_ucirepo(id=42)
+
+# Selecting the data for specified types of glass
+filtered_data = glass_identification.data.original.query("Type_of_glass in [1, 2, 3]")
+X = filtered_data.drop(columns=['Type_of_glass'])
+y = filtered_data['Type_of_glass'].to_numpy()
+
+# Setting random seed
+np.random.seed(0)
+
+# Performing the Kernel Two-Sample Test
+k_sample_test = KernelTest(h=2, num_iter=150, random_state=42).test(X, y)
+
+# Printing the test summary
+print(k_sample_test.summary(print_fmt="grid"))
+```
+The results of the test is shown below.
+<figure style="float: center;">
+<picture>
+  <source srcset= "images/quadratik/k-sample-test-results.webp" type="image/webp">
+  <img src= "images/quadratik/k-sample-test-results.png" alt="Results for the K-Sample Test." />
+</picture>
+The null hypothesis is rejected for the k-sample test indicates that there is **significant evidence to conclude that at least one of the distributions among the three glass types is different**. In other words, the samples from the three classes of glass do not all come from the same underlying population distribution. This suggests that there are meaningful differences in the characteristics or features of the glass types being compared.
+
+### Uniformity Test on the Sphere
+
+In this we test the null hypothesis of uniformity on the sphere. We illustrate this test using an example.
+
+The data for this example is generated from a multivariate standard normal distribution, and is further divided by the L2 norm of generated vectors. This processed data is uniformly distributed on the surface of the unit sphere.
+
+```python
+import numpy as np
+
+np.random.seed(0)
+from QuadratiK.poisson_kernel_test import PoissonKernelTest
+
+# data generation
+z = np.random.normal(size=(500, 3))
+data_unif = z / np.sqrt(np.sum(z**2, axis=1, keepdims=True))
+
+# performing the uniformity test
+unif_test = PoissonKernelTest(rho=0.5, random_state=42).test(data_unif)
+
+# printing the summary for uniformity test
+print(unif_test.summary(print_fmt = "grid"))
+```
+The results of the test is shown below.
+<figure style="float: center;">
+<picture>
+  <source srcset= "images/quadratik/uniformity-test-results.webp" type="image/webp">
+  <img src= "images/quadratik/uniformity-test-results.png" alt="Results for the Uniformity Test." />
+</picture>
+## Clustering
+
+`QuadratiK` implements the Poisson kernel-based clustering algorithm on the sphere proposed by Golzy and Markatou (2020). We will demonstrate the spherical clustering capabilities of `QuadratiK` through an image segmentation task.
+
+The image we will be using is shown below, and the task is to identify the various regions (eg. entity or other features on interest in an image).
+
+<figure style="float: center;">
+<picture>
+  <source srcset="images/quadratik/dog-cat.webp" type="image/webp">
+  <img src= "images/quadratik/dog-cat.png" alt="Dog Cat Image." />
+</picture>
+Particularly, in this image a potential image segmentation task is to identify the various entities i.e. the cat and the dog in the image. Let's apply the clustering algorithm and see what does it return to us.
+
+```python
+import matplotlib.pyplot as plt
+from PIL import Image
+import numpy as np
+
+# Load and resize the image
+image = Image.open("dog-cat.png")
+new_size = (50, 50)  # Width, Height
+image = image.resize(new_size)
+
+# Convert the image to a NumPy array
+image_array_resized = np.array(image, dtype=float).reshape((-1, 3))
+image_array_resized = image_array_resized + 10**-6  # Avoid division by zero
+
+# Apply Poisson Kernel Based Clustering
+from QuadratiK.spherical_clustering import PKBC
+
+k_values = range(2, 11)
+pkbc = PKBC(num_clust=k_values, random_state=0).fit(image_array_resized)
+
+segmented_images = []
+
+plt.figure(figsize=(16, 8))
+
+num_k_values = len(k_values)
+num_cols = 6
+num_rows = (num_k_values + num_cols - 1) // num_cols
+
+for i, k in enumerate(k_values, start=1):
+    labels = pkbc.labels_[k]
+    labels_reshaped = labels.reshape(new_size[1], new_size[0])
+
+    np.random.seed(42)
+    unique_labels = np.unique(labels)
+    colors = np.random.randint(0, 255, size=(len(unique_labels), 3))
+    segmented_image = np.zeros((new_size[1], new_size[0], 3), dtype=np.uint8)
+
+    for label in unique_labels:
+        segmented_image[labels_reshaped == label] = colors[label]
+
+    segmented_images.append(segmented_image)
+
+    # Plot segmented image
+    plt.subplot(num_rows, num_cols, i)
+    plt.imshow(segmented_image)
+    plt.axis('off')
+    plt.title(f"Segmented (k={k})")
+
+plt.tight_layout()
+plt.show()
+```
+
+The image is segmented into k clusters with k ranging from 2 to 8. Below, we display the regions identified for each value of k.
+
+<figure style="float: center;">
+<picture>
+  <source srcset= "images/quadratik/dog-cat-segmented.webp" type="image/webp">
+  <img src= "images/quadratik/dog-cat-segmented.png" alt="Dog Cat Image Segmented" />
+</picture>
+Starting from k = 5, the segmented images reveal only minor changes in the identified segments upon closer examination. Let us see if we can validate our observation using the elbow plots.
+
+```python
+validation_metrics, elbow_plots = pkbc.validation()
+elbow_plots
+```
+<figure style="float: center;">
+<picture>
+  <source srcset= "images/quadratik/validation-dog-cat.webp"  type="image/webp">
+  <img src= "images/quadratik/validation-dog-cat.png"  alt="Dog Cat Image Validation Plots" />
+</picture>
+The elbow plots show a clear elbow at k = 5, which aligns with our observation that all regions of the image are effectively identified at this value of k.
+
+The clustering algorithm proposed in Golzy and Markatou has been used in other works such as Golzy et al. (2023), Strelnikoff at al. (2020), and Strelnikoff et al. (2024).
+
+## Sampling from PKBD
+
+In this example, we generate observations from the Poisson kernel-based distribution on the sphere. `QuadratiK` in Python implements two algorithms to generate random samples, the acceptance-rejection algorithm using the Mises-Fisher and angular central Gaussian distributions. In the example, we consider mean direction $\mu = (1,1,1)$ and dimension d = 3 with concentration parameter $\rho = 0.9$. We sample n = 500 observations for the available methods.
+
+```python
+# Import the PKBD class from the spherical_clustering module in the QuadratiK package
+from QuadratiK.spherical_clustering import PKBD
+# Instantiate the PKBD class
+pkbd = PKBD()
+# Generate 500 samples from PKBD using rejvmf
+samples_rejvmf = pkbd.rpkb(
+    n=500, mu=[1, 1, 1], rho=0.9, method="rejvmf", random_state=42
+)
+# Generate 500 samples PKBD using rejacg
+samples_rejacg = pkbd.rpkb(
+    n=500, mu=[1, 1, 1], rho=0.9, method="rejacg", random_state=42)
+```
+
+The generated samples can also be visualized on the unit sphere.
+
+```python
+import matplotlib.pyplot as plt
+import numpy as np
+
+# Plot samples on unit sphere
+phi, theta = np.mgrid[0 : np.pi : 100j, 0 : 2 * np.pi : 100j]
+x = np.sin(phi) * np.cos(theta)
+y = np.sin(phi) * np.sin(theta)
+z = np.cos(phi)
+fig = plt.figure(figsize=(5, 5))
+ax = fig.add_subplot(111, projection="3d")
+ax.view_init(azim=50, elev=30)
+ax.plot_surface(x, y, z, color="white", alpha=0.8, linewidth=0)
+ax.scatter(
+    samples_rejvmf[:, 0],
+    samples_rejvmf[:, 1],
+    samples_rejvmf[:, 2],
+    color="b",
+    s=25,
+    marker="*",
+    label="rejvmf",
+)
+ax.scatter(
+    samples_rejacg[:, 0],
+    samples_rejacg[:, 1],
+    samples_rejacg[:, 2],
+    color="red",
+    s=25,
+    marker="o",
+    label="rejacg",
+)
+ax.set_xlim([-1, 1])
+ax.set_ylim([-1, 1])
+ax.set_zlim([-1, 1])
+ax.set_aspect("equal")
+ax.tick_params(axis="both", labelsize=8)
+plt.legend(loc="upper right", fontsize=14)
+plt.tight_layout()
+```
+
+<figure style="float: center;">
+  <picture>
+    <source srcset= "images/quadratik/unit-sphere.webp" type="image/webp">
+    <img src= "images/quadratik/unit-sphere.png" alt="PKBD Samples on Unit Sphere."/>
+  </picture>
+<br>
+
+More details on Poisson Kernel-Based Distributions can be found in the package documentation [here](https://quadratik.readthedocs.io/en/latest/user_guide/pkbd.html).
+
+## Dashboard
+
+`QuadratiK` also provides a graphical user interface (GUI) that enables users to interact with its methods in a non-programmatic and user-friendly manner.
+
+```python
+from QuadratiK.ui import UI
+UI().run()
+```
+
+<figure style="float: center;">
+  <picture>
+    <source srcset= "images/quadratik/dash-landing.webp"  type="image/webp">
+    <img src="/images/quadratik/dash-landing.png" alt="Dashboard."/>
+  </picture>
+## Concluding Remarks
+
+`QuadratiK` provides methods to researchers and practitioners to delve deeper into their data, draw robust inference, and conduct potentially impactful analyses and inference across a wide array of disciplines. The `QuadratiK` package is also available in `R` and is hosted on [CRAN](https://cran.r-project.org/web/packages/QuadratiK/index.html). You can learn more about `QuadratiK` in our [arXiv preprint](https://arxiv.org/abs/2402.02290). Additional theoretical papers of interest are listed in the reference section.
+
+Please feel free to reach me at raktimmu at buffalo.edu.
+
+Thank you! Happy coding to you — may your bugs be few, and your data ever insightful! 🚀😊
+
+## References
+
+- Saraceno G., Markatou M., Mukhopadhyay R., Golzy M. (2024). Goodness-of-Fit and Clustering of Spherical Data: the QuadratiK package in R and Python. arXiv preprint arXiv:2402.02290.
+
+- Ding Y., Markatou M., Saraceno G. (2023). “Poisson Kernel-Based Tests for Uniformity on the d-Dimensional Sphere.” Statistica Sinica. DOI: 10.5705/ss.202022.0347.
+
+- Golzy M. & Markatou M. (2020) Poisson Kernel-Based Clustering on the Sphere: Convergence Properties, Identifiability, and a Method of Sampling, Journal of Computational and Graphical Statistics, 29:4, 758-770, DOI: 10.1080/10618600.2020.1740713.
+
+- Sablica, L., Hornik, K., & Leydold, J. (2023). Efficient sampling from the PKBD distribution. Electronic Journal of Statistics, 17(2), 2180-2209.
+
+- Markatou, M., & Saraceno, G. (2024). A unified framework for multivariate two-sample and k-sample kernel-based quadratic distance goodness-of-fit tests. DOI: 10.48550/arXiv.2407.16374v1
+
+- Golzy, M., Rosen, G. H., Kruse, R. L., Hooshmand, K., Mehr, D. R., & Murray, K. S. (2023). Holistic assessment of quality of life predicts survival in older patients with bladder cancer. Urology, 174, 141-149.
+
+- Strelnikoff, S., Jammalamadaka, A., & Warmsley, D. (2020, December). Causal maps for multi-document summarization. In 2020 IEEE International Conference on Big Data (Big Data) (pp. 4437-4445). IEEE.
+
+- Strelnikoff, S., Jammalamadaka, A., & Warmsley, D. M. (2024). U.S. Patent No. 11,907,307. Washington, DC: U.S. Patent and Trademark Office.
diff --git a/content/blog/2025-02-07-pyopensci-2024-a-year-in-review.md b/content/blog/2025-02-07-pyopensci-2024-a-year-in-review.md
new file mode 100644
index 00000000..fcc9f503
--- /dev/null
+++ b/content/blog/2025-02-07-pyopensci-2024-a-year-in-review.md
@@ -0,0 +1,206 @@
+---
+title: '2024: A Transformative Year for pyOpenSci'
+date: '2025-02-07'
+type: blog
+excerpt: 2024 was a transformative year for pyOpenSci. Through training, mentorship,
+  and peer review, we expanded our community, created free educational resources,
+  and empowered scientists worldwide. Here’s what we built together—and why it matters
+  now more than ever.
+author: Leah Wasser
+blog_topic: updates
+toc: true
+comments: true
+url: "/blog/2024-pyopensci-retrospective.html"
+lastmod: '2025-02-07'
+image:
+  src: images/headers/pyopensci-floral.png
+  alt: '2024: A Transformative Year for pyOpenSci'
+---
+
+## Introduction
+
+In 2024, pyOpenSci’s vibrant community led efforts to make open source science more accessible, inclusive, and equitable for all. We empowered the broader community to create, contribute to, and discover better software through beginner-friendly [training events](https://www.pyopensci.org/events/), [collaborative tutorials](https://www.pyopensci.org/learn.html#start-learning-beginner-friendly-python-packaging-tutorials), and [software peer review](https://www.pyopensci.org/about-peer-review/index.html).
+
+{{< figure src="images/pyopensci-general/pyopensci-by-the-numbers-2024.png" alt="Infographic summarizing pyOpenSci's achievements in 2024 with the title 'pyOpenSci 2024: A year of community & growth.' The 'Training & Sprints' section shows 7 events and 180 attendees. The 'Peer Review' section highlights 39 accepted packages and approximately 100 editors and reviewers. The 'Community' section emphasizes 1,436 issues and pull requests submitted, 278 contributors, and 23 new co-developed lessons." >}}
+
+Looking back, I’m inspired and humbled by what we’ve achieved together:
+
+- <i class="fa-solid fa-users"></i> We co-created a [Python package template](https://github.com/pyOpenSci/pyos-package-template) aligned with our [beginner-friendly Python packaging tutorials](https://www.pyopensci.org/python-package-guide/tutorials/intro.html) that we co-developed.
+- <i class="fa-solid fa-graduation-cap"></i> We launched a new **Training Initiative** to empower open source newcomers and [explore what sustainability means](https://www.pyopensci.org/blog/pyopensci-funding-sustainability.html) for pyOpenSci.
+- <i class="fa-solid fa-magnifying-glass"></i> We expanded our [**Software Peer Review Program**](https://www.pyopensci.org/about-peer-review/index.html), increasing its global impact.
+- <i class="fa-solid fa-rocket"></i> And our contributor community grew
+
+
+As I reflect on an incredible year, I want to take a moment to celebrate these milestones and set the stage for an ambitious 2025. Here’s a look back at what we accomplished together in 2024 and where we're heading next.
+
+<!--
+https://github.com/pyOpenSci/software-submission/issues?q=is%3Aissue+is%3Aopen+created%3A%3E%3D2024-01-01+
+55 new software submissions for our peer review process supported by a strong editorial team and reviewers
+
+674 community issues and prs
+762 staff
+-->
+
+## <i class="fa-solid fa-users" style="color: #81c0aa;"></i> Co-creation of beginner-friendly content: Python packaging made easy(ier)
+
+A defining strength of the pyOpenSci community is its commitment to co-creating accessible technical lessons for Pythonistas at all skill levels. These lessons, in turn, support our beginner-friendly tutorials and training events (more below). In 2024, this commitment shone through in creating our tutorial, [**"How to Create a Python Package"**](https://www.pyopensci.org/python-package-guide/tutorials/intro.html). This tutorial provides an opinionated way to create a Python package--a key step in making Python packaging more approachable and accessible for all.
+
+Our packaging tutorial is the product of a vibrant collaboration between developers, scientists, and beginners. Packaging tool maintainers and packaging experts worked alongside those newer to packaging to co-develop, review, and refine content that is accurate, thorough, and welcoming to newcomers.
+
+
+{{< figure src="images/python-packaging/packaging-101-outline.png" alt="Diagram showing the lessons in our packaging tutorial. There are 6 total - what is a Python package, make code pip installable, publish your package to PyPI, add a README and LICENSE file, add metadata for PyPI and finally publish to conda forge.' style='width: 70%; max-width: 100%;" >}}
+
+### Collaborative learning in action: building together, learning together
+
+Our co-development process brought contributors of all experience levels together to create a resource that:
+
+- **Blend expertise:** Developers and scientists shared insights, while beginners shaped the content with fresh perspectives.
+- **Demystifies packaging:** Clear, precise explanations, reviewed by experts and tested by newcomers, break down complex steps for new users.
+- **Describes core concepts visually:** Custom graphics and step-by-step guides make technical concepts easier for visual learners to grasp.
+
+We're building both knowledge and community by publishing these lessons as free, open-access resources. This collaborative effort exemplifies the unique power of pyOpenSci to bridge expertise, foster learning, and strengthen the open source ecosystem.
+
+### Simplifying Python packaging: Our easy-to-use Python package template
+
+To further simplify the process of creating a new Python package, the community also came together to develop an easy-to-use [Python packaging template](https://github.com/pyOpenSci/pyos-package-template). The template allows you to create a skeleton Python package that follows our beginner-friendly Python package tutorial with just a few commands.
+
+Many learners used this template successfully during our Fall Festival (more below!) and we look forward to refining it further in the upcoming months.
+
+Give it a test-drive and let us know what you think!
+
+
+##  <i class="fa-solid fa-graduation-cap" style="color: #81c0aa;"></i> pyOpenSci's training new training initiative: empowering our global community
+
+In 2024, we launched the pyOpenSci [training initiative](https://www.pyopensci.org/blog/pyos-education-announcement.html) to lower barriers and make scientific software education more accessible to all.
+
+To further our commitment to equity, we awarded 25+ scholarships to support participation from a diverse group of students, researchers, and contributors.
+
+### Event Highlights: Fall Festival
+
+Our first-ever [Fall Festival](#) featured inspiring keynote speakers like Rowan Cockett, who introduced participants to [MyST Markdown](https://mystmd.org/), Melissa Mendoça who discussed her personal pathway into open source from academia, and Eric Ma, who overviewed the importance of [reproducibility in science](/blog/human-dimension-clean-documented-data-science-code.html).
+
+On the event's last day, George Stagg, developer of Quarto Live, and James Balamuta kicked off the day with an overview of how Quarto Live makes interactive publishing of dynamic scientific outputs easier, connecting scientific workflows with shared outputs.
+
+{{< figure src="images/events/fall-festival-blog-keynote-speakers.png" alt="Graphic showing the keynote speakers for the pyOpenSci Fall Festival. The title reads: pyOpenSci Fall Festival Keynote Speakers. The featured speakers are Melissa Mendoça, James Balamuta, Eric Ma, George Stagg, and Rowan Cockett, each displayed in a circular frame against a purple background with connecting nodes as a design element." >}}
+
+The dynamic spatial chat platform fostered real-time collaboration and made learning interactive, personalized, and fun!
+
+
+> I love the engagement…how people were attended to individually despite being in a group setting. I enjoyed that learning could happen in a personal and group setting.
+>
+> — Workshop Participant
+
+
+#### Volunteer contributors who made it possible
+
+The Fall Festival wouldn’t have been possible without the dedication of our incredible volunteers, who handled everything from workshop support to tech troubleshooting. Their efforts ensured a welcoming, smooth experience for participants.
+
+{{< figure src="images/events/fall-festival-thank-you.png" alt="Graphic showing a 'Thank You' message to pyOpenSci Fall Festival community supporters. The text reads 'Thank You, pyOpenSci Community Supporters!' with the Fall Festival logo. Circular photos of community members include Rich Iannone, Steven Sylvester, Jonny Saunders, Tracy Teal, Carol Willing, Felipe Moreno, Tetsuo Koyama, Isabel Zimmerman, and Jeremiah Paige, displayed against a purple background with connecting nodes as a design element. The pyOpenSci URL (pyopensci.org) is displayed in the lower left." >}}
+
+
+#### Open education lessons from the Fall Festival
+Participants didn’t just learn—they contributed! Thanks to the collaborative energy, the event produced several lessons that are now freely available to the community:
+
+- [Writing Clean Code](https://www.pyopensci.org/lessons/write-better-code/clean-modular-code/)
+- [Optimizing Code for Better Workflows](https://www.pyopensci.org/lessons/write-better-code/optimize-code/)
+- [Running Code Efficiently](https://www.pyopensci.org/lessons/package-share-code/run-code/)
+- [Publishing and Sharing Code](https://www.pyopensci.org/lessons/package-share-code/publish-share-code/)
+
+These lessons reinforce key technical skills and showcase the power of community-driven learning and co-creation.
+
+### Event highlight: Intro to Python packaging workshops
+
+As a part of our training initiative, we also ran two beginner-friendly packaging workshops where dozens of participants successfully created their first Python packages by following our [beginner-friendly packaging tutorials](https://www.pyopensci.org/python-package-guide/tutorials/intro.html).
+
+What did you enjoy most about the workshop?
+
+
+> The content and the crew! The team was so kind, patient, and approachable. I appreciate the amount of support and reassurance given during this tutorial. The content of the tutorial was also spot on. Everything we covered felt relevant and useful, and gave me the confidence to feel capable of creating my own packages.
+>
+> — Workshop Participant
+
+
+The success of our training materials underscores the demand for inclusive, high-quality open science resources; they also demonstrate the power of community collaboration.
+
+## <i class="fa-solid fa-magnifying-glass-chart" style="color: #81c0aa;"></i>  Expanding our software peer review program in 2024
+
+The pyOpenSci software peer review program empowers scientists to build and improve the tools they rely on to process and analyze data. In 2024, we expanded our ecosystem of reviewed scientific Python packages to **39**, thanks to the dedication of our editorial and review teams.
+
+We also tried out a new editor in chief rotation system to avoid too much time burden on any specific editor. Below are our fearless EiC's for 2024.
+
+{{< figure src="images/peer-review/pyos-eic-rotation-2024.png" alt="Graphic titled 'Editor in Chief 2024 Software Peer Review,' highlighting the four Editors-in-Chief for 2024 with photos and descriptions. • Szymon Molinski (Fall 2024): Image of Szymon holding a dog by the ocean. Passion: Open source development, breakdancing, and hiking with his pug. • Chiara Marmo (Summer 2024): Illustrated portrait of Chiara. Fun fact: She enjoys reading theater pieces, playing all roles herself, and takes pride in accomplishing unexpected things. • Alex Batisse (Spring 2024): Black-and-white photo of Alex. Passion: Understanding and visualizing information, from stats to dataviz, and making it intelligible for others. • Isabel Zimmerman (Winter 2024): Photo of Isabel smiling outdoors in a wide-brimmed hat. Passion: Machine learning operations and improving the processes that support creating, sharing, and maintaining models." >}}
+
+Our editorial team grew to **18 members**, with a rotating Editor-in-Chief position, and was supported by **81 volunteer reviewers** who contributed their time to ensure that [every reviewed package in our ecosystem](https://www.pyopensci.org/python-packages.html) meets the highest standards for quality and usability.
+
+In 2024, we received over **28 new submissions**.
+
+### Peer review success in 2024
+
+- **Publishing impact through partnerships:**
+  **21 packages** of our accepted packages were published in [JOSS through our peer review partnership](https://www.pyopensci.org/software-peer-review/partners/joss.html).
+
+- **Strengthening ecosystems through domain-specific affiliation: Astropy:**
+  Our domain-specific community partnership program accepted three packages for [Astropy affiliation](https://www.pyopensci.org/software-peer-review/partners/astropy.html). Our partnership with Astropy and JOSS demonstrates how communities with some overlapping goals can truly work together effectively.
+
+{{< figure src="images/peer-review/pyos-partnerships-peer-review.png" alt="Graphic illustrating the pyOpenSci partnerships and review flow: 1. pyOpenSci Accepted: The process starts with a package being accepted by pyOpenSci, represented by the pyOpenSci logo and a checkmark. 2. JOSS Published: Accepted packages can be published in the Journal of Open Source Software (JOSS), indicated by the JOSS logo and a checkmark. 3. Community Affiliated: Packages can also become affiliated with community-specific organizations, represented by a box labeled 'Community Affiliated' with a checkmark. The flowchart shows arrows connecting these stages, visually demonstrating the possible outcomes after pyOpenSci acceptance." >}}
+
+### Navigating ethical challenges in generative AI
+
+In 2024, we began to address the emerging challenge of reviewing packages that rely on proprietary generative AI models. We discussed important ethical questions about transparency vs. innovation in scientific software. Should we review packages that depend upon proprietary (closed box) models that are rapidly evolving?
+
+More work is needed, and we are committed to handling these complexities as we always do--collaboratively and with great care.
+
+## <i class="fa-solid fa-rocket" style="color: #81c0aa;"></i> A thriving, diverse contributor community: how contributions to pyOpenSci have skyrocketed
+
+In 2024, pyOpenSci welcomed 278 contributors from diverse backgrounds, many making their first-ever open source contributions. By prioritizing mentorship, accessibility, and community-led learning, we helped first-time contributors gain the confidence and skills to shape the future of open source science.
+
+This was also the first year where volunteer contributions outnumbered staff contributions—a testament to the power of community.
+
+Wow!
+
+{{< figure src="images/pyopensci-general/pyopensci-github-prs-issues.png" alt="Bar chart titled 'Staff vs. Volunteer Contributor by Quarter,' showing the count of contributions by quarter from Q4 2018 to Q1 2025. The chart uses stacked bars, with green representing volunteer contributions and purple representing staff contributions. The chart shows a significant growth in contributions starting around 2023, with volunteer contributions surpassing staff contributions in recent quarters." caption="Plot that shows an increase in contributions to pyOpenSci open education content." >}}
+
+### Empowering first-time contributors
+
+A key driver of contributor and community growth was our [**beginner-friendly sprints**](https://www.pyopensci.org/blog/pyopensci-pyconus-2024-sprints.html). Sprint events exemplified the power of community support combined with mentorship & just a bit of training (mostly around git and GitHub). These sprints welcomed over **50 participants** and resulted in **86 issues and pull requests**—many from first-time contributors.
+
+- **PyCon US, SciPy, and PyCascades Sprints:** Hosted across three major conferences, these events focused on hands-on mentorship, guiding participants through impactful contributions.
+
+
+> Amazing! Leah was so helpful as it was my first time doing anything like that. I had used GitHub for personal projects but never with other people so she was so good at teaching.
+>
+> — Workshop Participant
+
+
+Our sprints strengthened our contributor community and sparked new initiatives, like translating our packaging guide into Spanish and Japanese.
+
+## Funding and sustainability
+
+In 2024, we reached an important milestone in pyOpenSci’s journey. Our initial funding from the Sloan Foundation, which gave us our start as a fledgling project, ended in December. The Sloan Open Source Program’s generous support took us a long way—it helped me grow pyOpenSci from a part-time passion project into a thriving community dedicated to lowering barriers to open source scientific software.
+
+We are deeply grateful for Sloan’s belief in our vision and commitment to open science. Last fall, we also received support from the Chan Zuckerberg Initiative (CZI), which will empower us as we move forward. This combined funding has enabled us to launch our training initiative, expand our peer review program, and co-develop beginner-friendly lessons and tutorials.
+
+## Building the future: new initiatives and funding efforts
+
+As we look to the future, our current focus includes:
+- **Exploring funding models for pyOpenSci**
+- **Growing our peer review partners and program**
+- **Connecting with University OSPOS (Open Source Program Offices)**
+- **A focus on empowering the community to contribute to open source**
+- **Educational Videos that support our online content**
+
+## Strong together: Why inclusion in open science matters now more than ever
+
+At a time when access, equity, and sustainability in open science face challenges, we believe in building a space where everyone—regardless of background—can contribute, learn, and thrive. Diversity strengthens open source, and we are committed to ensuring that our community remains welcoming, supportive, and accessible.
+
+## Sustaining our impact
+
+As we head into 2025, sustainability and our commitment to diversity, equity, inclusion and accessibility remains a top priority. We’re committed to growing pyOpenSci in ways that support our contributors, empower learners, and strengthen open source science. We’re actively seeking new partnerships, welcoming new contributors and funding opportunities to ensure our work continues to thrive.
+
+To our funders, contributors, and community members—thank you. Your support makes our work possible and helps us build a future where scientific software is open, accessible, and collaborative.
+
+As we reflect on where we’ve been and where we’re going, it’s important to acknowledge the teams that continue to guide our vision and growth.
+Our leadership teams—including the [Executive Council](https://www.pyopensci.org/our-community/index.html#executive-council-leadership--staff), [Advisory Council](https://www.pyopensci.org/our-community/index.html#pyopensci-advisory-council) and
+[Peer Review Editorial Board](https://www.pyopensci.org/about-peer-review/index.html#meet-our-editorial-board) have been instrumental in carving the path forward for pyOpenSci.
+
+We look forward to building the future of open science, one contribution at a time—and we invite you to join us on this journey.
diff --git a/content/blog/2025-03-05-pyOpenSci-first-open-science-festival.md b/content/blog/2025-03-05-pyOpenSci-first-open-science-festival.md
new file mode 100644
index 00000000..82343707
--- /dev/null
+++ b/content/blog/2025-03-05-pyOpenSci-first-open-science-festival.md
@@ -0,0 +1,192 @@
+---
+title: 'Building Momentum for the Future: Reflections on Our First Open Science Festival
+  Week'
+date: '2025-03-05'
+type: blog
+excerpt: pyOpenSci ran 6 workshops in 2024, 4 of which happened during our Fall Festival!
+  Learn more about how the workshops went and watch the keynote talks that introduced
+  Quarto Live, MystMarkdown and stories about reproducibility, open science and open
+  source in this blog.
+author: Leah Wasser
+blog_topic: community
+toc: true
+comments: true
+url: "/blog/pyopensci-reflections-fall-festival-2024.html"
+lastmod: '2025-03-05'
+image:
+  src: images/headers/pyopensci-floral.png
+  alt: 'Building Momentum for the Future: Reflections on Our First Open Science Festival
+    Week'
+---
+
+## Our inaugural fall festival was a great success!
+
+Three years ago, I envisioned an online event where our community could come together to celebrate open source and open science, share knowledge, and learn new skills. Last month, that vision became reality with pyOpenSci’s first-ever [Fall Festival, held from October 28 to November 1](/events/pyopensci-2024-fall-festival.html). The event brought together **64 participants** from over **15 countries**—a global mix of researchers, developers, educators, and Python enthusiasts.
+
+
+<figure class="align-center">
+    <a href="/images/events/fall-festival-2024-stats.png">
+    <img src="/images/events/fall-festival-2024-stats.png" style="max-width:90%" alt="">
+    </a>
+The week was packed with inspiring keynotes, hands-on workshops, and informal office hours, where participants connected and reflected on their learning.
+
+
+What did you enjoy most about the fall festival:
+> Getting to know about pyOpenSci as an organization and resource. Also, [being provided with] practical, professional tools that I can use right away.
+{: .highlight-quote .purple }
+
+
+## Acknowledging our amazing pyOpenSci team
+
+Events like the Fall Festival don’t happen without an incredible team working behind the scenes to support every step of the process.
+I want to extend our heartfelt gratitude to all the instructors, helpers, and keynote speakers who contributed their time and expertise to make this event truly special. Your dedication, energy, and enthusiasm ensured an engaging and impactful experience for everyone involved!
+
+{{< figure src="images/events/fall-festival-thank-you.png" alt="Thank You graphic for pyOpenSci Fall Festival, featuring photos of community supporters. The circular portraits include Rich Iannone, Steven Sylvester, Jonny Saunders, Tracy Teal, Carol Willing, Felipe Moreno, Tetsuo Koyama, Isabel Zimmerman, and Jeremiah Paige, all placed against a purple background with the text: Thank You - Fall Festival - pyOpenSci Community Supporters" >}}
+
+
+A special shout-out to Carol Willing, Jeremiah Paige, and Jonny Saunders, who supported multiple workshops and co-developed and reviewed many of the lessons now published online. We’re so lucky to have such an incredible community. 🫶
+
+## What made this event special
+
+The vibe made this event special. The energy of participants who wanted to learn together was supported by the vibrant and knowledgeable pyOpenSci community. While many mentioned me directly, the vibe was more than just me. Our community came together to help scientists learn hard technical skills--together and without judgment.
+
+> I love the engagement…how people were attended to individually despite being in a group setting. I enjoyed that learning could happen in a personal and group setting.
+{: .highlight-quote }
+>
+
+We met learners where they were at!
+
+> The enthusiasm of Leah and her friends, Spatial chat and all new Python things I didn't used before like Packaging, Great Tables, Quarto, Clean Code and Programming in [GitHub] CodeSpaces
+{: .highlight-quote }
+
+Using the interactive platform SpatialChat rather than a traditional online platform like Zoom helped to create that vibe. More on that below.
+
+## Keynote talks
+
+We kicked the event off on Monday, October 28, with a morning of KeyNote talks headlined by **Eric Ma, Melissa Mendonça, and Rowan Cockett**. The Monday talks aligned perfectly with the training events held Tuesday through Friday. The talks set the stage for a truly engaging week of learning together.
+
+<figure class="align-center">
+    <picture>
+    <source srcset="/images/events/fall-festival-blog-keynote-speakers.webp" type="image/webp">
+    <img src="/images/events/fall-festival-blog-keynote-speakers.png" alt="">
+    </picture>
+### Eric Ma: The human side of clean code
+
+[Eric's talk](/blog/human-dimension-clean-documented-data-science-code.html) highlighted how simple practices like clear documentation, readable code, and user-friendly installation can amplify the impact of data science projects.
+
+A standout moment? The "Roast Your Repo" exercise! Eric invited attendees to critique a repository from his thesis, showcasing the power of small improvements—like adding a fleshed-out README or modularizing code—to make research reusable and collaborative. It was a fun, hands-on way to explore how the human touch transforms code quality. And let's be honest, we all likely have one of those code bases or repos from our early degrees! I sure do (and it's not even on GitHub!).
+
+### Melissa Mendonça: From academia to open source
+
+Melissa shared her journey from academia to open source software development, reflecting on the courage it takes to step into the unknown. She celebrated the scientific Python ecosystem, emphasizing how libraries like NumPy and SciPy enable countless domain-specific projects.
+
+Melissa also highlighted the challenges of volunteer-driven communities, stressing the need for clear governance and transparent user engagement. Her focus on open science principles—transparency, reproducibility, and accessibility—was inspiring and reinforced the importance of collaborative, inclusive practices.
+
+### Rowan Cockett: Rethinking scientific publishing
+
+Rowan invited us to imagine a future where scientific publications are as dynamic as the research they describe. He introduced [Myst Markdown](https://mystmd.org/) tools that blend code, data, and narrative and discussed his company, [CurveNote](https://curvenote.com/), which aims to revolutionize scientific publishing.
+
+His vision of collaborative, interactive, and automated publishing draws from open source principles and challenges the static nature of traditional papers. By rethinking how we share research, Rowan reminded us that we already have the tools to make science more immediately accessible and impactful.
+
+### Workshops and Quarto Live
+
+We also invited George Stagg (Posit), developer of Quarto Live and James Balamuta to talk about how Quarto Live is empowering education. Quarto Live makes it easy for you to create interactive data science environments for learning in the browser.
+
+* Yes, it runs on GitHub pages - no servers needed.
+* Yes, students can write Python on their phones.
+
+Both talks are below.
+
+#### George Stagg
+
+#### James Balamuta
+
+## Let the (open science & open source) learning begin!
+
+<figure class="align-center">
+    <a href="/images/events/people-table-working.svg">
+    <img src="/images/events/people-table-working.svg" alt="An illustration of a diverse group of people sitting around a round table in a collaborative meeting setting. Some are using laptops, others are holding notebooks or phones, with modern lighting and decorative plants in the background, creating a warm and productive atmosphere.">
+    </a>
+The main "course" of the event was 4 days of active learning. Here, participants engaged in interactive workshops designed to build skills and confidence in writing, sharing, and publishing scientific code. Using SpatialChat, we created a dynamic and collaborative environment that fostered real-time learning and group discussions—something you just can’t replicate in traditional video call platforms like Zoom.
+
+Our curriculum followed a clear narrative:
+
+**Write better code → Package it → Share it → Tell an interactive data story.**
+
+> [I enjoyed....] Leah's teaching style, the platform, and the tutorials. I felt very ease learning together with the pyOpenSci community.
+{: .highlight-quote .magenta }
+
+Each day introduced new tools and practices to help participants transform their workflows and make their science more accessible, reusable, and impactful. Here’s how we approached it:
+
+### Day 1: Write Better, Cleaner Scientific Code
+
+We started by diving into [writing better, cleaner code](https://www.pyopensci.org/lessons/write-better-code/clean-modular-code/). Participants explored how to make their code:
+- [DRY (Don’t Repeat Yourself)](https://www.pyopensci.org/lessons/write-better-code/clean-modular-code/python-dry-modular-code.html) and modular,
+- [Expressive](https://www.pyopensci.org/lessons/write-better-code/clean-modular-code/python-write-expressive-code.html) and easy to understand,
+- [Consistent with Python style guidelines](https://www.pyopensci.org/lessons/write-better-code/clean-modular-code/python-pep-8.html) like PEP 8.
+
+We introduced strategies to improve robustness, such as creating [functions](https://www.pyopensci.org/lessons/write-better-code/optimize-code/) and using [tests and checks](https://www.pyopensci.org/lessons/write-better-code/optimize-code/python-function-checks.html) to validate outputs.
+
+### Day 2: Create Your First Python Package
+
+On Day 2, participants learned how to turn their code into reusable, installable Python packages. I've taught Python packaging with Hatch several times over the past year, and everyone consistently loves having an all-in-one tool! They also pick it up quickly, making the tool accessible and usable--a win-win! This was one person's response to their favorite day:
+
+> ...I thought Hatch was really useful and I liked the fact that it can do a couple of things as one tool.
+{: .highlight-quote }
+
+
+The packaging day covered:
+- [An overview of Python packaging for beginners](https://www.pyopensci.org/python-package-guide/tutorials/intro.html#what-is-a-python-package),
+- Making code [installable in Python environments](https://www.pyopensci.org/python-package-guide/tutorials/create-python-package.html) with tools like [Hatch](https://www.pyopensci.org/python-package-guide/tutorials/get-to-know-hatch.html),
+- Adding package metadata using a [pyproject.toml file](https://www.pyopensci.org/python-package-guide/tutorials/pyproject-toml.html),
+- Including a [license](https://www.pyopensci.org/python-package-guide/tutorials/add-license-coc.html) to define how others can use and share your Python package.
+
+### Day 4: share your Python code (with everyone!)
+
+On Day 4, we empowered participants to share their work more broadly. Many learners enjoyed this day which was cool for me because it was entirely new content I had never taught before but thought was so important to any scientist building software and writing code. Below, we asked them what day their favorite was. The theme of this response was common in the feedback:
+
+
+>  [I enjoyed] making package installable via PyPI by using hatch (one often writes code, but never gets to this stage)
+{: .highlight-quote .magenta }
+
+ Key share your code topics included:
+- [Why sharing code matters](https://www.pyopensci.org/lessons/package-share-code/publish-share-code/share-code.html),
+- [Adding a DOI to code using Zenodo](https://www.pyopensci.org/lessons/package-share-code/publish-share-code/cite-code.html),
+- Publishing through [JOSS](https://joss.theoj.org/) or the [pyOpenSci peer review process](https://www.pyopensci.org/about-peer-review/index.html),
+- Publishing code on [PyPI](https://www.pyopensci.org/lessons/package-share-code/publish-share-code/publish-code.html#pypi) using Hatch.
+- NOTE: we also have a [publish to conda-forge lesson](https://www.pyopensci.org/python-package-guide/package-structure-code/publish-python-package-pypi-conda.html).
+
+<figure class="align-center">
+    <a href="/images/events/people-table-working-2.svg">
+    <img src="/images/events/people-table-working-2.svg" alt="An illustration of a diverse team gathered around a large, round table in a collaborative work meeting. Several people are using laptops, while others are holding notebooks or tablets. A small plant decorates the center of the table, and modern pendant lights hang overhead, contributing to a comfortable and productive workspace.">
+    </a>
+### Day 5: Interactive data storytelling with Quarto & GreatTables
+
+We wrapped up with an introduction to [Quarto](https://quarto.org/), a powerful tool for creating dynamic, interactive scientific narratives. Participants explored how to integrate code, data, and findings into a cohesive story—transforming static publications into living, engaging documents.
+
+We also showcased [Quarto Live](https://quarto.org/docs/guide/), which lets users dynamically interact with code in the browser. For educators, this opens exciting opportunities to create lessons where students can learn directly in a live coding environment. How cool is that?
+
+Fun fact: GreatTables has been [accepted by pyOpenSci](https://github.com/pyOpenSci/software-submission/issues/202) with the plan to be fast-tracked through the Journal of Open Source Software (JOSS) after the pyOpenSci review through [our JOSS partnership](https://www.pyopensci.org/software-peer-review/partners/joss.html).
+
+
+## Reflections on the 2024 pyOpenSci Fall Festival
+
+The 2024 Fall Festival was an incredible learning experience for pyOpenSci! One of the standout successes was our last-minute switch to using Spatial Chat as our virtual platform. Participants loved how easy and intuitive it was to use, and it quickly became a seamless way to foster interaction and collaboration.
+
+> I liked the use of software like spatialchat, where you could break out into groups to work on things. This makes everything a lot more casual and fosters networking.
+{: .highlight-quote }
+
+We were also thrilled to offer 16 scholarships for this event, making the festival accessible to diverse attendees.
+We’re excited to continue improving our events to maximize engagement and accessibility for all community members. We look forward to building on this success for future festivals!
+
+## <i class="fa-solid fa-rocket"></i> What's next for pyOpenSci
+
+Most of the resources used to teach are published on our [pyOpenSci lessons website](https://www.pyopensci.org/lessons). We’re actively working on updates to incorporate additional content still housed in Google Docs, ensuring it’s accessible to all.
+
+Looking ahead, we’re excited to run more events like this to support pyOpenSci’s broader mission of supporting the open source software scientists need to make their work open. We are planning to:
+
+* Develop a new set of lessons that support using GitHub collaboratively and empower contributors to make their first open source contributions.
+* Run online beginner-friendly sprints that further engage the community in making contributors to open source, no matter how big or small, we want to ease pain points!
+* Attend and run events at PyCon 2025 and SciPy 2025, holding events and connecting with you!
+
+Check our blog and events page for upcoming events and opportunities to engage with the vibrant pyOpenSci community. <i class="fa-solid fa-hand-sparkles"></i>
diff --git a/content/blog/2025-03-13-python-packaging-security-pypi.md b/content/blog/2025-03-13-python-packaging-security-pypi.md
new file mode 100644
index 00000000..cca2fcf2
--- /dev/null
+++ b/content/blog/2025-03-13-python-packaging-security-pypi.md
@@ -0,0 +1,296 @@
+---
+title: How to Secure Your Python Packages When Publishing to PyPI
+date: '2025-03-13'
+type: blog
+excerpt: Learn how to secure your Python package PyPI publishing workflows and protect
+  your package from attacks. This post covers actionable steps, using PyPI Trusted
+  Publisher, and sanitizing workflows, to ensure your projects stay safe.
+author: Leah Wasser
+blog_topic: learn
+toc: true
+comments: true
+url: "/blog/python-packaging-security-publish-pypi.html"
+lastmod: '2025-03-13'
+image:
+  src: images/headers/pyopensci-floral.png
+  alt: How to Secure Your Python Packages When Publishing to PyPI
+---
+
+## Is your PyPI publication workflow secure?
+
+We can learn a lot from the Python package breach [involving Ultralytics](https://blog.pypi.org/posts/2024-12-11-ultralytics-attack-analysis/). This breach highlighted the importance of making our PyPI publishing workflows for Python packages more secure.
+
+In this breach, hackers exploited a GitHub Actions workflow to inject malicious code into a Python package. This package was then published to PyPI. The outcome: users who downloaded the package unknowingly allowed their machines to be hijacked for Bitcoin mining.
+
+
+> Hackers tricked a Python package into running bad code, using other people’s computers to mine Bitcoin without permission. Yikes!
+
+
+While unsettling, there’s a silver lining: the PyPI security team had already addressed most of the issues that caused this breach.
+
+
+> Because the Ultralytics project was using Trusted Publishing and the PyPA’s publishing GitHub Action: PyPI staff, volunteers, and security researchers were able to dig into how maliciously injected software was able to make its way into the package.
+>
+> — Seth Larson, PSF Security Expert
+
+
+This means that the important thing for us, as maintainers, is that we all should know how to lock down our publishing workflows.
+Here, I'll cover the lessons learned that you can apply TODAY to your Python packaging workflows!
+
+*Special thanks to [Seth Larson](https://github.com/sethmlarson), [Hugo van Kemenade](https://github.com/hugovk), [Sviatoslav Sydorenko](https://github.com/webknjaz), [William Woodruff](https://github.com/woodruffw) and [Carol Willing](https://github.com/willingc) for reviewing and significantly improving blog post!!*
+
+<div class="notice" markdown="1">
+## TL;DR Takeaways
+
+The fall 2024 Ultralytics breach was a wake-up call for all maintainers: secure your workflows to protect your users and the Python ecosystem. The most important steps that you can take are actually the simplest:
+
+Below are **3 things that you can do right now** to secure your PyPI Python packaging workflow:
+
+### Secure GitHub--Human and GitHub--PyPI connections
+
+1. 🔒 If you have a GitHub Action that publishes to PyPI, make sure that the **publish section of your action uses a controlled GitHub environment**. Name that environment `pypi` and set environment permissions in GitHub that allow specific trusted maintainers to authorize the environment to run. I'll show you how to do this below.
+1. 🤝 Create a **Trusted Publisher link between your package's (GitHub/GitLab) repository and PyPI**. You can call this trusted connection within the locked-down GitHub environment (named `pypi`) that you created above.
+1. 🍒 Add [`zizmor`](https://woodruffw.github.io/zizmor/) to your build to check GitHub Actions for vulnerabilities. You can run zizmor on your workflow files locally, or you can set it up as a pre-commit hook which is probably a better bet.
+
+Together, these three steps protect both sides of your PyPI publication process--the trigger on GitHub and the connection between GitHub and PyPI. 🚀🚀🚀
+
+Don’t wait--start securing your Python publishing workflows today. 🔒
+
+</div>
+
+
+## A call to (GitHub) actions ...
+
+The Ultralytics breach highlights the need for us all to follow and understand secure PyPI publishing practices and carefully monitor workflows. Below are actionable steps you can take to enhance security when publishing Python packages to PyPI using GitHub Actions.
+
+<i class="fa-solid fa-circle-info"></i> [PyPA provides a great overview of using actions to publish your Python package.](https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/)
+{: .notice }
+
+## <i class="fa-solid fa-box"></i> 1. Create a dedicated GitHub environment for publishing actions
+
+First, make sure that your PyPI publish GitHub Action uses an isolated GitHub environment. Isolated environments ensure your publishing process remains secure even if other parts of your CI pipeline are compromised. This is because you can lock an environment down by ensuring that only specific users can authorize this environment to run.
+
+
+A GitHub Action is a CI/CD (Continuous Integration/Continuous Deployment) tool that allows you to automate tests. [Click here to read more about what CI/CI is.](https://www.pyopensci.org/python-package-guide/maintain-automate/ci.html)
+{: .notice .notice--success }
+
+If you look at the workflow example below, notice that we have an [environment called `pypi`](https://github.com/pyOpenSci/pyosMeta/blob/2a09fba/.github/workflows/publish-pypi.yml#L57) that is used for trusted publishing. The `pypi` environment creates a direct link between this action and PyPI Trusted Published (discussed below).
+
+```yaml
+  publish:
+    name: >-
+      Publish Python 🐍 distribution 📦 to PyPI
+    if: github.repository_owner == 'pyopensci'
+    needs:
+      - build
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/p/pyosmeta
+```
+
+To lock down a GitHub environment:
+
+* First, go to the <kbd>Settings</kbd> in your repository where the workflow is run
+* Within settings, select **environments** from the left-hand sidebar
+* Add a new environment. Use <kbd>pypi</kbd> as your environment name; this is what PyPA (the Python Packaging Authority) recommends.
+* Ensure <kbd>Required reviewers</kbd> is enabled. This setting allows you to designate specific individuals who can approve and manually run the workflow on GitHub. Any reviewers you add must have the appropriate permissions to authorize the workflow by clicking a button. This adds a human verification step to the process.
+* Once the <kbd>Required reviewers</kbd> button is checked, add maintainers who you want to be able to enable the action to run.
+
+*Optionally, you can click <kbd>prevent self-review</kbd>, preventing someone from triggering a release or a build and then running it!*
+
+{{< figure src="images/python-packaging/create-github-environment.gif" alt="Animated gif file that shows the GitHub interface where you can click on settings and go to the environment setting to create or edit a GitHub environment" caption="To create a new environment to use in a GitHub Action, 1) go to your repo's settings; 2) click <kbd>environment</kbd>; 3) add a new environment. In this screenshot, we already have a <kbd>pypi</kbd> environment created. Note that you can name your environment whatever you want, however, PyPI suggests that you use the name <kbd>pypi</kbd> for a Trusted Publisher workflow." >}}
+
+
+{{< figure src="images/python-packaging/github-action-environment-pypi.png" alt="Screenshot of the GitHub settings interface showing the 'Environments' section with configuration options for 'pypi.' The 'Deployment protection rules' section is visible, with 'Required reviewers' enabled and two reviewers listed: 'lwasser' and 'willingc.' Other options such as 'Prevent self-review' and 'Wait timer' are present but not enabled." caption="GitHub environment settings for 'pypi,' displaying deployment protection rules with required reviewers configured for workflow approvals." >}}
+
+
+## <i class="fa-solid fa-key"></i> 2. Use Trusted Publisher for PyPI
+
+Now that you have a GitHub environment setup, you can set up Trusted Publisher in your PyPI account.
+
+A Trusted Publisher setup creates a secure link between PyPI and your repository.
+- PyPI is allowed to authenticate your [package distribution files (sdist and wheel archives)](https://www.pyopensci.org/python-package-guide/package-structure-code/python-package-distribution-files-sdist-wheel.html#how-to-create-the-distribution-format-that-pypi-and-pip-expects) uploads directly, so no additional configuration is required.
+- Trusted Publisher restricts publishing to a specific GitHub Actions workflows and environments defined in your repository.
+
+Using a Trusted Publisher combined with a locked-down environment eliminates the need to store sensitive tokens as GitHub secrets. It also removes the need to refresh and update tokens periodically to avoid token leaks or theft issues.
+
+{{< figure src="images/python-packaging/trusted-publisher-pypi-github.png" alt="A workflow diagram showing GitHub Actions building distribution files (sdist and wheel), publishing them securely to PyPI, represented as a warehouse. The diagram includes a lock icon emphasizing security, with the pyOpenSci logo in the top-left corner." caption="Example of the PyPI Trusted Publisher form, used to securely link a GitHub repository with PyPI for publishing Python packages. Trusted Publisher reduces the risk of token theft and improves overall security." >}}
+
+If you only [publish locally to PyPI using the command line](https://www.pyopensci.org/python-package-guide/tutorials/publish-pypi.html), you must use a PyPI token. However, if you’re using GitHub Actions to automate your publishing process, setting up **Trusted Publisher** is a secure and easier-to-manage option.
+{: .notice }
+
+### How to get started
+
+[PyPI provides a great guide to getting started with Trusted Publisher](https://docs.pypi.org/trusted-publishers/adding-a-publisher/).
+
+
+The steps for setting up Trusted Publisher are:
+1. Login to your PyPI account
+2. Click on your profile to take you to **Your projects**.
+3. Click on **publishing** on the left-hand side of the site. (it's below account settings).
+4. At the top of the page is a Manage Publishers section. At the bottom, you will see **Add a new pending publisher**
+5. Fill out a form that looks like the one below in the add a new pending publisher section. Notice that you can select GitHub, GitLab, Google and ActiveState as platforms.
+6. Notice that the form asks for your project name, owner, repo name, workflow's file name, and environment (**STRONGLY recommended**).
+
+
+{{< figure src="images/python-packaging/trusted-publisher-form.png" alt="PyPI Trusted Publisher form example showing settings for linking a GitHub repository with PyPI for secure publishing.' loading='lazy" caption="Example of the PyPI Trusted Publisher form, used to securely link a GitHub repository with PyPI for publishing Python packages. Trusted Publisher reduces the risk of token theft and improves overall security." >}}
+
+For an example of a GitHub workflow that uses Trusted Publishing, check out our active pyOpenSci [PyPI publishing GitHub workflow](https://github.com/pyOpenSci/pyosMeta/blob/main/.github/workflows/publish-pypi.yml), which follows the Trusted Publisher approach.
+
+
+{{< figure src="images/python-packaging/trusted-publisher-manage.png" alt="PyPI Trusted Publisher manage settings showing what the Trusted Publisher setup looks like after you've created it in PyPI. It shows all of the items that you filled out in the form and has a remove button if you want to remove it from PyPI. ' loading='lazy" caption="Example of the PyPI Trusted Publisher setup in PyPI once you've created the Trusted PuUblisher link by filling the form out above." >}}
+
+
+**Note:** Read more here about [support for publishing to GitLab](https://docs.pypi.org/trusted-publishers/adding-a-publisher/#gitlab-cicd) using trusted publishing.
+{: .notice }
+
+## <i class="fa-solid fa-check-double"></i> 3. Add `zizmor` to your CI workflows
+
+Finally, consider adding [Zizmor](https://woodruffw.github.io/zizmor/) to your [Continuous Integration (CI)](https://www.pyopensci.org/python-package-guide/maintain-automate/ci.html#what-is-continuous-integration) and [pre-commit checks](https://www.pyopensci.org/python-package-guide/package-structure-code/code-style-linting-format.html#use-pre-commit-hooks-to-run-code-formatters-and-linters-on-commits).
+
+Zizmor is a static analysis tool designed to help identify GitHub Action security issues. Zizmor scans your workflows and highlights common vulnerabilities, ensuring your continuous integration / continuous deployment pipelines remain secure and efficient.
+
+Named as a playful nod to Dr. Zizmor’s famous “clear skin” ads, zizmor aims to give you “beautiful clean workflows.”
+
+Learn more about zizmor on the [official blog post by William Woodruff](https://blog.yossarian.net/2024/10/27/Now-you-can-have-beautiful-clean-workflows).
+{: .notice .notice--success }
+
+### How it works
+
+To use zizmor locally to check your workflows, first install it using `pip` or `pipx`:
+
+`pip install zizmor`
+
+Then, ask it to check a specific workflow file (or set of files).
+
+Below, I ran it on our pyosMeta PyPI build. Among other things, it found a template injection risk in our build that we can easily fix by adding a sanitization step discussed below!
+
+PyPI really is on top of things!
+
+```console
+$ zizmor .github/workflows/publish-pypi.yml
+
+error[template-injection]: code injection via template expansion
+   --> path/here/pyosMeta/.github/workflows/publish-pypi.yml:97:7
+github.ref_name may expand into attacker-controllable code
+```
+
+You can also set up `zizmor` as a pre-commit hook. pyOpenSci plans to do this in the  future, but here is an example of it [set up for core Python](https://github.com/python/cpython/pull/127749/files#diff-63a9c44a44acf85fea213a857769990937107cf072831e1a26808cfde9d096b9R64).
+
+Pre-commit hooks run checks every time you commit a file to Git history. [Learn more about using them here.](https://www.pyopensci.org/python-package-guide/package-structure-code/code-style-linting-format.html#use-pre-commit-hooks-to-run-code-formatters-and-linters-on-commits)
+
+## Other security measures you can consider
+
+There are other things that we can learn too from the recent breach. Many of these will be identified if you set up zizmor. These are discussed below.
+
+
+### Sanitize branch names in your workflow
+
+One of the critical issues in the Ultralytics breach involved a
+[**malicious branch name containing a shell script**](https://github.com/ultralytics/ultralytics/pull/18020)
+that was executed because `github.ref` was used without sanitization. This type
+of attack, known as **template injection**, allows malicious content in branch
+names to be treated as shell commands.
+
+
+> ...is a classic GitHub Actions template injection: the expansion of `github.head_ref || github.ref` is injected directly into the shell’s context, with no quoting or interpolation..
+>
+> — https://blog.yossarian.net/2024/12/06/zizmor-ultralytics-injection
+
+
+Because the branch name wasn’t sanitized, it was treated as a shell command and executed with full permissions. Yikes!
+
+In the example below, an unsanitized branch name could execute harmful commands:
+
+```yaml
+jobs:
+  example-job:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Run a script
+        run: |
+          echo "Running script for branch: $GITHUB_REF"
+```
+
+To prevent this, [sanitize or clean](https://docs.github.com/en/get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names) branch names before using them. A small Bash step can
+remove unsafe characters:
+
+
+```yaml
+jobs:
+  example-job:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Sanitize branch name
+        run: |
+          SAFE_BRANCH=$(echo $GITHUB_REF | sed 's/[^a-zA-Z0-9_\-\/]//g')
+          echo "Sanitized branch name: $SAFE_BRANCH"
+          echo "Running script for branch: $SAFE_BRANCH"
+```
+
+
+## Lock down GitHub permissions & delete old PyPI tokens and GitHub secrets
+
+In addition to securing your workflows, lock down your accounts and repositories. 2FA (2-factor authentication) is thankfully now required as a security measure for both GitHub and PyPI. However, be sure to store your recovery codes somewhere safe (like in a password manager!).
+
+Also consider:
+
+- **Revoking old tokens**: If you've previously created PyPI API tokens and/or associated GitHub secrets, delete any unused or outdated ones.
+- **Restrict repository access**: Limit write GitHub repository access to a trusted subset of maintainers. Most contributors don’t need direct write access, which reduces security risks.
+
+
+### 🚫 Avoid `pull_request_target` and consider release-based workflows
+
+A trigger event in a GitHub Action is an event that sets off an action to run. For instance, you might have a trigger that runs a linter like Black or Ruff when a new pull request is opened.
+
+The [`pull_request_target`](https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request_target) trigger event in GitHub Actions that Ultralytics used allows workflows to run with elevated permissions on the base branch, even when triggered by changes from a fork. Thus, your workflow becomes vulnerable when used as a trigger to push a release to PyPI.
+
+Instead of a pull_request_target or a pull_request, consider adopting a **release-based publishing workflow**. This approach:
+
+- Triggers publication workflows only on new versioned releases. You can lock down which maintainers are allowed to create releases using GitHub permissions
+- Ensure workflows related to publishing are explicitly scoped to `release` events.
+
+In the example GitHub Action `.yaml` file below, you see a `release` trigger defined. This tells the action to only trigger the workflow when you publish a release.
+
+
+```yaml
+name: Publish to PyPI
+on:
+  # By using release as a trigger, only GitHub users and actions with write access to make releases to our repo can trigger the push to PyPI
+  release:
+    types: [published]
+```
+
+Using a release-based workflow ensures that your publishing step is tightly controlled. A pull request will never accidentally trigger a publish build. This reduces your risk!
+
+
+
+## Don’t cache package dependencies in your publish step
+
+Caching dependencies involves storing dependencies to be reused in future workflow runs. This approach saves time, as GitHub doesn’t need to redownload all dependencies each time the workflow runs.
+
+However, caching dependencies can allow attackers to manipulate cached artifacts. If this happens, the workflow may pull in compromised versions from the cache during the next run.
+
+
+## Learn More
+
+pyOpenSci follows best practices for PyPI publishing using our custom GitHub Actions workflow. Check out our tutorial on Python packaging here:
+👉 [pyOpenSci Packaging Tutorial](https://www.pyopensci.org/python-package-guide/package-structure-code/python-package-structure.html)
+👉 Join our discourse here
+
+<div class="notice" markdown="1">
+## Get involved with pyOpenSci
+
+* Check out our [volunteer page](https://www.pyopensci.org/volunteer.html) if you are interested in getting involved.
+* Keep an eye on our [events page](/events/) for upcoming training events.
+
+Follow us on social platforms:
+
+* [<i class="fa-brands fa-mastodon"></i> Mastodon](https://fosstodon.org/@pyopensci)
+* [<i class="fa-solid fa-cloud"></i> Bluesky](https://bsky.app/profile/pyopensci.org)
+* [<i class="fa-brands fa-linkedin"></i> LinkedIn](https://www.linkedin.com/company/pyopensci)
+* [<i class="fa-brands fa-github"></i> GitHub](https://github.com/pyOpenSci)
+
+If you are on LinkedIn, you should [subscribe to our newsletter, too](https://www.linkedin.com/newsletters/7179551305344933888/?displayConfirmation=true).
+</div>
diff --git a/content/blog/2025-03-18-contribute-to-open-source-github-lessons.md b/content/blog/2025-03-18-contribute-to-open-source-github-lessons.md
new file mode 100644
index 00000000..b43c12b2
--- /dev/null
+++ b/content/blog/2025-03-18-contribute-to-open-source-github-lessons.md
@@ -0,0 +1,93 @@
+---
+title: 'Contribute to Open Source Software: It''s  More Than just Code'
+date: '2025-03-18'
+type: blog
+excerpt: Contributing to open source isn’t just about code—it’s also about navigating
+  social norms. Discover pyOpenSci’s new Contribute to Open Source lessons, which
+  cover both the technical and social aspects, and are free for anyone to use.
+author: Leah Wasser
+blog_topic: learn
+toc: true
+comments: true
+url: "/blog/contribute-to-open-source-lessons.html"
+lastmod: '2025-03-11'
+image:
+  src: images/headers/pyopensci-floral.png
+  alt: 'Contribute to Open Source Software: It''s  More Than just Code'
+---
+
+## Beyond code: the social side of open source
+
+When you think about contributing to open source, you might assume the biggest hurdle for newcomers is technical--learning Git, using GitHub, and/or writing code. Most contribute to open source guides focus on technical skills. But for many new contributors, the challenge isn’t only technical—it’s social too.
+
+Receiving open feedback on your contributions in the form of code review, whether code or documentation, [creates anxiety for  many](https://osf.io/preprints/psyarxiv/8k5a4_v1).
+
+- <i class="fas fa-user-plus" style="color:#81c0aa;"></i> **Joining an unfamiliar community:** Understanding who to reach out to and how the project operates can feel intimidating.
+- <i class="fas fa-comments" style="color:#81c0aa;"></i> **Understanding unspoken norms:**  Every project has its own culture, from how discussions happen to how decisions are made. And these norms are not always well-documented.
+- <i class="fas fa-handshake" style="color:#81c0aa;"></i> **Building confidence in a new space:** Many contributors worry about making mistakes, be it while using GitHub or submitting a Pull Request or even in the content updates themselves.
+- <i class="fas fa-exclamation-circle" style="color:#81c0aa;"></i> **Navigating constructive feedback** – Open source is built on open peer review; however, receiving public feedback on a contribution can be intimidating.
+
+
+In my 10+ years of building and maintaining software, contributing to projects, and running beginner-friendly sprints, I’ve seen firsthand that communication, collaboration, and project culture are just as—if not more—important than technical skills. I've also experienced the imposter syndrome first-hand. I was nervous about my first contributions and wasn't sure how to start contributing in a meaningful way.
+
+**Technical and social skills go hand in hand.** Open source communities are most productive when contributors and maintainers recognize this balance between the technical and social skills associated with contributing. In most cases, all of the people involved in the project are volunteers with varying priorities, skillsets, and motivations to participate.
+{: .notice .notice--info}
+
+### Developing our contribute to open source lessons
+
+This past year, with support from the [Better Software for Science (BSSw) Fellowship](https://bssw.io/fellows/leah-wasser), I developed lessons shaped by insights gained from the [pyOpenSci contributor community](https://www.pyopensci.org/our-community/index.html). Our lessons are now freely available as open educational resources designed to help contributors and maintainers foster a more welcoming, collaborative and productive open source community.
+
+<a href="https://www.pyopensci.org/lessons/contribute-open-source/index.html" class="btn btn--success">Check out our lessons now.</a>
+
+> BSSw is a unique partnership between the National Science Foundation (NSF) and the Department of Energy (DOE) that provides small grants to advocates in the scientific open source space.
+{: .notice }
+
+### A community-driven approach to open source
+
+Over the past two years, **pyOpenSci has welcomed over 300 contributors**, with more than **120 issues and pull requests** submitted during our [beginner-friendly sprints](/blog/pyopensci-pyconus-2024-sprints.html). These experiences reinforced what we already knew—technical skills are just one part of people successfully contributing to open source.
+
+Through our sprints, we saw firsthand how **clear guidance, supportive communities, and transparent contribution processes** helps newcomers gain confidence. Often, they stick around our community after the events. These insights shaped our *Contribute to Open Source* lessons.
+
+## Beyond code: The social skills of open source
+
+Our lessons address both the technical and social aspects of contributing to open source.
+
+### For contributors: how to navigate your first contribution
+
+For contributors, we focus on:
+1. Understanding the technical steps surrounding making your first contribution
+2. Signals that tell you that a project welcomes newcomers and,
+3. What to expect as they navigate their first contributions.
+
+A few highlights include:
+
+- <i class="fas fa-book" style="color:#81c0aa;"></i> **[Get to know a repository](https://www.pyopensci.org/lessons/contribute-open-source/get-to-know-repo.html):** Learn how to look for documentation files like `CONTRIBUTING` and `DEVELOPMENT` guides that will become your guiding light in making your first contributions. These files should help you understand whether new contributions are welcome, what the contribution process is, and what types of contributions are welcome.
+- <i class="fas fa-search" style="color:#81c0aa;"></i> **[Find and understand issues](https://www.pyopensci.org/lessons/contribute-open-source/identify-issue.html):** Explore how to search and create GitHub issues as you begin the process of finding a task to work on. Learn how to communicate effectively with maintainers who you may have never interacted with before.
+- <i class="fas fa-code-branch" style="color:#81c0aa;"></i> **[Create effective pull requests](https://www.pyopensci.org/lessons/contribute-open-source/pull-request.html):** Learn how to open a pull request, write clear pull request messages titles and descriptions. Also, learn how to make the pull request process more efficient by reviewing your own work and linking your PR to an issue to streamline maintainer review.
+
+### For Maintainers: Creating a contributor-friendly repository
+
+While these lessons are focused on contributing, we also provide some maintainer tips to help set clear expectations for contributors:
+
+- <i class="fas fa-comments" style="color:#81c0aa;"></i> **Communicate your availability:** Let contributors know if you have time to support them. It’s okay if you're busy—just set clear expectations!
+- <i class="fas fa-file-alt" style="color:#81c0aa;"></i> **Provide clear guidelines:** Add `CODE_OF_CONDUCT`, `CONTRIBUTING`, and `DEVELOPMENT` files to define what contributions you welcome and how contributors should engage with your project.
+- <i class="fas fa-tools" style="color:#81c0aa;"></i> **Use automation to support contributors:** Tools like [pre-commit.ci](https://pre-commit.ci/) help automate formatting and linting, reducing friction for new contributors.
+
+## Co-Creating open source contribution lessons
+
+Our *Contribute to Open Source* lessons, like all pyOpenSci resources, are co-developed collaboratively. By bringing together contributors with different backgrounds and skill levels, we ensure our materials are clear, accurate, and welcoming.
+
+A diverse contributor base makes our lessons stronger:
+* <i class="fas fa-microscope" style="color:#81c0aa;"></i> **Experts** provide technical accuracy.
+* <i class="fas fa-user-graduate" style="color:#81c0aa;"></i> **Beginners** ensure content is approachable.
+* <i class="fas fa-users" style="color:#81c0aa;"></i> **Everyone in between** help refine and improve the content.
+
+This same community-driven approach shaped our [packaging guide](https://www.pyopensci.org/python-package-guide/), which covers [packaging tools](https://www.pyopensci.org/python-package-guide/package-structure-code/python-package-build-tools.html) and [tutorials](https://www.pyopensci.org/python-package-guide/tutorials/intro.html). Like our lessons, it was co-developed and openly reviewed to ensure accessibility and clarity.
+
+{{< figure src="images/peer-review/co-development-open-education.png" alt="A diagram illustrating the co-development of open lessons by pyOpenSci. The diagram consists of a circular section divided into five segments labeled 'Maintainers,' 'Beginners,' 'Experts,' 'Researchers,' and 'Contributors,' surrounding a central section labeled 'Moderation.' An arrow extends from the circle to the right, labeled with key moderation activities such as 'Listen,' 'Moderate,' 'Facilitate,' 'Structured review,' and 'Code of Conduct,' leading to 'Accessible Lessons.' The background features a subtle floral pattern." >}}
+
+By openly co-developing and refining these resources together, we’re making scientific open source more accessible for everyone.
+
+## What's next? Broadening participation in open source
+
+With [PyCon US](https://us.pycon.org/2025/) and SciPy on the horizon, we’re excited to put these lessons into action. At our upcoming sprints, we’ll work together to **refine these resources—improving the lessons and packaging guide to make participating open source even more accessible.**  If you plan to be at either meeting, keep an eye out for pyOpenSci events!
diff --git a/content/blog/2025-03-21-pyopensci-commitment-inclusion.md b/content/blog/2025-03-21-pyopensci-commitment-inclusion.md
new file mode 100644
index 00000000..74a5e434
--- /dev/null
+++ b/content/blog/2025-03-21-pyopensci-commitment-inclusion.md
@@ -0,0 +1,55 @@
+---
+title: Reaffirming pyOpenSci's Commitment to Inclusion
+date: '2025-03-21'
+type: blog
+excerpt: pyOpenSci is growing a global, vibrant and inclusive open source community
+  where everyone from all backgrounds and identities can contribute to better, more
+  open science. Join us in breaking down barriers and building a future where all
+  voices shape scientific discovery.
+author: Executive Council
+blog_topic: community
+toc: true
+comments: true
+url: "/blog/pyopensci-commitment-inclusion.html"
+lastmod: '2025-03-21'
+image:
+  src: images/headers/pyopensci-floral.png
+  alt: Reaffirming pyOpenSci's Commitment to Inclusion
+---
+
+During challenging times, it’s critical to pause and reflect on who we are, what we care about, and why our work matters. Since its inception, pyOpenSci, a global community fiscally sponsored in the U.S., has been committed to actively building an inclusive, welcoming, open source community of practice that supports better, more open science. Our Code of Conduct reinforces our [values,](https://www.pyopensci.org/handbook/CODE_OF_CONDUCT.html) as does the thought that we put into the events that we run, the accessible resources that we develop, and the work that we do to make our [peer review program inclusive](https://www.pyopensci.org/#broadening-participation-in-scientific-open-source) and [creating Python software easier](https://www.pyopensci.org/python-package-guide/tutorials/intro.html).
+
+Today, we celebrate the core values that drive pyOpensci. Today, we reaffirm our long-standing commitment to building an inclusive, open source community and highlight our mission.
+
+> pyOpenSci broadens participation in scientific open source by breaking down social and technical barriers.
+
+And this is how we achieve our mission:
+
+> We are a community of novice to expert Pythonistas; together, we make creating, finding, sharing, and contributing to reusable code more accessible to everyone everywhere, supporting open science and advancing discovery.
+
+## Carving out space for everyone
+
+Creating an inclusive and welcoming space is core to broadening participation in open source and open science.
+
+* When people feel supported, they contribute
+* When knowledge is shared, communities grow and thrive.
+
+Through mentorship, beginner-friendly events, and accessible resources, we actively invite those who might not otherwise see a place for themselves in open source. Our review process includes both developers and those who use the software; here, inclusion ensures that our reviews consider usability and accessibility in addition to the technical nuances of packaging.
+
+{{< figure src="images/events/sprint-people-working.png" alt="..." >}}
+
+Through mentorship and support, we carve out space for new reviewers, which includes those from historically underrepresented backgrounds in open source to contribute to peer review. Similarly, our beginner-friendly lessons and training events are co-developed with beginner-to-expert contributors to ensure the technical concepts are accessible to more people.
+
+**Inclusion invites everyone to the table**; it creates space for new contributors and supports existing community members. Inclusion creates opportunities for everyone to work together. Together, we share knowledge, shape best practices, and ensure our work serves the broader community.
+
+{{< figure src="images/events/sprint-mentor-luiz-meer.png" alt="..." >}}
+
+## A blossoming ecosystem of contributors
+
+By breaking down barriers, we create open science on-ramps that help everyone learn, contribute, and grow together. In many ways, open source communities are like thriving gardens—diverse, vibrant, and sustained by many contributors.
+
+The most vibrant and resilient gardens are full of diverse color, texture, and life, attracting pollinators that sustain the whole system. Cultivating diversity builds resilience. Similarly, contributors in our pyOpenSci community come from different backgrounds, identities, and experience levels.
+
+When we make space for all contributors—ensuring they have what they need to grow—our community becomes more resilient as the ecosystem evolves. Scientific discovery happens organically. The more perspectives and experiences we include, the more impactful our work becomes.
+
+{{< figure src="images/events/sprint-scipy-2024.png" alt="..." >}}
diff --git a/content/blog/2025-05-06-pyos-pyconus-2025.md b/content/blog/2025-05-06-pyos-pyconus-2025.md
new file mode 100644
index 00000000..f864f87b
--- /dev/null
+++ b/content/blog/2025-05-06-pyos-pyconus-2025.md
@@ -0,0 +1,46 @@
+---
+title: pyOpenSci at PyCon US 2025 - Python, Packaging and Community
+date: '2025-05-06'
+type: blog
+excerpt: pyOpenSci is excited to be at PyCon US for the third year in a row! Find
+  us at the Maintainers summit on May 16th and then join us for a beginner-friendly
+  sprint after the meeting.
+author: Leah Wasser
+blog_topic: community
+toc: true
+comments: true
+url: "/blog/pyopensci-at-pyconus-2025.html"
+lastmod: '2025-05-06'
+image:
+  src: images/blog/headers/pycon-us-2024-header.png
+  alt: pyOpenSci at PyCon US 2025 - Python, Packaging and Community
+---
+
+<div class="notice" markdown = "1">
+## TL;DR
+
+* We’re excited to get back to PyCon US this year!
+* Join us for the Maintainers Summit, community events, and the Packaging Summit. At the end of each meeting, we will hold beginner-friendly sprints.
+* Join us in our beginner-friendly sprints on Monday / Tuesday following the conference.
+* Last year’s recap: [Read about pyOpenSci at PyCon US 2024](/blog/recap-pyos-pyconus-2024.html)
+
+</div>
+
+## PyCon US Maintainers Summit: Co-hosted by pyOpenSci
+
+I'm thrilled to be a second-time organizer of the PyCon US [Maintainers Summit](https://us.pycon.org/2025/events/maintainers-summit/) alongside long-time organizer [Inessa Pawson](https://github.com/InessaPawson) and Python Steering Council alum and past PyCon chair [Mariatta Wijaya](https://github.com/mariatta). This annual event brings maintainers, contributors, and community leaders together to share challenges and strategies in maintaining and sustaining open source software.
+
+
+{{< figure src="images/events/pyconus-maintainers-summit-2025.png" alt="Group of attendees collaborating at round tables during the PyCon US Maintainers Summit 2025, with text that reads 'Join Us! PyCon US Maintainers Summit 2025 – Friday 16 May 2025'. Two organizers pose and smile in the foreground wearing conference badges and masks." >}}
+
+All are welcome to attend, listen to talks, and connect with fellow Pythonistas who care about maintaining open source software!
+
+## Python packaging summit
+
+We’re also excited to attend the **Packaging Summit** this year. There's been a lot of work to improve the Python packaging ecosystem in the past year. This event is an excellent opportunity to learn more about current efforts.
+
+## Community lead activities
+
+Our advisory council member Chase Million will be hosting a space-focused open space (that's a mouthful!!), so if you are in the space science arena, keep an eye out on the Open Space board in the Hallway track at PyCon US for that!
+
+Also, check out [Zack Weinberg's talk on writing Extensions in Python that can be interrupted if you need to pause the task](https://us.pycon.org/2025/schedule/presentation/39/).
diff --git a/content/blog/2025-06-30-pyos-scipy-2025.md b/content/blog/2025-06-30-pyos-scipy-2025.md
new file mode 100644
index 00000000..90f28821
--- /dev/null
+++ b/content/blog/2025-06-30-pyos-scipy-2025.md
@@ -0,0 +1,188 @@
+---
+title: pyOpenSci at SciPy 2025 - science, Python and Community
+date: '2025-06-30'
+type: blog
+excerpt: pyOpenSci is excited to be at SciPy 2025 this year! Find us at our second
+  packaging tutorial, a birds of a feather session and hanging out in sessions where
+  our community members are leading events and talks. Don't forget to join us for
+  our beginner-friendly sprint after the meeting!
+author: pyopensci
+blog_topic: community
+toc: true
+comments: true
+url: "/blog/pyopensci-at-scipy-2025.html"
+lastmod: '2025-05-06'
+image:
+  src: images/headers/pyopensci-scipy-2025.png
+  alt: pyOpenSci at SciPy 2025 - science, Python and Community
+---
+
+## pyOpenSci at SciPy 2025: Community, Contribution, and Packaging Know-How
+
+We're heading to SciPy 2025 in Tacoma, Washington, and we couldn’t be more excited to connect with the incredible scientific Python community in person! This year, we’re showing up with tutorials, conversations, and community-driven events designed to support open science and lower the barrier to contributing to open source.
+
+Here's how you can connect with us throughout the conference:
+
+
+### Learn Packaging with pyOpenSci (Tutorial)
+
+pyOpenSc is back this year, teaching a hands-on tutorial on **Python packaging for scientific software**. Whether you’re just getting started or looking to strengthen your skills, this session is for you. You'll leave with a better understanding of how to create Python packages that are shareable, reusable, and aligned with scientific best practices.
+
+**When:** Monday, July 7, 2025, at 1:00 pm PDT \
+**Where:** Room 613/614, Greater Tacoma Convention Center \
+**Learn more / Register:** [SciPy 2025 Tutorial: Learn Packaging with pyOpenSci](https://cfp.scipy.org/scipy2025/talk/Z3VBWR/) \
+**Who’s teaching:**
+
+* **[Leah Wasser](https://github.com/lwasser)**: Executive Director and founder of pyOpenSci and open science community builder
+* **[Carol Willing](https://github.com/willingc)**: Long-time Python core developer and Jupyter contributor
+* **[Jeremiah Paige](https://github.com/ucodery)**: Pythonista and packaging expert
+* **[Tetsuo Koyama](https://github.com/tkoyama010)**: Software engineer and scientific open source contributor
+* **[Inessa Pawson](https://github.com/InessaPawson)**: Open Source program manager at Open Teams,  and advocate for inclusive open source
+
+**Note:** Tutorial registration is separate from your main conference ticket, so grab your spot early if you want in!
+
+### BoF: Let’s Talk About Python Packaging Pain Points
+
+**When:** Thursday, July 10, 2025, 1:15–2:10 pm PDT \
+**Where:** Room 315, Greater Tacoma Convention Center
+
+We’re thrilled to be hosting a **Birds of a Feather (BoF)** session this year—a full-circle moment, since pyOpenSci first kicked off with a BoF at SciPy in 2019. This time, we're gathering folks to talk candidly about the **pain points and friction** in Python packaging for scientific software. Join us for an interactive session. Share your pain points to help direct the work that pyOpenSci does over the upcoming year, and learn how to get involved.
+
+#### About the BoF
+
+This Birds of a Feather session invites attendees to join a community conversation around the challenges and solutions in packaging scientific software using Python. From figuring out where to start with packaging to troubleshooting wheels, reproducibility, and publishing to PyPI or conda-forge, we know many of these steps aren’t well-documented or can feel overwhelming.
+
+This session is a space for maintainers, contributors, and users to share:
+
+* What’s worked and what hasn’t in their packaging journey
+* Resources, tools, or templates that have helped
+* Ideas for how the community can better support each other
+
+
+### [Open Code, Open Science — What’s Getting in Your Way?](https://cfp.scipy.org/scipy2025/talk/3ZHYMH/)
+
+Collaborating on code and software is essential to open science—but it’s not always easy. Join this BoF for an interactive discussion on the real-world challenges of open source collaboration. We’ll explore common hurdles like Python packaging, contributing to existing codebases, and emerging issues around LLM-assisted development and AI-generated software contributions.
+
+We’ll kick off with a brief overview of pyOpenSci—an inclusive community of Pythonistas, from novices to experts—working to make it easier to create, find, share, and contribute to reusable code. We’ll then facilitate small-group discussions and use an interactive Mentimeter survey to help you share your experiences and ideas.
+
+Your feedback will directly shape pyOpenSci’s priorities for the coming year, as we build new programs and resources to support your work in the Python scientific ecosystem. Whether you’re just starting out or a seasoned developer, you’ll leave with clear ways to get involved and make an impact on the broader Python ecosystem in service of advancing scientific discovery.
+
+**Session Conveners:**
+
+* **[Leah Wasser](https://github.com/lwasser)** – Executive Director and Founder of pyOpenSci
+* **[Inessa Pawson](https://github.com/InessaPawson)** – Open Teams Open Source Program Manager, NumPy Steering Council Member
+* **[Tetsuo Koyama](https://github.com/tkoyama010)** – Scientific computing and visualization developer, PyVista team
+* **[Jeremiah Paige](https://github.com/ucodery)** – Python packaging expert
+* **[Avik Basu](https://github.com/ab93)** – Scientific open source contributor
+
+### **[Sprint With Us!](https://www.scipy2025.scipy.org/sprints)**
+
+**When:** July 12-13, 2025 \
+**Details:** Breakfast at 8:00 a.m., Kickoff at 9:00 a.m.
+
+Join us during the SciPy sprint weekend to work on real-world problems in open science.
+
+You can help us:
+
+* Improve and write documentation
+* Review tutorials
+* Translate our Python packaging guide
+* Contribute to our infrastructure
+
+Our sprints are:
+
+* Beginner-friendly
+* Focused on Python packaging, documentation, and translation
+* Collaborative and welcoming
+
+No prior open source experience? No problem. We’ve got guided lessons and mentors ready to help you take your first (or next!) step as a contributor.
+
+Check out our [help-wanted project board](https://github.com/orgs/pyOpenSci/projects/3/views/2) to get a sense of some of the ways you can contribute or help pyOpenSci during the event.
+
+### You won’t want to miss these pyOpenSci community member talks
+
+Make sure to support members of the pyOpenSci community who are speaking or presenting at SciPy 2025!
+
+Let’s cheer each other on, learn together, and continue making open science more accessible!
+
+### pyOpenSci Community Member Tutorials
+
+#### [Shiny for Python – Building Production-Ready Dashboards](https://cfp.scipy.org/scipy2025/talk/HEHW8W/)
+
+When: **Tuesday, July 8th, 2025, 1:30–5:30 pm PDT**
+Where: **Ballroom D, Greater Tacoma Convention Center**
+
+If you’re ready to level up your Python dashboards, don’t miss **[Daniel Chen’s](https://github.com/chendaniely)** hands-on workshop at SciPy 2025: *Shiny for Python – Building Production-Ready Dashboards*. Held on July 8, this half-day session will walk you through creating scalable web applications using Shiny’s new Python framework. You’ll learn to refactor apps with modules, write tests with Playwright, and deploy dashboards for free.
+
+Daniel brings deep teaching experience from his roles at Posit and UBC, making this ideal for Python users looking to expand into interactive web development—even if you’ve never touched Shiny before.
+
+Check out the dashboard templates in advance:[ Shiny for Python Templates](https://shiny.posit.co/py/templates/)
+
+
+#### [Reproducible ML Workflows with pixi](https://cfp.scipy.org/scipy2025/talk/GDN8PN/)
+
+**When: **Monday, July 7th, 2025, 1:30–5:30 pm PDT**
+**Where: **Room 315, Greater Tacoma Convention Center**
+
+Don’t miss *Reproducible Machine Learning Workflows for Scientists with pixi*—a practical, hands-on tutorial at SciPy 2025 led by data physicist **[Matthew Freikert](https://cfp.scipy.org/scipy2025/speaker/H8ZFYG/)**. This half-day workshop tackles one of the most frustrating pain points in scientific computing: building reproducible, CUDA-enabled environments across diverse machines.
+
+Matthew will walk participants through using Pixi, an fast, and efficient environment manager that supports conda, to create robust Python workflows with PyTorch and JAX. You’ll learn to install hardware-accelerated environments, solve for multi-platform lock files, and deploy them via container images—no prior CUDA or ML expertise required.
+
+Come prepared to code and leave with a repeatable setup for your AI/ML experiments.
+
+Learn more about pixi:[ https://pixi.sh](https://pixi.sh)
+
+#### [3D Visualization with PyVista](https://cfp.scipy.org/scipy2025/talk/MHNTAD/)
+
+**When: **Monday, July 7th, 2025, 1:30–5:30 pm PDT**
+Where: **Ballroom D, Greater Tacoma Convention Center**
+
+Get ready to bring your data to life in *3D Visualization with PyVista*, a hands-on SciPy 2025 tutorial led by PyVista co-creator **[Bane Sullivan](https://cfp.scipy.org/scipy2025/speaker/NEC33M/)** and core developer **[Tetsuo Koyama](https://github.com/tkoyama010)**. Taking place July 7, this session will introduce you to PyVista—a Pythonic interface to VTK that makes 3D plotting as intuitive as using Matplotlib.
+
+Used in over 2,000 open-source projects, PyVista is the go-to library for interactive 3D visualization across fields like engineering, geophysics, and scientific computing. You’ll explore real-world datasets, master PyVista’s data structures and filters, and learn how to integrate with libraries like meshio and trimesh. Plus, you’ll get hands-on with Jupyter plugins for server- and client-side rendering.
+
+Whether you’re a Python beginner or a power user looking to deepen your visualization toolkit, this tutorial is for you.
+
+Get set up before the workshop:[ https://tutorial.pyvista.org/getting-started.html#installation](https://tutorial.pyvista.org/getting-started.html#installation)
+
+
+### pyOpenSci Community Member Talks
+
+
+#### [Packaging a Scientific Python Project](https://cfp.scipy.org/scipy2025/talk/RECJVV/)
+
+**When: **Wednesday, July 9th, 2025, 1:55–2:25 pm PDT**
+Where: **Room 317, Greater Tacoma Convention Center**
+
+If you’ve ever felt overwhelmed by the rapidly evolving Python packaging ecosystem, **[Henry Schreiner’s](https://github.com/henryiii)** talk at SciPy 2025 is a must-attend. In *Packaging a Scientific Python Project*, Henry walks attendees through best practices for preparing scientific software for distribution using the **Scientific Python Development Guide**—an evolving resource he helped author.
+
+This session covers everything from backend selection and GitHub Actions to packaging compiled components with tools like scikit-build-core, pybind11, and cibuildwheel. Henry will also demo the repo-review tool, which checks your project against current best practices—right in the browser using WebAssembly.
+
+Whether you’re starting a new package or upgrading an old one, you’ll walk away with modern workflows and tooling that make robust, reproducible packaging less painful—and more powerful.
+
+
+<div class="notice" markdown="1">
+## Connect with us
+
+There are lots of ways to get involved if you are interested!
+
+* If you read through our lessons and want to suggest changes, open an issue in our [lessons repository here](https://github.com/pyOpenSci/lessons).
+* [Volunteer to be a reviewer for pyOpenSci’s software review process](https://docs.google.com/forms/u/6/d/e/1FAIpQLSeVf-L_1-jYeO84OvEE8UemEoCmIiD5ddP_aO8S90vb7srADQ/viewform?usp=send_form).
+* [Submit a scientific Python package to pyOpenSci for peer review.](https://www.pyopensci.org/software-peer-review/how-to/author-guide.html#submit-your-package-for-peer-review)
+* [Donate to pyOpenSci](https://give.communityin.org/pyopensci_2024?ref=ab_0sHhtifYvgR0sHhtifYvgR) to support scholarships for future training events and the development of new learning content.
+* Check out our [volunteer page](https://www.pyopensci.org/volunteer.html) for other ways to get involved.
+
+You can also:
+
+* Keep an eye on our [events page](https://www.pyopensci.org/events/) for upcoming training events.
+
+Follow us on socials:
+
+* [Mastodon](https://fosstodon.org/@pyopensci)
+* [Bluesky](https://bsky.app/profile/pyopensci.org)
+* [LinkedIn](https://www.linkedin.com/company/pyopensci/)
+* [GitHub](https://github.com/pyOpenSci)
+
+If you are on LinkedIn, check out and [subscribe to our newsletter](https://www.linkedin.com/newsletters/7179551305344933888/?displayConfirmation=true), too.
+
+</div>
diff --git a/content/blog/2025-07-24-scipy-2025-recap.md b/content/blog/2025-07-24-scipy-2025-recap.md
new file mode 100644
index 00000000..a4ff331a
--- /dev/null
+++ b/content/blog/2025-07-24-scipy-2025-recap.md
@@ -0,0 +1,96 @@
+---
+title: 'Highlights from SciPy 2025: Building Community, Code, and Culture'
+date: '2025-07-24'
+type: blog
+excerpt: Explore pyOpenSci’s highlights from SciPy 2025—from Python packaging workshops
+  and talks to first-time contributions, collaboration, and open science in action.
+author: pyopensci
+blog_topic: community
+toc: true
+comments: true
+url: "/blog/scipy-2025-recap.html"
+lastmod: '2025-05-06'
+image:
+  src: images/headers/pyopensci-scipy-2025.png
+  alt: 'Highlights from SciPy 2025: Building Community, Code, and Culture'
+---
+
+{{< figure src="images/events/scipy-2025/pixi-workshop.png" alt="A room full of attendees at the pyOpenSci packaging workshop during SciPy 2025, all seated and coding on laptops." >}}
+
+[SciPy 2025](https://www.scipy2025.scipy.org/) was one for the books, and for [pyOpenSci](https://www.pyopensci.org/), it was a powerful reminder of how far our community has come and how much energy we bring when we show up together.
+
+This year, more than 15 members of the pyOpenSci community participated in the conference. We hosted a workshop, facilitated a BoF session with over 60 participants, gave talks, and filled the hallway track with laughter, advice, and real conversations about scientific Python pain points and the future of research software. We also led a community sprint where contributors opened over 30 issues and pull requests—an incredible showing of collaboration across experience levels.
+
+To help new contributors feel supported, we shared our ['Contribute to Open Source' lessons](https://www.pyopensci.org/lessons/contribute-open-source/), which walk you through the process of making your first contribution in a welcoming, beginner-friendly way.
+
+Here are a few additional highlights from the week.
+
+## ⚙️ Workshops: Packaging tools, templates, and fast-track setups
+
+We kicked off SciPy with our pyOpenSci packaging workshop, where we introduced participants to our user-friendly packaging template and taught modern packaging practices using [Hatch](https://hatch.pypa.io). This was the second time we used the template in a live setting, and it was just as smooth as we hoped. Answer a few questions, and boom\! You’ve got a working, standards-compliant Python package.
+
+We love Hatch because it includes a task runner out of the box (see [the Scientific Python Development Guide](https://learn.scientific-python.org/development/) for why that matters), and it integrates seamlessly with [UV](https://astral.sh/uv). Hatch has supported UV under the hood for a while, and with a single config line in your pyproject.toml, you can enable UV’s speed in your workflow. (We’ve already [baked that into our template](https://github.com/pyOpenSci/pyos-package-template).)
+
+Shoutout to [Carol Willing](https://github.com/willingc), [Inessa Pawson](https://github.com/InessaPawson), [Jeremiah Paige](https://github.com/ucodery), and [Tetsuo Koyama](https://github.com/tkoyama010) for making this workshop such a success.
+
+We also attended the Pixi workshop, which showcased how [Pixi](https://pixi.sh) utilizes UV and supports mixed [PyPI](https://pypi.org/)/[Conda](https://docs.conda.io/projects/conda/en/latest/user-guide/getting-started.html) environments. The instructors walked us through spinning up cloud-based GPU compute using [NVIDIA Brev,](https://developer.nvidia.com/brev) which was quick, powerful, and surprisingly easy to configure. Pixi is a great option for you if you want the speed of UV but the Conda support!
+
+{{< figure src="images/events/scipy-2025/bof-discussions-pyopensci.png" alt="Small group discussion at pyOpenSci's Packaging Pain Points BoF session at SciPy 2025, with participants seated in a circle sharing insights." >}}
+
+## BoF: Breaking Down Pain Points, Together
+
+Our “Packaging Pain Points” BoF (Birds of a Feather) session drew *over 60 participants* and an incredible buzz of energy! We split into small groups to talk about the social and technical challenges researchers face when sharing Python code and workflows. The conversation was honest, collaborative, and energizing.
+
+We’ll share a dedicated post soon about the insights we gathered, but one thing is already clear: when we come together to name what’s hard, we create the conditions for real, inclusive solutions.
+
+Huge thanks to [Leah Wasser](https://github.com/lwasser), [Jonny Saunders](https://github.com/sneakers-the-rat), [Avik Basu](https://github.com/ab93), [Jeremiah Paige](https://github.com/ucodery), [Inessa Pawson](https://github.com/InessaPawson), [Tetsuo Koyama](https://github.com/tkoyama010), and everyone who helped make the session run smoothly.
+
+## Sprinting Toward Sustainable Software
+
+Our final-day sprint was one of the most vibrant and heartening moments of the week. The pyOpenSci community showed up in full force—so much so that we had to push two sets of tables together to fit everyone. The room buzzed with activity as over 30 issues and pull requests were opened in just one day, many from first-time contributors.
+
+What made it especially powerful? Experienced maintainers paired up organically with newcomers, walking them through the setup process, answering questions, and celebrating small wins. It was a clear embodiment of the pyOpenSci ethos: mentorship, openness, and shared learning.
+
+To support folks new to open source, we shared our [Contribute to Open Source lessons](https://www.pyopensci.org/lessons/), which walk through how to make your first contribution in a supportive and beginner-friendly way. These lessons helped ease people into the sprinting process and gave them the confidence to get started.
+
+We’re grateful to everyone who joined, and especially to those who made their very first open source contributions with us. If you were there, you helped make something truly special.
+
+{{< figure src="images/events/scipy-2025/pyopensci-python-packaging-workshop.png" alt="A woman Leah Wasser, smiling at the podium while preparing to present at a pyOpenSci workshop at SciPy 2025, with attendees gathered behind her." >}}
+
+## Talks, Lightning Talks, and the Hallway Track
+
+We’ll be honest, there were too many great talks at SciPy to cover them all. But we want to highlight a few of the more memorable lightning talks from our community this year:
+
+* [Jonny Saunders](https://github.com/sneakers-the-rat) gave an epic lightning talk that highlighted some of the challenges LLMs pose to the open-source and scientific communities. [This license,](https://github.com/sneakers-the-rat/gpu-free-ai/blob/main/LICENSE) for those who missed it, gives you a flavor of what happened during the talk\!
+* [Yuvi Panda](https://github.com/yuvipanda) delivered a deeply relatable talk on therapy, open source, and why maybe—just maybe—you should choose the former before the latter.
+* [Leah Wasser](https://github.com/lwasser) discussed our pyOpenSci mission to address social and technical pain points in scientific open source and reflected on the role of software peer review in supporting reproducible, high-quality research.
+* [Tetsuo Koyama](https://github.com/tkoyama010) gave a lively demo of [PyVista](https://docs.pyvista.org), a powerful 3D visualization library built on VTK and used by over 2,000 open source projects. Designed as the 3D equivalent of [Matplotlib](https://matplotlib.org/), PyVista makes it easy to create beautiful, interactive 3D visualizations right from Python with no prior VTK knowledge needed.
+
+And of course, we couldn’t wrap up the week without a shoutout to the SciPy Song—a tradition that keeps getting better every year\! This year’s version, crafted by [Naty Clementi](https://github.com/ncclementi), [Juanita Gomez](https://github.com/juanis2112), and [Paige Martin](https://github.com/paigem), even featured a nod to pyOpenSci\!
+
+{{< figure src="images/events/scipy-2025/lightning-talk-song.png" alt="Add alt" >}}
+
+If you missed the conference, talks will be available on YouTube in the coming months—but the *hallway track*, where collaborations begin and friendships form? That’s the part you really have to experience in person. We hope to see you there next year.
+
+## What’s Next?
+
+We’ll be following up on more posts soon, especially on:
+
+* The community feedback we gathered during the BoF
+* Lessons learned from teaching with UV, Hatch, and Pixi
+* Updates to our [packaging template](http://github.com/pyopensci/pyos-package-template) and documentation
+
+### We’re also thrilled to announce a new collaboration:
+
+pyOpenSci is partnering with the [Stanford Open Source Program Office (OSPO)](https://opensource.stanford.edu/) for our first joint event, happening August 7\! This interactive session will explore how software peer review helps researchers build better tools, improve their coding practices, and gain academic recognition.
+
+📅 Learn more: [pyOpenSci x Stanford OSPO Peer Review Event](https://www.pyopensci.org/events/pyopensci-stanford-ospo-peer-review.html)
+{: .btn .btn--primary }
+
+We’ll also be co-hosting a packaging workshop at Stanford later this year, so stay tuned for more details on that!
+
+If you joined us during SciPy this year, thank you. Whether you were sprinting, chatting, teaching, or just soaking it all in, you helped make it special.
+
+If you missed it but want to get involved, check out our [volunteer page](https://www.pyopensci.org/volunteer.html).
+
+Open science moves forward when we build it together, and SciPy 2025 reminded us just how much we can do when we do.
diff --git a/content/blog/2025-08-05-scipy-bof-lessons-learned.md b/content/blog/2025-08-05-scipy-bof-lessons-learned.md
new file mode 100644
index 00000000..8fc6f498
--- /dev/null
+++ b/content/blog/2025-08-05-scipy-bof-lessons-learned.md
@@ -0,0 +1,41 @@
+---
+title: 'Listening, learning, and building together: what we heard at our SciPy 2025
+  BoF'
+date: '2025-08-05'
+type: blog
+excerpt: We held an incredibly informative community session this year at the SciPy
+  meeting in Tacoma Washington. We asked the community what their open source Python
+  pain points were. Learn more about what we learned in this interactive session.
+author: Mandy Moore
+blog_topic: community
+toc: true
+comments: true
+url: "/blog/pyopensci-bof-community-scipy-2025.html"
+lastmod: '2025-08-05'
+image:
+  src: images/headers/pyopensci-scipy-2025.png
+  alt: 'Listening, learning, and building together: what we heard at our SciPy 2025
+    BoF'
+---
+
+{{< figure src="images/blog/2025/scipy-bof/community-discussion-2.png" alt="Attendees from different scientific backgrounds actively participate in a BoF discussion, sharing experiences from across the research software ecosystem." >}}
+
+At [SciPy 2025](https://www.scipy2025.scipy.org/) in July, [pyOpenSci hosted a Birds of a Feather session](https://www.pyopensci.org/events/pyopensci-scipy25-bof-packaging-challenges.html) focused on packaging challenges in research software.
+
+Rather than giving another talk or demo, we created a space to listen. Building on themes from [our earlier blog about the social side of packaging](https://www.pyopensci.org/blog/python-packaging-friends-dont-let-friends-package-alone.html), we invited folks into a Birds of a Feather (BoF) session centered on one big question:
+
+**What are your biggest pain points when it comes to sharing and maintaining research software—and what should pyOpenSci focus on next?**
+
+<div class="notice notice--primary" markdown="1">
+💬 What’s a BoF?
+
+A “Birds of a Feather” (BoF) session is an informal gathering where people with shared interests come together to discuss a topic—no slides, no lectures, just real conversation. At SciPy, our BoF served as a chance to connect, surface ideas, and shape the future of open science together.
+</div>
+
+The goal wasn’t to walk away with a perfect roadmap. It was to get honest input from people across the scientific open source ecosystem, like maintainers, researchers, tool builders, educators, and curious newcomers. We wanted to surface the real-world friction points that often get lost in documentation or conference talks. These aren’t just isolated issues—they’re patterns that affect how research software gets built, shared, cited, and sustained.
+
+And wow, did people show up!
+
+We kicked things off with a few warm-up questions, then broke into small groups for deeper discussion. Each group used [Mentimeter](https://www.mentimeter.com/) to log their thoughts in real time, so we could capture the full range of ideas. Some responses were serious. Others were playful (one response to “What’s hardest about packaging your code?” was simply: “cats” 😹). But across it all, real patterns emerged\!
+
+Here’s what we heard and how it’s shaping where we go from here.
diff --git a/content/blog/2025-08-13-meet-mandy.md b/content/blog/2025-08-13-meet-mandy.md
new file mode 100644
index 00000000..b2c7e567
--- /dev/null
+++ b/content/blog/2025-08-13-meet-mandy.md
@@ -0,0 +1,40 @@
+---
+title: Meet Mandy Moore, pyOpenSci’s new Communications and Community Lead!
+date: '2025-08-13'
+type: blog
+excerpt: Meet Mandy Moore, our new Communications and Community Lead! Mandy is bringing
+  15+ years of experience in marketing, content strategy, and community engagement
+  to help make open science more accessible and welcoming. Learn more about her work
+  and story in this post.
+author: Mandy Moore
+blog_topic: community
+toc: true
+comments: true
+url: "/blog/mandy-moore-communications-lead.html"
+lastmod: '2025-08-12'
+image:
+  src: images/headers/pyopensci-floral.png
+  alt: Meet Mandy Moore, pyOpenSci’s new Communications and Community Lead!
+---
+
+{{< figure src="images/blog/2025/meet-mandy-moore-comms.png" alt="Photo of Mandy Moore wearing a wide-brimmed black hat, sitting indoors with colorful lights in the background. Beside her is the pyOpenSci logo, featuring a stylized flower with circuit-like petals and a snake in the center, on a purple patterned background." >}}
+
+## Meet Mandy Moore, pyOpenSci’s new Communications and Community Lead!
+
+We’re thrilled to introduce **Mandy Moore** as our new **Communications and Community Lead** at [pyOpenSci](https://www.pyopensci.org/)\!
+
+Mandy joins us in a part-time role focused on growing and supporting our community through clear, engaging, and inclusive communication. She’s already helping us shape how we show up across platforms, whether that’s through newsletters, social posts, blogs, or behind-the-scenes strategy. Her work is helping us highlight not just what we do at pyOpenSci, but who we’re doing it for.
+
+Mandy brings more than 15 years of experience in marketing, content strategy, podcast production, and community engagement—primarily in the broader tech world. While she’s newer to both Python and open science, she’s no stranger to translating technical work into accessible, human-centered content. Over the years, she’s worked behind the scenes on developer-focused podcasts, led marketing for startups, and helped open source projects share their impact and grow inclusive, welcoming communities.
+
+At pyOpenSci, Mandy is leading our blog, social media, newsletter, and contributor communications. If you’ve noticed a friendlier voice on LinkedIn or seen our blog posts getting more structured and community-centered, that’s Mandy at work.
+
+In addition to her work with pyOpenSci, Mandy runs a freelance business supporting mission-driven startups, open source projects, and solo founders. Her services span everything from content strategy and social media to podcast production and branding. She’s worked with projects like [Leapter](https://www.leapter.com/), [WPConcierge](https://wpconcierge.com/), and the [Dead Code Podcast](https://deadcode.website), and she’s always up for a good brainstorm about making tech more human and accessible.
+
+Her role supports one of the most essential parts of pyOpenSci’s mission: **making scientific open source more accessible, more visible, and more sustainable**. Through thoughtful content and community engagement, Mandy is helping us break down both technical and social pain points, one story, post, or conversation at a time.
+
+> “I’m not a scientist or a developer,” Mandy says. “But I *am* someone who believes deeply in open science, shared knowledge, and the power of good communication to bring people together. I’m honored to support this community and can’t wait to learn from all of you.”
+
+Mandy lives in **York, Pennsylvania,** with her partner **Keith**, their three kids, and two very good dogs: **Gallagher**, a gentle golden retriever, and **Luna**, a tiny but mighty miniature Yorkshire Terrier. Outside of work, she’s a lifelong writer, recovering perfectionist, and astrology nerd who still gets excited about the magic of a well-written sentence. She’s currently in the middle of planning her November wedding, which means her calendar is full of both GitHub issues *and* flower mockups.
+
+Please join us in giving Mandy a warm welcome! You can connect on LinkedIn to say hi. You can also find her writing at exhotmess.net and learn more about her tech work at mandymoore.tech.
diff --git a/content/blog/2025-08-14-pyopensci-executive-council-rototation.md b/content/blog/2025-08-14-pyopensci-executive-council-rototation.md
new file mode 100644
index 00000000..21107747
--- /dev/null
+++ b/content/blog/2025-08-14-pyopensci-executive-council-rototation.md
@@ -0,0 +1,94 @@
+---
+title: 'Succession is Success: pyOpenSci''s Executive Council Transition Marks Organizational
+  Maturity'
+date: '2025-08-14'
+type: blog
+excerpt: The Executive Council drives pyOpenSci's mission and vision. Learn more about
+  how the council works, and about the current rotation that is happening as our board
+  chair steps down and another member joins us marking a milestone of incredible growth
+  for pyOpenSci.
+author: pyopensci
+blog_topic: community
+toc: true
+comments: true
+url: "/blog/pyopensci-executive-council-transition.html"
+lastmod: '2025-08-05'
+image:
+  src: images/headers/pyopensci-floral.png
+  alt: 'Succession is Success: pyOpenSci''s Executive Council Transition Marks Organizational
+    Maturity'
+---
+
+When an organization successfully navigates its first leadership transition, it's a milestone worth celebrating. It demonstrates that the structures, processes, and culture you've built are strong enough to endure beyond any single individual. We've seen these transitions happening in our [Editorial Board](https://www.pyopensci.org/handbook/governance/structure.html#peer-review-editorial-board) over the past 3 years. Today, we're proud to announce pyOpenSci's first [Executive Council](https://www.pyopensci.org/handbook/governance/executive-council.html#pyopensci-executive-council) transition—a sign of our organization's growth and maturity.
+
+{{< figure src="images/blog/2025/executive-council-rotation-tracy.png" alt="A graphic that says --Tracy Teal has completed a 3 year term as Executive Council Chair. We are grateful for the expertise, time and effort Tracy has put into the strategic vision for pyOpenSci.We also are grateful to Karen Cranston for stepping into the Executive Council chair position. And we welcome April Johnson as our newest Executive Council member!A timeline showing the growth of pyOpenSci from 2019 to 2024. It also has images of 3 women, Tracy, Karen and April on it on the right.' style='width: 80%;" >}}
+
+As founding Executive Council Chair **Tracy Teal** transitions from her leadership role after three transformative years, we're excited to welcome **Karen Cranston** as our new Executive Council Chair and **April Johnson** as a new Executive Council member. This transition represents not just changing leadership, but the successful maturation of pyOpenSci as an organization.
+
+## <i class="fa-solid fa-seedling"></i> From grassroots vision to established organization
+
+pyOpenSci began in 2018 as a passion project born from engagement in the Python, open source community. As a volunteer who deeply cared about scientific open source software, I saw numerous pain points in how the Python scientific community approached software quality and sustainability. We brought together a small group of [like-minded open source leaders](https://www.pyopensci.org/handbook/reference/index.html) to pilot what [peer review of scientific Python software](https://www.pyopensci.org/about-peer-review/index.html) could look like—creating something that didn't exist but was clearly needed.
+
+Five years later, our grassroots effort had evolved into something much larger. In 2022, with Sloan Foundation funding secured, we transitioned to fiscal sponsorship under the 501(c)(3) fiscal host, Community Initiatives, establishing pyOpenSci as an independent, fiscally-sponsored project. This transition marked our transformation from a purely volunteer-driven initiative to a structured organization with [formal governance](https://www.pyopensci.org/handbook/governance/structure.html), funding, and accountability structures.
+
+## <i class="fa-solid fa-sitemap"></i> Building strong governance: The Executive Council's role
+
+The [pyOpenSci Executive Council](https://www.pyopensci.org/handbook/governance/executive-council.html) was founded in 2022 as the cornerstone of our governance structure. The Council provides strategic oversight, organizational guidance, and accountability while serving as ambassadors for our mission and as a support system for our [Executive Director](https://www.pyopensci.org/handbook/governance/structure.html#executive-director). Working alongside our [Advisory Council](https://www.pyopensci.org/handbook/governance/structure.html#advisory-council), which offers domain-specific expertise, this governance structure has been instrumental in our steady growth.
+
+## <i class="fa-solid fa-star"></i> Three years of shared accomplishments
+
+Under Tracy's leadership as our founding Executive Council (EC) Chair, the EC has achieved remarkable milestones over the past three years. Together, we:
+
+* **Established our foundational identity:** Crafted a [powerful mission](https://www.pyopensci.org/handbook/governance/mission-values.html#mission-vision-and-values) while directing the vision and values of our organization that guide our work together.
+* **Built robust governance structures:** Created transparent decision-making processes and accountability mechanisms.
+* **Fostered a healthier and inclusive community:** Implemented a comprehensive [code of conduct](https://www.pyopensci.org/handbook/CODE_OF_CONDUCT.html) with clear procedures that support inclusive community engagement.
+* **Secured sustainable funding:** We have also secured [over $1,000,000 in funding](https://www.pyopensci.org/blog/czi-funds-pyOpenSci-2024.html) while building relationships for future support.
+
+These achievements reflect the successful synergy between Executive Council members who brought diverse expertise in nonprofit management, open source communities, and scientific software development to guide our strategic direction.
+
+## <i class="fa-solid fa-leaf"></i> Celebrating transition: a sign of success
+
+Three years into our journey as an independent organization, this Executive Council transition marks a milestone we're celebrating as a symbol of organizational maturity and success.
+
+Tracy's non profit leadership experience, strategic vision and steady guidance have been foundational to everything we've accomplished—from establishing our governance structures to guiding us through the critical early years of organizational development. As she transitions from her EC Chair role, we're deeply grateful for the strong foundation she's helped build.
+
+**Karen Cranston** will continue to serve on the pyOpenSci leadership team, moving into the role of EC Chair. Karen brings extensive experience in open science, having served in leadership roles at organizations such as [The Carpentries](https://carpentries.org/) and the [Open Bioinformatics Foundation](https://www.open-bio.org/) that bridge community, research and data science. Karen’s deep understanding of both the scientific community and organizational development makes her ideally suited to guide pyOpenSci through our next phase of growth.
+
+We're also thrilled to welcome **April Johnson** to our Executive Council. April brings invaluable expertise as a technology executive and consultant to humanities and civil rights nonprofits, most recently as [People Lead at 2i2c](https://2i2c.org/) and as Board Chair for [He She Ze & We](https://heshezewe.org/). Her experience in organizational development and people-centered leadership will be crucial as we continue to scale our community, work on sustainability, and impact.
+
+## <i class="fa-brands fa-pagelines"></i> What this maturity enables
+
+This successful transition demonstrates that pyOpenSci has evolved into a growing, sustainable organization. Succession is success as it demonstrates that we've built something larger than any individual contributor—with proven governance structures, institutional knowledge, and a thriving community that transcends leadership changes.
+
+As we move forward under Karen and April's guidance, we're excited about our next chapter. This includes a strategic focus on sustainability—thoughtfully considering how we generate revenue as an organization, and ways we can scale that also support long-term sustainability. We're also exploring deeper collaborations with aligned communities like [rOpenSci](https://ropensci.org/), [PREreview](https://prereview.org/), [The Carpentries](https://carpentries.org/), and [Open Life Science](https://openlifesci.org/).
+
+This transition positions us to take on bigger challenges, expand our impact on the scientific Python ecosystem, and continue building the future of open scientific software. We can't wait to see what comes next!
+
+
+<div class="notice" markdown="1">
+
+## Connect with us!
+
+There are lots of ways to get involved if you are interested\!
+
+* If you read through our lessons and want to suggest changes, open an issue in our [lessons repository here](https://github.com/pyOpenSci/lessons).
+* [Volunteer to be a reviewer for pyOpenSci’s software review process](https://docs.google.com/forms/u/6/d/e/1FAIpQLSeVf-L_1-jYeO84OvEE8UemEoCmIiD5ddP_aO8S90vb7srADQ/viewform?usp=send_form).
+* [Submit a scientific Python package to pyOpenSci for peer review.](https://www.pyopensci.org/software-peer-review/how-to/author-guide.html#submit-your-package-for-peer-review)
+* [Donate to pyOpenSci](https://give.communityin.org/pyopensci_2024?ref=ab_0sHhtifYvgR0sHhtifYvgR) to support scholarships for future training events and the development of new learning content.
+* Check out our [volunteer page](https://www.pyopensci.org/volunteer.html) for other ways to get involved.
+
+You can also:
+
+* Keep an eye on our [events page](https://www.pyopensci.org/events/) for upcoming training events.
+
+Follow us on social platforms:
+
+
+* [Mastodon](https://fosstodon.org/@pyopensci)
+* [Bluesky](https://bsky.app/profile/pyopensci.org)
+* [LinkedIn](https://www.linkedin.com/company/pyopensci/)
+* [GitHub](https://github.com/pyOpenSci)
+
+If you are on LinkedIn, check out and [subscribe to our newsletter](https://www.linkedin.com/newsletters/7179551305344933888/?displayConfirmation=true), too.
+
+</div>
diff --git a/content/blog/2025-09-11-pyopensci-september-news-2025.md b/content/blog/2025-09-11-pyopensci-september-news-2025.md
new file mode 100644
index 00000000..fc293756
--- /dev/null
+++ b/content/blog/2025-09-11-pyopensci-september-news-2025.md
@@ -0,0 +1,22 @@
+---
+title: 'What’s New in pyOpenSci: September Updates + Community Shoutouts'
+date: '2025-09-11'
+type: blog
+excerpt: This summer brought incredible momentum to pyOpenSci—from 60+ attendees at
+  our SciPy session to 13 packages actively under review and exciting new leadership
+  transitions. Join our November Python packaging workshop or explore how you can
+  get involved in peer review.
+author: pyopensci
+blog_topic: updates
+toc: true
+comments: true
+url: "/blog/pyopensci-september-2025-updates.html"
+lastmod: '2025-09-11'
+image:
+  src: images/headers/pyopensci-floral.png
+  alt: 'What’s New in pyOpenSci: September Updates + Community Shoutouts'
+---
+
+The summer was full of connection, collaboration, and momentum in the pyOpenSci community. Whether you joined us at SciPy, submitted a package for review, or just lurked, we’re so grateful you’re here!
+
+Here’s what’s been happening 👇
diff --git a/content/blog/2025-09-14-pyopensci-surviving-to-thriving.md b/content/blog/2025-09-14-pyopensci-surviving-to-thriving.md
new file mode 100644
index 00000000..f31cf7d4
--- /dev/null
+++ b/content/blog/2025-09-14-pyopensci-surviving-to-thriving.md
@@ -0,0 +1,93 @@
+---
+title: 'From Surviving to Thriving: A Convening to Reclaim and Sustain Open Science
+  Communities'
+date: '2025-09-14'
+type: blog
+excerpt: Building resilience in open science starts with collaboration. Learn how
+  pyOpenSci is partnering with the Carpentries, Prereview, Open Life Sciences, and
+  rOpenSci to reinvision how open communities can work together to share the future
+  of open science in uncertain times.
+author: pyopensci
+blog_topic: community
+toc: true
+comments: true
+url: "/blog/pyopensci-surviving-to-thriving.html"
+lastmod: '2025-09-09'
+image:
+  src: images/headers/pyopensci-floral.png
+  alt: 'From Surviving to Thriving: A Convening to Reclaim and Sustain Open Science
+    Communities'
+---
+
+*Authors: Kari L. Jordan, Erin Becker, Daniela Saderi, Vanessa Fairhurst, Patricia Herterich, Noam Ross, Yanina Bellini Saibene, Leah Wasser, Yo Yehudi*
+
+{{< figure src="images/blog/2025/waterfall-flikr.jpg" alt="A photograph of a waterfall cascading down rocks in a rich green forest setting' style='width: 80%;" caption="'Black Forest: waterfall' by *rboed* is licensed under CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/?ref=openverse." >}}
+
+
+
+Open science has transformed how research is conducted, shared, and reused. Yet the organisations at the heart of this transformation are often left vulnerable, underfunded, and disconnected from one another. To move from simply surviving to truly thriving, five leading open science organisations \-- [The Carpentries](https://carpentries.org/), [OLS](https://we-are-ols.org/), [rOpenSci](https://ropensci.org/), [pyOpenSci](https://www.pyopensci.org/), and [PREreview](https://prereview.org/)) \-- are convening to chart a collective path forward. We are so grateful to The Navigation Fund for supporting this work, and invite our communities to review the [full proposal](https://commons.datacite.org/doi.org/10.71707/qttn-3j47) online.
+
+## Why This Convening Matters
+
+Our work has reshaped scientific culture by modeling inclusive, participatory, and transparent practices. But despite the global reach and impact of our communities, we face shared challenges:
+
+* Chronic underfunding that undermines our ability to plan and grow.
+* Fragmentation across networks, which weakens collective visibility and coordination.
+* Unsustainable engagement models that over-rely on volunteers without adequate support systems.
+
+Like a single thread, each of our organisations is fragile alone; together, we can weave a stronger, more resilient open science fabric.
+
+## Current Gaps
+
+Open science is built on collaboration and transparency, but too often the organisations building this infrastructure operate in silos. The result is uneven visibility, duplicated efforts, and missed opportunities to align strategies. Community-driven organisations like ours face distinct challenges compared with technical infrastructure projects: recruiting contributors is not enough if the structures and motivation to sustain their engagement are missing.
+
+This fragmentation is not just an internal problem; it’s a loss for the broader research ecosystem that depends on our work.
+
+## Our Approach
+
+We are planning a strategic, in-person convening of leadership from our five organisations. This gathering will focus on:
+
+* Shared financial sustainability: Developing collective, value-aligned models for funding and resource generation.
+* Collaborative engagement strategies: Designing systems that strengthen and connect our communities across roles, regions, and lived experiences.
+* Equity-centered design: Ensuring accessibility, usability, and meaningful participation for all involved.
+
+Facilitated by [Wildly Open](https://wildlyopen.com/), we are excited to explore and better understand what is (and isn’t) working, and then build durable models for collaboration and sustainability.
+
+## What We Aim to Deliver
+
+* A coordinated sustainability strategy that reflects the shared values of our organisations.
+* A funder-facing pitch to mobilise resources in support of this strategy.
+* Stronger ties among our organisations that extend beyond the convening, creating lasting impact.
+
+## The Bigger Picture
+
+This convening is not an isolated event. It’s the first step in scaling a movement that reimagines how values-driven open science organisations can grow together, share resources, and strengthen the ecosystem we collectively serve. By working together, we can ensure that the future of open science is not only innovative, but also equitable, sustainable, and resilient.
+
+
+<div class="notice" markdown="1">
+
+## Connect with us!
+
+There are lots of ways to get involved if you are interested!
+
+* If you read through our lessons and want to suggest changes, open an issue in our [lessons repository here](https://github.com/pyOpenSci/lessons).
+* [Volunteer to be a reviewer for pyOpenSci’s software review process](https://docs.google.com/forms/u/6/d/e/1FAIpQLSeVf-L_1-jYeO84OvEE8UemEoCmIiD5ddP_aO8S90vb7srADQ/viewform?usp=send_form).
+* [Submit a scientific Python package to pyOpenSci for peer review.](https://www.pyopensci.org/software-peer-review/how-to/author-guide.html#submit-your-package-for-peer-review)
+* [Donate to pyOpenSci](https://give.communityin.org/pyopensci_2024?ref=ab_0sHhtifYvgR0sHhtifYvgR) to support scholarships for future training events and the development of new learning content.
+* Check out our [volunteer page](https://www.pyopensci.org/volunteer.html) for other ways to get involved.
+
+You can also:
+
+* Keep an eye on our [events page](https://www.pyopensci.org/events/) for upcoming training events.
+
+Follow us on social platforms:
+
+
+* [Mastodon](https://fosstodon.org/@pyopensci)
+* [Bluesky](https://bsky.app/profile/pyopensci.org)
+* [LinkedIn](https://www.linkedin.com/company/pyopensci/)
+* [GitHub](https://github.com/pyOpenSci)
+
+If you are on LinkedIn, check out and [subscribe to our newsletter](https://www.linkedin.com/newsletters/7179551305344933888/?displayConfirmation=true), too.
+
+</div>
diff --git a/content/blog/2025-10-02-why-we-choose-what-we-choose.md b/content/blog/2025-10-02-why-we-choose-what-we-choose.md
new file mode 100644
index 00000000..e4a3d35d
--- /dev/null
+++ b/content/blog/2025-10-02-why-we-choose-what-we-choose.md
@@ -0,0 +1,65 @@
+---
+title: Why We Choose What We Choose
+date: '2025-10-02'
+type: blog
+excerpt: In selecting one workflow to package a Python project, pyOpenSci chooses
+  between a lot of code tools. These choices often come after months of exploration
+  and debate. Find out what motivates us to make the decisions that we do.
+author: Jeremiah Paige
+blog_topic: community
+toc: true
+comments: true
+url: "/blog/how-we-choose-python-tools.html"
+lastmod: '2025-10-02'
+image:
+  src: images/headers/pyopensci-floral.png
+  alt: Why We Choose What We Choose
+---
+
+A primary focus at pyOpenSci, one of our petals of support, is selecting packaging tools that work well for our users and work well together. We use our curated selection of tooling in our packaging guide, in our online tutorials, and in our trainings. We don’t require the use of any of our selected tools to submit a package to our peer review program but we will suggest them if the package authors ask for help trying to clean up or adopt new workflows.
+
+The members of pyOpenSci spend a great deal of time selecting these tools, debating tradeoffs, test-driving them in new situations, looking at new community trends, and listening to feedback from events we run. But up until now we haven't typically posted in the open either how or why we have come to the decisions we did. This post outlines, in not very strict terms, the rubric we use when selecting a project that we want to recommend. We focus on a beginner-leaning happy path for packaging workflows. In other words, what works really well for new projects that don't have a lot, if any, non-conventional requirements to share their code.
+
+Our rubric comes from five categories, approximately ordered as follows:
+
+## Tools that are free and open
+
+We love open software! It's even in our name. We are always looking to nurture and support open source software, even beyond packaging projects. It should come as no surprise, then, that we only choose tools in our packaging guide that are themselves open source.
+
+We don’t just appreciate open source, though, we also look for projects that are open contribution – that do most of their maintenance, stewardship, and designing in public. This means there is a public bug tracker where new issues are accepted from anyone, and fixes for those bugs are also accepted from non-maintainers. It may also mean that new feature ideas are accepted from the community, or even given a period of public comment. Contributions from everyone, including members and non-members, should be respected as the exchange of free ideas. Project authors should not seek to take exclusive ownership of the collaborative efforts of the community they are a part of. This means that contributors of any level and for any purpose of the project should be recognized publicly. It also means that the project is not asking for the exclusive rights to those contributors' ideas (through overly restrictive Contributor License Agreements).
+
+Our commitment to open software goes beyond just projects that choose to host their code and bugs in a public manner. We also value Free Software; both as in Beer and as in Freedom. Permissive open source software empowers its users to take control of their tools and fix, extend, secure, and adapt code for the purposes that will best fit their own needs. Choosing projects that do not require a financial exchange in order to be used ensures that we can recommend our choices to anyone no matter their situation or location.
+
+## Tools that are inclusive
+
+Inclusivity is very important to us; it is a critical component of tooling projects we select. Programming, including packaging of that software, is a skill that should be available to everyone.
+
+The tools we advocate for should not seek to limit their use through actions such as: adoption of a restrictive license; poor, missing, obfuscated, or expert-only documentation; charging for use of the tool or any process related to its successful usage; not supporting mainstream operating systems. The projects behind the tools should welcome constructive bug reports from users of all levels, and ideally also welcome contributions from all their users.
+
+There are some signals that we look for to tell if the project is inclusive. We want all of our recommended tools to have a code of conduct for their project. The project should also have a contributors guide that is easy to find. Labeling issues or running sprints aimed at fostering commits from new contributors is also a great indicator.
+
+Projects that manage to attract and maintain a broad base of contributors will be viewed more positively. We value projects that strive to do this not only in code, but also in documentation, engagement with the bug tracker, external write-ups and tutorials, and so forth.
+
+## Tools that implement open standards
+
+It is very important to us that the tools and processes we stand behind support the full set of community standards.
+
+For Python, this typically means conforming to [Python Enhancement Proposals](https://peps.python.org), but may also involve other standard bodies such as [Scientific Python Ecosystem Coordination](https://scientific-python.org/specs/).
+
+Supporting community standards demonstrates that the project respects the community it is working within and is serious about interoperability with other tools and processes. When done right, these tools empower their users to move this workflow, or any of its inputs or outputs, to another standards-compliant tool or process with little to no friction. It also makes it easier to teach since many of the concepts, as well as in some cases entire parts of project data, are tool-agnostic and can feel "familiar" even to those that have never used the tool before. There is also likely to be more documentation developed through forums, blogs, workshops, and other online platforms, because they apply to more than one tool.
+
+It can be a lot of work for tool maintainers to keep up-to-date with changes in standardization, especially in a large and eclectic community such as Python. While we understand that it can take time to implement new features imposed from outside of a project, we also know that a selectively-implemented standard is often worse than no standard.
+
+## Tools that are well supported
+
+We would like to only recommend projects that we can confidently say are healthy, correct, and here to stay. A well-maintained project is a somewhat subjective metric that is hard to pin down, but whenever possible we would apply our [same standard](https://www.pyopensci.org/software-peer-review/how-to/author-guide.html#does-your-package-meet-packaging-requirements) for Peer Reviews of Scientific Software.
+
+Authors and maintainers should respond to open issues and continue to make fixes to the project. We do not have any expectation or metric of response time, open bug count, time to close commit requests, security artifacts, or any other level of effort requirement; only that the project is alive and healthy to the degree that is appropriate for its function. We also strongly prefer projects that have a team of core maintainers as opposed to an individual maintainer.
+
+## Tools that reduce user choices
+
+Python packaging suffers, perhaps infamously, from [Too Many Options](https://www.pyopensci.org/blog/python-packaging-friends-dont-let-friends-package-alone.html#just-say-no-to-tmo). We would like to make as many pragmatic choices as we can on behalf of the learner. Better yet is to make choices that will eliminate further choices and complexity later on in the process; this can help learners from getting stuck in runaway analysis paralysis.
+
+This means that these tools should implement sensible defaults for any configurable value. Like with Python, they should make the simple easy and the difficult possible.
+
+It also means that we will generally select one tool when two or more could do the same job. So long as the one tool fits our other criteria it doesn't have to "win" at every single task it is capable of doing when compared against a plethora of other tools.
diff --git a/content/blog/2025-11-18-generative-ai-peer-review.md b/content/blog/2025-11-18-generative-ai-peer-review.md
new file mode 100644
index 00000000..fe51b829
--- /dev/null
+++ b/content/blog/2025-11-18-generative-ai-peer-review.md
@@ -0,0 +1,289 @@
+---
+title: 'Navigating LLMs in Open Source: pyOpenSci''s New Peer Review Policy'
+date: '2025-11-18'
+type: blog
+excerpt: Generative AI products are reducing the effort and skill necessary to generate
+  large amounts of code. In some cases, this strains volunteer peer review programs
+  like ours. Learn about pyOpenSci's approach to developing a Generative AI policy
+  for our software peer review program.
+author: pyopensci
+blog_topic: software
+toc: true
+comments: true
+url: "/blog/generative-ai-peer-review-policy.html"
+lastmod: '2025-12-16'
+image:
+  src: images/headers/pyopensci-floral.png
+  alt: 'Navigating LLMs in Open Source: pyOpenSci''s New Peer Review Policy'
+---
+
+authors: Leah Wasser, Jed Brown, Carter Rhea, Ellie Abrahams, Carol Willing, Stefan van der Walt, Eliot Robson
+
+## Generative AI meets scientific open source
+
+Some developers believe that using Generative AI products increases
+efficiency. However, in scientific open source, speed isn't
+everything—transparency, quality, and community trust are just as
+important as understanding the environmental impacts of using large
+language models in our everyday work. Similarly, ethical questions
+arise when tools may benefit some communities while harming others.
+
+## Why we need guidelines
+
+At pyOpenSci, [we’ve drafted a new policy](https://github.com/pyOpenSci/software-peer-review/pull/344) for our peer review process to set clear expectations for disclosing the use of LLMs in scientific open-source software.
+
+Our goal is transparency and fostering reproducible research. For scientific rigor, we want maintainers to **disclose when and how they’ve used LLMs** so editors and reviewers can fairly and efficiently evaluate submissions. Further, we want to avoid burdening our volunteer editorial and reviewer team with being the initial reviewers of generated code.
+
+This is the beginning of our work to ensure that Gen AI tools are not
+creating undue burden on our volunteer software review team. Humans
+cannot perform in depth reviews at the rate at which these tools can
+create large volumes of code.
+
+## A complex topic: benefits and concerns
+
+LLMs are perceived as helping developers:
+
+* Explain complex codebases
+* Generate unit tests and docstrings
+* Simplify language barriers for participants in open source around
+  the world
+* Speed up everyday workflows
+
+Some contributors perceive these products as making open source more
+accessible. And for some, maybe they do. However, LLMs also present
+unprecedented social and environmental challenges that we have to
+critically evaluate.
+
+### Incorrectness of LLMs and misleading time benefits
+
+Although it is commonly stated that LLMs help improve the productivity
+of high-level developers, recent scientific explorations of this
+hypothesis [indicate the
+contrary](https://metr.org/blog/2025-07-10-early-2025-ai-experienced-os-dev-study/).
+What's more is that the responses of LLMs for complex coding tasks
+[tend to be
+incorrect](https://arxiv.org/html/2407.06153v1) and/or overly
+verbose/inefficient. It is crucial that, if you use an LLM to help
+produce code, you should independently evaluate code correctness and
+efficiency.
+
+### Environmental impacts
+
+Training and running LLMs [requires massive energy
+consumption](https://www.unep.org/news-and-stories/story/ai-has-environmental-problem-heres-what-world-can-do-about),
+raising sustainability concerns that sit uncomfortably alongside much
+of the global-scale scientific research that our community supports.
+
+### Impact on learning
+
+Heavy reliance on LLMs risks producing developers who can prompt, but
+not debug, maintain, or secure production code. This risk undermines
+long-term project sustainability and growth. In the long run, it will
+make it [harder for young developers to learn how to code and
+troubleshoot
+independently](https://knowledge.wharton.upenn.edu/article/without-guardrails-generative-ai-can-harm-education/).
+
+> We’re really worried that if humans don’t learn, if they start using these tools as a crutch and rely on it, then they won’t actually build those fundamental skills to be able to use these tools effectively in the future. _Hamsa Bastani_
+
+### Ethics and inclusion
+
+LLM outputs can reflect and amplify bias in training data. In
+documentation and tutorials, that bias can harm the very communities
+we want to support.
+
+## Our approach: transparency and disclosure
+
+We acknowledge that social and ethical norms, as well as concerns
+about environmental and societal impacts, vary widely across the
+community. We are not here to judge anyone who uses or doesn't use
+LLMs. Our focus centers on supporting informed decision-making and
+consent regarding LLM use in the pyOpenSci software submission,
+review, and editorial process.
+
+Our community’s expectation for maintainers submitting a package is simple: **be open and disclose any Generative AI use in your package** when you submit it to our open software review process.
+
+* Disclose LLM use in your README and at the top of relevant modules.
+* Describe how the Generative AI tools were used in your package's development.
+* Be clear about what human review you performed on Generative AI
+  outputs before submitting the package to our open peer review
+  process.
+
+Transparency helps reviewers understand context, trace decisions, and
+focus their time where it matters most. We do not want the burden of
+reviewing code generated from a model, placed on a volunteer. That
+effort belongs to the maintainer who ran the model that generated that
+code.
+
+### Human oversight
+
+LLM-assisted code must be **reviewed, edited, and tested by humans**
+before submission.
+
+* Run your tests and confirm the correctness of the code that you submitted.
+* Check for security and quality issues.
+* Ensure style, readability, and concise docstrings. Depending on the
+  AI tool, generated docstrings can sometimes be overly verbose without
+  adding meaningful understanding.
+* Explain your review process in your software submission to pyOpenSci.
+
+Please **don't offload vetting of generative AI content to volunteer
+reviewers**. Arrive with human-reviewed code that you understand,
+have tested, and can maintain. As the submitter, you are accountable
+for your submission: you take responsibility for the quality,
+correctness, and provenance of all code in your package, regardless of
+how it was generated.
+
+### Watch out for licensing issues.
+
+LLMs are trained on large amounts of open source code, and most of
+that code has licenses that require attribution (including permissive
+licenses like MIT and BSD-3). The problem? LLMs sometimes produce
+near-exact copies of that training data, but without any attribution
+or copyright notices. **LLM output does not comply with the license
+requirements of the input code, even when the input is permissively
+licensed**, because it fails to provide the required attribution.
+
+Not all code carries the same licensing risk. The risk varies
+depending on what you're generating.
+
+Risk of license infringement is **lower for routine tasks** like
+refactoring existing code, test suite improvements, creating
+boilerplate code, simple utility functions, and docstring generation.
+These tasks are more common, often use widely documented patterns,
+and are not as likely to be substantially similar to copyrighted
+training data.
+
+Tasks that are **higher risk** include:
+
+* Algorithm implementations
+* Developing workflows for complex data structures
+* Domain-specific logic that is potentially already published or
+  copyrighted
+
+For high-risk content (e.g., algorithm implementations), you need to
+understand the algorithm to vet its correctness, ensure the approach
+is not already published and copyrighted, vet its performance, and
+evaluate edge cases. If you understand it well enough to review it
+thoroughly, you can often implement it yourself. In these cases, use
+LLMs as learning aids—ask questions, study approaches, then write
+your own implementation.
+
+Why this matters:
+
+* LLM-generated code may be _substantially similar_ to copyrighted
+  training data; sometimes it is identical. Copyright law focuses on
+  how similar your content is compared to the original.
+* You can't trace what content the LLM learned from (the black box
+  problem); this makes due diligence impossible on your part. You
+  might accidentally commit plagiarism or copyright infringement by
+  using LLM output in your code even if you modify it.
+* License conflicts occur because of both items above. Read on...
+
+When licenses clash, it gets particularly messy. Even when licenses
+are compatible (e.g., MIT-licensed training data and MIT-licensed
+output), you still have a violation because attribution is missing.
+With incompatible licenses (say, an LLM outputs GPL code and your
+package uses MIT), you can't just add attribution to fix it—you'd
+technically have to delete everything and rewrite it from scratch
+using clean-room methods to comply with licensing requirements.
+
+The reality of all of this is that you can't eliminate this risk of
+license infringement or plagiarism with current LLM technology. But
+you can be more thoughtful about how you use the technology.
+
+### What you can do now
+
+Consider the following:
+
+* Assess the licensing risk based on what you're generating: routine
+  refactoring carries lower risk than implementing novel algorithms or
+  domain-specific logic.
+* Be aware that when you directly use content from an LLM, there will
+  be inherent license conflicts and attribution issues.
+* **Use LLMs as learning tools**: Ask questions, review outputs
+  critically, then write your own implementation based on
+  understanding. Often the outputs of LLMs are messy or inefficient.
+  Use them to learn, not to copy. This is especially important for
+  high-risk content like algorithms.
+* Understand and transform code returned from an LLM: Don't paste LLM
+  outputs directly. Review, edit, and ensure you fully understand what
+  you're using. You can ask the LLM questions to better understand its
+  outputs. This approach also helps you learn, which addresses the
+  education concerns that we raised earlier.
+* Consider [clean-room
+  techniques](https://en.wikipedia.org/wiki/Clean-room_design): Have
+  one person review LLM suggestions for approach; have another person
+  implement from that high-level description.
+* **Document your process**: If you plan to submit a Python package
+  for pyOpenSci review, we will ask you about your use of LLMs in your
+  work. Document the use of LLMs in your project's README file and in
+  any modules where LLM outputs have been applied. Confirm that it has
+  been reviewed by a human prior to submitting it to us, or any other
+  volunteer-led peer review process.
+
+You can't control what's in training data, but you can be thoughtful
+about how you use these tools.
+
+<div class="notice" markdown="1">
+Examples of how these licensing issues are impacting and stressing our
+legal systems:
+
+* [GitHub Copilot litigation](https://githubcopilotlitigation.com/case-updates.html)
+* [Litigation around text from LLMs](https://arxiv.org/abs/2505.12546)
+* [incompatible licenses](https://dwheeler.com/essays/floss-license-slide.html)
+</div>
+
+### Review for bias
+
+Inclusion is part of quality. Treat AI-generated text with the same
+care as code.
+Given the known biases that can manifest in Generative AI-derived text:
+
+* Review AI-generated text for stereotypes or exclusionary language.
+* Prefer plain, inclusive language.
+* Invite feedback and review from diverse contributors.
+
+## Things to consider in your development workflows
+
+If you are a maintainer or a contributor, some of the above can apply
+to your development and contribution process, too. Similar to how
+peer review systems are being taxed, rapid, AI-assisted pull requests
+and issues can also overwhelm maintainers too. To combat this:
+
+* If you are using generative AI tools in your daily workflows, keep each task small, focused, and well-defined. This is particularly important if you are using agent mode. This will produce smaller changes to your codebase that
+will be easier to thoughtfully review and evaluate.
+* Open an issue first before submitting a pull request to a repository that you don't own to ensure it's
+  welcome and needed
+* Keep your pull requests small with clear scopes.
+* If you use LLMs, test and edit all of the output before you submit a
+  pull request or issue.
+* Flag AI-assisted sections of any contribution so maintainers know
+  where to look closely.
+* Be responsive to feedback from maintainers, especially when
+  submitting code that is AI-generated.
+
+## Where we go from here
+
+A lot of thought and consideration has gone into the development of
+[pyOpenSci's Generative AI
+policies](https://www.pyopensci.org/software-peer-review/our-process/policies.html#policy-for-use-of-generative-ai-llms).
+
+We will continue to suggest best practices for embracing modern
+technologies while critically evaluating their realities and the
+impacts they have on our ecosystem. These guidelines help us maintain
+the quality and integrity of packages in our peer review process while
+protecting the volunteer community that makes open peer review
+possible. As AI tools evolve, so will our approach—but transparency,
+human oversight, and community trust will always remain at the center
+of our work.
+
+## Join the conversation
+
+This policy is just the beginning. As AI continues to evolve, so will
+our practices. We invite you to:
+
+👉 [Read the full draft policy and discussion](https://github.com/pyOpenSci/software-peer-review/pull/344)
+👉 Share your feedback and help us shape how the scientific Python
+  community approaches Generative AI in open source.
+
+The conversation is only starting, and your voice matters.
diff --git a/content/blog/2026-01-12-cynetdiff.md b/content/blog/2026-01-12-cynetdiff.md
new file mode 100644
index 00000000..555f5d8f
--- /dev/null
+++ b/content/blog/2026-01-12-cynetdiff.md
@@ -0,0 +1,23 @@
+---
+title: 'CyNetDiff: A Python Library for Accelerated Implementation of Network Diffusion
+  Models'
+date: '2026-01-12'
+type: blog
+excerpt: CyNetDiff is a Python package for accelerating network diffusion simulations,
+  recently accepted into the pyOpenSci ecosystem.
+author: Eliot W. Robson
+blog_topic: software
+comments: true
+url: "/blog/cynetdiff.html"
+lastmod: '2026-01-12'
+image:
+  src: images/headers/pyopensci-floral.png
+  alt: 'CyNetDiff: A Python Library for Accelerated Implementation of Network Diffusion
+    Models'
+---
+
+Network diffusion models study how information and epidemics spread over social networks, and have garnered increasing interest in recent years. Two of the most widely used models are the **independent cascade (IC)** and **linear threshold (LT) models**. These models simulate spread through a network by starting with a set of seed nodes that are designated as "active", and all other nodes are "inactive". Then, in each iteration, some inactive nodes become active, and the iterations continue until no other nodes can be activated.
+
+Many tasks related to these models, particularly influence maximization, require running simulations on large graphs many times, which can be computationally expensive. There has been significant prior work on reducing the number of simulations needed for these tasks, demonstrating the importance of an efficient implementation.
+
+While researchers often prefer high-level languages like Python for their flexibility and quick development, these computationally intensive tasks are better suited for low-level, compiled languages. To bridge this gap, we've developed **CyNetDiff**, a Python library that uses components written in Cython to provide the performance of a compiled language with the flexibility of a high-level language.
diff --git a/content/blog/2026-01-22-building-resilience-2026.md b/content/blog/2026-01-22-building-resilience-2026.md
new file mode 100644
index 00000000..27f9f30e
--- /dev/null
+++ b/content/blog/2026-01-22-building-resilience-2026.md
@@ -0,0 +1,151 @@
+---
+title: 'Building Resilience: pyOpenSci in 2026'
+date: '2026-01-22'
+type: blog
+excerpt: pyOpenSci learned a lot about resilience in 2025. As we navigate generative
+  AIs impact on scientific open source and shifting funding landscapes, pyOpenSci
+  is building resilience through training, sponsorship, and community-centered leadership.
+  Learn more about our plan.
+author: pyopensci
+blog_topic: community
+toc: true
+comments: true
+url: "/blog/2026-building-resilience-together.html"
+lastmod: '2026-01-22'
+image:
+  src: images/headers/pyopensci-floral.png
+  alt: 'Building Resilience: pyOpenSci in 2026'
+---
+
+## The world has changed
+
+I'm not going to sugarcoat it—2025 was hard.
+
+Watching organizations like the [Python Software Foundation turn down million-dollar National Science Foundation (NSF) grants](https://pyfound.blogspot.com/2025/10/NSF-funding-statement.html)
+because DEIA work was no longer supported made something painfully clear: the funding landscape that has grounded so many of us is no longer reliable.
+
+At the same time, Generative AI fundamentally changed how open source work happens. Maintainers found themselves reviewing more code than ever—much of it machine-generated—while navigating ethical questions about authorship and responsibility they didn't sign up to solve on their own.
+
+For many of us, the ground felt unstable—not just months out, but sometimes day to day.
+
+And yet, something important happened.
+
+Instead of pulling back, **the pyOpenSci community leaned in**. People showed up
+for each other. They reviewed, mentored, taught, organized, and adapted—often
+quietly, often while navigating uncertainty of their own.
+
+{{< figure src="images/blog/2025/pyos-sprint-group.png" alt="pyOpenSci community members working together" caption="The pyOpenSci community showing up for each other. SciPy 2025 beginner-friendly sprint." >}}
+
+## The moment that changed everything
+
+One moment from 2025 keeps coming back to me: our sprint at SciPy.
+
+We had record attendance at that sprint compared to previous years! The large group self-organized. Tables moved. Whiteboards filled with ad-hoc lessons
+on Git and GitHub. Experienced contributors mentored newcomers.
+
+I think about the colleague who sat down, saw the size of the sprint group,
+and asked—"how can I help?". He spent the day working with other sprinters,
+helping them make their first contributions to open source.
+
+This is one example of how baking structure and strong value systems into a community can yield incredible returns. The **community members show up for each other because that is just how pyOpenSci operates**. It's who we are, and it's magical.
+
+{{< figure src="images/blog/2025/tracey-james-scipy-2025.png" alt="Tracey and James at the SciPy 2025 sprint" caption="Tracey and James at the SciPy 2025 sprint, where community members came together to support each other and make their first contributions to open source." >}}
+
+
+>Community members show up for each other because that is how pyOpenSci operates. It's who we are and it's magical.
+{: .highlight-quote .magenta }
+
+
+{{< figure src="images/blog/2025/bof-group-inessa.png" alt="SciPy 2025 sprint participants working in small groups" caption="SciPy 2025 community session participants discussing challenges in scientific Open Source." >}}
+
+
+That day felt like the manifestation of a blueprint. It showed what happens when you create the
+right environment and empower a community to help each other. That model—
+shared ownership, peer learning, mutual support—changed how I think about
+building sustainable infrastructure and community.
+
+Resilience is about building inclusive spaces for people to both engage, learn, and support each other.
+
+## What we're building in 2026
+
+### Shifting how we think about sustainability
+
+One of the clearest lessons from 2025 is that a grant-dependent model alone
+can't support the community-centered infrastructure pyOpenSci is
+building. Grants will always matter, but they can't be the only pillar
+holding us up.
+
+As we move into 2026, pyOpenSci is shifting toward a more
+diversified sustainability plan--one that centers on training, sponsorship, and
+community support. And as always, our focus will remain on human-centered growth and development, which is particularly critical in our current moment of Generative AI-driven rapid change.
+
+Value-alignment will continue to be critical as we make this shift.
+
+### Training that connects people and builds responsible practice
+
+In 2026, we're investing in a new type of training: programs that bring
+researchers from around the world together to learn both software development
+best practices *and* the responsible use of Generative AI in scientific and
+open source workflows. The training will be held asynchronously to reduce barriers
+to participation and increase accessibility. And it will feature incredible leaders in the open source community in an effort to connect learners to the **real heart of Open Source--people**.
+
+
+We’re piloting this new training format through our [partnership with
+Stanford's Open Source Program Office (OSPO)](https://www.pyopensci.org/events/pyopensci-stanford-create-python-package-workshop.html). Building on the momentum, we’ll expand this model to other university OSPOs, leveraging the strong connections within the CURIOSS network and building an organizational membership program that supports researchers at scale. While our courses will initially be designed for OSPO researchers they will be valuable to anyone looking to develop the open source and responsible us of Generative
+AI skills that are in high demand in today's tech-driven job market.
+
+Generative AI can support open source workflows, but it can't fully replace
+the thought, design, and vision that only a human can implement. It also can't replace
+mentorship, care, and compassion—human parts of the tech world that both fuel the
+open source ecosystem and are also straining the fragile social web that supports it. Our training will continue to emphasize foundational open source skills, critical thinking and shared open source norms and workflows.
+
+Our goal is to create learning spaces that reduce isolation, build
+confidence, connect learners to the humans that drive open source, and strengthen the
+communities behind scientific software.
+
+{{< figure src="images/blog/2025/scipy-workshop-teaching.png" alt="Teaching a pyOpenSci workshop at SciPy 2025" caption="Teaching a pyOpenSci workshop at SciPy 2025, focused on Python packaging and open source best practices." >}}
+
+## The people who make this possible
+
+None of what we learned in 2025—or what we're building toward in 2026—
+happened in isolation.
+
+I'm deeply grateful to our 2025 Executive Council, **[Karen Cranston](https://github.com/kcranston)
+and [April Johnson](https://github.com/aprilmj)**, for their steady guidance
+and support as we navigated a challenging year. They encouraged me to embrace
+sustainable leadership and supported me as I developed new programs to ensure
+our long-term sustainability.
+
+Our Editors-in-Chief—**[James Balamuta](https://github.com/coatless),
+[Eliot Robson](https://github.com/eliotwrobson), and [Lauren Yee](https://github.com/yeelauren)**—
+led the peer review process through a period of rapid change, navigating
+AI-fueled submissions while keeping quality and care at the center.
+**[Carter Rhea](https://github.com/crhea93)** stepped up as an editor
+numerous times, supporting volunteers who were overburdened and leading one
+of our largest reviews—Astropy—which was just accepted in early 2026.
+
+{{< figure src="images/blog/2025/maintainers-summit-dan.png" alt="PyCon US 2025 Maintainers Summit" caption="PyCon US 2025 Maintainers Summit, where we created space for those who keep scientific Python running." >}}
+
+Members of our Advisory Council—**[Carol Willing](https://github.com/willingc),
+[Inessa Pawson](https://github.com/InessaPawson), and [Chase Million](https://github.com/cmillion)**—
+helped me think through sustainability, partnerships, and long-term direction
+with wisdom and generosity.
+
+{{< figure src="images/blog/2025/carol-willing-micromentor.png" alt="Carol Willing presenting on micromentoring" caption="Carol Willing from our Advisory Council presenting on micromentoring at the Maintainers Summit, co-organized by pyOpenSci at PYCON US 2025." >}}
+
+**And to the many community members who contributed through reviews, workshops,
+sprints, writing, mentoring, and quiet acts of support—thank you. This
+organization exists because you choose to show up.**
+
+## Community matters most
+
+When things are uncertain, community infrastructure matters most.
+It's how people find support that institutions can't provide. It's how
+knowledge gets shared when traditional collaboration pathways break down.
+It's how we take care of each other.
+
+That SciPy sprint showed me what's possible. When you create spaces where
+people can show up, learn together, and support each other—when you do that
+consistently—the community becomes the infrastructure.
+
+This is how we build resilience. This is how we help make the world better. **Together.**
diff --git a/content/blog/2026-05-01-clean-hugo-blog-theme-features.md b/content/blog/2026-05-01-clean-hugo-blog-theme-features.md
new file mode 100644
index 00000000..56c34a6f
--- /dev/null
+++ b/content/blog/2026-05-01-clean-hugo-blog-theme-features.md
@@ -0,0 +1,604 @@
+---
+title: 'clean-hugo theme: blog formatting and shortcode reference'
+date: 2019-01-01
+type: blog
+url: "/blog/clean-hugo-blog-theme-features.html"
+excerpt: A living reference for every shortcode and formatting option available in
+  the clean-hugo theme — figures, admonitions, admonition quotes, blockquotes,
+  pull quotes,
+  buttons, YouTube embeds,
+  and more.
+author: pyopensci
+toc: true
+blog_topic: community
+---
+This post is a living reference for the clean-hugo theme. Every shortcode
+and content-formatting option available in the theme is demonstrated here
+with a working example and the code that produces it. Use this post to
+test that a theme change has not broken existing content, and as a
+copy-paste resource when writing new blog posts.
+
+## Figures
+
+The `figure` shortcode renders images with optional captions and
+automatic WebP support. It generates a `<picture>` element with a WebP
+`<source>` and a fallback `<img>`. If a `.webp` file exists alongside the
+source image, modern browsers use it automatically.
+
+**Usage:**
+
+```
+{{</* figure
+  src="images/pyopensci-general/pyopensci-timeline2019-2024.png"
+  alt="Descriptive alt text."
+  caption="Optional caption with **Markdown** support."
+  link="images/pyopensci-general/pyopensci-timeline2019-2024.png"
+*/>}}
+```
+
+**Rendered:**
+
+{{< figure
+  src="images/pyopensci-general/pyopensci-timeline2019-2024.png"
+  alt="A timeline showing the growth of pyOpenSci from 2019 to 2024."
+  caption="Growth of pyOpenSci from 2019 to 2024. The `link` param makes the image click-to-enlarge."
+  link="images/pyopensci-general/pyopensci-timeline2019-2024.png"
+>}}
+
+Parameters:
+
+| Param | Required | Description |
+|---|---|---|
+| `src` | yes | Image path (static or page bundle) |
+| `alt` | yes | Alt text — always required for accessibility |
+| `caption` | no | Caption text, supports Markdown |
+| `link` | no | URL the image links to (defaults to `src`) |
+
+
+## Admonitions
+
+The `admonition` shortcode creates highlighted callout boxes. Five types
+are available. An optional `title` param adds a heading inside the box.
+
+**Usage:**
+
+```
+{{</* admonition type="info" title="Optional title" */>}}
+Content with **Markdown** support.
+{{</* /admonition */>}}
+```
+
+**All five types rendered:**
+
+{{< admonition type="note" title="Note (default)" >}}
+Use `type="note"` for general supplementary information. This is the
+default type if you omit the `type` param.
+{{< /admonition >}}
+
+{{< admonition type="info" title="Info" >}}
+Use `type="info"` for helpful context or background detail that readers
+may want but don't strictly need.
+{{< /admonition >}}
+
+{{< admonition type="warning" title="Warning" >}}
+Use `type="warning"` to flag something that could cause problems if
+overlooked — a deprecation, a known issue, a prerequisite.
+{{< /admonition >}}
+
+{{< admonition type="danger" title="Danger" >}}
+Use `type="danger"` for destructive or irreversible actions, or for
+critical requirements that must be met before proceeding.
+{{< /admonition >}}
+
+{{< admonition type="success" title="Success" >}}
+Use `type="success"` to confirm a completed step, highlight a positive
+outcome, or call attention to a best practice.
+{{< /admonition >}}
+
+**Without a title:**
+
+{{< admonition type="info" >}}
+Omit the `title` param and the header row is hidden entirely.
+{{< /admonition >}}
+
+
+## Admonition quotes
+
+The `admonition-quote` shortcode renders a quotation inside an
+admonition-style callout box. It uses the same `type` variants as
+`admonition`, with a single opening quote mark at the top (no closing
+quote). Optional `title`, `author`, and `event` params are supported.
+
+Same quote text in each example so you can compare styles.
+
+**Note:**
+
+```
+{{</* admonition-quote type="note" title="Note quote" author="Anonymous" event="AGU 2019 Townhall" */>}}
+Good research software is built for the people who use it.
+{{</* /admonition-quote */>}}
+```
+
+{{< admonition-quote type="note" title="Note quote" author="Anonymous" event="AGU 2019 Townhall" >}}
+Good research software is built for the people who use it.
+{{< /admonition-quote >}}
+
+**Info:**
+
+```
+{{</* admonition-quote type="info" */>}}
+Good research software is built for the people who use it.
+{{</* /admonition-quote */>}}
+```
+
+{{< admonition-quote type="info" >}}
+Good research software is built for the people who use it.
+{{< /admonition-quote >}}
+
+**Warning:**
+
+```
+{{</* admonition-quote type="warning" title="A community reminder" */>}}
+Good research software is built for the people who use it.
+{{</* /admonition-quote */>}}
+```
+
+{{< admonition-quote type="warning" title="A community reminder" >}}
+Good research software is built for the people who use it.
+{{< /admonition-quote >}}
+
+**Success:**
+
+```
+{{</* admonition-quote type="success" author="pyOpenSci community member" */>}}
+Good research software is built for the people who use it.
+{{</* /admonition-quote */>}}
+```
+
+{{< admonition-quote type="success" author="pyOpenSci community member" >}}
+Good research software is built for the people who use it.
+{{< /admonition-quote >}}
+
+**Danger:**
+
+```
+{{</* admonition-quote type="danger" */>}}
+Good research software is built for the people who use it.
+{{</* /admonition-quote */>}}
+```
+
+{{< admonition-quote type="danger" >}}
+Good research software is built for the people who use it.
+{{< /admonition-quote >}}
+
+Parameters:
+
+| Param | Default | Description |
+|---|---|---|
+| `type` | `note` | Admonition variant: `note`, `info`, `warning`, `danger`, `success` |
+| `title` | — | Optional heading above the quote |
+| `author` | — | Attribution name (optional) |
+| `event` | — | Event or source (optional) |
+
+
+## Blockquotes
+
+Plain Markdown blockquotes are for **inline citations** in the flow of a
+post — a left border, light background, and Lora italic body text. No
+shortcode is required.
+
+Use a **pull quote** when you want the same quote typography with a
+decorative opening mark and no sidebar box. Use an **admonition quote**
+when the quote should sit inside a colored callout box.
+
+**Single paragraph:**
+
+```markdown
+> Good research software is built for the people who use it.
+```
+
+> Good research software is built for the people who use it.
+
+**With attribution (written in Markdown):**
+
+```markdown
+> Good research software is built for the people who use it.
+>
+> — **pyOpenSci community member**, *Peer review guide*
+```
+
+> Good research software is built for the people who use it.
+>
+> — **pyOpenSci community member**, *Peer review guide*
+
+**Multi-line quote:**
+
+```markdown
+> Good research software is built for the people who use it.
+>
+> Quotes can span multiple paragraphs when you need more room.
+```
+
+> Good research software is built for the people who use it.
+>
+> Quotes can span multiple paragraphs when you need more room.
+
+**Nested in a list** (blockquote inside list item):
+
+```markdown
+* Before you submit, read the packaging guide.
+* Remember the goal of review:
+
+  > Good research software is built for the people who use it.
+
+* Then open your submission issue on GitHub.
+```
+
+* Before you submit, read the packaging guide.
+* Remember the goal of review:
+
+  > Good research software is built for the people who use it.
+
+* Then open your submission issue on GitHub.
+
+
+## Pull quotes
+
+The `pullquote` shortcode uses the same Lora quote text as blockquotes,
+with a decorative opening mark above and no left border or background.
+Three accent colors are available for the mark. Optional `author` and
+`event` params add attribution.
+
+Same quote text in each example so you can compare colors.
+
+**Teal (default):**
+
+```
+{{</* pullquote color="teal" author="Anonymous" event="AGU 2019 Townhall" */>}}
+Good research software is built for the people who use it.
+{{</* /pullquote */>}}
+```
+
+{{< pullquote color="teal" author="Anonymous" event="AGU 2019 Townhall" >}}
+Good research software is built for the people who use it.
+{{< /pullquote >}}
+
+**Magenta:**
+
+```
+{{</* pullquote color="magenta" */>}}
+Good research software is built for the people who use it.
+{{</* /pullquote */>}}
+```
+
+{{< pullquote color="magenta" >}}
+Good research software is built for the people who use it.
+{{< /pullquote >}}
+
+**Purple:**
+
+```
+{{</* pullquote color="purple" author="pyOpenSci community member" */>}}
+Good research software is built for the people who use it.
+{{</* /pullquote */>}}
+```
+
+{{< pullquote color="purple" author="pyOpenSci community member" >}}
+Good research software is built for the people who use it.
+{{< /pullquote >}}
+
+Parameters:
+
+| Param | Default | Description |
+|---|---|---|
+| `color` | `teal` | Color variant: `teal`, `magenta`, or `purple` |
+| `author` | — | Attribution name (optional) |
+| `event` | — | Event or source (optional, requires `author`) |
+
+
+## Buttons
+
+The `button` shortcode renders a styled CTA link. Variants use pyOpenSci
+brand colors. Default and large (`size="lg"`) sizes are supported.
+
+**Dark purple:**
+
+```
+{{</* button href="/blog/" variant="dark-purple" */>}}
+Dark purple
+{{</* /button */>}}
+```
+
+{{< button href="/blog/" variant="dark-purple" >}}Dark purple{{< /button >}}
+
+**White:**
+
+```
+{{</* button href="/blog/" variant="white" */>}}
+White
+{{</* /button */>}}
+```
+
+{{< button href="/blog/" variant="white" >}}White{{< /button >}}
+
+**Green:**
+
+```
+{{</* button href="/blog/" variant="green" */>}}
+Green
+{{</* /button */>}}
+```
+
+{{< button href="/blog/" variant="green" >}}Green{{< /button >}}
+
+**Light purple:**
+
+```
+{{</* button href="/blog/" variant="light-purple" */>}}
+Light purple
+{{</* /button */>}}
+```
+
+{{< button href="/blog/" variant="light-purple" >}}Light purple{{< /button >}}
+
+**Outline:**
+
+```
+{{</* button href="/blog/" variant="outline" */>}}
+Outline
+{{</* /button */>}}
+```
+
+{{< button href="/blog/" variant="outline" >}}Outline{{< /button >}}
+
+**Large:**
+
+```
+{{</* button href="/blog/" variant="dark-purple" size="lg" */>}}
+Large button
+{{</* /button */>}}
+```
+
+{{< button href="/blog/" variant="dark-purple" size="lg" >}}Large button{{< /button >}}
+
+**With icon (right):**
+
+```
+{{</* button href="/blog/" variant="dark-purple" icon="arrow-right" iconPosition="right" */>}}
+Continue reading
+{{</* /button */>}}
+```
+
+{{< button href="/blog/" variant="dark-purple" icon="arrow-right" iconPosition="right" >}}Continue reading{{< /button >}}
+
+**With icon (left):**
+
+```
+{{</* button href="https://github.com/pyOpenSci" variant="outline" icon="github" target="_blank" */>}}
+View on GitHub
+{{</* /button */>}}
+```
+
+{{< button href="https://github.com/pyOpenSci" variant="outline" icon="github" target="_blank" >}}View on GitHub{{< /button >}}
+
+Parameters:
+
+| Param | Default | Description |
+|---|---|---|
+| `href` | `#` | Link URL |
+| `variant` | `dark-purple` | `dark-purple`, `white`, `green`, `light-purple`, `outline` |
+| `size` | — | `lg` (optional) |
+| `icon` | — | Font Awesome icon name (without `fa-`) |
+| `iconPosition` | `left` | `left` or `right` |
+| `target` | — | `_blank` for external links |
+
+
+## YouTube
+
+The `youtube` shortcode embeds a YouTube video in a responsive 16:9
+container. Pass the video ID from the URL (the part after `v=`).
+
+**Usage:**
+
+```
+{{</* youtube id="n9IZGT4DxDs" */>}}
+```
+
+**Rendered:**
+
+{{< youtube id="n9IZGT4DxDs" >}}
+
+
+## Blog list
+
+The `blog-list` shortcode pulls the most recent blog posts and renders
+them as listing cards. Use it on any page to surface recent content.
+
+**Usage:**
+
+```
+{{</* blog-list title="Recent posts" limit=3 */>}}
+```
+
+Parameters:
+
+| Param | Default | Description |
+|---|---|---|
+| `title` | `Recent Thoughts` | Section heading |
+| `limit` | `3` | Number of posts to display |
+
+
+## Masonry gallery
+
+The `masonry` shortcode creates a responsive photo grid with
+click-to-enlarge lightbox (GLightbox). Write images as standard Markdown
+inside the shortcode.
+
+**Usage:**
+
+```
+{{</* masonry */>}}
+![Alt text for photo one](images/path/photo1.jpg)
+![Alt text for photo two](images/path/photo2.jpg)
+![Alt text for photo three](images/path/photo3.jpg)
+{{</* /masonry */>}}
+```
+
+Images tile responsively and open full-size in a lightbox when clicked.
+All images in a gallery share navigation arrows in the lightbox view.
+
+
+## Section heading
+
+The `section-heading` shortcode renders a large centred heading with an
+optional subtitle. Useful at the top of long posts to establish visual
+hierarchy.
+
+**Usage:**
+
+```
+{{</* section-heading
+  title="Section title"
+  subtitle="Optional subtitle • With separators"
+*/>}}
+```
+
+**Rendered:**
+
+{{< section-heading
+  title="Section heading example"
+  subtitle="Optional subtitle text • Can use • separators"
+>}}
+
+
+## Metrics bar
+
+The `metrics-bar` shortcode renders a row of key statistics with large
+numbers. Use it to highlight impact data.
+
+**Usage:**
+
+```
+{{</* metrics-bar
+  stat1="**128** blog posts"
+  stat2="**500+** community members"
+  stat3="**100+** reviewed packages"
+  stat4="**WCAG AA** accessible"
+*/>}}
+```
+
+**Rendered:**
+
+{{< metrics-bar
+  stat1="**128** blog posts migrated"
+  stat2="**500+** community members"
+  stat3="**100+** reviewed packages"
+  stat4="**WCAG AA** accessible"
+>}}
+
+
+## Cards
+
+Three card shortcodes are available for structured content blocks.
+
+### Two-card row
+
+```
+{{</* two-card-row */>}}
+{{</* card title="Card one" icon="fa-solid fa-star" */>}}
+Content for the first card with **Markdown** support.
+{{</* /card */>}}
+{{</* card title="Card two" icon="fa-solid fa-bolt" */>}}
+Content for the second card.
+{{</* /card */>}}
+{{</* /two-card-row */>}}
+```
+
+{{< two-card-row >}}
+{{< card title="Peer review" icon="fa-solid fa-magnifying-glass" >}}
+pyOpenSci runs an open, community-driven peer review process for
+scientific Python packages. Packages that pass review are listed in
+our ecosystem.
+{{< /card >}}
+{{< card title="Packaging guidance" icon="fa-solid fa-box-open" >}}
+Our Python Packaging Guide covers everything from creating your first
+package to publishing on PyPI — with tutorials written for scientists.
+{{< /card >}}
+{{< /two-card-row >}}
+
+### Single card wide
+
+```
+{{</* single-card-wide title="Wide card" icon="fa-solid fa-users" */>}}
+Full-width card content here.
+{{</* /single-card-wide */>}}
+```
+
+{{< single-card-wide title="Join the pyOpenSci community" icon="fa-solid fa-users" >}}
+pyOpenSci is a diverse, welcoming community of scientists, developers,
+and open source enthusiasts. Whether you want to submit a package for
+review, volunteer as a reviewer, or contribute to our guides —
+**there is a place for you here**.
+{{< /single-card-wide >}}
+
+
+## Standard Markdown elements
+
+These are not shortcodes — they are standard Markdown rendered by Hugo.
+Include them here so a full blog post render covers all common content
+types.
+
+### Code blocks
+
+Inline: `python3 -m pip install pyopensci`
+
+Fenced block with syntax highlighting:
+
+```python
+import pyopensci
+
+# Submit a package for review
+package = pyopensci.Package(
+    name="mypackage",
+    version="1.0.0",
+    github_url="https://github.com/example/mypackage",
+)
+package.submit()
+```
+
+```bash
+hugo serve --buildDrafts --disableFastRender
+```
+
+### Blockquotes
+
+See [Blockquotes](#blockquotes) above for full examples. Quick render check:
+
+```markdown
+> Good research software is built for the people who use it.
+```
+
+> Good research software is built for the people who use it.
+
+### Tables
+
+| Column A | Column B | Column C |
+|---|---|---|
+| Value 1 | Value 2 | Value 3 |
+| Value 4 | Value 5 | Value 6 |
+
+### Lists
+
+Unordered:
+
+* First item
+* Second item
+  * Nested item
+  * Another nested item
+* Third item
+
+Ordered:
+
+1. Step one
+2. Step two
+3. Step three
diff --git a/content/blog/2026-05-04-ship-it-cohort-one.md b/content/blog/2026-05-04-ship-it-cohort-one.md
new file mode 100644
index 00000000..2ca28df2
--- /dev/null
+++ b/content/blog/2026-05-04-ship-it-cohort-one.md
@@ -0,0 +1,145 @@
+---
+title: 'Ship It Cohort One: What We Built, What We Learned, and What''s Next'
+date: '2026-05-04'
+type: blog
+excerpt: 'pyOpenSci recently wrapped up the first cohort of Ship It: Python Packaging
+  in the Generative AI Era — a 10-day async course that took 55 university researchers
+  from zero to a published Python package. Here''s what we built, what participants
+  said, and what''s coming next.'
+author: Leah Wasser
+blog_topic: learn
+toc: true
+comments: true
+url: "/blog/ship-it-cohort-one.html"
+lastmod: '2026-05-04'
+image:
+  src: images/landing-pages/scipy-sprint-working.png
+  alt: Three people collaborating during a pyOpenSci sprint, working together on laptops
+    at a conference table.
+---
+
+Python packaging can be overwhelming — standards and tools evolve quickly, and the terminology is technical. To address these challenges, pyOpenSci recently launched **Ship It: Python Packaging in the Generative AI Era**. This 10-day asynchronous course connects university researchers and learners with open source experts, guiding them through the process of transforming code into a published, tested, and documented package — while weaving in a framework for using generative AI thoughtfully. The curriculum is informed by our community-driven resources, including the [pyOpenSci Python packaging guide](https://www.pyopensci.org/python-package-guide/) and our beginner-friendly [packaging tutorials](https://www.pyopensci.org/python-package-guide/tutorials/create-python-package.html).
+
+## What is Ship It?
+
+Ship It is a 10-day, fully online, asynchronous cohort course that takes you from zero to a published Python package — with tests, documentation, and automated workflows built on the [pyOpenSci packaging template](https://github.com/pyOpenSci/pyos-package-template).
+
+The course was designed as an accessible entry point for researchers, academics, research software engineers, and anyone who wants to package and share their work using modern best practices. Participants learn how to use packaging tools like [Hatch](https://hatch.pypa.io/) for environment management and task running, [uv](https://docs.astral.sh/uv/) for fast dependency resolution, and [pytest](https://pytest.org/) for testing — all inside GitHub Codespaces, so nobody gets stuck on local setup.
+
+Each weekday, a new module drops, made up of videos and text lessons. Each week, participants complete interactive "milestones" in which they share their own package or day's work and then test a classmate's. This project-based learning approach mirrors the spirit of open source collaboration. Engagement was also encouraged by a gamified points system, where participants earned points working toward a final LinkedIn badge and completion certificate. For many, the community aspect of the course was an unexpected — but carefully designed — highlight.
+
+In response to "what was your favorite part of the course", one participant said:
+
+
+> Probably the community part. Don't misunderstand me, the lectures are great, clear and well structured. Easy to follow. But interacting with the community, testing each other's code, has been sincerely great.
+
+
+## Learning from the people who build the tools
+
+Sprinkled throughout the course were interviews with open source leaders like Carol Willing (Jupyter, CPython) and Melissa Mendonça (NumPy, Napari), so learners got more than technical skills — they received insights from the people building the tools they use every day.
+
+The async format was a deliberate choice. pyOpenSci has run synchronous training events for years, but fixed timing limits who can attend, leaves little room for digestion, and tends to keep engagement within single institutions. An async cohort format gives participants flexibility to learn at their own pace while still building real connections across universities.
+
+We also wove a thread of responsible AI throughout the course. We've been thinking deeply about this topic for a few years, and we wanted to offer a clear framework for using AI tools in ways that grow your skills and sustain — rather than drain — the open source ecosystem.
+
+## Ship It by the numbers
+
+This first cohort was generously sponsored by Open Source at Stanford University and supported by the [CURIOSS OSPO network](https://curioss.org/), making it free for all 55 participants.
+
+- **55** registered participants from universities across the US
+- **27** videos across 10 modules
+- **6** gamified milestones — 14 participants completed all of them
+- **~30** participants created and published a Python package — for many, their first ever
+- Sponsored by [Stanford University](https://opensource.stanford.edu/) and supported by the CURIOSS OSPO network
+
+It was incredible to see that ~30 people published a Python package, many for the very first time. But the numbers only tell part of the story.
+
+## What participants experienced
+
+Ship It was designed to be hands-on from day one — and that showed in the outcomes. One participant, a structural biologist,was able to clean up a package they had been working on and share it at her departmental retreat. She shared her story with us:
+
+
+> This week I presented my Python package 'PDBCleanV2' at the Structural Biology Departmental Retreat. It was well received by attendees and, overall, a great experience. I wanted to thank you because pyOpenSci was a great influence in getting my package in shape.
+>
+> — Fatima Pardo, Structural Biologist
+
+
+That's the goal. Real code, real learning, real impact.
+
+### The community made it real
+
+The milestone structure pushed participants to engage with each other's work — and that turned out to be one of the most talked-about parts of the course.
+
+
+> I finally caught up on the content of the workshop, and I have been loving it. Some concepts used to seem very intimidating, but I liked how they were explained clearly. I have also been enjoying the community aspect, checking other people's packages and getting comments on mine.
+
+
+### Structure and clarity mattered
+
+Participants consistently called out the clear, step-by-step progression as a highlight. Going from "what even is a `pyproject.toml`" on Day 2 to "I just published my package to TestPyPi on Day 3 allowed for big early wins that helped people stay oriented and keep moving.
+
+
+> My favorite part of the course has been the step-by-step guidance and the hands-on experience of building a package. I also really liked the videos where the mentor shares the challenges they faced — it made the process feel more real and relatable. Testing classmates' packages was another highlight, as it helped me learn from others and see different approaches.
+
+
+
+> Loved how interactive the workshop was, and how responsive the instructors were. The content was great, and the videos made it so easy to understand the concepts. And having the text below helped me when I wanted to review.
+
+
+### Hands-on from day one
+
+Learners also commented on how the course broke down  technical packaging terms and content into easy to digest lessons.
+Imposter syndrome is real and pyOpenSci works hard to break down
+those barriers for everyone.
+
+
+> I am very motivated. The workshop made me less afraid of certain aspects of creating the package; the explanations have been very clear and to the point. I am planning to implement what we learned on my own package, and I feel confident that I can do it.
+
+
+### Honest takes on GenerativeAI
+
+Several participants specifically called out the AI content — not just the technical pieces, but the perspective. The responsible AI framing resonated, as did the expert interviews.
+
+In response to a question about the Generative AI content, one participant had this to say about the associated Generative AI milestone activities:
+
+
+> [the genAi module] It was an interesting session. I got more than I expected, in particular from the milestone. Seeing how other people interacted with AI and what we learned from it. I think it is important to have these discussions.
+
+
+GenerativeAI has such a profound impact on all aspects of writing code right now. We encouraged participants to experiment with using GenAI tools to write tests and implement "defensive code strategies" in their package modules and then reflect and share the outcomes of this effort with each other.
+
+### The course design flexibility made it accessible
+
+
+> I attended a conference during this course (full day for two days) and was still able to complete the course once the conference ended. I appreciate the structure of the course, and the flexibility was also needed.
+
+
+## A window into the Python ecosystem — and the AI conversation
+
+Ship It was about more than packaging mechanics. Through interviews with Python leaders like Carol Willing, CPython core developer, and Melissa Mendonça from Quansight, participants got an inside look at the Python ecosystem that most of us simply aren't exposed to in traditional academic environments.
+
+That included an honest conversation about AI — specifically, how the explosion of generative AI is placing real pressure on the open source human ecosystem. The people maintaining the tools you rely on are volunteers. That context matters.
+
+The course also explored how to use AI thoughtfully — as a tool for building more robust test suites, writing defensive code, and deepening your own understanding. Not something to become reliant on, but something to grow with.
+
+## What we learned from cohort one
+
+The flexibility of the async format resonated more than we expected. Participants were logging in at 2 am, at 7 am, whenever it fit their lives and time zones.
+
+My favorite part of running this course was the cross-institutional engagement. Learners at Stanford, Berkeley, UC Davis, UC Santa Barbara, Harvard, Wisconsin, and universities across the country were connecting with each other in ways that simply don't happen within a single institution. That's exactly what pyOpenSci is built for — bringing the broader community together rather than keeping expertise siloed.
+
+That community connection extended to the experts, too. Participants learned directly from the people building the tools they use every day through real conversations. That kind of engagement is what makes pyOpenSci's trainings shine, and it's hard to replicate.
+
+For pyOpenSci, the async cohort model also supports our sustainability goals. Running the course multiple times for different groups, at their own pace, means we can reach more people — and build toward long-term sustainability by doing what we do best: making packaging and sharing code more accessible so researchers can spend more time solving the world's greatest challenges and less time fighting with tooling.
+
+## Bringing Ship It to your institution
+
+If you're running an OSPO, a research computing program, or any initiative that supports academics who write and share code, ShipIt was built with you in mind. The course gives your community direct access to modern Python packaging practices, responsible AI frameworks, and — crucially — real connections to the people building the tools within the open source ecosystem.
+
+[Click here to learn more about our partnership program.](/learn-universities-labs.html). We'd love to talk with you about how we can support your community.
+
+## What's next
+
+The first cohort proved the model works. Researchers published packages, made connections across institutions, and left with skills and confidence they didn't have before. We're building on that for fall 2026.
+
+Keep an eye on our [events page](https://www.pyopensci.org/events/) for cohort announcements.
diff --git a/content/blog/2026-05-21-pycon-us-2026-community-connection.md b/content/blog/2026-05-21-pycon-us-2026-community-connection.md
new file mode 100644
index 00000000..2485c0fc
--- /dev/null
+++ b/content/blog/2026-05-21-pycon-us-2026-community-connection.md
@@ -0,0 +1,52 @@
+---
+title: 'PyCon US 2026: Community, connection, and what comes next'
+date: '2026-05-21'
+type: blog
+excerpt: Times are hard, but communities like pyOpenSci still show up. At PyCon US
+  2026 in Long Beach, we saw people connecting, sprinting, and supporting each other—and
+  why the humans are what make open source work.
+author: Leah Wasser
+blog_topic: community
+toc: true
+comments: true
+url: "/blog/pycon-us-2026-community-connection.html"
+lastmod: '2026-05-27'
+image:
+  src: images/blog/2026/pycon-us-2026-sprint-attendees.png
+  alt: Three pyOpenSci community members smiling together at an outdoor patio during
+    PyCon US 2026 in Long Beach.
+---
+
+Times are hard right now. Communities like pyOpenSci matter more than ever. We saw it at [PyCon US](https://us.pycon.org/2026/) this year — the political strain, the GenAI hype cycle and anxiety, the rapid changes reshaping open source. People are tired. People are frustrated. But here's what else we saw: people still showing up. Still connecting. Still supporting each other.
+
+When things get hard, when the ground shifts beneath us, we need each other more than ever. We need spaces to connect, to learn together, to solve challenging problems as a community. PyCon reminded me why I love this work so much.
+
+I'll never forget my very first PyCon in Salt Lake City. I was intimidated. It's a really big conference, and I only knew a few people. That first sprint? We had one person show up who wasn't already part of our community. He sat down and spent the entire day working on our website, helping us improve our infrastructure. He gave his time to help a nonprofit organization like pyOpenSci grow.
+
+[Read more about that first PyCon experience in Salt Lake City](/blog/pycon-2023-packaging-presentation-sprints-leah-wasser.html).
+
+{{< figure src="images/blog/2026/pycon-us-sprint-collaboration.png" alt="Two people collaborating on laptops at a round table during a PyCon US coding sprint. One person wears a PyCon US 2024 lanyard. The laptop on the right is covered in stickers for NumPy, NumFocus, Hubble, and other scientific open source projects." caption="Community members working together during a pyOpenSci sprint at PyCon US." >}}
+
+Fast forward three years to Long Beach, California. We filled rooms with our open spaces. We had tables of people sprinting, working on pyOpenSci projects, learning together. People who attended multiple sprints with us — people I remembered struggling to submit their first pull request, now confident in their GitHub skills. This is what community support looks like. This is what pyOpenSci's mission is all about: helping people grow. [Read about the Maintainer Summit](/blog/pycon-us-2026-maintainers-summit.html) and the [full sprint story](/blog/pycon-us-2026-sprints.html) from PyCon US 2026.
+
+{{< figure src="images/blog/2026/pycon-us-2026-sprint-attendees.png" alt="Two smiling PyCon US 2026 attendees sitting at a round table with laptops during a conference sprint. Both wear purple PyCon US 2026 lanyards from Long Beach." caption="Building connections and working together during the PyCon US 2026 sprints in Long Beach." >}}
+
+PyCon US has become my favorite conference. Not because of the topics covered or how it's organized, but because of the people. The people who were strangers a few years ago and have now become my closest friends and colleagues. The hallway conversations. The way people show up for each other.
+
+{{< figure src="images/blog/2026/pycon-us-2026-community-friends.png" alt="Three pyOpenSci community members smiling together at an outdoor patio during PyCon US 2026 in Long Beach. The person in the center wears a PyCon US 2026 conference lanyard and name badge." caption="Friendships and connections that grow year after year at PyCon US." >}}
+
+Even in a hard year — especially in a hard year — I left the conference feeling fulfilled, feeling whole, and so grateful for the friendships and relationships I've deepened over time.
+
+## In this series
+
+**Part 1: Community, connection, and what comes next** — You're reading it. An overview of PyCon US 2026 and why the people in the room are what make open source work.
+
+**Part 2: [The Maintainer Summit](/blog/pycon-us-2026-maintainers-summit.html)** — A milestone year for the summit: formal PyCon registration, 150+ maintainers, and roundtables on packaging, security, and generative AI.
+
+**Part 3: [The sprints](/blog/pycon-us-2026-sprints.html)** — From one person in Salt Lake City to a room full of contributors working together. Growth, learning, and community in action.
+
+**Part 4: [Generative AI and open source](/blog/pycon-us-2026-generative-ai-open-source.html)** — GenAI was everywhere at PyCon this year. Not as hype, but as a real challenge the community is wrestling with. Between our open space, the Maintainer Summit BoF, and Amanda Casari's powerful closing keynote, a theme emerged: the path forward is human.
+
+## What it all comes down to
+
+If there's one thing that tied all of these experiences together, it's this: **the humans are what make open source work.** The tools change, the challenges evolve, but the connections, the learning, the care people bring to this work — that's the irreplaceable part.
diff --git a/content/blog/2026-05-29-pycon-us-2026-maintainers-summit.md b/content/blog/2026-05-29-pycon-us-2026-maintainers-summit.md
new file mode 100644
index 00000000..b0bba2e8
--- /dev/null
+++ b/content/blog/2026-05-29-pycon-us-2026-maintainers-summit.md
@@ -0,0 +1,88 @@
+---
+title: 'Tools Track, GenAI Bof and Roundtables: This year''s PyCon US Maintainer Summit
+  was something special'
+date: '2026-05-29'
+type: blog
+excerpt: As a co-organizer of the PyCon US Maintainer Summit, Leah Wasser reflects
+  on a milestone year—150+ maintainers, formal PyCon registration, new community tools,
+  and roundtables on packaging, security, and generative AI.
+author: Leah Wasser
+blog_topic: community
+toc: true
+comments: true
+url: "/blog/pycon-us-2026-maintainers-summit.html"
+lastmod: '2026-05-29'
+image:
+  src: images/blog/2026/pycon-us-2026-maintainers-summit-organizers.png
+  alt: Maintainer Summit co-organizers Leah Wasser, Inessa Pawson, and Mariatta Wijaya
+    smile together for a selfie on an outdoor patio at PyCon US in Long Beach, wearing
+    conference lanyards.
+---
+
+*This post is Part 2 of a 4-part series on pyOpenSci at PyCon US 2026. [Part 1](/blog/pycon-us-2026-community-connection.html) covers community, connection, and what comes next.*
+
+I first attended the [PyCon US Maintainer Summit](https://us.pycon.org/2026/events/maintainers-summit/) five years ago as a speaker. I'm still here — now as a co-organizer. This year felt like a milestone for many different reasons.
+
+{{< figure src="images/blog/2026/pycon-us-2026-maintainers-summit-organizers-slide.png" alt="Maintainer Summit organizers slide with headshots of Inessa Pawson, Leah Wasser, and Mariatta Wijaya beneath the Maintainers Summit title and PyCon US Long Beach branding." caption="Maintainer Summit co-organizers <a href='https://github.com/InessaPawson'>Inessa Pawson</a>, Leah Wasser, and <a href='https://github.com/mariatta'>Mariatta Wijaya</a>." >}}
+
+## Building the summit: a year-round labor of love
+
+What most people don't realize is that organizing the PyCon US Maintainer Summit is a year-round effort. We start thinking about the next one almost as soon as the last one wraps — collecting participant feedback, reflecting on what worked, and thinking about what to change.
+
+This year we focused on something we've been working toward for a while: making the Maintainer Summit a more formal part of the PyCon US schedule. The Maintainer Summit has been running since 2019; this year we took a big step forward. Attendees could officially register, we could communicate directly with them through the PyCon US registration website, and we were formally listed on the PyCon US schedule. These might seem like small steps, but it takes a lot to make these types of changes in a large event like PyCon US that is organized by both PyCon US staff but also depends on a large team of volunteers.
+
+This year's successes wouldn't have happened without the incredible support of PyCon US co-chairs [Elaine Wong](https://github.com/elainewong) and [Jon Bonafato](https://github.com/jonafato), and PSF infrastructure lead [Jacob Coffee](https://github.com/jacobcoffee).
+
+## New structure and event features for the day
+
+We also rethought the structure of the Maintainer Summit this year. We added a Tools Track, inspired by the Tools Track at SciPy. We also added a GenAI Birds of a Feather session, and roundtables focused on lively discussions around packaging, security, and AI tools in open source.
+
+{{< figure src="images/blog/2026/pycon-us-2026-maintainers-summit-cary-hatch-tools-track.png" alt="Cary Hawkins presents on Hatch in the Tools Track at the PyCon US Maintainer Summit in Long Beach, standing at a podium beside a slide titled From Sidelines to Maintainer: How one conversation sparked new development in Hatch." caption="<a href='https://github.com/cjames23'>Cary Hawkins</a> presents on <a href='https://hatch.pypa.io/'>Hatch</a> in the Maintainer Summit during the newly added Tools Track that featured both Hatch and UV." >}}
+
+We also helped launch an unofficial Discord with an automated bot — built with help from some wonderful folks in the Python community — that provided real-time session updates and gave attendees a way to connect with each other throughout the day. A first for the summit. This was a great way to help attendees connect with each other and follow the conference schedule without having to keep checking the schedule website.
+
+None of this happens without an incredible team. [Inessa Pawson](https://github.com/InessaPawson) and [Mariatta Wijaya](https://github.com/mariatta) bring deep experience organizing events like this, and I've learned so much working alongside them. From the call for proposals, to reading submissions, to managing last-minute schedule changes — there's an enormous amount of work that goes into making a day like this feel seamless.
+
+{{< figure src="images/blog/2026/pycon-us-2026-maintainers-summit-organizers.png" alt="Maintainer Summit co-organizers Leah Wasser, Inessa Pawson, and Mariatta Wijaya smile together for a selfie on an outdoor patio at PyCon US in Long Beach, wearing conference lanyards." caption="Maintainer Summit co-organizers Leah Wasser, Inessa Pawson, and Mariatta Wijaya at PyCon US in Long Beach." >}}
+
+## A day full of energy
+
+This year our registrations peaked at 150+ people for a full day of conversation around packaging, security, and AI. The event ran from 10am to 6pm, and while attendance dipped after lunch (this always happens at these types of events), energy in the room kept building. People sticking around until 6pm when they closed down the room was a great sign that the community is growing and that people are interested in the topics we were discussing.
+
+{{< figure src="images/blog/2026/pycon-us-2026-maintainers-summit-room.png" alt="A wide view of the PyCon US Maintainer Summit in Long Beach, with dozens of maintainers seated at round tables, many with open laptops, listening to a session." >}}
+
+It was especially meaningful to have pyOpenSci community members represented. [Felipe Moreno](https://github.com/flpm) spoke about the translations infrastructure he built for our [Python packaging guide](https://www.pyopensci.org/python-package-guide/) — work that started at our [2024 sprint](/blog/pyopensci-pyconus-2024-sprints.html) and has grown into a multilingual contribution community. [Part 3 of this series](/blog/pycon-us-2026-sprints.html) tells the full 2026 sprint story, including Portuguese translation work that built on Felipe's infrastructure. [Avik Basu](https://github.com/ab93) shared work on a package he's been developing. Having pyOpenSci members on stage alongside maintainers of core Python tools like [uv](https://docs.astral.sh/uv/) ([Zanie Blue](https://github.com/zanieb)) and [Hatch](https://hatch.pypa.io/) ([Cary Hawkins](https://github.com/cjames23)), and community leaders like [Carol Willing](https://github.com/willingc) and [Mike Fiedler](https://github.com/miketheman) from the PSF covering security and AI, made for a powerful and well-rounded day.
+
+{{< figure src="images/blog/2026/pycon-us-2026-maintainers-summit-felipe-talk.png" alt="Felipe Moreno presents How Translations Work for pyOpenSci at the PyCon US Maintainer Summit in Long Beach, with a slide showing the pyOpenSci logo projected on screen." caption="<a href='https://github.com/flpm'>Felipe Moreno</a> presents on translation infrastructure for the pyOpenSci Python packaging guide at the Maintainer Summit." >}}
+
+## Roundtables: where the magic happens
+
+The roundtables are always the best part of this event. I will never forget my first roundtable discussion at this event four years ago. I sat with Travis Oliphant (creator of NumPy, SciPy, Numba) and Chase Million ([Million Concepts](https://millionconcepts.com/about.html) CEO) and we talked about business development in open source. Chase, to this day, is not only a long-standing colleague but also a good friend. These types of events allow attendees to build connections that they never forget.
+
+This year, roundtable topics included packaging led by [Zanie Blue](https://github.com/zanieb) from uv and [Cary Hawkins](https://github.com/cjames23) from Hatch, security led by [Mike Fiedler](https://github.com/miketheman) from the Python Software Foundation, and AI tools in open source led by the incredible [Carol Willing](https://github.com/willingc).
+
+What makes roundtables so powerful is that they're real conversations with experts and peers. At the end of a long day, when energy could easily be fading, the roundtables sparked connection and lifted the room.
+
+{{< figure src="images/blog/2026/pycon-us-2026-maintainers-summit-roundtables.png" alt="Two maintainers sit side by side at a round table during the PyCon US Maintainer Summit, focused on a session with laptops and conference lanyards on the table." >}}
+
+## The most electric moment
+
+Our Generative AI Birds of a Feather session, co-hosted with [Jackie Kazil](https://github.com/jackiekazil), was an energizing addition to this year's summit. Jackie reached out to us about hosting this part of the day. Maintainers everywhere are feeling overwhelmed and drained by the pace of AI change. Now more than ever, protecting our mental health and making space to connect, problem-solve together, and support each other matters.
+
+{{< figure src="images/blog/2026/pycon-us-2026-maintainers-summit-genai-bof.png" alt="Jackie Kazil co-hosts the Generative AI Birds of a Feather session at the PyCon US Maintainer Summit, with a live Mentimeter poll on screen asking maintainers how useful they find GenAI in their workflows." >}}
+
+But there's also genuine hope. The majority of people in the room are already using GenAI tools thoughtfully, and that energy of working through hard things *together* was everywhere — echoed beautifully in Amanda Casari's keynote on hope in the age of AI.
+
+
+
+I have a lot more to say about AI tools and generative AI in open source in [Part 4 of this series](/blog/pycon-us-2026-generative-ai-open-source.html).
+
+## Wrap up
+
+{{< figure src="images/blog/2026/pycon-us-2026-maintainers-summit-discussion.png" alt="Two attendees have a focused one-on-one discussion at a table during the PyCon US Maintainer Summit, leaning in as they talk through a shared challenge." >}}
+
+This year's Maintainer Summit felt like a turning point — 150+ maintainers in one room, a more formal home within PyCon US, and new formats that gave people space to connect, learn, and work through hard problems together. That's exactly what this community needs.
+
+pyOpenSci is proud to be an organizing partner for the PyCon US Maintainer Summit. Maintainer work can be isolating; days like this remind us we're not doing it alone. If you couldn't join us in Long Beach, we hope to see you next year.
+
+See you in there.
diff --git a/content/blog/2026-06-02-pycon-us-2026-sprints.md b/content/blog/2026-06-02-pycon-us-2026-sprints.md
new file mode 100644
index 00000000..0fa70123
--- /dev/null
+++ b/content/blog/2026-06-02-pycon-us-2026-sprints.md
@@ -0,0 +1,71 @@
+---
+title: 'It started with one contributor and now we fill the room: pyOpenSci sprints
+  at PyCon US 2026'
+date: '2026-06-01'
+type: blog
+excerpt: Our fourth PyCon US sprint grew from a single contributor in Salt Lake City
+  to ~20 people in Long Beach. Co-sprinting with Hatch, welcoming beginners, and a
+  new Portuguese packaging guide translation show where this community is headed.
+author: Leah Wasser
+blog_topic: community
+toc: true
+comments: true
+url: "/blog/pycon-us-2026-sprints.html"
+lastmod: '2026-05-29'
+image:
+  src: images/blog/2026/pycon-us-2026-sprint-round-table.png
+  alt: Several PyCon US 2026 attendees work together around a crowded round table
+    during the pyOpenSci sprint. Laptops show code editors and project pages, with
+    purple conference lanyards, charging cables, water bottles, and coffee cups spread
+    across the table.
+---
+
+*This post is Part 3 of a 4-part series on pyOpenSci at PyCon US 2026. [Part 1](/blog/pycon-us-2026-community-connection.html) covers community and connection. [Part 2](/blog/pycon-us-2026-maintainers-summit.html) covers the Maintainer Summit.*
+
+This year marked our fourth sprint at [PyCon US](https://us.pycon.org/2026/). If you want to really understand what pyOpenSci is about, our sprints are the place to look.
+
+{{< figure src="images/blog/2026/pycon-us-2026-sprints-keynote-slide.png" alt="The PyCon US 2026 sprints slide projected on the main keynote screen, listing Monday and Tuesday sprint projects including Django, Mailman, ScanAPI, Memray, PyStack, Djangonaut Space, BeeWare, and more." caption="Sprints at PyCon US 2026 — dozens of open source projects welcoming contributors on Monday and Tuesday." >}}
+
+When we held our very first sprint at PyCon US 2023 in Salt Lake City, it was my first time running a formal sprint. I missed the introductions to the sprints and pyOpenSci was not well known in the broader Python community--yet. One person showed up. [Read more about that first PyCon experience](/blog/pycon-2023-packaging-presentation-sprints-leah-wasser.html). This year, ~20 people showed up throughout the day. That arc — from a single contributor to a buzzing room of people at round tables — tells you everything about our community.
+
+{{< figure src="images/blog/2026/pycon-us-2026-sprint-room-wide.png" alt="A wide view of a busy conference room during the pyOpenSci sprint at PyCon US 2026 in Long Beach. In the foreground, three sprinters smile and work at a round table with open laptops while many more groups fill the room in the background." >}}
+
+If you're curious about how we run sprints, our [PyCon US 2024 sprint recap](/blog/pyopensci-pyconus-2024-sprints.html) walks through beginner-friendly setup, issue tagging, and supporting newer GitHub users.
+## Beginner-friendly, always
+
+pyOpenSci sprints are intentionally beginner-friendly and welcoming. We get a mix of people. Including those who are newer to sprinting, a little nervous, maybe unsure if they belong. We also get seasoned contributors who are looking for a way to give back to the community. That mix is exactly who we want in the room. We thrive on seeing people come in unsure and leaving with confidence, new skills, and a new sense of belonging, even if it's just a little bit more. Our strength is in meeting people where they are and giving them the skills, support, and confidence to make their first open source contributions in a safe, welcoming space.
+
+But also our content is technical; so it's important to have experts to review, and validate contributions, contribute new lessons and educational content updates and to help support newer contributors. And what is so special about those experts is they just show up and dive in and know how to help others in a way that is welcoming and supportive.
+
+
+{{< figure src="images/blog/2026/pycon-us-2026-sprint-round-table.png" alt="Several PyCon US 2026 attendees work together around a crowded round table during the pyOpenSci sprint. Laptops show code editors and project pages, with purple conference lanyards, charging cables, water bottles, and coffee cups spread across the table." >}}
+
+## What keeps us going
+
+One of the most meaningful things about running sprints year after year is watching people come back to join us. We have sprinters who showed up for the first time at a previous event — maybe SciPy or another PyCon US meeting. They might have been nervous, or just finding their footing, working through their first pull request. Then they return with more confidence and skills they'd built in the time between. Watching that transformation happen over multiple sprints, seeing people go from uncertain beginners to contributors who can hit the ground running, is everything.
+
+That's pyOpenSci. That's why we exist.
+
+## Building community through collaboration
+
+This year we also saw something wonderful: sprinters connecting with each other and deciding together what to work on. One collaboration that emerged was a translation project — contributors working together to make our [Python packaging guide](https://www.pyopensci.org/python-package-guide/) available in Portuguese.
+
+Starting a Portuguese translation of our packaging guide means our resources will reach an entirely new audience of scientists and researchers over time. This translation work started because two people showed up to a sprint, connected, and decided to work together to make our resources more accessible. And that wouldn't have been possible if one person, Felipe,  hadn't contributed the translation infrastructure to our guide back at a sprint in 2024!
+
+What an incredible full circle moment!
+
+{{< figure src="images/blog/2026/pycon-us-2026-sprint-mentorship.png" alt="At the pyOpenSci translation table during PyCon US 2026 in Long Beach, Felipe Moreno leans over a laptop to help sprinters add Portuguese translations to the packaging guide while other volunteers work at the same round table." caption="The translation table at PyCon US 2026. <a href='https://github.com/flpm'>Felipe Moreno</a> (in the middle) set up the translation infrastructure in 2024 at a sprint. Here Felipe is helping sprinters add Portuguese translations to our packaging guide! Felipe is both a pyOpenSci maintainer and one of the many long-time pyOpenSci contributors and volunteers who help make our supportive and welcoming sprints possible. This is the heart of pyOpenSci." >}}
+
+## Co-sprinting with Hatch
+
+This year we decided to share a room with [Hatch](https://hatch.pypa.io/), one of our favorite Python packaging projects, and its maintainer [Cary Hawkins](https://github.com/cjames23). Having a co-sprint with a project we genuinely love and recommend brought even more energy and expertise into the room. This got me thinking about how we might be able to support projects that we love more through future sprints.
+
+{{< figure src="images/blog/2026/pycon-us-2026-sprint-contributors.png" alt="Two PyCon US 2026 sprinters sit side by side at a round table, focused on their laptops during the pyOpenSci sprint. pyOpenSci stickers, power cables, and drinks are scattered on the table while other groups work at tables across the conference hall behind them." >}}
+
+## What's next
+
+Sprint day is my favorite day of any conference — even when I'm exhausted, even when the week has been long. There is nothing like watching people make their first contributions, find their confidence, and connect with each other over shared work. For me that connection fills my soul as it encapsulates the true spirit of open source and the heart of pyOpenSci.
+
+Our next sprint will be at [EuroPython](https://europython.eu/) in Poland in July — a joint sprint with EuroPython and EuroSciPy. I'll also be keynoting there, so I hope to see many of you in the room.
+
+If you've been thinking about sprinting with us for the first time: come. We'll be there, and so will a community that genuinely wants to see you succeed.
diff --git a/content/blog/2026-06-08-pycon-us-2026-generative-ai-open-source.md b/content/blog/2026-06-08-pycon-us-2026-generative-ai-open-source.md
new file mode 100644
index 00000000..0b9712e7
--- /dev/null
+++ b/content/blog/2026-06-08-pycon-us-2026-generative-ai-open-source.md
@@ -0,0 +1,215 @@
+---
+title: 'Generative AI and open source: what PyCon US 2026 taught us about the path
+  forward'
+date: '2026-06-08'
+type: blog
+excerpt: Generative AI was a dominant theme at PyCon US 2026 — not as a buzzword,
+  but as a lived reality the Python community is actively wrestling with. From our
+  pyOpenSci open space to the Maintainers Summit BoF to Amanda Casari's powerful closing
+  keynote, the path forward remains human.
+author: Leah Wasser
+blog_topic: community
+toc: true
+comments: true
+url: "/blog/pycon-us-2026-generative-ai-open-source.html"
+lastmod: '2026-06-05'
+image:
+  src: images/blog/2026/pycon-us-2026-amanda-casari-keynote.png
+  alt: Amanda Casari delivers the closing keynote at PyCon US 2026 beside a slide
+    that reads Disposable Code Is Here to Stay, but Durable Code Is What Runs the
+    World, attributed to Charity Majors.
+---
+
+*This post is Part 4 of a 4-part series on pyOpenSci at [PyCon US 2026](https://us.pycon.org/2026/). [Part 1](/blog/pycon-us-2026-community-connection.html) covers community and connection. [Part 2](/blog/pycon-us-2026-maintainers-summit.html) covers the Maintainer Summit. [Part 3](/blog/pycon-us-2026-sprints.html) covers the sprints.*
+
+
+## Generative AI and open source: what the community is wrestling with
+
+Generative AI was a dominant theme at PyCon US 2026 — prominent enough
+to have its own dedicated conference track for the first time. But for
+pyOpenSci, the conversation wasn't about machine learning applications
+or what AI can build. It was about something more immediate: **what
+generative AI tools are doing to open source communities themselves.**
+
+How are they changing who contributes? Who reviews? Who stays? What
+does it mean for the humans who maintain these projects — often
+voluntarily, often at the edges of burnout — when the barrier to
+submitting code drops to near zero while the cost of reviewing it keeps
+climbing?
+
+*At pyOpenSci, these questions have been front of mind for a few years — shaping our [peer review policy for AI-assisted submissions](https://www.pyopensci.org/software-peer-review/our-process/policies.html#policy-for-use-of-generative-ai-llms) and our course [Ship It: Python Packaging in the Generative AI Era](/blog/ship-it-cohort-one.html). PyCon US 2026 gave us a chance to bring that work into the broader conversation.*
+
+## Where we heard it: AI conversations across PyCon US 2026
+
+AI conversations showed up everywhere — hallways, structured open spaces, and the keynote stage.
+
+**On day one, pyOpenSci hosted an open space** around a simple but hard question: *What can we do together to ease some of the pain points around generative AI in open source?* Small groups formed around specific tensions and came back with themes that will feel familiar to anyone in this space.
+
+{{< figure src="images/blog/2026/pycon-us-2026-genai-open-space.png" alt="Attendees gather around a round table during the pyOpenSci generative AI open space at PyCon US 2026, laptops open as one participant gestures while leading a small-group discussion." caption="Small-group discussion at the pyOpenSci generative AI open space on day one of PyCon US 2026." >}}
+
+**At the Maintainers Summit on Saturday,** pyOpenSci co-hosted a Generative AI BoF with [Jackie Kazil](https://github.com/jackiekazil), giving us a rare snapshot of how maintainers are actually using and feeling about these tools. Taken together, these conversations painted a remarkably consistent picture.
+
+## What the community shared
+
+Nearly two thirds of our event participants maintain projects with four or fewer
+active co-maintainers. Over 80% are using generative AI tools — across
+chat, IDEs, and the command line — for everything from generating code to
+rubber ducking through problems. Most find them useful, but few called them
+*very* useful. That pragmatism, and the frustrations underneath it, shaped
+everything that follows. **Most people that we talk to use AI tools regularly.**
+
+{{< figure src="images/blog/2026/pycon-us-2026-genai-community-discussion.png" alt="Attendees sit together around a round table at PyCon US 2026, leaning in during a focused small-group conversation about generative AI and open source." caption="Maintainers and contributors working through generative AI questions together at PyCon US 2026." >}}
+
+## What we keep hearing: themes across the community
+
+These aren't new concerns — but PyCon US 2026 made clear they are intensifying.
+One pattern worth naming upfront: usage is high across the board. Course participants
+tend to be excited — energized by what the tools make possible. Maintainers are more
+measured. They're using the same tools, but they're sitting on the other side of the
+pull request. That difference in vantage point shapes everything that follows.
+
+### The maintainer burden is growing
+
+The barrier to submitting an open source contribution has dropped dramatically. The
+barrier to reviewing one has not. More PRs, more issues, more noise — but the same
+number of hours in the day. AI-generated code can look right while being wrong in ways
+that take real expertise to catch:
+
+
+> It's like a genius who's also a toddler — which is hard to explain to the people who want us to rely on it completely.
+>
+> — PyCon US 2026 Maintainers Summit BoF attendee
+
+
+Even course participants — people actively learning and enthusiastic about these tools
+— are already noticing the gap:
+
+
+> They are helpful and increase efficiency, but they make it harder to fully understand the code.
+>
+> — Ship It: Python Packaging in the Generative AI Era participant
+
+
+The review burden isn't just a workload problem. It's a trust problem. Reviewers used
+to assume a pull request came from someone who wanted to learn and contribute. That
+assumption no longer holds. Projects are asking hard questions about how to verify
+human intent, but no consensus approach has emerged.
+
+### The contributor pipeline is at risk
+
+Open source has always had an informal mentorship model — small issues, feedback,
+mistakes, gradual responsibility. That slow, messy process is how contributors become
+maintainers. AI tools are short-circuiting that ramp. When a new contributor can
+generate a plausible-looking pull request without deeply engaging with the codebase,
+they skip the hard learning that builds judgment and intuition:
+
+
+> It's made growing long-term contributors very hard.
+>
+> — PyCon US 2026 Maintainers Summit BoF attendee
+
+
+Our course participants are sensing this from the other side:
+
+
+> Very helpful for prototyping and learning, but not for scaling production — still need a senior software engineer to make good judgement.
+>
+> — Ship It: Python Packaging in the Generative AI Era participant
+
+
+
+> [AI tools are] Somewhere in between — they can be super helpful but I think they can fool people into thinking they don't need to understand the fundamentals.
+>
+> — Ship It: Python Packaging in the Generative AI Era participant
+
+
+There's a paradox here: the people who most need AI tools to bridge skill gaps are
+often the least equipped to critically evaluate their outputs. That requires deep
+knowledge of the codebase — exactly what newer contributors are still building.
+
+### AI policy shapes community culture
+
+Projects are taking wildly different stances — outright bans, permissive approaches,
+everything in between. But policies aren't just legal governance. The policy you
+create is a signal about what kind of community you're building.
+
+The [pip-tools policy discussion](https://github.com/jazzband/pip-tools/discussions/2278)
+offered one of the clearest framings we heard all week: **"Don't let AI speak for you."**
+A ban selects for contributors who want to engage deeply with the craft of developing software. A permissive
+policy may attract volume but sacrifice quality code. Neither choice is inherently right or wrong — but the
+choice determines the type of community that forms around your project. Every project is making that choice, whether
+explicitly or not.
+
+### The power asymmetry no one is talking about
+
+Companies are requiring engineers to use these tools, setting up token consumption
+leaderboards, tying job security to AI output volume. Meanwhile the individual
+maintainer — often unpaid, often solo — absorbs the downstream costs: more
+AI-generated PRs to review, more hallucinated issues to triage, no budget for tooling
+to help manage it.
+
+
+> Cost / access asymmetry between megacorporations with infinite token budgets and individuals without them.
+>
+> — PyCon US 2026 Maintainers Summit BoF attendee
+
+
+This asymmetry isn't just economic. It's a power dynamic reshaping who open source works for.
+
+### The ethics and sustainability conversation has gone quiet
+
+A few years ago, conversations about AI in open source were full of harder questions —
+copyright, consent, environmental cost. Legal and licensing questions remain genuinely
+unresolved: what is the copyright status of AI-generated code? How do licenses and attribution
+interact with AI-assisted contributions?
+
+
+> Copyright violations — something we were all talking about before, but not much any longer...
+>
+> — PyCon US 2026 Maintainers Summit BoF attendee
+
+
+Those conversations haven't been resolved. They've just been crowded out by urgency
+and pragmatism. The fact that we stopped having them doesn't mean the questions
+were answered.
+
+## The human thread: Amanda Casari's keynote: a note on hope
+
+All of these conversations — the frustrations, the policy debates, the
+pipeline worries — could easily leave you feeling like the ground is
+shifting in ways that are hard to stand on. And for a lot of
+maintainers, it is.
+
+But PyCon US 2026 didn't end on that note.
+
+The conference closed with one of the most moving keynote addresses
+I've witnessed — Amanda Casari speaking about resilience, hope, and
+what it means to be human in an era of rapid technological change.
+
+The message wasn't naive optimism. It was a recognition that yes, this
+is hard, and yes, people are burnt out — and also that the path forward
+is a human one. Connection, care, and community are not features that
+any AI tool can replicate. They are the thing.
+
+{{< figure src="images/blog/2026/pycon-us-2026-amanda-casari-keynote.png" alt="Amanda Casari delivers the closing keynote at PyCon US 2026 beside a slide that reads Disposable Code Is Here to Stay, but Durable Code Is What Runs the World, attributed to Charity Majors." caption="Amanda Casari's closing keynote at PyCon US 2026, citing Charity Majors: 'Disposable code is here to stay, but durable code is what runs the world.'" >}}
+
+That framing landed differently after a week of conversations about
+reviewer burden and contributor pipelines and token consumption
+leaderboards. It was a reminder that the reason any of this matters is
+the people — the ones showing up, often voluntarily, often quietly, to
+maintain the tools that the rest of the world depends on.
+
+## Wrapping it all up (but not with a pretty bow just yet)
+
+AI is a tool. A powerful one, with real implications for how open
+source works. But the humans — the ones showing up, building trust,
+passing knowledge on — that's the irreplaceable part.
+
+The conversations at PyCon US this year gave me genuine hope. Not because
+we solved anything, but because the community is engaging with these
+questions seriously, honestly, and together. That's how hard things
+get figured out.
+
+I'll be bringing these conversations to the UN Open Source Summit,
+EuroPython (where I'll be keynoting), EuroSciPy, and RSECon in
+September. I hope to see many of you along the way.
diff --git a/content/blog/_index.md b/content/blog/_index.md
new file mode 100644
index 00000000..4486fe25
--- /dev/null
+++ b/content/blog/_index.md
@@ -0,0 +1,10 @@
+---
+title: "pyOpenSci Blog"
+type: blog
+paginate: 9999
+description: >-
+  Updates from across pyOpenSci — accepted packages, peer review, training,
+  and the community behind the code.
+header:
+  overlay_image: images/blog/headers/pycon-us-2026-header.png
+---
diff --git a/content/events/2024-04-29-create-your-first-python-package-pyopensci-online-workshop.md b/content/events/2024-04-29-create-your-first-python-package-pyopensci-online-workshop.md
new file mode 100644
index 00000000..74e318b6
--- /dev/null
+++ b/content/events/2024-04-29-create-your-first-python-package-pyopensci-online-workshop.md
@@ -0,0 +1,53 @@
+---
+title: 'pyOpenSci Online Workshop: Create your first Python package'
+date: '2024-04-29'
+lastmod: ''
+excerpt: Python packaging can be tricky to navigate. pyOpenSci will lead a pilot workshop
+  on creating your first Python package. The goal of this workshop is to help scientists
+  learn how to package and make code installable and shareable. Read on to learn more!
+image:
+  src: images/headers/pyopensci-sustainability.png
+  alt: 'pyOpenSci Online Workshop: Create your first Python package'
+event:
+  start_date: '2024-04-29'
+  location: Online
+  event_type: training
+aliases:
+- "/events/april-2024-create-python-package-pyopensci-online-workshop.html"
+---
+
+## Create your first Python package: make your Python code easier to share and use
+
+* **What:** A hands-on workshop, titled: [Create Your First Python Package: Make Your Python Code Easier to Share and Use](https://cfp.scipy.org/2024/talk/QT9GBY/)
+* **Where:** [SciPy 2024](https://www.scipy2024.scipy.org/), Ballroom B/C
+* **When:** Tuesday, July 9th, 2024, from 13:30--17:30 Pacific
+* Resources:
+  *  [**Workshop GitHub repository:**](https://github.com/pyOpenSci/code-to-module-workshop/)
+  *  [**pyOpenSci demo package:**](https://github.com/pyOpenSci/pyosPackage)
+
+## Event overview
+
+## How to enroll
+<figure>
+    <a href="/images/blog/2024/april/pyos-code-to-mod.png">
+    <img src="/images/blog/2024/april/pyos-code-to-mod.png" style="max-width:100%" alt="A line art robot standing in a field of purple flowers. The text reads 'From Python Code to Module, a live, online workshop with pyOpenSci, Thursday, April 25th 2024'.">
+    </a>
+    <figcaption>
+      Tickets for our "From Python Code to Module" workshop are selling fast - get yours today!
+    </figcaption>
+</figure>
+
+If you’re interested in participating in our first paid, online, real-time training, sign up for our upcoming workshop: [“From Python Code to Module”](https://www.eventbrite.com/e/879586546037?aff=oddtdtcreator). This three hour course is intended for individuals who have experience writing Python code and Python functions, and will be taught by pyOpenSci’s Executive Director and founder, [Leah Wasser](https://github.com/lwasser). Leah has over 20 years of experience teaching data-intensive science with an emphasis helping scientists work through the pain points of working with different types of data, and puts an incredible amount of care and attention into ensuring each learner is successful in their educational goals. This is definitely a workshop you don’t want to miss!
+
+In this workshop, Leah will cover:
+
+- How to identify and explain the use of the basic components of a Python package: (a specific directory structure, an __init__.py file, a pyroject.toml file and some code).
+- Creating a basic python package that allows you to install your code into a local Python environment.
+- Installing your package in editable mode into a Python environment.
+
+She will also briefly discuss how LLM’s can be used to support tasks such as documenting and formatting your code to improve usability and maintainability. While also considering the ethical and logistical challenges, pitfalls and concerns associated with using AI-based tools in software development.
+
+The course will take place on Thursday, April 25th, from 10AM–1PM Mountain time, and use the Spatial Chat platform. Tickets are $10, and can be purchased on [the workshop’s Eventbrite page](https://www.eventbrite.com/e/from-python-code-to-module-tickets-879586546037?aff=oddtdtcreator). The class size is capped at 35, and tickets are selling fast–we hope to see you there!
+
+## Connect with us!
+You can stay up-to-date with all things pyOpenSci by following us on [LinkedIn](https://www.linkedin.com/company/pyopensci) and [Fosstodon](https://fosstodon.org/@pyOpenSci). And if you’re interested in our weekly newsletter where we share news, blog posts, and monthly updates, [subscribe on LinkedIn](https://www.linkedin.com/newsletters/pyopensci-newsletter-7179551305344933888!)
diff --git a/content/events/2024-07-13-create-your-first-python-package-scipy-2024.md b/content/events/2024-07-13-create-your-first-python-package-scipy-2024.md
new file mode 100644
index 00000000..b936ff08
--- /dev/null
+++ b/content/events/2024-07-13-create-your-first-python-package-scipy-2024.md
@@ -0,0 +1,282 @@
+---
+title: 'Workshop: pyOpenSci @ SciPy 2024--Create your first Python package'
+date: '2024-07-13'
+lastmod: ''
+excerpt: Python packaging can be tricky to navigate. pyOpenSci will lead a workshop
+  on creating your first Python package at SciPy 2024. The goal of this workshop is
+  to help scientists learn how to package and make code installable and shareable.
+  Read on to learn more!
+image:
+  src: images/headers/scipy-2024-workshop.png
+  alt: 'Workshop: pyOpenSci @ SciPy 2024--Create your first Python package'
+event:
+  start_date: '2024-07-13'
+  location: Online
+  event_type: training
+aliases:
+- "/events/create-first-python-package-scipy-2024.html"
+---
+
+## Create your first Python package: make your Python code easier to share and use
+
+* **What:** A hands-on workshop, titled: [Create Your First Python Package: Make Your Python Code Easier to Share and Use](https://cfp.scipy.org/2024/talk/QT9GBY/)
+* **Where:** [SciPy 2024](https://www.scipy2024.scipy.org/), Ballroom B/C
+* **When:** Tuesday, July 9th, 2024, from 13:30--17:30 Pacific
+* Resources:
+  *  [**Workshop GitHub repository:**](https://github.com/pyOpenSci/code-to-module-workshop/)
+  *  [**pyOpenSci demo package:**](https://github.com/pyOpenSci/pyosPackage)
+
+## Event overview
+
+Creating code that can be shared and reused is the gold-standard of open science. But the tools and skills to share your code can be tricky to learn. In this hands-on tutorial, you’ll learn how to turn your code into an installable Python module (a file containing Python code that defines functions, classes, and variables), that can be shared with others. We will provide pre-built code and module examples for each step of the tutorial to help make it more beginner-friendly, but you will need some basic Python skills to get the most out of this session.
+
+You will leave this tutorial understanding how to:
+
+* Create code that can be installed into different environments
+* Use [Hatch](https://hatch.pypa.io/latest/) as a workflow tool, making setup and installation of your code easier
+* Use Hatch to publish your package to the test version of [PyPI](https://pypi.org/)
+
+## Pre-requisites: What you need to know
+
+* Basic Python programming
+* How to write functions in Python
+* How to use a Python environment manager of your choosing
+
+## What you should have installed on your computer prior to the workshop
+
+* Python
+* An environment manager
+* Hatch
+* Shell (e.g. terminal on MAC or GitBash on Windows)
+
+[<i class="fas fa-hand-point-right"></i> Click here for setup instructions.](https://github.com/pyOpenSci/code-to-module-workshop/tree/cf9e7d9937c10bde9ee03075ebe78eb7a605f549)## Workshop agenda
+
+<table width="100%">
+  <tbody>
+    <tr>
+      <td colspan="2"><strong>Hour one:</strong> The structure of an installable module.</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td rowspan="5" width="25%" style="vertical-align: top;"><strong>Key takeaways</strong><ul>
+          <li>The purpose of the __init__.py file</li>
+          <li>How workflow tools such as Hatch can be useful when making code installable.</li>
+        </ul></td>
+    </tr>
+    <tr>
+      <td><strong>Breakdown</strong></td>
+    </tr>
+      <td><strong>0-15 minutes:</strong> Here we will get to know each other. I’ll also briefly introduce pyOpenSci and the work that we are doing in open science education and training space.</td>
+    <tr>
+      <td><strong>15-30 minutes, interactive discussion:</strong> Here, we’ll discuss why shareable code is important. And we’ll explore some best practices for making code easier to work with. I’ll also introduce Hatch as a workflow tool that streamlines tasks.</td>
+    </tr>
+    <tr>
+      <td><strong>30-60 minutes, hands-on:</strong> You will take an existing script and turn it into an installable module. You are welcome to use the provided scripts for this. If you are more comfortable with Python, then you can also bring your own script with you and work on it during the workshop.</td>
+    </tr>
+  </tbody>
+</table>
+<br>
+<table width="100%">
+  <tbody>
+    <tr>
+      <td colspan="2"><strong>Hour two:</strong> Everything you need to know about the <code>pyproject.toml</code> file & project metadata.</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td rowspan="5" width="25%"><strong>Breakdown</strong></td>
+    </tr>
+      <td><strong>0-15 minutes, interactive discussion:</strong> Here you’ll learn about the pyproject.toml and how it’s used to document dependencies, and metadata for your project.</td>
+    <tr>
+      <td><strong>15-30 minutes:</strong> A short break to stretch your legs and get a drink.</td>
+    </tr>
+    <tr>
+      <td><strong>30-60 minutes, hands-on:</strong> In the hands-on part of this hour, you will modify your <code>pyproject.toml</code> file with required dependencies needed to run your code. You will also learn how to install your code in interactive or development mode using both pip and Hatch. Interactive mode will allow you to dynamically update your code and test it locally without reinstalling it. Finally, you will take your shiny new Python module for a test drive in your favorite Python environment.</td>
+    </tr>
+  </tbody>
+</table>
+<br>
+<table width="100%">
+  <tbody>
+    <tr>
+      <td colspan="2"><strong>Hour three:</strong> The power of metadata and instructions for you, your future self & your colleagues.</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td rowspan="5" width="25%"><strong>Breakdown</strong></td>
+    </tr>
+      <td><strong>0-15 minutes, interactive discussion:</strong> In this part of the tutorial we’ll discuss the power of documentation when sharing code and also for you when you have to update things in the future.</td>
+    <tr>
+      <td><strong>15-50 minutes, hands-on:</strong> Here you will <a href="https://www.pyopensci.org/python-package-guide/tutorials/add-readme.html">create a README file</a> that helps users of your module understand how to install it and how to get started using it. You will also add <a href="https://www.pyopensci.org/python-package-guide/documentation/write-user-documentation/document-your-code-api-docstrings.html">docstrings</a> to your code. See how docstrings are useful as “hints” when coding real time. Optional: if you are speedy, you can also delve into <a href="https://www.pyopensci.org/python-package-guide/documentation/write-user-documentation/document-your-code-api-docstrings.html#adding-type-hints-to-your-docstrings">typing</a> your code on your own. However, we won’t directly cover typing in this tutorial.</td>
+    </tr>
+    <tr>
+      <td><strong>50-60 minutes:</strong> Break</td>
+    </tr>
+  </tbody>
+</table>
+<br>
+<table width="100%">
+  <tbody>
+    <tr>
+      <td colspan="2"><strong>Hour four:</strong> Publishing and sharing your code.</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td rowspan="5" width="25%"><strong>Breakdown</strong></td>
+    </tr>
+      <td><strong>0-15 minutes, interactive discussion:</strong> Here we will discuss what it means to “<a href="https://www.pyopensci.org/python-package-guide/tutorials/publish-pypi.html">publish</a>” code. We will also discuss other important elements such as license files and codes of conduct if you intend to turn your code into a published <a href="https://www.pyopensci.org/python-package-guide/tutorials/intro.html">package</a>.</td>
+    <tr>
+      <td><strong>15-45 minutes, hands-on:</strong> Publishing to PyPI vs. installing from Github. Those who’d like to follow along interactively can do so here. However, if your brain is tired, sit back and learn how to build your module into a package distribution using Hatch. And then we will give you all of the tools needed to <a href="https://www.pyopensci.org/python-package-guide/tutorials/publish-pypi.html">publish to the test version of PyPI</a>.</td>
+    </tr>
+    <tr>
+      <td><strong>45-60 minutes:</strong> Wrap up, answer any questions, and provide feedback on the session.</td>
+    </tr>
+  </tbody>
+</table>
+
+## Hatch & Python
+
+If you already have a working version of Python on your computer, then you are in good shape! **If you don’t have Python installed on your computer, then Hatch will install Python for you when you install it following the instructions below.**
+
+## Install Hatch
+
+_These instructions were adapted from the [Introduction to Hatch](https://www.pyopensci.org/python-package-guide/tutorials/get-to-know-hatch.html) section of the [pyOpenSci Python Packaging Guide](https://www.pyopensci.org/python-package-guide/)._
+
+### For Mac users
+
+_These instructions are for installing Hatch using the GUI installer. If you’d prefer to use the command line installer, please see the [Hatch documentation](https://hatch.pypa.io/latest/install/#command-line-installer)._
+
+1. In your browser, download the `.pkg` file: [hatch-universal.pkg](https://github.com/pypa/hatch/releases/latest/download/hatch-universal.pkg)
+2. Run the downloaded file and follow the on-screen instructions to install Hatch.
+3. Restart your terminal if it is already open.
+4. To verify that shell can find and run the `hatch` command, run:
+    1. `hatch --version` (in your Terminal / shell).
+
+### For Linux users
+
+_For Linux users, the easiest way to install Hatch is to use pipx which can be installed using apt install. Note: if you prefer to use a tool other than pipx, please refer to the [Hatch documentation](https://hatch.pypa.io/latest/) for more information_
+
+* Install Hatch from the command line using [pipx](https://pipx.pypa.io/stable/):
+
+```bash
+# First install pipx using apt install
+>> apt install pipx
+# Then use pipx to install hatch
+>> pipx install hatch
+```
+
+### For Windows users
+
+_These instructions are for installing Hatch using the GUI installer. If you’d prefer to use the command line installer, please see the [Hatch documentation](https://hatch.pypa.io/latest/install/#command-line-installer_1)._
+
+1. In your browser, download the `.msi` file: [hatch-x64.msi](https://github.com/pypa/hatch/releases/latest/download/hatch-x64.msi)
+2. Run your downloaded file and follow the on-screen instructions.
+3. Restart your terminal if it was already open.
+4. To verify that the shell can find and run the `hatch` command in your `PATH`, in your terminal run:
+    1. `hatch --version`
+
+### Configure Hatch (all systems)
+
+After installing Hatch, it’s useful to customize the Hatch configuration. The
+configuration allows you to specify things like the default name and email to
+use in your package’s metadata. If you don’t configure Hatch, you can always
+edit files later! However your Hatch package outputs might look a bit different
+than the ones in the workshop. (This is OK!)
+
+Hatch stores your configuration information in a `config.toml` file.
+
+While you can update the `config.toml` file through the command line, it might
+be easier to look at it and update it in a text editor if you are using it for
+the first time.
+
+1. Open and edit your `config.toml` file by either:
+    1. Running `hatch config explore` in your shell, which will open up a directory window that will allow you to double click on the file and open it in your favorite text editor.
+    2. Alternatively, you can retrieve the location of the Hatch config file by running `hatch config find` in your shell.
+2. Update your email and name
+    3. Once the file is open, update the [template] table of the `config.toml` file with your name and email. This information will be used in any `pyproject.toml` metadata files that you create using Hatch.
+3. Set tests to `false`
+
+    _While tests are important, setting the tests configuration in Hatch to true will create a more complex pyproject.toml file. We won’t be creating tests in this workshop._
+
+    Set tests to `false` in the `[template.plugins.default]` table.
+
+Your config file should look something like this:
+
+```toml
+mode = "local"
+project = ""
+shell = ""
+
+[dirs]
+project = []
+python = "isolated"
+data = "/Users/leahawasser/Library/Application Support/hatch"
+cache = "/Users/leahawasser/Library/Caches/hatch"
+
+[dirs.env]
+
+[projects]
+
+[publish.index]
+repo = "main"
+
+[template]
+name = "Leah Wasser"
+email = "leah@pyopensci.org"
+
+[template.licenses]
+headers = true
+default = [
+    "MIT",
+]
+
+[template.plugins.default]
+tests = false
+ci = false
+src-layout = true
+
+[terminal.styles]
+info = "bold"
+success = "bold cyan"
+error = "bold red"
+warning = "bold yellow"
+waiting = "bold magenta"
+debug = "bold"
+spinner = "simpleDotsScrolling"
+```
+
+Note: for future packages you may want to enable both CI and tests. This
+configuration is to simplify things for our beginner-friendly tutorial.
+
+4. Close the config file and run `hatch config show`
+
+    `hatch config show`
+
+This command prints out the contents of your config.toml file in your shell.
+Look at the values and ensure that your name and email are set and also make
+sure that `tests=false`.
+
+## Useful Commands
+
+### Conda environments
+
+* **Create environment:** `conda create -n env_name python=3.11`
+* **Activate environment:** `conda activate env_name`
+* **Leave environment:** `conda deactivate`
+
+### Venv environments
+
+Create environment
+
+* `python -m venv env_name`
+* Activate_windows: `env_name\Scripts\activate`
+* Activate MAC / LINUX: `source env_name/bin/activate`
+* Leave environment: `deactivate`
+
+## Helpful links
+
+* Our [example Python package repo, `pyosPackage`](https://github.com/pyOpenSci/pyosPackage), that goes along with pyOpenSci tutorials.
+* [Workshop information on the SciPy 2024 website](https://cfp.scipy.org/2024/talk/QT9GBY/).
+
+## <i class="fa-solid fa-link"></i> Connect with pyOpenSci
+
+Stay up-to-date with all things pyOpenSci by following us on [LinkedIn](https://linkedin.com/company/pyopensci) and [Fosstodon](https://fosstodon.org/@pyOpenSci). If you’re interested in our weekly newsletter where we share news, blog posts, and monthly updates, [subscribe on LinkedIn](https://www.bit.ly/pyOSNewsletter).
diff --git a/content/events/2024-10-28-pyopensci-fall-festival.md b/content/events/2024-10-28-pyopensci-fall-festival.md
new file mode 100644
index 00000000..bfc3c08f
--- /dev/null
+++ b/content/events/2024-10-28-pyopensci-fall-festival.md
@@ -0,0 +1,253 @@
+---
+title: pyOpenSci Fall Festival 2024
+date: '2024-10-28'
+lastmod: '2024-09-26'
+excerpt: Join us for pyOpenSci's inaugural Fall Festival, happening October 28 - November
+  1, 2024! This multi-day training event brings together scientists and Pythonistas
+  for inspiring talks, hands-on workshops, and office hours to help you grow your
+  open science and open source skills. Whether you're a new or experienced Pythonista,
+  there's something for you!
+image:
+  src: images/headers/pyopensci-sustainability.png
+  alt: pyOpenSci Fall Festival 2024
+event:
+  start_date: '2024-10-28'
+  end_date: '2024-11-01'
+  location: Online using Spatial Chat
+  event_type: community
+aliases:
+- "/events/pyopensci-2024-fall-festival.html"
+---
+
+## <i class="fa-regular fa-heart"></i> Announcing the pyOpenSci Fall Festival!
+
+
+
+Happening October 28--November 1, 2024, the pyOpenSci Fall Festival is an online community training and networking event designed to empower scientists with in-demand open science skills. Our goals for the Fall Festival are to:
+
+* empower you with technically-relevant open science skills,
+* call attention to and celebrate new and upcoming tools that support open reproducible science
+* build community, and
+* help raise funds for pyOpenSci operations that allow us to continue supporting community work.
+
+Interested? Read on to learn more!
+
+## <i class="fa-regular fa-file-lines"></i> pyOpenSci's 2024 Fall Festival logistics:
+
+* **What:** An online community training and networking event
+* **Where:** Online using SpatialChat
+* **When:** Monday, October 28--Friday, November 01, 2024
+* **Who:** If you are a scientist, a researcher, a student, or anyone interested in writing better, cleaner code that can be installed into different environments and shared, then this event is for you!
+* **Cost - Day 1 Keynote talks:** free.
+* **Cost- workshops:** $350--$625, with scholarships available
+
+## pyOpenSci's Fall Festival registration, cost, and scholarship information
+
+<div style="text-align: center;" markdown="1">
+
+[--> Click Here to Register now for the pyOpenSci Open Science Fall Festival <--](https://www.eventbrite.com/e/pyopensci-fall-festival-2024-registration-1000762657047)</div>
+
+**Important:** The agenda items in EventBrite are listed in UTC-6:00- This is an EventBrite bug. If you need clarification on start times, please email us at [media@pyopensci.org](mailto:media@pyopensci.org).
+{: .notice .notice--primary }
+
+### Pricing tiers
+
+We've created several pricing tiers to make the Fall Festival accessible to as many people as possible.
+
+#### Day one - October 28, 2024: Keynote talks
+
+Keynote talks are free for anyone to attend. Register now before we fill up!
+
+| Time | Speaker | Topic |
+|----------|----------|----------|
+| 8:30am - 8:40 AM UTC-6 | Leah Wasser | Meeting room opens |
+| 8:40am - 8:55 AM UTC-6 | Leah Wasser | Welcome to the Fall Festival - pyOpenSci, open source and open science |
+| 9:00am - 9:50 AM UTC-6 | Eric Mah | Open Science, biomedical work and LLMs |
+| 10:00am - 10:50 AM UTC-6 | Melissa Mendoça  | The value of open source for open science |
+| 11:00am - 11:50 PM UTC-6 | Rowan Crocket  | Catalyzing how scientists publish using MystMarkdown  |
+
+
+#### Days 2-4 - 29 October - November 1, 2024: Technical Workshops
+
+The general schedule for each days' event is below:
+
+| Time | Event |
+|----------|----------|----------|
+| 8:45am - 1:00 PM UTC-6 | Online Training |
+| 2:00pm - 4:00 PM UTC-6 | Online Office Hours |
+
+Friday's event will begin at 8:30 to support 2 speakers.
+
+You can register for a single-day workshop or the full event. Workshop registration includes office hours each day for more one-on-one help in the afternoon.
+
+| Registration Type  | Cost |
+|----------|----------|
+| Day One Keynote Talks - October 28 2024 | Free | |
+| Full 4-day Workshop: Student | $350 | |
+| Full 4-day Workshop: Standard | $475 | |
+| Full 4-day Workshop: Corporate | $625 | |
+|  |  | |
+| Single Day Workshop: Student | $100 | |
+| Single Day Workshop: Standard | $150 | |
+| Single Day Workshop: Corporate | $200 | |
+
+
+### Scholarships
+
+If you are financially unable to attend pyOpenSci's Fall Festival, you can apply for a scholarship using [this form](https://www.surveymonkey.com/r/pyOSFF2024). We will be accepting scholarship applications through October 24th, but review will begin on October 15, with priority given to early applications.
+
+[Click to apply for a scholarship.](https://www.surveymonkey.com/r/pyOSFF2024)## pyOpenSci Fall Festival events
+
+Our Fall Festival is a series of events that make it easy to connect with others, listen to inspiring talks, and learn at a pace that is comfortable for you.
+
+### Monday, October 28th: Kickoff and keynotes
+
+Join us on Monday, October 28, for a morning of impactful keynote talks from 3 incredible speakers.
+
+These Fall Festival keynote talks are free for anyone to attend. They will be recorded and published on the pyOpenSci YouTube channel after the event.
+
+Our speakers for the Fall Festival are:
+
+* [Eric Ma](https://ericmjl.github.io/)
+* [Melissa Mendoça](https://github.com/melissawm)
+* [Rowan Cockett](https://curvenote.com/mission)
+
+We'll also hold "Day 0" office hours for all registered workshop attendees. Drop into our Day 0 office hours to say hello, get used to using our online platform, Spatial Chat, and get help with any computer setup issues you might have before the workshops begin.
+
+We want to set you up for learning success!
+
+#### Keynote speaker bios
+
+**[Eric Ma](https://ericmjl.github.io/)**
+As Senior Principal Data Scientist at [Moderna](https://www.modernatx.com/en-US) Eric leads the Data Science and Artificial Intelligence (Research) team to accelerate science to the speed of thought. Prior to Moderna, he was at the [Novartis Institutes for Biomedical Research](https://www.novartis.com/research-and-development) conducting biomedical data science research with a focus on using Bayesian statistical methods in the service of discovering medicines for patients. Prior to Novartis, he was an Insight Health Data Fellow in the summer of 2017 and defended his doctoral [thesis](https://ericmjl.github.io/thesis/) in the [Department of Biological Engineering](https://be.mit.edu/) at [MIT](https://web.mit.edu/) in the spring of 2017.
+
+Eric is also an open-source software developer and has led the development of [pyjanitor](https://github.com/pyjanitor-devs/pyjanitor), a clean API for cleaning data in Python, and [nxviz](https://github.com/ericmjl/nxviz), a visualization package for NetworkX. He is also on the core developer team of NetworkX and PyMC. In addition, he gives back to the community through [code contributions](https://ericmjl.github.io/open-source/), [blogging](https://ericmjl.github.io/blog/), [teaching](https://ericmjl.github.io/teaching/), and [writing](https://ericmjl.github.io/books/).
+
+His personal life motto is found in the Gospel of Luke 12:48.
+
+**[Melissa Mendoça](https://github.com/melissawm)**
+I am a Senior DevEx Engineer at Quansight, working on NumPy, SciPy and other open source projects. I care deeply about teaching, mentoring, and have been involved in the Python community for some time. You can find most of my talk slides here on github or in [my website](https://melissawm.github.io/); feel free to use those according to the licenses stated in each repo/presentation.
+
+💬 Ask me about [NumPy](https://numpy.org/), SciPy, [napari](https://napari.org/stable/), Fortran, LaTeX, mathematical optimization, numerical linear algebra, [Contributor Experience](https://contributor-experience.org/).
+
+**[Rowan Cockett](https://curvenote.com/mission)**
+
+Rowan is the CEO and founder of [Curvenote](https://curvenote.com), where we build tools to free science from static PDF documents such that the scientific community can share more interactive, reproducible, and richly-linked scientific content. Curvenote provides an all-in-one publishing platform for researchers, societies and institutes, with a focus on computational research.
+
+Rowan is also on the steering-council for JupyterBook and MyST Markdown, which is part of Project Jupyter and provides widely used open-source tools for authoring and sharing scientific content. Rowan has a Ph.D. in computational geophysics from the University of British Columbia (UBC). While at UBC, Rowan helped start [SimPEG](https://simpeg.xyz), a large-scale simulation and parameter estimation package for geophysical processes (electromagnetics, fluid-flow, gravity, etc.), which is used in industry, national labs, and universities globally.
+
+Rowan has won multiple awards for innovative dissemination of research and open-educational resources, including a geoscience modeling application, Visible Geology, that has been used by more than a million geoscience students to interactively explore conceptual geologic models. In his previous role as the VP of Cloud Architecture at Seequent, Rowan ran a large software team working on computational software platforms, visualization tools, and version control systems for geoscientists.
+
+### Tuesday, October 29th--Friday, November 01st - Technical workshops
+
+Every workshop day of the pyOpenSci Fall Festival will follow a similar format.
+
+*Some days will kick off with an inspirational and technically related talk*
+
+All days will include:
+* A hands-on, interactive workshop with highly-qualified instructors and a group of knowledgeable, dedicated support volunteers.
+* A lengthy lunch break
+* Optional afternoon office hours, where registered attendees can get further help and support with the topics covered during the morning workshop
+
+## pyOpenSci's Fall Festival workshop agendas
+
+### Tuesday, October 29th: Write modular, clean code
+
+When developing a data processing workflow, it's tempting to start at the "top" and write each line of code needed to process your data. Or you may ask a LLM to write your code for you. However, this approach often makes maintaining code less efficient and complex. In this workshop, you will learn how to think about developing the code needed to process your data more efficiently.
+
+You will learn how to:
+
+1. Describe and organize the steps needed to create your workflow using pseudocode. Pseudocode is not only helpful in organizing your workflow; it is also what an AI-coding assistant tool such as ChatGPT or GitHub CoPilot requires to build a workflow for you.
+1. Create expressive, human-readable variable and function names to make your code easier to read and maintain.
+1. Create well-documented functions to perform repeated tasks. Functions allow you to make your code more modular and reduce the number of variables your code produces and stores in memory. LLMs can be helpful here, too, once you understand what you need to accomplish.
+1. Add tests and checks to your function to ensure your workflow runs as expected and handles messy data issues gracefully.
+1. Organize your workflow into modules, functions, and scripts that run and process your data.
+
+This workshop will help you transform messy, hard-to-manage code into clean, efficient, and reusable Python workflows. Over 3-4 hours, you'll learn the core concepts of refactoring your code so that it's easier to understand, maintain, and share with others. We'll start by looking at how to break down repetitive tasks into smaller, reusable functions or objects. Refactoring will make your code more organized and save you time in the long run by reducing the amount of repetitive work.
+
+Next, we'll focus on writing code that's functional and easy to read. Using clear, descriptive names and well-structured logic, you'll learn to write code that others (and your future self) can easily understand and modify. We'll also cover how to manage your code's use of memory and compute power, ensuring that your scripts run efficiently. Once the core concepts are understood, you will use LLM's to make your code more modular and easier to read and maintain. You will add functions needed to process your data reusable into a new Python module.
+
+By the end of the workshop, you'll have refactored your code into a well-organized module. This module will then serve as the foundation for the second workshop, where you'll learn how to turn it into a fully-fledged Python package that you can install and reuse across different projects and in different Python environments. This step-by-step approach will equip you with the skills to create robust, maintainable Python workflows for processing, visualizing, and analyzing data.
+
+### Wednesday, October 30th: Create a Python package
+
+**Summary**
+
+In the second Fall Festival workshop, you'll learn how to turn a Python module and script into an installable package. Optionally, you'll also learn how to add a script to a Python package so you can call it at the command line using Python package entry points. We will provide a module and script from Workshop 1 that you can use to complete Workshop 2.
+
+Packaging your code makes sharing, reproducing, and reusing your work easier—a fundamental element of open science. Packaging your Python code ensures it can be easily reused across different environments and workflows, whether locally, in the cloud, or when collaborating with others. Packaged code simplifies your work by allowing you to reuse your code in various projects. It also enhances your ability to share your tools with the broader scientific community, making your contributions more accessible and impactful.
+
+In the first workshop of the pyOpenSci Fall Festival, you learned how to turn a Python script into a maintainable command-line script that imports modular functionality from a well-written Python module. You can use the work you did in workshop 1 in this workshop.
+{: .notice .notice--info }
+
+In this workshop, you'll learn how to use the pyproject.toml file, a modern and straightforward way to define your package's metadata, dependencies, and setup instructions. We'll also introduce Hatch, a powerful tool that simplifies the packaging process, ensuring you can install your package into any Python environment with a single command. By the end of the workshop, you'll have the skills to transform your code into a Python package ready for distribution and use by others.
+
+This workshop will help you make your code more accessible and reproducible. You'll leave with a fully functional Python package created from your own module. Whether you're new to Python packaging or looking to refine your skills, this workshop will equip you with the tools and knowledge to distribute your scientific code efficiently and effectively.
+
+### Thursday, October 31st: Share your code
+
+**Summary**
+
+In Workshop 3: share your code, you will learn the essential steps to make your Python packages publicly available and easily installable. You'll start by setting up your package on GitHub, enabling others to `pip install` it directly. You'll also learn how to integrate Zenodo to assign a DOI to your package, allowing it to be cited in academic works, with easy updates for each new release. If there is time, the workshop will guide you through creating package releases, setting up GitHub Actions to automate the publication process to PyPI, and using Test PyPI with Hatch to ensure everything works smoothly before going live. Finally, you will learn how to publish your package to (test) PyPI and conda-forge as a stepping stone to publishing to the real PyPI. While the workshop will introduce the process of creating a Conda-Forge recipe, the actual publication to Conda-forge will be something you can explore further on your own
+
+By the end of this workshop, you know how to share your Python packages with the broader community effectively. You'll understand how to automate critical aspects of the release process, making it easier to maintain and update your packages over time. Overall, you'll leave this workshop empowered to contribute your code to the open-source ecosystem in a way that is accessible, citable, and well-maintained.
+
+### Friday, November 1: Reproducible reports and presentations with Quarto and Great Tables
+
+#### Morning talks
+
+We'll be opening this session with two incredible talks on Quarto from [James Balamuta](https://github.com/coatless) and [George Stagg](https://gws.phd/)!
+
+#### Workshop
+
+If you want to use data to make decisions, answer scientific questions, inform people on issues or participate in data-driven journalism, just conducting the data analysis is not enough. Effective communication requires weaving together narrative text and code to produce elegantly formatted output that people can easily read and understand. In this workshop, you'll learn how to use [Quarto](https://quarto.org/) for reports and presentations and Great Tables for elegantly formatted tables to convey information that's great for the readers, and easy for you to create too.
+Quarto is an open source tool based on Pandoc that allows you to create and publish reproducible, production-quality articles, presentations, dashboards, websites, blogs, and books in HTML, PDF, MS Word, ePub, and more, right from your Jupyter notebooks.
+
+With Great Tables you can make wonderful-looking tables in Python. Great Tables is an open source Python package that lets you mix and match things like a header and footer, attach a stub (which contains row labels), arrange spanner labels over top of the column labels, and much more. Not only that, but you can format the cell values in a variety of awesome ways.
+
+## Speakers and instructors
+
+*We'll continue to update this section with more information as we confirm speakers and instructors for the event!*
+
+* [Leah Wasser](https://www.leahwasser.com/)
+* [Eric Ma](https://ericmjl.github.io/)
+* [Melissa Mendoça](https://github.com/melissawm)
+* [Rowan Cockett](https://curvenote.com/blog/myst-markdown-pyopensci-2024)
+* [Carol Willing](https://www.willingconsulting.com/)
+* [Jeremiah Paige](https://github.com/ucodery)
+* [James Balamuta](https://github.com/coatless)
+* [George Stagg](https://gws.phd/)
+* [Tracy Teal](https://tkteal.com/)
+* [Rich Iannone](https://github.com/rich-iannone)
+
+## Volunteers
+
+Are you interested in volunteering? Please contact [fallfestival@pyopensci.org](mailto:fallfestival@pyopensci.org) to stay up to date about any event needs!
+
+## FAQ
+
+**How do I apply for a scholarship?**
+
+If you are financially unable to attend pyOpenSci's Fall Festival, you can apply for a scholarship using [this form](https://www.surveymonkey.com/r/pyOSFF2024). We will be accepting scholarship applications through October 24th, but review will begin on October 15, with priority given to early applications.
+
+**Can I register for a single day?**
+
+Yes! You can register for the entire event or buy tickets for one, two, or three days. To stay up to date on any changes to our ticketing for the pyOpenSci Fall Festival, be sure to follow us on [Fosstodon](https://fosstodon.org/@pyOpenSci) or [LinkedIn](https://linkedin.com/company/pyopensci).
+
+**What if I purchased a ticket but can no longer attend?**
+
+All refunds are processed through Eventbrite, and will be accepted until October 21, 2024. You will receive a refund for the price of your ticket minus any service fees.
+
+If you purchased your ticket after October 21, 2024 you will be ineligible for a refund, however you may donate it to another learner. To do so, please email [fallfestival@pyopensci.org](mailto:fallfestival@pyopensci.org).
+
+**How will pyOpenSci use my registration information?**
+
+pyOpenSci will use your registration information to send you information related to the Fall Festival, as well as to send you both pre- and post-surveys related to the Fall Festival.
+
+**How can I help promote the Fall Festival?**
+
+We would love for you to share your excitement and enthusiasm with your peers, both in-person and on social media! You're welcome to use any of the images that we've shared on social media related to the event. We'd also love it if you tag us in anything that you share!
+
+**Will the Fall Festival workshops be recorded?**
+
+We will only record the keynote talks on Monday, October 28, 2024. The additional talks and workshops will not be recorded. If workshop instructors share their content online, we will be sure to share the relevant links both here and on social media.
diff --git a/content/events/2025-05-05-community-call-contribute-open-source.md b/content/events/2025-05-05-community-call-contribute-open-source.md
new file mode 100644
index 00000000..f1e4d917
--- /dev/null
+++ b/content/events/2025-05-05-community-call-contribute-open-source.md
@@ -0,0 +1,43 @@
+---
+title: 'pyOpenSci Community Call 5 May 2025 @ 10 am Mountain Time: Right Time, Right
+  Community: My OSS Journey'
+date: '2025-05-05'
+lastmod: '2025-04-22'
+excerpt: Join pyOpenSci for a special Open Source Voices session! Learn about Pavithra's
+  open source journey and what helped her grow into a contributor and maintainer in
+  the open source world.
+image:
+  src: images/headers/pyopensci-sustainability.png
+  alt: 'pyOpenSci Community Call 5 May 2025 @ 10 am Mountain Time: Right Time, Right
+    Community: My OSS Journey'
+event:
+  start_date: '2025-05-05'
+  location: Online
+  event_type: community
+aliases:
+- "/events/pyopensci-community-call-may-2025.html"
+---
+
+## <i class="fa-regular fa-heart"></i> Join us for a talk on contributing to open source!
+Open Source Voices: *A community call for learning, sharing, and growing together*
+
+* **When:** Monday, 5 May 2025 @ 10:00-10:50 AM Mountain Time [(click this link to find the time and date in your timezone)](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+Source+Voices%3A+pyOpenSci+Contribute+Week&iso=20250505T10&p1=75&ah=1)
+* **Where:** Online via Google Meet (Register for link)
+* **Speaker:** Pavithra Eswaramoorthy, Developer Advocate, Quansight
+
+[<i class="fa-regular fa-circle-right"></i> Register here](https://bit.ly/pyos-contribute)<figure class="align-center">
+    <picture>
+    <source srcset="/images/events/community-call-pavithra-may-2025.webp" type="image/webp">
+    <img src="/images/events/community-call-pavithra-may-2025.png" alt="An image of Pavithra wearing a dark shirt and looking to the side. She has dark curly hair and is smiling.">
+    </picture>
+</figure>
+
+We’re kicking off the week with a special Open Source Voices session! Pavithra will share her open source journey and what helped her grow in the open source world.
+
+### Right Time, Right Community: My OSS Journey
+
+Pavithra Eswaramoorthy is a Developer Advocate at Quansight, where she works to improve the developer experience and community engagement for several open source projects in the PyData community. She has been involved in the open source community for over five years. Currently, she is part of the core team for the Bokeh visualization library and Nebari (JupyterHub-based data science platform).  In her spare time, she enjoys a good book and hot coffee.
+
+## All are welcome
+
+We welcome anyone and everyone to join and learn more about contributing to open source. This is a space for learning, questions, and community. Come and listen, get inspired, and meet others learning about open source.
diff --git a/content/events/2025-07-08-scipy25-create-python-package.md b/content/events/2025-07-08-scipy25-create-python-package.md
new file mode 100644
index 00000000..65216307
--- /dev/null
+++ b/content/events/2025-07-08-scipy25-create-python-package.md
@@ -0,0 +1,171 @@
+---
+title: 'Create Your First Python Package: SciPy 2025'
+date: '2025-07-08'
+lastmod: '2025-04-22'
+excerpt: Learn how to create your first Python package using the pyOpenSci template.
+image:
+  src: images/headers/pyopensci-sustainability.png
+  alt: 'Create Your First Python Package: SciPy 2025'
+event:
+  start_date: '2025-07-08'
+  location: Online
+  event_type: training
+aliases:
+- "/events/pyopensci-scipy25-create-python-package-workshop.html"
+---
+
+## <i class="fa-solid fa-box-open"></i> Learn how to create your first Python package!
+
+* **When:** Tuesday, 8 July 2025 @ 8:00–12:00 PM Pacific Time
+* **Where:** SciPy Meeting 2025 in Tacoma, Washington
+* **Instructors:**
+    * Leah Wasser
+    * Carol Willing
+    * Jeremiah Paige
+    * Tetsuo Koyama
+
+[<i class="fa-regular fa-circle-right"></i> View our workshop abstract](https://cfp.scipy.org/scipy2025/talk/Z3VBWR/)## Setup instructions
+
+You can choose to work on your own machine during the workshop or use the GitHub Codespace we've set up for you. Codespaces include all the tools needed to create your first package—preinstalled and ready to go.
+
+We encourage you to use GitHub Codespaces! If you prefer to install things locally, please do so **before** the workshop.
+
+
+### 1. Make sure you have a GitHub and Test PyPI account
+
+Before the workshop, please create and log into the following accounts:
+
+1. [Create a free GitHub account](https://www.github.com) if you don’t already have one.
+2. [Create a free account on Test PyPI](https://test.pypi.org/account/register) — we’ll use this to practice publishing packages.
+
+
+> <i class="fa-solid fa-lock"></i> **Important:** To follow along when we publish to Test PyPI, you must enable **two-factor authentication (2FA)** on your Test PyPI account. We strongly recommend doing this **before** the workshop!
+{: .notice .notice-important}
+
+## 2a. Setup for working locally on your laptop
+
+We recommend using GitHub Codespaces (see next section) to avoid issues with environment setup. However, if you prefer to work locally, please ensure your environment is set up and ready before the workshop.
+
+If you're comfortable with Python environments, arrive with an environment that has:
+
+- [Hatch installed](https://www.pyopensci.org/python-package-guide/tutorials/get-to-know-hatch.html#install-hatch)
+- [Copier installed](https://copier.readthedocs.io/en/stable/#installation)
+    - You can install both via `pipx`, `uv`, pixi, or any preferred package manager.
+- [VS Code](https://code.visualstudio.com/download) (or any IDE you prefer for packaging)
+
+> <i class="fa-solid fa-triangle-exclamation"></i> **Note:**
+> * We strongly suggest that you go to GitHub.com and [Fork our SciPy 2025 workshop repository](https://github.com/pyOpenSci/pyopensci-scipy25-create-python-package) just in case something with your local installation isn't working. This will ensure that you can follow along with us regardless of your environment setup!
+> * JupyterLab or Jupyter Notebook is **not ideal** for the packaging work we’ll be doing.
+{: .notice }
+
+
+## 2b. If you plan to use GitHub Codespaces (SUGGESTED)
+
+We strongly recommend using our curated [GitHub Codespace](https://codespaces.new/pyOpenSci/ff-2024-create-python-package?quickstart=1), which can be found in your forked workshop repository. This workspace is already set up with:
+
+* VSCode, copier, Hatch, and everything you need to create your first Python package successfully. Codespaces also allows you to easily commit your work during the workshop to your own forked GitHub repository.
+
+**Before the workshop do the following**
+
+* Go to GitHub.com and [Fork our SciPy 2025 workshop repository](https://github.com/pyOpenSci/pyopensci-scipy25-create-python-package)
+
+<figure>
+    <picture>
+    <img src="/images/github/codespaces/scipy-fork-repo.gif" alt=".">
+    </picture>
+</figure>
+
+*  Launch the codespace before the workshop:
+
+<i class="fa-solid fa-circle-info"></i> The initial spin-up for a codespace can take up to 15 minutes or longer. Once GitHub creates the cloud environment, it will be quicker to relaunch. Please do this before attending the workshop session.
+{: .notice }
+
+To open your Codespace,
+
+* Go to your forked SciPy 2025 workshop repository on GitHub,
+* Switch to a branch that you want to work on during the workshop,
+* Click the code drop-down button (where you'd find a link to clone a repo)
+* Click on the Codespaces tab in the drop-down.
+
+Within the Codespaces tab you will see a button: <kbd style="background-color: #2da44e; color: white; padding: 2px 6px; border-radius: 4px;">
+Create codespace on main
+</kbd>. This button launches a Codespace from the currently active branch. It will default to the
+`main` branch if you haven't changed your branch in the repository.
+
+The animated gif below walks you through how this works.
+
+<figure style="width: 55%; margin: 0 auto;">
+  <picture>
+    <source srcset="/images/github/codespaces/create-github-codespace-main.webp"
+            type="image/webp">
+    <img src="/images/github/codespaces/create-github-codespace-main.png"
+         alt="Create codespace on main button">
+  </picture>
+</figure>
+
+> <i class="fa-solid fa-circle-info"></i> To follow GitHub best practices, always create a new branch before making
+> changes to a repository, even if you own the repository. Avoid working directly on the `main` branch.
+
+## <i class="fa-solid fa-cloud"></i> About GitHub Codespaces: Working in the cloud
+
+## What is a codespace
+
+GitHub Codespaces are cloud-based development environments that let you
+code directly in your browser—no local setup needed. They provide fully
+configured, container-based environments connected to your GitHub
+repository.
+
+You can customize Codespaces with `.devcontainer` files to match your
+development setup. The Codespace for this workshop opens in Visual Studio
+Code by default, but you can configure it to use any IDE you prefer.
+
+Learn more in the [GitHub Codespaces docs](https://docs.github.com/en/codespaces/overview).
+
+Codespaces are free for up to 60 hours/month on GitHub’s free plan. Be sure
+to shut yours down after the workshop to conserve your allocated time.
+{: .notice}
+
+> Codespaces are associated with your **personal GitHub account**, even if
+you open one from the pyOpenSci repository. The usage counts toward your
+own GitHub credits.
+{: .notice }
+
+
+### View & manage open codespaces
+
+Once you've opened a Codespace, you can return to it later without needing
+to start from scratch. GitHub will reuse the environment, making it launch
+significantly faster the second time.
+
+If possible, resume the **same Codespace** you started in, rather than
+creating a new one in your fork. Read on to learn how to find and reopen a codespace.
+
+<i class="fa-solid fa-link"></i>
+[View all active Codespaces associated with your account](https://github.com/codespaces)
+
+{: .notice}
+> <i class="fa-solid fa-circle-info"></i> When you delete a Codespace, you're
+> ending the session, but the configuration remains available so you can
+> launch a new one anytime.
+> [Learn more in the GitHub docs](https://docs.github.com/en/codespaces/developing-in-a-codespace/stopping-and-starting-a-codespace)
+
+
+
+
+### How to relaunch a codespace
+
+To relaunch a Codespace:
+
+1. Go to your fork of the workshop repository.
+2. Click the **Code** dropdown (same as when you first created the Codespace).
+3. Select the **Codespaces** tab to view existing environments.
+4. Select the codespace that you want to resume from the list (see image below).
+
+As you can see in the animated gif below, GitHub codespaces always have fun names.
+
+<figure>
+  <picture>
+    <img src="/images/github/codespaces/reopen-codespace.gif"
+         alt="GIF showing how to reopen a GitHub Codespace">
+  </picture>
+</figure>
diff --git a/content/events/2025-07-10-scipy25-bof.md b/content/events/2025-07-10-scipy25-bof.md
new file mode 100644
index 00000000..e1ff5319
--- /dev/null
+++ b/content/events/2025-07-10-scipy25-bof.md
@@ -0,0 +1,36 @@
+---
+title: 'SciPy 2025: Open Code, Open Science: What’s Getting in Your Way?'
+date: '2025-07-10'
+lastmod: '2025-07-03'
+excerpt: Join us for an interactive discussion on pain points that you are experiencing
+  with developing and maintaining reusable software and code.
+image:
+  src: images/headers/pyopensci-sustainability.png
+  alt: 'SciPy 2025: Open Code, Open Science: What’s Getting in Your Way?'
+event:
+  start_date: '2025-07-10'
+  location: Online
+  event_type: community
+aliases:
+- "/events/pyopensci-scipy25-bof-packaging-challenges.html"
+---
+
+## <i class="fa-solid fa-box-open"></i> Learn how to create your first Python package!
+
+* **When:** Thursday, 10 July 2025 @ 1:15–2:10 PM Pacific Time
+* **Where:** Room 315 @ SciPy Meeting 2025 in Tacoma, Washington
+* **Session leaders:**
+    * Leah Wasser
+    * Inessa Pawson
+    * Carol Willing
+    * Jeremiah Paige
+    * Tetsuo Koyama
+    * Avik Basu
+
+
+
+[<i class="fa-regular fa-circle-right"></i> View our session abstract](https://cfp.scipy.org/scipy2025/talk/3ZHYMH/)Collaborating on code and software is essential to open science—but it’s not always easy. Join this BoF for an interactive discussion on the real-world challenges of open source collaboration. We’ll explore common hurdles like Python packaging, contributing to existing codebases, and emerging issues around LLM-assisted development and AI-generated software contributions.
+
+We’ll kick off with a brief overview of pyOpenSci—an inclusive community of Pythonistas, from novices to experts—working to make it easier to create, find, share, and contribute to reusable code. We’ll then facilitate small-group discussions and use an interactive Mentimeter survey to help you share your experiences and ideas.
+
+Your feedback will directly shape pyOpenSci’s priorities for the coming year, as we build new programs and resources to support your work in the Python scientific ecosystem. Whether you’re just starting out or a seasoned developer, you’ll leave with clear ways to get involved and make an impact on the broader Python ecosystem in service of advancing scientific discovery.
diff --git a/content/events/2025-08-07-stanford-ospo-peer-review-deep-dive.md b/content/events/2025-08-07-stanford-ospo-peer-review-deep-dive.md
new file mode 100644
index 00000000..4da33be3
--- /dev/null
+++ b/content/events/2025-08-07-stanford-ospo-peer-review-deep-dive.md
@@ -0,0 +1,73 @@
+---
+title: 'pyOpenSci: Improving research software and code through open and accessible
+  peer review'
+date: '2025-08-07'
+lastmod: '2025-07-03'
+excerpt: Discover how peer review improves research software quality and reproducibility.
+  Hosted for the community within Stanford’s Open Source Program Office, this deep
+  dive introduces pyOpenSci’s review process and ways for researchers to get involved
+  and grow their open source and leadership skills through participating in software
+  peer review.
+image:
+  src: images/headers/pyopensci-sustainability.png
+  alt: 'pyOpenSci: Improving research software and code through open and accessible
+    peer review'
+event:
+  start_date: '2025-08-07'
+  location: Online
+  event_type: talk
+aliases:
+- "/events/pyopensci-stanford-ospo-peer-review.html"
+---
+
+## pyOpenSci: Improving research software and code through open and accessible peer review
+
+* **When:** Thursday, 7 August @ 11:00 AM Mountain Time
+* **Where:** Zoom: this event is for the Stanford Open Source Community
+
+This event, hosted in partnership with [Stanford’s Open Source Program
+Office](https://opensource.stanford.edu/), explores how [software peer review](https://www.pyopensci.org/about-peer-review/index.html) can help you build more reliable research tools, improve your coding and software development skills, and gain academic recognition while also connecting with a global community of practice that is dedicated to supporting the broader research and scientific Python community build better research software.
+
+You’ll learn how pyOpenSci’s community-driven review
+process supports open, sustainable Python software—and how to get
+involved as a contributor or reviewer.
+
+Peer review improves software quality, documentation, and long-term
+sustainability—and gives contributors academic recognition through our
+partnership with the [Journal of Open Source Software (JOSS)](
+https://www.pyopensci.org/software-peer-review/partners/joss.html).
+
+The process is grounded in our [community-developed packaging
+guidelines](https://www.pyopensci.org/python-package-guide/index.html)
+tailored to scientific software.
+
+Whether you're building tools or reviewing them, you're helping shape a
+more open, collaborative, and reproducible future for science. Join us
+to improve research software—and get recognized for doing it.
+
+### Why attend
+
+- <i class="fa-solid fa-magnifying-glass-chart"></i> Learn what peer review
+  looks like for research software
+- <i class="fa-solid fa-code"></i> Improve your own coding practices by reviewing
+  real-world tools
+- <i class="fa-solid fa-diagram-project"></i> See how others structure code, write
+  tests, and document their work
+- <i class="fa-solid fa-award"></i> Gain visibility and academic credit for
+  contributions
+- <i class="fa-solid fa-right-to-bracket"></i> Take a low-barrier first step into the
+  open-source research ecosystem
+
+
+### Building bridges: The power of our Stanford partnership
+
+Through our partnership with Stanford, we're building a bridge between
+the University Open Source Program Offices and the global open-source community that powers scientific
+Python. Researchers and students gain access to high-quality, community-based
+training in research software practices—without Stanford needing to create
+that infrastructure from scratch.
+
+This collaboration supports Stanford’s leadership in open, reproducible
+science while giving its researchers meaningful opportunities to engage with
+the pyOpenSci community and contribute to a broader, inclusive ecosystem of
+scientific software development.
diff --git a/content/events/2025-10-02-stanford-ospo-how-to-create-a-python-package-workshop.md b/content/events/2025-10-02-stanford-ospo-how-to-create-a-python-package-workshop.md
new file mode 100644
index 00000000..953c7c0c
--- /dev/null
+++ b/content/events/2025-10-02-stanford-ospo-how-to-create-a-python-package-workshop.md
@@ -0,0 +1,169 @@
+---
+title: 'pyOpenSci Workshop: Create a Python package -- Stanford Open Source Program
+  Office'
+date: '2025-10-02'
+lastmod: '2025-09-02'
+excerpt: Python packaging can be tricky to navigate. pyOpenSci will lead a pilot workshop
+  on creating your first Python package. The goal of this workshop is to help scientists
+  learn how to package and make code installable and shareable. Read on to learn more!
+image:
+  src: images/headers/pyopensci-sustainability.png
+  alt: 'pyOpenSci Workshop: Create a Python package -- Stanford Open Source Program
+    Office'
+event:
+  start_date: '2025-10-02'
+  location: Online
+  event_type: training
+aliases:
+- "/events/pyopensci-stanford-create-python-package-workshop.html"
+---
+
+## Create a Python package: make your Python code easier to share and use
+
+* **When:** Thursday, 2 October @ 10:00 AM Mountain Time // 9:00AM Pacific Time
+* **Where:** We will use the Spatial Chat platform to create a classroom-like learning experience.
+
+This event, hosted in partnership with [Stanford’s Open Source Program
+Office](https://opensource.stanford.edu/), teaches participants best practices for packaging their Python code. You will learn how to build more reliable research tools and software development skills.
+
+## Setup instructions
+
+You can choose to work on your own machine during the workshop or use the GitHub Codespace we've set up for you. Codespaces include all the tools needed to create your first package—preinstalled and ready to go.
+
+We encourage you to use GitHub Codespaces! If you prefer to install things locally, please do so **before** the workshop.
+
+### 1. Make sure you have a GitHub and Test PyPI account
+
+Before the workshop, please create and log into the following accounts:
+
+1. [Create a free GitHub account](https://www.github.com) if you don’t already have one.
+2. [Create a free account on Test PyPI](https://test.pypi.org/account/register) — we’ll use this to practice publishing packages.
+
+
+> <i class="fa-solid fa-lock"></i> **Important:** To follow along when we publish to Test PyPI, you must enable **two-factor authentication (2FA)** on your Test PyPI account. We strongly recommend doing this **before** the workshop!
+{: .notice .notice-important}
+
+## 2a. Setup for working locally on your laptop
+
+We recommend using GitHub Codespaces (see next section) to avoid issues with environment setup. However, if you prefer to work locally, please ensure your environment is set up and ready before the workshop.
+
+If you're comfortable with Python environments, arrive with an environment that has:
+
+- [Hatch installed](https://www.pyopensci.org/python-package-guide/tutorials/get-to-know-hatch.html#install-hatch)
+- [Copier installed](https://copier.readthedocs.io/en/stable/#installation)
+    - You can install both via `pipx`, `uv`, pixi, or any preferred package manager.
+- [VS Code](https://code.visualstudio.com/download) (or any IDE you prefer for packaging)
+
+> <i class="fa-solid fa-triangle-exclamation"></i> **Note:**
+* We strongly suggest that you visit GitHub.com and [Fork our packaging workshop repository](https://github.com/pyOpenSci/pyopensci-workshop-create-python-package) in case any issues arise with your local installation. This will ensure that you can follow along with us regardless of your environment setup.
+> * JupyterLab or Jupyter Notebook is **not ideal** for the packaging work we’ll be doing.
+{: .notice }
+
+
+
+## 2b. If you plan to use GitHub Codespaces (SUGGESTED)
+
+We strongly recommend using our curated [GitHub Codespace](https://codespaces.new/pyOpenSci/pyopensci-workshop-create-python-package?quickstart=1), which can be found in your forked workshop repository. This workspace is already set up with:
+
+* VSCode, copier, Hatch, and everything you need to create your first Python package successfully. Codespaces also allows you to easily commit your work during the workshop to your own forked GitHub repository.
+
+**Before the workshop do the following**
+
+* Go to GitHub.com and [Fork our Python package workshop repository](https://github.com/pyOpenSci/pyopensci-workshop-create-python-package)
+
+<figure>
+    <picture>
+    <img src="/images/github/codespaces/scipy-fork-repo.gif" alt=".">
+    </picture>
+</figure>
+
+*  Launch the codespace before the workshop:
+
+<i class="fa-solid fa-circle-info"></i> The initial spin-up for a codespace can take up to 15 minutes or longer. Once GitHub creates the cloud environment, it will be quicker to relaunch. Please do this before attending the workshop session.
+{: .notice }
+
+To open your Codespace,
+
+* Go to your forked workshop repository on GitHub,
+* Switch to a branch that you want to work on during the workshop,
+* Click the code drop-down button (where you'd find a link to clone a repo)
+* Click on the Codespaces tab in the drop-down.
+
+Within the Codespaces tab you will see a button: <kbd style="background-color: #2da44e; color: white; padding: 2px 6px; border-radius: 4px;">
+Create codespace on main
+</kbd>. This button launches a Codespace from the currently active branch. It will default to the
+`main` branch if you haven't changed your branch in the repository.
+
+The animated gif below walks you through how this works.
+
+<figure style="width: 55%; margin: 0 auto;">
+  <picture>
+    <source srcset="/images/github/codespaces/create-github-codespace-main.webp"
+            type="image/webp">
+    <img src="/images/github/codespaces/create-github-codespace-main.png"
+         alt="Create codespace on main button">
+  </picture>
+</figure>
+
+> <i class="fa-solid fa-circle-info"></i> To follow GitHub best practices, always create a new branch before making
+> changes to a repository, even if you own the repository. Avoid working directly on the `main` branch.
+
+## <i class="fa-solid fa-cloud"></i> About GitHub Codespaces: Working in the cloud
+
+## What is a codespace
+
+GitHub Codespaces are cloud-based development environments that let you
+code directly in your browser—no local setup needed. They provide fully
+configured, container-based environments connected to your GitHub
+repository.
+
+You can customize Codespaces with `.devcontainer` files to match your
+development setup. The Codespace for this workshop opens in Visual Studio
+Code by default, but you can configure it to use any IDE you prefer.
+
+Learn more in the [GitHub Codespaces docs](https://docs.github.com/en/codespaces/overview).
+
+Codespaces are free for up to 60 hours/month on GitHub’s free plan. Be sure
+to shut yours down after the workshop to conserve your allocated time.
+{: .notice}
+
+> Codespaces are associated with your **personal GitHub account**, even if
+you open one from the pyOpenSci repository. The usage counts toward your
+own GitHub credits.
+{: .notice }
+
+### View & manage open codespaces
+
+Once you've opened a Codespace, you can return to it later without needing
+to start from scratch. GitHub will reuse the environment, making it launch
+significantly faster the second time.
+
+If possible, resume the **same Codespace** you started in, rather than
+creating a new one in your fork. Read on to learn how to find and reopen a codespace.
+
+<i class="fa-solid fa-link"></i>
+[View all active Codespaces associated with your account](https://github.com/codespaces)
+
+{: .notice}
+> <i class="fa-solid fa-circle-info"></i> When you delete a Codespace, you're
+> ending the session, but the configuration remains available so you can
+> launch a new one anytime.
+> [Learn more in the GitHub docs](https://docs.github.com/en/codespaces/developing-in-a-codespace/stopping-and-starting-a-codespace)
+
+### How to relaunch a codespace
+
+To relaunch a Codespace:
+
+1. Go to your fork of the workshop repository.
+2. Click the **Code** dropdown (same as when you first created the Codespace).
+3. Select the **Codespaces** tab to view existing environments.
+4. Select the codespace that you want to resume from the list (see image below).
+
+As you can see in the animated gif below, GitHub codespaces always have fun names.
+
+<figure>
+  <picture>
+    <img src="/images/github/codespaces/reopen-codespace.gif"
+         alt="GIF showing how to reopen a GitHub Codespace">
+  </picture>
+</figure>
diff --git a/content/events/2025-11-06-workshop-create-python-package-2hour.md b/content/events/2025-11-06-workshop-create-python-package-2hour.md
new file mode 100644
index 00000000..1b8fea1d
--- /dev/null
+++ b/content/events/2025-11-06-workshop-create-python-package-2hour.md
@@ -0,0 +1,113 @@
+---
+title: 'From Zero to Python Package: A 2-Hour Python Packaging Workshop'
+date: '2025-11-06'
+lastmod: '2025-09-08'
+excerpt: Turn your Python code into a professional package that others can easily
+  install, use, and contribute to. Learn the complete packaging workflow with hands-on
+  demos and proven templates.
+image:
+  src: images/headers/pyopensci-sustainability.png
+  alt: 'From Zero to Python Package: A 2-Hour Python Packaging Workshop'
+event:
+  start_date: '2025-11-06'
+  location: Online
+  event_type: training
+aliases:
+- "/events/python-packaging-workshop-november-2025.html"
+---
+
+## Everything that you need to know
+
+* **When:** Thursday, 6 November 2025 10:00 AM Mountain Time - 12:15 PM Mountain Time
+* **Where:** Interactive webinar with live demos
+
+### Cost
+
+Prices are in US Dollars. This workshop not only provides you with expert training, but it also supports the work that pyOpenSci does to support scientific open source.
+
+| Ticket Type |Early Bird (Before 5 November 2025 ) | Regular |
+| Regular | $149  | $199 |
+| Student | $45  | $85 |
+| Partner Community (Astropy, PyHC, OpenAstronomy, Pangeo) | $85  | $85 |
+| Partner Community Student (Astropy, PyHC, OpenAstronomy, Pangeo) | $40  | $40 |
+
+
+<i class="fa-regular fa-circle-right"></i> [Register Now on Eventbrite](https://www.eventbrite.com/e/pyopensci-zero-to-pure-python-package-in-minutes-tickets-1677115350159)
+<div class="notice" markdown="1">
+Scholarships are available to individuals who have been affected by job loss and funding cuts and who don't have the resources to attend our training. We will ensure that scholarship recipients represent a diverse range of voices, backgrounds, and experiences. Scholarships are also available to Undergraduate and Graduate level students. Scholarships will reduce the cost of the workshop to 20$ (Students) or 45$ (continuing education, academics and others). We offer a limited number of scholarships. Please be sure to explain why this workshop will benefit your work in Science and the greater open science community when you apply.
+
+[To apply for a scholarship, please fill out this Google form.](https://forms.gle/tnV3tj13cChQXLEH7)
+</div>
+
+Your research code deserves to reach more people. In this hands-on workshop, you'll learn how to transform your Python scripts into professional packages that others can easily install, use, and contribute to. Walk away with a complete packaging workflow and the confidence to share your work with the world.
+
+This workshop is part of pyOpenSci's commitment to building better research software through accessible packaging practices. Whether you're sharing analysis tools with colleagues or building the next great Python library, you'll gain practical skills to package like a pro.
+
+### Workshop Structure
+
+#### Part 1: Modern Python packaging foundations (30 minutes)
+
+- <i class="fas fa-folder-tree" style="color: #999;" ></i> **Package Structure:** Set up your project the right way from day one
+- <i class="fas fa-file-alt" style="color: #999;"></i> **Essential Files Walkthrough:** pyproject.toml, README, and what actually matters
+- <i class="fas fa-tools" style="color: #999;"></i> **Tool Decision Framework:** Navigate the packaging ecosystem with confidence
+
+#### Part 2: Build your Python package (30 minutes)
+
+- <i class="fas fa-hammer" style="color: #999;"></i> **Live Build Demo:** See packaging in action with real code
+- <i class="fas fa-vial" style="color: #999;"></i> **Setup Tests:** Make sure your package works everywhere and as new pull requests come in
+- <i class="fas fa-check-circle" style="color: #999;"></i> **Quality Checklist:** Professional packaging standards made simple
+
+#### <i class="fa-solid fa-mug-hot" style="color: #81c0aa;"></i> Break (10 minutes)
+
+#### Part 3: Publish and share your Python package (30 minutes)
+
+- <i class="fas fa-upload" style="color: #999;"></i> **PyPI Publishing:** Get your package on the Python Package Index
+- <i class="fas fa-shield-alt" style="color: #999;"></i> **Security Best Practices:** Protect your package and users when you are publishing using Trusted Publishing.
+- <i class="fas fa-sync-alt" style="color: #999;"></i> **Automation Setup:** Never manually release your package again; instead use GitHub actions with trusted publishing.
+
+#### Part 4: Documentation for a healthy project (20 minutes)
+
+- <i class="fas fa-users" style="color: #999;"></i> **What docs matter most?:** A brief overview of documentation to make it easier to onboard both contributors and new maintainers to your project.
+
+
+#### Wrap up: Questions (20 Minutes)
+
+- <i class="fas fa-question-circle" style="color: #999;"></i> **Q&A:** Get your questions answered
+
+### Why attend
+
+- <i class="fa-solid fa-rocket" style="color: #999;"></i> Learn modern packaging practices used by successful Python projects
+- <i class="fa-solid fa-tools" style="color: #999;"></i> Get production-ready templates and automation you can use immediately
+- <i class="fa-solid fa-shield-alt" style="color: #999;"></i> Understand publishing security best practices from day one
+- <i class="fa-solid fa-eye" style="color: #999;"></i> See live demos of the complete packaging workflow
+- <i class="fa-solid fa-graduation-cap" style="color: #999;"></i> Learn from pyOpenSci's experience reviewing dozens of packages
+
+### Perfect for you if...
+
+- <i class="fas fa-check" style="color: #81c0aa;"></i> You have Python code that others could benefit from using
+- <i class="fas fa-check" style="color: #81c0aa;"></i> You're tired of sharing code via email or messy file transfers
+- <i class="fas fa-check" style="color: #81c0aa;"></i> You want people to be able to install and use your tools
+- <i class="fas fa-check" style="color: #81c0aa;"></i> You've heard of PyPI but don't know how to get your package there and how to do it securely.
+- <i class="fas fa-check" style="color: #81c0aa;"></i> You want to better understand the complex Python packaging ecosystem
+
+### What you'll walk away with
+
+- **Complete Package Template:** Ready-to-use project structure
+- **Automation Workflows:** GitHub Actions for testing and publishing
+- **Quality Checklists:** Never miss important packaging steps
+- **Publishing Guide:** Step-by-step instructions for secure PyPI deployment using GitHub actions
+
+### Pre-requisites
+
+To successfully follow along in this workshop, you should:
+
+* Know how to write Python code
+* Understand how to write and use functions
+* Have a Free account to create a GitHub account (you can work using GitHub codespaces during this workshop, and setting this account up is free if you don't already have one.
+* You should have internet access
+
+### Your instructors & helpers
+
+* [**Leah Wasser**](https://www.github.com/lwasser), the Executive Director and Founder of pyOpenSci, brings over 20 years of experience teaching technical data science topics in the scientific space. pyOpenSci has worked with hundreds of scientific Python package maintainers and has helped over 50 packages improve their structure and distribution through our peer review process.
+* [**Jeremiah Paige:**](https://www.github.com/ucodery) is an open source author, contributor, and speaker, specifically working with Python for over 12 years. He is also a software engineer in the secure supply chain industry during work hours.
+* [**Avik Basu:**](https://github.com/ab93) is an open source contributor, speaker, and mentor. He is a seasoned machine learning engineer with extensive experience in both major tech companies and fast-moving startups.
diff --git a/content/events/2026-04-10-course-python-packaging-gen-ai.md b/content/events/2026-04-10-course-python-packaging-gen-ai.md
new file mode 100644
index 00000000..6feb4398
--- /dev/null
+++ b/content/events/2026-04-10-course-python-packaging-gen-ai.md
@@ -0,0 +1,181 @@
+---
+title: 'Ship It: Research Software Development in the GenAI Era'
+date: '2026-04-10'
+lastmod: '2026-03-03'
+excerpt: 'A trusted 10-day hands-on asynchronous cohort-based course developed by
+  pyOpenSci for Stanford University and the CURIOSS network.
+
+  '
+image:
+  src: images/headers/pyopensci-sustainability.png
+  alt: 'Ship It: Research Software Development in the GenAI Era'
+event:
+  start_date: '2026-04-10'
+  end_date: '2026-04-23'
+  location: Online
+  event_type: training
+aliases:
+- "/events/shipit-python-package-gen-ai-april-2026.html"
+instructors:
+- name: Leah Wasser
+  github: lwasser
+  bio: 'The Executive Director and Founder of pyOpenSci, Leah brings over 20 years
+    of experience teaching technical data science topics in the scientific space.
+    pyOpenSci has worked with hundreds of scientific Python package maintainers and
+    has helped over 50 packages improve their structure and distribution through our
+    peer review process.
+
+    '
+- name: Jeremiah Paige
+  github: ucodery
+  bio: 'An open source author, contributor, and speaker, specifically working with
+    Python for over 12 years. He is also a software engineer in the secure supply
+    chain industry during work hours.
+
+    '
+- name: Inessa Pawson
+  github: inessaPawson
+  bio: Bio coming soon.
+---
+
+
+<div class="content noimage" markdown="1">
+
+<div class="notice notice--success" markdown="1">
+## Everything you need to know
+
+* **When:** Friday, 10 April 2026 – Thursday, 23 April 2026
+* **Where:** Online asynchronous course with live office hours
+
+### Cost
+
+This course was paid for by the Stanford University Open Source
+Program Office (OSPO) and is available to both Stanford OSPO
+researchers and other OSPOs in the CURIOSS network.
+
+Learn more about our partnership with Stanford in this short video:
+[Ship It with Stanford OSPO](https://www.youtube.com/watch?v=9HDAZJS_Wck)
+
+</div>
+
+## About the course
+Learn directly from leaders in the open source space. Featuring hands-on
+activities, expert interviews with Python core developers and scientific Python
+maintainers, and live office hours where you can get help and ask questions,
+this 10-day asynchronous course empowers university researchers and
+practitioners to reliably build and share critical tools.
+
+Developed by pyOpenSci in partnership with the Stanford Open Source Program
+Office (OSPO), this program delivers a trusted, expert-led curriculum that
+guides you through the lifecycle of a modern Python package. You will evolve a
+working script into a tested, documented, and automated package published on
+PyPI.
+
+By participating in this course, you're also joining a vibrant open source
+ecosystem. Expect to work with today’s industry-standard
+tools—including uv,
+Hatch, pytest, and Sphinx—while exploring open-source workflows and learning
+how to use Generative AI critically, thoughtfully, and responsibly.
+
+## What you’ll learn
+
+* Structure a Python package from scratch.
+* Configure your package using pyproject.toml.
+* Build and publish your package to (test) PyPI.
+* Write and run different types of tests using pytest.
+* Automate your development workflows with task runners.
+* Create the core documentation files every package needs.
+* Use AI tools responsibly in your development workflow.
+
+This course is part of pyOpenSci’s **Ship It** curriculum — designed for
+researchers, scientists, and developers who want to build sustainable,
+production-ready open source software.
+
+## Who this course is for
+
+This course is designed for:
+
+* **Researchers, scientists, and postdocs** who write Python code and want to
+  share it
+* **University faculty, staff, and students** looking to teach or adopt modern
+  Python packaging practices
+* **Developers** who are new to open source packaging and want a structured,
+  guided path
+
+*No prior packaging experience is required.* If you are comfortable with Python
+programming and can write a Python function, then you're ready for this course.
+
+## What makes this course different
+
+pyOpenSci's unique advantage is its community. You're not just watching videos;
+you're learning alongside — and from — the people who maintain Python's
+packaging ecosystem.
+
+The course is delivered in a flexible, async format designed for busy
+researchers: each day you’ll discover 10–15 minutes of video content, and
+then you’ll complete a short bite-sized activity. Use the weekend to catch up
+if you fall behind.
+
+</div>
+
+<div class="pyos-section purple">
+<div class="content noimage" markdown="1">
+
+## Course Schedule at a Glance
+
+### Week 0: Setup
+
+The week before the course begins is focused on setup. You can complete the
+course either using GitHub Codespaces or locally on your computer.
+
+### Week 1: Foundation & Structure
+
+* <i class="fas fa-folder-tree" style="color: #999;" ></i> Day 1 — Create and
+  run your package
+* <i class="fas fa-folder-tree" style="color: #999;" ></i> Day 2 — Metadata and
+  dependencies: the pyproject.toml file
+* <i class="fas fa-hammer" style="color: #999;"></i> Day 3 — Build and publish
+  your package
+* <i class="fas fa-vial" style="color: #999;"></i> Day 4 — Introduction to
+  testing
+* <i class="fas fa-comments" style="color: #999;"></i> Day 5 — Live office
+  hours: show up, ask questions, get help.
+
+### Week 2: Task runners, GenAI & Documentation
+
+* <i class="fas fa-sync-alt" style="color: #999;"></i> Day 6 — Automate your
+  workflows: task runners and environments
+* <i class="fas fa-robot" style="color: #999;"></i> Day 7 — GenAI to support
+  your workflows
+* <i class="fas fa-users" style="color: #999;"></i> Day 8 — Documentation that
+  matters most to build your community and maintainer team
+* <i class="fas fa-flag-checkered" style="color: #999;"></i> Day 9 — Office
+  hours & wrap up
+
+</div>
+</div>
+
+<div class="content noimage" markdown="1">
+
+### What you'll walk away with
+
+- **Complete Package Template:** Ready-to-use project structure
+- **Automation Workflows:** GitHub Actions for testing and publishing
+- **Quality Checklists:** Never miss important packaging steps
+- **Publishing Guide:** Step-by-step instructions for secure PyPI deployment
+  using GitHub Actions
+
+### Pre-requisites
+
+To successfully follow along in this workshop, you should:
+
+* Know how to write Python code
+* Understand how to write and use Python functions
+* Have a free GitHub account. You can work using GitHub Codespaces during this
+  workshop, and setting up this account is free if you don't already have one.
+* Have internet access to access the course materials and tools.
+
+### Your instructors & helpers
+
+
+</div>
diff --git a/content/events/2026-05-16-pycon-us-maintainers-summit.md b/content/events/2026-05-16-pycon-us-maintainers-summit.md
new file mode 100644
index 00000000..30534538
--- /dev/null
+++ b/content/events/2026-05-16-pycon-us-maintainers-summit.md
@@ -0,0 +1,26 @@
+---
+title: PyCon US Maintainers Summit
+date: '2026-05-16'
+lastmod: ''
+excerpt: Join pyOpenSci and the broader Python community for a day of talks and roundtables
+  on sustainable open source maintainership.
+image:
+  src: images/headers/pyopensci-sprints-2025.png
+  alt: PyCon US Maintainers Summit
+event:
+  start_date: '2026-05-16'
+  end_date: '2026-05-16'
+  location: Long Beach, CA
+  event_type: community
+aliases:
+- "/events/2026-pycon-us-maintainers-summit.html"
+---
+
+## PyCon US Maintainers Summit
+
+* **What:** Maintainers Summit at PyCon US 2026
+* **When:** Saturday, May 16, 2026
+* **Where:** Room 201A, Long Beach Convention & Entertainment Center, Long Beach, CA
+* **More info:** [PyCon US Maintainers Summit page](https://us.pycon.org/2026/events/maintainers-summit/)
+
+The Maintainers Summit brings together maintainers and contributors across the Python ecosystem to share strategies for healthy, sustainable open source projects. The program includes talks, tools demos, and roundtable discussions.
diff --git a/content/events/2026-05-17-pycon-us-development-sprint.md b/content/events/2026-05-17-pycon-us-development-sprint.md
new file mode 100644
index 00000000..61f0c5e1
--- /dev/null
+++ b/content/events/2026-05-17-pycon-us-development-sprint.md
@@ -0,0 +1,26 @@
+---
+title: PyCon US Development Sprint
+date: '2026-05-17'
+lastmod: ''
+excerpt: Join pyOpenSci contributors for a one-day collaborative sprint focused on
+  improving open science tooling, docs, and contributor workflows.
+image:
+  src: images/headers/pyopensci-sprints-2025.png
+  alt: PyCon US Development Sprint
+event:
+  start_date: '2026-05-17'
+  end_date: '2026-05-17'
+  location: Long Beach, CA
+  event_type: sprint
+aliases:
+- "/events/2026-pycon-us-development-sprint.html"
+---
+
+## PyCon US Development Sprint
+
+* **What:** One-day collaborative sprint following the Maintainers Summit
+* **When:** Sunday, May 17, 2026
+* **Where:** PyCon US Sprints area, Long Beach Convention & Entertainment Center, Long Beach, CA
+* **More info:** [PyCon US sprints information](https://us.pycon.org/2026/events/dev-sprints/)
+
+This sprint day is dedicated to hands-on collaboration. Participants can contribute to packaging resources, documentation, peer review tooling, and community onboarding materials with support from maintainers and experienced contributors.
diff --git a/content/events/2026-06-21-un-meeting.md b/content/events/2026-06-21-un-meeting.md
new file mode 100644
index 00000000..9e49b65f
--- /dev/null
+++ b/content/events/2026-06-21-un-meeting.md
@@ -0,0 +1,21 @@
+---
+title: UN meeting (placeholder)
+date: '2026-06-21'
+excerpt: >
+  Placeholder for a UN-related meeting or side event in June 2026. Replace
+  with the official title, venue, and registration when details are available.
+image:
+  src: images/headers/pyopensci-sustainability.png
+  alt: Decorative pyOpenSci header image
+event:
+  start_date: '2026-06-21'
+  end_date: '2026-06-27'
+  location: TBD
+  conference: UN meeting 2026
+  event_type: community
+---
+
+## Details coming soon
+
+This week-long placeholder (**21–27 June 2026**) exercises multi-day live event
+handling on the events page. Update or remove when real details are confirmed.
diff --git a/content/events/2026-07-13-europython.md b/content/events/2026-07-13-europython.md
new file mode 100644
index 00000000..c884d3dd
--- /dev/null
+++ b/content/events/2026-07-13-europython.md
@@ -0,0 +1,22 @@
+---
+title: EuroPython 2026 (placeholder)
+date: '2026-07-13'
+excerpt: >
+  Placeholder for pyOpenSci at EuroPython 2026 in Kraków. Replace with session
+  details, links, and schedule when the program is confirmed.
+image:
+  src: images/headers/pyopensci-sustainability.png
+  alt: Decorative pyOpenSci header image
+event:
+  start_date: '2026-07-13'
+  end_date: '2026-07-20'
+  location: Kraków, Poland
+  conference: EuroPython 2026
+  event_type: talk
+---
+
+## Details coming soon
+
+EuroPython runs **13–20 July 2026**. This stub stays in the upcoming and live
+sections for the full conference week. Update front matter and body when our
+sessions are announced.
diff --git a/content/events/2026-07-19-euroscipy.md b/content/events/2026-07-19-euroscipy.md
new file mode 100644
index 00000000..07b12338
--- /dev/null
+++ b/content/events/2026-07-19-euroscipy.md
@@ -0,0 +1,21 @@
+---
+title: EuroSciPy 2026 (placeholder)
+date: '2026-07-19'
+excerpt: >
+  Placeholder for pyOpenSci at EuroSciPy 2026. Replace with talk titles,
+  tutorials, and links when the program is published.
+image:
+  src: images/headers/pyopensci-sustainability.png
+  alt: Decorative pyOpenSci header image
+event:
+  start_date: '2026-07-19'
+  end_date: '2026-07-22'
+  location: Kraków, Poland
+  conference: EuroSciPy 2026
+  event_type: community
+---
+
+## Details coming soon
+
+EuroSciPy runs **19–22 July 2026**. This stub remains live through the end of the
+conference. Add real content when scheduling is confirmed.
diff --git a/content/events/2026-09-02-rsecon-talk.md b/content/events/2026-09-02-rsecon-talk.md
new file mode 100644
index 00000000..3d6a0f59
--- /dev/null
+++ b/content/events/2026-09-02-rsecon-talk.md
@@ -0,0 +1,21 @@
+---
+title: RSECon talk
+date: '2026-09-02'
+excerpt: >
+  Placeholder event to preview the upcoming grid. Replace with venue, title,
+  and session details when available.
+image:
+  src: images/headers/pyopensci-sustainability.png
+  alt: 'Decorative pyOpenSci header image'
+event:
+  start_date: '2026-09-02'
+  end_date: '2026-09-02'
+  location: Sheffield, England, United Kingdom
+  conference: RSECon 2026
+  event_type: talk
+---
+
+## Details coming soon
+
+Replace this content with the real talk description, schedule link, and
+registration when RSECon announces sessions.
diff --git a/content/events/_index.md b/content/events/_index.md
new file mode 100644
index 00000000..3e20f700
--- /dev/null
+++ b/content/events/_index.md
@@ -0,0 +1,58 @@
+---
+title: Learn, Connect, and Grow with Us
+description: >-
+  pyOpenSci runs training, sprints, and community events to help you build
+  better open source software, code and workflows.
+header:
+  overlay_image: images/blog/headers/pycon-us-2026-header.png
+aliases:
+  - /events.html
+cards:
+  - modifier: "card--white"
+    icon: "fa-solid fa-palette"
+    title: "Community Events That Help Your Connect & Grow"
+    text_only: true
+  - modifier: card--white
+    title: Training
+    event_type: training
+    image:
+      src: images/headers/pyopensci-sustainability.png
+      alt: Hands-on pyOpenSci workshop session
+    excerpt: >-
+      We offer hands-on training sessions online on topics spanning Python packaging, software development and maintenance and contributing to open source software. We use spatial chat for highly interactive online sessions
+      and run cohort based asynchronous courses that span multiple days to multiple weeks that support structured learning at
+      your own pace and on your own time supported by expert instructors to answer questions.
+  - modifier: card--white
+    title: Beginner-friendly sprints
+    event_type: community
+    image:
+      src: images/events/sprint-scipy-2025.png
+      alt: pyOpenSci contributors collaborating at a sprint table
+    excerpt: >-
+      Open conversations and talks (for example, our Open Source Voices series)
+      focused on contributor journeys and how to get involved.
+  - modifier: card--white
+    title: Courses
+    event_type: training
+    image:
+      src: images/headers/pyopensci-sustainability.png
+      alt: pyOpenSci online course materials
+    excerpt: >-
+      Multi-day cohort-style programs with async content and live office hours,
+      built for researchers and teams who want structured support.
+  - modifier: card--white
+    title: Sprints and BoFs
+    event_type: sprint
+    image:
+      src: images/events/bof-session-scipy-2025.png
+      alt: Contributors collaborating at a conference sprint
+    excerpt: >-
+      Collaborative time at conferences (such as SciPy and PyCon US) for packaging,
+      peer review, and roadmap discussions alongside the broader scientific Python community.
+---
+
+{{< impact-cards >}}
+
+If you would like pyOpenSci at your conference, university, or OSPO, use the
+links in the site footer or open an issue on
+[github.com/pyOpenSci/pyopensci.github.io](https://github.com/pyOpenSci/pyopensci.github.io).
diff --git a/content/how-to-submit-a-package-to-pyopensci.md b/content/how-to-submit-a-package-to-pyopensci.md
new file mode 100644
index 00000000..e014a391
--- /dev/null
+++ b/content/how-to-submit-a-package-to-pyopensci.md
@@ -0,0 +1,179 @@
+---
+title: "How to submit a Python package to pyOpenSci for review"
+description: >-
+  Our open review process happens on GitHub and is community led. Learn how to
+  submit a Python package to pyOpenSci for peer review.
+layout: single
+url: /how-to-submit-a-package-to-pyopensci/
+aliases:
+  - /how-to-submit-a-package-to-pyopensci.html
+hero:
+  title: "How to submit a Python package to pyOpenSci for review"
+  excerpt: >-
+    Our open review process happens on GitHub and is community led.
+  image:
+    src: images/headers/pyos-peer-review-header.png
+    alt: "Illustration representing pyOpenSci software peer review."
+---
+
+## Submit your Python package for review
+
+Awesome, you've built a Python package! How do you ensure it follows best
+practices and gets seen by the broader Python community?
+
+**pyOpenSci's peer review process** connects you with community reviewers and
+editors who will help you refine your package's structure, documentation,
+maintainability, and usability. pyOpenSci accepted packages:
+
+* Join a [vetted ecosystem](/python-packages/) of high-quality scientific tools
+* Benefit from increased community visibility
+* Can be fast-tracked for publication in [Journal of Open Source Software (JOSS)](https://www.pyopensci.org/software-peer-review/partners/joss.html) through our end-to-end review
+
+{{< button href="https://www.pyopensci.org/software-peer-review/about/benefits.html" variant="dark-purple" target="_blank" >}}
+Learn more about the benefits of our peer review process
+{{< /button >}}
+
+{{< admonition type="info" title="Need help with your Python package?" >}}
+If you need help getting your package ready for review, you can submit a help
+request in our software-submission repository.
+
+Check out the [pyOpenSci Package Guide](https://www.pyopensci.org/python-package-guide/), including
+[beginning-to-end Python packaging tutorials](https://www.pyopensci.org/python-package-guide/tutorials/intro.html)
+and overviews of
+[continuous integration](https://www.pyopensci.org/python-package-guide/tests/tests-ci.html#run-tests-with-continuous-integration),
+[testing](https://www.pyopensci.org/python-package-guide/#tests), and
+[documentation](https://www.pyopensci.org/python-package-guide/#documentation) —
+all required for acceptance into the [pyOpenSci ecosystem](/python-packages/).
+{{< /admonition >}}
+
+## Step-by-step guide to submitting your package for review
+
+Our **open peer review process** happens on GitHub using structured issues in
+the [**pyOpenSci software submission repository**](https://github.com/pyopensci/software-submission).
+Our review process is **open, constructive, and focused on improving your
+software for others to use**.
+
+{{< button href="https://www.pyopensci.org/software-peer-review/how-to/author-guide.html" variant="dark-purple" target="_blank" >}}
+Read our Author Guide for an overview of the process
+{{< /button >}}
+
+### What happens after you submit your package?
+
+Once you submit your package, our **Editor-in-Chief** will review it to confirm:
+
+* It fits within **pyOpenSci's scope**
+* It meets **infrastructure and documentation requirements**
+
+### Expected timeline
+
+The timeline of your review depends upon a few things:
+
+* Whether we have an editor on board (or need to find one) to lead a review of your package
+* How long it takes your editor to find reviewers
+* How much work your package needs before the review begins
+
+However, once we find editors and reviewers for your package, you can expect a timeline like this:
+
+* **Initial pre-review checks:** ~2 weeks (varies based on submission volume)
+* **Finding editors and reviewers:** ~2–4 weeks (depends on package complexity and availability)
+* **Running the review:** 4–8+ weeks, depending on reviewer feedback and response time
+
+Read the full review process in our [Peer Review Guide](https://www.pyopensci.org/software-peer-review/how-to/author-guide.html).
+
+### 1. Check if your package is in pyOpenSci's scope
+
+Before submitting your package for review, make sure that it fits within
+[**pyOpenSci's peer review scope**](https://www.pyopensci.org/software-peer-review/about/package-scope.html).
+
+If you are unsure if your package is in scope,
+[**submit a pre-submission inquiry**](#submission-type) to get feedback from our
+editorial team.
+
+### 2. Check that your package meets our pre-review requirements
+
+Check that your package meets
+[**pyOpenSci's minimum Python package requirements**](https://www.pyopensci.org/software-peer-review/how-to/editor-in-chief-guide.html#editor-checklist-template)
+before you submit. The Editor in Chief will check your package against these
+criteria before the review begins.
+
+If you have questions or need help, submit a help-request issue in our
+software-submission repo or ask in our
+[GitHub Discussions](https://github.com/orgs/pyOpenSci/discussions).
+
+{{< admonition type="note" title="Core packaging criteria" >}}
+Our packaging guide covers criteria including:
+
+* **Your package is installable** through [PyPI](https://www.pyopensci.org/python-package-guide/package-structure-code/publish-python-package-pypi-conda.html#what-is-pypi) (preferred) and/or a [Conda channel](https://www.pyopensci.org/python-package-guide/package-structure-code/publish-python-package-pypi-conda.html#what-is-conda-and-anaconda-org)
+* **Clear documentation**, including user guides, tutorials, and API documentation
+* **Automated [testing](https://www.pyopensci.org/python-package-guide/tests/write-tests.html) and [CI](https://www.pyopensci.org/python-package-guide/tests/tests-ci.html)**
+* **Core [documentation files](https://www.pyopensci.org/python-package-guide/documentation/repository-files/intro.html):** `README.md`, `LICENSE`, `CONTRIBUTING.md`, and a Code of Conduct
+{{< /admonition >}}
+
+### 3. Submit your package for review
+
+Once you have determined that your package is in scope and meets our core
+packaging requirements, it is time to submit it for review:
+
+1. **Go to our software submission GitHub repository**: [pyOpenSci/software-submission](https://github.com/pyOpenSci/software-submission/issues/new/choose)
+2. **Click on the Issues tab**
+3. <a id="submission-type"></a> **Select the appropriate issue template**
+4. **Complete the issue form** and submit it
+
+{{< button href="https://github.com/pyOpenSci/software-submission/issues/new/choose" variant="dark-purple" target="_blank" >}}
+Submit your package here
+{{< /button >}}
+
+{{< admonition type="success" title="Three templates in our Issue Submission repo" >}}
+* **Help request:** Need guidance on testing, docs, or packaging? Submit a help request and our editorial team will assist.
+* **[Pre-submission inquiry](https://github.com/pyOpenSci/software-submission/issues/new?template=presubmission-inquiry.md):** Unsure if your package [fits our scope](https://www.pyopensci.org/software-peer-review/about/package-scope.html)? Submit an inquiry for feedback before review.
+* **Full submission:** Ready for peer review? Submit your package to kick off the process.
+
+{{< figure src="/images/peer-review/pyopensci-software-review-issue-selection.png" alt="Screenshot of the pyOpenSci issue selection screen on GitHub with three template options." caption="Select the issue template that best fits your current situation." >}}
+{{< /admonition >}}
+
+{{< figure src="/images/peer-review/peer-review-submit-issue.gif" alt="Animated gif showing how to open a new review submission on GitHub." caption="How to open a new review submission in our GitHub repository." >}}
+
+#### Guidelines for filling out the review issue template
+
+When you fill out the review template, please consider the following:
+
+##### Basic template criteria
+
+* **Complete all sections of the template.** If you have questions about fields, ask in the review issue.
+* **Do not modify existing formatting:** Please do not add bold, italics, or other markup to template fields.
+* **Submit your issue only when fully completed:** Consider forking our repository and working on the issue in your fork before submitting.
+* **If you made a pre-submission inquiry**, paste the link to the corresponding issue in your submission.
+
+##### Long-term maintenance and code of conduct
+
+To be considered for review, you must agree to the following when filling out the review submission:
+
+1. **Follow our Code of Conduct** during and after the review.
+2. **Commit to maintaining your package for at least 2 years.** If your primary goal is publication rather than ongoing maintenance, consider submitting directly to [JOSS](https://joss.theoj.org/) instead.
+
+##### Our partnerships
+
+Becoming published or affiliated with one of our partners is optional.
+
+{{< figure src="/images/peer-review/pyos-partnerships-peer-review.png" alt="Flowchart showing pyOpenSci acceptance leading to JOSS publication and community affiliation." caption="Packages accepted into pyOpenSci can also be published in JOSS through a streamlined process." >}}
+
+* **If you are interested in a fast track review through JOSS, check the JOSS box.** JOSS will accept our review and only review your `paper.md` file.
+* **Community affiliation:** If you want affiliation with a partner community like [Astropy](https://www.pyopensci.org/software-peer-review/partners/astropy.html), select the community partner in the template. Learn more about [community affiliation](https://www.pyopensci.org/software-peer-review/partners/scientific-communities.html).
+
+##### Please fill out our survey
+
+Completing the [pyOpenSci pre-review survey](https://forms.gle/F9mou7S3jhe8DMJ16) helps our volunteer team track submissions and improve our peer review process.
+
+##### Template sections that you can ignore
+
+Some template sections are **for editors only** and should be left blank, including editorial assignments and JOSS-specific fields (`JOSS DOI`, `Version accepted`, `Date accepted`).
+
+{{< admonition type="success" title="Need help?" >}}
+Check out our [**Python packaging guide**](https://www.pyopensci.org/python-package-guide/) for best practices on packaging, testing, and infrastructure setup.
+{{< /admonition >}}
+
+Once you're ready, **submit your issue**, and our editors will take it from there!
+
+{{< admonition type="info" title="Connect with us" >}}
+If you found this how-to guide useful, or if you have suggestions for improving it, reach out on [Bluesky](https://bsky.app/profile/pyopensci.org), [Fosstodon](https://fosstodon.org/@pyOpenSci), or [LinkedIn](https://www.linkedin.com/company/pyopensci).
+{{< /admonition >}}
diff --git a/content/learn-universities-labs.md b/content/learn-universities-labs.md
new file mode 100644
index 00000000..772246dc
--- /dev/null
+++ b/content/learn-universities-labs.md
@@ -0,0 +1,114 @@
+---
+title: "Open source training for universities & research labs"
+layout: splash
+url: /learn-universities-labs/
+aliases:
+  - /learn-universities-labs.html
+description: >-
+  pyOpenSci training and accelerator programs for university research
+  communities and labs — cohort courses, webinars, and partnership packages.
+hero:
+  title: "Open source training for universities & research labs"
+  color: primary-dark
+---
+
+## Open source training for university research communities
+
+{{< figure src="/images/people/scipy-sprint-2026.png" alt="A group of contributors sitting at a table at a pyOpenSci sprint working on their laptops and talking to each other." >}}
+
+Introduce your research community to the world of open source scientific
+software through pyOpenSci's training and community programs.
+
+Our programs help researchers develop sustainable, reusable code and research
+software while connecting them to the global scientific Python ecosystem.
+Participants gain access to top tier asynchronous training sessions led by
+Python experts, interactive hands on training workshops, and direct support
+from open source leaders.
+
+### Benefits for universities and research programs
+
+{{< university-benefits-list >}}
+
+{{< swoosh_section background="purple" swoosh="bottom" >}}
+
+{{< pullquote color="purple" author="Zach Chandler" event="Director, Stanford Open Source Program Office" >}}
+pyOpenSci has proven to be a valuable partner in developing our competencies
+in code peer review and open science as a whole community, instead of best
+practices being confined to particular labs. For any research university that
+does significant work in Python (which is all universities!) I highly
+recommend getting involved with pyOpenSci.
+{{< /pullquote >}}
+
+{{< /swoosh_section >}}
+
+## Research software accelerator programs
+
+Supporting you in building a thriving Open Source community at your institution.
+Guide your researchers from a working script to a published Python package
+using industry-standard tools like Hatch, pytest, uv, and Sphinx.
+
+{{< partnership-cards >}}
+
+*Note: Topics are confirmed each cohort cycle as new content is released.*
+
+### Complex, technical concepts made easy
+
+Researchers shouldn't have to struggle with sharing code and software on their
+own. Connect your students and researchers with a thriving, inclusive, and
+vibrant community of beginner-to-expert Pythonistas who support scientific open
+source. Open doors for your researchers to engage with other Python developers,
+troubleshoot challenges together, and gain ongoing support as they develop
+their scientific open source skills.
+
+{{< swoosh_section background="purple" swoosh="top" >}}
+
+## Don't take our word for it: hear from previous course learners
+
+{{< university-testimonials >}}
+
+*Our current content is the 10-day Ship It: Python Packaging in the GenAI Era course.*
+
+{{< /swoosh_section >}}
+
+### Beta Partnership packages
+
+We are currently piloting our partnership program to find the best combination
+of resources and events that best support our University partners.
+
+{{< swoosh_section background="purple" swoosh="top" >}}
+
+## Ready to explore a pyOpenSci membership?
+
+From emerging open source communities to established research software
+programs, pyOpenSci offers training and partnership opportunities at every
+stage.
+
+{{< button href="mailto:media@pyopensci.org?subject=pyOpenSci%20university%20membership%20inquiry" variant="dark-purple" size="lg" >}}
+Request program details
+{{< /button >}}
+
+### Did you know?
+
+pyOpenSci also offers a wide variety of free training resources for individual
+learners. Explore our workshops, webinars, and more on our
+[events page](/events/).
+
+{{< /swoosh_section >}}
+
+## Why partnering with pyOpenSci matters
+
+pyOpenSci is a nonprofit organization that supports open source scientific
+Python research software through software peer review, training, and community
+building. Revenue generated through partnerships directly supports the
+development, maintenance, and sustainability of open source research software.
+
+### Bottom line
+
+Researchers should not have to struggle with sharing code and software on
+their own. Connect your students and researchers with a thriving, inclusive,
+and vibrant community of beginner to expert Pythonistas who support scientific
+open source.
+
+Open doors for your researchers to engage with other Python developers,
+troubleshoot challenges together, and gain ongoing support as they develop
+their scientific open source skills.
diff --git a/content/learn.md b/content/learn.md
new file mode 100644
index 00000000..35c0636a
--- /dev/null
+++ b/content/learn.md
@@ -0,0 +1,131 @@
+---
+title: "Python Tutorials & Learning Resources for Scientists"
+layout: splash
+url: /learn/
+aliases:
+  - /learn.html
+description: >-
+  pyOpenSci training resources for scientists — beginner-friendly Python
+  packaging tutorials, GitHub collaboration lessons, and expert-led community
+  events.
+hero:
+  title: "Python Tutorials & Learning Resources for Scientists"
+  image:
+    src: images/headers/pyopensci-learn-header.png
+    alt: "pyOpenSci training and learning resources for scientists."
+intro_section:
+  text: >-
+    pyOpenSci is committed to supporting scientists as they leverage open source
+    to solve the world's most complex challenges. From beginners who hope to
+    build an installable Python package, contributors ready to master core GitHub
+    collaboration skills to experts looking to streamline packaging maintenance
+    workflows, our educational hub is a trusted resource for gaining the skills
+    needed to scale your project.
+---
+
+{{< intro-section >}}
+
+{{< admonition type="success" >}}
+Are you interested in cohort learning options? Visit our
+[university research communities and labs accelerator programs](/learn-universities-labs/)
+page to learn more.
+{{< /admonition >}}
+
+{{< swoosh_section background="purple" swoosh="bottom" >}}
+
+## Our process: Community-developed Python tutorials
+
+Our tutorials are created through a multi-stage community review process.
+
+* Tutorials are developed by the pyOpenSci team or community members.
+* Tutorials are reviewed by tool maintainers to ensure ideas and concepts are
+  accurate.
+* Before publication, tutorials then go through several rounds of community
+  review for accuracy, usability and accessibility.
+
+{{< figure src="/images/learn-graphics/community-created.png" alt="Hands holding a sign that says Community Developed on a dark purple background with green decorative elements." >}}
+
+{{< /swoosh_section >}}
+
+<div class="container learn-page__tutorials">
+
+## Start learning: beginner-friendly Python packaging tutorials
+
+Beginner-friendly Python packaging tutorials guide you through creating a Python
+package, following modern best practices. It's best to follow the tutorials in
+order, but you can always pick a specific topic if you wish to jump around.
+
+{{< tutorial-grid >}}
+
+</div>
+
+{{< swoosh_section background="purple" swoosh="top" >}}
+
+## Lessons: Collaborative GitHub for Scientists
+
+Support for this track comes in part from the
+[Better Scientific Software Fellowship](https://bssw.io/pages/bssw-fellowship-program).
+These lessons live in the
+[pyOpenSci lessons book](https://www.pyopensci.org/lessons/) and teach
+**GitHub collaboration** for open source and team science.
+
+Read
+[social etiquette in open source](https://www.pyopensci.org/lessons/contribute-open-source/social-open-source.html),
+then work through the contribute path:
+
+1. [Your contributing path](https://www.pyopensci.org/lessons/contribute-open-source/your-first-contribution.html)
+2. [Get to know the repo](https://www.pyopensci.org/lessons/contribute-open-source/get-to-know-repo.html)
+3. [Find an issue](https://www.pyopensci.org/lessons/contribute-open-source/identify-issue.html)
+4. [Fork a GitHub repository](https://www.pyopensci.org/lessons/contribute-open-source/fork-repo.html)
+5. [Edit and commit files](https://www.pyopensci.org/lessons/contribute-open-source/edit-commit-files.html)
+6. [Submit a pull request](https://www.pyopensci.org/lessons/contribute-open-source/pull-request.html)
+
+**Work locally:**
+[Clone a GitHub repository](https://www.pyopensci.org/lessons/contribute-open-source/clone-repo.html)
+
+**Background:**
+[What is Git/GitHub?](https://www.pyopensci.org/lessons/contribute-open-source/what-is-git-github.html),
+[GitHub Codespaces](https://www.pyopensci.org/lessons/contribute-open-source/github-codespaces.html),
+[Ways to contribute](https://www.pyopensci.org/lessons/contribute-open-source/ways-to-contribute.html)
+
+{{< figure src="/images/learn-graphics/github-collaboration.png" alt="Graphic with a light yellow background about essential collaboration skills for scientists using GitHub, with two people working at laptops." >}}
+
+{{< button href="https://www.pyopensci.org/lessons/contribute-open-source/index.html" variant="green" size="lg" target="_blank" >}}
+Open the collaboration lessons
+{{< /button >}}
+
+{{< /swoosh_section >}}
+
+<div class="container">
+
+## Expert-led training & community events
+
+pyOpenSci runs comprehensive training events that equip scientists with the
+critical skills needed to make their research software more open, reliable, and
+collaborative.
+
+When you attend our events, you experience the value of learning directly from
+leaders in the open-source space. Over the years, we have fostered a welcoming,
+supportive and diverse community where you can collaborate alongside
+cross-disciplinary peers facing similar challenges. From expert-led workshops
+to our highly collaborative sprint events, the connections you make and the
+skills you build here will transform your workflow.
+
+{{< figure src="/images/people/bof-scipy-2025.png" alt="People sitting in a conference room and smiling during a pyOpenSci event." >}}
+
+{{< button href="/events/" variant="green" >}}
+Explore upcoming events
+{{< /button >}}
+
+</div>
+
+{{< single-card-wide title="Find the open science tools that you need for your research" icon="fa-solid fa-feather" >}}
+
+Our catalog of vetted open source tools makes it easier for scientists to find
+the trusted tools that they need to develop their open science workflows.
+
+{{< button href="/python-packages/" variant="green" >}}
+View our growing list of accepted scientific Python packages
+{{< /button >}}
+
+{{< /single-card-wide >}}
diff --git a/content/python-packages.md b/content/python-packages.md
new file mode 100644
index 00000000..11387ebe
--- /dev/null
+++ b/content/python-packages.md
@@ -0,0 +1,29 @@
+---
+title: "pyOpenSci open peer review & accepted packages"
+description: >-
+  Python packages accepted into the pyOpenSci ecosystem through open software
+  peer review.
+layout: packages-list
+url: /python-packages/
+aliases:
+  - /python-packages.html
+hero:
+  title: pyOpenSci open peer review & accepted packages
+  image:
+    src: images/headers/pyopensci-software.png
+    alt: "Illustration representing pyOpenSci accepted Python packages."
+---
+
+Explore our accepted open source Python packages below. The metrics bar shows
+current totals. You can
+[check out packages currently under review](https://github.com/pyOpenSci/software-submission/issues)
+in our GitHub submission repository.
+
+Packages listed here have been accepted into the pyOpenSci ecosystem through our
+[open software peer review process](/about-peer-review/).
+
+To view packages affiliated with our partner communities, use the Astropy
+partner link above the filters or visit our
+[community partners section](/about-peer-review/#community-partners).
+
+[Learn how to submit a package for review](/how-to-submit-a-package-to-pyopensci/).
diff --git a/data/blog_topics.yml b/data/blog_topics.yml
new file mode 100644
index 00000000..67c51227
--- /dev/null
+++ b/data/blog_topics.yml
@@ -0,0 +1,8 @@
+community:
+  label: "Community"
+learn:
+  label: "Learn"
+software:
+  label: "Software"
+updates:
+  label: "Updates"
diff --git a/data/contributors.yml b/data/contributors.yml
new file mode 100644
index 00000000..7ccc0e65
--- /dev/null
+++ b/data/contributors.yml
@@ -0,0 +1,11606 @@
+- name: Leah Wasser
+  github_username: lwasser
+  github_image_id: 7649194
+  title:
+    - Executive Director & Founder
+    - Emeritus editor
+  sort: 1
+  bio: Open education, Open source and Open Science.Executive Director
+      @pyOpenSci
+  organization: pyOpenSci
+  date_added: '2019-10-10'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: true
+  advisory: false
+  emeritus_advisory: false
+  twitter: leahawasser
+  mastodon: https://fosstodon.org/@leahawasser
+  orcidid: 0000-0002-8177-6550
+  partners:
+  website: https://www.leahwasser.com
+  board: true
+  contributor_type:
+    - code-contrib
+    - community
+    - editor
+    - guidebook-contrib
+    - leadership
+    - maintainer
+    - open-education
+    - package-guide
+    - package-maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+    - cynetdiff
+    - errdapy
+    - nbless
+    - pandera
+    - pygmt
+    - pyrolite
+  packages_submitted:
+    - earthpy
+  packages_reviewed:
+  location: United States
+  email: leah@pyopensci.org
+- name: Karen Cranston
+  github_username: kcranston
+  github_image_id: 312034
+  title: Executive Council
+  sort: 3
+  bio:
+  organization:
+  date_added: '2022-11-09'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: kcranstn
+  mastodon:
+  orcidid:
+  partners:
+  website: https://karencranston.ca/
+  board: true
+  contributor_type:
+    - leadership
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Ottawa, ON
+  email: karen.cranston@gmail.com
+- name: April Johnson
+  github_username: aprilmj
+  github_image_id: 147750733
+  title: Executive Council
+  sort: 3
+  bio:
+  organization:
+  date_added: '2022-11-09'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://www.apriljohnson.io/
+  board: true
+  contributor_type:
+    - leadership
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Tracy Teal
+  github_username: tracykteal
+  github_image_id: 889238
+  title:
+    - Emeritus Board chair
+    - Emeritus Executive Council
+  sort:
+  bio:
+  organization:
+  date_added: '2022-11-09'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: true
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - leadership
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email: tkteal@gmail.com
+- name: Carol Willing
+  github_username: willingc
+  github_image_id: 2680980
+  title: Advisory Council
+  sort: 2
+  bio: Project Jupyter, nteract, and CPython core developer@python | @jupyter
+      | @jupyterhub | @ipython | @nteract | @pysplash
+  organization: Willing Consulting
+  date_added: '2023-03-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: true
+  emeritus_advisory: false
+  twitter: WillingCarol
+  mastodon:
+  orcidid:
+  partners:
+  website: https://hachyderm.io/web/@willingc
+  board: false
+  contributor_type:
+    - code-contrib
+    - community
+    - guidebook-contrib
+    - leadership
+    - open-education
+    - package-guide
+    - peer-review
+    - peer-review-guide
+    - reviewer
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - devicely
+  location: San Diego
+  email: carolcode@willingconsulting.com
+- name: Neil Chue Hong
+  github_username: npch
+  github_image_id: 1507151
+  title:
+  sort:
+  bio: Director of the Software Sustainability Institute (@softwaresaved).
+      Editor-in-Chief of the Journal of Open Research Software. Interested in
+      software metrics.
+  organization: '@softwaresaved'
+  date_added: '2023-02-24'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: true
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://www.software.ac.uk
+  board: false
+  contributor_type:
+    - contributor
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Edinburgh, United Kingdom
+  email:
+- name: Erin Robinson
+  github_username: erinmr
+  github_image_id: 2915555
+  title: Advisory Council
+  sort:
+  bio:
+  organization:
+  date_added: '2023-06-15'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: true
+  emeritus_advisory: false
+  twitter: connector_erin
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - leadership
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email: erinmr@gmail.com
+- name: Chris Holdgraf
+  github_username: choldgraf
+  github_image_id: 1839645
+  title: Advisory Council
+  sort:
+  bio: I work with Project Jupyter and other open communities to build tools
+      and solve problems for scientific research and education.
+  organization: UC Berkeley
+  date_added: '2019-10-10'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: true
+  emeritus_advisory: false
+  twitter: choldgraf
+  mastodon:
+  orcidid:
+  partners:
+  website: https://chrisholdgraf.com
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - leadership
+    - package-guide
+    - peer-review-guide
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - erdapy
+  location: California
+  email:
+- name: Inessa Pawson
+  github_username: InessaPawson
+  github_image_id: 43481325
+  title: Advisory Council
+  sort: 1
+  bio: NumPy Contributor Experience LeadOpen Source Program Manager at
+      OpenTeams Incubator
+  organization: '@numpy'
+  date_added: '2023-03-21'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: true
+  emeritus_advisory: false
+  twitter: inessapawson
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - leadership
+    - package-guide
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email: inessapawson@gmail.com
+- name: Pradyun Gedam
+  github_username: pradyunsg
+  github_image_id: 3275593
+  title: Advisory Council
+  sort:
+  bio: "@pypa member, @psf fellow, @toml-lang core, @sphinx-doc contributor. Past
+      intern at @enthought and IITB.Don't email or tweet me for tech support."
+  organization: '@bloomberg Python Infrastructure'
+  date_added: '2023-03-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: true
+  emeritus_advisory: false
+  twitter: pradyunsg
+  mastodon: https://mastodon.social/@pradyunsg
+  orcidid:
+  partners:
+  website: https://pradyunsg.me
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - leadership
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: London, UK
+  email:
+- name: Ivan Ogasawara
+  github_username: xmnlab
+  github_image_id: 5209757
+  title:
+    - Advisory Council
+    - Emeritus editor
+  sort:
+  bio: Open Source Developer
+  organization: xmnlab
+  date_added: '2019-10-15'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: true
+  advisory: true
+  emeritus_advisory: false
+  twitter: xmnlab
+  mastodon:
+  orcidid: 0000-0001-5049-4289
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - alumni-editor
+    - code-contrib
+    - community
+    - editor
+    - guidebook-contrib
+    - leadership
+    - metrics-contrib
+    - package-guide
+    - peer-review
+    - peer-review-guide
+    - reviewer
+    - web-contrib
+  packages_eic:
+  packages_editor:
+    - devicely
+    - jointly
+    - sevivi
+  packages_submitted:
+  packages_reviewed:
+    - movingpandas
+    - pandera
+  location: Earth
+  email: ivan.ogasawara@gmail.com
+- name: Filipe
+  github_username: ocefpaf
+  github_image_id: 950575
+  title:
+    - Advisory Council
+    - Editor
+  sort:
+  bio: Filipe Fernandes is a Physical oceanographer by training, turned
+      research software engineer, and a software packager hobbyist.
+  organization:
+  date_added: '2019-10-17'
+  deia_advisory: false
+  editorial_board: true
+  emeritus_editor: false
+  advisory: true
+  emeritus_advisory: false
+  twitter: ocefpaf
+  mastodon:
+  orcidid: 0000-0003-4165-2913
+  partners:
+  website: https://ocefpaf.github.io/python4oceanographers
+  board: false
+  contributor_type:
+    - editor
+    - guidebook-contrib
+    - leadership
+    - package-guide
+    - peer-review
+    - reviewer
+    - web-contrib
+  packages_eic:
+  packages_editor:
+    - afscgap
+    - xnemogcm
+  packages_submitted:
+    - errdapy
+  packages_reviewed:
+    - nbless
+  location: Florianópolis, SC
+  email: ocefpaf@gmail.com
+- name: Leonardo Uieda
+  github_username: leouieda
+  github_image_id: 290082
+  title: Emeritus Advisory Council
+  sort:
+  bio: Geophysicist investigating Earth's gravity & magnetic fields from
+      global to microscopic scale 🛰️🔬🌎
+  organization: University of Liverpool
+  date_added: '2023-01-18'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: true
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://www.leouieda.com
+  board: false
+  contributor_type:
+    - leadership
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Liverpool, UK
+  email: email@leouieda.com
+- name: Lindsey Heagy
+  github_username: lheagy
+  github_image_id: 6361812
+  title: Emeritus Advisory Council
+  sort:
+  bio: Asst. Prof at UBC EOAS. Researcher working on geophysical simulations
+      and inversions (in @simpeg!) and data science.
+  organization: '@simpeg, @geoscixyz, @ubcgif, @2i2c_org'
+  date_added: '2019-12-10'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: true
+  twitter: lindsey_jh
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - leadership
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email: lheagy@eos.ubc.ca
+- name: Martin Fleischmann
+  github_username: martinfleis
+  github_image_id: 36797143
+  title: Advisory Council
+  sort:
+  bio: Researcher in geographic data science. Member of @geopandas and @pysal
+      development teams.
+  organization:
+  date_added: '2020-04-09'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: true
+  emeritus_advisory: false
+  twitter: martinfleis
+  mastodon: https://fosstodon.org/@martinfleis
+  orcidid: 0000-0003-3319-3366
+  partners:
+  website: https://martinfleischmann.net
+  board: false
+  contributor_type:
+    - leadership
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - movingpandas
+    - pyinterpolate
+  location: Prague
+  email: martin@martinfleischmann.net
+- name: Yuvi Panda
+  github_username: yuvipanda
+  github_image_id: 30430
+  title: Advisory Council
+  sort: 2
+  bio:
+  organization: '@2i2c-org'
+  date_added: '2023-01-18'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: true
+  emeritus_advisory: false
+  twitter:
+  mastodon: https://hachyderm.io/@yuvipanda
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - community
+    - guidebook-contrib
+    - leadership
+    - package-guide
+    - peer-review-guide
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Chase Million
+  github_username: cmillion
+  github_image_id: 1483210
+  title: Advisory Council
+  sort: 0
+  bio:
+  organization:
+  date_added: '2023-11-20'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: true
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - leadership
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - swiftgalaxy
+  location:
+  email:
+- name: Ariane Sasso
+  github_username: arianesasso
+  github_image_id: 3659681
+  title:
+    - Emeritus Editor
+  sort: 3
+  bio: Researcher in Medical Informatics and Digital Health ⌚ 👩‍💻 🧬
+  organization: '@hpi-dhc'
+  date_added: '2021-08-24'
+  deia_advisory: true
+  editorial_board: false
+  emeritus_editor: true
+  advisory: false
+  emeritus_advisory: false
+  twitter: arianemsasso
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - editor
+    - guidebook-contrib
+    - maintainer
+    - package-guide
+    - package-maintainer
+    - peer-review
+    - peer-review-guide
+    - submitting-author
+  packages_eic:
+  packages_editor:
+    - biocypher
+    - pynteny
+  packages_submitted:
+    - devicely
+    - jointly
+  packages_reviewed:
+  location: Berlin, Germany
+  email: ariane.sasso@gmail.com
+- name: David Nicholson
+  github_username: NickleDave
+  github_image_id: 11934090
+  title:
+    - Emeritus Editor in Chief
+    - Editor
+  sort: 2
+  bio: ML, AI; behavior + cog + neuro. Open + inclusive science. Pythonista.
+      He/him/they/them. Habla espanglish y baila salsa y bachata a medio
+      tiempo.
+  organization:
+  date_added: '2019-12-10'
+  deia_advisory: false
+  editorial_board: true
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: nicholdav
+  mastodon: https://fosstodon.org/@nicholdav
+  orcidid: 0000-0002-4261-4719
+  partners:
+  website: https://nicholdav.info/
+  board: false
+  contributor_type:
+    - contributor
+    - editor
+    - eic
+    - maintainer
+    - package-guide
+    - peer-review
+    - peer-review-guide
+    - reviewer
+    - submitting-author
+    - web-contrib
+  packages_eic:
+    - ncompare
+    - sleplet
+  packages_editor:
+    - openomics
+    - physcraper
+    - pystiche
+  packages_submitted:
+    - crowsetta
+  packages_reviewed:
+    - plenoptic
+    - pydov
+  location: Charm City
+  email:
+- name: Chiara Marmo
+  github_username: cmarmo
+  github_image_id: 1662261
+  title:
+    - Emeritus Editor in Chief
+    - Emeritus Editor
+    - Peer review triage
+  sort:
+  bio:
+  organization:
+  date_added: '2023-01-24'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: true
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid: 0000-0003-2843-6044
+  partners:
+  website: https://orcid.org/0000-0003-2843-6044
+  board: false
+  contributor_type:
+    - community
+    - editor
+    - eic
+    - guidebook-contrib
+    - package-guide
+    - peer-review
+    - peer-review-guide
+    - reviewer
+  packages_eic:
+    - felupe
+    - montepy
+    - neonutilities
+    - solar data tools
+    - stingray
+    - thztools
+  packages_editor:
+    - astartes
+    - crowsetta
+    - fluidimage
+    - pooltool
+    - pypartmc
+    - sunpy
+  packages_submitted:
+  packages_reviewed:
+    - ncompare
+  location:
+  email:
+- name: Jenny Palomino
+  github_username: jlpalomino
+  github_image_id: 4017492
+  title: Emeritus Editor
+  sort: 3
+  bio: Technical Curriculum Developer, Data Engineering
+  organization: Google
+  date_added: '2019-10-25'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: true
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - contributor
+    - editor
+    - maintainer
+    - peer-review
+    - reviewer
+    - web-contrib
+  packages_eic:
+  packages_editor:
+    - movingpandas
+  packages_submitted:
+    - earthpy
+  packages_reviewed:
+    - erddapy
+  location:
+  email:
+- name: Szymon Moliński
+  github_username: SimonMolinsky
+  github_image_id: 31246246
+  title: Editor
+  sort: 2
+  bio: GIS, remote sensing, machine learning, time-series and spatial
+  organization: Sare
+  date_added: '2022-09-16'
+  deia_advisory: false
+  editorial_board: true
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - code-contrib
+    - community
+    - editor
+    - eic
+    - guidebook-contrib
+    - maintainer
+    - package-guide
+    - peer-review
+    - reviewer
+    - submitting-author
+  packages_eic:
+    - galassify
+    - galfitools
+    - tda-mapper
+  packages_editor:
+    - sleplet
+    - xgi
+  packages_submitted:
+    - pyinterpolate
+  packages_reviewed:
+    - pygmt
+  location:
+  email: simon@ml-gis-service.com
+- name: Anita Graser
+  github_username: anitagraser
+  github_image_id: 590385
+  title:
+    - Emeritus Editor
+  sort: 3
+  bio: Spatial data science with a focus on mobility & data quality
+  organization:
+  date_added: '2020-03-26'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: true
+  advisory: false
+  emeritus_advisory: false
+  twitter: underdarkGIS
+  mastodon:
+  orcidid:
+  partners:
+  website: https://anitagraser.com
+  board: false
+  contributor_type:
+    - editor
+    - maintainer
+    - package-maintainer
+    - peer-review
+    - submitting-author
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - movingpandas
+  packages_reviewed:
+  location:
+  email:
+- name: Alex Batisse
+  github_username: Batalex
+  github_image_id: 11004857
+  title:
+    - Emeritus Editor in Chief
+    - EmeritusEditor
+  sort: 2
+  bio:
+  organization:
+  date_added: '2023-02-04'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: true
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon: https://fosstodon.org/@batalex
+  orcidid:
+  partners:
+  website: https://batalex.github.io
+  board: false
+  contributor_type:
+    - code-contrib
+    - community
+    - editor
+    - eic
+    - package-guide
+    - peer-review
+    - peer-review-guide
+    - reviewer
+    - web-contrib
+  packages_eic:
+    - ams
+    - cynetdiff
+    - fluidimage
+    - great tables
+    - pooltool
+    - pypartmc
+    - quadratik
+  packages_editor:
+    - cardsort
+    - great tables
+    - harmonize-wq
+    - pymultifit
+    - sciform
+    - xclim
+  packages_submitted:
+  packages_reviewed:
+    - pynteny
+  location:
+  email: alexandre.batisse@hey.com
+- name: Max Joseph
+  github_username: mbjoseph
+  github_image_id: 2664564
+  title:
+  sort:
+  bio: AI + Earth Observation + Bayesian stats
+  organization: '@planetlabs'
+  date_added: '2019-10-17'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: mxwlj
+  mastodon:
+  orcidid:
+  partners:
+  website: https://mbjoseph.github.io
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - maintainer
+    - peer-review
+    - peer-review-guide
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - earthpy
+  packages_reviewed:
+    - pandera
+  location: Denver, CO
+  email: maxwellbjoseph@gmail.com
+- name: Luiz Irber
+  github_username: luizirber
+  github_image_id: 6642
+  title:
+    - Emeritus editor
+  sort:
+  bio: 'CS PhD @ucdavis,Rustacean and Pythonista.Previously: @dib-lab'
+  organization:
+  date_added: '2019-10-17'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: true
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://luizirber.org
+  board: false
+  contributor_type:
+    - code-contrib
+    - community
+    - editor
+    - maintainer
+    - metrics-contrib
+    - peer-review
+  packages_eic:
+  packages_editor:
+    - earthpy
+  packages_submitted:
+    - sourmash
+  packages_reviewed:
+  location: Davis, CA
+  email:
+- name: Jesse Mostipak
+  github_username: kierisi
+  github_image_id: 23085445
+  title:
+  sort: 3
+  bio:
+  organization: pyOpenSci
+  date_added: '2023-11-21'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+    - peer-review-guide
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Paige Bailey
+  github_username: dynamicwebpaige
+  github_image_id: 3712347
+  title:
+  sort:
+  bio: ✨ Keep it simple, make it scale. AI should be about empowering users
+      and building understanding. 👩‍💻Product Lead (Generative Models)
+      @DeepMind | ex-@GitHub
+  organization: '@GitHub'
+  date_added: '2023-02-24'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: dynamicwebpaige
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - contributor
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Seattle, WA
+  email: paige.bailey@alumni.rice.edu
+- name: Carson Farmer
+  github_username: carsonfarmer
+  github_image_id: 1220613
+  title:
+  sort:
+  bio: Research & Development @textileio and @tablelandnetwork
+  organization: '@textileio @tablelandnetwork'
+  date_added: '2023-02-24'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: carsonfarmer
+  mastodon:
+  orcidid:
+  partners:
+  website: https://carsonfarmer.com
+  board: false
+  contributor_type:
+    - contributor
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Victoria, B.C., Canada
+  email: carson.farmer@gmail.com
+- name: Joe Hamman
+  github_username: jhamman
+  github_image_id: 2443309
+  title:
+  sort:
+  bio: Scientist and Engineer and Human.
+  organization: Earthmover
+  date_added: '2023-02-24'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: _jhamman
+  mastodon:
+  orcidid:
+  partners:
+  website: https://joehamman.com
+  board: false
+  contributor_type:
+    - contributor
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Seattle, WA
+  email: joe@earthmover.io
+- name: Kylen Solvik
+  github_username: kysolvik
+  github_image_id: 24379590
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2023-02-24'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - contributor
+    - guidebook-contrib
+    - peer-review
+    - peer-review-guide
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - nbless
+  location:
+  email: kysolvik@gmail.com
+- name: Martin Skarzynski
+  github_username: marskar
+  github_image_id: 12806339
+  title:
+  sort:
+  bio: 🧮Biostatistics Branch🏛NCI Division of🦀Cancer Epidemiology and🧬Genetics
+      (DCEG)💻Bioinformatics📊DataScience💺Co-chair🎓FAES🐍Python®Rstats⚕Health🤖ML🧠AI
+  organization:
+  date_added: '2023-02-24'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://marskar.github.io/
+  board: false
+  contributor_type:
+    - contributor
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - nbless
+  packages_reviewed:
+  location: Rockville/Bethesda, Maryland
+  email:
+- name: Mike Trizna
+  github_username: MikeTrizna
+  github_image_id: 472677
+  title:
+  sort:
+  bio:
+  organization: Smithsonian Institution
+  date_added: '2023-02-24'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - contributor
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Washington, DC
+  email: triznam@si.edu
+- name: Niels Bantilan
+  github_username: cosmicBboy
+  github_image_id: 2816689
+  title:
+  sort:
+  bio: Data Scientist, Machine Learning Engineer
+  organization: '@unionai'
+  date_added: '2019-12-10'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: cosmicbboy
+  mastodon:
+  orcidid:
+  partners:
+  website: https://cosmicbboy.github.io/
+  board: false
+  contributor_type:
+    - contributor
+    - maintainer
+    - package-maintainer
+    - peer-review
+    - peer-review-guide
+    - submitting-author
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - pandera
+  packages_reviewed:
+  location: Atlanta, GA, US
+  email: niels.bantilan@gmail.com
+- name: Sean Gillies
+  github_username: sgillies
+  github_image_id: 33697
+  title:
+  sort:
+  bio: b. 1969, he/him
+  organization: '@planetlabs'
+  date_added: '2019-12-10'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://sgillies.net
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - earthpy
+  location: Fort Collins, Colorado
+  email: sean.gillies@gmail.com
+- name: Rohit Goswami
+  github_username: HaoZeke
+  github_image_id: 4336207
+  title:
+    - Editor
+  sort:
+  bio:
+  organization: '@Quansight-Labs, @TheochemUI'
+  date_added: '2019-12-10'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: rg0swami
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - earthpy
+  location: University of Iceland
+  email: rog32@hi.is
+- name: Morgan Williams
+  github_username: morganjwilliams
+  github_image_id: 11415019
+  title:
+  sort:
+  bio:
+  organization: CSIRO Mineral Resources
+  date_added: '2020-06-08'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: metasomite
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - package-maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - pyrolite
+  packages_reviewed:
+  location: Perth, WA, Australia
+  email:
+- name: Philip Meier
+  github_username: pmeier
+  github_image_id: 6849766
+  title:
+  sort:
+  bio: Senior Software Engineer working on PyTorch / torchvision
+  organization: '@Quansight'
+  date_added: '2020-10-14'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - package-maintainer
+    - peer-review
+    - reviewer
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - pystiche
+  packages_reviewed:
+    - sevivi
+  location: Germany
+  email:
+- name: Edgar Riba
+  github_username: edgarriba
+  github_image_id: 5157099
+  title:
+  sort:
+  bio: '@kornia Creator | PhD, Computer Vision Research Engineer'
+  organization: Kornia.org
+  date_added: '2020-10-14'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: edgarriba
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - pystiche
+    - sevivi
+  location: Barcelona, Spain
+  email: edgar.riba@gmail.com
+- name: Databank Ondergrond Vlaanderen
+  github_username: DOV-Vlaanderen
+  github_image_id: 24718915
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2021-02-19'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-maintainer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - pydov
+  packages_reviewed:
+  location:
+  email:
+- name: Roel Huybrechts
+  github_username: Roel
+  github_image_id: 140299
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2021-03-02'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://mastodon.social/@rhuybrec
+  board: false
+  contributor_type:
+    - package-maintainer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - pydov
+  packages_reviewed:
+  location:
+  email: roel@huybrechts.re
+- name: Stijn Van Hoey
+  github_username: stijnvanhoey
+  github_image_id: 754862
+  title:
+  sort:
+  bio:
+  organization: '@fluves'
+  date_added: '2021-03-02'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-maintainer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - pydov
+  packages_reviewed:
+  location:
+  email:
+- name: Pieter Jan Haest
+  github_username: pjhaest
+  github_image_id: 22764347
+  title:
+  sort:
+  bio: Project manager industry 4.0
+  organization: De Watergroep
+  date_added: '2021-03-02'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://corporate.dewatergroep.be/en
+  board: false
+  contributor_type:
+    - package-maintainer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - pydov
+  packages_reviewed:
+  location: Belgium
+  email:
+- name: Nhat (Jonny) Tran
+  github_username: JonnyTran
+  github_image_id: 4750391
+  title:
+  sort:
+  bio: Graph neural networks, bioinformatics, non-coding RNA, NLP, and ML
+      engineering.
+  organization: Actively looking
+  date_added: '2021-04-30'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: Jonny_Wireless
+  mastodon:
+  orcidid: 0000-0002-2575-9633
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - package-maintainer
+    - peer-review
+    - reviewer
+    - submitting-author
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - openomics
+  packages_reviewed:
+    - xgi
+  location:
+  email:
+- name: Katharina Sielemann
+  github_username: ksielemann
+  github_image_id: 62541949
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2021-05-07'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: ksielemann
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - openomics
+  location:
+  email:
+- name: Moritz Lürig
+  github_username: mluerig
+  github_image_id: 15648068
+  title:
+  sort:
+  bio: Postdoc in ecology and evolution; interested in computer vision and
+      ecological informatics
+  organization: Lund University
+  date_added: '2021-05-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: mluerig
+  mastodon:
+  orcidid:
+  partners:
+  website: https://www.luerig.net
+  board: false
+  contributor_type:
+    - contributor
+    - maintainer
+    - package-maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - phenopype
+  packages_reviewed:
+  location: Sweden
+  email: moritz.luerig@gmail.com
+- name: Emily Jane McTavish
+  github_username: snacktavish
+  github_image_id: 1652782
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2021-09-16'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://McTavishLab.github.io
+  board: false
+  contributor_type:
+    - contributor
+    - editor
+    - maintainer
+    - package-maintainer
+    - peer-review
+    - reviewer
+    - submitting-author
+  packages_eic:
+  packages_editor:
+    - sourmash
+  packages_submitted:
+    - physcraper
+  packages_reviewed:
+    - taxpasta
+  location:
+  email: ejmctavish@ucmerced.edu
+- name: Luna L. Sanchez Reyes
+  github_username: LunaSare
+  github_image_id: 26721915
+  title:
+  sort:
+  bio: Nature. Computers. Life. Doing open science with @phylotastic and
+      @OpenTreeOfLife
+  organization: University of California, Merced
+  date_added: '2021-09-16'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: LunaSare
+  mastodon:
+  orcidid:
+  partners:
+  website: https://www.lunasare.com
+  board: false
+  contributor_type:
+    - contributor
+    - maintainer
+    - package-maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - physcraper
+  packages_reviewed:
+  location: Merced, CA, USA
+  email: sanchez.reyes.luna@gmail.com
+- name: K. Arthur Endsley
+  github_username: arthur-e
+  github_image_id: 1211103
+  title:
+  sort:
+  bio: Computational Geoscientist
+  organization: University of Montana NTSG
+  date_added: '2022-01-12'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - jointly
+  location: Missoula, MT
+  email: endsley@umich.edu
+- name: Álex Sáez
+  github_username: AlexS12
+  github_image_id: 6061587
+  title:
+  sort:
+  bio: Aerospace engineer passionate about Flight Mechanics.Python, Fortran,
+      Matlab and lately Julia. (These are my personal projects)
+  organization: AIRBUS D&S
+  date_added: '2022-01-12'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - jointly
+  location: Madrid (Spain)
+  email: alex.saez.12@gmail.com
+- name: Julius Busecke
+  github_username: jbusecke
+  github_image_id: 14314623
+  title:
+  sort:
+  bio: Climate Scientist | Oceanographer |Open Source Enthusiast
+  organization: Columbia/LDEO -- @ocean-transport
+  date_added: '2022-09-08'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: JuliusBusecke
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - pygmt
+  location: Brooklyn, New York
+  email:
+- name: Nicolas Palopoli
+  github_username: NPalopoli
+  github_image_id: 1713937
+  title: Co-Executive Director
+  sort:
+  bio: Computational Biologist
+  organization: Universidad Nacional de Quilmes & MetaDocencia
+  date_added: '2023-03-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon: https://fediscience.org/@npalopoli
+  orcidid: ​0000-0001-7925-6436
+  partners:
+  website: https://about.me/npalopoli
+  board: false
+  contributor_type:
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Buenos Aires, Argentina
+  email: nicopalo@gmail.com
+- name: Erik Welch
+  github_username: eriknw
+  github_image_id: 2058401
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2023-03-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: eriknwelch
+  mastodon:
+  orcidid:
+  partners:
+  website: https://fosstodon.org/@eriknw
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - maintainer
+    - package-guide
+    - peer-review
+    - peer-review-guide
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - python-graphblas
+  packages_reviewed:
+  location: Austin, TX
+  email:
+- name: Pamphile Roy
+  github_username: tupui
+  github_image_id: 23188539
+  title:
+  sort:
+  bio: Artificial Intelligence, Backend, Data, Stats, Engineer probably doing
+      some Python 🐍
+  organization: '@Quansight'
+  date_added: '2023-03-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: PamphileRoy
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Graz, Austria
+  email: roy.pamphile@gmail.com
+- name: Jonny Saunders
+  github_username: sneakers-the-rat
+  github_image_id: 12961499
+  title: Emeritus Editor
+  sort: 2
+  bio: Bad at programming in beautiful Oregon
+  organization:
+  date_added: '2023-03-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: true
+  advisory: false
+  emeritus_advisory: false
+  twitter: json_dirs
+  mastodon: https://neuromatch.social/@jonny
+  orcidid: 0000-0003-0545-5066
+  partners:
+  website: https://jon-e.net
+  board: false
+  contributor_type:
+    - community
+    - editor
+    - eic
+    - guidebook-contrib
+    - open-education
+    - package-guide
+    - peer-review
+    - reviewer
+    - web-contrib
+  packages_eic:
+    - plenoptic
+  packages_editor:
+    - automata
+    - cynetdiff
+    - plenoptic
+  packages_submitted:
+  packages_reviewed:
+    - python-graphblas
+  location:
+  email:
+- name: Randy Döring
+  github_username: radoering
+  github_image_id: 30527984
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2023-03-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Juan Luis Cano Rodríguez
+  github_username: astrojuanlu
+  github_image_id: 316517
+  title:
+  sort:
+  bio: Open Knowledge + Radical Transparency
+  organization: '@kedro-org'
+  date_added: '2023-03-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - package-guide
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Spain
+  email: hello@juanlu.space
+- name: Henry Schreiner
+  github_username: henryiii
+  github_image_id: 4616906
+  title:
+  sort:
+  bio: Particle physicist and software architect working with @iris-hep.
+      @scikit-hep, @pybind, and @scikit-build admin. @pypa member.
+  organization: Princeton University
+  date_added: '2023-03-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: henryschreiner3
+  mastodon:
+  orcidid:
+  partners:
+  website: https://iscinumpy.dev
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Princeton, NJ
+  email: HenrySchreinerIII@gmail.com
+- name: Stefan van der Walt
+  github_username: stefanv
+  github_image_id: 45071
+  title:
+  sort:
+  bio: Everything Scientific Python. Works on NumPy, SciPy, scikit-image,
+      NetworkX, etc. Author of Elegant SciPy. Researcher at UC Berkeley.
+  organization: University of California, Berkeley
+  date_added: '2023-03-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: stefanvdwalt
+  mastodon:
+  orcidid:
+  partners:
+  website: https://mentat.za.net
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - package-guide
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Berkeley, CA
+  email:
+- name: Eli Schwartz
+  github_username: eli-schwartz
+  github_image_id: 6551424
+  title:
+  sort:
+  bio: '@archlinux bugwrangler and Trusted User'
+  organization:
+  date_added: '2023-03-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email: eschwartz93@gmail.com
+- name: Ralf Gommers
+  github_username: rgommers
+  github_image_id: 98330
+  title:
+  sort:
+  bio: NumPy, SciPy, data-apis.org, PyWavelets maintainer. Building open
+      source communities at Quansight Labs.
+  organization: Quansight
+  date_added: '2023-03-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: ralfgommers
+  mastodon:
+  orcidid:
+  partners:
+  website: https://github.com/rgommers/
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Netherlands
+  email: ralf.gommers@gmail.com
+- name: Ofek Lev
+  github_username: ofek
+  github_image_id: 9677399
+  title:
+  sort:
+  bio: I like developing beautiful APIs.
+  organization: '@datadog'
+  date_added: '2023-03-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://ofek.dev
+  board: false
+  contributor_type:
+    - code-contrib
+    - community
+    - guidebook-contrib
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Knowhere
+  email: oss@ofek.dev
+- name: Tom Augspurger
+  github_username: TomAugspurger
+  github_image_id: 1312546
+  title:
+  sort:
+  bio:
+  organization: '@microsoft'
+  date_added: '2023-03-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://tomaugspurger.github.io
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email: tom.w.augspurger@gmail.com
+- name: Ryan Abernathey
+  github_username: rabernat
+  github_image_id: 1197350
+  title:
+  sort:
+  bio: Open source maintainer. CEO and co-founder of @earth-mover.
+      @pangeo-data creator. Professor of Earth and Environmental Sciences at
+      Columbia University.
+  organization: Earthmover PBC
+  date_added: '2023-03-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: rabernat
+  mastodon:
+  orcidid:
+  partners:
+  website: https://github.com/rabernat
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: New York City
+  email:
+- name: Steve Moss
+  github_username: gawbul
+  github_image_id: 321291
+  title:
+  sort:
+  bio: Dad, husband, and PhD 👨‍🎓 Scientist 👨‍🔬 Technologist 📱 Engineer 👨‍💻
+      Bibliophile 📚 Philomath 🧐
+  organization: Dr Stephen P. Moss
+  date_added: '2023-03-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: gawbul
+  mastodon:
+  orcidid:
+  partners:
+  website: https://www.gawbul.io
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - peer-review
+    - peer-review-guide
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - openomics
+  location: Earth
+  email:
+- name: Matthew Brett
+  github_username: matthew-brett
+  github_image_id: 67612
+  title:
+  sort:
+  bio:
+  organization: London Interdisciplinary School
+  date_added: '2023-03-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: London, UK
+  email:
+- name: Zehua Chen
+  github_username: ReventonC
+  github_image_id: 6276623
+  title:
+  sort:
+  bio: Cat-centered Design.
+  organization:
+  date_added: '2023-03-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Atlanta, GA
+  email:
+- name: Sumit Kashyap
+  github_username: sumit-158
+  github_image_id: 96618001
+  title:
+  sort:
+  bio: Open source and community | GSoC' 22 @openfoodfacts |
+  organization:
+  date_added: '2023-03-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: itss_sumit
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: India
+  email: mr.sumitkrr@gmail.com
+- name: Erik Sundell
+  github_username: consideRatio
+  github_image_id: 3837114
+  title:
+  sort:
+  bio: Climate change mitigation efforts need nuclear alongside other low
+      carbon sources.https://twitter.com/e_Sundell/status/1258480862359937024
+  organization: Sundell Open Source Consulting AB
+  date_added: '2023-03-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: e_Sundell
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Sweden
+  email: erik.i.sundell@gmail.com
+- name: Ariel Rokem
+  github_username: arokem
+  github_image_id: 118582
+  title:
+  sort:
+  bio:
+  organization: The University of Washington eScience Institute
+  date_added: '2023-03-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://arokem.org
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Seattle, WA
+  email: arokem@gmail.com
+- name: James Mason
+  github_username: jmason86
+  github_image_id: 947614
+  title:
+  sort:
+  bio: solar physics, space weather, and aerospace engineering. principal
+      investigator of nasa's suncet mission.
+  organization: Johns Hopkins Applied Physics Lab
+  date_added: '2023-03-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: starfleetjames
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Washington DC
+  email:
+- name: James Tocknell
+  github_username: aragilar
+  github_image_id: 1281144
+  title:
+  sort:
+  bio: PhD Student in Astrophysics
+  organization: Department of Physics and Astronomy, Macquarie University
+  date_added: '2023-04-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Frost Ming
+  github_username: frostming
+  github_image_id: 16336606
+  title:
+  sort:
+  bio: Love 🐍 Python, 📷 Photography and beautiful things
+  organization:
+  date_added: '2023-04-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: frostming90
+  mastodon:
+  orcidid:
+  partners:
+  website: https://frostming.com
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Shenzhen, China
+  email: me@frostming.com
+- name: Hugo van Kemenade
+  github_username: hugovk
+  github_image_id: 1324225
+  title:
+  sort:
+  bio: Python core developer, PSF Fellow, open-source maintainer, PEP editor,
+      NaNoGenMo organiser
+  organization: Nord Software
+  date_added: '2023-04-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - package-guide
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Helsinki, Finland
+  email:
+- name: Matt Hall
+  github_username: kwinkunks
+  github_image_id: 1692372
+  title:
+  sort:
+  bio: Open source scientist / programmer.Founder of @softwareunderground.
+  organization: '@equinor'
+  date_added: '2023-04-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Bergen, Norway
+  email: kwinkunks@gmail.com
+- name: Jannis Leidel
+  github_username: jezdez
+  github_image_id: 1610
+  title:
+  sort:
+  bio: Principal SWE at @anaconda working on @conda. @conda-forge core member.
+      @python director and fellow.@jazzband and @pypa founder. @mozilla and
+      @django alum
+  organization: '@anaconda'
+  date_added: '2023-04-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: jezdez
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Germany
+  email:
+- name: Dave Hirschfeld
+  github_username: dhirschfeld
+  github_image_id: 881019
+  title:
+  sort:
+  bio: Full-Stack Analytics Engineer
+  organization:
+  date_added: '2023-04-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: dave_hirschfeld
+  mastodon:
+  orcidid:
+  partners:
+  website: https://dhirschfeld.github.io
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Brisbane, Australia
+  email: dave.hirschfeld@gmail.com
+- name: Benjamin Rodenberg
+  github_username: BenjaminRodenberg
+  github_image_id: 5740604
+  title:
+  sort:
+  bio:
+  organization: Technical University of Munich
+  date_added: '2023-04-14'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - community
+    - peer-review
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email: benjamin.rodenberg@in.tum.de
+- name: Travis Logan
+  github_username: tlogan2000
+  github_image_id: 22454970
+  title:
+  sort:
+  bio:
+  organization: Ouranos
+  date_added: '2023-04-14'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - community
+    - maintainer
+    - peer-review
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - xclim
+  packages_reviewed:
+  location: Montreal
+  email:
+- name: Pascal Bourgault
+  github_username: aulemahal
+  github_image_id: 20629530
+  title:
+  sort:
+  bio: Physical oceanography graduate turned climate science specialist and
+      scientific developer.
+  organization: Ouranos
+  date_added: '2023-04-14'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - community
+    - maintainer
+    - peer-review
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - xclim
+  packages_reviewed:
+  location: Montréal
+  email: bourgault.pascal@ouranos.ca
+- name: Arne
+  github_username: enra64
+  github_image_id: 7622426
+  title:
+  sort:
+  bio: IT-Systems Engineering Student at Hasso Plattner Institute, more active
+      at gitlab.com/enra64
+  organization:
+  date_added: '2023-04-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://gitlab.com/enra64
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - jointly
+  packages_reviewed:
+  location:
+  email:
+- name: Robert Guggenberger
+  github_username: agricolab
+  github_image_id: 20556511
+  title:
+  sort:
+  bio: Dr.rer.soc. Dr.rer.nat. Rock climbing, Research Software, Neurofeedback
+      and Brain Stimulation.
+  organization: neuroConn
+  date_added: '2023-04-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: agricolabs
+  mastodon:
+  orcidid:
+  partners:
+  website: https://fosstodon.org/@agricolab
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - devicely
+  location: Tuebingen, Germany
+  email:
+- name: Boas Pucker
+  github_username: bpucker
+  github_image_id: 36674497
+  title:
+  sort:
+  bio: Professor at TU Braunschweig with research interests in plant genomics
+      and specialized metabolism.
+      Details:https://www.tu-braunschweig.de/en/ifp/pbb
+  organization: Plant Biotechnology and Bioinformatics, Institute of Plant
+      Biology, TU Braunschweig
+  date_added: '2023-04-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: boas_pucker
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - physcraper
+  location: Germany
+  email:
+- name: Leonardo de Oliveira Martins
+  github_username: leomrtns
+  github_image_id: 7119518
+  title:
+  sort:
+  bio: Bioinformatician @quadram-institute-bioscience (Norwich, UK).
+      Phylogenomics and Data Sciences.
+  organization: '@quadram-institute-bioscience'
+  date_added: '2023-04-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: leomrtns
+  mastodon:
+  orcidid:
+  partners:
+  website: https://leomrtns.github.io
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - physcraper
+  location: Norwich, UK
+  email: Leonardo.de-Oliveira-Martins@quadram.ac.uk
+- name: Soumith Chintala
+  github_username: soumith
+  github_image_id: 1310570
+  title:
+  sort:
+  bio: /\︿╱\ _________________________________\0_ 0
+      /╱\╱____________________________  \▁︹_/
+  organization: Facebook AI Research
+  date_added: '2023-04-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://soumith.ch
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - pystiche
+  location: New York, USA
+  email:
+- name: Arthur Porto
+  github_username: agporto
+  github_image_id: 20894263
+  title:
+  sort:
+  bio: Evolutionary Biology, Genetics and Machine learning
+  organization:
+  date_added: '2023-04-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - phenopype
+  location: Baton Rouge, LA
+  email:
+- name: Seth Donoughe
+  github_username: sdonoughe
+  github_image_id: 14017155
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2023-04-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: seth_donoughe
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - phenopype
+  location:
+  email:
+- name: Ben Cook
+  github_username: jbencook
+  github_image_id: 4348863
+  title:
+    - Guest editor
+  sort:
+  bio:
+  organization:
+  date_added: '2023-04-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: true
+  advisory: false
+  emeritus_advisory: false
+  twitter: jbencook
+  mastodon:
+  orcidid:
+  partners:
+  website: https://sparrow.dev
+  board: false
+  contributor_type:
+    - editor
+    - peer-review
+  packages_eic:
+  packages_editor:
+    - phenopype
+  packages_submitted:
+  packages_reviewed:
+  location: Omaha, NE
+  email: ben@sparrow.dev
+- name: Romain Beucher
+  github_username: rbeucher
+  github_image_id: 3680918
+  title:
+  sort:
+  bio: Model Evaluation and Diagnostics Team Lead for the Australian
+      Earth-System Simulator National Research Infrastructure (ACCESS-NRI)
+  organization: ACCESS-NRI
+  date_added: '2023-04-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: romain_beucher
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - pyrolite
+  location: Canberra, Australia
+  email: romain.beucher@anu.edu.au
+- name: Charles Le Losq
+  github_username: charlesll
+  github_image_id: 6821569
+  title:
+  sort:
+  bio: Geoscientist, Assistant Professor, willing to improve data reduction
+      protocols through programming and data science
+  organization: Institut de physique du globe de Paris
+  date_added: '2023-04-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: Charles_LeLosq
+  mastodon:
+  orcidid:
+  partners:
+  website: https://charlesll.github.io/
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - pyrolite
+  location: France
+  email: lelosq@ipgp.fr
+- name: Wei Ji
+  github_username: weiji14
+  github_image_id: 23487320
+  title:
+  sort:
+  bio: Geospatial Data Scientist/ML Practitioner @developmentseed. Towards
+      cloud-native geospatial machine learning!
+  organization: '@developmentseed'
+  date_added: '2023-04-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - pygmt
+  packages_reviewed:
+  location: Wellington
+  email:
+- name: Tessa Rhinehart
+  github_username: rhine3
+  github_image_id: 27306428
+  title:
+  sort:
+  bio: 'Work: research programmer creating computational tools for bioacoustics.
+      Play: tinkerer creating open-source tools for birders'
+  organization: University of Pittsburgh
+  date_added: '2023-03-29'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: TessaRhinehart
+  mastodon:
+  orcidid: 0000-0002-4352-3464
+  partners:
+  website: https://tessarhinehart.com
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - crowsetta
+  location: Pittsburgh, PA, USA
+  email: tessa.rhinehart@pitt.edu
+- name: Agustina
+  github_username: aguspesce
+  github_image_id: 13738018
+  title:
+  sort:
+  bio: Lic. in Physics and PhD in Geophysics.
+  organization:
+  date_added: '2023-04-12'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid: 0000-0002-5538-8845
+  partners:
+  website: https://aguspesce.github.io
+  board: false
+  contributor_type:
+    - community
+    - peer-review
+    - peer-review-guide
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - xclim
+  location: British Columbia, Canada
+  email: pesce.agustina@gmail.com
+- name: Sylvain HAUPERT
+  github_username: shaupert
+  github_image_id: 43136040
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2023-04-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - crowsetta
+  location: PARIS
+  email:
+- name: Yannick Jadoul
+  github_username: YannickJadoul
+  github_image_id: 8025744
+  title:
+  sort:
+  bio:
+  organization: Max Planck Institute for Psycholinguistics & Vrije
+      Universiteit Brussel
+  date_added: '2023-04-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - a
+    - c
+    - e
+    - o
+    - r
+    - s
+    - t
+    - w
+  location: Nijmegen, the Netherlands
+  email: Yannick.Jadoul@ai.vub.ac.be
+- name: Semidán Robaina
+  github_username: Robaina
+  github_image_id: 21340147
+  title:
+  sort:
+  bio: Computational Biology | Data Science | Python Dev. | Ph.D. Systems
+      Biology
+  organization: ULL
+  date_added: '2023-04-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: srobainae
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - community
+    - maintainer
+    - peer-review
+    - peer-review-guide
+    - reviewer
+    - submitting-author
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - pynteny
+  packages_reviewed:
+    - cardsort
+  location: Atlantic Ocean
+  email: srobaina@ull.edu.es
+- name: Trevor James Smith
+  github_username: Zeitsperre
+  github_image_id: 10819524
+  title:
+  sort:
+  bio: Python, Linux, and FOSS-GIS enthusiast. Climate Scenarios and Services
+      Specialist at Ouranos (@Ouranosinc) in Montreal.
+  organization: Ouranos
+  date_added: '2023-04-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - community
+    - maintainer
+    - package-guide
+    - peer-review
+    - peer-review-guide
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - xclim
+  packages_reviewed:
+  location: Montreal, Canada
+  email:
+- name: James Munroe
+  github_username: jmunroe
+  github_image_id: 6181563
+  title:
+  sort:
+  bio:
+  organization: '@2i2c-org'
+  date_added: '2023-04-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: __jmunroe
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - community
+    - peer-review
+    - peer-review-guide
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - xclim
+  location:
+  email: jmunroe@earthdata.ca
+- name: Corinna Thoben
+  github_username: c-thoben
+  github_image_id: 103432571
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2023-04-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - pynteny
+  location:
+  email:
+- name: Tom Russell
+  github_username: tomalrussell
+  github_image_id: 2762769
+  title: Editor
+  sort: 2
+  bio: Research software person. Work @nismod, tech lead @colouring-cities
+  organization: University of Oxford
+  date_added: '2023-04-18'
+  deia_advisory: false
+  editorial_board: true
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: tlrss
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - contributor
+    - editor
+    - guest editor
+    - package-guide
+    - peer-review
+  packages_eic:
+  packages_editor:
+    - ncompare
+    - python-graphblas
+  packages_submitted:
+  packages_reviewed:
+  location: Oxford / London
+  email:
+- name: C. Titus Brown
+  github_username: ctb
+  github_image_id: 51016
+  title: Editor
+  sort: 2
+  bio: Prof at UC Davis. Blogs at http://ivory.idyll.org/blog/ and tweets at
+      https://twitter.com/ctitusbrown.
+  organization: University of California, Davis
+  date_added: '2023-04-18'
+  deia_advisory: false
+  editorial_board: true
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: ctitusbrown
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - contributor
+    - editor
+    - guest editor
+    - maintainer
+    - package-guide
+    - peer-review
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+    - plot_phylo
+    - taxpasta
+  packages_submitted:
+    - sourmash
+  packages_reviewed:
+  location: Davis, CA
+  email: titus@idyll.org
+- name: Meenal Jhajharia
+  github_username: mjhajharia
+  github_image_id: 55153708
+  title: Emeritus Editor
+  sort: 2
+  bio:
+  organization: \varnothing
+  date_added: '2023-04-18'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: true
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - contributor
+    - editor
+    - guest editor
+    - peer-review
+  packages_eic:
+  packages_editor:
+    - bibat
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: John McCray
+  github_username: mccrayjr
+  github_image_id: 69483966
+  title:
+  sort:
+  bio: Software Developer
+  organization:
+  date_added: '2023-04-24'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - community
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Washington, DC
+  email:
+- name: Meer (Miriam) Williamson
+  github_username: meerkatters
+  github_image_id: 50787305
+  title:
+  sort:
+  bio: SE based in Seattle interested in public health.
+  organization: Fred Hutch
+  date_added: '2023-04-24'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - code-contrib
+    - community
+    - metrics-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Seattle, WA
+  email:
+- name: Tiffany Xiao
+  github_username: tiffanyxiao
+  github_image_id: 13580331
+  title:
+  sort:
+  bio: Currently a data science software engineer at Bloomberg.
+  organization: Bloomberg
+  date_added: '2023-04-24'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://tiffanyxiao.com/
+  board: false
+  contributor_type:
+    - code-contrib
+    - community
+    - metrics-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: New York, New York
+  email: cdtiffanyxiao@gmail.com
+- name: Austin
+  github_username: austinlg96
+  github_image_id: 19922895
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2023-04-24'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - code-contrib
+    - community
+    - metrics-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: JAKE
+  github_username: paajake
+  github_image_id: 12656820
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2023-04-24'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: paajake
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - code-contrib
+    - community
+    - metrics-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Ghana
+  email: paajake@gmail.com
+- name: Barnabas Bulpett (He/Him)
+  github_username: bbulpett
+  github_image_id: 6424805
+  title:
+  sort:
+  bio: Software Engineer
+  organization: '@vitalsource'
+  date_added: '2023-04-24'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - code-contrib
+    - community
+    - metrics-contrib
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Gotham
+  email:
+- name: Jeremy Paige
+  github_username: ucodery
+  github_image_id: 28751151
+  title:
+  sort:
+  bio:
+  organization: '@ActiveState'
+  date_added: '2023-05-26'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: ucodery
+  mastodon:
+  orcidid:
+  partners:
+  website: https://blog.ucodery.com
+  board: false
+  contributor_type:
+    - community
+    - guidebook-contrib
+    - open-education
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email: ucodery@gmail.com
+- name: Mahe Iram Khan
+  github_username: ForgottenProgramme
+  github_image_id: 65779580
+  title:
+  sort:
+  bio:
+  organization: Anaconda Inc.
+  date_added: '2023-05-26'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: IramMahe
+  mastodon:
+  orcidid:
+  partners:
+  website: https://forgottenprogramme.github.io/
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Berlin, Germany
+  email:
+- name: Qin
+  github_username: chiinita
+  github_image_id: 17188345
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2023-05-26'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: London, UK
+  email:
+- name: David Stansby
+  github_username: dstansby
+  github_image_id: 6197628
+  title:
+  sort:
+  bio:
+  organization: UCL
+  date_added: '2023-05-26'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: davidstansby
+  mastodon:
+  orcidid:
+  partners:
+  website: https://www.davidstansby.com
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - maintainer
+    - peer-review
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - sunpy
+  packages_reviewed:
+  location: London, UK
+  email: d.stansby@ucl.ac.uk
+- name: Juanita Gomez
+  github_username: juanis2112
+  github_image_id: 18587879
+  title:
+  sort:
+  bio: Computer Science PhD student at University of California, Santa Cruz
+      Community Manager at @scientific-python
+  organization: UC, Santa Cruz
+  date_added: '2023-05-26'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: juanitagomezr
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - code-contrib
+    - community
+    - metrics-contrib
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Santa Cruz, California
+  email: juanitagomezr2112@gmail.com
+- name: Sarah Kaiser
+  github_username: crazy4pi314
+  github_image_id: 6486256
+  title:
+  sort:
+  bio: Sr. Cloud Developer Advocate for Python @Microsoft | Python Foundation
+      Fellow  | Maker and breaker of many things
+  organization: Microsoft
+  date_added: '2023-05-26'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://www.sckaiser.com
+  board: false
+  contributor_type:
+    - code-contrib
+    - community
+    - metrics-contrib
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Seattle, WA
+  email: sckaiser@sckaiser.com
+- name: A Samuel Pottinger
+  github_username: sampottinger
+  github_image_id: 110391
+  title:
+  sort:
+  bio: Data scientist with a software engineering, data visualization, and
+      machine learning background. Occasionally contributes to Processing.
+  organization: UC Berkeley
+  date_added: '2023-06-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://gleap.org
+  board: false
+  contributor_type:
+    - maintainer
+    - package-maintainer
+    - peer-review
+    - reviewer
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - afscgap
+  packages_reviewed:
+    - tda-mapper
+  location:
+  email:
+- name: Anderson Bravalheri
+  github_username: abravalheri
+  github_image_id: 320755
+  title:
+  sort:
+  bio:
+  organization: University of Bristol
+  date_added: '2023-06-14'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Bristol, UK
+  email:
+- name: Daniel Possenriede
+  github_username: dpprdan
+  github_image_id: 1423562
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2023-06-14'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: dpprdan
+  mastodon:
+  orcidid:
+  partners:
+  website: https://possenrie.de
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Hamburg, Germany
+  email:
+- name: C.A.M. Gerlach
+  github_username: CAM-Gerlach
+  github_image_id: 17051931
+  title:
+  sort:
+  bio: NASA-funded deep learning, IoT and satellite researcher. UAH grad
+      student. Python and Spyder core dev. Python Docs Team and PEP Editor.
+      Star✦Fleet Commander.
+  organization: '@hamma-dev @python @spyder-ide @star-fleet-tours'
+  date_added: '2023-06-14'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: StarFleetTours
+  mastodon:
+  orcidid:
+  partners:
+  website: https://www.hamma.dev
+  board: false
+  contributor_type:
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Huntsville, AL, United States
+  email: CAM.Gerlach@Gerlach.CAM
+- name: Teddy Groves
+  github_username: teddygroves
+  github_image_id: 17163471
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2023-07-12'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid: 0000-0002-7109-3270
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - contributor
+    - maintainer
+    - peer-review
+    - submitting-author
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - bibat
+  packages_reviewed:
+  location:
+  email: groves.teddy@gmail.com
+- name: James A. Fellows Yates
+  github_username: jfy133
+  github_image_id: 17950287
+  title:
+  sort:
+  bio: Bioinformatician with specialism in ancient DNA and metagenomics.
+      nf-core core-team member and SPAAM community
+      founder.@jfy133@genomic.social
+  organization: HKI Jena, MPI-EVA Leipzig
+  date_added: '2023-07-12'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: jfy133
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - community
+    - maintainer
+    - peer-review
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - taxpasta
+  packages_reviewed:
+  location: Leipzig, Germany
+  email: jfy133@gmail.com
+- name: Moritz E. Beber
+  github_username: Midnighter
+  github_image_id: 135653
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2023-07-12'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: me_beber
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - community
+    - maintainer
+    - package-guide
+    - peer-review
+    - peer-review-guide
+    - reviewer
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - taxpasta
+  packages_reviewed:
+    - biocypher
+  location: Copenhagen, Denmark
+  email: midnighter@posteo.net
+- name: Szabolcs Horvát
+  github_username: szhorvat
+  github_image_id: 1212871
+  title:
+  sort:
+  bio: physicist at Center for Systems Biology Dresden
+  organization:
+  date_added: '2023-07-15'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid: 0000-0002-3100-523X
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - python-graphblas
+  location:
+  email: szhorvat@gmail.com
+- name: ruoxi
+  github_username: yang-ruoxi
+  github_image_id: 13646711
+  title:
+  sort:
+  bio: Computational materials scientist
+  organization:
+  date_added: '2023-07-15'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - package-guide
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: P. L. Lim
+  github_username: pllim
+  github_image_id: 2090236
+  title:
+  sort:
+  bio: My views and opinions are my own and do not represent my employer's.
+  organization: Space Telescope Science Institute
+  date_added: '2023-07-15'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - community
+    - guidebook-contrib
+    - maintainer
+    - peer-review
+    - peer-review-guide
+    - reviewer
+    - submitting-author
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - astropy
+  packages_reviewed:
+    - zodipy
+  location: Baltimore, MD, USA
+  email:
+- name: Nick Murphy
+  github_username: namurphy
+  github_image_id: 8931994
+  title:
+  sort:
+  bio: '"Never go up against a plasma physicist when puns are on the line."'
+  organization: Center for Astrophysics | Harvard & Smithsonian
+  date_added: '2023-07-15'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://orcid.org/0000-0001-6628-8033
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - package-guide
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Cambridge, Massachusetts, USA
+  email: namurphy@cfa.harvard.edu
+- name: Hans Moritz Günther
+  github_username: hamogu
+  github_image_id: 498688
+  title:
+    - Editor
+  sort: 2
+  bio:
+  organization: MIT
+  date_added: '2023-07-15'
+  deia_advisory: false
+  editorial_board: true
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+    - Astropy
+  website:
+  board: false
+  contributor_type:
+    - community
+    - editor
+    - guidebook-contrib
+    - open-education
+    - peer-review
+    - peer-review-guide
+    - web-contrib
+  packages_eic:
+  packages_editor:
+    - astrodata
+    - galfitools
+    - martini
+    - pyautogalaxy
+    - stingray
+  packages_submitted:
+  packages_reviewed:
+  location: Cambridge, MA, USA
+  email:
+- name: g-patlewicz
+  github_username: g-patlewicz
+  github_image_id: 52672925
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2023-07-15'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - guidebook-contrib
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Mike Sarahan
+  github_username: msarahan
+  github_image_id: 38393
+  title:
+  sort:
+  bio:
+  organization: '@posit-pbc'
+  date_added: '2023-07-15'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Austin, TX
+  email: msarahan@gmail.com
+- name: Thomas J. Fan
+  github_username: thomasjpfan
+  github_image_id: 5402633
+  title:
+  sort:
+  bio: Staff Software Engineer at Quansight Labs, @scikit-learn maintainer
+  organization: '@Quansight-Labs'
+  date_added: '2023-07-15'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: thomasjpfan
+  mastodon:
+  orcidid:
+  partners:
+  website: https://thomasjpfan.com
+  board: false
+  contributor_type:
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: New York City
+  email: thomasjpfan@gmail.com
+- name: Kerry McAdams
+  github_username: klmcadams
+  github_image_id: 58492561
+  title:
+  sort:
+  bio:
+  organization: '@ansys'
+  date_added: '2023-07-27'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Ricky Nilsson
+  github_username: rickynilsson
+  github_image_id: 12720117
+  title:
+  sort:
+  bio: Astronomer / Data Scientist / Applications Developer
+  organization: Caltech-IPAC/NExScI
+  date_added: '2023-07-27'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://rickynilsson.github.io
+  board: false
+  contributor_type:
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Los Angeles, CA
+  email: ricky.nilsson@gmail.com
+- name: Oriol Abril-Pla
+  github_username: OriolAbril
+  github_image_id: 23738400
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2023-07-27'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: OriolAbril
+  mastodon:
+  orcidid:
+  partners:
+  website: https://oriolabrilpla.cat
+  board: false
+  contributor_type:
+    - package-guide
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - bibat
+  location: Barcelona
+  email:
+- name: Alexey Izmailov
+  github_username: alizma
+  github_image_id: 74629347
+  title:
+  sort:
+  bio: antiblob
+  organization: '{Ø,{Ø},{Ø,{Ø}}, ... }'
+  date_added: '2023-07-27'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - bibat
+  location:
+  email: alizma@brown.edu
+- name: Tessa Pierce Ward
+  github_username: bluegenes
+  github_image_id: 7740734
+  title:
+  sort:
+  bio: NSF Postdoc at UC Davis
+  organization:
+  date_added: '2023-07-27'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: saltyscientist
+  mastodon:
+  orcidid:
+  partners:
+  website: https://bluegenes.github.io
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - reviewer
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - sourmash
+  packages_reviewed:
+    - taxpasta
+  location: San Diego, CA
+  email:
+- name: Sofia Stamouli
+  github_username: sofstam
+  github_image_id: 91951607
+  title:
+  sort:
+  bio: Bioinformatician
+  organization:
+  date_added: '2023-07-27'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - taxpasta
+  packages_reviewed:
+  location: Stockholm, Sweden
+  email:
+- name: Tylar
+  github_username: 7yl4r
+  github_image_id: 1051390
+  title:
+  sort:
+  bio: USF IMaRS Software Engineer - code whisperer, data viz enthusiast,
+      scientific generalist, compulsive overengineerer, & UX PhD
+  organization: USF IMaRS
+  date_added: '2023-07-27'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: 7yl4r
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - afscgap
+  location: St. Petersburg, FL
+  email: mail@tylar.info
+- name: Ayush Anand
+  github_username: ayushanand18
+  github_image_id: 36472216
+  title:
+  sort:
+  bio: Open Source Adv, GSoC 2022 - IOOS | PyTorch, Azure, ReactJS | CS
+      Undergrad @ NIT Durgapur
+  organization:
+  date_added: '2023-07-27'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: theayushanand
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - afscgap
+  location: New Delhi, India
+  email:
+- name: Giulia Zarpellon
+  github_username: gizarp
+  github_image_id: 32750231
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2023-07-27'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - afscgap
+  packages_reviewed:
+  location:
+  email:
+- name: Jim Kitchen
+  github_username: jim22k
+  github_image_id: 2807270
+  title:
+  sort:
+  bio:
+  organization: Anaconda
+  date_added: '2023-07-27'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - python-graphblas
+  packages_reviewed:
+  location: Austin, TX
+  email:
+- name: Sultan Orazbayev
+  github_username: SultanOrazbayev
+  github_image_id: 20208402
+  title:
+  sort:
+  bio:
+  organization: '@cid-harvard'
+  date_added: '2023-07-27'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - code-contrib
+    - community
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - python-graphblas
+  packages_reviewed:
+  location: Kazakhstan
+  email: contact@econpoint.com
+- name: Isabel Zimmerman
+  github_username: isabelizimm
+  github_image_id: 54685329
+  title:
+    - Emeritus Editor in Chief
+    - Emeritus Editor
+  sort: 2
+  bio:
+  organization: '@rstudio'
+  date_added: '2023-08-14'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: true
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - community
+    - editor
+    - eic
+    - package-guide
+    - peer-review
+    - reviewer
+  packages_eic:
+    - automata
+    - harmonize-wq
+    - martini
+    - petrofit
+    - plot_phylo
+    - sunpy
+    - zodipy
+  packages_editor:
+    - blockingpy
+    - quadratik
+    - rdata
+  packages_submitted:
+  packages_reviewed:
+    - sciform
+  location: FLorida, USA
+  email:
+- name: Eliot Robson
+  github_username: eliotwrobson
+  github_image_id: 1345068
+  title:
+    - Peer Review Lead
+    - Editor
+    - Emeritus Editor in Chief
+  sort: 0
+  bio: I'm just this guy, you know?
+  organization: UIUC
+  date_added: '2023-09-11'
+  deia_advisory: false
+  editorial_board: true
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: eliotdexter
+  mastodon:
+  orcidid:
+  partners:
+  website: https://eliotwrobson.github.io/
+  board: false
+  contributor_type:
+    - editor
+    - eic
+    - maintainer
+    - peer-review
+    - reviewer
+    - submitting-author
+    - web-contrib
+  packages_eic:
+    - cheminformant
+    - pyinterpolate
+  packages_editor:
+    - cheminformant
+  packages_submitted:
+    - automata
+    - cynetdiff
+  packages_reviewed:
+    - blockingpy
+    - pooltool
+  location: Urbana, IL
+  email: erobson2@illinois.edu
+- name: Ty Schlichenmeyer
+  github_username: schlich
+  github_image_id: 21191435
+  title:
+  sort:
+  bio: Neuro & Data Engineer & Educator
+  organization:
+  date_added: '2023-09-11'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - community
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: St Louis, MO
+  email: ty.schlich@gmail.com
+- name:
+  github_username: khynder
+  github_image_id: 133049827
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2023-09-11'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - cardsort
+  location:
+  email:
+- name: Katharina Kloppenborg
+  github_username: katoss
+  github_image_id: 23122159
+  title:
+  sort:
+  bio: PhD Student in Human Computer Interaction and Participatory Health
+      Research | Data for good volunteer | M.Sc. Cognitive Science
+  organization: CRI
+  date_added: '2023-09-11'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: k_kloppenborg
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - cardsort
+  packages_reviewed:
+  location: Paris, France
+  email:
+- name: Dongdong Tian
+  github_username: seisman
+  github_image_id: 3974108
+  title:
+  sort:
+  bio: Associate Professor in Geophysics at China University of Geosciences.
+      Core developer of @GenericMappingTools.
+  organization: China University of Geosciences
+  date_added: '2023-09-11'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://seisman.info
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - pygmt
+  packages_reviewed:
+  location: Wuhan, China
+  email: seisman.info@gmail.com
+- name: Max Jones
+  github_username: maxrjones
+  github_image_id: 14077947
+  title:
+  sort:
+  bio: Data scientist | Background in oceanography and volcanology |
+      Maintaining @GenericMappingTools and building xarray extensions
+  organization: '@carbonplan'
+  date_added: '2023-09-11'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - pygmt
+  packages_reviewed:
+  location:
+  email:
+- name: Michael Grund
+  github_username: michaelgrund
+  github_image_id: 23025878
+  title:
+  sort:
+  bio: Data Scientist | Background in geophysics and seismology | Maintainer
+      of PyGMT
+  organization: SNP Innovation Lab
+  date_added: '2023-09-11'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - pygmt
+  packages_reviewed:
+  location: Germany
+  email:
+- name: Will Schlitzer
+  github_username: willschlitzer
+  github_image_id: 29518865
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2023-09-11'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - pygmt
+  packages_reviewed:
+  location: New Jersey
+  email:
+- name: Nathan Korinek
+  github_username: nkorinek
+  github_image_id: 38253680
+  title:
+  sort:
+  bio: Geography Masters student at CU Boulder studying remote sensing and
+      data analysis with EarthLab!
+  organization:
+  date_added: '2020-09-11'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - earthpy
+  packages_reviewed:
+  location: Boulder, CO
+  email: Nathan.Korinek@colorado.edu
+- name: Joe McGlinchy
+  github_username: joemcglinchy
+  github_image_id: 4762214
+  title:
+  sort:
+  bio: Remote Sensing Scientist with Hydrosat, Inc.
+  organization: '@hydrosat'
+  date_added: '2020-09-11'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - earthpy
+  packages_reviewed:
+  location: Arvada, Colorado, USA
+  email: jmcglinchy@hydrosat.com
+- name: Yvonne Fröhlich
+  github_username: yvonnefroehlich
+  github_image_id: 94163266
+  title:
+  sort:
+  bio: Research Assistant | PhD student in Seismology | Maintainer of PyGMT
+  organization: Karlsruhe Institute of Technology - Geophysical Institute
+  date_added: '2023-09-15'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - pygmt
+  packages_reviewed:
+  location: Karlsruhe (Germany)
+  email:
+- name: Éric
+  github_username: merwok
+  github_image_id: 635179
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2023-10-22'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Beryl Kanali
+  github_username: BerylKanali
+  github_image_id: 50364045
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2023-10-22'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - astartes
+  location:
+  email:
+- name: Du Phan
+  github_username: du-phan
+  github_image_id: 10564525
+  title:
+  sort:
+  bio: Research Scientist @dataiku-research
+  organization: '@dataiku'
+  date_added: '2023-10-22'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - astartes
+  location: Paris, France
+  email:
+- name: Jackson Burns
+  github_username: JacksonBurns
+  github_image_id: 33505528
+  title:
+  sort:
+  bio: Chemical Engineering and Computation Researcher @ MIT
+  organization:
+  date_added: '2023-10-22'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: WowThatBurns
+  mastodon:
+  orcidid:
+  partners:
+  website: https://jacksonwarnerburns.com
+  board: false
+  contributor_type:
+    - maintainer
+    - package-guide
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - astartes
+  packages_reviewed:
+  location: MIT
+  email:
+- name: Kevin Spiekermann
+  github_username: kspieks
+  github_image_id: 31116084
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2023-10-22'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - astartes
+  packages_reviewed:
+  location:
+  email:
+- name: Himaghna Bhattacharjee
+  github_username: himaghna
+  github_image_id: 35175139
+  title:
+  sort:
+  bio:
+  organization: University of Delaware
+  date_added: '2023-10-22'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - astartes
+  packages_reviewed:
+  location: San Francisco, USA
+  email:
+- name: Marta Leszczyńska
+  github_username: Reckony
+  github_image_id: 38528736
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2023-10-22'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - xgi
+  location:
+  email: marta.monika.leszczynska@intel.com
+- name: Nicholas Landry
+  github_username: nwlandry
+  github_image_id: 8760347
+  title:
+  sort:
+  bio:
+  organization: University of Vermont
+  date_added: '2023-10-22'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: nwlandry
+  mastodon:
+  orcidid:
+  partners:
+  website: https://nwlandry.com
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - xgi
+  packages_reviewed:
+  location: Burlington, VT
+  email:
+- name: Leo Torres
+  github_username: leotrs
+  github_image_id: 1096704
+  title:
+  sort:
+  bio: Postdoc at MPI for Mathematics in the Sciences
+  organization: leotrs.com
+  date_added: '2023-10-22'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - xgi
+  packages_reviewed:
+  location: Leipzig, Lima, Boston
+  email: leo@leotrs.com
+- name: Maxime Lucas
+  github_username: maximelucas
+  github_image_id: 7493360
+  title:
+  sort:
+  bio:
+  organization: CENTAI Institute
+  date_added: '2023-10-22'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://maximelucas.github.io
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - xgi
+  packages_reviewed:
+  location: Turin, Italy
+  email:
+- name: Iacopo Iacopini
+  github_username: iaciac
+  github_image_id: 16819231
+  title:
+  sort:
+  bio: Complex Networks · Data Science · Computational Social Science · Cities
+  organization: Network Science Institute, Northeastern University London
+  date_added: '2023-10-22'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: iacopoiacopini
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - xgi
+  packages_reviewed:
+  location: London
+  email: iacopiniiacopo@gmail.com
+- name: Giovanni Petri
+  github_username: lordgrilo
+  github_image_id: 2098905
+  title:
+  sort:
+  bio:
+  organization: Northeastern University London / CENTAI Institute
+  date_added: '2023-10-22'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: lordgrilo
+  mastodon:
+  orcidid:
+  partners:
+  website: https://lordgrilo.github.io
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - xgi
+  packages_reviewed:
+  location: London/Turin
+  email: giovanni.petri@nulondon.ac.uk
+- name: Alice Schwarze
+  github_username: acuschwarze
+  github_image_id: 11501103
+  title:
+  sort:
+  bio: PhD in applied maths
+  organization: Dartmouth College
+  date_added: '2023-10-22'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://aliceschwarze.gitlab.io/
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - xgi
+  packages_reviewed:
+  location: Hanover, NH
+  email:
+- name: Thomas Robiglio
+  github_username: thomasrobiglio
+  github_image_id: 83019028
+  title:
+  sort:
+  bio:
+  organization: Politecnico di Torino
+  date_added: '2023-10-22'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: thomrobiglio
+  mastodon:
+  orcidid:
+  partners:
+  website: https://thomasrobiglio.github.io
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - xgi
+  packages_reviewed:
+  location: Torino, Italy
+  email:
+- name: Alice Patania
+  github_username: alpatania
+  github_image_id: 4749196
+  title:
+  sort:
+  bio: Computational topologist, spreading the TDA verb to Neuroscience.
+  organization: University of Vermont
+  date_added: '2023-10-22'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: AlicePatania
+  mastodon:
+  orcidid:
+  partners:
+  website: https://alpatania.github.io
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - xgi
+  packages_reviewed:
+  location:
+  email: apatania@uvm.edu
+- name: Joseph H Kennedy
+  github_username: jhkennedy
+  github_image_id: 7882693
+  title:
+  sort:
+  bio: I'm a Research Software Engineer, Computational Glaciologist, Climate
+      Scientist, and Adventurer living/playing in Alaska
+  organization: Alaska Satellite Facility
+  date_added: '2023-12-14'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://jhkennedy.org
+  board: false
+  contributor_type:
+    - package-guide
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - eomaps
+  location: Fairbanks, AK
+  email:
+- name: William F. Broderick
+  github_username: billbrod
+  github_image_id: 6338509
+  title:
+  sort:
+  bio: Associate data scientist at Flatiron Institute, working to make
+      computational neuroscience more open, cumulative, and reproducible.
+  organization: Flatiron Institute
+  date_added: '2023-12-14'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://orcid.org/0000-0002-8999-9003
+  board: false
+  contributor_type:
+    - maintainer
+    - package-guide
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - plenoptic
+  packages_reviewed:
+  location: New York, NY
+  email: billbrod@gmail.com
+- name: Gregor Sturm
+  github_username: grst
+  github_image_id: 7051479
+  title:
+  sort:
+  bio: Clinical Bioinformatics @Boehringer-Ingelheim.@scverse core dev.
+      Formerly PhD student @icbi-lab.My private account.
+  organization: Boehringer Ingelheim
+  date_added: '2023-12-14'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://grst.github.io
+  board: false
+  contributor_type:
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Biberach, DE
+  email: mail@gregor-sturm.de
+- name: Sean Kelly
+  github_username: nutjob4life
+  github_image_id: 814813
+  title:
+  sort:
+  bio: An agoraphobic gourmand, Python hacker, Plone committer, Apache
+      Software Foundation member, NASA scientist, gastrophysicist, etc.
+  organization: Sean Kelly Consulting
+  date_added: '2023-12-14'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: nutjob4life
+  mastodon:
+  orcidid:
+  partners:
+  website: https://about.me/sean.c.kelly
+  board: false
+  contributor_type:
+    - peer-review
+    - peer-review-guide
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - sunpy
+  location:
+  email: kelly@seankelly.biz
+- name: Andrew Nesbitt
+  github_username: andrew
+  github_image_id: 1060
+  title:
+  sort:
+  bio: Software engineer and researcher
+  organization: '@ecosyste-ms and @octobox'
+  date_added: '2023-12-14'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: teabass
+  mastodon:
+  orcidid:
+  partners:
+  website: https://nesbitt.io
+  board: false
+  contributor_type:
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: UK
+  email:
+- name: Lukas Heumos
+  github_username: Zethson
+  github_image_id: 21954664
+  title:
+  sort:
+  bio: PhD student at @theislab and @schillerlab. Co-founder @scverse.
+      Research software engineer @laminlabs
+  organization: '@theislab @schillerlab @scverse @laminlabs'
+  date_added: '2023-12-14'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: lukasheumos
+  mastodon:
+  orcidid:
+  partners:
+  website: https://lukasheumos.com
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - biocypher
+  location: Germany
+  email: lukas.heumos@posteo.net
+- name: Sebastian Lobentanzer
+  github_username: slobentanzer
+  github_image_id: 13223629
+  title:
+  sort: 2
+  bio:
+  organization:
+  date_added: '2023-12-14'
+  deia_advisory: false
+  editorial_board: true
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: slobentanzer
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - community
+    - maintainer
+    - open-education
+    - peer-review
+    - submitting-author
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - biocypher
+  packages_reviewed:
+  location:
+  email:
+- name: Maria Knorps
+  github_username: mknorps
+  github_image_id: 27200848
+  title:
+  sort:
+  bio: Programming mathematician
+  organization: Tweag
+  date_added: '2023-12-15'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Toruń/Gdynia, Poland
+  email: maria.knorps@gmail.com
+- name: Lauren Yee
+  github_username: yeelauren
+  github_image_id: 12127746
+  title:
+    - Editor
+    - Editor in Chief
+  sort: 1
+  bio:
+  organization:
+  date_added: '2023-12-21'
+  deia_advisory: false
+  editorial_board: true
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - editor
+    - eic
+    - peer-review
+    - reviewer
+  packages_eic:
+    - astropy
+  packages_editor:
+    - tda-mapper
+  packages_submitted:
+  packages_reviewed:
+    - eomaps
+  location:
+  email:
+- name: Bane Sullivan
+  github_username: banesullivan
+  github_image_id: 22067021
+  title: Editor
+  sort: 2
+  bio:
+  organization:
+  date_added: '2023-12-27'
+  deia_advisory: false
+  editorial_board: true
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - code-contrib
+    - editor
+    - peer-review
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+    - eomaps
+    - pyinterpolate
+    - thztools
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Philipp A.
+  github_username: flying-sheep
+  github_image_id: 291575
+  title:
+  sort:
+  bio:
+  organization: '@theislab'
+  date_added: '2023-12-27'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: München
+  email: flying-sheep@web.de
+- name: Septaris/Babouh
+  github_username: Septaris
+  github_image_id: 8026975
+  title:
+  sort:
+  bio:
+  organization: Observatoire de Paris
+  date_added: '2024-01-30'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - sunpy
+  location: Meudon
+  email:
+- name: Nabil Freij
+  github_username: nabobalis
+  github_image_id: 1392107
+  title:
+  sort:
+  bio: Research Software Engineer
+  organization: BAERI/LMSAL (@LM-SAL)
+  date_added: '2024-01-30'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - sunpy
+  packages_reviewed:
+  location: Palo Alto, CA, USA
+  email: nabil.freij@gmail.com
+- name: Steven Christe
+  github_username: ehsteve
+  github_image_id: 739053
+  title:
+  sort:
+  bio: Research Astrophysicist at the NASA Goddard Space Flight Center.
+  organization: NASA Goddard Space Flight Center
+  date_added: '2024-01-30'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://orcid.org/0000-0001-6127-795X
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - sunpy
+  packages_reviewed:
+  location: Washington, DC
+  email:
+- name: David Pérez-Suárez
+  github_username: dpshelio
+  github_image_id: 963242
+  title:
+  sort:
+  bio: Astrophysicist lent towards the day side of it.Happy to be the
+      happiness of the the garden
+  organization: '@UCL-ARC'
+  date_added: '2024-01-30'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://dpshelio.github.io
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - sunpy
+  packages_reviewed:
+  location: London
+  email:
+- name: Jack Ireland
+  github_username: wafels
+  github_image_id: 983575
+  title:
+  sort:
+  bio: Research Astrophysicist
+  organization:
+  date_added: '2024-01-30'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - sunpy
+  packages_reviewed:
+  location:
+  email:
+- name: Albert Y. Shih
+  github_username: ayshih
+  github_image_id: 991759
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2024-01-30'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - sunpy
+  packages_reviewed:
+  location:
+  email:
+- name: Stuart Mumford
+  github_username: Cadair
+  github_image_id: 1391051
+  title:
+  sort:
+  bio: I write open source software for solar and astro physics. I am the
+      lead-developer of SunPy, contribute to Astropy, and work on DKIST.
+  organization: Aperio Software
+  date_added: '2024-01-30'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - sunpy
+  packages_reviewed:
+  location: Holmfirth
+  email: stuart@cadair.com
+- name: DanRyanIrish
+  github_username: DanRyanIrish
+  github_image_id: 6806704
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2024-01-30'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - sunpy
+  packages_reviewed:
+  location:
+  email: ryand5@tcd.ie
+- name: Will Barnes
+  github_username: wtbarnes
+  github_image_id: 8676141
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2024-01-30'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: wtbarnes_
+  mastodon:
+  orcidid:
+  partners:
+  website: https://wtbarnes.github.io/
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - sunpy
+  packages_reviewed:
+  location: Washington, D.C.
+  email: will.t.barnes@gmail.com
+- name: Conor MacBride
+  github_username: ConorMacBride
+  github_image_id: 25007832
+  title:
+  sort:
+  bio: Data Scientist · Astrophysics PhD
+  organization:
+  date_added: '2024-01-30'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://macbride.me
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - sunpy
+  packages_reviewed:
+  location: Derry, Northern Ireland
+  email: conor@macbride.me
+- name: Alasdair Wilson
+  github_username: alasdairwilson
+  github_image_id: 60351846
+  title:
+  sort:
+  bio:
+  organization: University of Oxford
+  date_added: '2024-01-30'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - sunpy
+  packages_reviewed:
+  location:
+  email:
+- name: Laura Hayes
+  github_username: hayesla
+  github_image_id: 4620298
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2024-01-30'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: Laura_hayess
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - sunpy
+  packages_reviewed:
+  location: Leiden, Netherlands
+  email: hayesla@tcd.ie
+- name: Vishnunarayan K I
+  github_username: vn-ki
+  github_image_id: 31964688
+  title:
+  sort:
+  bio: Just another curious guy.
+  organization: IIT Indore
+  date_added: '2024-01-30'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - sunpy
+  packages_reviewed:
+  location: Kerala, India
+  email:
+- name: Michael Tso
+  github_username: cmtso
+  github_image_id: 37928699
+  title:
+  sort:
+  bio: environmental data scientist
+  organization: '@NERC-CEH'
+  date_added: '2024-02-15'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: michael_ts0
+  mastodon:
+  orcidid:
+  partners:
+  website: https://cmtso.github.io
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - ncompare
+  location:
+  email:
+- name: Daniel Kaufman
+  github_username: danielfromearth
+  github_image_id: 114174502
+  title:
+  sort:
+  bio:
+  organization: NASA's Atmospheric Science Data Center
+  date_added: '2024-02-15'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - ncompare
+  packages_reviewed:
+  location:
+  email:
+- name: Michael Chow
+  github_username: machow
+  github_image_id: 2574498
+  title:
+  sort:
+  bio: Learning, Memory, Computation
+  organization: '@rstudio'
+  date_added: '2024-02-15'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: chowthedog
+  mastodon:
+  orcidid:
+  partners:
+  website: https://mchow.com
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - great tables
+  packages_reviewed:
+    - sciform
+  location:
+  email: chowmichedu@gmail.com
+- name: Justin Gerber
+  github_username: jagerber48
+  github_image_id: 48464524
+  title:
+  sort:
+  bio: Atomic Physicist
+  organization: Quantinuum
+  date_added: '2024-02-15'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - sciform
+  packages_reviewed:
+  location:
+  email: justin.gerber48@gmail.com
+- name:
+  github_username: jaimergp
+  github_image_id: 2559438
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2024-02-25'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name:
+  github_username: h-vetinari
+  github_image_id: 33685575
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2024-02-25'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email: h.vetinari@gmx.com
+- name: Richard Iannone
+  github_username: rich-iannone
+  github_image_id: 5612024
+  title:
+  sort:
+  bio: I enjoy creating useful things for data analysis, transformation, and
+      visualization. It's super fun too! ₍⸍⸌̣ʷ̣̫⸍̣⸌₎
+  organization: '@rstudio'
+  date_added: '2024-03-09'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: riannone
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - reviewer
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - great tables
+  packages_reviewed:
+    - rdata
+  location: Toronto, Canada
+  email: rich@posit.co
+- name: Hassan Kibirige
+  github_username: has2k1
+  github_image_id: 780341
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2024-03-09'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: HKibirige
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - rdata
+  location: Kampala, Uganda
+  email: has2k1@gmail.com
+- name: Carlos Ramos Carreño
+  github_username: vnmabus
+  github_image_id: 2364173
+  title:
+  sort:
+  bio: Software engineer and mathematician
+  organization:
+  date_added: '2024-11-22'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - rdata
+  packages_reviewed:
+  location: Frankfurt, Germany
+  email: carlosramosca@hotmail.com
+- name: Derek Homeier
+  github_username: dhomeier
+  github_image_id: 709020
+  title:
+    - Editor
+  sort: 2
+  bio:
+  organization:
+  date_added:
+  deia_advisory: false
+  editorial_board: true
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+    - Astropy
+  website:
+  board: false
+  contributor_type:
+    - editor
+    - peer-review
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+    - petrofit
+    - zodipy
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Sviatoslav Sydorenko (Святослав Сидоренко)
+  github_username: webknjaz
+  github_image_id: 578543
+  title:
+  sort:
+  bio: '🇺🇦 #StandWithUkraine* traveler* oversees @aio-libs CI* maintains @CherryPy*
+      made Octomachinery & alls-green, pypi-publish & checkout-python-sdist GHAs'
+  organization: '@Ansible Core Engineering Team @ @RedHatOfficial'
+  date_added: '2024-03-20'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: webknjaz
+  mastodon:
+  orcidid:
+  partners:
+  website: https://webknjaz.me
+  board: false
+  contributor_type:
+    - community
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Mikulov, CZ ↜ Brno, CZ ↜ Brovary/Kyiv, UA
+  email: webknjaz+github/profile@redhat.com
+- name: Raphael Quast
+  github_username: raphaelquast
+  github_image_id: 22773387
+  title:
+  sort:
+  bio:
+  organization: TU Wien
+  date_added: '2024-03-20'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - eomaps
+  packages_reviewed:
+  location:
+  email:
+- name: Cale Kochenour
+  github_username: calekochenour
+  github_image_id: 54423680
+  title:
+  sort:
+  bio: Remote sensing analyst.
+  organization:
+  date_added: '2024-05-07'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Colorado, United States
+  email: calekochenour@gmail.com
+- name: Miguel Alizo
+  github_username: miguelalizo
+  github_image_id: 108839050
+  title:
+  sort:
+  bio: Software Developer with a background in Mechanical and Aerospace
+      engineering 🚀 ✈️ -Rustacean 🦀 and Pythonista 🐍
+  organization:
+  date_added: '2024-05-07'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Seattle, WA
+  email:
+- name:
+  github_username: nyeshlur
+  github_image_id: 72169901
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2024-05-07'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Tyler Bonnell
+  github_username: Tyler-Bonnell
+  github_image_id: 89505514
+  title:
+  sort:
+  bio: Public health epidemiologist interested in injury and violence
+      prevention and data science tool development.
+  organization: Washington Start Department of Health
+  date_added: '2024-05-07'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Seattle, WA
+  email:
+- name: Pat Tressel
+  github_username: ptressel
+  github_image_id: 618916
+  title:
+  sort:
+  bio:
+  organization: Elcano Project @elcano
+  date_added: '2024-05-07'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Seattle, WA, USA
+  email: ptressel@myuw.net
+- name: Tobias Megies
+  github_username: megies
+  github_image_id: 1842780
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2024-05-07'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Leo Singer
+  github_username: lpsinger
+  github_image_id: 728407
+  title:
+  sort:
+  bio:
+  organization: NASA Goddard Space Flight Center
+  date_added: '2024-05-07'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: GravityAndBikes
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - greopy
+    - zodipy
+  location: Greenbelt, MD
+  email: leo.singer@ligo.org
+- name: Metin San
+  github_username: MetinSa
+  github_image_id: 28634670
+  title:
+  sort:
+  bio: PhD Research Fellow in Cosmology at the University of Oslo.
+  organization: Institute of Theoretical Astrophysics (UiO)
+  date_added: '2024-05-07'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - zodipy
+  packages_reviewed:
+  location: Oslo, Norway
+  email: metin.san@astro.uio.no
+- name: Duncan Watts
+  github_username: dncnwtts
+  github_image_id: 6478137
+  title:
+  sort:
+  bio:
+  organization: University of Oslo
+  date_added: '2024-05-07'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: dncnwtts
+  mastodon:
+  orcidid:
+  partners:
+  website: https://dncnwtts.github.io
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - zodipy
+  packages_reviewed:
+  location: Oslo
+  email: duncanjosephwatts@gmail.com
+- name: Daniel Herman
+  github_username: hermda02
+  github_image_id: 17911822
+  title:
+  sort:
+  bio: Data Scientist at chronos.ai -- PhD in Cosmology
+  organization:
+  date_added: '2024-05-07'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - zodipy
+  packages_reviewed:
+  location: Oslo, Norway
+  email:
+- name: Paige Martin
+  github_username: paigem
+  github_image_id: 26591824
+  title:
+  sort:
+  bio: Open Science Expert, Climate Data Scientist, Science Capacity Sharing
+      Enthusiast
+  organization: NASA Transform to Open Science
+  date_added: '2024-05-07'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: SciencePaige
+  mastodon:
+  orcidid:
+  partners:
+  website: https://paigem.github.io
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - xnemogcm
+  location: Canberra, Australia
+  email:
+- name: Callum Rollo
+  github_username: callumrollo
+  github_image_id: 28703282
+  title:
+  sort:
+  bio: Oceanographer, Pythonista and data science-ish. Breaks things on
+      Fridays
+  organization: Voice of the Ocean Foundation
+  date_added: '2024-05-07'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://callumrollo.github.io/
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - xnemogcm
+  location: Gothenburg, Sweden
+  email: c.rollo@outlook.com
+- name: Romain Caneill
+  github_username: rcaneill
+  github_image_id: 18579092
+  title:
+  sort:
+  bio: Doctor in Physical Oceanography. Studying sea ice, ocean stratif,
+      buoyancy fluxes, nonlinear EOS, with numerical modelling (NextSIM, NEMO)
+      and observations.
+  organization: Institut des Géosciences de l'Environnement
+  date_added: '2024-05-07'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://romaincaneill.fr
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - reviewer
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - xnemogcm
+  packages_reviewed:
+    - harmonize-wq
+  location: Grenoble, France
+  email: romain.caneill@ens-lyon.org
+- name: Lili Andersson-Li
+  github_username: LilyAnderssonLee
+  github_image_id: 64467552
+  title:
+  sort:
+  bio: Bioinformatician,Dept of Microbiology, Tumor and Cell Biology
+  organization: Karolinska Institutet
+  date_added: '2024-05-07'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - sourmash
+  location: Sweden
+  email:
+- name: Elais Player
+  github_username: elais
+  github_image_id: 2111879
+  title:
+  sort:
+  bio: Pfft.
+  organization: Lawrence Berkeley National Laboratory
+  date_added: '2024-05-07'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - sourmash
+  location: Oakland, California
+  email:
+- name: Ken Seehart
+  github_username: kenseehart
+  github_image_id: 612119
+  title:
+  sort:
+  bio:
+  organization: Game of Y
+  date_added: '2024-06-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Ryan
+  github_username: ryanskeith
+  github_image_id: 657220
+  title:
+  sort:
+  bio: A guy that likes python and anything automation, dsp or data-science.
+  organization: Anaconda, Inc.
+  date_added: '2024-06-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: USA
+  email:
+- name: Patrick Byers
+  github_username: pb-413
+  github_image_id: 36516871
+  title:
+  sort:
+  bio:
+  organization: Lucas Systems
+  date_added: '2024-06-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: pb_413
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Pittsburgh PA
+  email:
+- name: Megan Sosey
+  github_username: sosey
+  github_image_id: 503615
+  title:
+  sort:
+  bio: Scientist, Developer, space enthusiast
+  organization: Space Telescope Science Institute
+  date_added: '2024-06-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: OmegaSpaces
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Baltimore, MD
+  email: sosey@stsci.edu
+- name: Brianne Wilhelmi
+  github_username: BSuperbad
+  github_image_id: 100496041
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2024-06-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Cheng H. Lee
+  github_username: chenghlee
+  github_image_id: 3485949
+  title:
+  sort:
+  bio:
+  organization: Anaconda
+  date_added: '2024-06-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Austin, TX
+  email:
+- name:
+  github_username: Vaunty
+  github_image_id: 68826427
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2024-06-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Felipe Moreno
+  github_username: flpm
+  github_image_id: 17676929
+  title:
+  sort:
+  bio: Security + Python + Design
+  organization: Bloomberg LP
+  date_added: '2024-06-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - community
+    - package-guide
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: New York, NY
+  email:
+- name: Sneha Yadav
+  github_username: sn3hay
+  github_image_id: 156010030
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2024-06-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Emily Zhang
+  github_username: BradonZhang
+  github_image_id: 10603251
+  title:
+  sort:
+  bio: Hello, I make things sometimes.
+  organization:
+  date_added: '2024-06-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: New York
+  email: bradonzhang@gmail.com
+- name: Filipe Laíns
+  github_username: FFY00
+  github_image_id: 11718923
+  title:
+  sort:
+  bio: electro-metrology, semiconductor manufacturing, and nuclear physics
+      enthusiast • python core dev, archlinux packager
+  organization:
+  date_added: '2024-06-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: MissingClara
+  mastodon:
+  orcidid:
+  partners:
+  website: https://ffy00.github.io/
+  board: false
+  contributor_type:
+    - peer-review-guide
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Portugal
+  email: lains@riseup.net
+- name: Steven Silvester
+  github_username: blink1073
+  github_image_id: 2096628
+  title:
+  sort:
+  bio:
+  organization: MongoDB
+  date_added: '2024-06-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - community
+    - package-guide
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Shannon
+  github_username: magsol
+  github_image_id: 135417
+  title:
+  sort:
+  bio:
+  organization: University of Georgia
+  date_added: '2024-06-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://magsol.github.io/
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - sleplet
+  location: Athens, GA
+  email: magsol@gmail.com
+- name: Jakub Tomasz Gnyp
+  github_username: gnypit
+  github_image_id: 62402006
+  title:
+  sort:
+  bio:
+  organization: University of Gdańsk
+  date_added: '2024-06-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - sleplet
+  location: Gdańsk
+  email:
+- name: Patrick J. Roddy
+  github_username: paddyroddy
+  github_image_id: 15052188
+  title:
+  sort:
+  bio: Research Software Developer at UCL
+  organization: '@UCL'
+  date_added: '2024-06-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://paddyroddy.github.io
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - sleplet
+  packages_reviewed:
+  location: London
+  email: patrickjamesroddy@gmail.com
+- name: Zack Weinberg
+  github_username: zackw
+  github_image_id: 325899
+  title:
+  sort:
+  bio: I AM NOT LOOKING FOR A JOB. DO NOT CONTACT ME WITH  JOB OFFERS. I do
+      security research and misc systems coding. Please see my personal
+      website for more detail.
+  organization:
+  date_added: '2024-07-04'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Pittsburgh, PA
+  email:
+- name: Stefano Rivera
+  github_username: stefanor
+  github_image_id: 442117
+  title:
+  sort:
+  bio: 'Linux engineer: doing dev-ops, full-stack work, and some management. Looks
+      after some Python things in DebianI am COS positive (Conference Organizer
+      Syndrome'
+  organization: Freexian, Debian, Ubuntu
+  date_added: '2024-07-04'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: stefanorivera
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: The Internet
+  email: stefanor@debian.org
+- name: Stefanie Molin
+  github_username: stefmolin
+  github_image_id: 24376333
+  title:
+  sort:
+  bio: Software Engineer | Speaker | Author of "Hands-On Data Analysis with
+      Pandas"
+  organization: '@Bloomberg'
+  date_added: '2024-07-04'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: StefanieMolin
+  mastodon:
+  orcidid:
+  partners:
+  website: https://stefaniemolin.com
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Ananthu C V
+  github_username: WeepingClown13
+  github_image_id: 95921427
+  title:
+  sort:
+  bio: Debian Maintainer. Lives in terminal.
+  organization:
+  date_added: '2024-07-04'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email: ananthucv5@gmail.com
+- name: Gabriel Stefanini Vicente
+  github_username: g4brielvs
+  github_image_id: 4053416
+  title:
+  sort:
+  bio: The true delight is in the finding out rather than in the knowing
+  organization: '@worldbank'
+  date_added: '2024-07-04'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://g4brielvs.me
+  board: false
+  contributor_type:
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email: gvicente@worldbank.org
+- name: Tom Aldcroft
+  github_username: taldcroft
+  github_image_id: 348089
+  title:
+  sort:
+  bio:
+  organization: Center for Astrophysics | Harvard & Smithsonian
+  date_added: '2024-07-04'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - martini
+    - stingray
+  location: Cambridge, MA
+  email: taldcroft@gmail.com
+- name: Michele Delli Veneri
+  github_username: MicheleDelliVeneri
+  github_image_id: 46787099
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2024-07-04'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - martini
+  location:
+  email:
+- name: Kyle Oman
+  github_username: kyleaoman
+  github_image_id: 32932511
+  title:
+  sort:
+  bio: Assistant Professor and Royal Society Dorothy Hodgkin Fellow at the
+      Institute for Computational Cosmology, Durham University.
+  organization:
+  date_added: '2024-07-04'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://kyleaoman.github.io
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - reviewer
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - martini
+    - swiftgalaxy
+  packages_reviewed:
+    - petrofit
+  location:
+  email: kyle.a.oman@durham.ac.uk
+- name: Phil Dong
+  github_username: phildong
+  github_image_id: 35715936
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2024-07-04'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - automata
+  location:
+  email:
+- name: Iris Young
+  github_username: irisdyoung
+  github_image_id: 14185571
+  title:
+  sort:
+  bio: Structural biology methods developer and scientific software developer
+  organization: Lawrence Berkeley National Laboratory
+  date_added: '2024-07-04'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://irisdyoung.github.io/
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - automata
+  location: San Francisco, CA
+  email: irisdyoung@gmail.com
+- name: Nima Sarajpoor
+  github_username: NimaSarajpoor
+  github_image_id: 38519522
+  title:
+    - Emeritus Editor
+  sort: 2
+  bio: Data Scientist  | OSS Contributor  | Philomath
+  organization:
+  date_added: '2024-07-04'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: true
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://nimasarajpoor.github.io/blog/
+  board: false
+  contributor_type:
+    - editor
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+    - ams
+  packages_submitted:
+  packages_reviewed:
+    - automata
+  location:
+  email: nimasarajpoor@gmail.com
+- name: Caleb Evans
+  github_username: caleb531
+  github_image_id: 872474
+  title:
+  sort:
+  bio: Hi, I'm Caleb, a web developer who lives for Christ by building
+      enjoyable apps and useful tools. I hope you are blessed by what I've
+      made!
+  organization:
+  date_added: '2024-07-04'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: caleb531
+  mastodon:
+  orcidid:
+  partners:
+  website: https://calebevans.me/
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - automata
+  packages_reviewed:
+  location: Carlsbad, CA
+  email: caleb@calebevans.me
+- name:
+  github_username: Sinna
+  github_image_id: 2612667
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2024-07-04'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - biocypher
+  location:
+  email:
+- name:
+  github_username: SeanAverS
+  github_image_id: 110581427
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2024-07-15'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Canada
+  email:
+- name: Han
+  github_username: ayhanxian
+  github_image_id: 20816603
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2024-07-15'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - community
+    - package-guide
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Roberto Pastor Muela
+  github_username: RobPasMue
+  github_image_id: 37798125
+  title:
+  sort:
+  bio: Aerospace engineer, passionate about simulations, CFD and
+      astrodynamics.
+  organization: '@ansys'
+  date_added: '2024-08-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://robpasmue.github.io
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Leganés, Madrid
+  email:
+- name: Olek
+  github_username: yardasol
+  github_image_id: 45364492
+  title:
+  sort:
+  bio: PhD student @ ARFC.Working on literature review for PhD Thesis, but am
+      always open for PR reviews!
+  organization:
+  date_added: '2024-08-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name:
+  github_username: hpodzorski-USGS
+  github_image_id: 159824971
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2024-08-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Naty Clementi
+  github_username: ncclementi
+  github_image_id: 7526622
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2024-08-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: ncclementi
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Arlington, VA
+  email:
+- name: John Drake
+  github_username: John-Drake
+  github_image_id: 22374979
+  title:
+  sort:
+  bio: Bioinformatician
+  organization:
+  date_added: '2024-08-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Phoenix, AZ
+  email:
+- name: Revathy Venugopal
+  github_username: Revathyvenugopal162
+  github_image_id: 104772255
+  title:
+  sort:
+  bio:
+  organization: ANSYS
+  date_added: '2024-08-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - community
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Lyon, France
+  email:
+- name: Elise Hinman
+  github_username: ehinman
+  github_image_id: 121896266
+  title:
+  sort:
+  bio: Data Scientist
+  organization: USGS
+  date_added: '2024-08-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - code-contrib
+    - community
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Madison, WI
+  email:
+- name: Tetsuo Koyama
+  github_username: tkoyama010
+  github_image_id: 7513610
+  title:
+  sort: 2
+  bio: '3D visualization library @pyvista maintainer & translator,@scipy-conference
+      chairperson,Photo by: @peacock0803sz CC-BY 2.0'
+  organization: '@ark-info-sys'
+  date_added: '2024-08-15'
+  deia_advisory: false
+  editorial_board: true
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: tkoyama010
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - community
+    - editor
+    - package-guide
+    - peer-review
+    - web-contrib
+  packages_eic:
+  packages_editor:
+    - felupe
+  packages_submitted:
+  packages_reviewed:
+  location: Japan
+  email: tkoyama010@gmail.com
+- name: Kozo Nishida
+  github_username: kozo2
+  github_image_id: 12192
+  title:
+  sort:
+  bio: PyData Osaka organizer,Bioconductor Community Advisory Board,Software
+      Carpentry Japanese Team
+  organization:
+  date_added: '2024-08-15'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: kozo2
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Tokyo, Japan
+  email:
+- name: Jacqui Levy
+  github_username: Jacqui-123
+  github_image_id: 110696550
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2024-08-15'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - harmonize-wq
+  location:
+  email:
+- name: Justin Bousquin
+  github_username: jbousquin
+  github_image_id: 6400726
+  title:
+  sort:
+  bio: People | Water | Where
+  organization: U.S. Environmental Protection Agency
+  date_added: '2024-08-15'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - harmonize-wq
+  packages_reviewed:
+  location: Gulf Breeze, FL
+  email: bousquin.justin@epa.gov
+- name: Melissa Weber Mendonça
+  github_username: melissawm
+  github_image_id: 3949932
+  title:
+  sort:
+  bio: Senior DevEx Engineer at Quansight, former math professor (UFSC).
+      Mathematical optimization, numerical linear algebra, LaTeX, Python,
+      Fortran, OSS.
+  organization: '@Quansight'
+  date_added: '2024-09-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://melissawm.github.io
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Florianópolis, Brazil
+  email: melissawm@gmail.com
+- name: Russ Biggs
+  github_username: russbiggs
+  github_image_id: 8487728
+  title:
+  sort:
+  bio:
+  organization:
+  date_added:
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: true
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Kelly L. Rowland
+  github_username: kellyrowland
+  github_image_id: 5440574
+  title:
+  sort: 2
+  bio:
+  organization:
+  date_added:
+  deia_advisory: false
+  editorial_board: true
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - editor
+    - peer-review
+  packages_eic:
+  packages_editor:
+    - montepy
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Silvana Ovaitt
+  github_username: shirubana
+  github_image_id: 22824806
+  title:
+  sort: 2
+  bio:
+  organization:
+  date_added:
+  deia_advisory: false
+  editorial_board: true
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - editor
+    - peer-review
+  packages_eic:
+  packages_editor:
+    - solar data tools
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Sebastiano Tronto
+  github_username: sebastianotronto
+  github_image_id: 14557809
+  title:
+  sort: 2
+  bio:
+  organization:
+  date_added: '2024-09-17'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://sebastiano.tronto.net
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - pooltool
+  location:
+  email: sebastiano@tronto.net
+- name: Evan Kiefl
+  github_username: ekiefl
+  github_image_id: 8688665
+  title:
+  sort:
+  bio: Software Engineer / Biologist / Billiards addict. I did my PhD in
+      Biophysical Sciences at the University of Chicago.
+  organization:
+  date_added: '2024-09-17'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: evankiefl
+  mastodon:
+  orcidid:
+  partners:
+  website: https://ekiefl.github.io
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - pooltool
+  packages_reviewed:
+  location:
+  email:
+- name: Jon Kiparsky
+  github_username: jonkiparsky
+  github_image_id: 5283553
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2024-10-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email: jon.kiparsky@gmail.com
+- name: Matteo Bachetti
+  github_username: matteobachetti
+  github_image_id: 7190189
+  title:
+  sort:
+  bio: Astrophysicist at INAF, time series cruncher@StingraySoftware @NuSTAR
+      @astropy @discos
+  organization: INAF/Osservatorio Astronomico di Cagliari
+  date_added: '2024-10-15'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - stingray
+  packages_reviewed:
+  location: Selargius (CA), Italy
+  email:
+- name: Daniela Huppenkothen
+  github_username: dhuppenkothen
+  github_image_id: 5237391
+  title:
+  sort:
+  bio:
+  organization: SRON Netherlands Institute for Space Research
+  date_added: '2024-10-15'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - stingray
+  packages_reviewed:
+  location: Utrecht, Netherlands
+  email:
+- name: Mason Ng
+  github_username: masonng-astro
+  github_image_id: 46072835
+  title:
+  sort:
+  bio: "['23-'24] 6th year PhD candidate in the MIT Department of Physics (+MIT
+      Kavli Institute for Astrophysics and Space Research)"
+  organization: Massachusetts Institute of Technology
+  date_added: '2024-11-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: NZMason
+  mastodon:
+  orcidid:
+  partners:
+  website: https://mason-ng.com
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - stingray
+  location: Cambridge, MA
+  email:
+- name: Frank Male
+  github_username: frank1010111
+  github_image_id: 4694479
+  title:
+  sort:
+  bio: Full stack scientific programmer - from raw data to decisions
+  organization: Penn State University
+  date_added: '2024-12-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - thztools
+  location: State College, PA
+  email:
+- name:
+  github_username: Romain-Peretti
+  github_image_id: 184390495
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2024-12-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - thztools
+  location:
+  email:
+- name: J. Steven Dodge
+  github_username: jsdodge
+  github_image_id: 4602669
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2024-12-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - community
+    - maintainer
+    - open-education
+    - package-guide
+    - peer-review
+    - reviewer
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - thztools
+  packages_reviewed:
+    - piva
+  location:
+  email:
+- name: Guglielmo Mastroserio
+  github_username: mgullik
+  github_image_id: 14329835
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2024-12-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - stingray
+  packages_reviewed:
+  location:
+  email:
+- name: John Swinbank
+  github_username: jdswinbank
+  github_image_id: 460854
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2024-12-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://swinbank.org/
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - stingray
+  packages_reviewed:
+  location: Utrecht, NL
+  email: john@swinbank.org
+- name:
+  github_username: matteolucchini1
+  github_image_id: 35686549
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2024-12-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - stingray
+  packages_reviewed:
+  location:
+  email:
+- name: Alyssa Columbus
+  github_username: acolum
+  github_image_id: 21285656
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2024-12-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://alyssacolumbus.com
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - quadratik
+  location:
+  email:
+- name: Avik Basu
+  github_username: ab93
+  github_image_id: 3485425
+  title:
+    - Editor
+  sort: 2
+  bio: Data Scientist | Machine Learning Engineer
+  organization: Intuit
+  date_added: '2024-12-13'
+  deia_advisory: false
+  editorial_board: true
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - editor
+    - peer-review
+    - peer-review-guide
+    - reviewer
+  packages_eic:
+  packages_editor:
+    - ams
+    - galassify
+  packages_submitted:
+  packages_reviewed:
+    - quadratik
+  location: Sunnyvale
+  email:
+- name: Raktim Mukhopadhyay
+  github_username: rmj3197
+  github_image_id: 54344732
+  title:
+  sort:
+  bio:
+  organization: SUNY at Buffalo
+  date_added: '2024-12-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - quadratik
+  packages_reviewed:
+  location: Buffalo, New York, USA
+  email:
+- name: Giovanni Saraceno
+  github_username: giovsaraceno
+  github_image_id: 92368611
+  title:
+  sort:
+  bio: My principal area of research are robust statistics, directional
+      statistics, kernel-based methods, neural networks, neuroscience
+      applications.
+  organization: University of Padova
+  date_added: '2024-12-13'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - quadratik
+  packages_reviewed:
+  location:
+  email:
+- name: Santiago Soler
+  github_username: santisoler
+  github_image_id: 11541317
+  title:
+  sort:
+  bio: PhD in Geophysics and Physicist. Postdoc researcher at UBC. Develop
+      @fatiando and @simpeg.
+  organization: '@fatiando @simpeg @ubcgif @compgeolab @GeoLatinas'
+  date_added: '2025-01-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://www.santisoler.com
+  board: false
+  contributor_type:
+    - code-contrib
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: British Columbia, Canada
+  email: santisoler@fastmail.com
+- name: Seth Michael Larson
+  github_username: sethmlarson
+  github_image_id: 18519037
+  title:
+  sort:
+  bio: PSF Security Developer-in-Residence 🐍 PSF Fellow ✨ Minnesoootan, he/him
+  organization: '@psf'
+  date_added: '2025-01-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://sethmlarson.dev
+  board: false
+  contributor_type:
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Minneapolis, MN
+  email: sethmichaellarson@gmail.com
+- name: Erik Whiting
+  github_username: erik-whiting
+  github_image_id: 47164199
+  title:
+  sort:
+  bio: Sr. software engineer @callrail. CS PhD student, deep learning and
+      computational biophysics @YesselmanLab and @yao-laboratory
+  organization:
+  date_added: '2025-01-14'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: ErikWhiting4
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+    - peer-review
+    - reviewer
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - galassify
+    - pyautogalaxy
+  location: Omaha, NE
+  email: erik@erikwhiting.com
+- name:
+  github_username: cjbassin
+  github_image_id: 9651609
+  title:
+  sort:
+  bio: '@CorinneBassin-NOAA@CorinneBassin-SOI'
+  organization:
+  date_added: '2025-01-14'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - great tables
+  location:
+  email:
+- name: Guillaume Lemaitre
+  github_username: glemaitre
+  github_image_id: 7454015
+  title:
+  sort:
+  bio:
+  organization: Open-source engineer @probabl-ai
+  date_added: '2025-01-14'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: glemaitre58
+  mastodon:
+  orcidid:
+  partners:
+  website: https://glemaitre.github.io/
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - great tables
+  location: Paris-Saclay / France
+  email: guillaume@probabl.ai
+- name: Ammar Aziz
+  github_username: ammaraziz
+  github_image_id: 7768245
+  title:
+  sort:
+  bio:
+  organization: Victorian Infectious Disease Reference Laboratory (VIDRL)
+  date_added: '2025-02-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - plot_phylo
+  location:
+  email:
+- name: Jayaram Kancherla
+  github_username: jkanche
+  github_image_id: 399324
+  title:
+  sort:
+  bio: Python, Genomics, JavaScript & everything in between.
+  organization: '@Genentech'
+  date_added: '2025-02-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: jayaram
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - plot_phylo
+  location: San Francisco
+  email: jayaram.kancherla@gmail.com
+- name: Katy Brown
+  github_username: KatyBrown
+  github_image_id: 8896865
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-02-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: thekatybrown1
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - plot_phylo
+  packages_reviewed:
+  location: University of Cambridge
+  email: kab84@cam.ac.uk
+- name: Aarya Patil
+  github_username: aaryapatil
+  github_image_id: 15609154
+  title:
+  sort:
+  bio: LSST Discovery Alliance Postdoctoral Fellow. Finance committee and
+      voting member @astropy.
+  organization: Max Planck Institute for Astronomy
+  date_added: '2025-02-19'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: aarya_patil
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - astrodata
+  location: Heidelberg, Germany
+  email:
+- name: Matt Craig
+  github_username: mwcraig
+  github_image_id: 1147167
+  title:
+  sort:
+  bio:
+  organization: Minnesota State University Moorhead
+  date_added: '2025-02-19'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: astronomatty
+  mastodon:
+  orcidid:
+  partners:
+  website: https://mwcraig.github.io
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - astrodata
+  location: Moorhead, MN
+  email: mattwcraig@gmail.com
+- name: Teal
+  github_username: teald
+  github_image_id: 6620029
+  title:
+  sort:
+  bio: Astronomy, Software, & Other Things
+  organization: NOIRLab
+  date_added: '2025-02-19'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://teald.github.io
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - astrodata
+  packages_reviewed:
+  location: Riverside, CA
+  email: teal.dillon@gmail.com
+- name: Chris Simpson
+  github_username: chris-simpson
+  github_image_id: 22304216
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-02-19'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - astrodata
+  packages_reviewed:
+  location:
+  email: chris.simpson@noirlab.edu
+- name:
+  github_username: jehturner
+  github_image_id: 322026
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-02-19'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - astrodata
+  packages_reviewed:
+  location: La Serena, Chile
+  email:
+- name: Simon O'Meara
+  github_username: simonom
+  github_image_id: 26569960
+  title:
+  sort:
+  bio: Researcher at the National Centre for Atmospheric Science (UK)
+  organization: National Centre for Atmospheric Science, University of
+      Manchester
+  date_added: '2025-02-19'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - pypartmc
+  location: M13 9PL
+  email: simon.omeara@manchester.ac.uk
+- name: Dan Baston
+  github_username: dbaston
+  github_image_id: 6318931
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-02-19'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - pypartmc
+  location: Vermont, USA
+  email: dbaston@gmail.com
+- name: Sylwester Arabas
+  github_username: slayoo
+  github_image_id: 89685
+  title:
+  sort:
+  bio: researching clouds in the cloud
+  organization: agh.edu.pl
+  date_added: '2025-02-19'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://slayoo.github.io/
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - peer-review-guide
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - pypartmc
+  packages_reviewed:
+  location: Kraków, Poland
+  email: sylwester.arabas@agh.edu.pl
+- name: Zach D'Aquino
+  github_username: zdaq12
+  github_image_id: 107204919
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-02-19'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - pypartmc
+  packages_reviewed:
+  location:
+  email:
+- name: Jeffrey Curtis
+  github_username: jcurtis2
+  github_image_id: 8780125
+  title:
+  sort:
+  bio: Research Scientist in the Department of Climate, Meteorology &
+      Atmospheric Sciences at the University of Illinois Urbana-Champaign.
+  organization: University of Illinois Urbana-Champaign
+  date_added: '2025-02-19'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://publish.illinois.edu/jcurtis2/
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - pypartmc
+  packages_reviewed:
+  location: Urbana, Illinois
+  email:
+- name: Nicole Riemer
+  github_username: nriemer
+  github_image_id: 8496047
+  title:
+  sort:
+  bio:
+  organization: University of Illinois at Urbana-Champaign
+  date_added: '2025-02-19'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - pypartmc
+  packages_reviewed:
+  location: Urbana, IL
+  email: nriemer@illinois.edu
+- name: Matthew West
+  github_username: mwest1066
+  github_image_id: 875833
+  title:
+  sort:
+  bio: Professor of Mechanical Science and Engineering
+  organization: University of Illinois at Urbana-Champaign
+  date_added: '2025-02-19'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - pypartmc
+  packages_reviewed:
+  location: Urbana, Illinois, USA
+  email: mwest@illinois.edu
+- name: Agriya Khetarpal
+  github_username: agriyakhetarpal
+  github_image_id: 74401230
+  title:
+  sort:
+  bio: sentient stochastic parrot. @pyodide • @jupyterlite • @pybamm-team •
+      @scientific-python
+  organization: Quansight
+  date_added: '2025-02-28'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: agriyakhetarpal
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - community
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Nadia Dencheva
+  github_username: nden
+  github_image_id: 1110361
+  title:
+  sort:
+  bio:
+  organization: Space Telescope Science Institute
+  date_added: '2025-02-28'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - petrofit
+  location:
+  email:
+- name: Robel Geda
+  github_username: robelgeda
+  github_image_id: 10345916
+  title:
+  sort:
+  bio: Simulations and Visualizations.P.C Sameer A. Khan.
+  organization: Princeton University
+  date_added: '2025-02-28'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://robelgeda.com
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - petrofit
+  packages_reviewed:
+  location:
+  email: robel@robel.io
+- name: Steve Crawford
+  github_username: crawfordsm
+  github_image_id: 1107188
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-02-28'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://crawfordsm.github.io/
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - petrofit
+  packages_reviewed:
+  location: Baltimore, MD
+  email: crawfordsm@gmail.com
+- name: Madicken Munk
+  github_username: munkm
+  github_image_id: 6745434
+  title:
+  sort:
+  bio: Group Leader @arfc, member of @data-exp-lab, @scientific-python, and
+      @yt-project
+  organization: '@NCSA'
+  date_added: '2025-03-20'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://munkm.github.io
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - montepy
+  location: University of Illinois at Urbana-Champaign
+  email:
+- name: Joanna Piper Morgan
+  github_username: jpmorgan98
+  github_image_id: 67020956
+  title:
+  sort:
+  bio: PhD Candidate at Oregon State University focused on radiation transport
+      on GPUs
+  organization: Oregon State University
+  date_added: '2025-03-20'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://jpmorgan98.github.io/
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - montepy
+  location: Corvallis, OR
+  email:
+- name: Micah Gale
+  github_username: MicahGale
+  github_image_id: 12405772
+  title:
+  sort:
+  bio: Nuclear Engineer, PhD Student, aspiring Rustacean; interested in
+      Computational Reactor Physics, and other less useful things. Member of
+      @cnerg.
+  organization: '@idaholab'
+  date_added: '2025-03-20'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - montepy
+  packages_reviewed:
+  location: Madison, Wisconsin
+  email: mdgale@wisc.edu
+- name: Travis L.
+  github_username: tjlaboss
+  github_image_id: 19986691
+  title:
+  sort:
+  bio: Neutronics analysis and reactor physics automation.Engineer at
+      @idaholab andPh.D student with @anovak-lab
+  organization: Idaho National Laboratory
+  date_added: '2025-03-20'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - montepy
+  packages_reviewed:
+  location:
+  email:
+- name: Marie Roald
+  github_username: MarieRoald
+  github_image_id: 3594989
+  title:
+  sort:
+  bio: Python enthusiast and data nerd working at the National Library of
+      Norway. Excited about open source, science outreach and visualization.
+  organization: '@NationalLibraryOfNorway @Sprakbanken'
+  date_added: '2025-05-19'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://marieroald.github.io
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Oslo
+  email:
+- name:
+  github_username: mrgah
+  github_image_id: 11444003
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-05-19'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Ethan White
+  github_username: ethanwhite
+  github_image_id: 744427
+  title:
+  sort:
+  bio: Environmental Data Scientist/Professor. Ecology + open data + open
+      science + open source.
+  organization: '@weecology, Univ of Florida'
+  date_added: '2025-05-30'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://www.weecology.org/
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - neonutilities
+  location: Gainesville, FL
+  email: ethan@weecology.org
+- name:
+  github_username: benjamindonnachie
+  github_image_id: 83379521
+  title:
+  sort:
+  bio: Cybersecurity professional researching machine learning to accelerate
+      post-breach triage with the Open University.
+  organization:
+  date_added: '2025-05-30'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - neonutilities
+  location:
+  email:
+- name: Julieta Millan
+  github_username: JuliMillan
+  github_image_id: 66881995
+  title:
+    - Editor
+  sort: 2
+  bio: Biology, data science and open science
+  organization:
+  date_added: '2025-05-30'
+  deia_advisory: false
+  editorial_board: true
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://julimillan.github.io/
+  board: false
+  contributor_type:
+    - editor
+    - peer-review
+  packages_eic:
+  packages_editor:
+    - neonutilities
+  packages_submitted:
+  packages_reviewed:
+  location: La Plata, Argentina
+  email:
+- name: Claire Lunch
+  github_username: cklunch
+  github_image_id: 7001492
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-05-30'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - neonutilities
+  packages_reviewed:
+  location:
+  email:
+- name: Bridget Hass
+  github_username: bhass-neon
+  github_image_id: 101811216
+  title:
+  sort:
+  bio: Remote Sensing Data Scientist - NEON AOP and Data Skills
+  organization: National Ecological Observatory Network
+  date_added: '2025-05-30'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - neonutilities
+  packages_reviewed:
+  location: Boulder, CO
+  email:
+- name:
+  github_username: znickerson8
+  github_image_id: 56763388
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-05-30'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - neonutilities
+  packages_reviewed:
+  location:
+  email:
+- name: Yngve Mardal Moe
+  github_username: yngvem
+  github_image_id: 3531982
+  title:
+  sort:
+  bio: Data scientist with a passion for scientific computing, applied
+      mathematics and computational biology.
+  organization: Bouvet
+  date_added: '2025-06-01'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Oslo
+  email: yngve.m.moe@gmail.com
+- name: Akhil Krishna R
+  github_username: akhilkrishnar0
+  github_image_id: 164136572
+  title:
+  sort:
+  bio:
+  organization: Christ University
+  date_added: '2025-06-02'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+      https://sites.google.com/res.christuniversity.in/akhilkrishnar/about?pli=1
+  board: false
+  contributor_type:
+    - package-guide
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - galassify
+  location: Bangalore. India
+  email:
+- name: Zac Warham
+  github_username: ZacWarham
+  github_image_id: 48937711
+  title:
+  sort:
+  bio: 'I could never decide between cute animals and a computer screen so here
+      are some of my attempts at doing both! Contact me to learn more: zacwarham@outlook.com'
+  organization:
+  date_added: '2025-06-02'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Vancouver
+  email:
+- name: Sanket Kumar Kar
+  github_username: SanketKumarKar
+  github_image_id: 197726103
+  title:
+  sort:
+  bio:
+  organization: Vellore Institute of Technology, Chennai
+  date_added: '2025-06-05'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Chennai
+  email: sanketkumarkar@gmail.com
+- name: Daniel Chen
+  github_username: chendaniely
+  github_image_id: 5782147
+  title:
+  sort:
+  bio: bow ties are cool
+  organization: '@rstudio @UBC-DSCI @UBC-MDS'
+  date_added: '2025-06-10'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: chendaniely
+  mastodon:
+  orcidid:
+  partners:
+  website: https://chendaniely.github.io
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: JFK -> DCA -> ROA -> JFK -> YVR
+  email:
+- name: Carter Lee Rhea
+  github_username: crhea93
+  github_image_id: 34322936
+  title:
+    - Editor
+  sort: 2
+  bio: Graduate student at Université de Montréal studying astrophysics.
+  organization:
+  date_added: '2025-06-16'
+  deia_advisory: false
+  editorial_board: true
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - code-contrib
+    - editor
+    - peer-review
+    - peer-review-guide
+    - reviewer
+    - web-contrib
+  packages_eic:
+  packages_editor:
+    - astropy
+    - blockingpy
+    - piva
+    - swiftgalaxy
+  packages_submitted:
+  packages_reviewed:
+    - felupe
+    - pyinterpolate
+  location: Montreal, QC, CANADA
+  email:
+- name: Jinning Wang
+  github_username: jinningwang
+  github_image_id: 79226045
+  title:
+  sort:
+  bio: No audacity, no young.
+  organization: University of Tennessee, Knoxville
+  date_added: '2025-06-16'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://ning.guru
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - reviewer
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - ams
+  packages_reviewed:
+    - solar data tools
+  location: Knoxville, Tennessee, USA
+  email: jinninggm@gmail.com
+- name: Echedey Luis
+  github_username: echedey-ls
+  github_image_id: 80125792
+  title:
+  sort:
+  bio: FOSS, PV, Electronics, and Sustainability enthusiast. Also an
+      Electronics Engineer.
+  organization: UPM
+  date_added: '2025-06-16'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - solar data tools
+  location: Spain
+  email:
+- name: Chris Deline
+  github_username: cdeline
+  github_image_id: 23244088
+  title:
+  sort:
+  bio:
+  organization: '@NREL'
+  date_added: '2025-06-16'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - solar data tools
+  location: Golden, CO
+  email: chris.deline@nrel.gov
+- name: Sara A. Miskovich
+  github_username: pluflou
+  github_image_id: 44688920
+  title:
+  sort:
+  bio: Staff Engineer @slaclab |Physics PhD
+  organization: SLAC National Accelerator Laboratory
+  date_added: '2025-06-16'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: saramiskovich
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - solar data tools
+  packages_reviewed:
+  location: Menlo Park, CA
+  email: saramiskovich@gmail.com
+- name: Bennet Meyers
+  github_username: bmeyers
+  github_image_id: 1463184
+  title:
+  sort:
+  bio: PV Performance Specialist, Scientific Coding Enthusiast
+  organization: Stanford & SLAC National Lab
+  date_added: '2025-06-16'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - solar data tools
+  packages_reviewed:
+  location: California
+  email:
+- name: Mihai Maruseac
+  github_username: mihaimaruseac
+  github_image_id: 323199
+  title:
+  sort:
+  bio: Supply chain security @ Google OSS Security Team. Previously TensorFlow
+      Security & OSS (@ Google); Haskell+differential privacy+ML @ LeapYear.
+  organization: Google
+  date_added: '2025-07-18'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: mihaimaruseac
+  mastodon:
+  orcidid:
+  partners:
+  website: https://mihai.page
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: San Francisco
+  email: mihaimaruseac@google.com
+- name: Lauren Moore
+  github_username: tomato-gits
+  github_image_id: 59707547
+  title:
+  sort:
+  bio: Beginner python dev interested in supporting open-source projects,
+      especially scientific and citizen science programs, non-profit orgs, and
+      local governments.
+  organization:
+  date_added: '2025-07-18'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Ana
+  github_username: aplozadab
+  github_image_id: 109044427
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-07-18'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Seattle
+  email:
+- name: Kyohei Sahara
+  github_username: schwalbe10
+  github_image_id: 16644529
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-07-18'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: schwalbe10
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Henry Cuzco
+  github_username: hfactor13
+  github_image_id: 40706933
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-07-18'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: James Lamb
+  github_username: jameslamb
+  github_image_id: 7608904
+  title:
+  sort:
+  bio: (he/him) RAPIDS packaging at NVIDIA. LightGBM maintainer. Economist at
+      heart.
+  organization: NVIDIA
+  date_added: '2025-07-18'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Chicago, IL
+  email: jaylamb20@gmail.com
+- name: Breanna Powell
+  github_username: brepowell
+  github_image_id: 85724630
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-07-22'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Seattle, Washington
+  email:
+- name: Malvika Sharan
+  github_username: malvikasharan
+  github_image_id: 5370471
+  title:
+  sort:
+  bio: 'Keywords: Open Source, Open Science, Community Engagement, Technology, Accessibility'
+  organization: The Turing Way - The Alan Turing Institute
+  date_added: '2025-07-24'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: malvikasharan
+  mastodon:
+  orcidid:
+  partners:
+  website: https://malvikasharan.github.io/
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Galen Seilis
+  github_username: galenseilis
+  github_image_id: 11385121
+  title:
+  sort:
+  bio: Data Scientist
+  organization:
+  date_added: '2025-07-25'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: GSeilis
+  mastodon:
+  orcidid:
+  partners:
+  website: https://galenseilis.github.io/blog/
+  board: false
+  contributor_type:
+    - peer-review-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Canada, British Columbia
+  email:
+- name: Mandy Moore
+  github_username: therubyrep
+  github_image_id: 2262962
+  title: Communications Lead
+  sort: 4
+  bio: Independent social media marketer and audio and video production expert
+  organization: pyOpenSci
+  date_added: '2025-07-25'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Red Lion, PA
+  email: mandy@mandymoore.tech
+- name:
+  github_username: kaiyamag
+  github_image_id: 98053751
+  title:
+  sort:
+  bio: Hello! I am a creative computer science student with a passion for
+      exploring! Some of my research projects are showcased here.
+  organization:
+  date_added: '2025-07-25'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - code-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Franklin Koch
+  github_username: fwkoch
+  github_image_id: 9453731
+  title:
+  sort:
+  bio:
+  organization: '@curvenote'
+  date_added: '2025-07-25'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - code-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Calgary, AB
+  email: franklinwkoch@gmail.com
+- name: Angus Hollands
+  github_username: agoose77
+  github_image_id: 1248413
+  title:
+  sort:
+  bio: 👐 Open Source ⚙️ Applications Engineer @ 🌎 2i2c & owner @ OIE LTD,
+      developing 👐 open-source 📈 scientific 💻✨ software since 2009 ❤️
+  organization: 2i2c
+  date_added: '2025-07-25'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://oieltd.com
+  board: false
+  contributor_type:
+    - code-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: United Kingdom
+  email: angus@oieltd.com
+- name: Camille Latapie
+  github_username: clatapie
+  github_image_id: 78221213
+  title:
+  sort:
+  bio: Applied Mathematics engineer interested in modeling.
+  organization:
+  date_added: '2025-07-25'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - code-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: France
+  email:
+- name:
+  github_username: rogerb121
+  github_image_id: 109387723
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-07-25'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - code-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: steven
+  github_username: stevenrayhinojosa-gmail-com
+  github_image_id: 17886818
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-07-25'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - code-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Austin
+  email:
+- name: s choi
+  github_username: infinite0x20
+  github_image_id: 66569284
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-07-25'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - open-education
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name:
+  github_username: ecourt93
+  github_image_id: 197415376
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-07-25'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - open-education
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Evelyn Montes Sobal
+  github_username: EvelynMS1
+  github_image_id: 102782127
+  title:
+  sort:
+  bio: Full Stack Web Developer montessobalevelyn@gmail.com
+  organization:
+  date_added: '2025-07-25'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - open-education
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Karina Souza
+  github_username: KarinaS0uza
+  github_image_id: 97332018
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-07-25'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - open-education
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Seattle
+  email:
+- name:
+  github_username: veronicasoelundkirsebom
+  github_image_id: 68337448
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-07-25'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - open-education
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Tim Dawson
+  github_username: TimothyEDawson
+  github_image_id: 142453358
+  title:
+  sort:
+  bio: Combustion Group Leader at CFD Research Corporation.
+  organization: CFD Research Corporation
+  date_added: '2025-08-07'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email: tim.dawson@cfd-research.com
+- name: James J Balamuta
+  github_username: coatless
+  github_image_id: 833642
+  title:
+  sort:
+  bio: 'omnipresent explorer of the unknown, fashionably caffeinated informatics
+      phd, amorous cavalier. design, build, analyze. #rstats #python @tmsalab'
+  organization:
+  date_added: '2025-08-07'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: axiomsofxyz
+  mastodon:
+  orcidid:
+  partners:
+  website: https://thecoatlessprofessor.com
+  board: false
+  contributor_type:
+    - eic
+    - peer-review
+  packages_eic:
+    - blockingpy
+    - galfitools
+    - greopy
+    - piva
+    - pyautogalaxy
+    - pymultifit
+    - swiftgalaxy
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: United States
+  email:
+- name: Arthur Eigenbrot
+  github_username: eigenbrot
+  github_image_id: 2183757
+  title:
+  sort:
+  bio:
+  organization: National Solar Observatory
+  date_added: '2025-08-07'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - piva
+  location:
+  email:
+- name: Wojtek Pudelko
+  github_username: pudeIko
+  github_image_id: 37271202
+  title:
+  sort:
+  bio:
+  organization: University of Zürich
+  date_added: '2025-08-07'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - piva
+  packages_reviewed:
+  location: Zürich, Switzerland
+  email:
+- name: Sanjana Kandi
+  github_username: KandiSanjana
+  github_image_id: 62292708
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-08-07'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - greopy
+    - pymultifit
+  location: Seattle
+  email:
+- name: Jonas Eschle
+  github_username: jonas-eschle
+  github_image_id: 17454848
+  title:
+    - Editor
+  sort: 2
+  bio: Large scale statistics, machine learning and software engineering in
+      High Energy Physics
+  organization: CERN
+  date_added: '2025-08-07'
+  deia_advisory: false
+  editorial_board: true
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - editor
+    - peer-review
+  packages_eic:
+  packages_editor:
+    - greopy
+  packages_submitted:
+  packages_reviewed:
+  location: Geneva, Switzerland
+  email: jonas.eschle@cern.ch
+- name:
+  github_username: irideselby
+  github_image_id: 172918893
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-08-07'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - greopy
+  packages_reviewed:
+  location:
+  email:
+- name: Kai Striega
+  github_username: Kai-Striega
+  github_image_id: 30074037
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-08-22'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - cynetdiff
+    - fluidimage
+  location:
+  email:
+- name: SQ
+  github_username: jeremyzhangsq
+  github_image_id: 32925891
+  title:
+  sort:
+  bio: Research Fellow in SoC@NUS
+  organization: SoC@NUS
+  date_added: '2025-08-22'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://www.comp.nus.edu.sg/~s-zhang/
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - cynetdiff
+  location: Singapore
+  email:
+- name: Abhishek Umrawal
+  github_username: abhishekumrawal
+  github_image_id: 7496935
+  title:
+  sort:
+  bio: Tch. Asst. Prof. of ECE at Illinois | Ph.D. from Purdue | AI & ML
+      Researcher
+  organization: University of Illinois Urbana-Champaign
+  date_added: '2025-08-22'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - cynetdiff
+  packages_reviewed:
+  location: Urbana, IL
+  email: abhishekumrawal@gmail.com
+- name: Alireza
+  github_username: Alizak-Mech
+  github_image_id: 174788670
+  title:
+  sort:
+  bio: A Mechanical Engineer with a Bachelor's degree in Mechanical
+      Engineering and a Master's degree in Energy Engineering, specializing in
+      Energy Technologies.
+  organization:
+  date_added: '2025-09-10'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - ams
+  location:
+  email: alirezakhoee@yahoo.com
+- name: Alireza Alamgir
+  github_username: AlirezaAlamgir
+  github_image_id: 174625766
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-09-10'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - ams
+  location:
+  email:
+- name: Kavian Mashayekhi
+  github_username: Kawians
+  github_image_id: 115752969
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-09-10'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - ams
+  location:
+  email:
+- name: Ellie Abrahams
+  github_username: elliesch
+  github_image_id: 12628861
+  title:
+  sort:
+  bio: cryosphere + image processing + data science
+  organization: Stanford, University
+  date_added: '2025-09-27'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - tda-mapper
+  location: Stanford, CA
+  email:
+- name: Jed Brown
+  github_username: jedbrown
+  github_image_id: 3303
+  title:
+  sort:
+  bio: Physical Prediction, Inference, & Design (PhyPID). Fast algorithms &
+      community software. Prof at CU Boulder. Alpinist, skier, runner.
+  organization: CU Boulder
+  date_added: '2025-09-27'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://jedbrown.org
+  board: false
+  contributor_type:
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email: jed@jedbrown.org
+- name: Nicolás Guarín-Zapata
+  github_username: nicoguaro
+  github_image_id: 1097787
+  title:
+  sort:
+  bio:
+  organization: Universidad EAFIT
+  date_added: '2025-09-27'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: nicoguaro
+  mastodon:
+  orcidid:
+  partners:
+  website: https://nicoguaro.github.io
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - felupe
+  location: Medellín
+  email:
+- name: Andreas Dutzler
+  github_username: adtzlr
+  github_image_id: 5793153
+  title:
+  sort:
+  bio: PhD Candidate in Mechanical Engineering@ TU Graz. Development Engineer
+      in the Railway Industry. Opinions related to this account are my own.
+  organization: Graz University of Technology
+  date_added: '2025-09-27'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - felupe
+  packages_reviewed:
+  location: Graz, Austria
+  email:
+- name:
+  github_username: Michael-Howes
+  github_image_id: 50608711
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-10-17'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location:
+  email:
+- name: Nick Hodgskin
+  github_username: VeckoTheGecko
+  github_image_id: 36369090
+  title:
+  sort:
+  bio: Research Software Engineer at @UtrechtUniversity
+  organization: Utrecht University
+  date_added: '2025-10-17'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - web-contrib
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Utrecht, Netherlands
+  email:
+- name: Ang
+  github_username: HzaCode
+  github_image_id: 92981090
+  title:
+  sort:
+  bio: Medical Doctor · Open-Source Developer · Marathoner/Tri · CSCS
+      (Finalist) | 🌊 Starting a new research journey soon. | Run as fast as my
+      coding:)
+  organization:
+  date_added: '2025-10-17'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - cheminformant
+  packages_reviewed:
+  location:
+  email: ang@hezhiang.com
+- name: Blake A. Wilson
+  github_username: blakeaw
+  github_image_id: 20207940
+  title:
+  sort:
+  bio: Computational research science in physical chemistry, systems biology,
+      and nano-bioengineering.
+  organization:
+  date_added: '2025-10-17'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://blakeaw.github.io/
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - swiftgalaxy
+  location: Texas, USA
+  email:
+- name: Kristina Gagalova
+  github_username: KristinaGagalova
+  github_image_id: 25466163
+  title:
+  sort:
+  bio: Life curious and traveller - 🙋🏻‍♀️ Nextflow Ambassador; Works on:🧬
+      Genome Science and Algorithms | 💻 Software Development | 👽 AI dev
+  organization: Research scientist
+  date_added: '2025-10-17'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://kristinagagalova.github.io/
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - pymultifit
+  location:
+  email: kristina.gagalova@curtin.edu.au
+- name: Syed Ali Mohsin Bukhari
+  github_username: syedalimohsinbukhari
+  github_image_id: 68902636
+  title:
+  sort:
+  bio:
+  organization: Space and Astrophysics Research Lab
+  date_added: '2025-10-17'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - pymultifit
+  packages_reviewed:
+  location: Islamabad, Pakistan
+  email: syedali.b@outlook.com
+- name: Akrita
+  github_username: akritaag
+  github_image_id: 2558622
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-10-17'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - blockingpy
+  location: Seattle, WA
+  email: akrita.ag@gmail.com
+- name: Tymoteusz Strojny
+  github_username: T-Strojny
+  github_image_id: 117780025
+  title:
+  sort:
+  bio: Master’s student in Data Processing and Analytics at Adam Mickiewicz
+      University in Poznań
+  organization:
+  date_added: '2025-10-17'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - blockingpy
+  packages_reviewed:
+  location:
+  email:
+- name: Michael Pilosov, PhD
+  github_username: mathematicalmichael
+  github_image_id: 40366263
+  title:
+  sort:
+  bio: artist trapped in a mathematician's mind
+  organization: '@mindthemath'
+  date_added: '2025-10-18'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter: compmathematics
+  mastodon:
+  orcidid:
+  partners:
+  website: https://mpilosov.com
+  board: false
+  contributor_type:
+    - package-guide
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+  location: Denver, CO
+  email:
+- name: James Nightingale
+  github_username: Jammy2211
+  github_image_id: 23455639
+  title:
+  sort:
+  bio: Ernest Rutherford Fellow at Newcastle UniversityDeveloper of PyAutoLens
+  organization: Newcastle University
+  date_added: '2025-11-08'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - reviewer
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - pyautogalaxy
+  packages_reviewed:
+    - galfitools
+  location: Newcastle
+  email: James.Nightingale@newcastle.ac.uk
+- name: T. E. Pickering
+  github_username: tepickering
+  github_image_id: 2481822
+  title:
+  sort:
+  bio: astronomer, python hacker
+  organization: MMT Observatory
+  date_added: '2025-11-08'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://www.mmto.org
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - galfitools
+  location: Tucson, AZ, USA
+  email: te.pickering@gmail.com
+- name: Chris Añorve
+  github_username: canorve
+  github_image_id: 3579189
+  title:
+  sort:
+  bio: Computer Astro programmer
+  organization: FACITE
+  date_added: '2025-11-08'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - reviewer
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - galfitools
+  packages_reviewed:
+    - pyautogalaxy
+  location: Sinaloa, Mexico
+  email:
+- name:
+  github_username: Manalclay
+  github_image_id: 166520075
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-12-09'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - galassify
+  packages_reviewed:
+  location:
+  email:
+- name: Andoni
+  github_username: andonij
+  github_image_id: 91870745
+  title:
+  sort:
+  bio:
+  organization: UGR
+  date_added: '2025-12-09'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - galassify
+  packages_reviewed:
+  location: Spain
+  email:
+- name: Aditya P T
+  github_username: adityapt
+  github_image_id: 13266121
+  title:
+  sort:
+  bio: Principal Data Scientist
+  organization: Zillow
+  date_added: '2025-12-31'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - astropy
+  location: Bay Area
+  email:
+- name:
+  github_username: egbdfX
+  github_image_id: 107475738
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-12-31'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - astropy
+  location:
+  email:
+- name: i
+  github_username: i
+  github_image_id: 2905137
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2025-12-31'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - astropy
+  packages_reviewed:
+  location:
+  email:
+- name: The Astropy Project
+  github_username: astropy
+  github_image_id: 847984
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2026-01-24'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://www.astropy.org
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - astropy
+  packages_reviewed:
+  location:
+  email:
+- name: Daniela Pamplona
+  github_username: DanielaPamplona
+  github_image_id: 46706155
+  title:
+  sort:
+  bio:
+  organization: UPEC
+  date_added: '2026-03-16'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website: https://danielapamplona.github.io/
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - plenoptic
+  location: France
+  email:
+- name: Leah Mendelson
+  github_username: leahmendelson
+  github_image_id: 8322733
+  title:
+  sort:
+  bio: Associate Professor of Engineering
+  organization: Harvey Mudd College
+  date_added: '2026-05-04'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - fluidimage
+  location: Claremont, CA
+  email: lmendelson@g.hmc.edu
+- name:
+  github_username: emmylia321
+  github_image_id: 168062638
+  title:
+  sort:
+  bio:
+  organization:
+  date_added: '2026-05-04'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - peer-review
+    - reviewer
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+  packages_reviewed:
+    - fluidimage
+  location:
+  email:
+- name: Pierre Augier
+  github_username: paugier
+  github_image_id: 8842662
+  title:
+  sort:
+  bio:
+  organization: CNRS
+  date_added: '2026-05-04'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - fluidimage
+  packages_reviewed:
+  location:
+  email: pierre.augier@univ-grenoble-alpes.fr
+- name: Luca Simi
+  github_username: lucasimi
+  github_image_id: 45110399
+  title:
+  sort:
+  bio: Software engineer by day, math nerd by night.
+  organization:
+  date_added: '2026-05-18'
+  deia_advisory: false
+  editorial_board: false
+  emeritus_editor: false
+  advisory: false
+  emeritus_advisory: false
+  twitter:
+  mastodon:
+  orcidid:
+  partners:
+  website:
+  board: false
+  contributor_type:
+    - maintainer
+    - peer-review
+    - submitting-author
+  packages_eic:
+  packages_editor:
+  packages_submitted:
+    - tda-mapper
+  packages_reviewed:
+  location: Rome, Italy
+  email:
diff --git a/data/packages.yml b/data/packages.yml
new file mode 100644
index 00000000..b00ec872
--- /dev/null
+++ b/data/packages.yml
@@ -0,0 +1,3296 @@
+- package_name: ChemInformant
+  package_description: A robust, high-throughput Python client for retrieving
+      chemical information from the PubChem API; it returns analysis-ready
+      Pandas/SQL outputs, handles caching, rate-limiting and retries, and
+      includes convenient CLI tools.
+  submitting_author:
+      name: Zhiang He
+      github_username: HzaCode
+  all_current_maintainers:
+    - name: Zhiang He
+      github_username: HzaCode
+  repository_link: https://github.com/HzaCode/ChemInformant
+  repository_host: github
+  version_submitted: 2.4.0 (released 2025-07-30)
+  categories:
+    - data-retrieval
+    - data-extraction
+    - data-processing-munging
+    - data-validation-testing
+    - workflow-automation
+    - scientific-software-wrapper
+    - database-interoperability
+  editor:
+      name: Eliot Robson
+      github_username: eliotwrobson
+  eic:
+      name: Eliot Robson
+      github_username: eliotwrobson
+  reviewers:
+  archive: https://zenodo.org/doi/10.5281/zenodo.16623785
+  version_accepted: TBD
+  date_accepted: missing
+  created_at: 2025-07-31 17:50:42+00:00
+  updated_at: 2025-10-07 16:39:26+00:00
+  closed_at: 2025-10-01 15:35:48+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/254
+  joss: https://joss.theoj.org/papers/10.21105/joss.08341
+  partners:
+  gh_meta:
+      name: ChemInformant
+      description: ⚗️ An all-in-one solution for chemical property retrieval
+          from PubChem.
+      created_at: '2024-01-21'
+      stargazers_count: 29
+      watchers_count: 4
+      open_issues_count: 0
+      forks_count: 4
+      documentation: https://hezhiang.com/cheminformant_real.html
+      contrib_count: 2
+      last_commit: '2026-04-19'
+  labels:
+    - 6/pyOS-approved
+    - joss-fast-track
+  active: true
+- package_name: astropy
+  package_description: A Community Python Library for Astronomy
+  submitting_author:
+      name: P. L. Lim
+      github_username: pllim
+  all_current_maintainers:
+    - name: The Astropy Project
+      github_username: astropy
+  repository_link: https://github.com/astropy/astropy
+  repository_host: github
+  version_submitted: 7.1.0
+  categories:
+    - data-retrieval
+    - data-extraction
+    - data-processing-munging
+    - data-visualization
+    - scientific-software-wrapper
+  editor:
+      name: Carter Lee Rhea
+      github_username: crhea93
+  eic:
+      name: Lauren Yee
+      github_username: yeelauren
+  reviewers:
+    - name: Aditya P T
+      github_username: adityapt
+    - name:
+      github_username: egbdfx
+  archive: https://zenodo.org/doi/10.5281/zenodo.17756022
+  version_accepted: 7.1.0
+  date_accepted: '2025-12-17'
+  created_at: 2025-07-14 21:58:24+00:00
+  updated_at: 2026-01-23 22:37:03+00:00
+  closed_at: 2026-01-22 23:06:56+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/251
+  joss:
+  partners:
+    - astropy
+  gh_meta:
+      name: astropy
+      description: Astronomy and astrophysics core library
+      created_at: '2011-07-21'
+      stargazers_count: 5165
+      watchers_count: 139
+      open_issues_count: 1278
+      forks_count: 2077
+      documentation: https://www.astropy.org
+      contrib_count: 447
+      last_commit: '2026-05-18'
+  labels:
+    - 6/pyOS-approved
+    - astropy
+  active: true
+- package_name: Pyinterpolate
+  package_description: 'Spatial interpolation: Kriging and Variogram Analysis toolset'
+  submitting_author:
+      name: Szymon Moliński
+      github_username: SimonMolinsky
+  all_current_maintainers:
+    - name: Szymon Moliński
+      github_username: SimonMolinsky
+  repository_link: https://github.com/DataverseLabs/pyinterpolate
+  repository_host: github
+  version_submitted: 1.0.1
+  categories:
+    - data-processing-munging
+  editor:
+      name: Bane Sullivan
+      github_username: banesullivan
+  eic:
+      name: Eliot Robson
+      github_username: eliotwrobson
+  reviewers:
+    - name: Carter Lee Rhea
+      github_username: crhea93
+    - name: Martin Fleischmann
+      github_username: martinfleis
+  archive: https://zenodo.org/doi/10.5281/zenodo.17691515
+  version_accepted: 1.2.0
+  date_accepted: 2025-12-3
+  created_at: 2025-07-12 14:09:45+00:00
+  updated_at: 2026-01-21 20:08:01+00:00
+  closed_at: 2026-01-21 20:08:01+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/250
+  joss: https://joss.theoj.org/papers/10.21105/joss.02869
+  partners:
+  gh_meta:
+      name: pyinterpolate
+      description: Kriging | Poisson Kriging | Variogram Analysis
+      created_at: '2018-04-16'
+      stargazers_count: 175
+      watchers_count: 2
+      open_issues_count: 7
+      forks_count: 30
+      documentation: https://pyinterpolate.readthedocs.io/en/stable/
+      contrib_count: 13
+      last_commit: '2025-12-26'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+  active: true
+- package_name: swiftgalaxy
+  package_description: Load in particles of a simulated galaxy, rotate
+      coordinates, easy spherical/cylindrical coordinates, access integrated
+      properties, and more.
+  submitting_author:
+      name: Kyle Oman
+      github_username: kyleaoman
+  all_current_maintainers:
+    - name: Kyle Oman
+      github_username: kyleaoman
+  repository_link: https://github.com/SWIFTSIM/swiftgalaxy
+  repository_host: github
+  version_submitted: 2.1.1
+  categories:
+    - data-extraction
+    - data-processing-munging
+  editor:
+      name: Carter Lee Rhea
+      github_username: crhea93
+  eic:
+      name: James J Balamuta
+      github_username: coatless
+  reviewers:
+    - name: Blake A. Wilson
+      github_username: blakeaw
+    - name: Chase Million
+      github_username: cmillion
+  archive: https://zenodo.org/doi/10.5281/zenodo.17382007
+  version_accepted: v2.2.1
+  date_accepted: '2025-10-17'
+  created_at: 2025-05-24 11:05:16+00:00
+  updated_at: 2025-12-17 23:10:08+00:00
+  closed_at: 2025-12-17 23:09:26+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/244
+  joss: https://joss.theoj.org/papers/10.21105/joss.09278
+  partners:
+  gh_meta:
+      name: swiftgalaxy
+      description: Load in particles of a simulated galaxy, rotate
+          coordinates, easy spherical/cylindrical coordinates, access
+          integrated properties, and more.
+      created_at: '2022-05-03'
+      stargazers_count: 9
+      watchers_count: 3
+      open_issues_count: 3
+      forks_count: 5
+      documentation: https://swiftgalaxy.readthedocs.io/en/stable/index.html
+      contrib_count: 3
+      last_commit: '2026-05-06'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+  active: true
+- package_name: PyAutoGalaxy
+  package_description: Astronomy software for analysing the morphologies and
+      structures of galaxies
+  submitting_author:
+      name: James Nightingale
+      github_username: Jammy2211
+  all_current_maintainers:
+    - name: James Nightingale
+      github_username: Jammy2211
+  repository_link: https://github.com/Jammy2211/PyAutoGalaxy
+  repository_host: github
+  version_submitted: '[2025.1.18.7](https://github.com/Jammy2211/PyAutoGalaxy/tree/2025.1.18.7)'
+  categories:
+    - data-processing-munging
+    - scientific-software-wrapper
+  editor:
+      name: Hans Moritz Günther
+      github_username: hamogu
+  eic:
+      name: James J Balamuta
+      github_username: coatless
+  reviewers:
+    - name: Chris Añorve
+      github_username: canorve
+    - name: Erik Whiting
+      github_username: erik-whiting
+  archive: https://zenodo.org/doi/10.5281/zenodo.19552258
+  version_accepted: v2026.4.13.6
+  date_accepted: '2026-05-04'
+  created_at: 2025-03-13 13:15:30+00:00
+  updated_at: 2026-05-04 17:41:20+00:00
+  closed_at: 2026-05-04 17:41:20+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/235
+  joss:
+  partners:
+    - astropy
+  gh_meta:
+      name: PyAutoGalaxy
+      description: 'PyAutoGalaxy: Open-Source Multiwavelength Galaxy Structure &
+          Morphology'
+      created_at: '2019-10-19'
+      stargazers_count: 32
+      watchers_count: 3
+      open_issues_count: 6
+      forks_count: 13
+      documentation: https://pyautogalaxy.readthedocs.io/
+      contrib_count: 15
+      last_commit: '2026-05-18'
+  labels:
+    - 6/pyOS-approved
+    - astropy
+  active: true
+- package_name: pymultifit
+  package_description: A python library for fitting data with multiple models.
+  submitting_author:
+      name: Syed Ali Mohsin Bukhari
+      github_username: syedalimohsinbukhari
+  all_current_maintainers:
+    - name: Syed Ali Mohsin Bukhari
+      github_username: syedalimohsinbukhari
+  repository_link: https://github.com/syedalimohsinbukhari/pyMultiFit
+  repository_host: github
+  version_submitted: ~v1.0.3~
+      [v1.0.6](https://github.com/syedalimohsinbukhari/pyMultiFit/releases/tag/v1.0.6)
+  categories:
+    - data-processing-munging
+  editor:
+      name: Alex Batisse
+      github_username: batalex
+  eic:
+      name: James J Balamuta
+      github_username: coatless
+  reviewers:
+    - name: Sanjana Kandi
+      github_username: KandiSanjana
+    - name: Kristina Gagalova
+      github_username: KristinaGagalova
+  archive: https://zenodo.org/records/17273507
+  version_accepted: 1.0.7
+  date_accepted: '2025-10-05'
+  created_at: 2025-01-21 07:30:12+00:00
+  updated_at: 2025-11-05 11:15:18+00:00
+  closed_at: 2025-11-05 10:09:46+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/233
+  joss: https://joss.theoj.org/papers/10.21105/joss.09295
+  partners:
+  gh_meta:
+      name: pyMultiFit
+      description: A library to fit the data with multiple fitters.
+      created_at: '2024-07-17'
+      stargazers_count: 5
+      watchers_count: 1
+      open_issues_count: 11
+      forks_count: 0
+      documentation: https://pymultifit.readthedocs.io/latest/
+      contrib_count: 2
+      last_commit: '2025-12-25'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+  active: true
+- package_name: BlockingPy
+  package_description: Blocking records for record linkage and deduplication
+      with Approximate Nearest Neighbor algorithms.;
+  submitting_author:
+      name: Tymoteusz Strojny
+      github_username: T-Strojny
+  all_current_maintainers:
+    - name: Tymoteusz Strojny
+      github_username: T-Strojny
+  repository_link: https://github.com/ncn-foreigners/BlockingPy
+  repository_host: github
+  version_submitted: v0.1.7
+  categories:
+    - data-processing-munging
+  editor:
+    - name: Carter Lee Rhea
+      github_username: crhea93
+    - name: Isabel Zimmerman
+      github_username: isabelizimm
+  eic:
+      name: James J Balamuta
+      github_username: coatless
+  reviewers:
+    - name: Akrita
+      github_username: akritaag
+    - name: Eliot Robson
+      github_username: eliotwrobson
+  archive:
+  version_accepted: TBD
+  date_accepted: missing
+  created_at: 2025-01-09 18:13:33+00:00
+  updated_at: 2026-04-14 06:48:44+00:00
+  closed_at: 2026-04-13 22:09:55+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/232
+  joss:
+  partners:
+  gh_meta:
+      name: BlockingPy
+      description: Blocking records for record linkage and data deduplication
+          based on ANN algorithms in Python.
+      created_at: '2024-10-11'
+      stargazers_count: 20
+      watchers_count: 1
+      open_issues_count: 1
+      forks_count: 2
+      documentation: https://blockingpy.readthedocs.io/en/latest/
+      contrib_count: 1
+      last_commit: '2026-03-09'
+  labels:
+    - 6/pyOS-approved
+  active: true
+- package_name: PIVA
+  package_description: Visualization and analysis toolkit for experimental
+      data from Angle-Resolved Photoemission Spectroscopy (ARPES)
+  submitting_author:
+      name: Wojciech Radoslaw Pudelko
+      github_username: pudeIko
+  all_current_maintainers:
+    - name: Wojciech Radoslaw Pudelko
+      github_username: pudeIko
+  repository_link: https://github.com/pudeIko/piva
+  repository_host: github
+  version_submitted: v2.3.2
+  categories:
+    - data-extraction
+    - data-visualization
+  editor:
+      name: Carter Lee Rhea
+      github_username: crhea93
+  eic:
+      name: James J Balamuta
+      github_username: coatless
+  reviewers:
+    - name: J. Steven Dodge
+      github_username: jsdodge
+    - name: Arthur Eigenbrot
+      github_username: eigenbrot
+  archive: https://zenodo.org/doi/10.5281/zenodo.16755506
+  version_accepted: v3.0.0
+  date_accepted: '2025-08-04'
+  created_at: 2025-01-04 14:36:12+00:00
+  updated_at: 2025-10-06 13:10:53+00:00
+  closed_at: 2025-10-06 13:10:53+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/231
+  joss: https://joss.theoj.org/papers/10.21105/joss.09129
+  partners:
+  gh_meta:
+      name: piva
+      description: Interactive tools for the visualization and analysis of
+          multidimensional photoemission data
+      created_at: '2022-04-12'
+      stargazers_count: 9
+      watchers_count: 1
+      open_issues_count: 7
+      forks_count: 3
+      documentation: https://piva.readthedocs.io/en/latest/intro.html
+      contrib_count: 3
+      last_commit: '2025-10-06'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+  active: true
+- package_name: GREOPy
+  package_description: Calculate relativistic light rays sent by an emitter to
+      a receiver in the presence of a gravitational field.
+  submitting_author:
+      name: Jan P. Hackstein
+      github_username: irideselby
+  all_current_maintainers:
+    - name:
+      github_username: irideselby
+  repository_link: https://codeberg.org/JPHackstein/GREOPy
+  repository_host: codeberg
+  version_submitted: v0.2.1
+  categories:
+    - data-processing-munging
+  editor:
+      name: Jonas Eschle
+      github_username: jonas-eschle
+  eic:
+      name: James J Balamuta
+      github_username: coatless
+  reviewers:
+    - name: Leo Singer
+      github_username: lpsinger
+    - name: Sanjana Kandi
+      github_username: KandiSanjana
+  archive: https://zenodo.org/records/14537866
+  version_accepted: '1.0'
+  date_accepted: '2025-08-04'
+  created_at: 2024-12-21 12:34:09+00:00
+  updated_at: 2025-10-07 18:08:25+00:00
+  closed_at: 2025-10-07 18:05:53+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/227
+  joss: https://joss.theoj.org/papers/10.21105/joss.08765
+  partners:
+  gh_meta:
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+  active: true
+- package_name: tda-mapper
+  package_description: A Python library implementing the Mapper algorithm for
+      Topological Data Analysis.
+  submitting_author:
+      name: Luca Simi
+      github_username: lucasimi
+  all_current_maintainers:
+    - name: Luca Simi
+      github_username: lucasimi
+  repository_link: https://github.com/lucasimi/tda-mapper-python
+  repository_host: github
+  version_submitted: v0.9.0
+  categories:
+    - data-processing-munging
+    - data-visualization
+  editor:
+      name: Lauren Yee
+      github_username: yeelauren
+  eic:
+      name: Szymon Moliński
+      github_username: SimonMolinsky
+  reviewers:
+    - name: A Samuel Pottinger
+      github_username: sampottinger
+    - name: Ellie Abrahams
+      github_username: elliesch
+  archive:
+  version_accepted: TBD
+  date_accepted: missing
+  created_at: 2024-12-15 09:07:37+00:00
+  updated_at: 2026-05-12 14:55:58+00:00
+  closed_at:
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/222
+  joss:
+  partners:
+  gh_meta:
+      name: tda-mapper-python
+      description: A simple and efficient Python implementation of Mapper
+          algorithm for Topological Data Analysis
+      created_at: '2022-10-03'
+      stargazers_count: 177
+      watchers_count: 6
+      open_issues_count: 10
+      forks_count: 25
+      documentation: https://tda-mapper.readthedocs.io/en/main/
+      contrib_count: 1
+      last_commit: '2025-09-22'
+  labels:
+    - 6/pyOS-approved
+  active: true
+- package_name: GALFITools
+  package_description: A library for efficient data processing customized for
+      the GALFIT package
+  submitting_author:
+      name: Chris Añorve
+      github_username: canorve
+  all_current_maintainers:
+    - name: Chris Añorve
+      github_username: canorve
+  repository_link: https://github.com/canorve/GALFITools
+  repository_host: github
+  version_submitted: v1.15.0
+  categories:
+    - data-extraction
+    - data-processing-munging
+    - data-visualization
+  editor:
+      name: Hans Moritz Günther
+      github_username: hamogu
+  eic:
+    - name: Szymon Moliński
+      github_username: SimonMolinsky
+    - name: James J Balamuta
+      github_username: coatless
+  reviewers:
+    - name: James Nightingale
+      github_username: Jammy2211
+    - name: T. E. Pickering
+      github_username: tepickering
+  archive: https://zenodo.org/records/17010007
+  version_accepted: 1.18.0
+  date_accepted: '2025-10-30'
+  created_at: 2024-12-07 00:28:52+00:00
+  updated_at: 2025-12-31 20:10:10+00:00
+  closed_at: 2025-12-31 18:36:25+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/220
+  joss: https://joss.theoj.org/papers/10.21105/joss.09534
+  partners:
+    - astropy
+  gh_meta:
+      name: GALFITools
+      description: A library for GALFIT
+      created_at: '2018-11-10'
+      stargazers_count: 19
+      watchers_count: 1
+      open_issues_count: 1
+      forks_count: 4
+      documentation:
+      contrib_count: 3
+      last_commit: '2026-05-18'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+    - astropy
+  active: true
+- package_name: GALAssify
+  package_description: A Python package for visually classifying astronomical
+      objects
+  submitting_author:
+      name: Manuel Alcázar-Laynez
+      github_username: Manalclay
+  all_current_maintainers:
+    - name:
+      github_username: Manalclay
+    - name: Andoni
+      github_username: andonij
+  repository_link: https://gitlab.com/astrogal/GALAssify/
+  repository_host: gitlab
+  version_submitted: v1.0.1
+  categories:
+    - data-validation-testing
+    - data-visualization
+  editor:
+      name: Avik Basu
+      github_username: ab93
+  eic:
+      name: Szymon Moliński
+      github_username: SimonMolinsky
+  reviewers:
+    - name: Akhil Krishna R
+      github_username: akhilkrishnar0
+    - name: Erik Whiting
+      github_username: erik-whiting
+  archive: https://zenodo.org/records/17433197
+  version_accepted: v2.0.0
+  date_accepted: '2025-11-16'
+  created_at: 2024-09-30 09:12:52+00:00
+  updated_at: 2025-12-12 13:12:57+00:00
+  closed_at: 2025-12-10 03:33:49+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/214
+  joss:
+  partners:
+  gh_meta:
+  labels:
+    - 6/pyOS-approved
+  active: true
+- package_name: neonutilities
+  package_description: neonutilities is a package for accessing and wrangling
+      data generated and published by the National Ecological Observatory
+      Network.
+  submitting_author:
+      name: Claire Lunch
+      github_username: cklunch
+  all_current_maintainers:
+    - name: Claire Lunch
+      github_username: cklunch
+    - name: Bridget Hass
+      github_username: bhass-neon
+    - name:
+      github_username: znickerson8
+  repository_link: https://github.com/NEONScience/NEON-utilities-python
+  repository_host: github
+  version_submitted: v1.0.1
+  categories:
+    - data-retrieval
+    - data-processing-munging
+  editor:
+      name: Julieta Millan
+      github_username: JuliMillan
+  eic:
+      name: Chiara Marmo
+      github_username: cmarmo
+  reviewers:
+    - name: Ethan White
+      github_username: ethanwhite
+    - name:
+      github_username: benjamindonnachie
+  archive: https://zenodo.org/doi/10.5281/zenodo.15530180
+  version_accepted: v1.1.0
+  date_accepted: 2025-05- 10
+  created_at: 2024-09-25 21:27:31+00:00
+  updated_at: 2025-06-11 23:06:08+00:00
+  closed_at: 2025-05-30 16:31:22+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/213
+  joss:
+  partners:
+  gh_meta:
+      name: NEON-utilities-python
+      description: Repository for Python package containing data-wrangling
+          utilities for working with NEON data.
+      created_at: '2023-08-25'
+      stargazers_count: 10
+      watchers_count: 4
+      open_issues_count: 0
+      forks_count: 5
+      documentation: https://neon-utilities-python.readthedocs.io/en/latest/
+      contrib_count: 6
+      last_commit: '2026-03-24'
+  labels:
+    - 6/pyOS-approved
+  active: true
+- package_name: FElupe
+  package_description: Finite element analysis for continuum mechanics of
+      solid bodies.
+  submitting_author:
+      name: Andreas Dutzler
+      github_username: adtzlr
+  all_current_maintainers:
+    - name: Andreas Dutzler
+      github_username: adtzlr
+  repository_link: https://github.com/adtzlr/felupe
+  repository_host: github
+  version_submitted: v9.1.0
+  categories:
+    - data-retrieval
+    - data-extraction
+    - data-processing-munging
+    - data-visualization
+  editor:
+      name: Tetsuo Koyama
+      github_username: tkoyama010
+  eic:
+      name: Chiara Marmo
+      github_username: cmarmo
+  reviewers:
+    - name: Nicolás Guarín-Zapata
+      github_username: nicoguaro
+    - name: Carter Lee Rhea
+      github_username: crhea93
+  archive: https://zenodo.org/doi/10.5281/zenodo.17202699
+  version_accepted: 9.4.0
+  date_accepted: 2025-9-18
+  created_at: 2024-09-14 22:37:44+00:00
+  updated_at: 2025-11-17 22:40:42+00:00
+  closed_at: 2025-11-17 22:40:18+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/212
+  joss: https://joss.theoj.org/papers/10.21105/joss.09160
+  partners:
+  gh_meta:
+      name: felupe
+      description: finite element analysis for continuum mechanics of solid
+          bodies
+      created_at: '2021-04-22'
+      stargazers_count: 171
+      watchers_count: 4
+      open_issues_count: 4
+      forks_count: 17
+      documentation: https://felupe.readthedocs.io/en/stable
+      contrib_count: 6
+      last_commit: '2026-05-16'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+  active: true
+- package_name: Solar Data Tools
+  package_description: Library of tools for analyzing photovoltaic power
+      time-series data.
+  submitting_author:
+      name: Sara Miskovich
+      github_username: pluflou
+  all_current_maintainers:
+    - name: Sara A. Miskovich
+      github_username: pluflou
+    - name: Bennet Meyers
+      github_username: bmeyers
+  repository_link: https://github.com/slacgismo/solar-data-tools
+  repository_host: github
+  version_submitted: 1.6.4
+  categories:
+    - data-retrieval
+    - data-extraction
+    - data-processing-munging
+    - data-visualization
+  editor:
+      name: Silvana Ovaitt
+      github_username: shirubana
+  eic:
+      name: Chiara Marmo
+      github_username: cmarmo
+  reviewers:
+    - name: Jinning Wang
+      github_username: jinningwang
+    - name: Echedey Luis
+      github_username: echedey-ls
+    - name: Chris Deline
+      github_username: cdeline
+  archive: https://zenodo.org/doi/10.5281/zenodo.15243716
+  version_accepted: 1.7.1
+  date_accepted: '2025-06-13'
+  created_at: 2024-08-17 06:30:02+00:00
+  updated_at: 2025-06-27 21:22:44+00:00
+  closed_at: 2025-06-27 21:22:44+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/210
+  joss: https://joss.theoj.org/papers/10.21105/joss.08478
+  partners:
+  gh_meta:
+      name: solar-data-tools
+      description: 'Some data analysis tools for working with historical PV solar
+          time-series data sets. '
+      created_at: '2019-02-17'
+      stargazers_count: 95
+      watchers_count: 10
+      open_issues_count: 3
+      forks_count: 33
+      documentation: https://solar-data-tools.readthedocs.io
+      contrib_count: 20
+      last_commit: '2026-04-28'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+  active: true
+- package_name: THzTools
+  package_description: Data analysis software tools for terahertz time-domain
+      spectroscopy (THz-TDS)
+  submitting_author:
+      name: J. Steven Dodge
+      github_username: jsdodge
+  all_current_maintainers:
+    - name: J. Steven Dodge
+      github_username: jsdodge
+  repository_link: https://github.com/dodge-research-group/thztools
+  repository_host: github
+  version_submitted: 0.5.4
+  categories:
+    - data-processing-munging
+  editor:
+      name: Bane Sullivan
+      github_username: banesullivan
+  eic:
+      name: Chiara Marmo
+      github_username: cmarmo
+  reviewers:
+    - name: Frank Male
+      github_username: frank1010111
+    - name:
+      github_username: Romain-Peretti
+  archive: https://zenodo.org/doi/10.5281/zenodo.10100093
+  version_accepted: 0.5.5
+  date_accepted: '2024-11-22'
+  created_at: 2024-08-01 11:54:53+00:00
+  updated_at: 2025-03-26 06:49:24+00:00
+  closed_at: 2024-12-03 02:41:20+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/209
+  joss: https://joss.theoj.org/papers/10.21105/joss.07542
+  partners:
+  gh_meta:
+      name: thztools
+      description: Tools for terahertz time-domain spectroscopy (THz-TDS)
+      created_at: '2022-11-22'
+      stargazers_count: 27
+      watchers_count: 2
+      open_issues_count: 3
+      forks_count: 16
+      documentation: https://dodge-research-group.github.io/thztools/
+      contrib_count: 5
+      last_commit: '2024-12-03'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+  active: true
+- package_name: MontePy
+  package_description: MontePy is a python library for reading, editing, and
+      writing MCNP input files.
+  submitting_author:
+      name: Micah Gale
+      github_username: micahgale
+  all_current_maintainers:
+    - name: Micah Gale
+      github_username: micahgale
+    - name: Travis L.
+      github_username: tjlaboss
+  repository_link: https://github.com/idaholab/MontePy
+  repository_host: github
+  version_submitted: 0.2.10
+  categories:
+    - workflow-automation
+    - scientific-software-wrapper
+  editor:
+      name: Kelly L. Rowland
+      github_username: kellyrowland
+  eic:
+      name: Chiara Marmo
+      github_username: cmarmo
+  reviewers:
+    - name: Madicken Munk
+      github_username: munkm
+    - name: Joanna Piper Morgan
+      github_username: jpmorgan98
+  archive: https://zenodo.org/doi/10.5281/zenodo.15185506
+  version_accepted: 0.5.5
+  date_accepted: '2025-03-19'
+  created_at: 2024-07-01 21:04:05+00:00
+  updated_at: 2025-05-20 13:22:25+00:00
+  closed_at: 2025-04-30 19:12:35+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/205
+  joss: https://joss.theoj.org/papers/10.21105/joss.07951
+  partners:
+  gh_meta:
+      name: MontePy
+      description: MontePy is the most user friendly Python library (API) to
+          read, edit, and write MCNP input files.
+      created_at: '2024-01-09'
+      stargazers_count: 62
+      watchers_count: 4
+      open_issues_count: 104
+      forks_count: 20
+      documentation: https://www.montepy.org/
+      contrib_count: 8
+      last_commit: '2026-05-12'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+  active: true
+- package_name: Great Tables
+  package_description: Make awesome display tables using Python.
+  submitting_author:
+      name: Richard Iannone
+      github_username: rich-iannone
+  all_current_maintainers:
+    - name: Richard Iannone
+      github_username: rich-iannone
+    - name: Michael Chow
+      github_username: machow
+  repository_link: https://github.com/posit-dev/great-tables
+  repository_host: github
+  version_submitted: v0.13.0
+  categories:
+    - data-visualization
+  editor:
+      name: Alex Batisse
+      github_username: Batalex
+  eic:
+      name: Alex Batisse
+      github_username: Batalex
+  reviewers:
+    - name:
+      github_username: cjbassin
+    - name: Guillaume Lemaitre
+      github_username: glemaitre
+  archive: https://zenodo.org/doi/10.5281/zenodo.15312934
+  version_accepted: v0.14.0
+  date_accepted: '2025-01-03'
+  created_at: 2024-06-14 19:55:59+00:00
+  updated_at: 2025-07-29 22:16:52+00:00
+  closed_at: 2025-07-29 22:16:20+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/202
+  joss:
+  partners:
+  gh_meta:
+      name: great-tables
+      description: Make awesome display tables using Python
+      created_at: '2022-05-06'
+      stargazers_count: 2658
+      watchers_count: 15
+      open_issues_count: 120
+      forks_count: 125
+      documentation: https://posit-dev.github.io/great-tables/
+      contrib_count: 32
+      last_commit: '2026-05-15'
+  labels:
+    - 6/pyOS-approved
+  active: true
+- package_name: Stingray
+  package_description: A spectral-timing software package for astrophysical
+      X-ray (and other) data
+  submitting_author:
+      name: Matteo Bachetti
+      github_username: matteobachetti
+  all_current_maintainers:
+    - name: Daniela Huppenkothen
+      github_username: dhuppenkothen
+    - name: Guglielmo Mastroserio
+      github_username: mgullik
+    - name: John Swinbank
+      github_username: jdswinbank
+    - name:
+      github_username: matteolucchini1
+  repository_link: https://github.com/stingraysoftware/stingray
+  repository_host: github
+  version_submitted: '2.1'
+  categories:
+    - data-processing-munging
+    - data-validation-testing
+  editor:
+      name: Hans Moritz Günther
+      github_username: hamogu
+  eic:
+      name: Chiara Marmo
+      github_username: cmarmo
+  reviewers:
+    - name: Tom Aldcroft
+      github_username: taldcroft
+    - name: Mason Ng
+      github_username: masonng-astro
+  archive: https://zenodo.org/doi/10.5281/zenodo.11383212
+  version_accepted: '2.1'
+  date_accepted: '2024-10-01'
+  created_at: 2024-06-14 12:59:47+00:00
+  updated_at: 2024-11-23 00:06:34+00:00
+  closed_at: 2024-11-13 00:03:51+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/201
+  joss: https://joss.theoj.org/papers/10.21105/joss.07389
+  partners:
+    - astropy
+  gh_meta:
+      name: stingray
+      description: Anything can happen in the next half hour (including
+          spectral timing made easy)!
+      created_at: '2015-09-30'
+      stargazers_count: 215
+      watchers_count: 17
+      open_issues_count: 44
+      forks_count: 178
+      documentation: https://stingray.science/stingray
+      contrib_count: 58
+      last_commit: '2026-03-16'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+    - astropy
+  active: true
+- package_name: Fluidimage
+  package_description: '"Fluidimage: a Python framework to study flows from images"'
+  submitting_author:
+      name: Pierre Augier
+      github_username: paugier
+  all_current_maintainers:
+    - name: Pierre Augier
+      github_username: paugier
+  repository_link: https://foss.heptapod.net/fluiddyn/fluidimage
+  repository_host: other
+  version_submitted: 0.5.3
+  categories:
+    - data-processing-munging
+    - data-visualization
+  editor:
+      name: Chiara Marmo
+      github_username: cmarmo
+  eic:
+      name: Alex Batisse
+      github_username: Batalex
+  reviewers:
+    - name: Leah Mendelson
+      github_username: leahmendelson
+    - name: Kai Striega
+      github_username: Kai-Striega
+    - name:
+      github_username: emmylia321
+  archive:
+  version_accepted: TBD
+  date_accepted: missing
+  created_at: 2024-05-30 12:53:48+00:00
+  updated_at: 2026-04-27 06:11:55+00:00
+  closed_at: 2026-04-13 20:31:52+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/194
+  joss:
+  partners:
+  gh_meta:
+  labels:
+    - 6/pyOS-approved
+  active: true
+- package_name: astrodata
+  package_description: Common interface for astronomical data products.
+  submitting_author:
+      name: D.J. Teal
+      github_username: teald
+  all_current_maintainers:
+    - name: Teal
+      github_username: teald
+    - name: Chris Simpson
+      github_username: chris-simpson
+    - name:
+      github_username: jehturner
+  repository_link: https://github.com/GeminiDRSoftware/astrodata
+  repository_host: github
+  version_submitted: 2.9.2
+  categories:
+    - data-extraction
+    - data-processing-munging
+  editor:
+      name: Hans Moritz Günther
+      github_username: hamogu
+  eic:
+  reviewers:
+    - name: Aarya Patil
+      github_username: aaryapatil
+    - name: Matt Craig
+      github_username: mwcraig
+  archive: https://zenodo.org/records/14804283
+  version_accepted: 2.10.1
+  date_accepted: '2025-02-04'
+  created_at: 2024-05-13 23:48:03+00:00
+  updated_at: 2025-04-11 19:09:21+00:00
+  closed_at: 2025-04-11 19:09:19+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/181
+  joss:
+  partners:
+    - astropy
+  gh_meta:
+      name: astrodata
+      description:
+      created_at: '2023-10-17'
+      stargazers_count: 1
+      watchers_count: 2
+      open_issues_count: 16
+      forks_count: 3
+      documentation: https://geminidrsoftware.github.io/astrodata/
+      contrib_count: 4
+      last_commit: '2025-04-02'
+  labels:
+    - 6/pyOS-approved
+    - astropy
+  active: true
+- package_name: QuadratiK
+  package_description: QuadratiK includes test for multivariate normality,
+      test for uniformity on the sphere, non-parametric two- and k-sample
+      tests, random generation of points from the Poisson kernel-based density
+      and clustering algorithm for spherical data.
+  submitting_author:
+      name: Raktim Mukhopadhyay
+      github_username: rmj3197
+  all_current_maintainers:
+    - name: Raktim Mukhopadhyay
+      github_username: rmj3197
+    - name: Giovanni Saraceno
+      github_username: giovsaraceno
+  repository_link: https://github.com/rmj3197/QuadratiK
+  repository_host: github
+  version_submitted: 1.1.0
+  categories:
+    - data-processing-munging
+  editor:
+      name: Isabel Zimmerman
+      github_username: isabelizimm
+  eic:
+      name: Alex Batisse
+      github_username: Batalex
+  reviewers:
+    - name: Alyssa Columbus
+      github_username: acolum
+    - name: Avik Basu
+      github_username: ab93
+  archive: https://zenodo.org/records/14546750
+  version_accepted: 1.1.2
+  date_accepted: '2024-12-03'
+  created_at: 2024-05-13 21:23:44+00:00
+  updated_at: 2025-03-17 01:23:41+00:00
+  closed_at: 2025-02-27 20:45:41+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/180
+  joss:
+  partners:
+  gh_meta:
+      name: QuadratiK
+      description: QuadratiK includes test for multivariate normality, test
+          for uniformity on the sphere, non-parametric two- and k-sample
+          tests, random generation of points from the Poisson kernel-based
+          density and clustering algorithm for spherical data.
+      created_at: '2024-02-04'
+      stargazers_count: 3
+      watchers_count: 2
+      open_issues_count: 0
+      forks_count: 0
+      documentation: https://quadratik.readthedocs.io/
+      contrib_count: 1
+      last_commit: '2026-05-01'
+  labels:
+    - 6/pyOS-approved
+  active: true
+- package_name: PyPartMC
+  package_description: Python interface to PartMC aerosol-dynamics Monte-Carlo
+      simulation package
+  submitting_author:
+      name: Sylwester Arabas
+      github_username: slayoo
+  all_current_maintainers:
+    - name: Zach D'Aquino
+      github_username: zdaq12
+    - name: Jeffrey Curtis
+      github_username: jcurtis2
+    - name: Nicole Riemer
+      github_username: nriemer
+    - name: Matthew West
+      github_username: mwest1066
+  repository_link: https://github.com/open-atmos/PyPartMC/
+  repository_host: github
+  version_submitted: v1.2.0
+  categories:
+    - scientific-software-wrapper
+  editor:
+      name: Chiara Marmo
+      github_username: cmarmo
+  eic:
+      name: Alex Batisse
+      github_username: Batalex
+  reviewers:
+    - name: Simon O'Meara
+      github_username: simonom
+    - name: Dan Baston
+      github_username: dbaston
+  archive: https://zenodo.org/doi/10.5281/zenodo.14801138
+  version_accepted: 1.4.2
+  date_accepted: '2025-02-12'
+  created_at: 2024-05-03 18:22:59+00:00
+  updated_at: 2025-02-17 21:44:56+00:00
+  closed_at: 2025-02-17 18:52:18+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/179
+  joss:
+  partners:
+  gh_meta:
+      name: PyPartMC
+      description: Python (and C++) interface to PartMC with Jupyter/Python,
+          Julia and Matlab examples
+      created_at: '2021-10-26'
+      stargazers_count: 31
+      watchers_count: 5
+      open_issues_count: 53
+      forks_count: 16
+      documentation: https://open-atmos.github.io/PyPartMC/
+      contrib_count: 10
+      last_commit: '2026-05-13'
+  labels:
+    - 6/pyOS-approved
+  active: true
+- package_name: CyNetDiff
+  package_description: A performance-focused library implementing algorithms
+      for simulating network diffusion processes, written in Cython.
+  submitting_author:
+      name: Name
+      github_username: eliotwrobson
+  all_current_maintainers:
+    - name: Eliot Robson
+      github_username: eliotwrobson
+    - name: Abhishek Umrawal
+      github_username: abhishekumrawal
+  repository_link: https://github.com/eliotwrobson/CyNetDiff
+  repository_host: github
+  version_submitted: v0.1.13
+  categories:
+    - data-processing-munging
+  editor:
+    - name: Jonny Saunders
+      github_username: sneakers-the-rat
+    - name: Leah Wasser
+      github_username: lwasser
+  eic:
+      name: Alex Batisse
+      github_username: Batalex
+  reviewers:
+    - name: Kai Striega
+      github_username: Kai-Striega
+    - name: SQ
+      github_username: jeremyzhangsq
+  archive:
+  version_accepted: v0.1.18
+  date_accepted: '2025-08-22'
+  created_at: 2024-04-22 03:28:38+00:00
+  updated_at: 2025-09-03 00:17:41+00:00
+  closed_at: 2025-09-03 00:17:41+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/175
+  joss: https://zenodo.org/doi/10.5281/zenodo.10801503
+  partners:
+  gh_meta:
+      name: CyNetDiff
+      description: A performance-focused library implementing algorithms for
+          simulating network diffusion processes, written in Cython.
+      created_at: '2023-12-12'
+      stargazers_count: 6
+      watchers_count: 2
+      open_issues_count: 2
+      forks_count: 1
+      documentation: https://eliotwrobson.github.io/CyNetDiff/
+      contrib_count: 1
+      last_commit: '2025-08-23'
+  labels:
+    - 6/pyOS-approved
+  active: true
+- package_name: AMS
+  package_description: Power system dispatch modeling and dispatch-dynamic
+      co-simulation.
+  submitting_author:
+      name: Jinning Wang
+      github_username: jinningwang
+  all_current_maintainers:
+    - name: Jinning Wang
+      github_username: jinningwang
+  repository_link: https://github.com/CURENT/ams
+  repository_host: github
+  version_submitted: v0.9.6
+  categories:
+    - data-processing-munging
+  editor:
+    - name: Avik Basu
+      github_username: ab93
+    - name: Nima Sarajpoor
+      github_username: NimaSarajpoor
+  eic:
+      name: Alex Batisse
+      github_username: Batalex
+  reviewers:
+    - name: Alireza Gholamzadeh Khoee
+      github_username: Alizak-Mech
+    - name: Alireza Alamgir Tehrani
+      github_username: AlirezaAlamgir
+    - name: Kavian Mashayekhi
+      github_username: Kawians
+  archive: https://zenodo.org/records/17220598
+  version_accepted: v1.0.14
+  date_accepted: '2025-09-07'
+  created_at: 2024-04-22 01:37:56+00:00
+  updated_at: 2025-11-14 21:42:03+00:00
+  closed_at: 2025-11-14 02:04:35+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/174
+  joss:
+  partners:
+  gh_meta:
+      name: ams
+      description: Power system generation scheduling and co-simulation with
+          dynamics.
+      created_at: '2022-10-05'
+      stargazers_count: 24
+      watchers_count: 2
+      open_issues_count: 9
+      forks_count: 9
+      documentation: https://ltb.curent.org
+      contrib_count: 3
+      last_commit: '2026-05-03'
+  labels:
+    - 6/pyOS-approved
+  active: true
+- package_name: pooltool
+  package_description: Pooltool is a general purpose billiards simulator
+      crafted specifically for science and engineering.
+  submitting_author:
+      name: Evan Kiefl
+      github_username: ekiefl
+  all_current_maintainers:
+    - name: Evan Kiefl
+      github_username: ekiefl
+  repository_link: https://github.com/ekiefl/pooltool
+  repository_host: github
+  version_submitted: v0.3.3
+  categories:
+    - data-processing-munging
+    - data-visualization
+  editor:
+      name: Chiara Marmo
+      github_username: cmarmo
+  eic:
+      name: Alex Batisse
+      github_username: Batalex
+  reviewers:
+    - name: Sebastiano Tronto
+      github_username: sebastianotronto
+    - name: Eliot Robson
+      github_username: eliotwrobson
+  archive: https://zenodo.org/doi/10.5281/zenodo.13824503
+  version_accepted: 0.4.1
+  date_accepted: '2024-09-16'
+  created_at: 2024-04-15 21:44:43+00:00
+  updated_at: 2024-11-22 01:30:45+00:00
+  closed_at: 2024-10-01 11:51:34+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/173
+  joss: https://joss.theoj.org/papers/10.21105/joss.07301
+  partners:
+  gh_meta:
+      name: pooltool
+      description: A sandbox billiards game that emphasizes realistic physics
+      created_at: '2020-04-09'
+      stargazers_count: 368
+      watchers_count: 12
+      open_issues_count: 2
+      forks_count: 80
+      documentation: https://pooltool.readthedocs.io
+      contrib_count: 12
+      last_commit: '2026-05-18'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+  active: true
+- package_name: martini
+  package_description: MARTINI is a modular package for the creation of
+      synthetic resolved HI line observations (data cubes) of
+      smoothed-particle hydrodynamics simulations of galaxies.
+  submitting_author:
+      name: Kyle Oman
+      github_username: kyleaoman
+  all_current_maintainers:
+    - name: Kyle Oman
+      github_username: kyleaoman
+  repository_link: https://github.com/kyleaoman/martini
+  repository_host: github
+  version_submitted: 2.0.11 (note JOSS paper is in branch joss-paper, and that
+      branch is somewhat behind main & 2.0.11)
+  categories:
+    - data-processing-munging
+  editor:
+      name: Hans Moritz Günther
+      github_username: hamogu
+  eic:
+      name: Isabel Zimmerman
+      github_username: isabelizimm
+  reviewers:
+    - name: Tom Aldcroft
+      github_username: taldcroft
+    - name: Michele Delli Veneri
+      github_username: MicheleDelliVeneri
+  archive: https://zenodo.org/doi/10.5281/zenodo.11193206
+  version_accepted: 2.0.15
+  date_accepted: '2024-06-03'
+  created_at: 2024-03-06 17:08:29+00:00
+  updated_at: 2025-01-14 18:42:39+00:00
+  closed_at: 2024-07-01 15:58:14+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/164
+  joss: https://joss.theoj.org/papers/10.21105/joss.06860
+  partners:
+    - astropy
+  gh_meta:
+      name: martini
+      description: Mock spatially resolved spectral line observations of
+          simulated galaxies.
+      created_at: '2017-10-19'
+      stargazers_count: 25
+      watchers_count: 1
+      open_issues_count: 14
+      forks_count: 9
+      documentation: https://martini.readthedocs.io/
+      contrib_count: 2
+      last_commit: '2026-05-12'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+    - astropy
+  active: true
+- package_name: ZodiPy
+  package_description: Zodiacal emission simulations in timestreams or HEALPix
+      for solar system observers.
+  submitting_author:
+      name: Metin San
+      github_username: metinsa
+  all_current_maintainers:
+    - name: Metin San
+      github_username: metinsa
+    - name: Duncan Watts
+      github_username: dncnwtts
+    - name: Daniel Herman
+      github_username: hermda02
+  repository_link: https://github.com/Cosmoglobe/zodipy
+  repository_host: github
+  version_submitted: v.0.8.5
+  categories:
+    - scientific-software-wrapper
+  editor:
+      name: Derek Homeier
+      github_username: dhomeier
+  eic:
+      name: Isabel Zimmerman
+      github_username: isabelizimm
+  reviewers:
+    - name: P. L. Lim
+      github_username: pllim
+    - name: Leo Singer
+      github_username: lpsinger
+  archive: https://zenodo.org/doi/10.5281/zenodo.10999612
+  version_accepted: v.0.9.2
+  date_accepted: '2024-04-21'
+  created_at: 2024-02-24 12:28:07+00:00
+  updated_at: 2025-01-14 18:43:28+00:00
+  closed_at: 2024-05-13 17:38:26+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/161
+  joss: https://joss.theoj.org/papers/10.21105/joss.06648
+  partners:
+    - astropy
+  gh_meta:
+      name: zodipy
+      description: 'Astropy-affiliated package for zodiacal light simulations. Maintainers:
+          @metinsa, @hermda02, @dncnwtts'
+      created_at: '2021-08-11'
+      stargazers_count: 13
+      watchers_count: 2
+      open_issues_count: 2
+      forks_count: 12
+      documentation: https://cosmoglobe.github.io/zodipy/
+      contrib_count: 9
+      last_commit: '2026-04-18'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+    - astropy
+  active: true
+- package_name: plot_phylo
+  package_description: A Python package to plot a phylogenetic tree on an
+      existing Matplotlib axis.
+  submitting_author:
+      name: Katy Brown
+      github_username: KatyBrown
+  all_current_maintainers:
+    - name: Katy Brown
+      github_username: KatyBrown
+  repository_link: https://github.com/KatyBrown/plot_phylo
+  repository_host: github
+  version_submitted: 1.9.0
+  categories:
+    - data-visualization
+    - workflow-automation
+  editor:
+      name: C. Titus Brown
+      github_username: ctb
+  eic:
+      name: Isabel Zimmerman
+      github_username: isabelizimm
+  reviewers:
+    - name: Ammar Aziz
+      github_username: ammaraziz
+    - name: Jayaram Kancherla
+      github_username: jkanche
+  archive: https://zenodo.org/doi/10.5281/zenodo.13871592
+  version_accepted: 0.1.11
+  date_accepted: '2025-01-21'
+  created_at: 2024-02-22 11:55:59+00:00
+  updated_at: 2025-03-19 21:22:07+00:00
+  closed_at: 2025-03-19 21:22:05+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/160
+  joss:
+  partners:
+  gh_meta:
+      name: plot_phylo
+      description: Python package to plot a phylogenetic tree on an existing
+          matplotlib axis.
+      created_at: '2023-12-22'
+      stargazers_count: 29
+      watchers_count: 1
+      open_issues_count: 7
+      forks_count: 1
+      documentation: https://plot-phylo.readthedocs.io
+      contrib_count: 1
+      last_commit: '2025-07-21'
+  labels:
+    - 6/pyOS-approved
+  active: true
+- package_name: PetroFit
+  package_description: The PetroFit Project is an open-source effort to
+      develop end-to-end tools for making accurate photometric measurements,
+      estimating morphological properties, and fitting 2D models to galaxy
+      images.
+  submitting_author:
+      name: Robel Geda
+      github_username: robelgeda
+  all_current_maintainers:
+    - name: Robel Geda
+      github_username: robelgeda
+    - name: Steve Crawford
+      github_username: crawfordsm
+  repository_link: https://github.com/PetroFit/petrofit
+  repository_host: github
+  version_submitted: v0.5.0 (will be updated to v1.0.0 after review)
+  categories:
+    - data-processing-munging
+  editor:
+      name: Derek Homeier
+      github_username: dhomeier
+  eic:
+      name: Isabel Zimmerman
+      github_username: isabelizimm
+  reviewers:
+    - name: Nadia Dencheva
+      github_username: nden
+    - name: Kyle Oman
+      github_username: kyleaoman
+  archive: https://zenodo.org/doi/10.5281/zenodo.14962700
+  version_accepted: '[v0.6.0](https://github.com/PetroFit/petrofit/releases/tag/v0.6.0)'
+  date_accepted: '2025-02-28'
+  created_at: 2024-02-16 22:46:47+00:00
+  updated_at: 2025-05-02 11:04:54+00:00
+  closed_at: 2025-05-02 11:04:53+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/159
+  joss:
+  partners:
+    - astropy
+  gh_meta:
+      name: petrofit
+      description: Python package for calculating Petrosian properties and
+          fitting galaxy light profiles
+      created_at: '2021-03-16'
+      stargazers_count: 32
+      watchers_count: 2
+      open_issues_count: 30
+      forks_count: 7
+      documentation: https://petrofit.readthedocs.io
+      contrib_count: 3
+      last_commit: '2025-08-22'
+  labels:
+    - 6/pyOS-approved
+    - astropy
+  active: true
+- package_name: harmonize-wq
+  package_description: Standardize, clean, and wrangle Water Quality Portal
+      data into more analytic-ready formats
+  submitting_author:
+      name: Justin Bousquin
+      github_username: jbousquin
+  all_current_maintainers:
+    - name: Justin Bousquin
+      github_username: jbousquin
+  repository_link: https://github.com/USEPA/harmonize-wq
+  repository_host: github
+  version_submitted: 0.4.0
+  categories:
+    - data-processing-munging
+  editor:
+      name: Alex Batisse
+      github_username: Batalex
+  eic:
+      name: Isabel Zimmerman
+      github_username: isabelizimm
+  reviewers:
+    - name: Romain Caneill
+      github_username: rcaneill
+    - name: Jacqui Levy
+      github_username: jacqui-123
+  archive: https://zenodo.org/doi/10.5281/zenodo.13356847
+  version_accepted: 0.5.0
+  date_accepted: '2024-08-10'
+  created_at: 2024-02-08 19:43:03+00:00
+  updated_at: 2025-02-06 17:12:04+00:00
+  closed_at: 2025-02-06 17:12:02+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/157
+  joss: https://joss.theoj.org/papers/10.21105/joss.07305
+  partners:
+  gh_meta:
+      name: harmonize-wq
+      description: Standardize, clean, and wrangle Water Quality Portal data
+          into more analytic-ready formats
+      created_at: '2022-06-27'
+      stargazers_count: 18
+      watchers_count: 4
+      open_issues_count: 27
+      forks_count: 10
+      documentation: https://usepa.github.io/harmonize-wq/
+      contrib_count: 6
+      last_commit: '2026-05-08'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+  active: true
+- package_name: xnemogcm
+  package_description: Interface to open NEMO global circulation model output
+      dataset with xarray and create a xgcm grid.
+  submitting_author:
+      name: Romain Caneill
+      github_username: rcaneill
+  all_current_maintainers:
+    - name: Romain Caneill
+      github_username: rcaneill
+  repository_link: https://github.com/rcaneill/xnemogcm/
+  repository_host: github
+  version_submitted: 0.4.2
+  categories:
+    - data-processing-munging
+  editor:
+      name: Filipe
+      github_username: ocefpaf
+  eic:
+  reviewers:
+    - name: Paige Martin
+      github_username: paigem
+    - name: Callum Rollo
+      github_username: callumrollo
+  archive: https://zenodo.org/doi/10.5281/zenodo.10973846
+  version_accepted: 0.4.3
+  date_accepted: '2024-04-02'
+  created_at: 2024-01-06 12:33:45+00:00
+  updated_at: 2024-05-02 16:32:24+00:00
+  closed_at: 2024-04-18 10:12:09+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/155
+  joss:
+  partners:
+  gh_meta:
+      name: xnemogcm
+      description: Interface to open NEMO global circulation model output
+          dataset with xarray and create a xgcm grid.
+      created_at: '2020-01-24'
+      stargazers_count: 24
+      watchers_count: 1
+      open_issues_count: 1
+      forks_count: 11
+      documentation: https://xnemogcm.readthedocs.io/
+      contrib_count: 6
+      last_commit: '2026-05-18'
+  labels:
+    - 6/pyOS-approved
+  active: true
+- package_name: automata
+  package_description: A Python library for simulating finite automata,
+      pushdown automata, and Turing machines.
+  submitting_author:
+      name: Eliot Robson
+      github_username: eliotwrobson
+  all_current_maintainers:
+    - name: Eliot Robson
+      github_username: eliotwrobson
+    - name: Caleb Evans
+      github_username: caleb531
+  repository_link: https://github.com/caleb531/automata
+  repository_host: github
+  version_submitted: v8.2.0
+  categories:
+    - data-processing-munging
+    - data-visualization
+  editor:
+      name: Jonny Saunders
+      github_username: sneakers-the-rat
+  eic:
+      name: Isabel Zimmerman
+      github_username: isabelizimm
+  reviewers:
+    - name: Phil Dong
+      github_username: phildong
+    - name: Iris Young
+      github_username: irisdyoung
+    - name: Nima Sarajpoor
+      github_username: NimaSarajpoor
+  archive: https://zenodo.org/doi/10.5281/zenodo.10864492
+  version_accepted: 8.4.0
+      ([repo](https://github.com/caleb531/automata/releases/tag/v8.4.0),
+      [pypi](https://pypi.org/project/automata-lib/8.4.0/),
+      [archive](https://zenodo.org/records/12594180))
+  date_accepted: '2024-06-29'
+  created_at: 2023-12-31 02:23:34+00:00
+  updated_at: 2024-08-01 19:14:28+00:00
+  closed_at: 2024-08-01 19:14:27+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/152
+  joss:
+  partners:
+  gh_meta:
+      name: automata
+      description: A Python library for simulating finite automata, pushdown
+          automata, and Turing machines
+      created_at: '2016-02-16'
+      stargazers_count: 404
+      watchers_count: 7
+      open_issues_count: 10
+      forks_count: 70
+      documentation: https://caleb531.github.io/automata/
+      contrib_count: 19
+      last_commit: '2026-01-02'
+  labels:
+    - 6/pyOS-approved
+  active: true
+- package_name: Plenoptic
+  package_description: a python library for model-based synthesis of
+      perceptual stimuli
+  submitting_author:
+      name: Billy Broderick
+      github_username: billbrod
+  all_current_maintainers:
+    - name: William F. Broderick
+      github_username: billbrod
+  repository_link: https://github.com/plenoptic-org/plenoptic
+  repository_host: github
+  version_submitted: v1.0.2
+  categories:
+  editor:
+      name: Jonny Saunders
+      github_username: sneakers-the-rat
+  eic:
+      name: Jonny Saunders
+      github_username: sneakers-the-rat
+  reviewers:
+    - name: David Nicholson
+      github_username: NickleDave
+    - name: Daniela Pamplona
+      github_username: DanielaPamplona
+    - name:
+      github_username: '2023-12-13'
+  archive:
+  version_accepted: TBD
+  date_accepted: '2026-03-11'
+  created_at: 2023-11-17 20:39:40+00:00
+  updated_at: 2026-05-07 15:36:30+00:00
+  closed_at:
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/150
+  joss:
+  partners:
+  gh_meta:
+      name: plenoptic
+      description: Visualize/test models for visual representation by
+          synthesizing images.
+      created_at: '2019-06-18'
+      stargazers_count: 89
+      watchers_count: 6
+      open_issues_count: 82
+      forks_count: 18
+      documentation: https://docs.plenoptic.org/
+      contrib_count: 18
+      last_commit: '2026-05-18'
+  labels:
+    - 6/pyOS-approved
+  active: true
+- package_name: SLEPLET
+  package_description: Slepian Scale-Discretised Wavelets in Python
+  submitting_author:
+      name: Patrick J. Roddy
+      github_username: paddyroddy
+  all_current_maintainers:
+    - name: Patrick J. Roddy
+      github_username: paddyroddy
+  repository_link: https://github.com/astro-informatics/sleplet
+  repository_host: github
+  version_submitted: '[v1.4.4](https://pypi.org/project/sleplet/1.4.4)'
+  categories:
+    - data-processing-munging
+    - data-visualization
+  editor:
+      name: Szymon Moliński
+      github_username: SimonMolinsky
+  eic:
+      name: David Nicholson
+      github_username: NickleDave
+  reviewers:
+    - name: Shannon Quinn
+      github_username: magsol
+    - name: Jakub Tomasz Gnyp
+      github_username: gnypit
+  archive: https://zenodo.org/doi/10.5281/zenodo.7268074
+  version_accepted: 1.4.7
+  date_accepted: '2024-05-21'
+  created_at: 2023-11-16 01:32:15+00:00
+  updated_at: 2025-01-14 18:45:55+00:00
+  closed_at: 2024-06-06 08:29:04+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/149
+  joss: https://joss.theoj.org/papers/10.21105/joss.05221
+  partners:
+  gh_meta:
+      name: sleplet
+      description: Slepian Scale-Discretised Wavelets in Python
+      created_at: '2020-10-21'
+      stargazers_count: 10
+      watchers_count: 2
+      open_issues_count: 3
+      forks_count: 1
+      documentation: https://pypi.org/project/sleplet
+      contrib_count: 5
+      last_commit: '2026-05-15'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+  active: true
+- package_name: sunpy
+  package_description: Python for Solar Physics
+  submitting_author:
+      name: Nabil Freij
+      github_username: nabobalis
+  all_current_maintainers:
+    - name: Steven Christe
+      github_username: ehsteve
+    - name: David Pérez-Suárez
+      github_username: dpshelio
+    - name: Jack Ireland
+      github_username: wafels
+    - name: Albert Y. Shih
+      github_username: ayshih
+    - name: Stuart Mumford
+      github_username: Cadair
+    - name: Nabil Freij
+      github_username: nabobalis
+    - name: David Stansby
+      github_username: dstansby
+    - name: DanRyanIrish
+      github_username: DanRyanIrish
+    - name: Will Barnes
+      github_username: wtbarnes
+    - name: Conor MacBride
+      github_username: ConorMacBride
+    - name: Alasdair Wilson
+      github_username: alasdairwilson
+    - name: Laura Hayes
+      github_username: hayesla
+    - name: Vishnunarayan K I
+      github_username: vn-ki
+  repository_link: https://github.com/sunpy/sunpy
+  repository_host: github
+  version_submitted: 5.0.1
+  categories:
+    - data-retrieval
+    - data-extraction
+    - data-processing-munging
+    - data-visualization
+  editor:
+      name: Chiara Marmo
+      github_username: cmarmo
+  eic:
+      name: Isabel Zimmerman
+      github_username: isabelizimm
+  reviewers:
+    - name: Septaris/Babouh
+      github_username: Septaris
+    - name: Sean Kelly
+      github_username: nutjob4life
+  archive: https://zenodo.org/record/8384174
+  version_accepted: 5.1.1
+  date_accepted: '2024-01-18'
+  created_at: 2023-10-30 18:45:06+00:00
+  updated_at: 2025-01-14 18:46:34+00:00
+  closed_at: 2024-01-27 23:05:39+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/147
+  joss: https://joss.theoj.org/papers/10.21105/joss.01832
+  partners:
+  gh_meta:
+      name: sunpy
+      description: SunPy - Python for Solar Physics
+      created_at: '2011-08-06'
+      stargazers_count: 1021
+      watchers_count: 45
+      open_issues_count: 237
+      forks_count: 649
+      documentation: https://www.sunpy.org
+      contrib_count: 247
+      last_commit: '2026-05-18'
+  labels:
+    - 6/pyOS-approved
+  active: true
+- package_name: ncompare
+  package_description: '`ncompare` compares two netCDF files at the command line,
+      by generating a report of the matching and non-matching groups, variables,
+      and attributes.'
+  submitting_author:
+      name: Daniel Kaufman
+      github_username: danielfromearth
+  all_current_maintainers:
+    - name: Daniel Kaufman
+      github_username: danielfromearth
+  repository_link: https://github.com/nasa/ncompare
+  repository_host: github
+  version_submitted: 1.4.0
+  categories:
+    - data-validation-testing
+  editor:
+      name: Tom Russell
+      github_username: tomalrussell
+  eic:
+      name: David Nicholson
+      github_username: NickleDave
+  reviewers:
+    - name: Chiara Marmo
+      github_username: cmarmo
+    - name: Michael Tso
+      github_username: cmtso
+  archive: https://zenodo.org/doi/10.5281/zenodo.10625407
+  version_accepted: 1.7.2
+  date_accepted: '2024-02-06'
+  created_at: 2023-10-25 13:12:48+00:00
+  updated_at: 2025-01-14 18:47:21+00:00
+  closed_at: 2024-06-12 15:48:36+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/146
+  joss: https://joss.theoj.org/papers/10.21105/joss.06490
+  partners:
+  gh_meta:
+      name: ncompare
+      description: Compare the structure of two netCDF (or HDF5) files
+      created_at: '2023-08-17'
+      stargazers_count: 31
+      watchers_count: 3
+      open_issues_count: 3
+      forks_count: 9
+      documentation: https://ncompare.readthedocs.io
+      contrib_count: 7
+      last_commit: '2025-12-30'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+  active: true
+- package_name: rdata
+  package_description: Read R datasets from Python.
+  submitting_author:
+      name: Carlos Ramos Carreño
+      github_username: vnmabus
+  all_current_maintainers:
+    - name: Carlos Ramos Carreño
+      github_username: vnmabus
+  repository_link: https://github.com/vnmabus/rdata
+  repository_host: github
+  version_submitted: 0.9.2.dev1
+  categories:
+    - data-processing-munging
+  editor:
+      name: Isabel Zimmerman
+      github_username: isabelizimm
+  eic:
+  reviewers:
+    - name: Richard Iannone
+      github_username: rich-iannone
+    - name: Hassan Kibirige
+      github_username: has2k1
+  archive: https://zenodo.org/doi/10.5281/zenodo.10776842
+  version_accepted: '[0.11.0](https://github.com/vnmabus/rdata/releases/tag/0.11.0)'
+  date_accepted: 2024-2-29
+  created_at: 2023-10-20 08:26:10+00:00
+  updated_at: 2025-02-22 00:24:49+00:00
+  closed_at: 2025-02-21 20:20:59+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/144
+  joss: https://joss.theoj.org/papers/10.21105/joss.07540
+  partners:
+  gh_meta:
+      name: rdata
+      description: A Python library for R datasets.
+      created_at: '2018-07-02'
+      stargazers_count: 57
+      watchers_count: 2
+      open_issues_count: 5
+      forks_count: 3
+      documentation: https://rdata.readthedocs.io
+      contrib_count: 4
+      last_commit: '2026-04-20'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+  active: true
+- package_name: EOmaps
+  package_description: EOmaps is a python package to visualize, analyze and
+      compare geographical datasets.
+  submitting_author:
+      name: Raphael Quast
+      github_username: raphaelquast
+  all_current_maintainers:
+    - name: Raphael Quast
+      github_username: raphaelquast
+  repository_link: https://github.com/raphaelquast/EOmaps
+  repository_host: github
+  version_submitted: '7.3'
+  categories:
+    - data-visualization
+  editor:
+      name: Bane Sullivan
+      github_username: banesullivan
+  eic:
+  reviewers:
+    - name: Lauren Yee
+      github_username: yeelauren
+    - name: Joseph H Kennedy
+      github_username: jhkennedy
+  archive: https://zenodo.org/doi/10.5281/zenodo.10822829
+  version_accepted: 8.0.2
+  date_accepted: '2024-03-14'
+  created_at: 2023-09-26 12:14:47+00:00
+  updated_at: 2024-03-20 06:03:26+00:00
+  closed_at: 2024-03-20 05:56:50+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/138
+  joss:
+  partners:
+  gh_meta:
+      name: EOmaps
+      description: A library to create interactive maps of geographical
+          datasets
+      created_at: '2021-09-27'
+      stargazers_count: 362
+      watchers_count: 4
+      open_issues_count: 10
+      forks_count: 27
+      documentation: https://eomaps.readthedocs.io/
+      contrib_count: 9
+      last_commit: '2026-01-21'
+  labels:
+    - 6/pyOS-approved
+  active: true
+- package_name: sourmash
+  package_description: '`sourmash` is a command line tool and Python library for
+      sketching collections of DNA, RNA, and amino acid k-mers for biological sequence
+      search, comparison, and analysis.'
+  submitting_author:
+      name: Tessa Pierce-Ward
+      github_username: bluegenes
+  all_current_maintainers:
+    - name: C. Titus Brown
+      github_username: ctb
+    - name: Luiz Irber
+      github_username: luizirber
+    - name: Tessa Pierce Ward
+      github_username: bluegenes
+  repository_link: https://github.com/sourmash-bio/sourmash
+  repository_host: github
+  version_submitted: '4.8'
+  categories:
+    - data-processing-munging
+  editor:
+      name: Emily Jane McTavish
+      github_username: snacktavish
+  eic:
+  reviewers:
+    - name: Lili Andersson-Li
+      github_username: LilyAnderssonLee
+    - name: Elais Player
+      github_username: elais
+  archive: https://zenodo.org/doi/10.5281/zenodo.10951577
+  version_accepted: '[v4.8.8](https://github.com/sourmash-bio/sourmash/releases/tag/v4.8.8)'
+  date_accepted: 2024-4-4
+  created_at: 2023-08-14 21:02:57+00:00
+  updated_at: 2024-11-23 00:44:05+00:00
+  closed_at: 2024-07-22 20:13:57+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/129
+  joss: https://joss.theoj.org/papers/10.21105/joss.06830
+  partners:
+  gh_meta:
+      name: sourmash
+      description: Quickly search, compare, and analyze genomic and
+          metagenomic data sets.
+      created_at: '2016-04-09'
+      stargazers_count: 542
+      watchers_count: 17
+      open_issues_count: 769
+      forks_count: 92
+      documentation: https://sourmash.readthedocs.io/en/latest/
+      contrib_count: 46
+      last_commit: '2026-05-18'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+  active: true
+- package_name: Sciform
+  package_description: A package for converting python numbers (floats,
+      Decimals) into scientific-formatted strings more suitable for reading
+      and presentation.
+  submitting_author:
+      name: Justin Gerber
+      github_username: jagerber48
+  all_current_maintainers:
+    - name: Justin Gerber
+      github_username: jagerber48
+  repository_link: https://github.com/jagerber48/sciform
+  repository_host: github
+  version_submitted: 0.24.0
+  categories:
+    - data-visualization
+  editor:
+      name: Alex Batisse
+      github_username: Batalex
+  eic:
+  reviewers:
+    - name: Isabel Zimmerman
+      github_username: isabelizimm
+    - name: Michael Chow
+      github_username: machow
+  archive: https://zenodo.org/doi/10.5281/zenodo.10645273
+  version_accepted: 0.34.1
+  date_accepted: '2024-02-07'
+  created_at: 2023-07-21 04:41:08+00:00
+  updated_at: 2024-05-02 17:46:01+00:00
+  closed_at: 2024-05-02 16:42:00+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/121
+  joss:
+  partners:
+  gh_meta:
+      name: sciform
+      description: A package for formatting numbers into scientific formatted
+          strings.
+      created_at: '2023-05-26'
+      stargazers_count: 17
+      watchers_count: 1
+      open_issues_count: 8
+      forks_count: 2
+      documentation: https://sciform.readthedocs.io/en/stable/
+      contrib_count: 2
+      last_commit: '2025-09-11'
+  labels:
+    - 6/pyOS-approved
+  active: true
+- package_name: astartes
+  package_description: Better Data Splits for Machine Learning
+  submitting_author:
+      name: Jackson Burns
+      github_username: JacksonBurns
+  all_current_maintainers:
+    - name: Kevin Spiekermann
+      github_username: kspieks
+    - name: Himaghna Bhattacharjee
+      github_username: himaghna
+  repository_link: https://github.com/JacksonBurns/astartes
+  repository_host: github
+  version_submitted:
+      v[1.1.2](https://github.com/JacksonBurns/astartes/releases/tag/v1.1.2)
+  categories:
+    - data-processing-munging
+  editor:
+      name: Chiara Marmo
+      github_username: cmarmo
+  eic:
+  reviewers:
+    - name: Beryl Kanali
+      github_username: BerylKanali
+    - name: Du Phan
+      github_username: du-phan
+  archive: https://zenodo.org/record/8431894
+  version_accepted:
+      v[1.1.3](https://github.com/JacksonBurns/astartes/releases/tag/v1.1.3)
+  date_accepted: '2023-10-15'
+  created_at: 2023-07-10 22:12:51+00:00
+  updated_at: 2025-02-01 17:50:10+00:00
+  closed_at: 2023-11-12 21:12:16+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/120
+  joss: https://joss.theoj.org/papers/10.21105/joss.05996
+  partners:
+  gh_meta:
+      name: astartes
+      description: Better Data Splits for Machine Learning
+      created_at: '2022-04-22'
+      stargazers_count: 101
+      watchers_count: 2
+      open_issues_count: 7
+      forks_count: 6
+      documentation: https://jacksonburns.github.io/astartes/
+      contrib_count: 3
+      last_commit: '2025-09-30'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+  active: true
+- package_name: XGI
+  package_description: XGI is a Python package for higher-order networks.
+  submitting_author:
+      name: Nicholas Landry
+      github_username: nwlandry
+  all_current_maintainers:
+    - name: Nicholas Landry
+      github_username: nwlandry
+    - name: Leo Torres
+      github_username: leotrs
+    - name: Maxime Lucas
+      github_username: maximelucas
+    - name: Iacopo Iacopini
+      github_username: iaciac
+    - name: Giovanni Petri
+      github_username: lordgrilo
+    - name: Alice Schwarze
+      github_username: acuschwarze
+    - name: Thomas Robiglio
+      github_username: thomasrobiglio
+    - name: Alice Patania
+      github_username: alpatania
+  repository_link: https://github.com/xgi-org/xgi
+  repository_host: github
+  version_submitted: '0.7'
+  categories:
+    - data-retrieval
+    - data-processing-munging
+    - data-visualization
+  editor:
+      name: Szymon Moliński
+      github_username: SimonMolinsky
+  eic:
+  reviewers:
+    - name: Nhat Jonny Tran
+      github_username: JonnyTran
+    - name: Marta Leszczyńska
+      github_username: Reckony
+  archive: https://zenodo.org/record/8365068
+  version_accepted: 0.7.4
+  date_accepted: '2023-09-23'
+  created_at: 2023-06-08 16:15:32+00:00
+  updated_at: 2025-02-01 17:51:41+00:00
+  closed_at: 2023-10-23 07:38:27+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/115
+  joss: https://joss.theoj.org/papers/10.21105/joss.05162
+  partners:
+  gh_meta:
+      name: xgi
+      description: CompleX Group Interactions (XGI) is a Python package for
+          higher-order networks.
+      created_at: '2021-09-08'
+      stargazers_count: 248
+      watchers_count: 9
+      open_issues_count: 53
+      forks_count: 47
+      documentation: https://xgi.readthedocs.io
+      contrib_count: 21
+      last_commit: '2026-05-16'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+  active: true
+- package_name: biocypher
+  package_description: framework for creating biomedical knowledge graphs
+  submitting_author:
+      name: Sebastian Lobentanzer
+      github_username: slobentanzer
+  all_current_maintainers:
+    - name: Sebastian Lobentanzer
+      github_username: slobentanzer
+  repository_link: https://github.com/biocypher/biocypher
+  repository_host: github
+  version_submitted: 0.5.14
+  categories:
+    - data-retrieval
+    - data-extraction
+    - data-processing-munging
+    - data-deposition
+    - data-validation-testing
+    - workflow-automation
+    - database-interoperability
+  editor:
+      name: Ariane Sasso
+      github_username: arianesasso
+  eic:
+  reviewers:
+    - name: Lukas Heumos
+      github_username: Zethson
+    - name: Moritz E. Beber
+      github_username: Midnighter
+    - name:
+      github_username: Sinna
+  archive: https://zenodo.org/doi/10.5281/zenodo.10158204
+  version_accepted: v0.5.33
+  date_accepted: '2023-11-14'
+  created_at: 2023-05-04 18:08:32+00:00
+  updated_at: 2023-12-14 23:29:54+00:00
+  closed_at: 2023-11-28 18:03:51+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/110
+  joss:
+  partners:
+  gh_meta:
+      name: biocypher
+      description: A unifying framework for biomedical research knowledge
+          graphs
+      created_at: '2021-09-10'
+      stargazers_count: 304
+      watchers_count: 8
+      open_issues_count: 179
+      forks_count: 51
+      documentation: https://biocypher.org
+      contrib_count: 20
+      last_commit: '2026-05-09'
+  labels:
+    - 6/pyOS-approved
+  active: true
+- package_name: cardsort
+  package_description: A python package to analyse data from open card sorting
+      tasks
+  submitting_author:
+      name: Katharina Kloppenborg
+      github_username: katoss
+  all_current_maintainers:
+    - name: Katharina Kloppenborg
+      github_username: katoss
+  repository_link: https://github.com/katoss/cardsort
+  repository_host: github
+  version_submitted: '[0.2.2](https://github.com/katoss/cardsort/releases/tag/v0.2.2)'
+  categories:
+    - data-extraction
+    - data-processing-munging
+    - data-visualization
+  editor:
+      name: Alex Batisse
+      github_username: Batalex
+  eic:
+  reviewers:
+    - name: Semidán Robaina
+      github_username: Robaina
+    - name:
+      github_username: khynder
+  archive: https://zenodo.org/record/8214655
+  version_accepted: v
+      [0.2.36](https://github.com/katoss/cardsort/releases/tag/v0.2.36)
+  date_accepted: '2023-08-16'
+  created_at: 2023-04-20 11:29:27+00:00
+  updated_at: 2023-12-13 10:40:37+00:00
+  closed_at: 2023-08-23 08:21:12+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/102
+  joss:
+  partners:
+  gh_meta:
+      name: cardsort
+      description: A python package to analyse cardsorting data from
+          kardsort.com outputs.
+      created_at: '2023-03-16'
+      stargazers_count: 8
+      watchers_count: 2
+      open_issues_count: 0
+      forks_count: 2
+      documentation: https://cardsort.readthedocs.io
+      contrib_count: 4
+      last_commit: '2025-04-15'
+  labels:
+    - 6/pyOS-approved
+  active: true
+- package_name: afscgap
+  package_description: Community contributed Python-based tools for working
+      with public bottom trawl surveys data from the NOAA Alaska Fisheries
+      Science Center Groundfish Assessment Program ([NOAA AFSC
+      GAP](https://www.fisheries.noaa.gov/contact/groundfish-assessment-program)).
+  submitting_author:
+      name: Sam Pottinger
+      github_username: sampottinger
+  all_current_maintainers:
+    - name: A Samuel Pottinger
+      github_username: sampottinger
+    - name: Giulia Zarpellon
+      github_username: gizarp
+  repository_link: https://github.com/SchmidtDSE/afscgap
+  repository_host: github
+  version_submitted: 0.0.7
+  categories:
+    - data-retrieval
+    - data-processing-munging
+    - data-visualization
+  editor:
+      name: Filipe
+      github_username: ocefpaf
+  eic:
+  reviewers:
+    - name: Tylar
+      github_username: 7yl4r
+    - name: Ayush Anand
+      github_username: ayushanand18
+  archive: https://zenodo.org/badge/latestdoi/603308264
+  version_accepted: 0.0.7
+  date_accepted: '2023-05-30'
+  created_at: 2023-03-25 00:27:27+00:00
+  updated_at: 2023-08-29 02:15:31+00:00
+  closed_at: 2023-06-28 19:06:00+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/93
+  joss: https://joss.theoj.org/papers/10.21105/joss.05593
+  partners:
+  gh_meta:
+      name: afscgap
+      description: Python-based tools for NOAA AFSC GAP marine species surveys
+          data
+      created_at: '2023-02-18'
+      stargazers_count: 5
+      watchers_count: 3
+      open_issues_count: 2
+      forks_count: 4
+      documentation: https://pyafscgap.org
+      contrib_count: 3
+      last_commit: '2026-02-05'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+  active: true
+- package_name: taxpasta
+  package_description: TAXonomic Profile Aggregation and STAndardisation
+  submitting_author:
+      name: Moritz E. Beber
+      github_username: Midnighter
+  all_current_maintainers:
+    - name: Moritz E. Beber
+      github_username: Midnighter
+    - name: Sofia Stamouli
+      github_username: sofstam
+    - name: James A. Fellows Yates
+      github_username: jfy133
+  repository_link: https://github.com/taxprofiler/taxpasta
+  repository_host: github
+  version_submitted: 0.2.1
+  categories:
+    - data-processing-munging
+  editor:
+      name: C. Titus Brown
+      github_username: ctb
+  eic:
+  reviewers:
+    - name: Emily Jane McTavish
+      github_username: snacktavish
+    - name: Tessa Pierce Ward
+      github_username: bluegenes
+  archive: https://github.com/taxprofiler/taxpasta/releases/tag/0.4.0
+  version_accepted: 0.4.0
+  date_accepted: '2023-07-05'
+  created_at: 2023-03-02 16:50:50+00:00
+  updated_at: 2023-12-13 10:49:10+00:00
+  closed_at: 2023-07-12 14:22:46+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/84
+  joss: https://joss.theoj.org/papers/10.21105/joss.05627
+  partners:
+  gh_meta:
+      name: taxpasta
+      description: TAXnomic Profile Aggregation and STAndardisation
+      created_at: '2022-06-03'
+      stargazers_count: 44
+      watchers_count: 4
+      open_issues_count: 17
+      forks_count: 8
+      documentation: https://taxpasta.readthedocs.io/
+      contrib_count: 5
+      last_commit: '2025-08-19'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+  active: true
+- package_name: bibat
+  package_description: An interactive template for Bayesian statistical
+      analysis projects
+  submitting_author:
+      name: Teddy Groves
+      github_username: teddygroves
+  all_current_maintainers:
+    - name: Teddy Groves
+      github_username: teddygroves
+  repository_link: https://github.com/teddygroves/bibat/
+  repository_host: github
+  version_submitted: 0.1.0
+  categories:
+    - workflow-automation
+  editor:
+      name: Meenal Jhajharia
+      github_username: mjhajharia
+  eic:
+  reviewers:
+    - name: Oriol Abril-Pla
+      github_username: OriolAbril
+    - name: Alexey Izmailov
+      github_username: alizma
+  archive: https://zenodo.org/record/8124312
+  version_accepted: 0.1.10
+  date_accepted: '2023-07-05'
+  created_at: 2023-03-01 14:16:51+00:00
+  updated_at: 2023-12-14 23:37:44+00:00
+  closed_at: 2023-12-13 22:30:02+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/83
+  joss:
+  partners:
+  gh_meta:
+      name: bibat
+      description: A batteries-included template for Bayesian data analysis
+          projects
+      created_at: '2021-03-04'
+      stargazers_count: 22
+      watchers_count: 1
+      open_issues_count: 13
+      forks_count: 2
+      documentation: https://bibat.readthedocs.io/
+      contrib_count: 1
+      last_commit: '2024-04-10'
+  labels:
+    - 6/pyOS-approved
+  active: true
+- package_name: Python-graphblas
+  package_description: 'Python library for GraphBLAS: high-performance sparse linear
+      algebra for scalable graph analytics'
+  submitting_author:
+      name: Erik Welch
+      github_username: eriknw
+  all_current_maintainers:
+    - name: Erik Welch
+      github_username: eriknw
+    - name: Jim Kitchen
+      github_username: jim22k
+    - name: Sultan Orazbayev
+      github_username: SultanOrazbayev
+  repository_link: https://github.com/python-graphblas/python-graphblas
+  repository_host: github
+  version_submitted: 2023.1.0
+  categories:
+    - data-munging
+    - scientific-software-wrapper
+  editor:
+      name: Tom Russell
+      github_username: tomalrussell
+  eic:
+  reviewers:
+    - name: Jonny Saunders
+      github_username: sneakers-the-rat
+    - name: Szabolcs Horvát
+      github_username: szhorvat
+  archive: https://zenodo.org/record/8125660
+  version_accepted: 2023.7.0
+  date_accepted: '2023-07-14'
+  created_at: 2023-02-04 23:07:20+00:00
+  updated_at: 2024-03-12 17:32:53+00:00
+  closed_at: 2023-07-27 17:48:29+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/81
+  joss:
+  partners:
+  gh_meta:
+      name: python-graphblas
+      description: 'Python library for GraphBLAS: high-performance sparse linear
+          algebra for scalable graph analytics'
+      created_at: '2019-11-11'
+      stargazers_count: 155
+      watchers_count: 9
+      open_issues_count: 55
+      forks_count: 16
+      documentation: https://python-graphblas.readthedocs.io/en/stable/
+      contrib_count: 11
+      last_commit: '2026-04-22'
+  labels:
+    - 6/pyOS-approved
+  active: true
+- package_name: xclim
+  package_description: Climate indices computation package based on Xarray
+  submitting_author:
+      name: Trevor James Smith
+      github_username: Zeitsperre
+  all_current_maintainers:
+    - name: Trevor James Smith
+      github_username: Zeitsperre
+    - name: Travis Logan
+      github_username: tlogan2000
+    - name: Pascal Bourgault
+      github_username: aulemahal
+  repository_link: https://github.com/Ouranosinc/xclim
+  repository_host: github
+  version_submitted: v0.40.0
+  categories:
+    - data-munging
+    - reproducibility
+    - geospatial
+  editor:
+      name: Alex Batisse
+      github_username: Batalex
+  eic:
+  reviewers:
+    - name: James Munroe
+      github_username: jmunroe
+    - name: Agustina
+      github_username: aguspesce
+  archive: https://zenodo.org/badge/latestdoi/142608764
+  version_accepted: v0.42.0
+  date_accepted: '2023-04-11'
+  created_at: 2023-01-16 16:59:20+00:00
+  updated_at: 2023-09-18 22:18:20+00:00
+  closed_at: 2023-05-22 04:04:53+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/73
+  joss: https://joss.theoj.org/papers/10.21105/joss.05415
+  partners:
+  gh_meta:
+      name: xclim
+      description: 'Library of derived climate variables, ie climate indicators,
+          based on xarray. '
+      created_at: '2018-07-27'
+      stargazers_count: 395
+      watchers_count: 13
+      open_issues_count: 41
+      forks_count: 70
+      documentation: https://xclim.readthedocs.io/en/stable/
+      contrib_count: 45
+      last_commit: '2026-05-15'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+    - Pangeo
+  active: true
+- package_name: crowsetta
+  package_description: A Python tool to work with any format for annotating
+      animal vocalizations and bioacoustics data.
+  submitting_author:
+      name: David Nicholson
+      github_username: NickleDave
+  all_current_maintainers:
+    - name: David Nicholson
+      github_username: NickleDave
+  repository_link: https://github.com/vocalpy/crowsetta
+  repository_host: github
+  version_submitted: '[4.0.0.post2](https://github.com/vocalpy/crowsetta/releases/tag/4.0.0.post2)'
+  categories:
+    - data-extraction
+    - data-munging
+    - reproducibility
+  editor:
+      name: Chiara Marmo
+      github_username: cmarmo
+  eic:
+  reviewers:
+    - name: Tessa Rhinehart
+      github_username: rhine3
+    - name: Sylvain HAUPERT
+      github_username: shaupert
+  archive: https://zenodo.org/badge/latestdoi/159904494
+  version_accepted: v
+      [5.0](https://github.com/vocalpy/crowsetta/releases/tag/5.0.0)
+  date_accepted: '2023-03-28'
+  created_at: 2023-01-03 19:39:16+00:00
+  updated_at: 2024-11-21 00:50:18+00:00
+  closed_at: 2023-04-13 20:26:00+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/68
+  joss: https://joss.theoj.org/papers/10.21105/joss.05338
+  partners:
+  gh_meta:
+      name: crowsetta
+      description: A tool to work with any format for annotating animal sounds
+      created_at: '2018-12-01'
+      stargazers_count: 62
+      watchers_count: 1
+      open_issues_count: 41
+      forks_count: 4
+      documentation: https://crowsetta.readthedocs.io/en/latest/
+      contrib_count: 2
+      last_commit: '2025-12-16'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+  active: true
+- package_name: Pynteny
+  package_description: Query sequence database by HMMs arranged in predefined
+      synteny structure
+  submitting_author:
+      name: Semidán Robaina
+      github_username: Robaina
+  all_current_maintainers:
+    - name: Semidán Robaina
+      github_username: Robaina
+  repository_link: https://github.com/Robaina/Pynteny
+  repository_host: github
+  version_submitted: v0.0.5
+  categories:
+    - data-retrieval
+    - data-extraction
+    - education
+  editor:
+      name: Ariane Sasso
+      github_username: arianesasso
+  eic:
+  reviewers:
+    - name: Alex Batisse
+      github_username: Batalex
+    - name: Corinna Thoben
+      github_username: c-thoben
+  archive: https://zenodo.org/record/7696204
+  version_accepted: 1.0.0
+  date_accepted: '2023-03-10'
+  created_at: 2022-12-16 22:02:53+00:00
+  updated_at: 2023-08-29 01:32:03+00:00
+  closed_at: 2023-04-12 20:48:15+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/67
+  joss: https://joss.theoj.org/papers/10.21105/joss.05289
+  partners:
+  gh_meta:
+      name: Pynteny
+      description: Query sequence database by HMMs arranged in predefined
+          synteny structure
+      created_at: '2022-06-06'
+      stargazers_count: 14
+      watchers_count: 1
+      open_issues_count: 1
+      forks_count: 1
+      documentation: https://robaina.github.io/Pynteny
+      contrib_count: 2
+      last_commit: '2026-04-01'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+  active: true
+- package_name: Jointly
+  package_description: Jointly is a python package for synchronizing sensors
+      with accelerometer data
+  submitting_author:
+      name: Arne Herdick
+      github_username: enra64
+  all_current_maintainers:
+    - name: Arne
+      github_username: enra64
+    - name: Ariane Sasso
+      github_username: arianesasso
+  repository_link: https://github.com/hpi-dhc/jointly
+  repository_host: github
+  version_submitted: 1.0.2
+  categories:
+    - data-munging
+  editor:
+      name: Ivan Ogasawara
+      github_username: xmnlab
+  eic:
+  reviewers:
+    - name: Álex Sáez
+      github_username: AlexS12
+    - name: K. Arthur Endsley
+      github_username: arthur-e
+  archive: https://zenodo.org/badge/latestdoi/303936309
+  version_accepted: 1.0.3
+  date_accepted: '2021-12-29'
+  created_at: 2021-08-31 12:58:45+00:00
+  updated_at: 2023-08-29 02:01:15+00:00
+  closed_at: 2022-01-12 18:45:20+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/45
+  joss:
+  partners:
+  gh_meta:
+      name: jointly
+      description: 'Jointly: A Python package for synchronizing sensors with accelerometer
+          data'
+      created_at: '2020-10-14'
+      stargazers_count: 11
+      watchers_count: 3
+      open_issues_count: 0
+      forks_count: 1
+      documentation: https://jointly.readthedocs.io/
+      contrib_count: 5
+      last_commit: '2022-01-11'
+  labels:
+    - 6/pyOS-approved
+  active: true
+- package_name: PyGMT
+  package_description: A Python interface for the Generic Mapping Tools
+  submitting_author:
+      name: Wei Ji Leong
+      github_username: weiji14
+  all_current_maintainers:
+    - name: Wei Ji
+      github_username: weiji14
+    - name: Dongdong Tian
+      github_username: seisman
+    - name: Max Jones
+      github_username: maxrjones
+    - name: Michael Grund
+      github_username: michaelgrund
+    - name: Will Schlitzer
+      github_username: willschlitzer
+    - name: Yvonne Fröhlich
+      github_username: yvonnefroehlich
+  repository_link: https://github.com/GenericMappingTools/pygmt
+  repository_host: github
+  version_submitted:
+  categories:
+    - data-munging
+    - data-visualization
+    - geospatial
+  editor:
+      name: Leah Wasser
+      github_username: lwasser
+  eic:
+  reviewers:
+    - name: Julius Busecke
+      github_username: jbusecke
+    - name: Szymon Moliński
+      github_username: simonmolinsky
+  archive: https://zenodo.org/record/6702566
+  version_accepted: V 0.7.0
+  date_accepted: 2022-9-1
+  created_at: 2021-07-23 00:37:07+00:00
+  updated_at: 2024-12-15 05:27:30+00:00
+  closed_at: 2023-06-12 22:47:16+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/43
+  joss:
+  partners:
+  gh_meta:
+      name: pygmt
+      description: A Python interface for the Generic Mapping Tools.
+      created_at: '2017-03-17'
+      stargazers_count: 859
+      watchers_count: 25
+      open_issues_count: 120
+      forks_count: 235
+      documentation: https://www.pygmt.org
+      contrib_count: 51
+      last_commit: '2026-05-18'
+  labels:
+    - 6/pyOS-approved
+  active: true
+- package_name: Devicely
+  package_description: A Python package for reading, timeshifting and writing
+      sensor data
+  submitting_author:
+      name: Ariane Sasso
+      github_username: arianesasso
+  all_current_maintainers:
+    - name: Ariane Sasso
+      github_username: arianesasso
+  repository_link: https://github.com/hpi-dhc/devicely
+  repository_host: github
+  version_submitted: 0.2.5
+  categories:
+    - data-munging
+  editor:
+      name: Ivan Ogasawara
+      github_username: xmnlab
+  eic:
+  reviewers:
+    - name: Carol Willing
+      github_username: willingc
+    - name: Robert Guggenberger
+      github_username: agricolab
+  archive: https://zenodo.org/badge/latestdoi/279395106
+  version_accepted: v1.1.1
+  date_accepted: '2021-08-19'
+  created_at: 2021-04-03 19:25:41+00:00
+  updated_at: 2023-08-29 02:06:23+00:00
+  closed_at: 2022-09-07 15:40:27+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/37
+  joss: https://joss.theoj.org/papers/10.21105/joss.03679
+  partners:
+  gh_meta:
+      name: devicely
+      description: 'Devicely: A Python package for reading, timeshifting and writing
+          sensor data'
+      created_at: '2020-07-13'
+      stargazers_count: 16
+      watchers_count: 4
+      open_issues_count: 1
+      forks_count: 8
+      documentation: https://hpi-dhc.github.io/devicely/
+      contrib_count: 4
+      last_commit: '2021-12-21'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+  active: true
+- package_name: openomics
+  package_description: Library for integration of multi-omics, annotation, and
+      interaction data
+  submitting_author:
+      name: Jonny Tran
+      github_username: JonnyTran
+  all_current_maintainers:
+    - name: Nhat (Jonny) Tran
+      github_username: JonnyTran
+  repository_link: https://github.com/JonnyTran/OpenOmics
+  repository_host: github
+  version_submitted: '[0.8.4](https://github.com/JonnyTran/OpenOmics/releases/tag/v0.8.4)'
+  categories:
+    - data-retrieval
+    - data-extraction
+    - data-munging
+    - reproducibility
+  editor:
+      name: David Nicholson
+      github_username: NickleDave
+  eic:
+  reviewers:
+    - name: Steve Moss
+      github_username: gawbul
+    - name: Katharina Sielemann
+      github_username: ksielemann
+  archive: https://zenodo.org/record/4731011
+  version_accepted: v
+      [0.8.8](https://github.com/JonnyTran/OpenOmics/releases/tag/v0.8.8)
+  date_accepted: '2021-04-17'
+  created_at: 2021-01-01 19:54:20+00:00
+  updated_at: 2023-11-09 17:53:10+00:00
+  closed_at: 2021-05-10 17:48:02+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/31
+  joss: https://joss.theoj.org/papers/10.21105/joss.03249
+  partners:
+  gh_meta:
+      name: OpenOmics
+      description: A bioinformatics API to interface with public multi-omics
+          bio databases for wicked fast data integration.
+      created_at: '2018-03-16'
+      stargazers_count: 36
+      watchers_count: 4
+      open_issues_count: 6
+      forks_count: 10
+      documentation: https://openomics.readthedocs.io/en/latest/
+      contrib_count: 8
+      last_commit: '2024-05-15'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+  active: true
+- package_name: Physcraper
+  package_description: Automated phylogenetic updating
+  submitting_author:
+      name: Emily Jane McTavish
+      github_username: snacktavish
+  all_current_maintainers:
+    - name: Emily Jane McTavish
+      github_username: snacktavish
+    - name: Luna L. Sanchez Reyes
+      github_username: LunaSare
+  repository_link: https://github.com/McTavishLab/physcraper
+  repository_host: github
+  version_submitted: '[0.55](https://github.com/McTavishLab/physcraper/releases/tag/0.55)'
+  categories:
+    - data-retrieval
+    - data-munging
+  editor:
+      name: David Nicholson
+      github_username: NickleDave
+  eic:
+  reviewers:
+    - name: Boas Pucker
+      github_username: bpucker
+    - name: Leonardo de Oliveira Martins
+      github_username: leomrtns
+  archive: https://zenodo.org/record/5512990
+  version_accepted: v
+      [1.0](https://github.com/McTavishLab/physcraper/releases/tag/v1.0.0)
+  date_accepted: '2021-09-14'
+  created_at: 2020-07-15 22:31:52+00:00
+  updated_at: 2023-09-09 19:52:35+00:00
+  closed_at: 2021-09-18 01:07:07+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/26
+  joss:
+  partners:
+  gh_meta:
+      name: physcraper
+      description: Welcome to Physcraper’s repository! Automatic gene tree
+          updating using the Open Tree of Life.
+      created_at: '2015-08-24'
+      stargazers_count: 13
+      watchers_count: 6
+      open_issues_count: 36
+      forks_count: 5
+      documentation: https://physcraper.readthedocs.io/en/main/
+      contrib_count: 5
+      last_commit: '2022-05-13'
+  labels:
+    - 6/pyOS-approved
+  active: true
+- package_name: pystiche
+  package_description: Framework for Neural Style Transfer (NST) built upon
+      PyTorch
+  submitting_author:
+      name: Philip Meier
+      github_username: pmeier
+  all_current_maintainers:
+    - name: Philip Meier
+      github_username: pmeier
+  repository_link: https://github.com/pystiche/pystiche
+  repository_host: github
+  version_submitted: '[0.5.0post0](https://github.com/pystiche/pystiche/releases/tag/v0.5.0.post0)'
+  categories:
+    - reproducibility
+  editor:
+      name: David Nicholson
+      github_username: NickleDave
+  eic:
+  reviewers:
+    - name: Edgar Riba
+      github_username: edgarriba
+    - name: Soumith Chintala
+      github_username: soumith
+  archive: https://zenodo.org/record/4073515
+  version_accepted: v
+      [0.6.0](https://github.com/pystiche/pystiche/releases/tag/v0.6.0)
+  date_accepted: '2020-10-08'
+  created_at: 2020-07-02 12:57:08+00:00
+  updated_at: 2023-11-08 23:49:27+00:00
+  closed_at: 2020-10-14 16:05:10+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/25
+  joss: https://joss.theoj.org/papers/10.21105/joss.02761
+  partners:
+  gh_meta:
+      name: pystiche
+      description: Framework for Neural Style Transfer (NST) built upon
+          PyTorch
+      created_at: '2019-09-16'
+      stargazers_count: 274
+      watchers_count: 9
+      open_issues_count: 11
+      forks_count: 24
+      documentation:
+      contrib_count: 10
+      last_commit: '2022-03-18'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+  active: true
+- package_name: phenopype
+  package_description: a phenotyping pipeline for Python
+  submitting_author:
+      name: Moritz Lürig
+      github_username: mluerig
+  all_current_maintainers:
+    - name: Moritz Lürig
+      github_username: mluerig
+  repository_link: https://github.com/phenopype/phenopype
+  repository_host: github
+  version_submitted: 1.0.5
+  categories:
+    - data-extraction
+    - reproducibility
+  editor:
+      name: Ben Cook
+      github_username: jbencook
+  eic:
+  reviewers:
+    - name: Arthur Porto
+      github_username: agporto
+    - name: Seth Donoughe
+      github_username: sdonoughe
+  archive: https://zenodo.org/record/4761417
+  version_accepted: 2.0.1
+  date_accepted: '2021-05-13'
+  created_at: 2020-05-04 16:51:36+00:00
+  updated_at: 2023-09-09 20:44:07+00:00
+  closed_at: 2021-05-17 21:07:45+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/24
+  joss:
+  partners:
+  gh_meta:
+      name: phenopype
+      description: A phenotyping pipeline for Python
+      created_at: '2022-01-04'
+      stargazers_count: 13
+      watchers_count: 1
+      open_issues_count: 1
+      forks_count: 4
+      documentation: https://www.phenopype.org
+      contrib_count: 1
+      last_commit: '2025-02-03'
+  labels:
+    - 6/pyOS-approved
+  active: true
+- package_name: pyrolite
+  package_description: A set of tools for getting the most from your
+      geochemical data.
+  submitting_author:
+      name: Morgan Williams
+      github_username: morganjwilliams
+  all_current_maintainers:
+    - name: Morgan Williams
+      github_username: morganjwilliams
+  repository_link: https://github.com/morganjwilliams/pyrolite
+  repository_host: github
+  version_submitted: '[0.2.5](https://github.com/morganjwilliams/pyrolite/releases/tag/0.2.5)'
+  categories:
+    - data-munging
+    - reproducibility
+    - education
+    - data-visualization*
+  editor:
+      name: Leah Wasser
+      github_username: lwasser
+  eic:
+  reviewers:
+    - name: Romain Beucher
+      github_username: rbeucher
+    - name: Charles Le Losq
+      github_username: charlesll
+  archive: https://zenodo.org/record/3877690
+  version_accepted: v
+      [0.2.7](https://github.com/morganjwilliams/pyrolite/releases/tag/0.2.7)
+  date_accepted: '2020-06-04'
+  created_at: 2020-02-19 04:54:35+00:00
+  updated_at: 2023-09-10 20:51:18+00:00
+  closed_at: 2020-06-09 13:13:43+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/20
+  joss: https://joss.theoj.org/papers/10.21105/joss.02314
+  partners:
+  gh_meta:
+      name: pyrolite
+      description: A set of tools for getting the most from your geochemical
+          data.
+      created_at: '2018-06-13'
+      stargazers_count: 163
+      watchers_count: 5
+      open_issues_count: 10
+      forks_count: 51
+      documentation: https://pyrolite.readthedocs.io
+      contrib_count: 15
+      last_commit: '2026-04-17'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+  active: true
+- package_name: MovingPandas
+  package_description: Trajectory classes and functions built on top of
+      GeoPandas
+  submitting_author:
+      name: Anita Graser
+      github_username: anitagraser
+  all_current_maintainers:
+    - name: Anita Graser
+      github_username: anitagraser
+  repository_link: https://github.com/movingpandas/movingpandas
+  repository_host: github
+  version_submitted: '0.2'
+  categories:
+    - geospatial
+    - data-visualization*
+  editor:
+      name: Jenny Palomino
+      github_username: jlpalomino
+  eic:
+  reviewers:
+    - name: Ivan Ogasawara
+      github_username: xmnlab
+    - name: Martin Fleischmann
+      github_username: martinfleis
+  archive: https://zenodo.org/record/3710951
+  version_accepted: v
+      [0.3.rc1](https://github.com/movingpandas/movingpandas/releases/tag/v0.3.rc1)
+  date_accepted: '2020-03-19'
+  created_at: 2020-01-06 17:13:27+00:00
+  updated_at: 2023-09-10 20:38:04+00:00
+  closed_at: 2020-04-08 17:14:16+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/18
+  joss:
+  partners:
+  gh_meta:
+      name: movingpandas
+      description: MovingPandas - a Python library for movement data
+          exploration and analysis
+      created_at: '2018-12-16'
+      stargazers_count: 1398
+      watchers_count: 38
+      open_issues_count: 32
+      forks_count: 205
+      documentation: https://movingpandas.org
+      contrib_count: 40
+      last_commit: '2026-04-05'
+  labels:
+    - 6/pyOS-approved
+  active: true
+- package_name: pandera
+  package_description: validate the types, properties, and statistics of
+      pandas data structures
+  submitting_author:
+      name: Niels Bantilan
+      github_username: cosmicbboy
+  all_current_maintainers:
+    - name: Niels Bantilan
+      github_username: cosmicbboy
+  repository_link: https://github.com/unionai-oss/pandera
+  repository_host: github
+  version_submitted: 0.1.5
+  categories:
+    - data-munging
+    - reproducibility
+  editor:
+      name: Leah Wasser
+      github_username: lwasser
+  eic:
+  reviewers:
+    - name: Max Joseph
+      github_username: mbjoseph
+    - name: Ivan Ogasawara
+      github_username: xmnlab
+  archive: https://github.com/pandera-dev/pandera/releases/tag/v0.2.3
+  version_accepted: v0.2.3
+  date_accepted: '2019-10-10'
+  created_at: 2019-08-14 22:21:25+00:00
+  updated_at: 2023-08-29 02:14:08+00:00
+  closed_at: 2021-12-16 21:55:55+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/12
+  joss:
+  partners:
+  gh_meta:
+      name: pandera
+      description: A light-weight, flexible, and expressive statistical data
+          testing library
+      created_at: '2018-11-01'
+      stargazers_count: 4341
+      watchers_count: 21
+      open_issues_count: 410
+      forks_count: 396
+      documentation: https://www.union.ai/pandera
+      contrib_count: 182
+      last_commit: '2026-05-08'
+  labels:
+    - 6/pyOS-approved
+  active: true
+- package_name: Nbless
+  package_description: Construct, deconstruct, convert, execute, & prepare
+      slides from Jupyter notebooks
+  submitting_author:
+      name: Martin Skarzynski
+      github_username: marskar
+  all_current_maintainers:
+    - name: Martin Skarzynski
+      github_username: marskar
+  repository_link: https://github.com/py4ds/nbless
+  repository_host: github
+  version_submitted: 0.2.26
+  categories:
+    - reproducibility
+    - education
+  editor:
+      name: Leah Wasser
+      github_username: lwasser
+  eic:
+  reviewers:
+    - name: Filipe
+      github_username: ocefpaf
+    - name: Kylen Solvik
+      github_username: kysolvik
+  archive:
+  version_accepted: TBD
+  date_accepted: '2019-06-17'
+  created_at: 2019-05-30 18:27:38+00:00
+  updated_at: 2025-01-13 17:42:30+00:00
+  closed_at: 2019-08-06 15:45:11+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/7
+  joss:
+  partners:
+  gh_meta:
+      name: nbless
+      description: Construct, deconstruct, convert, execute, and prepare
+          slides from Jupyter notebooks
+      created_at: '2018-09-05'
+      stargazers_count: 34
+      watchers_count: 0
+      open_issues_count: 0
+      forks_count: 6
+      documentation: https://py4ds.github.io/nbless/
+      contrib_count: 4
+      last_commit: '2019-07-25'
+  labels:
+    - 6/pyOS-approved
+    - archived
+  active: false
+- package_name: earthpy
+  package_description: A package built to support working with spatial data
+      using open source python
+  submitting_author:
+      name: Leah Wasser
+      github_username: lwasser
+  all_current_maintainers:
+    - name: Leah Wasser
+      github_username: lwasser
+    - name: Nathan Korinek
+      github_username: nkorinek
+    - name: Max Joseph
+      github_username: mbjoseph
+    - name: Joe McGlinchy
+      github_username: joemcglinchy
+    - name: Jenny Palomino
+      github_username: jlpalomino
+  repository_link: https://github.com/earthlab/earthpy
+  repository_host: github
+  version_submitted: '[0.7](https://github.com/earthlab/earthpy/releases/tag/v0.7.0)'
+  categories:
+    - geospatial
+  editor:
+      name: Luiz Irber
+      github_username: luizirber
+  eic:
+  reviewers:
+    - name: Rohit Goswami
+      github_username: HaoZeke
+    - name: Sean Gillies
+      github_username: sgillies
+  archive: https://zenodo.org/record/3520899
+  version_accepted: v
+      [0.7.5](https://github.com/earthlab/earthpy/releases/tag/v0.7.5)
+  date_accepted: '2019-11-06'
+  created_at: 2019-05-08 15:02:14+00:00
+  updated_at: 2025-02-15 03:57:27+00:00
+  closed_at: 2019-11-13 22:59:32+00:00
+  issue_link: https://github.com/pyOpenSci/software-submission/issues/3
+  joss: https://joss.theoj.org/papers/10.21105/joss.01886
+  partners:
+  gh_meta:
+      name: earthpy
+      description: A package built to support working with spatial data using
+          open source python
+      created_at: '2018-02-20'
+      stargazers_count: 535
+      watchers_count: 16
+      open_issues_count: 29
+      forks_count: 158
+      documentation: https://earthpy.readthedocs.io
+      contrib_count: 29
+      last_commit: '2025-07-31'
+  labels:
+    - 6/pyOS-approved
+    - 9/joss-approved
+    - archived
+  active: false
diff --git a/data/tutorials.yml b/data/tutorials.yml
new file mode 100644
index 00000000..0b064c90
--- /dev/null
+++ b/data/tutorials.yml
@@ -0,0 +1,90 @@
+- order: 0
+  title: "0. Get to know Hatch"
+  excerpt: >-
+    Hatch is an end-to-end Python packaging and workflow tool. In this tutorial,
+    you will install and learn how to configure Hatch for Python packaging.
+  link: https://www.pyopensci.org/python-package-guide/tutorials/get-to-know-hatch.html
+
+- order: 1
+  title: "1. What is a Python package"
+  excerpt: >-
+    Learn about what a Python package is and the basic components that make up a
+    Python package.
+  link: https://www.pyopensci.org/python-package-guide/tutorials/intro.html
+
+- order: 2
+  title: "2. Make your Python code installable"
+  excerpt: >-
+    Learn how to create the most basic version of a Python package which can
+    then be installed into a Python environment.
+  link: https://www.pyopensci.org/python-package-guide/tutorials/create-python-package.html
+
+- order: 3
+  title: "3. Publish your Python package to PyPI"
+  excerpt: >-
+    Learn how to publish your Python package to test.PyPI.org and to PyPI.org.
+  link: https://www.pyopensci.org/python-package-guide/tutorials/publish-pypi.html
+
+- order: 4
+  title: "4. Publish to conda forge using grayskull"
+  excerpt: >-
+    Learn how to publish your Python package to the conda-forge channel of conda
+    using the grayskull Python package.
+  link: https://www.pyopensci.org/python-package-guide/tutorials/publish-conda-forge.html
+
+- order: 5
+  title: "5. Add a README file to your Python package"
+  excerpt: >-
+    A README file is often the landing page that a user will use to understand
+    your package. Learn about how to create a useful README file for your Python
+    package.
+  link: https://www.pyopensci.org/python-package-guide/tutorials/add-readme.html
+
+- order: 6
+  title: "6. Add a LICENSE and CODE_OF_CONDUCT"
+  excerpt: >-
+    License and code of conduct files are important to add to your Python package
+    as they provide instructions for both how users can use your package and
+    also how the community of users should interact with you as a maintainer.
+  link: https://www.pyopensci.org/python-package-guide/tutorials/add-license-coc.html
+
+- order: 7
+  title: "7. Add metadata with a pyproject.toml file"
+  excerpt: >-
+    To enhance the visibility of your package on PyPI and provide more
+    information about its compatibility with Python versions, project development
+    status, and project maintainers, you should add additional metadata to your
+    pyproject.toml file. This lesson will guide you through the process.
+  link: https://www.pyopensci.org/python-package-guide/tutorials/pyproject-toml.html
+
+- order: 8
+  title: "Command line reference for packaging"
+  excerpt: >-
+    Quick-reference tables for shell commands used across the packaging
+    tutorials, from installing Hatch and pipx through building, testing, and
+    publishing.
+  link: https://www.pyopensci.org/python-package-guide/tutorials/command-line-reference.html
+
+- order: 9
+  title: "Trusted publishing with GitHub Actions"
+  excerpt: >-
+    Automate building and publishing to PyPI from GitHub Actions and configure
+    PyPI Trusted Publishing so you can ship releases without long-lived API
+    tokens on the repository.
+  link: https://www.pyopensci.org/python-package-guide/tutorials/trusted-publishing.html
+
+- order: 10
+  title: "Use Hatch environments in your package"
+  excerpt: >-
+    After you create a package with the pyOpenSci template, use Hatch to run
+    tests, build distributions, check metadata, and work with your development
+    environments day to day.
+  link: https://www.pyopensci.org/python-package-guide/tutorials/develop-python-package-hatch.html
+
+- order: 11
+  title: "Migrate setup.py to pyproject.toml with Hatch"
+  excerpt: >-
+    If your project already uses setup.py, Hatch can help you move toward a
+    modern pyproject.toml while keeping metadata and build settings aligned with
+    current packaging standards.
+  link: https://www.pyopensci.org/python-package-guide/tutorials/setup-py-to-pyproject-toml.html
diff --git a/hugo.toml b/hugo.toml
new file mode 100644
index 00000000..3502ef67
--- /dev/null
+++ b/hugo.toml
@@ -0,0 +1,247 @@
+# pyOpenSci website (Hugo) — lives at repo root. Legacy Jekyll site is in
+# jekyll/. Production still builds Jekyll from jekyll/ until cutover.
+
+baseURL = 'https://www.pyopensci.org/'
+languageCode = 'en-us'
+title = 'pyOpenSci'
+theme = 'clean-hugo'
+timeZone = 'America/Denver'
+
+enableRobotsTXT = true
+buildFuture = true
+
+# Site images: use Hugo’s normal `static/images/` (published as /images/...).
+# The legacy Jekyll site still reads from `jekyll/images/` for its own build.
+
+[sitemap]
+  changefreq = 'weekly'
+  filename = 'sitemap.xml'
+  priority = 0.5
+
+[markup]
+  [markup.goldmark.renderer]
+    unsafe = true
+  [markup.highlight]
+    style = 'monokai'
+    lineNos = false
+    noClasses = false
+    codeFences = true
+    guessSyntax = true
+
+[params]
+  author = 'pyOpenSci'
+  tagline = 'We support the open source contributors and developers who fuel scientific discovery.'
+
+  # Upper-left nav: logo image (served from mounted jekyll/images via static/images).
+  [params.nav_logo]
+    src = 'images/logo.png'
+    alt = 'pyOpenSci logo: a purple flower opening over the O in Open, representing open science.'
+  blog_title = 'pyOpenSci Blog'
+  description = 'pyOpenSci broadens participation in scientific open source.'
+
+  [params.seo]
+    default_image = 'images/landing-pages/scipy-sprint-working.png'
+
+  [params.social]
+    type = 'Organization'
+    github = 'https://github.com/pyopensci'
+    bluesky = 'https://bsky.app/profile/pyopensci.org'
+    linkedin = 'https://www.linkedin.com/company/pyopensci/'
+    mastodon = 'https://fosstodon.org/@pyOpenSci'
+    youtube = 'https://www.youtube.com/@pyopensci'
+
+  [params.footer]
+    follow_label = 'Follow'
+    mission = '''pyOpensci is dedicated to creating a welcoming, supportive and diverse community around the open source Python tools that drive open science. Our <a href="https://www.pyopensci.org/handbook/CODE_OF_CONDUCT.html" target="_blank" rel="noopener noreferrer">Code of Conduct</a> defines expected behavior and guidelines that help create such a community. pyOpenSci is a fiscally sponsored project of <a href="https://communityinitiatives.org/" target="_blank" rel="noopener noreferrer">Community Initiatives</a>, a registered 501(c)3 non-profit organization based in California, USA. pyOpenSci is grateful for support from the <a href="https://sloan.org/" target="_blank" rel="noopener noreferrer">Sloan Foundation</a> and the <a href="https://chanzuckerberg.com/" target="_blank" rel="noopener noreferrer">Chan Zuckerberg Initiative</a>.'''
+
+[[params.footer.links]]
+  label = 'Mastodon'
+  icon = 'fab fa-fw fa-mastodon'
+  url = 'https://fosstodon.org/@pyOpenSci'
+  rel_me = true
+
+[[params.footer.links]]
+  label = 'Bluesky'
+  icon = 'fa-solid fa-cloud'
+  url = 'https://bsky.app/profile/pyopensci.org'
+
+[[params.footer.links]]
+  label = 'LinkedIn'
+  icon = 'fab fa-fw fa-linkedin'
+  url = 'https://www.linkedin.com/company/pyopensci'
+
+[[params.footer.links]]
+  label = 'GitHub'
+  icon = 'fab fa-fw fa-github'
+  url = 'https://github.com/pyOpenSci'
+
+[[params.footer.links]]
+  label = 'YouTube'
+  icon = 'fa-brands fa-youtube'
+  url = 'https://www.youtube.com/@pyopensci'
+
+[params.theme]
+  enableGallery = false
+  enableFontAwesome = true
+
+  [params.theme.fonts]
+    heading = 'Poppins'
+    body = 'Nunito Sans'
+
+  [params.theme.colors]
+    primary = '#2E6060'
+    primaryDark = '#142929'
+    primaryLight = '#D6E3E3'
+    secondary = '#F1E0A6'
+    accent = '#42213D'
+    accentLight = '#E4B8C6'
+    neutral = '#395E66'
+    white = '#FFFFFF'
+    gray50 = '#F9FAFB'
+    gray200 = '#E5E7EB'
+    gray600 = '#4B5563'
+    gray700 = '#374151'
+    gray900 = '#111827'
+    link = '#2E6060'
+    linkOnDark = '#2DD4BF'
+    linkHover = '#1F4345'
+    featureCard = '#EBC1D3'
+    'heroBg' = '#33205C'
+    brandPurple = '#33205C'
+    brandPurpleDark = '#542668'
+    brandPurpleMedium = '#735FAB'
+    brandSoftPurple = '#BAB3D4'
+    brandLightPurple = '#E1DFED'
+    brandMagenta = '#BB82B0'
+    brandHeaderPurple = '#6B5B95'
+    'admonition-info' = '#53354F'
+    'admonition-success' = '#71B3B5'
+    'admonition-warning' = '#E4B8C6'
+    'admonition-danger' = '#F1E0A6'
+    'admonition-note' = '#CAE4E4'
+
+    # Event cards on /events/ (event_type: training | sprint | community | talk)
+    eventLabelTrainingBg = '#D6E3E3'
+    eventLabelTrainingFg = '#142929'
+    eventLabelSprintBg = '#E4B8C6'
+    eventLabelSprintFg = '#111827'
+    eventLabelCommunityBg = '#F1E0A6'
+    eventLabelCommunityFg = '#111827'
+    eventLabelTalkBg = '#CAE4E4'
+    eventLabelTalkFg = '#142929'
+    eventDateBadgeBg = '#42213D'
+    eventDateBadgeFg = '#FFFFFF'
+
+[params.nav_button]
+  text = 'Donate'
+  url = 'https://give.communityin.org/pyopensci_2024'
+  variant = 'dark-purple'
+
+# Main nav — Training + Research Software internal pages live; Community +
+# Support Us still use '#' until people + support pages land.
+
+[[menu.main]]
+  name = 'Training'
+  weight = 10
+
+[[menu.main]]
+  name = 'For Learners'
+  url = '/learn/'
+  parent = 'Training'
+  weight = 1
+
+[[menu.main]]
+  name = 'For Universities & Labs'
+  url = '/learn-universities-labs/'
+  parent = 'Training'
+  weight = 2
+
+
+[[menu.main]]
+  name = 'Research Software'
+  weight = 20
+
+[[menu.main]]
+  name = 'Peer Review'
+  url = '/about-peer-review/'
+  parent = 'Research Software'
+  weight = 1
+
+[[menu.main]]
+  name = 'Submit a Package'
+  url = '/how-to-submit-a-package-to-pyopensci/'
+  parent = 'Research Software'
+  weight = 2
+
+[[menu.main]]
+  name = 'Our Packages'
+  url = '/python-packages/'
+  parent = 'Research Software'
+  weight = 3
+
+[[menu.main]]
+  name = 'Peer Review Guide'
+  url = 'https://www.pyopensci.org/software-peer-review/'
+  parent = 'Research Software'
+  weight = 4
+  [menu.main.params]
+    external = true
+    icon = 'fas fa-external-link-alt'
+
+[[menu.main]]
+  name = 'Packaging Guide'
+  url = 'https://www.pyopensci.org/python-package-guide/'
+  parent = 'Research Software'
+  weight = 5
+  [menu.main.params]
+    external = true
+    icon = 'fas fa-external-link-alt'
+
+[[menu.main]]
+  name = 'Community'
+  weight = 30
+
+[[menu.main]]
+  name = 'Our Community'
+  url = '#'
+  parent = 'Community'
+  weight = 1
+  [menu.main.params]
+    icon = 'fa-brands fa-discourse'
+
+[[menu.main]]
+  name = 'Blog'
+  url = '/blog/'
+  parent = 'Community'
+  weight = 2
+
+[[menu.main]]
+  name = 'Events'
+  url = '/events/'
+  parent = 'Community'
+  weight = 3
+
+[[menu.main]]
+  name = 'Handbook'
+  url = 'https://www.pyopensci.org/handbook/'
+  parent = 'Community'
+  weight = 4
+  [menu.main.params]
+    external = true
+    icon = 'fas fa-external-link-alt'
+
+[[menu.main]]
+  name = 'Support Us'
+  weight = 40
+
+[[menu.main]]
+  name = 'Ways to Give'
+  url = '#'
+  parent = 'Support Us'
+  weight = 1
+
+[[menu.main]]
+  name = 'Volunteer'
+  url = '#'
+  parent = 'Support Us'
+  weight = 2
diff --git a/lychee.toml b/lychee.toml
index 9a5fd5d9..b35f38cd 100644
--- a/lychee.toml
+++ b/lychee.toml
@@ -2,8 +2,8 @@
 # Docs: https://lychee.cli.rs/
 #
 # Domain-level skips live in .lycheeignore.
-# CI may pass additional flags via .github/workflows/linkcheck.yml
-# (e.g. --root-dir $GITHUB_WORKSPACE/_site).
+# CI may pass additional flags via .github/workflows/build-site.yml
+# (e.g. --root-dir public) or linkcheck.yml (still uses _site until migrated).
 
 ############################# Display ##############################
 
diff --git a/netlify.toml b/netlify.toml
index d8435556..27f3d920 100644
--- a/netlify.toml
+++ b/netlify.toml
@@ -1,10 +1,9 @@
 [build]
-  command = "bundle exec jekyll build"
-  publish = "_site"
+  command = "npm ci && hugo --gc --minify"
+  publish = "public"
 
 [build.environment]
-  JEKYLL_ENV = "production"
-
-# Include future-dated posts on PR deploy previews only.
-[context.deploy-preview]
-  command = "bundle exec jekyll build --future"
+  HUGO_VERSION = "0.139.4"
+  NODE_VERSION = "20"
+  HUGO_ENV = "production"
+  TZ = "America/Denver"
diff --git a/package-lock.json b/package-lock.json
new file mode 100644
index 00000000..ea848217
--- /dev/null
+++ b/package-lock.json
@@ -0,0 +1,923 @@
+{
+  "name": "pyopensci-hugo-site",
+  "lockfileVersion": 3,
+  "requires": true,
+  "packages": {
+    "": {
+      "name": "pyopensci-hugo-site",
+      "devDependencies": {
+        "autoprefixer": "^10.4.24",
+        "postcss": "^8.5.6",
+        "postcss-cli": "^11.0.1"
+      }
+    },
+    "node_modules/ansi-regex": {
+      "version": "5.0.1",
+      "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz",
+      "integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=8"
+      }
+    },
+    "node_modules/ansi-styles": {
+      "version": "4.3.0",
+      "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-4.3.0.tgz",
+      "integrity": "sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "color-convert": "^2.0.1"
+      },
+      "engines": {
+        "node": ">=8"
+      },
+      "funding": {
+        "url": "https://github.com/chalk/ansi-styles?sponsor=1"
+      }
+    },
+    "node_modules/anymatch": {
+      "version": "3.1.3",
+      "resolved": "https://registry.npmjs.org/anymatch/-/anymatch-3.1.3.tgz",
+      "integrity": "sha512-KMReFUr0B4t+D+OBkjR3KYqvocp2XaSzO55UcB6mgQMd3KbcE+mWTyvVV7D/zsdEbNnV6acZUutkiHQXvTr1Rw==",
+      "dev": true,
+      "license": "ISC",
+      "dependencies": {
+        "normalize-path": "^3.0.0",
+        "picomatch": "^2.0.4"
+      },
+      "engines": {
+        "node": ">= 8"
+      }
+    },
+    "node_modules/autoprefixer": {
+      "version": "10.5.0",
+      "resolved": "https://registry.npmjs.org/autoprefixer/-/autoprefixer-10.5.0.tgz",
+      "integrity": "sha512-FMhOoZV4+qR6aTUALKX2rEqGG+oyATvwBt9IIzVR5rMa2HRWPkxf+P+PAJLD1I/H5/II+HuZcBJYEFBpq39ong==",
+      "dev": true,
+      "funding": [
+        {
+          "type": "opencollective",
+          "url": "https://opencollective.com/postcss/"
+        },
+        {
+          "type": "tidelift",
+          "url": "https://tidelift.com/funding/github/npm/autoprefixer"
+        },
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/ai"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "browserslist": "^4.28.2",
+        "caniuse-lite": "^1.0.30001787",
+        "fraction.js": "^5.3.4",
+        "picocolors": "^1.1.1",
+        "postcss-value-parser": "^4.2.0"
+      },
+      "bin": {
+        "autoprefixer": "bin/autoprefixer"
+      },
+      "engines": {
+        "node": "^10 || ^12 || >=14"
+      },
+      "peerDependencies": {
+        "postcss": "^8.1.0"
+      }
+    },
+    "node_modules/baseline-browser-mapping": {
+      "version": "2.10.24",
+      "resolved": "https://registry.npmjs.org/baseline-browser-mapping/-/baseline-browser-mapping-2.10.24.tgz",
+      "integrity": "sha512-I2NkZOOrj2XuguvWCK6OVh9GavsNjZjK908Rq3mIBK25+GD8vPX5w2WdxVqnQ7xx3SrZJiCiZFu+/Oz50oSYSA==",
+      "dev": true,
+      "license": "Apache-2.0",
+      "bin": {
+        "baseline-browser-mapping": "dist/cli.cjs"
+      },
+      "engines": {
+        "node": ">=6.0.0"
+      }
+    },
+    "node_modules/binary-extensions": {
+      "version": "2.3.0",
+      "resolved": "https://registry.npmjs.org/binary-extensions/-/binary-extensions-2.3.0.tgz",
+      "integrity": "sha512-Ceh+7ox5qe7LJuLHoY0feh3pHuUDHAcRUeyL2VYghZwfpkNIy/+8Ocg0a3UuSoYzavmylwuLWQOf3hl0jjMMIw==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=8"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/braces": {
+      "version": "3.0.3",
+      "resolved": "https://registry.npmjs.org/braces/-/braces-3.0.3.tgz",
+      "integrity": "sha512-yQbXgO/OSZVD2IsiLlro+7Hf6Q18EJrKSEsdoMzKePKXct3gvD8oLcOQdIzGupr5Fj+EDe8gO/lxc1BzfMpxvA==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "fill-range": "^7.1.1"
+      },
+      "engines": {
+        "node": ">=8"
+      }
+    },
+    "node_modules/browserslist": {
+      "version": "4.28.2",
+      "resolved": "https://registry.npmjs.org/browserslist/-/browserslist-4.28.2.tgz",
+      "integrity": "sha512-48xSriZYYg+8qXna9kwqjIVzuQxi+KYWp2+5nCYnYKPTr0LvD89Jqk2Or5ogxz0NUMfIjhh2lIUX/LyX9B4oIg==",
+      "dev": true,
+      "funding": [
+        {
+          "type": "opencollective",
+          "url": "https://opencollective.com/browserslist"
+        },
+        {
+          "type": "tidelift",
+          "url": "https://tidelift.com/funding/github/npm/browserslist"
+        },
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/ai"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "baseline-browser-mapping": "^2.10.12",
+        "caniuse-lite": "^1.0.30001782",
+        "electron-to-chromium": "^1.5.328",
+        "node-releases": "^2.0.36",
+        "update-browserslist-db": "^1.2.3"
+      },
+      "bin": {
+        "browserslist": "cli.js"
+      },
+      "engines": {
+        "node": "^6 || ^7 || ^8 || ^9 || ^10 || ^11 || ^12 || >=13.7"
+      }
+    },
+    "node_modules/caniuse-lite": {
+      "version": "1.0.30001791",
+      "resolved": "https://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30001791.tgz",
+      "integrity": "sha512-yk0l/YSrOnFZk3UROpDLQD9+kC1l4meK/wed583AXrzoarMGJcbRi2Q4RaUYbKxYAsZ8sWmaSa/DsLmdBeI1vQ==",
+      "dev": true,
+      "funding": [
+        {
+          "type": "opencollective",
+          "url": "https://opencollective.com/browserslist"
+        },
+        {
+          "type": "tidelift",
+          "url": "https://tidelift.com/funding/github/npm/caniuse-lite"
+        },
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/ai"
+        }
+      ],
+      "license": "CC-BY-4.0"
+    },
+    "node_modules/chokidar": {
+      "version": "3.6.0",
+      "resolved": "https://registry.npmjs.org/chokidar/-/chokidar-3.6.0.tgz",
+      "integrity": "sha512-7VT13fmjotKpGipCW9JEQAusEPE+Ei8nl6/g4FBAmIm0GOOLMua9NDDo/DWp0ZAxCr3cPq5ZpBqmPAQgDda2Pw==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "anymatch": "~3.1.2",
+        "braces": "~3.0.2",
+        "glob-parent": "~5.1.2",
+        "is-binary-path": "~2.1.0",
+        "is-glob": "~4.0.1",
+        "normalize-path": "~3.0.0",
+        "readdirp": "~3.6.0"
+      },
+      "engines": {
+        "node": ">= 8.10.0"
+      },
+      "funding": {
+        "url": "https://paulmillr.com/funding/"
+      },
+      "optionalDependencies": {
+        "fsevents": "~2.3.2"
+      }
+    },
+    "node_modules/cliui": {
+      "version": "8.0.1",
+      "resolved": "https://registry.npmjs.org/cliui/-/cliui-8.0.1.tgz",
+      "integrity": "sha512-BSeNnyus75C4//NQ9gQt1/csTXyo/8Sb+afLAkzAptFuMsod9HFokGNudZpi/oQV73hnVK+sR+5PVRMd+Dr7YQ==",
+      "dev": true,
+      "license": "ISC",
+      "dependencies": {
+        "string-width": "^4.2.0",
+        "strip-ansi": "^6.0.1",
+        "wrap-ansi": "^7.0.0"
+      },
+      "engines": {
+        "node": ">=12"
+      }
+    },
+    "node_modules/color-convert": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/color-convert/-/color-convert-2.0.1.tgz",
+      "integrity": "sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "color-name": "~1.1.4"
+      },
+      "engines": {
+        "node": ">=7.0.0"
+      }
+    },
+    "node_modules/color-name": {
+      "version": "1.1.4",
+      "resolved": "https://registry.npmjs.org/color-name/-/color-name-1.1.4.tgz",
+      "integrity": "sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA==",
+      "dev": true,
+      "license": "MIT"
+    },
+    "node_modules/dependency-graph": {
+      "version": "1.0.0",
+      "resolved": "https://registry.npmjs.org/dependency-graph/-/dependency-graph-1.0.0.tgz",
+      "integrity": "sha512-cW3gggJ28HZ/LExwxP2B++aiKxhJXMSIt9K48FOXQkm+vuG5gyatXnLsONRJdzO/7VfjDIiaOOa/bs4l464Lwg==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=4"
+      }
+    },
+    "node_modules/electron-to-chromium": {
+      "version": "1.5.346",
+      "resolved": "https://registry.npmjs.org/electron-to-chromium/-/electron-to-chromium-1.5.346.tgz",
+      "integrity": "sha512-3PGbvVwt9AppQsta0Kuq5DIcSj7aQfDfCVS7KnV3nhXEDtuJVRS7kK28Q+qy5KRkQ4bICV4xOaXNeUaXe78dDg==",
+      "dev": true,
+      "license": "ISC"
+    },
+    "node_modules/emoji-regex": {
+      "version": "8.0.0",
+      "resolved": "https://registry.npmjs.org/emoji-regex/-/emoji-regex-8.0.0.tgz",
+      "integrity": "sha512-MSjYzcWNOA0ewAHpz0MxpYFvwg6yjy1NG3xteoqz644VCo/RPgnr1/GGt+ic3iJTzQ8Eu3TdM14SawnVUmGE6A==",
+      "dev": true,
+      "license": "MIT"
+    },
+    "node_modules/escalade": {
+      "version": "3.2.0",
+      "resolved": "https://registry.npmjs.org/escalade/-/escalade-3.2.0.tgz",
+      "integrity": "sha512-WUj2qlxaQtO4g6Pq5c29GTcWGDyd8itL8zTlipgECz3JesAiiOKotd8JU6otB3PACgG6xkJUyVhboMS+bje/jA==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=6"
+      }
+    },
+    "node_modules/fill-range": {
+      "version": "7.1.1",
+      "resolved": "https://registry.npmjs.org/fill-range/-/fill-range-7.1.1.tgz",
+      "integrity": "sha512-YsGpe3WHLK8ZYi4tWDg2Jy3ebRz2rXowDxnld4bkQB00cc/1Zw9AWnC0i9ztDJitivtQvaI9KaLyKrc+hBW0yg==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "to-regex-range": "^5.0.1"
+      },
+      "engines": {
+        "node": ">=8"
+      }
+    },
+    "node_modules/fraction.js": {
+      "version": "5.3.4",
+      "resolved": "https://registry.npmjs.org/fraction.js/-/fraction.js-5.3.4.tgz",
+      "integrity": "sha512-1X1NTtiJphryn/uLQz3whtY6jK3fTqoE3ohKs0tT+Ujr1W59oopxmoEh7Lu5p6vBaPbgoM0bzveAW4Qi5RyWDQ==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": "*"
+      },
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/rawify"
+      }
+    },
+    "node_modules/fs-extra": {
+      "version": "11.3.4",
+      "resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-11.3.4.tgz",
+      "integrity": "sha512-CTXd6rk/M3/ULNQj8FBqBWHYBVYybQ3VPBw0xGKFe3tuH7ytT6ACnvzpIQ3UZtB8yvUKC2cXn1a+x+5EVQLovA==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "graceful-fs": "^4.2.0",
+        "jsonfile": "^6.0.1",
+        "universalify": "^2.0.0"
+      },
+      "engines": {
+        "node": ">=14.14"
+      }
+    },
+    "node_modules/fsevents": {
+      "version": "2.3.3",
+      "resolved": "https://registry.npmjs.org/fsevents/-/fsevents-2.3.3.tgz",
+      "integrity": "sha512-5xoDfX+fL7faATnagmWPpbFtwh/R77WmMMqqHGS65C3vvB0YHrgF+B1YmZ3441tMj5n63k0212XNoJwzlhffQw==",
+      "dev": true,
+      "hasInstallScript": true,
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "darwin"
+      ],
+      "engines": {
+        "node": "^8.16.0 || ^10.6.0 || >=11.0.0"
+      }
+    },
+    "node_modules/get-caller-file": {
+      "version": "2.0.5",
+      "resolved": "https://registry.npmjs.org/get-caller-file/-/get-caller-file-2.0.5.tgz",
+      "integrity": "sha512-DyFP3BM/3YHTQOCUL/w0OZHR0lpKeGrxotcHWcqNEdnltqFwXVfhEBQ94eIo34AfQpo0rGki4cyIiftY06h2Fg==",
+      "dev": true,
+      "license": "ISC",
+      "engines": {
+        "node": "6.* || 8.* || >= 10.*"
+      }
+    },
+    "node_modules/glob-parent": {
+      "version": "5.1.2",
+      "resolved": "https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz",
+      "integrity": "sha512-AOIgSQCepiJYwP3ARnGx+5VnTu2HBYdzbGP45eLw1vr3zB3vZLeyed1sC9hnbcOc9/SrMyM5RPQrkGz4aS9Zow==",
+      "dev": true,
+      "license": "ISC",
+      "dependencies": {
+        "is-glob": "^4.0.1"
+      },
+      "engines": {
+        "node": ">= 6"
+      }
+    },
+    "node_modules/graceful-fs": {
+      "version": "4.2.11",
+      "resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.2.11.tgz",
+      "integrity": "sha512-RbJ5/jmFcNNCcDV5o9eTnBLJ/HszWV0P73bc+Ff4nS/rJj+YaS6IGyiOL0VoBYX+l1Wrl3k63h/KrH+nhJ0XvQ==",
+      "dev": true,
+      "license": "ISC"
+    },
+    "node_modules/is-binary-path": {
+      "version": "2.1.0",
+      "resolved": "https://registry.npmjs.org/is-binary-path/-/is-binary-path-2.1.0.tgz",
+      "integrity": "sha512-ZMERYes6pDydyuGidse7OsHxtbI7WVeUEozgR/g7rd0xUimYNlvZRE/K2MgZTjWy725IfelLeVcEM97mmtRGXw==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "binary-extensions": "^2.0.0"
+      },
+      "engines": {
+        "node": ">=8"
+      }
+    },
+    "node_modules/is-extglob": {
+      "version": "2.1.1",
+      "resolved": "https://registry.npmjs.org/is-extglob/-/is-extglob-2.1.1.tgz",
+      "integrity": "sha512-SbKbANkN603Vi4jEZv49LeVJMn4yGwsbzZworEoyEiutsN3nJYdbO36zfhGJ6QEDpOZIFkDtnq5JRxmvl3jsoQ==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=0.10.0"
+      }
+    },
+    "node_modules/is-fullwidth-code-point": {
+      "version": "3.0.0",
+      "resolved": "https://registry.npmjs.org/is-fullwidth-code-point/-/is-fullwidth-code-point-3.0.0.tgz",
+      "integrity": "sha512-zymm5+u+sCsSWyD9qNaejV3DFvhCKclKdizYaJUuHA83RLjb7nSuGnddCHGv0hk+KY7BMAlsWeK4Ueg6EV6XQg==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=8"
+      }
+    },
+    "node_modules/is-glob": {
+      "version": "4.0.3",
+      "resolved": "https://registry.npmjs.org/is-glob/-/is-glob-4.0.3.tgz",
+      "integrity": "sha512-xelSayHH36ZgE7ZWhli7pW34hNbNl8Ojv5KVmkJD4hBdD3th8Tfk9vYasLM+mXWOZhFkgZfxhLSnrwRr4elSSg==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "is-extglob": "^2.1.1"
+      },
+      "engines": {
+        "node": ">=0.10.0"
+      }
+    },
+    "node_modules/is-number": {
+      "version": "7.0.0",
+      "resolved": "https://registry.npmjs.org/is-number/-/is-number-7.0.0.tgz",
+      "integrity": "sha512-41Cifkg6e8TylSpdtTpeLVMqvSBEVzTttHvERD741+pnZ8ANv0004MRL43QKPDlK9cGvNp6NZWZUBlbGXYxxng==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=0.12.0"
+      }
+    },
+    "node_modules/jsonfile": {
+      "version": "6.2.1",
+      "resolved": "https://registry.npmjs.org/jsonfile/-/jsonfile-6.2.1.tgz",
+      "integrity": "sha512-zwOTdL3rFQ/lRdBnntKVOX6k5cKJwEc1HdilT71BWEu7J41gXIB2MRp+vxduPSwZJPWBxEzv4yH1wYLJGUHX4Q==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "universalify": "^2.0.0"
+      },
+      "optionalDependencies": {
+        "graceful-fs": "^4.1.6"
+      }
+    },
+    "node_modules/lilconfig": {
+      "version": "3.1.3",
+      "resolved": "https://registry.npmjs.org/lilconfig/-/lilconfig-3.1.3.tgz",
+      "integrity": "sha512-/vlFKAoH5Cgt3Ie+JLhRbwOsCQePABiU3tJ1egGvyQ+33R/vcwM2Zl2QR/LzjsBeItPt3oSVXapn+m4nQDvpzw==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=14"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/antonk52"
+      }
+    },
+    "node_modules/nanoid": {
+      "version": "3.3.12",
+      "resolved": "https://registry.npmjs.org/nanoid/-/nanoid-3.3.12.tgz",
+      "integrity": "sha512-ZB9RH/39qpq5Vu6Y+NmUaFhQR6pp+M2Xt76XBnEwDaGcVAqhlvxrl3B2bKS5D3NH3QR76v3aSrKaF/Kiy7lEtQ==",
+      "dev": true,
+      "funding": [
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/ai"
+        }
+      ],
+      "license": "MIT",
+      "bin": {
+        "nanoid": "bin/nanoid.cjs"
+      },
+      "engines": {
+        "node": "^10 || ^12 || ^13.7 || ^14 || >=15.0.1"
+      }
+    },
+    "node_modules/node-releases": {
+      "version": "2.0.38",
+      "resolved": "https://registry.npmjs.org/node-releases/-/node-releases-2.0.38.tgz",
+      "integrity": "sha512-3qT/88Y3FbH/Kx4szpQQ4HzUbVrHPKTLVpVocKiLfoYvw9XSGOX2FmD2d6DrXbVYyAQTF2HeF6My8jmzx7/CRw==",
+      "dev": true,
+      "license": "MIT"
+    },
+    "node_modules/normalize-path": {
+      "version": "3.0.0",
+      "resolved": "https://registry.npmjs.org/normalize-path/-/normalize-path-3.0.0.tgz",
+      "integrity": "sha512-6eZs5Ls3WtCisHWp9S2GUy8dqkpGi4BVSz3GaqiE6ezub0512ESztXUwUB6C6IKbQkY2Pnb/mD4WYojCRwcwLA==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=0.10.0"
+      }
+    },
+    "node_modules/picocolors": {
+      "version": "1.1.1",
+      "resolved": "https://registry.npmjs.org/picocolors/-/picocolors-1.1.1.tgz",
+      "integrity": "sha512-xceH2snhtb5M9liqDsmEw56le376mTZkEX/jEb/RxNFyegNul7eNslCXP9FDj/Lcu0X8KEyMceP2ntpaHrDEVA==",
+      "dev": true,
+      "license": "ISC"
+    },
+    "node_modules/picomatch": {
+      "version": "2.3.2",
+      "resolved": "https://registry.npmjs.org/picomatch/-/picomatch-2.3.2.tgz",
+      "integrity": "sha512-V7+vQEJ06Z+c5tSye8S+nHUfI51xoXIXjHQ99cQtKUkQqqO1kO/KCJUfZXuB47h/YBlDhah2H3hdUGXn8ie0oA==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=8.6"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/jonschlinkert"
+      }
+    },
+    "node_modules/pify": {
+      "version": "2.3.0",
+      "resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
+      "integrity": "sha512-udgsAY+fTnvv7kI7aaxbqwWNb0AHiB0qBO89PZKPkoTmGOgdbrHDKD+0B2X4uTfJ/FT1R09r9gTsjUjNJotuog==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=0.10.0"
+      }
+    },
+    "node_modules/postcss": {
+      "version": "8.5.13",
+      "resolved": "https://registry.npmjs.org/postcss/-/postcss-8.5.13.tgz",
+      "integrity": "sha512-qif0+jGGZoLWdHey3UFHHWP0H7Gbmsk8T5VEqyYFbWqPr1XqvLGBbk/sl8V5exGmcYJklJOhOQq1pV9IcsiFag==",
+      "dev": true,
+      "funding": [
+        {
+          "type": "opencollective",
+          "url": "https://opencollective.com/postcss/"
+        },
+        {
+          "type": "tidelift",
+          "url": "https://tidelift.com/funding/github/npm/postcss"
+        },
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/ai"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "nanoid": "^3.3.11",
+        "picocolors": "^1.1.1",
+        "source-map-js": "^1.2.1"
+      },
+      "engines": {
+        "node": "^10 || ^12 || >=14"
+      }
+    },
+    "node_modules/postcss-cli": {
+      "version": "11.0.1",
+      "resolved": "https://registry.npmjs.org/postcss-cli/-/postcss-cli-11.0.1.tgz",
+      "integrity": "sha512-0UnkNPSayHKRe/tc2YGW6XnSqqOA9eqpiRMgRlV1S6HdGi16vwJBx7lviARzbV1HpQHqLLRH3o8vTcB0cLc+5g==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "chokidar": "^3.3.0",
+        "dependency-graph": "^1.0.0",
+        "fs-extra": "^11.0.0",
+        "picocolors": "^1.0.0",
+        "postcss-load-config": "^5.0.0",
+        "postcss-reporter": "^7.0.0",
+        "pretty-hrtime": "^1.0.3",
+        "read-cache": "^1.0.0",
+        "slash": "^5.0.0",
+        "tinyglobby": "^0.2.12",
+        "yargs": "^17.0.0"
+      },
+      "bin": {
+        "postcss": "index.js"
+      },
+      "engines": {
+        "node": ">=18"
+      },
+      "peerDependencies": {
+        "postcss": "^8.0.0"
+      }
+    },
+    "node_modules/postcss-load-config": {
+      "version": "5.1.0",
+      "resolved": "https://registry.npmjs.org/postcss-load-config/-/postcss-load-config-5.1.0.tgz",
+      "integrity": "sha512-G5AJ+IX0aD0dygOE0yFZQ/huFFMSNneyfp0e3/bT05a8OfPC5FUoZRPfGijUdGOJNMewJiwzcHJXFafFzeKFVA==",
+      "dev": true,
+      "funding": [
+        {
+          "type": "opencollective",
+          "url": "https://opencollective.com/postcss/"
+        },
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/ai"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "lilconfig": "^3.1.1",
+        "yaml": "^2.4.2"
+      },
+      "engines": {
+        "node": ">= 18"
+      },
+      "peerDependencies": {
+        "jiti": ">=1.21.0",
+        "postcss": ">=8.0.9",
+        "tsx": "^4.8.1"
+      },
+      "peerDependenciesMeta": {
+        "jiti": {
+          "optional": true
+        },
+        "postcss": {
+          "optional": true
+        },
+        "tsx": {
+          "optional": true
+        }
+      }
+    },
+    "node_modules/postcss-reporter": {
+      "version": "7.1.0",
+      "resolved": "https://registry.npmjs.org/postcss-reporter/-/postcss-reporter-7.1.0.tgz",
+      "integrity": "sha512-/eoEylGWyy6/DOiMP5lmFRdmDKThqgn7D6hP2dXKJI/0rJSO1ADFNngZfDzxL0YAxFvws+Rtpuji1YIHj4mySA==",
+      "dev": true,
+      "funding": [
+        {
+          "type": "opencollective",
+          "url": "https://opencollective.com/postcss/"
+        },
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/ai"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "picocolors": "^1.0.0",
+        "thenby": "^1.3.4"
+      },
+      "engines": {
+        "node": ">=10"
+      },
+      "peerDependencies": {
+        "postcss": "^8.1.0"
+      }
+    },
+    "node_modules/postcss-value-parser": {
+      "version": "4.2.0",
+      "resolved": "https://registry.npmjs.org/postcss-value-parser/-/postcss-value-parser-4.2.0.tgz",
+      "integrity": "sha512-1NNCs6uurfkVbeXG4S8JFT9t19m45ICnif8zWLd5oPSZ50QnwMfK+H3jv408d4jw/7Bttv5axS5IiHoLaVNHeQ==",
+      "dev": true,
+      "license": "MIT"
+    },
+    "node_modules/pretty-hrtime": {
+      "version": "1.0.3",
+      "resolved": "https://registry.npmjs.org/pretty-hrtime/-/pretty-hrtime-1.0.3.tgz",
+      "integrity": "sha512-66hKPCr+72mlfiSjlEB1+45IjXSqvVAIy6mocupoww4tBFE9R9IhwwUGoI4G++Tc9Aq+2rxOt0RFU6gPcrte0A==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">= 0.8"
+      }
+    },
+    "node_modules/read-cache": {
+      "version": "1.0.0",
+      "resolved": "https://registry.npmjs.org/read-cache/-/read-cache-1.0.0.tgz",
+      "integrity": "sha512-Owdv/Ft7IjOgm/i0xvNDZ1LrRANRfew4b2prF3OWMQLxLfu3bS8FVhCsrSCMK4lR56Y9ya+AThoTpDCTxCmpRA==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "pify": "^2.3.0"
+      }
+    },
+    "node_modules/readdirp": {
+      "version": "3.6.0",
+      "resolved": "https://registry.npmjs.org/readdirp/-/readdirp-3.6.0.tgz",
+      "integrity": "sha512-hOS089on8RduqdbhvQ5Z37A0ESjsqz6qnRcffsMU3495FuTdqSm+7bhJ29JvIOsBDEEnan5DPu9t3To9VRlMzA==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "picomatch": "^2.2.1"
+      },
+      "engines": {
+        "node": ">=8.10.0"
+      }
+    },
+    "node_modules/require-directory": {
+      "version": "2.1.1",
+      "resolved": "https://registry.npmjs.org/require-directory/-/require-directory-2.1.1.tgz",
+      "integrity": "sha512-fGxEI7+wsG9xrvdjsrlmL22OMTTiHRwAMroiEeMgq8gzoLC/PQr7RsRDSTLUg/bZAZtF+TVIkHc6/4RIKrui+Q==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=0.10.0"
+      }
+    },
+    "node_modules/slash": {
+      "version": "5.1.0",
+      "resolved": "https://registry.npmjs.org/slash/-/slash-5.1.0.tgz",
+      "integrity": "sha512-ZA6oR3T/pEyuqwMgAKT0/hAv8oAXckzbkmR0UkUosQ+Mc4RxGoJkRmwHgHufaenlyAgE1Mxgpdcrf75y6XcnDg==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=14.16"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/source-map-js": {
+      "version": "1.2.1",
+      "resolved": "https://registry.npmjs.org/source-map-js/-/source-map-js-1.2.1.tgz",
+      "integrity": "sha512-UXWMKhLOwVKb728IUtQPXxfYU+usdybtUrK/8uGE8CQMvrhOpwvzDBwj0QhSL7MQc7vIsISBG8VQ8+IDQxpfQA==",
+      "dev": true,
+      "license": "BSD-3-Clause",
+      "engines": {
+        "node": ">=0.10.0"
+      }
+    },
+    "node_modules/string-width": {
+      "version": "4.2.3",
+      "resolved": "https://registry.npmjs.org/string-width/-/string-width-4.2.3.tgz",
+      "integrity": "sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "emoji-regex": "^8.0.0",
+        "is-fullwidth-code-point": "^3.0.0",
+        "strip-ansi": "^6.0.1"
+      },
+      "engines": {
+        "node": ">=8"
+      }
+    },
+    "node_modules/strip-ansi": {
+      "version": "6.0.1",
+      "resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz",
+      "integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "ansi-regex": "^5.0.1"
+      },
+      "engines": {
+        "node": ">=8"
+      }
+    },
+    "node_modules/thenby": {
+      "version": "1.4.1",
+      "resolved": "https://registry.npmjs.org/thenby/-/thenby-1.4.1.tgz",
+      "integrity": "sha512-D5a/bO0KdalOE3q8MlrRmSxjbKZHT3MQmXkJP+r97Vw8MMwOZKOwUSEyTtK7eSMj2y0kyAjpYMRMZmmLw1FtNQ==",
+      "dev": true,
+      "license": "Apache-2.0"
+    },
+    "node_modules/tinyglobby": {
+      "version": "0.2.16",
+      "resolved": "https://registry.npmjs.org/tinyglobby/-/tinyglobby-0.2.16.tgz",
+      "integrity": "sha512-pn99VhoACYR8nFHhxqix+uvsbXineAasWm5ojXoN8xEwK5Kd3/TrhNn1wByuD52UxWRLy8pu+kRMniEi6Eq9Zg==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "fdir": "^6.5.0",
+        "picomatch": "^4.0.4"
+      },
+      "engines": {
+        "node": ">=12.0.0"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/SuperchupuDev"
+      }
+    },
+    "node_modules/tinyglobby/node_modules/fdir": {
+      "version": "6.5.0",
+      "resolved": "https://registry.npmjs.org/fdir/-/fdir-6.5.0.tgz",
+      "integrity": "sha512-tIbYtZbucOs0BRGqPJkshJUYdL+SDH7dVM8gjy+ERp3WAUjLEFJE+02kanyHtwjWOnwrKYBiwAmM0p4kLJAnXg==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=12.0.0"
+      },
+      "peerDependencies": {
+        "picomatch": "^3 || ^4"
+      },
+      "peerDependenciesMeta": {
+        "picomatch": {
+          "optional": true
+        }
+      }
+    },
+    "node_modules/tinyglobby/node_modules/picomatch": {
+      "version": "4.0.4",
+      "resolved": "https://registry.npmjs.org/picomatch/-/picomatch-4.0.4.tgz",
+      "integrity": "sha512-QP88BAKvMam/3NxH6vj2o21R6MjxZUAd6nlwAS/pnGvN9IVLocLHxGYIzFhg6fUQ+5th6P4dv4eW9jX3DSIj7A==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=12"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/jonschlinkert"
+      }
+    },
+    "node_modules/to-regex-range": {
+      "version": "5.0.1",
+      "resolved": "https://registry.npmjs.org/to-regex-range/-/to-regex-range-5.0.1.tgz",
+      "integrity": "sha512-65P7iz6X5yEr1cwcgvQxbbIw7Uk3gOy5dIdtZ4rDveLqhrdJP+Li/Hx6tyK0NEb+2GCyneCMJiGqrADCSNk8sQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "is-number": "^7.0.0"
+      },
+      "engines": {
+        "node": ">=8.0"
+      }
+    },
+    "node_modules/universalify": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/universalify/-/universalify-2.0.1.tgz",
+      "integrity": "sha512-gptHNQghINnc/vTGIk0SOFGFNXw7JVrlRUtConJRlvaw6DuX0wO5Jeko9sWrMBhh+PsYAZ7oXAiOnf/UKogyiw==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">= 10.0.0"
+      }
+    },
+    "node_modules/update-browserslist-db": {
+      "version": "1.2.3",
+      "resolved": "https://registry.npmjs.org/update-browserslist-db/-/update-browserslist-db-1.2.3.tgz",
+      "integrity": "sha512-Js0m9cx+qOgDxo0eMiFGEueWztz+d4+M3rGlmKPT+T4IS/jP4ylw3Nwpu6cpTTP8R1MAC1kF4VbdLt3ARf209w==",
+      "dev": true,
+      "funding": [
+        {
+          "type": "opencollective",
+          "url": "https://opencollective.com/browserslist"
+        },
+        {
+          "type": "tidelift",
+          "url": "https://tidelift.com/funding/github/npm/browserslist"
+        },
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/ai"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "escalade": "^3.2.0",
+        "picocolors": "^1.1.1"
+      },
+      "bin": {
+        "update-browserslist-db": "cli.js"
+      },
+      "peerDependencies": {
+        "browserslist": ">= 4.21.0"
+      }
+    },
+    "node_modules/wrap-ansi": {
+      "version": "7.0.0",
+      "resolved": "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-7.0.0.tgz",
+      "integrity": "sha512-YVGIj2kamLSTxw6NsZjoBxfSwsn0ycdesmc4p+Q21c5zPuZ1pl+NfxVdxPtdHvmNVOQ6XSYG4AUtyt/Fi7D16Q==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "ansi-styles": "^4.0.0",
+        "string-width": "^4.1.0",
+        "strip-ansi": "^6.0.0"
+      },
+      "engines": {
+        "node": ">=10"
+      },
+      "funding": {
+        "url": "https://github.com/chalk/wrap-ansi?sponsor=1"
+      }
+    },
+    "node_modules/y18n": {
+      "version": "5.0.8",
+      "resolved": "https://registry.npmjs.org/y18n/-/y18n-5.0.8.tgz",
+      "integrity": "sha512-0pfFzegeDWJHJIAmTLRP2DwHjdF5s7jo9tuztdQxAhINCdvS+3nGINqPd00AphqJR/0LhANUS6/+7SCb98YOfA==",
+      "dev": true,
+      "license": "ISC",
+      "engines": {
+        "node": ">=10"
+      }
+    },
+    "node_modules/yaml": {
+      "version": "2.8.3",
+      "resolved": "https://registry.npmjs.org/yaml/-/yaml-2.8.3.tgz",
+      "integrity": "sha512-AvbaCLOO2Otw/lW5bmh9d/WEdcDFdQp2Z2ZUH3pX9U2ihyUY0nvLv7J6TrWowklRGPYbB/IuIMfYgxaCPg5Bpg==",
+      "dev": true,
+      "license": "ISC",
+      "bin": {
+        "yaml": "bin.mjs"
+      },
+      "engines": {
+        "node": ">= 14.6"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/eemeli"
+      }
+    },
+    "node_modules/yargs": {
+      "version": "17.7.2",
+      "resolved": "https://registry.npmjs.org/yargs/-/yargs-17.7.2.tgz",
+      "integrity": "sha512-7dSzzRQ++CKnNI/krKnYRV7JKKPUXMEh61soaHKg9mrWEhzFWhFnxPxGl+69cD1Ou63C13NUPCnmIcrvqCuM6w==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "cliui": "^8.0.1",
+        "escalade": "^3.1.1",
+        "get-caller-file": "^2.0.5",
+        "require-directory": "^2.1.1",
+        "string-width": "^4.2.3",
+        "y18n": "^5.0.5",
+        "yargs-parser": "^21.1.1"
+      },
+      "engines": {
+        "node": ">=12"
+      }
+    },
+    "node_modules/yargs-parser": {
+      "version": "21.1.1",
+      "resolved": "https://registry.npmjs.org/yargs-parser/-/yargs-parser-21.1.1.tgz",
+      "integrity": "sha512-tVpsJW7DdjecAiFpbIB1e3qxIQsE6NoPc5/eTdrbbIC4h0LVsWhnoa3g+m2HclBIujHzsxZ4VJVA+GUuc2/LBw==",
+      "dev": true,
+      "license": "ISC",
+      "engines": {
+        "node": ">=12"
+      }
+    }
+  }
+}
diff --git a/package.json b/package.json
new file mode 100644
index 00000000..6f1ee33f
--- /dev/null
+++ b/package.json
@@ -0,0 +1,10 @@
+{
+  "name": "pyopensci-hugo-site",
+  "private": true,
+  "description": "PostCSS deps for clean-hugo theme (Hugo asset pipeline)",
+  "devDependencies": {
+    "autoprefixer": "^10.4.24",
+    "postcss": "^8.5.6",
+    "postcss-cli": "^11.0.1"
+  }
+}
diff --git a/postcss.config.js b/postcss.config.js
new file mode 100644
index 00000000..90d9fffc
--- /dev/null
+++ b/postcss.config.js
@@ -0,0 +1,5 @@
+module.exports = {
+  plugins: {
+    autoprefixer: {},
+  },
+}
diff --git a/static/CNAME b/static/CNAME
new file mode 100644
index 00000000..b3eaf6ed
--- /dev/null
+++ b/static/CNAME
@@ -0,0 +1 @@
+www.pyopensci.org
diff --git a/static/android-chrome-192x192.png b/static/android-chrome-192x192.png
new file mode 100644
index 00000000..61654d3a
Binary files /dev/null and b/static/android-chrome-192x192.png differ
diff --git a/static/android-chrome-512x512.png b/static/android-chrome-512x512.png
new file mode 100644
index 00000000..cae01404
Binary files /dev/null and b/static/android-chrome-512x512.png differ
diff --git a/static/apple-touch-icon.png b/static/apple-touch-icon.png
new file mode 100644
index 00000000..621c0459
Binary files /dev/null and b/static/apple-touch-icon.png differ
diff --git a/static/favicon-16x16.png b/static/favicon-16x16.png
new file mode 100644
index 00000000..611737c7
Binary files /dev/null and b/static/favicon-16x16.png differ
diff --git a/static/favicon-32x32.png b/static/favicon-32x32.png
new file mode 100644
index 00000000..b9fcc186
Binary files /dev/null and b/static/favicon-32x32.png differ
diff --git a/static/favicon.ico b/static/favicon.ico
new file mode 100644
index 00000000..0e7e7d5e
Binary files /dev/null and b/static/favicon.ico differ
diff --git a/static/images/automata/finite_language_dfa.png b/static/images/automata/finite_language_dfa.png
new file mode 100644
index 00000000..1f813410
Binary files /dev/null and b/static/images/automata/finite_language_dfa.png differ
diff --git a/static/images/blog/2024/april/pyos-code-to-mod.png b/static/images/blog/2024/april/pyos-code-to-mod.png
new file mode 100644
index 00000000..55fe6738
Binary files /dev/null and b/static/images/blog/2024/april/pyos-code-to-mod.png differ
diff --git a/static/images/blog/2024/eric-ma-blog-post-header.png b/static/images/blog/2024/eric-ma-blog-post-header.png
new file mode 100644
index 00000000..03a7d136
Binary files /dev/null and b/static/images/blog/2024/eric-ma-blog-post-header.png differ
diff --git a/static/images/blog/2024/eric-ma-blog-post-header.webp b/static/images/blog/2024/eric-ma-blog-post-header.webp
new file mode 100644
index 00000000..608d4c09
Binary files /dev/null and b/static/images/blog/2024/eric-ma-blog-post-header.webp differ
diff --git a/static/images/blog/2024/july/pyopensci-community-lead-software-peer-review.png b/static/images/blog/2024/july/pyopensci-community-lead-software-peer-review.png
new file mode 100644
index 00000000..9ab087a1
Binary files /dev/null and b/static/images/blog/2024/july/pyopensci-community-lead-software-peer-review.png differ
diff --git a/static/images/blog/2024/july/pyopensci-constructive-peer-review.png b/static/images/blog/2024/july/pyopensci-constructive-peer-review.png
new file mode 100644
index 00000000..dc9ed93a
Binary files /dev/null and b/static/images/blog/2024/july/pyopensci-constructive-peer-review.png differ
diff --git a/static/images/blog/2024/july/pyopensci-have-you-created-package.png b/static/images/blog/2024/july/pyopensci-have-you-created-package.png
new file mode 100644
index 00000000..3fafdc10
Binary files /dev/null and b/static/images/blog/2024/july/pyopensci-have-you-created-package.png differ
diff --git a/static/images/blog/2024/july/pyopensci-leah-talk-pip-install-gdal.jpg b/static/images/blog/2024/july/pyopensci-leah-talk-pip-install-gdal.jpg
new file mode 100644
index 00000000..9cf20536
Binary files /dev/null and b/static/images/blog/2024/july/pyopensci-leah-talk-pip-install-gdal.jpg differ
diff --git a/static/images/blog/2024/july/pyopensci-package-guide-review.png b/static/images/blog/2024/july/pyopensci-package-guide-review.png
new file mode 100644
index 00000000..e4ac6ca6
Binary files /dev/null and b/static/images/blog/2024/july/pyopensci-package-guide-review.png differ
diff --git a/static/images/blog/2024/july/pyopensci-packaging-hatch.png b/static/images/blog/2024/july/pyopensci-packaging-hatch.png
new file mode 100644
index 00000000..56078add
Binary files /dev/null and b/static/images/blog/2024/july/pyopensci-packaging-hatch.png differ
diff --git a/static/images/blog/2024/july/pyopensci-packaging-tables.png b/static/images/blog/2024/july/pyopensci-packaging-tables.png
new file mode 100644
index 00000000..4e4f25b3
Binary files /dev/null and b/static/images/blog/2024/july/pyopensci-packaging-tables.png differ
diff --git a/static/images/blog/2024/july/pyopensci-partnerships-joss-astropy.png b/static/images/blog/2024/july/pyopensci-partnerships-joss-astropy.png
new file mode 100644
index 00000000..91ad691d
Binary files /dev/null and b/static/images/blog/2024/july/pyopensci-partnerships-joss-astropy.png differ
diff --git a/static/images/blog/2024/july/pyopensci-publication-partnership.png b/static/images/blog/2024/july/pyopensci-publication-partnership.png
new file mode 100644
index 00000000..493a31d4
Binary files /dev/null and b/static/images/blog/2024/july/pyopensci-publication-partnership.png differ
diff --git a/static/images/blog/2024/july/pyopensci-scipy-24-sprints.jpeg b/static/images/blog/2024/july/pyopensci-scipy-24-sprints.jpeg
new file mode 100644
index 00000000..9272da74
Binary files /dev/null and b/static/images/blog/2024/july/pyopensci-scipy-24-sprints.jpeg differ
diff --git a/static/images/blog/2024/july/pyopensci-sprints-day-1.png b/static/images/blog/2024/july/pyopensci-sprints-day-1.png
new file mode 100644
index 00000000..5dab8999
Binary files /dev/null and b/static/images/blog/2024/july/pyopensci-sprints-day-1.png differ
diff --git a/static/images/blog/2024/july/pyopensci-sprints-day-2.png b/static/images/blog/2024/july/pyopensci-sprints-day-2.png
new file mode 100644
index 00000000..89cb3cee
Binary files /dev/null and b/static/images/blog/2024/july/pyopensci-sprints-day-2.png differ
diff --git a/static/images/blog/2024/july/pyopensci-talk-leah-wasser-scipy24.jpg b/static/images/blog/2024/july/pyopensci-talk-leah-wasser-scipy24.jpg
new file mode 100644
index 00000000..bfb3babc
Binary files /dev/null and b/static/images/blog/2024/july/pyopensci-talk-leah-wasser-scipy24.jpg differ
diff --git a/static/images/blog/2024/july/pyopensci-what-if.png b/static/images/blog/2024/july/pyopensci-what-if.png
new file mode 100644
index 00000000..69df493e
Binary files /dev/null and b/static/images/blog/2024/july/pyopensci-what-if.png differ
diff --git a/static/images/blog/2024/july/pyopensci-workshop-successful-package.png b/static/images/blog/2024/july/pyopensci-workshop-successful-package.png
new file mode 100644
index 00000000..dd608559
Binary files /dev/null and b/static/images/blog/2024/july/pyopensci-workshop-successful-package.png differ
diff --git a/static/images/blog/2024/july/pyos-tutorial-scipy-24.jpeg b/static/images/blog/2024/july/pyos-tutorial-scipy-24.jpeg
new file mode 100644
index 00000000..476baf85
Binary files /dev/null and b/static/images/blog/2024/july/pyos-tutorial-scipy-24.jpeg differ
diff --git a/static/images/blog/2024/july/scipy-24-lobster-claw.jpeg b/static/images/blog/2024/july/scipy-24-lobster-claw.jpeg
new file mode 100644
index 00000000..18383d1a
Binary files /dev/null and b/static/images/blog/2024/july/scipy-24-lobster-claw.jpeg differ
diff --git a/static/images/blog/2024/july/scipy-24-pyopensci-package-submission-growth.png b/static/images/blog/2024/july/scipy-24-pyopensci-package-submission-growth.png
new file mode 100644
index 00000000..389fc880
Binary files /dev/null and b/static/images/blog/2024/july/scipy-24-pyopensci-package-submission-growth.png differ
diff --git a/static/images/blog/2024/june/pycon-python-packaging-confusion.png b/static/images/blog/2024/june/pycon-python-packaging-confusion.png
new file mode 100644
index 00000000..0a399823
Binary files /dev/null and b/static/images/blog/2024/june/pycon-python-packaging-confusion.png differ
diff --git a/static/images/blog/2024/june/pycon-python-packaging-too-many-options.png b/static/images/blog/2024/june/pycon-python-packaging-too-many-options.png
new file mode 100644
index 00000000..0274bdf9
Binary files /dev/null and b/static/images/blog/2024/june/pycon-python-packaging-too-many-options.png differ
diff --git a/static/images/blog/2024/june/pyopensci-issue-specific.png b/static/images/blog/2024/june/pyopensci-issue-specific.png
new file mode 100644
index 00000000..d60eb081
Binary files /dev/null and b/static/images/blog/2024/june/pyopensci-issue-specific.png differ
diff --git a/static/images/blog/2024/june/pyopensci-maintainer-python-packaging-frustration.png b/static/images/blog/2024/june/pyopensci-maintainer-python-packaging-frustration.png
new file mode 100644
index 00000000..7b8badcf
Binary files /dev/null and b/static/images/blog/2024/june/pyopensci-maintainer-python-packaging-frustration.png differ
diff --git a/static/images/blog/2024/june/pyopensci-packaging-guide-overview.png b/static/images/blog/2024/june/pyopensci-packaging-guide-overview.png
new file mode 100644
index 00000000..712c7738
Binary files /dev/null and b/static/images/blog/2024/june/pyopensci-packaging-guide-overview.png differ
diff --git a/static/images/blog/2024/june/pyopensci-python-packaging-create-early-wins.png b/static/images/blog/2024/june/pyopensci-python-packaging-create-early-wins.png
new file mode 100644
index 00000000..d7d94762
Binary files /dev/null and b/static/images/blog/2024/june/pyopensci-python-packaging-create-early-wins.png differ
diff --git a/static/images/blog/2024/june/pyopensci-python-packaging-fundamentals-first.png b/static/images/blog/2024/june/pyopensci-python-packaging-fundamentals-first.png
new file mode 100644
index 00000000..b83e4eef
Binary files /dev/null and b/static/images/blog/2024/june/pyopensci-python-packaging-fundamentals-first.png differ
diff --git a/static/images/blog/2024/june/pyopensci-python-packaging-people-can-help.png b/static/images/blog/2024/june/pyopensci-python-packaging-people-can-help.png
new file mode 100644
index 00000000..f1c0b504
Binary files /dev/null and b/static/images/blog/2024/june/pyopensci-python-packaging-people-can-help.png differ
diff --git a/static/images/blog/2024/june/pyopensci-python-packaging-tmo.png b/static/images/blog/2024/june/pyopensci-python-packaging-tmo.png
new file mode 100644
index 00000000..0ad7949b
Binary files /dev/null and b/static/images/blog/2024/june/pyopensci-python-packaging-tmo.png differ
diff --git a/static/images/blog/2024/june/pyopensci-sprint-label-issues.png b/static/images/blog/2024/june/pyopensci-sprint-label-issues.png
new file mode 100644
index 00000000..39c7ce89
Binary files /dev/null and b/static/images/blog/2024/june/pyopensci-sprint-label-issues.png differ
diff --git a/static/images/blog/2024/june/pyopensci-sprint-project-board.png b/static/images/blog/2024/june/pyopensci-sprint-project-board.png
new file mode 100644
index 00000000..467fc7f8
Binary files /dev/null and b/static/images/blog/2024/june/pyopensci-sprint-project-board.png differ
diff --git a/static/images/blog/2024/june/pyos-sprint-blog-learning.png b/static/images/blog/2024/june/pyos-sprint-blog-learning.png
new file mode 100644
index 00000000..059e4638
Binary files /dev/null and b/static/images/blog/2024/june/pyos-sprint-blog-learning.png differ
diff --git a/static/images/blog/2024/may/23-05-2024-get-involved.png b/static/images/blog/2024/may/23-05-2024-get-involved.png
new file mode 100644
index 00000000..e7faea78
Binary files /dev/null and b/static/images/blog/2024/may/23-05-2024-get-involved.png differ
diff --git a/static/images/blog/2024/may/april-workshop.png b/static/images/blog/2024/may/april-workshop.png
new file mode 100644
index 00000000..0854d507
Binary files /dev/null and b/static/images/blog/2024/may/april-workshop.png differ
diff --git a/static/images/blog/2024/may/fall-festival-save-the-date-2024.png b/static/images/blog/2024/may/fall-festival-save-the-date-2024.png
new file mode 100644
index 00000000..b6fad4ce
Binary files /dev/null and b/static/images/blog/2024/may/fall-festival-save-the-date-2024.png differ
diff --git a/static/images/blog/2024/may/juno-stickers.png b/static/images/blog/2024/may/juno-stickers.png
new file mode 100644
index 00000000..79646832
Binary files /dev/null and b/static/images/blog/2024/may/juno-stickers.png differ
diff --git a/static/images/blog/2024/may/leah-pycon.png b/static/images/blog/2024/may/leah-pycon.png
new file mode 100644
index 00000000..3b79e5fb
Binary files /dev/null and b/static/images/blog/2024/may/leah-pycon.png differ
diff --git a/static/images/blog/2024/may/leah-talking-pyconus-2024.jpg b/static/images/blog/2024/may/leah-talking-pyconus-2024.jpg
new file mode 100644
index 00000000..87788d53
Binary files /dev/null and b/static/images/blog/2024/may/leah-talking-pyconus-2024.jpg differ
diff --git a/static/images/blog/2024/may/oss-fall-festival.png b/static/images/blog/2024/may/oss-fall-festival.png
new file mode 100644
index 00000000..f1034399
Binary files /dev/null and b/static/images/blog/2024/may/oss-fall-festival.png differ
diff --git a/static/images/blog/2024/may/pyOS-fall-festival-square.png b/static/images/blog/2024/may/pyOS-fall-festival-square.png
new file mode 100644
index 00000000..cba6ac1e
Binary files /dev/null and b/static/images/blog/2024/may/pyOS-fall-festival-square.png differ
diff --git a/static/images/blog/2024/may/pyOS-open-science-festival.png b/static/images/blog/2024/may/pyOS-open-science-festival.png
new file mode 100644
index 00000000..84b19c1d
Binary files /dev/null and b/static/images/blog/2024/may/pyOS-open-science-festival.png differ
diff --git a/static/images/blog/2024/may/pycon-24-sprints-pyopensci.png b/static/images/blog/2024/may/pycon-24-sprints-pyopensci.png
new file mode 100644
index 00000000..28c89d2a
Binary files /dev/null and b/static/images/blog/2024/may/pycon-24-sprints-pyopensci.png differ
diff --git a/static/images/blog/2024/may/pycon-24-sprints-table-pyopensci.png b/static/images/blog/2024/may/pycon-24-sprints-table-pyopensci.png
new file mode 100644
index 00000000..5ebdc652
Binary files /dev/null and b/static/images/blog/2024/may/pycon-24-sprints-table-pyopensci.png differ
diff --git a/static/images/blog/2024/may/pycon-us-2024.png b/static/images/blog/2024/may/pycon-us-2024.png
new file mode 100644
index 00000000..9eb25a9b
Binary files /dev/null and b/static/images/blog/2024/may/pycon-us-2024.png differ
diff --git a/static/images/blog/2024/may/pycon-us-24-pyopensci-sprints-juno.png b/static/images/blog/2024/may/pycon-us-24-pyopensci-sprints-juno.png
new file mode 100644
index 00000000..bb01f438
Binary files /dev/null and b/static/images/blog/2024/may/pycon-us-24-pyopensci-sprints-juno.png differ
diff --git a/static/images/blog/2024/may/pyconus-2024-pyopensci-openspace.png b/static/images/blog/2024/may/pyconus-2024-pyopensci-openspace.png
new file mode 100644
index 00000000..6b3c7ac4
Binary files /dev/null and b/static/images/blog/2024/may/pyconus-2024-pyopensci-openspace.png differ
diff --git a/static/images/blog/2024/may/pyopensci-pyconus-2024-juno-thankyou.png b/static/images/blog/2024/may/pyopensci-pyconus-2024-juno-thankyou.png
new file mode 100644
index 00000000..c15024a7
Binary files /dev/null and b/static/images/blog/2024/may/pyopensci-pyconus-2024-juno-thankyou.png differ
diff --git a/static/images/blog/2024/may/pyopensci-too-many-python-packaging-options-pycon-talk-2024.png b/static/images/blog/2024/may/pyopensci-too-many-python-packaging-options-pycon-talk-2024.png
new file mode 100644
index 00000000..e8809d10
Binary files /dev/null and b/static/images/blog/2024/may/pyopensci-too-many-python-packaging-options-pycon-talk-2024.png differ
diff --git a/static/images/blog/2024/may/pyos-call-for-editors.png b/static/images/blog/2024/may/pyos-call-for-editors.png
new file mode 100644
index 00000000..6f2b689b
Binary files /dev/null and b/static/images/blog/2024/may/pyos-call-for-editors.png differ
diff --git a/static/images/blog/2024/may/pyos-june-newsletter.png b/static/images/blog/2024/may/pyos-june-newsletter.png
new file mode 100644
index 00000000..0e5df050
Binary files /dev/null and b/static/images/blog/2024/may/pyos-june-newsletter.png differ
diff --git a/static/images/blog/2024/may/zodipy.png b/static/images/blog/2024/may/zodipy.png
new file mode 100644
index 00000000..f3af93ed
Binary files /dev/null and b/static/images/blog/2024/may/zodipy.png differ
diff --git a/static/images/blog/2025/bof-group-inessa.png b/static/images/blog/2025/bof-group-inessa.png
new file mode 100644
index 00000000..c55dcc98
Binary files /dev/null and b/static/images/blog/2025/bof-group-inessa.png differ
diff --git a/static/images/blog/2025/bof-group-inessa.webp b/static/images/blog/2025/bof-group-inessa.webp
new file mode 100644
index 00000000..2bfd2538
Binary files /dev/null and b/static/images/blog/2025/bof-group-inessa.webp differ
diff --git a/static/images/blog/2025/carol-willing-micromentor.png b/static/images/blog/2025/carol-willing-micromentor.png
new file mode 100644
index 00000000..613becee
Binary files /dev/null and b/static/images/blog/2025/carol-willing-micromentor.png differ
diff --git a/static/images/blog/2025/carol-willing-micromentor.webp b/static/images/blog/2025/carol-willing-micromentor.webp
new file mode 100644
index 00000000..2bb8978c
Binary files /dev/null and b/static/images/blog/2025/carol-willing-micromentor.webp differ
diff --git a/static/images/blog/2025/executive-council-rotation-tracy.png b/static/images/blog/2025/executive-council-rotation-tracy.png
new file mode 100644
index 00000000..7e1191cb
Binary files /dev/null and b/static/images/blog/2025/executive-council-rotation-tracy.png differ
diff --git a/static/images/blog/2025/executive-council-rotation-tracy.webp b/static/images/blog/2025/executive-council-rotation-tracy.webp
new file mode 100644
index 00000000..eabe8d63
Binary files /dev/null and b/static/images/blog/2025/executive-council-rotation-tracy.webp differ
diff --git a/static/images/blog/2025/maintainers-summit-dan.png b/static/images/blog/2025/maintainers-summit-dan.png
new file mode 100644
index 00000000..d1d66a04
Binary files /dev/null and b/static/images/blog/2025/maintainers-summit-dan.png differ
diff --git a/static/images/blog/2025/maintainers-summit-dan.webp b/static/images/blog/2025/maintainers-summit-dan.webp
new file mode 100644
index 00000000..f371e4f6
Binary files /dev/null and b/static/images/blog/2025/maintainers-summit-dan.webp differ
diff --git a/static/images/blog/2025/meet-mandy-moore-comms.png b/static/images/blog/2025/meet-mandy-moore-comms.png
new file mode 100644
index 00000000..525fb619
Binary files /dev/null and b/static/images/blog/2025/meet-mandy-moore-comms.png differ
diff --git a/static/images/blog/2025/meet-mandy-moore-comms.webp b/static/images/blog/2025/meet-mandy-moore-comms.webp
new file mode 100644
index 00000000..c4d2c15a
Binary files /dev/null and b/static/images/blog/2025/meet-mandy-moore-comms.webp differ
diff --git a/static/images/blog/2025/pyos-sprint-group.png b/static/images/blog/2025/pyos-sprint-group.png
new file mode 100644
index 00000000..1d782184
Binary files /dev/null and b/static/images/blog/2025/pyos-sprint-group.png differ
diff --git a/static/images/blog/2025/pyos-sprint-group.webp b/static/images/blog/2025/pyos-sprint-group.webp
new file mode 100644
index 00000000..613963c7
Binary files /dev/null and b/static/images/blog/2025/pyos-sprint-group.webp differ
diff --git a/static/images/blog/2025/scipy-bof/breakout-group.png b/static/images/blog/2025/scipy-bof/breakout-group.png
new file mode 100644
index 00000000..00a2722c
Binary files /dev/null and b/static/images/blog/2025/scipy-bof/breakout-group.png differ
diff --git a/static/images/blog/2025/scipy-bof/breakout-group.webp b/static/images/blog/2025/scipy-bof/breakout-group.webp
new file mode 100644
index 00000000..d6f8e112
Binary files /dev/null and b/static/images/blog/2025/scipy-bof/breakout-group.webp differ
diff --git a/static/images/blog/2025/scipy-bof/community-discussion-2.png b/static/images/blog/2025/scipy-bof/community-discussion-2.png
new file mode 100644
index 00000000..5222260a
Binary files /dev/null and b/static/images/blog/2025/scipy-bof/community-discussion-2.png differ
diff --git a/static/images/blog/2025/scipy-bof/community-discussion-2.webp b/static/images/blog/2025/scipy-bof/community-discussion-2.webp
new file mode 100644
index 00000000..2c06e251
Binary files /dev/null and b/static/images/blog/2025/scipy-bof/community-discussion-2.webp differ
diff --git a/static/images/blog/2025/scipy-bof/community-discussion.png b/static/images/blog/2025/scipy-bof/community-discussion.png
new file mode 100644
index 00000000..1f19d2c1
Binary files /dev/null and b/static/images/blog/2025/scipy-bof/community-discussion.png differ
diff --git a/static/images/blog/2025/scipy-bof/community-discussion.webp b/static/images/blog/2025/scipy-bof/community-discussion.webp
new file mode 100644
index 00000000..83cacc8f
Binary files /dev/null and b/static/images/blog/2025/scipy-bof/community-discussion.webp differ
diff --git a/static/images/blog/2025/scipy-bof/plot-use-of-llms.png b/static/images/blog/2025/scipy-bof/plot-use-of-llms.png
new file mode 100644
index 00000000..f0d3f851
Binary files /dev/null and b/static/images/blog/2025/scipy-bof/plot-use-of-llms.png differ
diff --git a/static/images/blog/2025/scipy-bof/plot-use-of-llms.webp b/static/images/blog/2025/scipy-bof/plot-use-of-llms.webp
new file mode 100644
index 00000000..d6bb14fd
Binary files /dev/null and b/static/images/blog/2025/scipy-bof/plot-use-of-llms.webp differ
diff --git a/static/images/blog/2025/scipy-bof/results-open-code-painpoints-2.png b/static/images/blog/2025/scipy-bof/results-open-code-painpoints-2.png
new file mode 100644
index 00000000..ba8cc221
Binary files /dev/null and b/static/images/blog/2025/scipy-bof/results-open-code-painpoints-2.png differ
diff --git a/static/images/blog/2025/scipy-bof/results-open-code-painpoints-2.webp b/static/images/blog/2025/scipy-bof/results-open-code-painpoints-2.webp
new file mode 100644
index 00000000..54d9b104
Binary files /dev/null and b/static/images/blog/2025/scipy-bof/results-open-code-painpoints-2.webp differ
diff --git a/static/images/blog/2025/scipy-bof/results-open-code-painpoints.png b/static/images/blog/2025/scipy-bof/results-open-code-painpoints.png
new file mode 100644
index 00000000..429afa86
Binary files /dev/null and b/static/images/blog/2025/scipy-bof/results-open-code-painpoints.png differ
diff --git a/static/images/blog/2025/scipy-bof/results-open-code-painpoints.webp b/static/images/blog/2025/scipy-bof/results-open-code-painpoints.webp
new file mode 100644
index 00000000..922232c9
Binary files /dev/null and b/static/images/blog/2025/scipy-bof/results-open-code-painpoints.webp differ
diff --git a/static/images/blog/2025/scipy-workshop-teaching.png b/static/images/blog/2025/scipy-workshop-teaching.png
new file mode 100644
index 00000000..2f26f6df
Binary files /dev/null and b/static/images/blog/2025/scipy-workshop-teaching.png differ
diff --git a/static/images/blog/2025/scipy-workshop-teaching.webp b/static/images/blog/2025/scipy-workshop-teaching.webp
new file mode 100644
index 00000000..b36e753c
Binary files /dev/null and b/static/images/blog/2025/scipy-workshop-teaching.webp differ
diff --git a/static/images/blog/2025/tracey-james-scipy-2025.png b/static/images/blog/2025/tracey-james-scipy-2025.png
new file mode 100644
index 00000000..852a791e
Binary files /dev/null and b/static/images/blog/2025/tracey-james-scipy-2025.png differ
diff --git a/static/images/blog/2025/tracey-james-scipy-2025.webp b/static/images/blog/2025/tracey-james-scipy-2025.webp
new file mode 100644
index 00000000..c38540ac
Binary files /dev/null and b/static/images/blog/2025/tracey-james-scipy-2025.webp differ
diff --git a/static/images/blog/2025/waterfall-flikr.jpg b/static/images/blog/2025/waterfall-flikr.jpg
new file mode 100644
index 00000000..4482659a
Binary files /dev/null and b/static/images/blog/2025/waterfall-flikr.jpg differ
diff --git a/static/images/blog/2025/waterfall-flikr.webp b/static/images/blog/2025/waterfall-flikr.webp
new file mode 100644
index 00000000..9b12ebe3
Binary files /dev/null and b/static/images/blog/2025/waterfall-flikr.webp differ
diff --git a/static/images/blog/2026/pycon-us-2026-amanda-casari-keynote.png b/static/images/blog/2026/pycon-us-2026-amanda-casari-keynote.png
new file mode 100644
index 00000000..9317cbda
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-amanda-casari-keynote.png differ
diff --git a/static/images/blog/2026/pycon-us-2026-amanda-casari-keynote.webp b/static/images/blog/2026/pycon-us-2026-amanda-casari-keynote.webp
new file mode 100644
index 00000000..46970f90
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-amanda-casari-keynote.webp differ
diff --git a/static/images/blog/2026/pycon-us-2026-community-friends.png b/static/images/blog/2026/pycon-us-2026-community-friends.png
new file mode 100644
index 00000000..3074fd69
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-community-friends.png differ
diff --git a/static/images/blog/2026/pycon-us-2026-community-friends.webp b/static/images/blog/2026/pycon-us-2026-community-friends.webp
new file mode 100644
index 00000000..fb07d3b8
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-community-friends.webp differ
diff --git a/static/images/blog/2026/pycon-us-2026-genai-community-discussion.png b/static/images/blog/2026/pycon-us-2026-genai-community-discussion.png
new file mode 100644
index 00000000..7adefa0d
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-genai-community-discussion.png differ
diff --git a/static/images/blog/2026/pycon-us-2026-genai-community-discussion.webp b/static/images/blog/2026/pycon-us-2026-genai-community-discussion.webp
new file mode 100644
index 00000000..840d84e1
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-genai-community-discussion.webp differ
diff --git a/static/images/blog/2026/pycon-us-2026-genai-open-space.png b/static/images/blog/2026/pycon-us-2026-genai-open-space.png
new file mode 100644
index 00000000..2872df29
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-genai-open-space.png differ
diff --git a/static/images/blog/2026/pycon-us-2026-genai-open-space.webp b/static/images/blog/2026/pycon-us-2026-genai-open-space.webp
new file mode 100644
index 00000000..3bf78d8a
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-genai-open-space.webp differ
diff --git a/static/images/blog/2026/pycon-us-2026-maintainers-summit-cary-hatch-tools-track.png b/static/images/blog/2026/pycon-us-2026-maintainers-summit-cary-hatch-tools-track.png
new file mode 100644
index 00000000..5a5128db
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-maintainers-summit-cary-hatch-tools-track.png differ
diff --git a/static/images/blog/2026/pycon-us-2026-maintainers-summit-cary-hatch-tools-track.webp b/static/images/blog/2026/pycon-us-2026-maintainers-summit-cary-hatch-tools-track.webp
new file mode 100644
index 00000000..ddfa3971
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-maintainers-summit-cary-hatch-tools-track.webp differ
diff --git a/static/images/blog/2026/pycon-us-2026-maintainers-summit-discussion.png b/static/images/blog/2026/pycon-us-2026-maintainers-summit-discussion.png
new file mode 100644
index 00000000..0985537a
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-maintainers-summit-discussion.png differ
diff --git a/static/images/blog/2026/pycon-us-2026-maintainers-summit-discussion.webp b/static/images/blog/2026/pycon-us-2026-maintainers-summit-discussion.webp
new file mode 100644
index 00000000..5f0c4f09
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-maintainers-summit-discussion.webp differ
diff --git a/static/images/blog/2026/pycon-us-2026-maintainers-summit-felipe-talk.png b/static/images/blog/2026/pycon-us-2026-maintainers-summit-felipe-talk.png
new file mode 100644
index 00000000..b27e1d4c
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-maintainers-summit-felipe-talk.png differ
diff --git a/static/images/blog/2026/pycon-us-2026-maintainers-summit-felipe-talk.webp b/static/images/blog/2026/pycon-us-2026-maintainers-summit-felipe-talk.webp
new file mode 100644
index 00000000..5e362e4f
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-maintainers-summit-felipe-talk.webp differ
diff --git a/static/images/blog/2026/pycon-us-2026-maintainers-summit-genai-bof.png b/static/images/blog/2026/pycon-us-2026-maintainers-summit-genai-bof.png
new file mode 100644
index 00000000..077ca029
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-maintainers-summit-genai-bof.png differ
diff --git a/static/images/blog/2026/pycon-us-2026-maintainers-summit-genai-bof.webp b/static/images/blog/2026/pycon-us-2026-maintainers-summit-genai-bof.webp
new file mode 100644
index 00000000..62400da5
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-maintainers-summit-genai-bof.webp differ
diff --git a/static/images/blog/2026/pycon-us-2026-maintainers-summit-organizers-slide.png b/static/images/blog/2026/pycon-us-2026-maintainers-summit-organizers-slide.png
new file mode 100644
index 00000000..8b546a64
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-maintainers-summit-organizers-slide.png differ
diff --git a/static/images/blog/2026/pycon-us-2026-maintainers-summit-organizers-slide.webp b/static/images/blog/2026/pycon-us-2026-maintainers-summit-organizers-slide.webp
new file mode 100644
index 00000000..6aaa6785
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-maintainers-summit-organizers-slide.webp differ
diff --git a/static/images/blog/2026/pycon-us-2026-maintainers-summit-organizers.png b/static/images/blog/2026/pycon-us-2026-maintainers-summit-organizers.png
new file mode 100644
index 00000000..2ed00af7
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-maintainers-summit-organizers.png differ
diff --git a/static/images/blog/2026/pycon-us-2026-maintainers-summit-organizers.webp b/static/images/blog/2026/pycon-us-2026-maintainers-summit-organizers.webp
new file mode 100644
index 00000000..0d1bf811
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-maintainers-summit-organizers.webp differ
diff --git a/static/images/blog/2026/pycon-us-2026-maintainers-summit-room.png b/static/images/blog/2026/pycon-us-2026-maintainers-summit-room.png
new file mode 100644
index 00000000..ddcc1d7e
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-maintainers-summit-room.png differ
diff --git a/static/images/blog/2026/pycon-us-2026-maintainers-summit-room.webp b/static/images/blog/2026/pycon-us-2026-maintainers-summit-room.webp
new file mode 100644
index 00000000..87d717c2
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-maintainers-summit-room.webp differ
diff --git a/static/images/blog/2026/pycon-us-2026-maintainers-summit-roundtables.png b/static/images/blog/2026/pycon-us-2026-maintainers-summit-roundtables.png
new file mode 100644
index 00000000..fdd4cefa
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-maintainers-summit-roundtables.png differ
diff --git a/static/images/blog/2026/pycon-us-2026-maintainers-summit-roundtables.webp b/static/images/blog/2026/pycon-us-2026-maintainers-summit-roundtables.webp
new file mode 100644
index 00000000..260ff815
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-maintainers-summit-roundtables.webp differ
diff --git a/static/images/blog/2026/pycon-us-2026-sprint-attendees.png b/static/images/blog/2026/pycon-us-2026-sprint-attendees.png
new file mode 100644
index 00000000..21a40add
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-sprint-attendees.png differ
diff --git a/static/images/blog/2026/pycon-us-2026-sprint-attendees.webp b/static/images/blog/2026/pycon-us-2026-sprint-attendees.webp
new file mode 100644
index 00000000..7e1c68ce
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-sprint-attendees.webp differ
diff --git a/static/images/blog/2026/pycon-us-2026-sprint-contributors.png b/static/images/blog/2026/pycon-us-2026-sprint-contributors.png
new file mode 100644
index 00000000..d4f73f11
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-sprint-contributors.png differ
diff --git a/static/images/blog/2026/pycon-us-2026-sprint-contributors.webp b/static/images/blog/2026/pycon-us-2026-sprint-contributors.webp
new file mode 100644
index 00000000..fdfb1fb6
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-sprint-contributors.webp differ
diff --git a/static/images/blog/2026/pycon-us-2026-sprint-mentorship.png b/static/images/blog/2026/pycon-us-2026-sprint-mentorship.png
new file mode 100644
index 00000000..34a35c67
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-sprint-mentorship.png differ
diff --git a/static/images/blog/2026/pycon-us-2026-sprint-mentorship.webp b/static/images/blog/2026/pycon-us-2026-sprint-mentorship.webp
new file mode 100644
index 00000000..50eb112c
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-sprint-mentorship.webp differ
diff --git a/static/images/blog/2026/pycon-us-2026-sprint-room-wide.png b/static/images/blog/2026/pycon-us-2026-sprint-room-wide.png
new file mode 100644
index 00000000..7b54216b
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-sprint-room-wide.png differ
diff --git a/static/images/blog/2026/pycon-us-2026-sprint-room-wide.webp b/static/images/blog/2026/pycon-us-2026-sprint-room-wide.webp
new file mode 100644
index 00000000..6aa8d3e3
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-sprint-room-wide.webp differ
diff --git a/static/images/blog/2026/pycon-us-2026-sprint-round-table.png b/static/images/blog/2026/pycon-us-2026-sprint-round-table.png
new file mode 100644
index 00000000..bf040218
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-sprint-round-table.png differ
diff --git a/static/images/blog/2026/pycon-us-2026-sprint-round-table.webp b/static/images/blog/2026/pycon-us-2026-sprint-round-table.webp
new file mode 100644
index 00000000..c8b0c4fd
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-sprint-round-table.webp differ
diff --git a/static/images/blog/2026/pycon-us-2026-sprints-keynote-slide.png b/static/images/blog/2026/pycon-us-2026-sprints-keynote-slide.png
new file mode 100644
index 00000000..9b3a1012
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-sprints-keynote-slide.png differ
diff --git a/static/images/blog/2026/pycon-us-2026-sprints-keynote-slide.webp b/static/images/blog/2026/pycon-us-2026-sprints-keynote-slide.webp
new file mode 100644
index 00000000..3d06afee
Binary files /dev/null and b/static/images/blog/2026/pycon-us-2026-sprints-keynote-slide.webp differ
diff --git a/static/images/blog/2026/pycon-us-sprint-collaboration.png b/static/images/blog/2026/pycon-us-sprint-collaboration.png
new file mode 100644
index 00000000..1449af5b
Binary files /dev/null and b/static/images/blog/2026/pycon-us-sprint-collaboration.png differ
diff --git a/static/images/blog/2026/pycon-us-sprint-collaboration.webp b/static/images/blog/2026/pycon-us-sprint-collaboration.webp
new file mode 100644
index 00000000..519bf451
Binary files /dev/null and b/static/images/blog/2026/pycon-us-sprint-collaboration.webp differ
diff --git a/static/images/blog/headers/23-05-2024-call-for-editors.png b/static/images/blog/headers/23-05-2024-call-for-editors.png
new file mode 100644
index 00000000..1bee20d7
Binary files /dev/null and b/static/images/blog/headers/23-05-2024-call-for-editors.png differ
diff --git a/static/images/blog/headers/23-05-2024-call-for-editors.webp b/static/images/blog/headers/23-05-2024-call-for-editors.webp
new file mode 100644
index 00000000..ad65c317
Binary files /dev/null and b/static/images/blog/headers/23-05-2024-call-for-editors.webp differ
diff --git a/static/images/blog/headers/automata-header.png b/static/images/blog/headers/automata-header.png
new file mode 100644
index 00000000..93957d59
Binary files /dev/null and b/static/images/blog/headers/automata-header.png differ
diff --git a/static/images/blog/headers/automata-header.webp b/static/images/blog/headers/automata-header.webp
new file mode 100644
index 00000000..5fd7aeb7
Binary files /dev/null and b/static/images/blog/headers/automata-header.webp differ
diff --git a/static/images/blog/headers/call-for-editors.png b/static/images/blog/headers/call-for-editors.png
new file mode 100644
index 00000000..7e83a2e1
Binary files /dev/null and b/static/images/blog/headers/call-for-editors.png differ
diff --git a/static/images/blog/headers/call-for-editors.webp b/static/images/blog/headers/call-for-editors.webp
new file mode 100644
index 00000000..70c71360
Binary files /dev/null and b/static/images/blog/headers/call-for-editors.webp differ
diff --git a/static/images/blog/headers/david-nicholson-2023-header.png b/static/images/blog/headers/david-nicholson-2023-header.png
new file mode 100644
index 00000000..b5388ab7
Binary files /dev/null and b/static/images/blog/headers/david-nicholson-2023-header.png differ
diff --git a/static/images/blog/headers/david-nicholson-2023-header.webp b/static/images/blog/headers/david-nicholson-2023-header.webp
new file mode 100644
index 00000000..15d986a2
Binary files /dev/null and b/static/images/blog/headers/david-nicholson-2023-header.webp differ
diff --git a/static/images/blog/headers/eric-ma-blog-post-header.png b/static/images/blog/headers/eric-ma-blog-post-header.png
new file mode 100644
index 00000000..507075ff
Binary files /dev/null and b/static/images/blog/headers/eric-ma-blog-post-header.png differ
diff --git a/static/images/blog/headers/eric-ma-blog-post-header.webp b/static/images/blog/headers/eric-ma-blog-post-header.webp
new file mode 100644
index 00000000..608d4c09
Binary files /dev/null and b/static/images/blog/headers/eric-ma-blog-post-header.webp differ
diff --git a/static/images/blog/headers/eric-ma-header.png b/static/images/blog/headers/eric-ma-header.png
new file mode 100644
index 00000000..b21f4811
Binary files /dev/null and b/static/images/blog/headers/eric-ma-header.png differ
diff --git a/static/images/blog/headers/eric-ma-header.webp b/static/images/blog/headers/eric-ma-header.webp
new file mode 100644
index 00000000..1cb7c14b
Binary files /dev/null and b/static/images/blog/headers/eric-ma-header.webp differ
diff --git a/static/images/blog/headers/pandas.jpg b/static/images/blog/headers/pandas.jpg
new file mode 100644
index 00000000..b3702683
Binary files /dev/null and b/static/images/blog/headers/pandas.jpg differ
diff --git a/static/images/blog/headers/pandas.png b/static/images/blog/headers/pandas.png
new file mode 100644
index 00000000..abff5b83
Binary files /dev/null and b/static/images/blog/headers/pandas.png differ
diff --git a/static/images/blog/headers/pandas.webp b/static/images/blog/headers/pandas.webp
new file mode 100644
index 00000000..f8a5f44a
Binary files /dev/null and b/static/images/blog/headers/pandas.webp differ
diff --git a/static/images/blog/headers/pycon-us-2024-header.png b/static/images/blog/headers/pycon-us-2024-header.png
new file mode 100644
index 00000000..5d37cc88
Binary files /dev/null and b/static/images/blog/headers/pycon-us-2024-header.png differ
diff --git a/static/images/blog/headers/pycon-us-2024-header.webp b/static/images/blog/headers/pycon-us-2024-header.webp
new file mode 100644
index 00000000..a4be50a9
Binary files /dev/null and b/static/images/blog/headers/pycon-us-2024-header.webp differ
diff --git a/static/images/blog/headers/pycon-us-2024.png b/static/images/blog/headers/pycon-us-2024.png
new file mode 100644
index 00000000..e962ebb6
Binary files /dev/null and b/static/images/blog/headers/pycon-us-2024.png differ
diff --git a/static/images/blog/headers/pycon-us-2024.webp b/static/images/blog/headers/pycon-us-2024.webp
new file mode 100644
index 00000000..08297677
Binary files /dev/null and b/static/images/blog/headers/pycon-us-2024.webp differ
diff --git a/static/images/blog/headers/pycon-us-2026-header.png b/static/images/blog/headers/pycon-us-2026-header.png
new file mode 100644
index 00000000..672a86a0
Binary files /dev/null and b/static/images/blog/headers/pycon-us-2026-header.png differ
diff --git a/static/images/blog/headers/pycon-us-2026-header.webp b/static/images/blog/headers/pycon-us-2026-header.webp
new file mode 100644
index 00000000..ee051cc8
Binary files /dev/null and b/static/images/blog/headers/pycon-us-2026-header.webp differ
diff --git a/static/images/blog/headers/pyopensci-sustainability.png b/static/images/blog/headers/pyopensci-sustainability.png
new file mode 100644
index 00000000..e59c4565
Binary files /dev/null and b/static/images/blog/headers/pyopensci-sustainability.png differ
diff --git a/static/images/blog/headers/pyopensci-sustainability.webp b/static/images/blog/headers/pyopensci-sustainability.webp
new file mode 100644
index 00000000..d811604c
Binary files /dev/null and b/static/images/blog/headers/pyopensci-sustainability.webp differ
diff --git a/static/images/blog/headers/pyos-two-years.png b/static/images/blog/headers/pyos-two-years.png
new file mode 100644
index 00000000..97c33057
Binary files /dev/null and b/static/images/blog/headers/pyos-two-years.png differ
diff --git a/static/images/blog/headers/pyos-two-years.webp b/static/images/blog/headers/pyos-two-years.webp
new file mode 100644
index 00000000..2fe9b2a7
Binary files /dev/null and b/static/images/blog/headers/pyos-two-years.webp differ
diff --git a/static/images/blog/headers/sleptlet-header.png b/static/images/blog/headers/sleptlet-header.png
new file mode 100644
index 00000000..6c0814fc
Binary files /dev/null and b/static/images/blog/headers/sleptlet-header.png differ
diff --git a/static/images/blog/headers/sleptlet-header.webp b/static/images/blog/headers/sleptlet-header.webp
new file mode 100644
index 00000000..5b4ab22b
Binary files /dev/null and b/static/images/blog/headers/sleptlet-header.webp differ
diff --git a/static/images/blog/undefined.png b/static/images/blog/undefined.png
new file mode 100644
index 00000000..bd1a9e5c
Binary files /dev/null and b/static/images/blog/undefined.png differ
diff --git a/static/images/brooke-cagle-group-unsplash.png b/static/images/brooke-cagle-group-unsplash.png
new file mode 100644
index 00000000..4bbc9591
Binary files /dev/null and b/static/images/brooke-cagle-group-unsplash.png differ
diff --git a/static/images/brooke-cagle-unsplash.png b/static/images/brooke-cagle-unsplash.png
new file mode 100644
index 00000000..d719fb3d
Binary files /dev/null and b/static/images/brooke-cagle-unsplash.png differ
diff --git a/static/images/communities/astropy-banner.png b/static/images/communities/astropy-banner.png
new file mode 100644
index 00000000..79db6255
Binary files /dev/null and b/static/images/communities/astropy-banner.png differ
diff --git a/static/images/communities/astropy_project_logo.svg b/static/images/communities/astropy_project_logo.svg
new file mode 100644
index 00000000..890ea7f5
--- /dev/null
+++ b/static/images/communities/astropy_project_logo.svg
@@ -0,0 +1,123 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Generator: Adobe Illustrator 21.0.0, SVG Export Plug-In . SVG Version: 6.00 Build 0)  -->
+<svg version="1.1"
+	 id="svg2" xmlns:cc="http://creativecommons.org/ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:osb="http://www.openswatchbook.org/uri/2009/osb" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:svg="http://www.w3.org/2000/svg"
+	 xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" viewBox="0 0 452.3 156.7"
+	 style="enable-background:new 0 0 452.3 156.7;" xml:space="preserve">
+<style type="text/css">
+	.st0{fill:url(#path3837_1_);}
+	.st1{fill:none;stroke:#FFFFFF;stroke-width:13;}
+	.st2{fill:#FFFFFF;}
+	.st3{fill:#FFFFFF;stroke:#FFFFFF;stroke-width:2.3603;stroke-linecap:round;stroke-linejoin:round;}
+	.st4{fill:none;stroke:#FFFFFF;stroke-width:3.7264;}
+	.st5{fill:none;stroke:#FFFFFF;stroke-width:4.0254;}
+	.st6{fill:none;stroke:#FFFFFF;stroke-width:4.063;}
+	.st7{enable-background:new    ;}
+	.st8{fill:#4D4D4D;}
+	.st9{fill:#FF5000;}
+</style>
+<g>
+
+		<linearGradient id="path3837_1_" gradientUnits="userSpaceOnUse" x1="-737.8835" y1="1639.9272" x2="-817.2668" y2="1735.7957" gradientTransform="matrix(1.0651 -0.9041 0.8901 1.0732 -593.9965 -2438.5088)">
+		<stop  offset="0" style="stop-color:#FFA900"/>
+		<stop  offset="1" style="stop-color:#FD0000"/>
+	</linearGradient>
+	<path id="path3837" class="st0" d="M140.9,25.4c23.8,28.7,16,75.1-17.5,103.6s-80,28.2-103.9-0.5l0,0C-4.4,99.7,3.5,53.3,37,24.9
+		S117-3.3,140.9,25.4L140.9,25.4z"/>
+	<path id="path5413" class="st1" d="M82.1,75.6C60.7,56.3,48.5,84,59.9,101.1c12.5,18.8,39.4,18.4,55.2,4.3c20-17.8,19.5-49.7,2-69"
+		/>
+	<path id="path3819" class="st2" d="M95,91.3c-4.8,4.7-16.1,2.6-25.3-4.5l0,0C60.5,79.6,57,70,61.8,65.4l0,0
+		c4.8-4.7,16.1-2.6,25.3,4.5l0,0C96.3,77,99.9,86.6,95,91.3L95,91.3z"/>
+	<path id="path3853" class="st3" d="M101.1,28.5l9.3,15.7L124.7,30l-18.1-7.6L101.1,28.5z"/>
+	<g id="g3804" transform="matrix(0.95039189,0,0,0.93299787,-2.487134,-0.56516029)">
+		<path id="path3855-7" class="st4" d="M105.7,23l-1.6-9.7l0.1,0.3l0,0"/>
+		<path id="path3855-7-0" class="st5" d="M95.6,22.1l10.7,0.5H106l0,0"/>
+		<path id="path3855-7-05" class="st6" d="M111.9,27.7l-6.8-5.4l0.3,0.2l0,0"/>
+	</g>
+	<path id="path3942" class="st1" d="M51.8,131.2c2.4,2.1,10.5,5.5,13.3,9c2.9,3.6,2.4,7.8,2.4,10.2"/>
+	<path id="path2987-5" class="st1" d="M76.7,83.7c26.2,14.4,31.4-16,15.8-30.4c-17.2-15.9-44-9.3-56.3,8.4
+		c-15.8,22.6-7.1,54.6,15.6,69.6c0.8,0.6,1.7,1.1,2.6,1.6"/>
+</g>
+<g class="st7">
+	<path class="st8" d="M190.2,89.1h-21.7l-5.7,18.2h-7.7l20.2-59.7h8.6l20.2,59.7h-8.1L190.2,89.1z M188.2,83l-2.8-9.1
+		c-1.1-3.3-2.1-6.7-3.1-10c-1-3.3-1.9-6.7-2.9-10.1h-0.4c-0.9,3.5-1.9,6.8-2.8,10.1c-1,3.3-2,6.6-3.1,10l-2.8,9.1H188.2z"/>
+	<path class="st8" d="M225.3,108.4c-3.2,0-6.2-0.6-9-1.7c-2.9-1.2-5.3-2.6-7.5-4.4l3.7-5c1.9,1.6,3.9,2.9,6,3.8c2,1,4.4,1.5,7.1,1.5
+		c2.9,0,5.1-0.7,6.6-2c1.5-1.3,2.2-3,2.2-4.9c0-1.2-0.3-2.2-0.9-3c-0.6-0.8-1.4-1.6-2.3-2.2c-0.9-0.6-2-1.2-3.2-1.7
+		c-1.2-0.5-2.4-1-3.6-1.5c-1.6-0.5-3.2-1.2-4.7-1.9c-1.6-0.7-3-1.5-4.2-2.5c-1.2-1-2.3-2.2-3-3.5c-0.8-1.3-1.2-2.9-1.2-4.8
+		c0-1.8,0.3-3.4,1-5c0.7-1.5,1.7-2.9,3-4c1.3-1.1,2.9-2,4.8-2.6c1.9-0.6,4-1,6.4-1c2.8,0,5.4,0.5,7.7,1.5c2.3,1,4.4,2.2,6.1,3.5
+		l-3.5,4.7c-1.5-1.2-3.1-2.1-4.7-2.8c-1.6-0.7-3.4-1.1-5.4-1.1c-2.8,0-4.8,0.6-6.1,1.9c-1.3,1.3-2,2.8-2,4.5c0,1,0.3,1.9,0.8,2.7
+		c0.5,0.8,1.3,1.4,2.2,2c0.9,0.6,2,1.1,3.1,1.5s2.4,0.9,3.7,1.4c1.6,0.6,3.2,1.2,4.8,1.9c1.6,0.7,3,1.5,4.3,2.5
+		c1.3,1,2.3,2.2,3.1,3.7s1.2,3.2,1.2,5.3c0,1.8-0.3,3.5-1,5.1c-0.7,1.6-1.7,3-3.1,4.2c-1.4,1.2-3.1,2.2-5.1,2.9
+		C230.2,108,227.9,108.4,225.3,108.4z"/>
+	<path class="st8" d="M264,108.4c-2.4,0-4.4-0.4-6-1.1c-1.6-0.7-2.9-1.7-3.9-3s-1.7-2.8-2.1-4.6c-0.4-1.8-0.6-3.8-0.6-6V69.1h-6.6
+		v-5.6l6.9-0.5l0.9-12.4h6.3V63h11.9v6.1h-11.9v24.6c0,2.7,0.5,4.8,1.5,6.3c1,1.5,2.8,2.2,5.3,2.2c0.8,0,1.6-0.1,2.5-0.4
+		c0.9-0.2,1.7-0.5,2.5-0.8l1.5,5.6c-1.2,0.4-2.5,0.8-4,1.1C266.8,108.2,265.4,108.4,264,108.4z"/>
+	<path class="st8" d="M280.8,63h6.2l0.6,8h0.3c1.5-2.8,3.4-5,5.5-6.6c2.2-1.6,4.5-2.5,7.1-2.5c1.8,0,3.3,0.3,4.7,0.9l-1.5,6.6
+		c-0.7-0.2-1.4-0.4-2-0.5c-0.6-0.1-1.4-0.2-2.3-0.2c-1.9,0-3.8,0.8-5.9,2.3c-2,1.5-3.8,4.2-5.3,7.9v28.4h-7.5V63z"/>
+	<path class="st8" d="M328.7,108.4c-2.7,0-5.3-0.5-7.8-1.5s-4.6-2.5-6.5-4.5c-1.9-2-3.4-4.4-4.5-7.3c-1.1-2.9-1.7-6.1-1.7-9.8
+		c0-3.7,0.6-7,1.7-9.9c1.1-2.9,2.6-5.3,4.5-7.3c1.9-2,4-3.5,6.5-4.6c2.5-1,5.1-1.5,7.8-1.5c2.7,0,5.3,0.5,7.8,1.5
+		c2.5,1,4.6,2.5,6.5,4.6c1.9,2,3.4,4.4,4.5,7.3c1.1,2.9,1.7,6.2,1.7,9.9c0,3.6-0.6,6.9-1.7,9.8c-1.1,2.9-2.6,5.3-4.5,7.3
+		c-1.9,2-4,3.5-6.5,4.5S331.4,108.4,328.7,108.4z M328.7,102.2c1.9,0,3.6-0.4,5.2-1.2c1.6-0.8,2.9-2,4-3.5c1.1-1.5,2-3.3,2.6-5.3
+		c0.6-2.1,0.9-4.4,0.9-6.9c0-2.5-0.3-4.9-0.9-7c-0.6-2.1-1.5-3.9-2.6-5.4c-1.1-1.5-2.5-2.7-4-3.5c-1.6-0.8-3.3-1.2-5.2-1.2
+		c-1.9,0-3.6,0.4-5.2,1.2c-1.6,0.8-2.9,2-4,3.5c-1.1,1.5-2,3.3-2.6,5.4c-0.6,2.1-0.9,4.4-0.9,7c0,2.5,0.3,4.9,0.9,6.9
+		c0.6,2.1,1.5,3.8,2.6,5.3c1.1,1.5,2.5,2.6,4,3.5C325,101.8,326.8,102.2,328.7,102.2z"/>
+</g>
+<g class="st7">
+	<path class="st9" d="M362.3,63.6h3.5l0.4,5.5h0.3c2.1-1.7,4.4-3.2,7-4.5c2.5-1.3,5.1-2,7.9-2c5.8,0,10.2,2,13.1,6.1
+		c2.9,4,4.4,9.5,4.4,16.2c0,3.7-0.5,7-1.5,9.9c-1,2.9-2.4,5.4-4.2,7.4c-1.8,2-3.9,3.6-6.2,4.6c-2.3,1.1-4.8,1.6-7.3,1.6
+		c-2.1,0-4.2-0.5-6.4-1.4c-2.2-0.9-4.4-2.3-6.7-4v24h-4V63.6z M366.3,99.2c2.5,2.1,4.9,3.5,7.1,4.4c2.2,0.9,4.1,1.3,5.8,1.3
+		c2.2,0,4.2-0.5,6.1-1.5c1.9-1,3.5-2.3,4.8-4.1c1.3-1.8,2.4-3.9,3.1-6.3c0.8-2.5,1.1-5.2,1.1-8.1c0-2.7-0.3-5.2-0.8-7.5
+		c-0.5-2.3-1.3-4.3-2.4-6c-1.1-1.7-2.5-3-4.3-3.9c-1.8-0.9-3.9-1.4-6.4-1.4c-2.2,0-4.4,0.6-6.8,1.9c-2.3,1.2-4.8,3-7.5,5.3V99.2z"/>
+	<path class="st9" d="M410.1,127.2c-1.6,0-3.1-0.3-4.5-0.9l0.9-3.5c0.5,0.2,1,0.3,1.6,0.5c0.6,0.2,1.2,0.2,1.9,0.2
+		c2.7,0,5-1.1,6.8-3.3c1.8-2.2,3.3-4.9,4.4-8.3l1.2-3.8l-17.9-44.5h4.4l10.6,27.5c0.7,1.8,1.4,3.8,2.2,6c0.8,2.2,1.7,4.2,2.5,6.2
+		h0.4c0.7-1.9,1.3-4,2-6.2c0.7-2.2,1.3-4.2,2-6l9.4-27.5h4.1l-17.3,49.1c-0.6,1.8-1.4,3.6-2.2,5.4c-0.9,1.8-1.9,3.3-3.1,4.6
+		c-1.2,1.3-2.5,2.4-4.1,3.2C413.8,126.8,412.1,127.2,410.1,127.2z"/>
+</g>
+<g class="st7">
+	<path class="st8" d="M160.9,21.9h-5.5v-1h12.1v1h-5.5V38h-1.2V21.9z"/>
+	<path class="st8" d="M170.7,19.3h1.1v8.2c0.7-0.7,1.3-1.2,2-1.6c0.7-0.4,1.4-0.6,2.3-0.6c1.3,0,2.3,0.4,2.9,1.2
+		c0.6,0.8,0.9,2,0.9,3.6v8h-1.1v-7.9c0-1.3-0.2-2.3-0.7-3s-1.2-0.9-2.2-0.9c-0.7,0-1.4,0.2-2,0.6c-0.6,0.4-1.3,1-2.1,1.8V38h-1.1
+		V19.3z"/>
+	<path class="st8" d="M189.1,38.3c-0.8,0-1.5-0.1-2.2-0.4c-0.7-0.3-1.3-0.7-1.8-1.3s-0.9-1.2-1.2-2.1c-0.3-0.8-0.5-1.7-0.5-2.7
+		s0.2-1.9,0.5-2.8c0.3-0.8,0.7-1.5,1.2-2.1c0.5-0.6,1.1-1,1.7-1.3c0.6-0.3,1.3-0.5,2-0.5c1.5,0,2.7,0.5,3.5,1.5
+		c0.8,1,1.3,2.4,1.3,4.3c0,0.2,0,0.3,0,0.5c0,0.2,0,0.3-0.1,0.5h-9c0,0.8,0.1,1.5,0.4,2.2c0.2,0.7,0.5,1.2,0.9,1.7
+		c0.4,0.5,0.9,0.8,1.5,1.1c0.6,0.3,1.2,0.4,1.9,0.4c0.7,0,1.3-0.1,1.8-0.3s1.1-0.5,1.5-0.8l0.5,0.9c-0.5,0.3-1.1,0.6-1.7,0.8
+		S190.1,38.3,189.1,38.3z M192.5,30.9c0-1.6-0.3-2.8-1-3.6c-0.7-0.8-1.6-1.2-2.7-1.2c-0.5,0-1,0.1-1.5,0.3s-0.9,0.5-1.3,0.9
+		c-0.4,0.4-0.7,0.9-1,1.5c-0.3,0.6-0.4,1.3-0.5,2H192.5z"/>
+</g>
+<g>
+	<g class="st7">
+		<path class="st9" d="M241.7,117.8h5.7c1.3,0,2.4,0.1,3.4,0.3c1,0.2,1.9,0.6,2.6,1.1c0.7,0.5,1.2,1.2,1.6,2s0.6,1.8,0.6,3
+			c0,2.3-0.7,4-2.1,5.1c-1.4,1.1-3.4,1.7-5.9,1.7h-4.2v9.9h-1.6V117.8z M247.1,129.5c2.3,0,4-0.4,5.1-1.3s1.7-2.2,1.7-4.1
+			c0-1.9-0.6-3.3-1.7-4c-1.2-0.7-2.9-1.1-5.2-1.1h-3.7v10.4H247.1z"/>
+		<path class="st9" d="M260.3,124h1.3l0.1,3.1h0.1c0.5-1.1,1.2-1.9,2-2.6s1.7-1,2.7-1c0.3,0,0.6,0,0.9,0.1s0.5,0.1,0.8,0.3l-0.3,1.4
+			c-0.3-0.1-0.5-0.2-0.7-0.2c-0.2,0-0.5-0.1-0.8-0.1c-0.7,0-1.5,0.3-2.3,1c-0.8,0.6-1.5,1.8-2.2,3.3v11.4h-1.5V124z"/>
+		<path class="st9" d="M276.8,141.2c-1,0-1.9-0.2-2.8-0.6c-0.9-0.4-1.7-1-2.3-1.7c-0.7-0.7-1.2-1.7-1.6-2.7
+			c-0.4-1.1-0.6-2.3-0.6-3.7c0-1.4,0.2-2.7,0.6-3.8c0.4-1.1,0.9-2,1.6-2.8c0.7-0.7,1.5-1.3,2.3-1.7c0.9-0.4,1.8-0.6,2.8-0.6
+			s1.9,0.2,2.8,0.6c0.9,0.4,1.7,1,2.4,1.7c0.7,0.7,1.2,1.7,1.6,2.8c0.4,1.1,0.6,2.4,0.6,3.8c0,1.4-0.2,2.6-0.6,3.7
+			c-0.4,1.1-0.9,2-1.6,2.7c-0.7,0.7-1.5,1.3-2.4,1.7C278.7,141,277.7,141.2,276.8,141.2z M276.8,139.9c0.8,0,1.6-0.2,2.3-0.5
+			c0.7-0.4,1.3-0.9,1.8-1.5s0.9-1.4,1.2-2.3c0.3-0.9,0.4-1.9,0.4-3c0-1.1-0.1-2.1-0.4-3c-0.3-0.9-0.7-1.7-1.2-2.4s-1.1-1.2-1.8-1.5
+			c-0.7-0.4-1.5-0.5-2.3-0.5s-1.6,0.2-2.3,0.5c-0.7,0.4-1.3,0.9-1.8,1.5s-0.9,1.5-1.2,2.4c-0.3,0.9-0.4,1.9-0.4,3
+			c0,1.1,0.1,2.1,0.4,3c0.3,0.9,0.7,1.7,1.2,2.3s1.1,1.2,1.8,1.5C275.2,139.7,275.9,139.9,276.8,139.9z"/>
+		<path class="st9" d="M286.9,148.8c-0.4,0-0.8,0-1.2-0.1c-0.4-0.1-0.7-0.2-1-0.3l0.4-1.3c0.2,0.1,0.5,0.1,0.8,0.2
+			c0.3,0.1,0.6,0.1,0.9,0.1c0.9,0,1.5-0.3,1.8-1s0.4-1.6,0.4-2.6V124h1.5v19.9c0,1.7-0.3,2.9-0.9,3.7
+			C289.1,148.4,288.2,148.8,286.9,148.8z M289.9,120c-0.4,0-0.7-0.1-1-0.4c-0.3-0.3-0.4-0.6-0.4-1c0-0.4,0.1-0.8,0.4-1
+			c0.3-0.2,0.6-0.4,1-0.4c0.4,0,0.7,0.1,1,0.4c0.3,0.2,0.4,0.6,0.4,1c0,0.4-0.1,0.7-0.4,1C290.6,119.8,290.2,120,289.9,120z"/>
+		<path class="st9" d="M303.1,141.2c-1,0-2-0.2-3-0.6s-1.7-1-2.4-1.7s-1.2-1.7-1.6-2.8c-0.4-1.1-0.6-2.3-0.6-3.7
+			c0-1.4,0.2-2.6,0.6-3.7c0.4-1.1,0.9-2,1.6-2.8c0.7-0.8,1.4-1.3,2.3-1.8s1.7-0.6,2.7-0.6c2,0,3.5,0.7,4.6,2
+			c1.1,1.4,1.7,3.3,1.7,5.7c0,0.2,0,0.4,0,0.6c0,0.2,0,0.4-0.1,0.6h-11.8c0,1.1,0.2,2,0.5,2.9c0.3,0.9,0.7,1.7,1.2,2.3
+			c0.5,0.6,1.2,1.1,1.9,1.5c0.8,0.4,1.6,0.5,2.5,0.5c0.9,0,1.7-0.1,2.4-0.4c0.7-0.3,1.4-0.6,2-1.1l0.6,1.2c-0.7,0.4-1.4,0.8-2.2,1.1
+			C305.3,141.1,304.3,141.2,303.1,141.2z M307.5,131.4c0-2.2-0.4-3.8-1.3-4.8c-0.9-1.1-2-1.6-3.5-1.6c-0.7,0-1.4,0.1-2,0.4
+			c-0.6,0.3-1.2,0.7-1.7,1.3c-0.5,0.6-0.9,1.2-1.3,2c-0.3,0.8-0.5,1.7-0.6,2.7H307.5z"/>
+		<path class="st9" d="M319.5,141.2c-1.1,0-2.1-0.2-3-0.6c-0.9-0.4-1.7-1-2.4-1.7c-0.7-0.7-1.2-1.7-1.6-2.7s-0.6-2.3-0.6-3.7
+			c0-1.4,0.2-2.7,0.6-3.8c0.4-1.1,1-2,1.6-2.8c0.7-0.7,1.5-1.3,2.4-1.7c0.9-0.4,1.9-0.6,2.9-0.6c1.1,0,2.1,0.2,2.8,0.6
+			s1.4,0.9,2,1.4l-0.9,1.1c-0.5-0.5-1.1-0.9-1.7-1.3c-0.6-0.3-1.4-0.5-2.2-0.5c-0.8,0-1.6,0.2-2.3,0.5c-0.7,0.4-1.3,0.9-1.9,1.5
+			c-0.5,0.7-1,1.5-1.3,2.4c-0.3,0.9-0.5,1.9-0.5,3c0,1.1,0.1,2.1,0.4,3c0.3,0.9,0.7,1.7,1.2,2.3c0.5,0.7,1.1,1.2,1.9,1.5
+			c0.7,0.4,1.6,0.5,2.4,0.5c0.9,0,1.7-0.2,2.4-0.6s1.4-0.8,2-1.4l0.8,1.1c-0.7,0.6-1.5,1.2-2.4,1.6S320.6,141.2,319.5,141.2z"/>
+		<path class="st9" d="M332.9,141.2c-0.8,0-1.5-0.1-2-0.4c-0.5-0.2-0.9-0.6-1.3-1s-0.5-1-0.7-1.6c-0.1-0.6-0.2-1.3-0.2-2.1v-10.8
+			h-2.6v-1.2l2.6-0.1l0.2-4.9h1.3v4.9h4.8v1.3h-4.8v11c0,0.5,0,1,0.1,1.5c0.1,0.4,0.2,0.8,0.4,1.1c0.2,0.3,0.5,0.6,0.8,0.7
+			c0.4,0.2,0.8,0.3,1.4,0.3c0.3,0,0.7-0.1,1-0.2s0.7-0.2,1-0.4l0.4,1.3c-0.5,0.2-1,0.3-1.4,0.5C333.7,141.2,333.3,141.2,332.9,141.2
+			z"/>
+	</g>
+</g>
+</svg>
diff --git a/static/images/desola-lanre-ologun-unsplash.png b/static/images/desola-lanre-ologun-unsplash.png
new file mode 100644
index 00000000..3b89b63f
Binary files /dev/null and b/static/images/desola-lanre-ologun-unsplash.png differ
diff --git a/static/images/events/bof-session-scipy-2025.png b/static/images/events/bof-session-scipy-2025.png
new file mode 100644
index 00000000..37c4c5c7
Binary files /dev/null and b/static/images/events/bof-session-scipy-2025.png differ
diff --git a/static/images/events/community-call-pavithra-may-2025.png b/static/images/events/community-call-pavithra-may-2025.png
new file mode 100644
index 00000000..fe3e6ed7
Binary files /dev/null and b/static/images/events/community-call-pavithra-may-2025.png differ
diff --git a/static/images/events/community-call-pavithra-may-2025.webp b/static/images/events/community-call-pavithra-may-2025.webp
new file mode 100644
index 00000000..3596c036
Binary files /dev/null and b/static/images/events/community-call-pavithra-may-2025.webp differ
diff --git a/static/images/events/fall-festival-2024-stats.png b/static/images/events/fall-festival-2024-stats.png
new file mode 100644
index 00000000..ee6f42e2
Binary files /dev/null and b/static/images/events/fall-festival-2024-stats.png differ
diff --git a/static/images/events/fall-festival-2024-stats.webp b/static/images/events/fall-festival-2024-stats.webp
new file mode 100644
index 00000000..724ad3a1
Binary files /dev/null and b/static/images/events/fall-festival-2024-stats.webp differ
diff --git a/static/images/events/fall-festival-blog-keynote-speakers.png b/static/images/events/fall-festival-blog-keynote-speakers.png
new file mode 100644
index 00000000..d8f8caea
Binary files /dev/null and b/static/images/events/fall-festival-blog-keynote-speakers.png differ
diff --git a/static/images/events/fall-festival-blog-keynote-speakers.webp b/static/images/events/fall-festival-blog-keynote-speakers.webp
new file mode 100644
index 00000000..7a82e324
Binary files /dev/null and b/static/images/events/fall-festival-blog-keynote-speakers.webp differ
diff --git a/static/images/events/fall-festival-favorite-day.png b/static/images/events/fall-festival-favorite-day.png
new file mode 100644
index 00000000..2b373a03
Binary files /dev/null and b/static/images/events/fall-festival-favorite-day.png differ
diff --git a/static/images/events/fall-festival-favorite-day.webp b/static/images/events/fall-festival-favorite-day.webp
new file mode 100644
index 00000000..a338a223
Binary files /dev/null and b/static/images/events/fall-festival-favorite-day.webp differ
diff --git a/static/images/events/fall-festival-thank-you.png b/static/images/events/fall-festival-thank-you.png
new file mode 100644
index 00000000..0187f434
Binary files /dev/null and b/static/images/events/fall-festival-thank-you.png differ
diff --git a/static/images/events/fall-festival-thank-you.webp b/static/images/events/fall-festival-thank-you.webp
new file mode 100644
index 00000000..8f5e5cfc
Binary files /dev/null and b/static/images/events/fall-festival-thank-you.webp differ
diff --git a/static/images/events/people-table-working-2.svg b/static/images/events/people-table-working-2.svg
new file mode 100644
index 00000000..91fa5e80
--- /dev/null
+++ b/static/images/events/people-table-working-2.svg
@@ -0,0 +1 @@
+<?xml version="1.0" encoding="UTF-8"?><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1920 1080"><defs><style>.cls-1{fill:#904f9c;}.cls-2{fill:#1e0442;}.cls-3{fill:#fcf7df;}.cls-4{fill:#f9848c;}.cls-5{fill:#4b2068;}.cls-6{fill:#1b0140;}.cls-7{fill:#e54976;}.cls-8{fill:#c03666;}.cls-9{fill:#6b338c;}.cls-10{fill:#88c0af;}.cls-11{fill:#9e6ebb;}.cls-12{fill:#4d3670;}.cls-13{fill:#7d4399;}.cls-14{fill:#7bb9a7;}.cls-15{fill:#3e2261;}.cls-16{fill:#e3d8d1;}.cls-17{fill:#311355;}.cls-18{fill:#884c99;}.cls-19{fill:#07032a;}.cls-20{fill:#fbf6de;}.cls-21{fill:#75458c;}.cls-22{fill:#18013b;}.cls-23{fill:#f5b499;}.cls-24{fill:#17092e;}.cls-25{fill:#8d4e9c;}.cls-26{fill:#1b0141;}</style></defs><g id="BACKGROUND"><rect class="cls-6" x="-91.5" y="-46.5" width="2051" height="1150"/><rect class="cls-6" x="-102" y="951" width="2077" height="165"/></g><g id="Layer_1"><path class="cls-13" d="M1632.64-108V64.97c-1.75-.1-3.57-.05-5.32,0V-108h5.32Z"/><path class="cls-21" d="M331.36-108V64.97c-1.75-.07-3.57-.07-5.32,0V-108h5.32Z"/><path class="cls-14" d="M145.08,440.19c2.75,36.41,31.92,79.35,31.93,101.12,0,5.23-4.09,11.6-2.66,18.63.3,1.46,2.03,1.94,2.66,2.66,1.69,1.96,4.73,2.08,5.32,2.66.29.28-.72,3.71,1.8,5.41,14.45,7.64,56.41,19.8,66.68,29.9,3.31,3.25,10.67,20.54,11.36,25.89,2.42,18.75-1.8,41.9.03,61.2,4.84-1.01,4.95-5.23,5.39-9.22,1.81-16.18-1.51-35.42-.1-51.99,7.33,0,27.25-1.58,31.97,1.3,5.85,9.86,10.82,20.42,15.93,30.64.89,1.77,1.82,3.53,2.66,5.32,6.29,13.37,8.63,25.64,13.31,37.26-4.41,13.49-26.96,36.54-39.92,39.92-2.33.61-7.63.05-10.64,0-3.49-.06-7.04.52-10.48-.23l-.18-7.77c-12.74,11.86-29.15,7.54-45.22,8-3.54.1-7.1-.06-10.64,0s-7.1-.01-10.64,0c-49.51.17-84.39,4.23-119.75-37.26-28.3-33.21-43.54-99.89-50.2-142.73-2.36-15.18-8.21-46.71-3.02-59.51.87,5.09,5.97,4.03,7.98,5.32,4.61,2.96,7.43,6.47,13.36,9.27,36.68,17.28,79.65,29.85,117.01,46.6,1.35-7.07-1.49-4.63-5.32-6.5-24.5-11.97-51.38-21.17-76.77-31.13-.7-12.99-4.87-26.78-5.71-39.53-.43-6.51-.93-17.94,0-23.95,3.04-19.59,47.88-22.59,63.87-21.29Z"/><path class="cls-7" d="M1912.05,517.36c.19,4.42-.06,8.88,0,13.31l-2.61,1.33,2.61,1.33c-.08,3.54.15,7.11,0,10.64-3.37,3.15-5,8.9-5.32,13.31-.18,2.48-.23,5.52,0,7.98-.6,3.56-2.24,7.07-2.66,10.64-.3,2.59.14,5.36,0,7.98l-2.61,1.33,2.61,1.33c-.2,2.61.34,5.46,0,7.98-7.01,6.96-7.82,19.72-7.98,29.27-.4,1.17-1.84,2.88-2.66,5.32-3.39,10.12-6.84,22.38-10.64,31.93-4.93,12.38-12.93,29.84-21.29,39.92-18.82,22.68-50.93,37.42-79.83,39.92-3.5.3-7.12-.15-10.64,0s-7.1-.1-10.64,0c-15.85.45-32.03.21-47.9,0-.89-.01-1.77.01-2.66,0-3.55-.05-7.1.07-10.64,0-5.31-.11-10.66.22-15.97,0-3.52-.15-7.14.28-10.64,0h-2.66c-1.73-.17-3.68.28-5.32,0-5.13-3.72-7.34-4.85-8.17-11.8-2.39-20-1.95-89.81,2.84-107.95,14.12-25.67,42.13-29.63,67.23-40.68,3.99-1.76,8.71-.39,7.28-7.22.8-.27,1.86.27,2.66,0,52.58-17.58,105.15-36.88,156.96-57.25,5.97-2.35,12-5.7,17.36-9.25,2.65,1.61,1.18,7.54,1.31,10.63Z"/><path class="cls-18" d="M1845.52,796.77c21.12.5,39.31-5.67,41.99,23.22,3.02,32.64-36.95,63.24-64.47,72.72-3.5,1.2-27.89,7.85-29.41,7.85h-246.15v85.15c-1.76-.09-3.56-.03-5.32,0v-5.32c0-3.55,0-7.1,0-10.64,0-23.03,0-46.17.01-69.2-48.74-.48-97.64.69-146.37.01-14.08-.2-28.55.82-42.58,0-6.19-.36-15.83-5.13-23.95-2.66v-2.66c19.51-5.84,52.96-7.14,75-11.48,26.17-5.16,68.03-18.8,91.71-20.28,6.19-.38,10.99,2.29,16.9,2.49l2.64-1.37c-.07-2.18.29-4.46.02-6.62,19.16-5.15,41.77-21.67,61.21-21.29,13.58.27,26.04,7.3,39.37,9.86,59.24,11.36,131.04,13.89,190.13.11,51.3-11.96,22.91-28.16-8.64-39.24-.7-3.58-1.9-7.07-2.66-10.64h2.66c15.92.27,31.98-.38,47.9,0Z"/><path class="cls-18" d="M81.22,823.17c-3.72,5.44-7.48,11.9-1.33,17.15,5.3,4.53,67.94,11.34,79.86,12.24,49.96,3.78,109.8,2.12,158.91-8.01,9.11-1.88,22.72-4.54,28.68-11.58,56.43,22.14,127.77,35.82,188.38,45.87,27.55,4.57,56.26,5.9,83.05,12.97-2.55-.3-5.37.12-7.98,0-21.03-.96-48.5,2.23-71.85,2.45-36.32.35-72.78-.2-109.1,0-22.31.13-52.26-2.4-73.32-.12-3.87.42-6.84.3-9.18,3.8v77.24c12.63.24,21.94-2.8,26.61,9.81-18.53-.9-37.87,2.33-55.88-2.45,1.17-1.63-.55-4.35,4.36-6.93,5.22-2.75,13.59-2.93,19.59-2.88v-78.46h-184.95c-5.18,0-33.96-9.04-40.41-11.81-23.9-10.27-51.79-36.54-48.74-61.75,4.3-.56,9.76,2.52,13.31,2.45Z"/><path class="cls-10" d="M86.54,299.15c-18.07,3.41-72.59-23.17-76.8-39.18-1.44-5.47,2.62-11.66,2.38-17.89-.32-8.45-5.25-17.9-5.12-26.47.16-10.54,19.67-60.71,29.8-59.72,3.81.37,21.13,9.07,25.56,11.77,20.76,12.61,32.76,28.92,29.51,54.32,5.95,7.53,10.4-25.53,20.89-11.57,15.64,20.82,11.88,79-18.14,88.99l18.56,50.32,5.17-28.05,13.43-19.83,39.89-21.29c3.04,14.4,3.11,23.01.03,37.25-1.92,8.88-8.82,27.2-13.31,34.59-9.2,15.17-15.21,19.68-31.93,23.95-1.7.43-3.54,2.02-5.32,2.66-1.41-3.1-10.18-17.7-12.2-18.18-39.42,14.21-78.65-2.69-96.91-38.97,28.06-11.83,62.72-10.1,87.8,9.26,1.76-2.22-8.71-24.62-10.62-29.27,4.91-2.2,1.39-8.68.13-12.08-7.87-21.27-19.22-43.42-29.39-63.78-5.14-3.66-1.97,4.77-1.33,6.67,7.4,22.01,19.04,45.27,27.93,66.54ZM57.24,221.97c.71-4.96.02-9.22-5.27-10.64-.71,4.96-.02,9.22,5.27,10.64Z"/><path class="cls-12" d="M1603.36,168.75c3.26,20.04,21.02,13.45,35.7,18.64l14.86-18.64h71.85c19.26,22.88,37.26,46.14,55.88,69.19-14.91,6.79-29.92.13-43.91-.24-82.83-2.18-166.64-2.56-250.13.36-5.01.18-10.89,2.22-9.32-5.44,17.53-21.72,35.32-42.58,53.22-63.87h71.85Z"/><path class="cls-17" d="M469.74,264.55c-5.73,2.88-9.17,7.67-12.11,13.18-3.95,7.4-9.73,26.23-11.84,34.72-45.68.32-91.45-.39-137.16-.11-23.74.14-49.35,2.44-73.07,2.77-9.68.13-20.44-4.54-33.11-2.5-9.37,1.51-25.18,17.12-30.76,5.16,3.08-14.24,3.02-22.85-.03-37.25l-39.89,21.29c-7.63,1.17-6.25-2.87-3.91-7.89,5.8-12.42,17.67-22.4,25.19-32.02,2.76,4.45,7.21,5.01,11.92,5.38,86.29,6.87,181.89-1.85,268.95-.19,17.65.34,19.09,4.25,35.8-2.54Z"/><path class="cls-15" d="M1478.29,232.62c-1.58,7.67,4.31,5.62,9.32,5.44,83.49-2.92,167.3-2.54,250.13-.36,13.99.37,29.01,7.03,43.91.24,7.28,9.01,17.24,16.44,26.61,29.27-12.88,8.76-31.35,8.85-46.85,10.4-34.65,3.46-73.1,2.89-108.73,3.03-39.88.17-70.23-1.55-109.07-5.59-17.47-1.82-34.71,2.89-52.03,2.81-2-10.76-19.07-21.07-23.95-37.26,4.01,1.12,7.91-4.6,10.64-7.98Z"/><path class="cls-12" d="M272.82,168.75l1.33,2.61,1.33-2.61c9.73-.19,19.54.09,29.27,0,2.46,22.97,45.11,20.81,50.56,0,19.16.18,49.24-2.8,66.53,0,.29.05,4.18,2.08,5.32,2.66,7.58,3.84,27.8,30.23,34.54,38.63,4.48,5.6,10.09,13.5,13.36,19.91-25.35-10.35-41.22-5.07-65.08-5.22-66.83-.43-133.78-3.55-199.71.44-8.77.53-20.41,7.83-27.94,2.12,8.08-9.66,16.22-24.38,25.25-34.63,6.31-7.16,15.14-17.93,22.65-21.26,1.49-.66,5.03-2.62,5.32-2.66,10.8-1.49,25.67.27,37.26,0Z"/><path class="cls-3" d="M1627.31,64.97c1.75-.05,3.57-.1,5.32,0,37.06,2.06,21.27,11.37,32.26,32.94,4.76,9.34,49.7,57.56,60.88,70.84h-194.26c8.12-9.66,60.67-70.05,62.45-74.6,2.72-6.94-.18-12.98,3.89-20.06,5.92-10.28,19.65-8.86,29.46-9.13Z"/><path class="cls-3" d="M326.04,64.97c1.75-.07,3.57-.07,5.32,0,8.37.33,18.94-1.9,25.19,5.41s2.14,16.38,5.44,23.83c5.98,13.47,49.71,54.15,62.51,71.88l-2.66,2.66c-17.29-2.8-47.37.18-66.53,0-16.81-.16-33.75-.15-50.56,0-9.73.09-19.54-.19-29.27,0-.89.02-1.77-.02-2.66,0-11.59.27-26.45-1.49-37.26,0l-2.66-2.66c11.42-16.65,55.25-58.8,59.84-69.22,3.62-8.22-1.3-16.47,6.63-25.3,7.69-8.56,16.67-6.2,26.67-6.59Z"/><path class="cls-4" d="M1834.88,442.85c.9.14,3.3,2.86,5.32,2.66l13.31,2.66c4.78,9.88,9.36,9.67,10.64,23.95.05.58-5.03,6.33,0,10.64l-7.98,39.92c-31.87,11.56-63.78,27.54-95.8,37.26-1.06-15.5,1.47-32.66,0-47.9-.12-1.21-1.41-2.38-2.66-2.66,4.24-14.39,10.03-60.36,7.98-74.51,23.26-.67,46.19,4.38,69.19,7.98Z"/><path class="cls-5" d="M475.06,229.96c7.34,3,16.69,16.01,18.63,23.95-3.61,1.13-8.25,1.77-10.64,2.66-17.97-20.28-59.08-8.18-83.7-7.86-72.64.95-145.73.68-218.37-.08-4.5-.05-11.84,1.7-14.6-2.71,5.71-7.18,10.66-12.28,15.97-18.63,7.52,5.71,19.16-1.59,27.94-2.12,65.93-3.99,132.88-.87,199.71-.44,23.85.15,39.73-5.12,65.08,5.22Z"/><path class="cls-10" d="M1837.54,299.15c7.31,6.52,13.33-6.16,20.11-.28,10.56,9.16-3.3,21.22-1.46,32.2l11.93-18.6c10.15,10.79,9.56,16.6,4.02,29.25l10.61-2.64c2.41,31.9-5.7,66.75-42.56,71.84-1.4.19-4.07.27-5.32,0-10.35-2.24-31.78-16.2-35.78-26.76-2.24-5.91-8.13-42.31-.15-42.39l6.6,3.98c-5.12-6.9-9.5-14.07-5.27-22.65.68-.34,1.65-4.71,3.88-4.82l8.12,4.77c-5.73-15.17-6.56-17.68,9.28-21.23,1.89-.43,9.13.18,13.31-2.66-.26,19.59,1.22,40.5-.03,59.85-.53,8.27-1.29,27.68-7.95,29.29,7.44,4.07,9.55,5.33,8,14.65l26.53-30.63-21.21,14.66c-.45-29.34-2.3-58.44-2.69-87.82ZM1864.16,349.68h3.94s3.98-3.99,3.98-3.99l-7.92,1.38v2.61ZM1822.9,384.3v2.66c1.73-.89,1.73-1.77,0-2.66Z"/><path class="cls-15" d="M483.04,256.57c-4.04,1.51-9.15,6.3-13.31,7.98-16.7,6.78-18.15,2.87-35.8,2.54-87.06-1.66-182.66,7.06-268.95.19-4.71-.37-9.16-.93-11.92-5.38,4.6-5.88,9.29-10.92,13.31-15.97,2.76,4.41,10.1,2.66,14.6,2.71,72.65.76,145.73,1.03,218.37.08,24.62-.32,65.73-12.43,83.7,7.86Z"/><path class="cls-10" d="M121.14,413.57c6.24,3.37,12.49,14.39,21.29,7.98h2.66c-2.26,6-.47,12.47,0,18.63-15.99-1.3-60.83,1.69-63.87,21.29-28.79-6.89-50.76-34.79-61.21-61.18,34.15-6.08,70.89-3.04,101.12,13.28Z"/><path class="cls-19" d="M1845.52,796.77c-15.92-.38-31.98.27-47.9,0l-2.66-2.66c-3.83-17.71-9.59-35.44-13.31-53.22,28.91-2.49,61.01-17.23,79.83-39.92,6.29,31.93-17.3,62.87-15.97,95.8Z"/><path class="cls-20" d="M203.63,740.89c-.69,12.21-12.97,32.54-23.95,37.26-8.49,3.64-17.75,2.32-26.61,2.66l-1.33-2.61-1.33,2.61c-1.77.02-3.56.06-5.32,0-2.95-.09-10.08.06-10.64,0-3.83-.43-10.13-.93-13.31-2.66-.63-.35-1.8-3.99-3.88-5.43-2.4-1.67-6.33-2.15-6.77-2.55-15.52-14.36-26.77-45.67-26.61-66.53,35.35,41.49,70.24,37.43,119.75,37.26Z"/><path class="cls-15" d="M1864.15,482.76c14.51,2.22,34.14,3.98,46.14,13.17,2.73,2.09,1.3,4.76,1.75,5.46-16.76,11.89-37.28,14.54-55.88,21.29l7.98-39.92Z"/><path class="cls-21" d="M115.81,794.11c2.04.17,8.39,5.19,13.31,2.66-1.4,4.19-4.5,12.7-5.32,15.97-13.07.3-30.54,10.38-42.58,10.64-3.54.08-9-3.27-13.31-2.66,1.01-9.07,1.91-22.14,13.31-23.95,9.12-1.45,25.76-3.41,34.59-2.66Z"/><path class="cls-12" d="M78.56,485.42l2.65,34.58-42.56-13.29c-2.02-1.29-7.11-.23-7.98-5.32,6.84-16.89,32.04-16.01,47.9-15.97Z"/><path class="cls-17" d="M1912.05,501.39c2.94,4.56,8.09,5.85,5.31,15.98l-5.31-.02c-.13-3.08,1.34-9.01-1.31-10.63-5.35,3.56-11.38,6.91-17.36,9.25-51.81,20.38-104.38,39.68-156.96,57.25l7.98-7.98c7.63.07,10.43-3.64,15.97-5.32,32.02-9.72,63.93-25.69,95.8-37.26,18.6-6.75,39.12-9.39,55.88-21.29Z"/><path class="cls-25" d="M1853.51,448.17c24.68-1.5,48.45,6.86,71.83,13.34.67,3.62-4.76,4.04-7.32,4.58-17.32,3.67-36.34,2.78-53.87,6.03-1.29-14.28-5.87-14.07-10.64-23.95Z"/><path class="cls-15" d="M81.22,485.42c.84,12.75,5.02,26.54,5.71,39.53,25.39,9.96,52.26,19.16,76.77,31.13,3.83,1.87,6.67-.57,5.32,6.5-37.37-16.75-80.33-29.32-117.01-46.6-5.94-2.8-8.75-6.31-13.36-9.27l42.56,13.29-2.65-34.58h2.66Z"/><path class="cls-15" d="M110.49,770.16c.43.4,4.36.88,6.77,2.55,2.08,1.44,3.24,5.09,3.88,5.43l-5.32,15.97c-8.83-.75-25.47,1.21-34.59,2.66,1.6-11.91,17.48-24.61,29.27-26.61Z"/><path class="cls-16" d="M1837.54,299.15c.39,29.37,2.23,58.48,2.69,87.82l21.21-14.66-26.53,30.63c1.55-9.32-.57-10.58-8-14.65,6.66-1.61,7.42-21.02,7.95-29.29,1.24-19.34-.24-40.26.03-59.85.09-6.79-1.23-15.13,1.33-21.32,2.4,0,1.28,17.6,1.33,21.32Z"/><path class="cls-16" d="M89.2,301.81c-.39-.94-2.3-1.79-2.66-2.66-8.89-21.27-20.53-44.53-27.93-66.54-.64-1.9-3.81-10.33,1.33-6.67,10.16,20.36,21.52,42.51,29.39,63.78,1.26,3.41,4.78,9.89-.13,12.08Z"/><path class="cls-14" d="M139.76,405.59c1.27,3.49.07,11.57,2.66,15.97-8.79,6.41-15.05-4.62-21.29-7.98l13.25,4.02c-5.92-10.92-8.42-28.03-13.25-38.62,1.78-.64,3.62-2.23,5.32-2.66-.33,10.91,10.5,21.56,13.31,29.27Z"/><path class="cls-21" d="M1840.2,410.91v34.59c-2.02.2-4.42-2.52-5.32-2.66v-31.93c1.25.27,3.93.19,5.32,0Z"/><path class="cls-17" d="M1893.42,629.12c3.65,5.74-2.53,17.32-4.52,23.55-1.28,4.01,1.12,9.44-6.13,8.38,3.8-9.55,7.25-21.81,10.64-31.93Z"/><path class="cls-17" d="M1896.08,623.8c.17-9.55.98-22.31,7.98-29.27-1.78,13.28-4,17.63-7.98,29.27Z"/><path class="cls-17" d="M1912.05,543.97c-.19,4.43.2,8.9,0,13.33l-5.32-.02c.32-4.4,1.95-10.16,5.32-13.31Z"/><path class="cls-17" d="M1906.73,565.26c.13,1.42,4.87,6.23,2.65,10.63h-5.31c.42-3.56,2.06-7.07,2.66-10.63Z"/><path class="cls-10" d="M235.56,168.75c-.29.04-3.83,2-5.32,2.66-.18-2.55,1.54-3.68,2.66-5.32l2.66,2.66Z"/><path class="cls-17" d="M1904.07,586.55l-2.61-1.33,2.61-1.33c-.05.88.07,1.78,0,2.66Z"/><path class="cls-17" d="M1912.05,533.32l-2.61-1.33,2.61-1.33c.01.89.02,1.78,0,2.66Z"/><path class="cls-3" d="M1153.64,213.99c44.13,7.37,55.16,26.56,64.76,66.97,6.67,28.05,13.27,61.91,7.1,90.02,10.58,1.42,21.33,1.74,31.93,2.68,7.04.62,6.43.7,13.31,0,3.49,25.31-14.08,60.27,24.07,59.77l-.12,12.08c-5.73,1.33-13.4,6.85-13.31,13.31-48.89,3.55-45.8,64.19-71.85,95.8-2.21-6.02-5.56-6.29-10.64-7.98l-15.97-42.58h-90.48l21.31,63.88c4.42-2.16,12.6-1.47,15.95-2.68-1.72,14.36,22.18,15.72,31.93,15.97,1.56,12.82,15.17,14.5,23.95,18.63-16.8,8.5-36.61,4.33-54.66,5.21-121.24,5.94-243.32,7.16-364.43.08-31.37-1.83-63.06-6.43-94.5-7.96-1.41-10.79-2.38-17.75-2.66-29.27l21.29,2.66c2.56,5.11,17.28,19.95,22.95,20.58,18.38-7.09,51.63-5.62,68.24-12.7,3.04-1.3,1.71-5.07,1.95-5.22,3.52-2.18,20.66,3.46,25.3-2.64l25.26-55.88-80.65-2.17c-6.03,1.81-20.1,29.76-20.47,36.74-5.79,3.02-17.35,6.32-15.97-2.66-2.18-11.26-8.01-23.31-12.84-33.73-8-17.28-17.91-48.02-40.39-46.1-.91-13.66-4.64-25.5-5.32-39.92l16.91-.37,4.01-3.99.55-20.8-8.11-1.49c.78-8.63,2.38-18.01-.05-26.57l58.53-2.68c-.33-4.58-2.77-8.57-2.65-13.29l2.66-2.66c0-2.65-.09-5.33,0-7.98,6.21-5.21,7.85-7.01,15.97-7.98-10.33,10.16-12.54,17.04-10.62,31.92,4.74-.26,2.21-8.87,3.82-13.44,2.61-7.42,8.83-11.39,16.28-13.02,6.35-1.39,8.36-.82,3.83,5.18-4.24.06-12.2-1.27-14.81,2.49l-1.27,17.06c.91,3.74,17.6,5.23,22.31,7.61,3.03,1.53,3.65,4.27,4.42,4.78-5.11-.78-22.98-6.07-23.94-5.31-4.77,3.79,3.61,5.89,4.99,6.88,4.17,2.95,25.06,16.03,28.31,17.02,5.66,1.73,4.8-5.49,3.55-8.88-1.03-2.8-9.47-7.43-12.91-9.71,4.42.67,8.95-.23,13.28,2.68l2.69-26.63,11.95-61.23,19.99-2.64c-2.94-23.21-8.11-45.86-10.65-69.18,10.43.51,19.02,4.92,29.27,0,2.02,22.07-1.48,46.81-.01,69.2,19.49-.06,39.07.03,58.56-.01,10.62-.03,21.31.02,31.93,0h2.66l-8,69.2h90.49c1.64,6.55,11.71,41.1,15,42.2,39.06-2.96,87.04,5.18,124.98.52,4.11-.51,4.97-2.35,6.38-2.81,9.67-3.21,29.33-16.39,34.62-25.25-10.61-2.8-26,5.57-34.62,11.95-.48-2.28-3.28-6.03-4.12-10.43-4.23-22.14-7.18-44.6-11.98-66.62-3.46-.62-7.02.1-10.51-.12-.88-7.75,2.35-14.91,2.77-22.52.6-10.82-2.42-48.95,1.24-54.63,1.57-2.43,5.35-4.63,9.3-10.67,2.36-3.62,5.2-7.31,7.98-10.64ZM1182.91,337.73c-2.77-8.65,0-58.06,0-71.85,0-2.33,7.69-7.9-2.65-6.66-3.32,25.81-4.4,52.13-.27,78.05l-13.07,8.45,26.64,1.3c-.5-4.51-9.74-6.48-10.64-9.29ZM988.65,488.08c11.45-8.8,34.33-19.71,21.27-35.84,9.43-2.78,15.8-19.99,2.49-16.29-7.99,2.22-12.09,14.57-21.09,14.86-1.76-1.86,18.71-30.23,12.88-48.81-4.49-14.31-18.59,9.96-23.51,11.57l-9.36-26.66-8.02,2.65-1.3,16.02-7.94-2.65,2.62,29.25c-4.58-2.03-4.31-6.88-10.73-9.09-3.56-1.22-6.71-2.22-10.52-1.52-2.77,11.5,5.37,16.98,7.96,26.58l-10.65.02c-1.15,22.35,17.2,28.65,31.95,39.91-8.28.18-16.63-.61-24.91.37-5.29,1.72-3.92,6.18-4.36,10.27-2.42,22.72,7.37,49.56,19.17,68.63l44.28.13c14.12-23.89,15.59-41.89,16.39-68.75.03-.87,7.07-7.35-1.75-10.22-5.66-1.85-17.86-.26-24.86-.42Z"/><path class="cls-14" d="M517.64,248.59c.57,10.71,2.56,17.46,14.54,18.8,16.45,1.84,18.73-1.92,20.06-16.14,53.83,4.71,51.26,61.29,63.87,101.12-5.79,2.09-19.51,27.79-21.29,34.59-1.53-.48-4.27-2.77-5.32-2.66,1.37-6.71-3.75-11.43-5.32-15.97-6.2-17.85-4.96-34.65-6.65-53.25-.6,17.65-3.41,35.66-3.99,53.25-.2,6.19.14,12.43,0,18.63-.7.18-5.2,4.2-9.05,5.51-17.88,6.06-13.89-2.89-22.89,15.78-2.52,5.23-6.14,9.08-5.32,15.97-17.64-2.31-41.67-6.72-58.54-5.32-37.59-10.08-48.78-10.56-42.72-54.69,1.7-12.4,7.56-38.81,10.78-51.75,2.12-8.49,7.89-27.32,11.84-34.72,2.94-5.51,6.37-10.3,12.11-13.18,4.15-1.69,9.26-6.47,13.31-7.98,2.4-.9,7.04-1.53,10.64-2.66,7.72-2.42,15.62-5.54,23.95-5.32Z"/><path class="cls-19" d="M664,365.67c-4.47,19.44-6.27,41.3-5.32,61.21.68,14.42,4.41,26.25,5.32,39.92,1.47,22.14,1.5,41.24-19.29,53.89-16.59,10.09-41,8.62-57.88-.67-6.19-3.4-18.87-17.55-22.45-24.12-19.74-36.31,11.08-38.36,22.45-66.35,6.08-14.97,4.31-28.52,7.98-42.58,1.78-6.8,15.5-32.51,21.29-34.59,8.22-2.96,37.37,1.43,45.21,6.79,2.88,1.97,2.23,6.09,2.69,6.52Z"/><path class="cls-13" d="M1071.15,312.45c.89,0,1.77,0,2.66,0,15.04.13,30.2-.25,45.24,0,4.41.07,8.92-.28,13.31,0,3.49.23,7.05-.5,10.51.12,4.8,22.02,7.75,44.48,11.98,66.62.84,4.4,3.64,8.15,4.12,10.43.79,3.78-.55,9.18,0,13.31-1.4.47-2.27,2.31-6.38,2.81-37.94,4.67-85.92-3.47-124.98-.52-3.3-1.11-13.36-35.66-15-42.21-4.01-16.01-3.75-34.87-10.64-50.53,9.25,2.76,22.35-2.64,29.27-2.69,10.31-.07,26.73,2.65,39.92,2.66ZM1078.32,352.66c-11.07,2.77-10.33,23.82,7.09,18,9.41-3.14,3.12-20.56-7.09-18Z"/><path class="cls-14" d="M1403.78,269.88c.62,4.42,1.89,8.83,5.28,12,10.53,4.37,25.36.87,26.65-12,31.3.47,36.25,11.01,45.24,37.26,2.13,6.22,3.38,12.45,5.32,18.63l-26.25,8.43c-1.68,2.38.4,7.84-.36,10.2-4.41,13.56-8.9,27.53-7.98,42.58-23.59,3.4-36.02,7.77-61.21,2.66-2.85-6.23-3.66-13.07-5.89-19.54-1.13-3.28-4.66-4.1-4.76-4.41-3.38-11.32,1.01-41.05-18.63-37.26,6.39-29.23,3.53-59.1,42.58-58.54Z"/><path class="cls-13" d="M805.04,211.33c.06,6.23,2.25,9.51,2.66,13.31,2.53,23.32,7.71,45.96,10.65,69.18l-19.99,2.64-11.95,61.23c-4.5-1.09-12.67-7.28-15.97-7.98v-2.66c2.57-10.98,4.79-27.44,5.29-38.61.75-16.34-.47-32.86.01-49.19-3.28-4.32-4.82.05-5.31,3.93-2.01,15.71.51,36.75.11,53.37-.18,7.59-2.94,14.11-2.77,22.52-6.87.56-14.61-.8-21.29,0-8.11.97-9.75,2.77-15.97,7.98,1.4-42.24,7.22-81.02,21.29-122.41,16.86-8.24,34.21-12.91,53.22-13.31Z"/><path class="cls-23" d="M1486.28,325.76c.25.81-.25,1.85,0,2.66,6.44,21.26,27.15,63.22,3.65,79.49-7.52,5.21-17.78,3.49-24.94,8.33-31.61-5.51-56.79-4.1-87.82,0-15.58-6.72-5.19-14.58-23.95-15.97,3.85-16.26-14.97-1.68-18.62-5.32v-21.28c5.86,1.36,8.72-.94,13.29-2.68,1.63-.62,3.53,1.47,5.35-1.84,4.43-8.08,5.75-30.6,7.96-40.74,19.64-3.79,15.25,25.93,18.63,37.26l-7.99,18.58c6.44,2.33,11.84,3.99,18.63,5.37,25.18,5.1,37.61.74,61.21-2.66,7.48-1.08,16.04,1.04,23.94-2.69l-15.96-39.88c.77-2.36-1.31-7.82.36-10.2l26.25-8.43Z"/><path class="cls-20" d="M1116.38,213.99c.24,2.59-.37,5.48,0,7.98,1.49,10.15,6.65,11.41,7.37,14.94,1.07,5.24-4.11,26.74-4.69,34.31-.95,12.39-2.41,29.21-.02,41.23-15.04-.25-30.19.13-45.24,0-1.96-13.12,1.16-35.71-7.96-45.24l5.3,45.24c-13.19-.01-29.6-2.73-39.92-2.66,12.72-28.71,22.83-75.52,54.01-88.35,9.26-3.81,21.23-5.54,31.14-7.45Z"/><path class="cls-7" d="M1467.65,240.6c4.88,16.19,21.95,26.49,23.95,37.26,1.26,6.79-3.31,25.85-10.64,29.27-8.99-26.25-13.94-36.79-45.24-37.26.79-7.89-3.43-27.2-6.53-34.72-6-14.56-24.39-45.96-41.37-47.77,14.53-26.94,56.12-23.8,69.32,3.86,6.86,14.37,5.96,34.23,10.52,49.36Z"/><path class="cls-7" d="M834.31,208.67c-.36-.9-8.35-6.52-7.98-10.62,29.77,3.26,24.99-25.77,28.7-46.32l-19.01-14.73-17.71,26.43-9.66-5.02c-13.65,3.28-1.63,14.29-.73,22.24,1.03,9.06-2.97,20.07-2.87,30.67-19.01.4-36.37,5.06-53.22,13.31,6.28-18.47,12.83-30.53,19.91-47.95,12.31-30.27,13.15-70.38,60.66-60.55,40.99,8.48,36.88,78.98,1.92,92.53Z"/><path class="cls-19" d="M1257.42,373.66c13.87-2.34,7.46-17.37,13.35-22.58,8.19-7.24,31.98-12.21,42.44-7.93,1.15.47,19.37,13.23,20.3,14.33,5.63,6.64.77,11.04,14.38,13.51-4.57,1.74-7.43,4.04-13.3,2.68v21.28c3.65,3.64,22.48-10.94,18.62,5.32-7.01-.52-14.27.36-21.3-.02-.18,4.41.25,8.9.01,13.32-14.45,4.63-37.39,6.12-43.74-10.75-1.64-4.37-.8-11.04-1.9-12.78-2.11-3.33-15.1.84-10.26-16.4-1.74.09-3.57-.17-5.31.01-6.87.7-6.27.62-13.31,0Z"/><path class="cls-13" d="M895.51,293.82c-19.49.05-39.07-.04-58.56.01-1.46-22.39,2.03-47.13.01-69.2-.1-1.13-2.1-8.69-2.66-10.64,52.91.68,49.03,41.38,61.21,79.83Z"/><path class="cls-23" d="M576.18,179.4c1.05,19.45,5.13,39.63-5.4,57.12-6.19,3.42-12.02,5.06-18.53,1.43-.34,4.38.38,8.94-.02,13.3-1.32,14.22-3.61,17.98-20.06,16.14-11.98-1.34-13.97-8.09-14.54-18.8-.65-12.11,2.27-16.11,5.32-26.61,1.55-5.32,3.22-18.94,5.14-20.14,3.6-2.25,10.83-.21,16.11-2.52,7.44-3.26,17.45-22.78,31.97-19.92Z"/><path class="cls-23" d="M1153.64,174.08c-1.98,2.26-4.91,6.15-5.05,9.13l5.05,30.79c-2.78,3.33-5.62,7.03-7.98,10.64-11.72,7.78-19.53,7.23-29.27-2.66-.37-2.51.24-5.39,0-7.98-1.29-13.79-3.49-4.69-10.81-11.77-9.67-9.36-12.43-44.44-7.81-57.42,5.99,5.23,18.86,7.49,24.95,10.98,11.2,6.41,7.64,16.59,23.94,7.76l7,10.53Z"/><path class="cls-23" d="M1435.71,269.88c-1.29,12.87-16.12,16.37-26.65,12-3.39-3.17-4.67-7.58-5.28-12-.78-5.58,1.79-13.65-1.27-18.7-2.12-3.49-8.71-3.4-11.34-5.95-8.34-8.06-10.29-37.3-8.55-48.48.94-6.05,3.55-6.3,5.2-9.37,16.99,1.81,35.37,33.21,41.37,47.77,3.1,7.52,7.32,26.83,6.53,34.72Z"/><path class="cls-23" d="M805.04,211.33c-.09-10.6,3.9-21.62,2.87-30.67-.9-7.96-12.92-18.97.73-22.24l9.66,5.02,17.71-26.43,19.01,14.73c-3.71,20.54,1.07,49.58-28.7,46.32-.37,4.09,7.63,9.72,7.98,10.62.5,1.26-.44,3.8,0,5.32.56,1.95,2.56,9.51,2.66,10.64-10.26,4.92-18.85.51-29.27,0-.41-3.8-2.61-7.07-2.66-13.31Z"/><path class="cls-9" d="M1097.76,144.8c-3.7-3.23-11-13.73-7.77-18.42,35.12-15.62,83.33-17.99,73.66,35.11-2.17,11.93-8.42,10.78-10.01,12.59l-7-10.53c-16.29,8.83-12.74-1.35-23.94-7.76-6.09-3.48-18.95-5.75-24.95-10.98Z"/><path class="cls-19" d="M522.96,221.98c-25.69-17.5-21.14-59.92,11.9-63.92,14.09-1.71,27.44,2.95,41.33,2.7.24,6.17-.35,12.47-.01,18.64-14.52-2.86-24.53,16.66-31.97,19.92-5.27,2.31-12.51.27-16.11,2.52-1.92,1.2-3.59,14.82-5.14,20.14Z"/><path class="cls-23" d="M664,365.67c1.56,1.44,5.28-1.54,7.98,7.98,2.43,8.56.83,17.94.05,26.57l8.11,1.49-.55,20.8-4.01,3.99-16.91.37c-.94-19.91.86-41.77,5.32-61.21Z"/><path class="cls-10" d="M427.16,171.41c-1.14-.58-5.03-2.61-5.32-2.66l2.66-2.66c1.22,1.7,2.82,2.86,2.66,5.32Z"/><polygon class="cls-13" points="930.11 293.82 927.45 293.82 928.76 291.21 930.11 293.82"/><path class="cls-13" d="M727.86,357.69c.06-2.43,2.66-2.47,2.66-2.66l-2.66,2.66Z"/><path class="cls-26" d="M1425.07,1033.61c-.5-5.42,1.52-11.09,7.19-12.78,6-1.8,60.44-1.49,62.29,1.04l2.38,11.74c-23.91.11-47.94-.15-71.85,0Z"/><path class="cls-26" d="M1339.92,1033.61c-22.14.03-44.39-.02-66.53,0,3.56-26.73,33.68-6.26,46.77-5.32,8.92.64,19.49-14.06,19.76,5.32Z"/><path class="cls-26" d="M1398.46,1033.61c-1.63-6.93,6.14-7.41,11.94-8.02l1.37,8.02c-4.43.02-8.87-.01-13.31,0Z"/><path class="cls-22" d="M525.62,597.19c-6.65,9.37,6.88,17.85,15.97,15.97.12,1.76-.13,3.56,0,5.32-4.8,4.88-16.84,11.13-19.43,16.72-2.07,4.48.53,8.73-.38,12.75-1.17,5.17-6.11,4.64-6.73,7-2.37,8.99.66,14.9,10.59,12.96,6.41-8.15,9.31-23.52,21.28-25.49,3.27,29.55-5.02,50.46,18.63,74.51,1.42,1.45,5.26,2.42,5.33,4.28l-34.59,150.05,10.07-4.54,36.49-147.13h51.89c-.33,11.48.46,23.13,0,34.59-27.67,5.83-34.77,36.52-2.66,37.26-1.27,25.02-5.62,54.64-5.52,78.46.04,11.04,4.07,22.79,10.83,8.01.68-27.9,1.38-55.97,2.68-83.81,5.18-.42,10.91.61,15.97,0,8.15,7.62,26.37-3.59,31.93,7.98-2.34,1.45-11.95,14.36-12.75,17.87-3.75,16.38,7.74,35.35,23.38,40.66-9.13-15.54-.28-25.67.01-37.24,10.36,6.91,10.27,58.35,13.32,61.22l7.95-.03c-1.37-28.38-9.95-55.95-13.35-83.95-.8-6.61,2.83-12.92,2.72-14.49,3.59-3.93,12.44-8.26,15.22-11.45,1.3-1.49.4-4.09.74-4.51,6.96-8.57,12.42-16.31,18.68-25.36,2.29-3.31,2.02-7.89,7.93-6.57,4.05,22.8,15.75,49.93,20.62,73.84,2.09,10.26,1.57,33.54,4.7,40.54.96,2.15,16.8,17.43,19.13,18.12,7.82,2.32,19.02-.44,27.4.52-11.74-12.78-20.08-5.4-23.23-25.97-8.67-56.67,1.58-140.5-16.68-192.21h13.31c.3.77-.29,1.88,0,2.66.92,2.48,2.21,4.14,2.66,5.32,2.88,7.57,21.41,66.58,35.94,42.6,3.47-5.72-2.38-43.73-4.01-53.24,9.67,3.61,7.02,11.46,8.74,19.23.54,2.44,3.76,4.67,4.07,6.59.53,3.21-13.54,20.6,5.87,28.67,4.09,1.7,40.07,3.37,47.09,3.24,4.53-.08,7.63-2.59,11.4-4.51.06,2.66-.11,5.34-.02,7.99,14.95-1.31,32.25,1.73,46.84.13,3.69-.41,6.05-2.77,6.4-2.8,31.65-2.17,64.1-3.15,95.8-5.32.88-.06,1.78.04,2.66,0-1.06,10.97-3.39,13.41,0,23.95.26.79-.19,1.82,0,2.66l-2.62,1.32c.47,1.57,1.47,1.15,2.62,1.34,7.53,1.23,15.73-1.44,24.1,1.19,9.13,2.87,10.47,15.01,21.15,9.45-1.38-3.96-1.45-9.82-2.67-13.29-5.14-14.62-13.03-11.13-23.75-17.5-6.53-3.89.24-7.75-16.17-9.11-1.48-8.04,4.05-5.14,9.18-5.33,6.6-.24,13.28.62,19.81-.29,6.39-21.56-1.23-46.27,9.33-66.5l41.51-2.39c-2.99,8.71-1.4,18.56-2.66,26.61-13.94,3.03-4.01-9.96-11.71-16.22-10.47-8.52-28.2,5.59-28.2,14.89v49.23c14.16-2.09,21.23-2.82,34.59,2.66l-5.44,120.64c.8,3.31,10.28,4.53,13.42,4.43-.04,7.86-3.28,15.16-7.98,21.29-3.65-.01-37.02,9.13-40.73,11.16-3.44,1.88-7.96,5.26-1.85,7.47,1.57,3.63,5.86,2.64,9.09,2.81,16.17.88,40.46,1.32,56.34,0,4.3-.36,5.56.75,9.08-2.82,4.6-4.66,2.39-9.96,2.66-15.97.22-4.92.49-11.21,0-15.97-.46-4.48-2.56-5.04-2.66-5.32-.45-1.3.3-3.68,0-5.32,4.42-.24,8.91.2,13.32.01,3.08-3.01-1.99-76.16,7.97-85.17,7.48,37.41,34.15,76.36,42.58,114.43-.23.71-2.15,1.6-2.66,2.66-2.64,5.47.62,10.11,2.66,15.97-1.77,8.95-5.69,13.75,7.97,13.29.52-6.05-.67-12.66.01-18.61h34.6c2.18-4.45-2.51-9.12-2.67-10.64-.63-6.29.91-12.77-.62-19.34-4.15-17.79-16.03-39.39-20.67-57.83,2.16-20.29-1.33-43.33,5.32-63.87h50.56l10.66,165h7.96s-7.96-165.02-7.96-165.02l10.25.39,4.4,12.95c7.4-.09,6.59-8.49,6.74-13.22l34.23.15,34.8,149.64,8.02,1.77-34.6-151.63c10.77-.09,9.54-4.99,13.33-10.68.99-1.49,3.88-1.91,5.54-6.33,8.59-22.93,5.28-49.85,10.43-73.51,0,.35,2.87,2.7,2.8,6.43-.15,8.42-7.64,40.52-.31,45.63,24.16,7.42,46.25-9.33,69.36-4.16,1.73,13.59,3.6,27.57,5.34,41.23,5.96,46.88,12.88,93.74,18.52,140.67l8.07,7.05c-5.91-.19-10.71-2.87-16.9-2.49-23.68,1.47-65.54,15.12-91.71,20.28-22.04,4.35-55.5,5.64-75,11.48-1.21.36-1.94,2.26-2.66,2.66-1.77.98-3.51,3.95-5.32,5.32-.63-.47-5.88.12-7.98,0-35.36-2.06-71.27,2.24-106.44,2.66-1.77.02-3.55.02-5.32,0-45.6-.41-91.22-3.8-137.15-2.74-5.05.12-10.35-1.25-14.53,2.74-7.07-.22-14.22.21-21.29,0-45.52-1.32-93.03-3.82-139.81-2.74-5.05.12-10.36-1.26-14.53,2.74-2.66-.04-5.32.04-7.98,0-77.6-1.15-155.38.71-233.02.18-9.48.39-5.64-7.04-14.46-8.16-26.79-7.67-55.5-9.12-83.05-14.08-60.62-10.91-131.95-25.76-188.38-49.79-.38-.16-1.71-3.39-4.55-4.66-9.61-4.32-19.44-9.74-30.05-11.3l-21.29-77.17c12.95-3.38,35.51-26.43,39.92-39.92,6.06,15.05,11.4,17.58,18.63,26.61,2.54,3.16,16.39,51.03,15.97,55.88-.57,6.58-8.9,14.47-5.31,23.96h7.96c1.29-1.17-3.05-9.86,3.95-7.96,13.34,3.63,39.72,34.39,54.58,12-4.21-5.08-6.76-7.97-13.28-9.38.29-1.66-.44-3.98,0-5.32.14-.43,3.44-.52,2.66-2.63-1.62-.42-4.36.48-5.33-.03-1.59-.84-1.81-1.12-2.66-2.66-4.81-8.74-3.2-3.13-5.32-5.32-20.33-20.95-16.8-38.63-26.61-61.21l.03-5.32c5.83,3.01,5.14,3.99,10.62,2.66,1.32-.32,3.39.76,4.94-.4,1.17-1.17.11-3.57.39-4.92,2.61-13.05.86-4.2,7.74-9.55,2.31-1.8,2.58-6.24,4.65-6.61,3.49-.63,13.28,3.88,20.93,3.06,6.67-.71,10.47-6.11,17.24-5.53-.06.88.06,1.78,0,2.66l-5.36,158.1,7.96,1.56c5.17-40.32,11.19-80.71,16.01-121.09,2.78-23.34,5.35-46.99,8-70.5,1.64-14.53,1.11-31.16,2.66-45.24.68-6.19,1.7-14.74,2.66-21.29.8-5.45,4.63-11.71,2.66-18.64,1.04-1.08,23.26,2.48,27.1,3.51,5.7,1.52,17.01,8.83,20.79,9.81Z"/><path class="cls-7" d="M408.53,674.36c-6.25,2.16-36.22,23.36-37.06,28.32l15.77,19.58c-5.48,1.33-4.79.35-10.62-2.66l-.03,5.32c-1.63-3.75-8.1-8.34-9.3-13.29l-17.31,15.95c-7.23-9.03-12.57-11.56-18.63-26.61-4.67-11.61-7.02-23.89-13.31-37.26,1.67.28,3.93-.41,5.32,0,1.78,3.2,1.58,8.08,6.68,10.59.94-3.63-3.47-9.64-6.68-10.59-1.79-3.22-1.56-8.11-6.67-10.63l-1.32,5.31c-5.12-10.22-10.08-20.78-15.93-30.64-4.71-2.88-24.64-1.29-31.97-1.3-.89,0-1.77,0-2.66,0-.06-2.66.09-5.33,0-7.98,17.48-2.32,30.05-13.93,42.6-25.28-17.16-1.48-26.23,18.13-42.6,19.96-6.38-18.98-48.41-33.03-64.91-40.34-3.98-1.76-8.26-1.49-6.94-7.56,19.13.02,41.09-10.18,61.21-13.31,24.82-3.86,76.17-8.98,99.14-2.01,14.32,4.35,17.47,15.79,22.59,27.97,12.55,29.87,21.45,65.61,32.62,96.45ZM294.08,623.79v-3.94s-3.99-3.98-3.99-3.98l1.38,7.92h2.61ZM336.66,677.03l-5.27,3.93,15.92,17.33c-.61-7.97-12.28-12.79-10.65-21.26ZM352.64,700.99h-5.29s.01,3.94.01,3.94l3.98,4.02,1.3-7.96Z"/><path class="cls-19" d="M235.56,315.11c9.32,6.71,2.29,15.29,2.66,18.63-11.28.15-25.95,20.27-31.99,22.72-4.69,1.9-16.27-5.29-18.57,2.61-2.01,6.93,9.09,11.79,9.9,18.88,1.14,10.06-5.77,27.18-4.58,38.28-5.74-.35-18.89,4.27-18.21,11.48,13.73,20.7,19.04,49.27,31.45,69.74,6.97,11.5,8.06,6.17,13.37,9.26,2.59,1.5,5.6,22.24,13.31,23.95-2.32,3.83-2.55,10.76-6.77,15.86-7.45,8.99-23.31,10.66-33.92,7.54-8.05-2.37-6.88-13.28-15.19-12.75-.02-21.78-29.18-64.71-31.93-101.12-.47-6.15-2.26-12.63,0-18.63,2.3-6.11,5.2-9.56,7.98-18.63,5.02-16.38,13.18-33.1,5.32-50.56,4.48-7.39,11.38-25.71,13.31-34.59,5.58,11.96,21.39-3.65,30.76-5.16,12.67-2.04,23.43,2.63,33.11,2.5Z"/><path class="cls-22" d="M224.92,740.89c16.06-.46,32.48,3.86,45.22-8l.18,7.77c3.44.75,7,.17,10.48.23,5.29,22.95,9.49,46.55,15.97,69.19l-45.07-17.46-26.78-3.83c.24-15.93-.17-31.97,0-47.9Z"/><path class="cls-9" d="M254.19,525.34v26.61c-20.11,3.13-42.08,13.32-61.21,13.31-3.55,0-7.1,0-10.64,0-.59-.58-3.63-.71-5.32-2.66l-2.66-2.66c-1.43-7.02,2.67-13.39,2.66-18.63,8.31-.53,7.14,10.38,15.19,12.75,10.61,3.12,26.47,1.46,33.92-7.54,4.22-5.1,4.46-12.03,6.77-15.86,5.84-9.65,13.05-12.4,21.29-18.63v13.31Z"/><path class="cls-2" d="M214.27,740.89v50.56c-8.69,1.53-24.61-2.17-31.93,0l-2.66-13.31c10.98-4.71,23.26-25.05,23.95-37.26,3.55-.01,7.1.06,10.64,0Z"/><path class="cls-16" d="M291.44,740.89l21.29,77.17v13.32s-10.34-.33-10.34-.33c-.43-7.43-3.66-14.11-5.62-20.98-6.48-22.64-10.67-46.23-15.97-69.19,3.02.05,8.31.61,10.64,0Z"/><path class="cls-16" d="M224.92,740.89c-.17,15.93.24,31.97,0,47.9-.27,17.92.36,35.47-2.67,53.24h-7.96c-.02-16.83-.01-33.76-.01-50.58v-50.56c3.55-.06,7.1.1,10.64,0Z"/><path class="cls-10" d="M267.5,626.46c-1.42,16.57,1.91,35.81.1,51.99-.45,3.98-.55,8.21-5.39,9.22-1.83-19.31,2.39-42.45-.03-61.2h2.66c.89,0,1.77,0,2.66,0Z"/><path class="cls-16" d="M192.98,565.26c-1.32,6.07,2.96,5.8,6.94,7.56,16.49,7.31,58.53,21.36,64.91,40.34.38,1.14-.06,3.65,0,5.32.09,2.66-.06,5.33,0,7.98h-2.66c-.69-5.35-8.05-22.64-11.36-25.89-10.27-10.1-52.23-22.26-66.68-29.9-2.52-1.7-1.51-5.13-1.8-5.41,3.55,0,7.1,0,10.64,0Z"/><path class="cls-8" d="M323.38,663.72c3.21.95,7.61,6.96,6.68,10.59-5.1-2.51-4.9-7.39-6.68-10.59Z"/><path class="cls-8" d="M323.38,663.72c-1.4-.41-3.65.28-5.32,0-.84-1.79-1.77-3.55-2.66-5.32l1.32-5.31c5.1,2.52,4.87,7.41,6.67,10.63Z"/><path class="cls-15" d="M177.02,562.6c-.63-.73-2.36-1.2-2.66-2.66l2.66,2.66Z"/><path class="cls-19" d="M1632.64,549.29c10.57-.22,36.14,1.56,47.9,2.66,19.4,1.82,45.49,13.14,63.87,13.31l-7.98,7.98c-.8.27-1.86-.27-2.66,0-24.67,8.21-65.38,18.46-74.51,45.24h-5.32c-1.77,0-3.55,0-5.32,0-.29-1.28-1.41-2.48-2.66-2.66-6.26-.92-19.17,1.83-23.39-.59-1.28-.73-15.35-21.13-17.07-24.15-4.96-8.68-4.85-24.3-15.42-25.83,4.27-4.13,10.03-10.4,15.84-12.11,4.21-1.24,22.13-3.76,26.74-3.86Z"/><path class="cls-26" d="M1760.37,740.89c-.3,18.51,11.87,32.79,10.64,50.56-19.35-1.15-39.16.84-58.54,0-.11-13.57-5.39-32.54-2.66-47.9l2.66-2.66c15.87.21,32.04.45,47.9,0Z"/><path class="cls-22" d="M1664.57,740.89c1.65.28,3.59-.17,5.32,0,.88.09,1.78-.07,2.66,0,3.5.28,7.12-.15,10.64,0,2.86,7.2-4.34,7.54-5.14,9.98-2.12,6.48-.99,12.91-4.98,21.14-5.34,11.02-17.07,16.97-21.81,27.42-8.6,2.62-16.09,6.51-23.95,10.64,5.47-19.97,6.72-46.03,13.31-66.53,1.01-.56,1.95-2.44,2.66-2.66,1.14-.36,3.59.74,4.83-.52,1.33-1.35.12-3.79.49-4.81,6.34-.8,10.18,4.35,15.97,5.32Z"/><path class="cls-2" d="M1699.16,740.89c.08,16.82-.11,33.74,0,50.56-15.2,0-33.31,3.53-47.9,7.98,4.75-10.44,16.47-16.4,21.81-27.42,3.99-8.23,2.85-14.66,4.98-21.14.8-2.44,8-2.79,5.14-9.98,5.3.22,10.66-.11,15.97,0Z"/><path class="cls-16" d="M1709.81,740.89v2.66c-2.72,15.36,2.55,34.33,2.66,47.9.14,16.84-2.7,32.32-2.62,49.02l-6.7,1.58c-6.04-1.91-3.94-42.52-3.99-50.6-.11-16.82.08-33.74,0-50.56,3.55.07,7.1-.05,10.64,0Z"/><path class="cls-16" d="M1781.66,740.89c3.72,17.78,9.47,35.51,13.31,53.22.18.85-.18,1.81,0,2.66.76,3.57,1.96,7.06,2.66,10.64,1.53,7.84,8.73,26.47-1.3,26.6-4.71-1.08-13.08-33.54-14.67-39.91-4.18-16.72-5.29-36.38-10.64-53.22,3.52-.15,7.15.3,10.64,0Z"/><path class="cls-5" d="M1659.25,618.48c-.26.76.23,1.8,0,2.66-4.79,18.14-5.23,87.95-2.84,107.95.83,6.95,3.03,8.08,8.17,11.8-5.79-.97-9.63-6.13-15.97-5.32,10.76-29.39-4.41-84.62,5.32-117.09h5.32Z"/><path class="cls-24" d="M1771.01,740.89c5.36,16.84,6.46,36.51,10.64,53.22-3.28-2.26-6.82-2.43-10.64-2.66,1.23-17.77-10.95-32.05-10.64-50.56,3.54-.1,7.11.15,10.64,0Z"/><path class="cls-23" d="M1733.76,573.24c1.43,6.83-3.29,5.46-7.28,7.22-25.1,11.05-53.11,15.01-67.23,40.68.23-.86-.26-1.9,0-2.66,9.13-26.78,49.84-37.02,74.51-45.24Z"/><path class="cls-5" d="M1709.81,743.55v-2.66c.89.01,1.77-.01,2.66,0l-2.66,2.66Z"/><path class="cls-5" d="M1672.55,740.89c-.88-.07-1.78.09-2.66,0h2.66Z"/><path class="cls-22" d="M1558.12,682.34c-4.9,24.85-6.87,49.01-5.32,74.51-5.29,9.43-10.48,15.42-18.61,22.67l4.39,6.3c19.71,3.3,45.97-18.2,50.01-36.64,2.75-12.54,3.19-27.49,6.79-42.88,10.59,11.87,19.59,24.94,34.59,31.93-4.65,26.7-12.49,52.9-15.97,79.83-10.65-.14-20.61,6.87-29.94,11.44-3.8,1.86-8.81.18-7.32,7.19-19.43-.38-42.04,16.14-61.21,21.29-6.94-55.39-9.76-118.78-13.31-175.63h55.88ZM1589.75,788.51c1.88-2.18.8-13.4-3.68-15.64-5.73,6.48-23.37,18.13-6.02,17.89,1.29-.02,9.38-1.87,9.7-2.25Z"/><path class="cls-5" d="M1699.16,791.45c.05,8.09-2.05,48.69,3.99,50.6l6.7-1.58c-.09-16.7,2.76-32.18,2.62-49.02,19.39.84,39.2-1.15,58.54,0,3.82.23,7.37.4,10.64,2.66,1.59,6.37,9.95,38.83,14.67,39.91,10.03-.13,2.83-18.76,1.3-26.6,31.55,11.08,59.93,27.28,8.64,39.24-59.09,13.78-130.9,11.25-190.13-.11-13.33-2.56-25.79-9.59-39.37-9.86-1.5-7.01,3.51-5.32,7.32-7.19,9.33-4.57,19.29-11.58,29.94-11.44-.55,4.24-6.35,8.39,1.33,13.25,2.78-.2,10.89-17.28,11.97-21.24,7.86-4.14,15.35-8.02,23.95-10.64,14.59-4.45,32.7-7.99,47.9-7.98Z"/><path class="cls-13" d="M1502.24,658.39c.43,7.92-.49,16.04,0,23.95,3.55,56.85,6.37,120.24,13.31,175.63.27,2.15-.09,4.44-.02,6.62l-2.64,1.37-8.07-7.05c-5.65-46.92-12.56-93.79-18.52-140.67-1.74-13.66-3.61-27.64-5.34-41.23-.64-5.05.63-10.91,0-15.97l21.29-2.66Z"/><path class="cls-26" d="M1395.8,900.55c9.18,28.29-6.63,29.25-30.76,26.76-20.51-2.11-13.15-10.94-11.82-26.76,14.02.82,28.5-.2,42.58,0Z"/><path class="cls-2" d="M1542.16,980.39v5.32c-7.99.12-13.5.22-21.29,2.66-.28-2.64-.35-4.47,2.66-5.32,4.56-1.29,13.2.5,18.63-2.66Z"/><path class="cls-2" d="M1329.27,897.89h-2.66c.72-.4,1.46-2.3,2.66-2.66v2.66Z"/><path class="cls-6" d="M1797.62,796.77h-2.66c-.18-.85.18-1.81,0-2.66l2.66,2.66Z"/><path class="cls-6" d="M618.76,897.89c8.82,1.12,4.98,8.56,14.46,8.16,77.65.53,155.42-1.33,233.02-.18,1.48,8.05-4.07,5.13-9.19,5.32-2.53.09-31.9-1.69-22.73,5.31,8.57,1.18,29.05-3.76,33.28,5.31,2.48,5.31.2,11.69,1.94,16.69.65,1.87,8.02,17.19,8.67,17.94,3.79,4.42,14.14,1.06,16.78,9.82,1.4,4.64,1.36,18.22-.01,22.9-3.51,11.96-31.89,6.02-43.15,7.4-24.16,2.98-26.94,7.7-55.99,7.65-58.56-.1-117.91-1.95-175.76-.06-16.12.53-30.61,11.95-46.7,6.96-3.97-1.23-6.66-5.72-11.93-6.68-6.55-1.2-14.23,1.28-20.67-.62-8.84-2.61-5.82-14.17-9.66-16.96-5.63-4.08-20.99,2.8-27.04-4.89-7.37-9.36,2.46-53.85-4.9-58.97-8.84-2.75-18.1.25-27.04-2.29-6.38-1.82-5.01-8.39-11.64-9.57-8.98-1.59-33.21,5.54-30.69-10.59,36.32-.22,72.79.37,109.1,0-.4,6.9-7.23,23.29,1.71,26.24,16.47,3.03,34.37-1.73,49.9-2.02,6.3-.12,30.91,8.59,30.91-4.11,0-10.18-11.8-13.4-10.66-22.76,2.61.13,5.44-.32,7.98,0ZM812.38,941.12c-4.72-4.73-25.93-4.76-30.67-.02-4.7,4.7-4.74,25.93,0,30.67,5.24,5.24,60.33,9.74,48.71-12.73-12.3-3.6-13.46-13.33-18.04-17.92Z"/><path class="cls-5" d="M145.08,783.47l12.39,15.68c6.67-1.24,13.73-1.62,20.36-3,3.24-.67,4.2-4.6,4.51-4.7,7.33-2.17,23.24,1.53,31.93,0,0,16.82-.01,33.75.01,50.58h7.96c3.04-17.77,2.41-35.32,2.67-53.24l26.78,3.83,45.07,17.46c1.96,6.86,5.19,13.55,5.62,20.98l10.33.33v-13.32c10.62,1.56,20.45,6.98,30.06,11.3,2.83,1.27,4.17,4.5,4.55,4.66-5.95,7.64-19.57,10.53-28.68,12.57-49.1,10.99-108.95,12.8-158.91,8.69-11.91-.98-74.56-8.37-79.86-13.29-6.15-5.71-2.39-12.71,1.33-18.62,12.04-.27,29.51-10.34,42.58-10.64-1.3,5.14-1.33,13.01-2.65,18.61l10.24-.38,13.69-47.5Z"/><path class="cls-26" d="M610.78,897.89c-1.13,9.37,10.66,12.58,10.66,22.76,0,12.7-24.61,3.99-30.91,4.11-15.53.3-33.43,5.06-49.9,2.02-8.94-2.95-2.11-19.33-1.71-26.24,23.35-.24,50.82-3.71,71.85-2.66Z"/><path class="cls-22" d="M153.07,402.93l-13.31,2.66c-2.8-7.71-13.63-18.36-13.31-29.27,16.73-4.27,22.73-8.78,31.93-23.95,7.85,17.46-.3,34.18-5.32,50.56Z"/><path class="cls-16" d="M57.24,221.97c-5.29-1.42-5.98-5.68-5.27-10.64,5.29,1.42,5.98,5.68,5.27,10.64Z"/><path class="cls-10" d="M1653.92,168.75l-14.86,18.64c-14.69-5.19-32.45,1.4-35.7-18.64h50.56Z"/><path class="cls-2" d="M1675.21,331.08c-.45,2.42.49,5.63,0,7.98-3.37,16.38-11.98,38.2,1.16,53.38,9.42,10.88,14.03.31,14.81,18.47-33.39.85-39.26,36.23-59.88,55.84-3.1-4.4-8.53-7.25-11.97-10.6-.47-.46-6.27-7.3-7.93-9.26-8.52-10.04-25.16-39.56-34.65-43.96l-15.87-30.7-41.37-6.5c9.44,15.97,15.99,33.95,27.97,47.84.35.41-.77,3.31.59,4.63,1.77,1.74,13.08,2.85,17.77,4.96,17.99,8.1,21.42,31.05,29.54,46.29-33.27-27.08-88.16-45.86-130.39-53.22,7.15-4.84,17.42-3.12,24.94-8.33,23.5-16.27,2.79-58.23-3.65-79.49,11.24-3.92,24.98,5,33.26,5,5.62,0,12.87-4.65,21.18-5.11,43.51-2.39,91.14.18,134.5,2.77Z"/><path class="cls-19" d="M1741.74,333.74c5.18,25.32,19.92,54.06,23.48,79.21.72,5.1,1.19,9.28-4.85,11.27-7.37-7.04-22.11-8.36-31.93-7.98-.49-6.42-10.53-23.92-10.58-33.63-.04-6.91,7.4-11.62,5.27-19.58-22.21,4.94-26.83-21.92-47.91-23.96.49-2.36-.45-5.56,0-7.98.55-2.99-1.64-5.37,1.65-8.22,10.68-9.25,35.5-9.51,48.11-2.95,6.8,3.54,10.78,11.35,16.77,13.84Z"/><path class="cls-2" d="M445.79,312.45c-3.23,12.94-9.08,39.35-10.78,51.75-6.07,44.13,5.13,44.61,42.72,54.69-27.27,2.26-100.09,27.54-118.16,48.16-13.18,15.05-8.26,20.83-4.25,36.99,1.29,5.2,4.07,7.26,5.32,10.64.17.46-3.76,1.94.26,8.82,12.99,22.23,68.59,41.09,92.88,52.39.04,10.86-2.21,21.02-2.66,31.93-.77,18.67-1.23,37.13-2.66,55.88-.13,1.76.13,3.57,0,5.32-4.42-.18-8.9.27-13.31,0-.37-.02-1.63-2.79-3.69-2.84-1.84-.05-1.37,4.06-3.02,4.71-5.89,2.34-16.24,2.18-19.9,3.45-11.16-30.84-20.07-66.58-32.62-96.45-5.12-12.19-8.27-23.62-22.59-27.97-22.97-6.97-74.32-1.85-99.14,2.01v-26.61c7.71-1.25,5.78,8.13,12.48,10.2,19.14,5.92,33.25-21.54,43.4-34.15.91-.71,1.7-1.84,2.66-2.66.43-.37,2.76.19,5.32-2.66,3.69-4.1,7.26-10.34,7.98-15.97,11.15-7.83,26.67-31.36,34.59-42.58,8.71-12.33,20.25-16.65,15.31-35.26-1.66-6.25-12.56-20.71-16.64-7.28l-2.65-5.35-6.62,14.67,13.26,1.29v10.64c-2.28,1.99-7.53,2.5-10.68,2.68l.04,18.61c-5.94,1.69-15.08,15.59-21.4,19.85-2.41,1.62-16,8.53-18.52,9.43-11.62,4.12-25.41,3.01-34.59,5.32-13.47-23.86-10.21-51.45-41.83-60.64-3.89-1.13-13.35-3.47-11.39,4.76-.88-.02-2.2-.22-2.66,0l-.02-23.96,17.4-2.56c9-16.96,5.84-31.31,3.23-48.76-.64-4.29-4.6-6.78-4.65-7.21-.37-3.34,6.66-11.92-2.66-18.63,23.72-.33,49.33-2.63,73.07-2.77,45.71-.28,91.48.43,137.16.11Z"/><path class="cls-10" d="M355.31,168.75c-5.45,20.81-48.1,22.97-50.56,0,16.81-.15,33.75-.16,50.56,0Z"/><path class="cls-10" d="M272.82,168.75c.89-.02,1.77.02,2.66,0l-1.33,2.61-1.33-2.61Z"/><path class="cls-2" d="M1504.9,1025.63l5.32-21.29c-1.47,12.86,1.71,9.55-5.32,21.29Z"/><path class="cls-2" d="M1510.23,999.01c1.04-5.72,2.56-8.19,7.98-10.64l-7.98,10.64Z"/><path class="cls-20" d="M1464.99,416.24c42.23,7.36,97.13,26.14,130.39,53.22.26.49,2.5.89,3.53,2.75,1.36,2.48-2.78,5.86,7.08,7.91-.75-11.08,7.94-15.96,13.34-23.96,3.44,3.35,8.87,6.2,11.97,10.6,20.62-19.6,26.48-54.98,59.88-55.84.33,7.73-1.61,21.38.4,27.54,4.49,13.75,37.95-8.08,36.86-22.22,9.82-.37,24.56.94,31.93,7.98,2.59,2.47,4.8,7.01,5.32,10.64,2.05,14.15-3.74,60.12-7.98,74.51-.57,1.92-8.08,7.31-5.3,13.29l7.96-10.63c1.47,15.24-1.06,32.4,0,47.9-5.53,1.68-8.33,5.39-15.97,5.32-18.37-.16-44.47-11.49-63.87-13.31v-21.29c16.03,1.61,51.6,7.97,65.16,2.61,4.2-1.66,7.72-2.05,6.66-7.92l-4.34,5.37-22.25-.04c1.87-12.07-1.4-18.09-10.59-25.3,10.45-10.04,13.71-29.56,15.9-43.89l-18.98,44.81c-12.18-1.7-25.77,3.45-36.87,3.07-5.71-14.4-5.77-29.97-5.35-45.23-5.3,2.4-5.18,11.53-8.39,16.86-4.56,7.59-13.21,12.52-15.54,20.39-3.82-.82-9.44.8-13.31,0-10.38-2.14-14.92-4.97-23.9-10.65-.67,5.66-4.38,11.8-8.03,15.97-33.51,38.37-139.51,55.57-188.94,63.87-2.09-18.33-5.75-15.29-21.29-15.97.27-1.68-.4-3.89,0-5.32,3.72-13.41-3.87-64.02-10.99-78.16-9.7-19.27-19.76-13.83-34.25-20.3-1.61-.72-8.47-9.74-13.31-10.64,0-7.08,0-14.2,0-21.29,12.59-.88,26.39,1.21,38.79.11,3.5-.31,5.76-2.68,6.45-2.77,31.03-4.1,56.21-5.51,87.82,0ZM1470.32,472.1h-34.62s2.67,47.93,2.67,47.93c37.46,6.95,31.7-20.61,31.95-47.93Z"/><path class="cls-23" d="M1760.37,512.03l-7.96,10.63c-2.79-5.98,4.73-11.38,5.3-13.29,1.25.28,2.54,1.45,2.66,2.66Z"/><polygon class="cls-6" points="1864.16 349.68 1864.16 347.07 1872.08 345.69 1868.1 349.68 1864.16 349.68"/><path class="cls-2" d="M1834.88,410.91v31.93c-23-3.61-45.93-8.66-69.19-7.98-.53-3.64-2.73-8.17-5.32-10.64,6.04-1.99,5.58-6.17,4.85-11.27-3.56-25.14-18.31-53.89-23.48-79.21,14.81,6.14,44.42-3.55,58.54-10.64-4.23,8.58.15,15.75,5.27,22.65l-6.6-3.98c-7.99.07-2.09,36.47.15,42.39,4,10.56,25.42,24.51,35.78,26.76Z"/><path class="cls-17" d="M1821.57,301.81c-15.84,3.56-15.02,6.06-9.28,21.23l-8.12-4.77c-2.23.11-3.2,4.48-3.88,4.82-14.12,7.1-43.74,16.78-58.54,10.64-5.99-2.48-9.97-10.3-16.77-13.84-12.61-6.56-37.43-6.3-48.11,2.95-3.29,2.85-1.1,5.24-1.65,8.22-43.35-2.59-90.99-5.16-134.5-2.77-8.31.46-15.56,5.11-21.18,5.11-8.28,0-22.02-8.92-33.26-5-.25-.81.25-1.85,0-2.66-1.95-6.18-3.19-12.41-5.32-18.63,7.34-3.42,11.91-22.48,10.64-29.27,17.32.08,34.56-4.63,52.03-2.81,38.84,4.05,69.18,5.76,109.07,5.59,35.63-.15,74.07.42,108.73-3.03,15.5-1.55,33.97-1.64,46.85-10.4,6.28,8.6,23.22,20.99,13.31,34.59Z"/><path class="cls-16" d="M1822.9,384.3c1.73.89,1.73,1.77,0,2.66v-2.66Z"/><path class="cls-17" d="M153.07,402.93c-2.78,9.07-5.68,12.51-7.98,18.63h-2.66c-2.59-4.39-1.39-12.48-2.66-15.97l13.31-2.66Z"/><path class="cls-16" d="M145.08,780.8v2.66l-13.69,47.5-10.24.38c1.32-5.6,1.35-13.47,2.65-18.61.82-3.26,3.92-11.78,5.32-15.97,1.5-4.47,6.73-9.3,5.32-15.97.56.06,7.69-.09,10.64,0Z"/><path class="cls-23" d="M179.68,778.14l2.66,13.31c-.31.09-1.27,4.03-4.51,4.7-6.63,1.37-13.69,1.75-20.36,3l-12.39-15.68v-2.66c1.77.06,3.55.02,5.32,0,.89-.01,1.78.03,2.66,0,8.86-.34,18.12.98,26.61-2.66Z"/><path class="cls-23" d="M134.44,780.8c1.41,6.67-3.82,11.5-5.32,15.97-4.91,2.53-11.26-2.49-13.31-2.66l5.32-15.97c3.18,1.73,9.48,2.24,13.31,2.66Z"/><path class="cls-16" d="M153.07,780.8c-.88.03-1.77-.01-2.66,0l1.33-2.61,1.33,2.61Z"/><path class="cls-19" d="M1390.48,549.29c-58.05-8.17-98.29,23.22-98.46,82.49.02,10.77-14.44,8.82-22.65,7.97-16.27-1.69-9.4-6.63-12.48-9.91-2.9-3.09-66.3-8.01-76.63-8.7,24.29-10.66,51.79-1.42,77.03-8.14.65-3.46-.05-7.01.14-10.49.4-7.02-1.37-18.17,0-23.95,2.05-8.65,21.24-37.25,26.26-49.58,1.57-3.86,3.86-7.09,2.99-11.62-15.2,16.22-21.32,42.37-31.91,61.2-5.67,10.08-14.37,17.98-18.63,26.61-8.38,2.08-12.71,5.97-22.53,5.44-9.88-.54-19.35-6.68-28.03-10.76s-22.39-5.8-23.95-18.63c-.89-7.34,2.04-14.16,2.66-21.29,9.64.57,22.8,2.46,31.1,2.55,4.11.04,5.12-2.3,6.16-2.55,1.98-.46,5.17,1.09,7.43-.53,1.42-1.24.18-4.33.56-4.79,26.05-31.61,22.96-92.25,71.85-95.8,20.21-1.47,47.49,5.74,63.87-7.98,14.49,6.47,24.55,1.03,34.25,20.3,7.12,14.14,14.71,64.75,10.99,78.16Z"/><path class="cls-21" d="M1185.57,599.85c8.68,4.08,18.15,10.22,28.03,10.76,9.81.53,14.15-3.35,22.53-5.44,7.09-1.76,13.82-3.62,21.29-2.66-.2,3.48.51,7.03-.14,10.49-25.24,6.72-52.73-2.52-77.03,8.14-9.64-.64-19.59.34-29.27,0-21.27-.75-38.93.08-59.76.11-139.26.23-278.02,1.38-416.57-10.75-.81-4.47-1.96-7.93-2.66-13.31,31.43,1.52,63.12,6.12,94.5,7.96,121.11,7.08,243.19,5.85,364.43-.08,18.05-.88,37.86,3.28,54.66-5.21Z"/><path class="cls-7" d="M717.22,546.63l-29.27,10.64c-3.6-8.06-8.77-22.39-12.63-28.53-1.71-2.72.15-4.69-5.98-3.39.23,14.15-.36,28.42-.01,42.56.29,11.52,1.25,18.48,2.66,29.27.7,5.37,1.85,8.83,2.66,13.31,1.85,10.22,6.76,19.44-7.98,18.63-4.03-18.98-4.77-43.21-17.24-58.6-12.8-15.79-39.93-26.9-59.93-23.9l-2.66-26.61c16.88,9.28,41.29,10.76,57.88.67,20.8-12.65,20.77-31.74,19.29-53.89,22.48-1.92,32.38,28.82,40.39,46.1,4.83,10.43,10.65,22.47,12.84,33.73Z"/><path class="cls-18" d="M964.7,488.08c-14.76-11.26-33.11-17.55-31.95-39.91l10.65-.02c-2.59-9.61-10.73-15.08-7.96-26.58,3.81-.69,6.96.3,10.52,1.52,6.43,2.2,6.16,7.06,10.73,9.09l-2.62-29.25,7.94,2.65,1.3-16.02,8.02-2.65,9.36,26.66c4.91-1.6,19.02-25.88,23.51-11.57,5.83,18.58-14.64,46.95-12.88,48.81,9-.29,13.1-12.64,21.09-14.86,13.31-3.69,6.94,13.51-2.49,16.29,13.06,16.13-9.82,27.04-21.27,35.84-7.93-.18-16.02-.17-23.95,0Z"/><path class="cls-13" d="M1129.69,565.26c-3.35,1.21-11.53.52-15.95,2.68l-21.31-63.88h90.48l15.97,42.58c-4.7-1.57-21.15-7.19-18.62,2.62l21.28,10.69c-1.04.24-2.05,2.59-6.16,2.55-8.29-.09-21.46-1.98-31.1-2.55-5.35-.32-9.57-3.54-19.73-2.34-10.83,1.28-11.96,6.61-14.86,7.66Z"/><path class="cls-7" d="M1015.26,498.73c-.8,26.87-2.27,44.86-16.39,68.75l-44.28-.13c-11.8-19.06-21.59-45.9-19.17-68.63h79.83Z"/><path class="cls-13" d="M733.19,549.29c.37-6.98,14.44-34.93,20.47-36.74l80.65,2.17-25.26,55.88c-4.64,6.1-21.78.46-25.3,2.64-4.73-23.6-31.18-20.8-47.87-10.65-.62-4.48-2.94-8.63-2.69-13.3Z"/><path class="cls-23" d="M717.22,546.63c-1.38,8.98,10.18,5.68,15.97,2.66-.25,4.67,2.07,8.82,2.69,13.3,16.69-10.15,43.14-12.95,47.87,10.65-.24.15,1.09,3.92-1.95,5.22-16.61,7.08-49.85,5.61-68.24,12.7-5.67-.63-20.39-15.47-22.95-20.58-1.19-2.37-.93-9.44-2.66-13.31l29.27-10.64Z"/><path class="cls-23" d="M1270.73,373.66c1.74-.18,3.57.08,5.31-.01-4.84,17.24,8.15,13.06,10.26,16.4,1.1,1.74.26,8.42,1.9,12.78,6.35,16.86,29.29,15.38,43.74,10.75-.09,1.76,0,3.56,0,5.32,0,7.08,0,14.2,0,21.29-1.85-.35-33.34,4.41-37.26,5.32l.12-12.08c-38.15.5-20.58-34.46-24.07-59.77Z"/><path class="cls-10" d="M1145.66,224.64c-3.95,6.04-7.73,8.23-9.3,10.67-3.65,5.68-.64,43.81-1.24,54.63-.42,7.61-3.65,14.77-2.77,22.52-4.39-.28-8.89.07-13.31,0-2.39-12.02-.93-28.84.02-41.23.58-7.57,5.76-29.06,4.69-34.31-.72-3.53-5.88-4.8-7.37-14.94,9.74,9.89,17.55,10.44,29.27,2.66Z"/><path class="cls-23" d="M759.8,349.71c3.17-.04,7.97-.57,10.64,0,3.3.7,11.47,6.89,15.97,7.98l-2.69,26.63c-4.33-2.91-8.86-2.01-13.28-2.68-.77-.51-1.38-3.24-4.42-4.78-4.71-2.38-21.39-3.87-22.31-7.61l1.27-17.06c2.61-3.76,10.57-2.43,14.81-2.49Z"/><path class="cls-24" d="M964.7,488.08c7.93-.17,16.02-.18,23.95,0,7,.16,19.2-1.42,24.86.42,8.82,2.88,1.78,9.35,1.75,10.22h-79.83c.44-4.09-.93-8.55,4.36-10.27,8.28-.99,16.63-.19,24.91-.37Z"/><path class="cls-11" d="M1331.93,440.19c4.84.91,11.7,9.93,13.31,10.64-16.37,13.73-43.65,6.52-63.87,7.98-.1-6.45,7.58-11.98,13.31-13.31,3.92-.91,35.41-5.67,37.26-5.32Z"/><path class="cls-23" d="M1164.28,559.93c-.62,7.13-3.55,13.95-2.66,21.29-9.75-.24-33.65-1.61-31.93-15.97,2.91-1.05,4.04-6.38,14.86-7.66,10.16-1.2,14.38,2.02,19.73,2.34Z"/><path class="cls-24" d="M669.32,567.92c-.35-14.14.24-28.42.01-42.56,6.13-1.3,4.27.67,5.98,3.39,3.86,6.14,9.03,20.47,12.63,28.53,1.73,3.87,1.48,10.93,2.66,13.31l-21.29-2.66Z"/><path class="cls-23" d="M1182.91,337.73c.9,2.81,10.14,4.78,10.64,9.29l-26.64-1.3,13.07-8.45c-4.12-25.91-3.04-52.24.27-78.05,10.34-1.23,2.65,4.33,2.65,6.66,0,13.79-2.77,63.2,0,71.85Z"/><path class="cls-2" d="M1158.96,389.62c8.62-6.38,24.01-14.75,34.62-11.95-5.29,8.86-24.95,22.05-34.62,25.25-.55-4.12.79-9.53,0-13.31Z"/><path class="cls-24" d="M770.44,381.64c3.44,2.28,11.89,6.91,12.91,9.71,1.25,3.39,2.11,10.61-3.55,8.88-3.24-.99-24.13-14.08-28.31-17.02-1.39-.98-9.76-3.08-4.99-6.88.96-.76,18.83,4.53,23.94,5.31Z"/><path class="cls-11" d="M767.78,339.06c.03,1.57,2.98,5.38,2.66,7.98v2.66c-2.67-.57-7.47-.04-10.64,0,4.54-6,2.52-6.57-3.83-5.18-7.45,1.63-13.67,5.6-16.28,13.02-1.6,4.57.93,13.18-3.82,13.44-1.92-14.88.29-21.76,10.62-31.92,6.68-.8,14.42.56,21.29,0Z"/><path class="cls-23" d="M1198.88,546.63c5.08,1.7,8.43,1.96,10.64,7.98-.38.46.86,3.55-.56,4.79-2.26,1.63-5.45.07-7.43.53l-21.28-10.69c-2.53-9.81,13.92-4.19,18.62-2.62Z"/><path class="cls-20" d="M477.72,418.9c16.87-1.4,40.9,3.01,58.54,5.32,16.32,2.14,32.41,8.71,50.56,5.32-11.37,28-42.19,30.04-22.45,66.35,3.57,6.58,16.26,20.72,22.45,24.12l2.66,26.61c-1.25.19-2.37,1.39-2.66,2.66-20.85-1.77-42.29-3.9-45.24,21.29-18.59-.15-37.37-5.26-55.42-9.78-29.06-7.27-66.99-18.01-93.27-31.8-14.07-7.38-24.23-17.35-37.58-24.95-4.01-16.16-8.93-21.95,4.25-36.99,18.07-20.62,90.88-45.9,118.16-48.16ZM525.63,456.14l-38.77,2.5c-1.52,11.14-4.34,40.97,5.7,47.85,5.59,3.83,22.83,4.47,27.09-.45,2.93-3.38,7.83-48.06,5.98-49.91Z"/><path class="cls-23" d="M594.81,386.96c-3.67,14.05-1.91,27.61-7.98,42.58-18.15,3.39-34.25-3.19-50.56-5.32-.82-6.88,2.8-10.74,5.32-15.97,5.91-4.66,16.02-.72,21.37-3.92,2.5-1.49,6.83-14.72,13.23-17.37,2.08-.56,11.41-2.47,13.31-2.66,1.05-.1,3.8,2.19,5.32,2.66Z"/><path class="cls-21" d="M584.17,368.34c1.58,4.53,6.69,9.25,5.32,15.97-1.9.19-11.23,2.1-13.31,2.66-.83.22-1.83-.22-2.66,0,.14-6.2-.2-12.44,0-18.63h10.64Z"/><path class="cls-16" d="M576.18,386.96c-6.4,2.65-10.73,15.88-13.23,17.37-5.35,3.19-15.46-.74-21.37,3.92,9-18.67,5.01-9.72,22.89-15.78,3.85-1.31,8.35-5.32,9.05-5.51.83-.22,1.83.22,2.66,0Z"/><path class="cls-12" d="M584.17,368.34h-10.64c.58-17.59,3.39-35.6,3.99-53.25,1.69,18.6.45,35.4,6.65,53.25Z"/><path class="cls-11" d="M1078.32,352.66c10.21-2.55,16.5,14.86,7.09,18-17.42,5.81-18.16-15.23-7.09-18Z"/><path class="cls-23" d="M1073.81,312.45c-.89,0-1.77,0-2.66,0l-5.3-45.24c9.11,9.52,5.99,32.11,7.96,45.24Z"/><path class="cls-2" d="M1459.66,344.39l15.96,39.88c-7.91,3.73-16.46,1.61-23.94,2.69-.92-15.05,3.58-29.02,7.98-42.58Z"/><path class="cls-24" d="M1390.48,389.62c-6.79-1.38-12.19-3.04-18.63-5.37l7.99-18.58c.09.31,3.62,1.13,4.76,4.41,2.23,6.46,3.04,13.31,5.89,19.54Z"/><path class="cls-5" d="M767.78,339.06c-.17-8.41,2.59-14.93,2.77-22.52.39-16.62-2.12-37.66-.11-53.37.5-3.88,2.03-8.25,5.31-3.93-.48,16.32.73,32.85-.01,49.19-.51,11.17-2.72,27.64-5.29,38.61.32-2.6-2.63-6.41-2.66-7.98Z"/><path class="cls-7" d="M1353.22,400.27c18.76,1.39,8.37,9.24,23.95,15.97-.68.09-2.94,2.46-6.45,2.77-12.4,1.1-26.2-.99-38.79-.11,0-1.77-.09-3.56,0-5.32.24-4.42-.2-8.91-.01-13.32,7.03.37,14.29-.5,21.3.02Z"/><path class="cls-6" d="M1028.57,905.88c-6.12,1.77-19.88,8.35-25.08,7.99-4.75-.33-9.37-4.78-16.08-5.42-34.77-3.31-78.47-2.02-113.18-2.58,4.17-4,9.48-2.62,14.53-2.74,46.79-1.08,94.3,1.41,139.81,2.74Z"/><path class="cls-6" d="M1201.54,905.88c1.48,8.04-4.07,5.14-9.19,5.32-44.82,1.61-97.8-3.95-142.49-5.32,4.18-3.99,9.48-2.62,14.53-2.74,45.93-1.06,91.55,2.33,137.15,2.74Z"/><path class="cls-26" d="M1321.29,903.22c.23.17-1.07,4.61,1.75,5.36,4.27,1.14,18.25-1.24,19.53-.03l-3.98,7.97h-70.52c.69-12.85,25.47-7.65,36.04-7.98,5.13-.16,10.68,2.71,9.19-5.32,2.1.12,7.35-.47,7.98,0Z"/><path class="cls-26" d="M1491.61,1006.98c-.48-4.8-1.42-20.23,6.6-18.6,8.07,1.64,3.48,20.54-6.6,18.6Z"/><path class="cls-14" d="M586.83,549.29c9.05.77,26.75,4.74,35.21,8.7,50.23,23.51,24.18,102.36,63.2,136.38,17.91,15.61,17.28-2.94,31.98-1.38,8.64.91,19,5.44,21.36,14.62.87,5.39-14.28,8.29-18.7,9.33-.84.2-1.82-.19-2.66,0h-151.68c-23.64-24.05-15.35-44.96-18.63-74.51-.75-6.75-4.93-18.51-5.32-23.95-.13-1.76.12-3.56,0-5.32-.41-6.15-2.63-14.36-2.66-15.97-.03-1.37,2.57-6.41,2.66-10.64.12-5.17-.58-11.05,0-15.97,2.95-25.19,24.39-23.06,45.24-21.29Z"/><path class="cls-14" d="M1390.48,554.61c15.54.67,19.2-2.36,21.29,15.97.47,4.1-.05,9,0,13.31.14,12.58-2.46,23.68-2.66,34.59-.06,3.55.08,7.1,0,10.64-5.15,23.66-1.84,50.58-10.43,73.51-1.66,4.42-4.54,4.84-5.54,6.33l-190.32,2.67-1.28-7.99c9.73-7.77,15.68-6.62,26.61-10.64,36.05,9.1,56.09-9.4,65.32-42.45,1.9-6.79-.02-14.17,1.2-18.76,2.59-9.72,8.64-32.78,12.79-41.76,15.68-33.93,50.04-36.84,83.01-35.41Z"/><path class="cls-20" d="M1180.25,621.14c10.32.69,73.73,5.61,76.63,8.7,3.08,3.28-3.79,8.22,12.48,9.91,8.21.85,22.68,2.8,22.65-7.97h2.66c-1.22,4.58.69,11.97-1.2,18.76-9.24,33.05-29.27,51.55-65.32,42.45-7.63-1.92-31.1-14.51-37.29-6.86-8.64,16.43-6.19,39.6-2.63,57.43-9.96,9.01-4.89,82.16-7.97,85.17-4.41.18-8.9-.25-13.32-.01-8.06.43-17.95,2.48-23.95,2.66-3.14.09-12.62-1.13-13.42-4.43l5.44-120.64c3.43-3.08,2.38-6.76,2.66-10.64.57-7.89-.4-16.03,0-23.95.76-5.16,1.83-10.67,2.66-15.97,1.27-8.05-.32-17.9,2.66-26.61,1.24-3.62,4.64-6.32,7.98-7.98,9.68.34,19.63-.64,29.27,0Z"/><path class="cls-19" d="M1150.98,621.14c-3.35,1.66-6.74,4.36-7.98,7.98l-41.51,2.39c-10.55,20.23-2.94,44.95-9.33,66.5-6.54.9-13.21.05-19.81.29-5.12.19-10.66-2.71-9.18,5.33-.86-.07-1.8-.04-2.66,0s-1.78-.06-2.66,0v-71.86c-44.28-.52-88.76.75-133.05.01-16.04-.26-33.65-2.65-50.56-2.66-12.34,0-26.91-1.16-38.84-.18-5.35.44-6.52.38-9.06,5.51-.57-1.16,1.75-5.04-1.74-5.37-12.86-1.96-25.12-2.85-38.17-2.62-2.65.05-5.35-.19-7.98,0-3.82.27-7.36.37-10.64,2.66-3.9-2.65-20.68-10.89-23.94-7.97.54,7.18,6.52,9.5,7.81,17.42,1.78,10.93-.67,22.43-2.5,33.12-4.58,2.25-9,5.92-14.12,8.5-6.64,3.34-18.35,2.41-17.81,10.13-39.39,12.34-44.75-33.84-50.56-61.21,14.75.81,9.84-8.41,7.98-18.63,138.56,12.14,277.31,10.98,416.57,10.75,20.83-.03,38.5-.86,59.76-.11Z"/><path class="cls-6" d="M924.78,631.78c44.29.73,88.77-.53,133.07-.01v71.86c-31.71,2.17-64.16,3.15-95.81,5.32-26.79-6.91-34.87-24.51-37.26-50.56-.06-.71,2.56-3.88,2.49-6.74-.17-6.65-3.71-13-2.49-19.87Z"/><path class="cls-23" d="M767.78,629.12c1.73,1.17,5.12,2.45,5.32,2.66.54.56,7.21,11.73,7.98,13.31,1.43,2.92,1.71,5.3,2.66,7.98,18.26,51.71,8.01,135.54,16.68,192.21,3.15,20.57,11.5,13.19,23.23,25.97-8.37-.95-19.58,1.8-27.4-.52-2.34-.69-18.18-15.98-19.13-18.12-3.13-7-2.6-30.28-4.7-40.54-4.88-23.92-16.57-51.05-20.62-73.84-.73-4.11-2.73-37.39-2.08-40.62,1.91-9.44,14.3-22.69,17.99-32.59-5.82.69-13.26,4.08-18.57,6.68,1.83-10.69,4.29-22.2,2.5-33.12-1.29-7.92-7.27-10.24-7.81-17.42,3.26-2.92,20.04,5.32,23.94,7.97Z"/><path class="cls-6" d="M1409.1,618.48c11.1,1.8,2.62-21.31,5.35-23.92,16.98,2.93,59.5-21.41,61.18,7.96.3,5.23-.79,8.09,0,15.97,1.48,14.75,3.52,28.23,5.32,42.58.63,5.05-.64,10.92,0,15.97-23.1-5.17-45.2,11.59-69.36,4.16-7.34-5.11.15-37.21.31-45.63.07-3.73-2.81-6.08-2.8-6.43.08-3.54-.06-7.1,0-10.64Z"/><path class="cls-16" d="M1201.54,703.63l1.28,7.99,190.32-2.67c-3.79,5.7-2.56,10.59-13.33,10.68l34.6,151.63-8.02-1.77-34.8-149.64-34.23-.15c-.15,4.73.66,13.13-6.74,13.22l-4.4-12.95-10.25-.39,7.96,165.02h-7.96s-10.66-165-10.66-165h-50.56c-6.66,20.54-3.16,43.57-5.32,63.87-2.7,25.41-5.74,51.18-7.98,77.17-.19,2.16-2.18,6.43-2.66,10.64-.68,5.96.51,12.57-.01,18.61-13.66.46-9.74-4.34-7.97-13.29.95-4.81,7.57-11.69-2.66-15.97.51-1.06,2.43-1.95,2.66-2.66,9.11-28.65,7.83-74.78,10.64-106.44.99-11.09,4.7-22.6,2.68-34.61-5.3-.14-10.67.2-15.98.01-11.47-.4-23.1.3-34.58-.01-1.47-8.3,3.15-9.44,7.97-13.29Z"/><path class="cls-4" d="M1228.15,692.99c-10.93,4.03-16.88,2.87-26.61,10.64-4.82,3.85-9.44,4.99-7.97,13.29,11.48.32,23.11-.39,34.58.01,1.9,11.71,5.37,25.59,13.31,34.59-2.81,31.67-1.53,77.8-10.64,106.44-8.43-38.06-35.1-77.01-42.58-114.43-3.56-17.82-6.01-40.99,2.63-57.43,6.19-7.65,29.66,4.94,37.29,6.86Z"/><path class="cls-16" d="M717.22,716.94c-4.44,1-13.84-2.34-15.77,4.32-.37,1.28,2.36,16.95,2.47,22.29.14,7.06-.39,14.25,0,21.29.53,9.45,5.16,18.92,5.32,21.29.11,1.58-3.53,7.88-2.72,14.49,3.4,28,11.99,55.57,13.35,83.95l-7.95.03c-3.05-2.86-2.96-54.31-13.32-61.22.01-.59-4.31-4.37-2.64-8l5.28,2.69,2.67-18.63c-2.58.21-5.48-.39-7.97-.01-1.2-6.61,4.99-12.07,5.38-17.63.27-3.8-2.74-5.97-2.72-6.32.97-19.5.72-36.26-5.69-55.52-10.21.95-41.49-3.78-47.53,2.3-5.34,5.37-2.01,25.39-2.66,34.59-.89,12.51-2.07,24.61-2.66,37.26-1.3,27.84-2,55.91-2.68,83.81-6.76,14.78-10.79,3.03-10.83-8.01-.09-23.82,4.26-53.44,5.52-78.46.63-12.53,2.16-24.79,2.66-37.26.46-11.47-.33-23.12,0-34.59h-51.89l-36.49,147.13-10.07,4.54,34.59-150.05c-.07-1.87-3.91-2.84-5.33-4.28h151.68Z"/><path class="cls-6" d="M874.22,629.12c4.02,14.44,19.45,24.85,26.61,34.59,8.95,12.19,7.65,25.9,7.98,39.92-3.76,1.92-6.87,4.43-11.4,4.51-7.02.13-43-1.54-47.09-3.24-19.41-8.08-5.35-25.47-5.87-28.67-.32-1.92-3.53-4.15-4.07-6.59-1.72-7.77.93-15.62-8.74-19.23-.15-.86.16-1.8,0-2.66-.84-4.6-1.73-5.17-2.66-7.98-.56-1.68-1.82-3.61-2.66-5.32,2.54-5.13,3.71-5.07,9.06-5.51,11.92-.98,26.5.17,38.84.18Z"/><path class="cls-13" d="M469.74,669.04c-2.66,23.51-5.22,47.16-8,70.5-4.82,40.38-10.84,80.77-16.01,121.09l-7.96-1.56,5.36-158.1,5.32.02c-.38-5.02,2.06-13.06-2.65-15.99.36-5.42,2.25-10.54,2.66-15.97.13-1.76-.13-3.57,0-5.32,7.37,2.48,12.86,7.18,21.29,5.32Z"/><path class="cls-4" d="M751.81,738.23c-5.92-1.32-5.64,3.26-7.93,6.57-6.26,9.05-11.72,16.79-18.68,25.36-5.49-5.44-14.02-5.53-21.29-5.32-.39-7.03.14-14.23,0-21.29,7.08-6.08,13.32-17.35,15.97-26.61,4.42-1.03,19.57-3.94,18.7-9.33-2.36-9.18-12.73-13.71-21.36-14.62v-2.66c-.54-7.72,11.17-6.79,17.81-10.13,5.12-2.58,9.54-6.25,14.12-8.5,5.31-2.6,12.75-5.99,18.57-6.68-3.69,9.9-16.07,23.15-17.99,32.59-.66,3.23,1.35,36.51,2.08,40.62Z"/><path class="cls-14" d="M786.41,626.46c13.05-.23,25.31.66,38.17,2.62,3.49.32,1.18,4.21,1.74,5.37.84,1.71,2.1,3.64,2.66,5.32l2.66,7.98c.16.86-.15,1.8,0,2.66,1.63,9.51,7.48,47.52,4.01,53.24-14.53,23.98-33.06-35.03-35.94-42.6l-2.66-5.32c-.29-.78.3-1.89,0-2.66-2.97-7.75-4.07-10.97-7.98-18.63-1.04-2.03-.88-5.76-2.66-7.98Z"/><path class="cls-23" d="M376.6,724.92c9.81,22.58,6.28,40.26,26.61,61.21l5.32,5.32c.85,1.54,1.08,1.83,2.66,2.66l2.66,2.66c-.44,1.34.29,3.67,0,5.32-7.13-1.53-12.71-.09-22.02-3.27s-17.4-10.1-25.88-15.36c.42-4.85-13.43-52.72-15.97-55.88l17.31-15.95c1.2,4.95,7.67,9.54,9.3,13.29Z"/><path class="cls-6" d="M1135.01,706.29c-13.36-5.48-20.43-4.75-34.59-2.66v-49.23c0-9.3,17.73-23.41,28.2-14.89,7.7,6.27-2.23,19.25,11.71,16.22-.83,5.3-1.9,10.81-2.66,15.97-.9,6.11-7.19,17.54,0,23.95-.28,3.88.77,7.56-2.66,10.64Z"/><path class="cls-21" d="M645.37,722.26c7.44,1.38,26.66,13.65,30.79,18.44,7.59,8.83,9.25,31.1,22.43,34.78-.02.34,2.99,2.51,2.72,6.32-.4,5.57-6.59,11.03-5.38,17.63-.42.06-7.63,2.44-7.98,2.66-5.56-11.58-23.78-.36-31.93-7.98.55-.07,2.1-2.15,4.24-2.45,4.99-.69,19.08,2.52,17.01-4.15-3.35-10.79-20.49-33.68-34.56-30.65.65-9.2-2.68-29.22,2.66-34.59Z"/><path class="cls-24" d="M541.59,586.55c-.1,4.23-2.69,9.28-2.66,10.64-3.99-.63-9.81.9-13.31,0-3.78-.97-15.09-8.29-20.79-9.81-3.85-1.03-26.06-4.6-27.1-3.51,1.97,6.94-1.87,13.2-2.66,18.64-7.15-3.82-5.4-20.17-8.57-23.36-1.86-1.87-9.47-1.74-12.72-3.25-24.29-11.3-79.88-30.16-92.88-52.39-4.02-6.87-.09-8.36-.26-8.82,47.97,45.35,118.75,56.85,180.95,71.85Z"/><path class="cls-23" d="M924.78,658.39c2.39,26.05,10.47,43.65,37.26,50.56-.35.02-2.7,2.39-6.4,2.8-14.59,1.6-31.89-1.44-46.84-.13-.09-2.65.08-5.33.02-7.99-.34-14.01.97-27.73-7.98-39.92,5.47-7.47,15.75-5.14,23.95-5.32Z"/><path class="cls-23" d="M1270.73,860.64c-8.47-3.92-19.36,2.08-29.27,0,2.24-25.99,5.28-51.76,7.98-77.17,4.64,18.44,16.52,40.04,20.67,57.83,1.53,6.57-.01,13.06.62,19.34Z"/><path class="cls-7" d="M1135.01,852.65c.35,0,3.06,2.75,6.45,2.76,9.39.02,18.79-.18,28.15-.1-.27,6.01,1.94,11.3-2.66,15.97h-74.51c-6.12-2.21-1.59-5.59,1.85-7.47,3.71-2.03,37.08-11.17,40.73-11.16Z"/><path class="cls-21" d="M451.11,607.83l5.32-.02v10.68c5.76.02,13.78-1.73,15.97,5.31-1.55,14.07-1.02,30.71-2.66,45.24-8.43,1.86-13.92-2.84-21.29-5.32,1.43-18.75,1.89-37.21,2.66-55.88Z"/><path class="cls-23" d="M695.93,799.43c2.49-.38,5.39.22,7.97.01l-2.67,18.63-5.28-2.69c-1.67,3.63,2.65,7.42,2.64,8-.29,11.57-9.14,21.7-.01,37.24-15.64-5.31-27.13-24.29-23.38-40.66.8-3.5,10.41-16.42,12.75-17.87.36-.22,7.57-2.6,7.98-2.66Z"/><path class="cls-11" d="M642.71,756.85c14.07-3.03,31.21,19.87,34.56,30.65,2.07,6.67-12.02,3.46-17.01,4.15-2.14.3-3.69,2.38-4.24,2.45-5.05.61-10.79-.42-15.97,0,.59-12.64,1.77-24.75,2.66-37.26Z"/><path class="cls-19" d="M413.86,802.09c6.52,1.4,9.07,4.29,13.28,9.38-14.85,22.39-41.24-8.37-54.58-12-6.99-1.9-2.66,6.79-3.95,7.95h-7.96c-3.59-9.48,4.74-17.37,5.31-23.95,8.48,5.26,16.21,12.06,25.88,15.36s14.89,1.73,22.02,3.27Z"/><path class="cls-23" d="M435.14,669.04c-.4,6.19-5.5,10.6-10.64,13.31-6.94,3.65-35.03,12.7-38.8,18.58l6.87,16.01c-.27,1.36.78,3.75-.39,4.92-1.55,1.16-3.62.08-4.94.4l-15.77-19.58c.84-4.95,30.81-26.16,37.06-28.32,3.66-1.27,14.01-1.11,19.9-3.45,1.65-.66,1.18-4.77,3.02-4.71,2.06.06,3.32,2.82,3.69,2.84Z"/><path class="cls-19" d="M424.5,682.34l.02,5.26,18.61,2.73c-.18,2.64.18,5.34,0,7.98-6.77-.58-10.57,4.81-17.24,5.53-7.65.82-17.44-3.69-20.93-3.06-2.08.37-2.34,4.81-4.65,6.61-6.88,5.35-5.12-3.5-7.74,9.55l-6.87-16.01c3.77-5.88,31.86-14.93,38.8-18.58Z"/><path class="cls-18" d="M546.91,642.43c-11.97,1.97-14.87,17.33-21.28,25.49-9.93,1.94-12.96-3.96-10.59-12.96.62-2.36,5.56-1.84,6.73-7,.91-4.02-1.69-8.27.38-12.75,2.59-5.59,14.63-11.84,19.43-16.72.39,5.44,4.57,17.2,5.32,23.95Z"/><path class="cls-9" d="M453.77,575.9c3.24,1.51,10.85,1.38,12.72,3.25,3.18,3.19,1.43,19.54,8.57,23.36-.96,6.55-1.98,15.1-2.66,21.29-2.19-7.04-10.2-5.3-15.98-5.31v-10.68s-5.31.02-5.31.02c.45-10.92,2.7-21.07,2.66-31.93Z"/><path class="cls-23" d="M1166.94,828.7c.3,1.65-.45,4.02,0,5.32l2.66,5.32c.49,4.76.22,11.05,0,15.97-9.36-.09-18.76.11-28.15.1-3.38,0-6.09-2.76-6.45-2.76,4.7-6.13,7.94-13.43,7.98-21.29,6-.18,15.89-2.23,23.95-2.66Z"/><path class="cls-11" d="M632.06,791.45c-32.1-.74-25.01-31.42,2.66-37.26-.5,12.46-2.03,24.72-2.66,37.26Z"/><path class="cls-9" d="M1103.08,730.24c-13.95-6.12-27.77-7.65-42.58-2.66-3.39-10.54-1.06-12.98,0-23.95.86-.04,1.8-.07,2.66,0,16.41,1.37,9.64,5.23,16.17,9.11,10.72,6.37,18.61,2.88,23.75,17.5Z"/><path class="cls-1" d="M1103.08,730.24c1.22,3.47,1.29,9.34,2.67,13.29-10.68,5.56-12.02-6.58-21.15-9.45-8.37-2.63-16.57.04-24.1-1.19v-2.66c-.19-.84.26-1.87,0-2.66,14.81-4.99,28.63-3.46,42.58,2.66Z"/><path class="cls-7" d="M1270.73,860.64c.15,1.53,4.84,6.2,2.67,10.63h-34.6c.48-4.2,2.48-8.48,2.66-10.63,9.91,2.08,20.81-3.92,29.27,0Z"/><path class="cls-23" d="M725.2,770.16c-.34.42.56,3.03-.74,4.51-2.78,3.19-11.64,7.52-15.22,11.45-.17-2.36-4.79-11.84-5.32-21.29,7.26-.21,15.8-.12,21.29,5.32Z"/><path class="cls-12" d="M538.93,597.19c.03,1.61,2.25,9.82,2.66,15.97-9.08,1.88-22.62-6.6-15.97-15.97,3.5.9,9.32-.63,13.31,0Z"/><path class="cls-2" d="M1166.94,871.28c-3.52,3.57-4.78,2.46-9.08,2.82-15.87,1.31-40.17.87-56.34,0-3.23-.18-7.52.82-9.09-2.81h74.51Z"/><path class="cls-2" d="M797.05,653.07h-13.31c-.95-2.69-1.23-5.06-2.66-7.98l5.3,2.66.54-11.53,2.15-1.78c3.92,7.66,5.02,10.88,7.98,18.63Z"/><path class="cls-21" d="M445.79,685.01c4.71,2.93,2.27,10.96,2.65,15.99l-5.32-.02c.06-.88-.06-1.78,0-2.66.18-2.64-.18-5.34,0-7.98s2.63-4.83,2.66-5.32Z"/><path class="cls-4" d="M1230.81,876.6c-2.04-5.85-5.31-10.49-2.66-15.97,10.23,4.28,3.61,11.16,2.66,15.97Z"/><path class="cls-19" d="M403.21,786.13c2.12,2.19.51-3.42,5.32,5.32l-5.32-5.32Z"/><path class="cls-2" d="M799.71,661.06c-.45-1.18-1.74-2.84-2.66-5.32l2.66,5.32Z"/><path class="cls-7" d="M1169.61,839.35l-2.66-5.32c.1.28,2.2.84,2.66,5.32Z"/><path class="cls-19" d="M411.19,794.11c.97.51,3.7-.39,5.33.03.78,2.11-2.52,2.2-2.66,2.63l-2.66-2.66Z"/><path class="cls-9" d="M1060.5,732.91c-1.15-.19-2.15.23-2.62-1.34l2.62-1.32v2.66Z"/><path class="cls-8" d="M264.83,613.16c16.38-1.82,25.45-21.44,42.6-19.96-12.55,11.35-25.12,22.96-42.6,25.28-.06-1.68.38-4.18,0-5.32Z"/><polygon class="cls-8" points="352.64 700.99 351.33 708.94 347.35 704.92 347.34 700.99 352.64 700.99"/><path class="cls-8" d="M336.66,677.03c-1.62,8.47,10.05,13.29,10.65,21.26l-15.92-17.33,5.27-3.93Z"/><polygon class="cls-8" points="294.08 623.79 291.47 623.79 290.09 615.87 294.08 619.85 294.08 623.79"/><path class="cls-9" d="M192.98,416.24c6.59.4,11.49,5.99,20.03,5.6,8.05-.38,7.88-4.93,9.25-5.6.46-.22,1.78-.02,2.66,0,17.05.36,31.76,51.39,31.93,66.53-11.5,6.2-24.3,18.37-37.26,23.95-5.31-3.08-6.4,2.24-13.37-9.26-12.41-20.46-17.72-49.04-31.45-69.74-.68-7.21,12.48-11.83,18.21-11.48Z"/><path class="cls-23" d="M238.22,333.74c.05.43,4.01,2.92,4.65,7.21,2.61,17.44,5.77,31.79-3.23,48.76l-17.4,2.56.02,23.96c-1.37.66-1.19,5.22-9.25,5.6-8.53.4-13.44-5.2-20.03-5.6-1.2-11.1,5.72-28.23,4.58-38.28-.81-7.09-11.91-11.95-9.9-18.88,2.29-7.9,13.88-.71,18.57-2.61,6.04-2.45,20.71-22.57,31.99-22.72Z"/><path class="cls-23" d="M312.73,466.8c-19.17,20.28-7.71,28.07,13.31,13.31-.73,5.63-4.3,11.87-7.98,15.97l-5.32,2.66c-.96.82-1.75,1.96-2.66,2.66-5.68,4.42-12.68,7.3-17.29,13.26l-10.62-21.22c-10.07,5.29-18.95,11.8-27.97,18.6-8.24,6.22-15.45,8.98-21.29,18.63-7.71-1.71-10.72-22.45-13.31-23.95,12.96-5.58,25.76-17.75,37.26-23.95,3.02-1.63,20.13-10.35,21.29-10.64,9.19-2.31,22.97-1.2,34.59-5.32Z"/><path class="cls-19" d="M310.07,501.39c-10.15,12.61-24.26,40.06-43.4,34.15-6.7-2.07-4.77-11.44-12.48-10.2v-13.31c9.01-6.81,17.9-13.31,27.97-18.6l10.62,21.22c4.62-5.96,11.62-8.84,17.29-13.26Z"/><path class="cls-6" d="M1632.64,501.39l-10.64,8.02c-2.24,3.02,5.34,10.23,8.17,11.75,17.5,9.36,31.38,7.59,50.37,9.51v10.64c-14.56,1.2-35.92-.7-47.9,7.98-4.61.09-22.53,2.62-26.74,3.86-5.81,1.71-11.56,7.98-15.84,12.11-30.06,29.07-21.11,58.6-23.95,95.8h-2.66c-4.32,1.89-2.15,7.35-2.66,10.64-.68,4.4-2.01,7.37-2.66,10.64h-55.88c-.49-7.91.43-16.03,0-23.95-.71-13.2-1.98-26.55-2.66-39.92-.64-12.53-1.74-24.78-2.66-37.26,18.84-15.66,24.75-11.64,45.72-19.48,13.2-4.93,40.15-17.76,48.98-28.25,4.36-5.17,2.61-8.62,3.76-10.82,2.26-4.32,11.62-13.08,5.32-15.97,3.64-4.17,7.35-10.31,8.03-15.97,8.98,5.68,13.52,8.51,23.9,10.65Z"/><path class="cls-23" d="M1590.06,565.26c10.57,1.53,10.46,17.14,15.42,25.83,1.72,3.01,15.79,23.41,17.07,24.15,4.22,2.42,17.13-.33,23.39.59v2.66c-9.6,0-19.34-.42-28.92.35-8.7,28.77-14.81,58.22-21.64,87.47-3.6,15.39-4.04,30.35-6.79,42.88-4.04,18.44-30.3,39.94-50.01,36.64l-4.39-6.3c8.13-7.25,13.32-13.24,18.61-22.67,13.69-24.4,13.46-58.54,10.64-85.15-.18-1.74.13-3.57,0-5.32,2.59-.72,2.49-3.07,2.66-5.32,2.84-37.2-6.12-66.73,23.95-95.8Z"/><path class="cls-4" d="M1645.94,618.48c.89,0,1.77,0,2.66,0,1.77,0,3.55,0,5.32,0-9.74,32.47,5.44,87.7-5.32,117.09-.37,1.02.83,3.45-.49,4.81-1.24,1.26-3.68.15-4.83.52h-2.66c-3.24-1.15-7.71-1.29-10.64-2.66-15-6.99-24-20.06-34.59-31.93,6.84-29.25,12.95-58.7,21.64-87.47,9.58-.77,19.31-.35,28.92-.35Z"/><path class="cls-7" d="M1680.54,541.31v10.64c-11.76-1.1-37.33-2.88-47.9-2.66,11.98-8.69,33.34-6.78,47.9-7.98Z"/><path class="cls-5" d="M1648.6,618.48c-.89,0-1.77,0-2.66,0v-2.66c1.25.18,2.37,1.38,2.66,2.66Z"/><path class="cls-16" d="M1640.62,740.89v2.66c-6.59,20.5-7.83,46.56-13.31,66.53-1.08,3.95-9.2,21.04-11.97,21.24-7.69-4.86-1.88-9.01-1.33-13.25,3.47-26.94,11.32-53.13,15.97-79.83,2.94,1.37,7.41,1.51,10.64,2.66Z"/><path class="cls-5" d="M1640.62,743.55v-2.66h2.66c-.71.22-1.65,2.1-2.66,2.66Z"/><path class="cls-7" d="M1552.8,756.85c-1.55-25.5.42-49.66,5.32-74.51.65-3.28,1.98-6.24,2.66-10.64h2.66c2.81,26.61,3.04,60.75-10.64,85.15Z"/><path class="cls-7" d="M1589.75,788.51c-.33.38-8.41,2.23-9.7,2.25-17.36.25.29-11.4,6.02-17.89,4.48,2.24,5.57,13.46,3.68,15.64Z"/><path class="cls-21" d="M1499.58,618.48c.68,13.36,1.95,26.71,2.66,39.92l-21.29,2.66c-1.8-14.35-3.84-27.82-5.32-42.58h23.95Z"/><path class="cls-26" d="M812.38,941.12c4.58,4.59,5.75,14.32,18.04,17.92,11.62,22.47-43.47,17.97-48.71,12.73-4.73-4.74-4.7-25.97,0-30.67,4.74-4.74,25.94-4.71,30.67.02Z"/><path class="cls-23" d="M1675.21,339.06c21.08,2.04,25.7,28.9,47.91,23.96,2.13,7.96-5.31,12.67-5.27,19.58.05,9.72,10.09,27.22,10.58,33.63,1.09,14.13-32.37,35.96-36.86,22.22-2.01-6.16-.07-19.81-.4-27.54-.77-18.16-5.39-7.59-14.81-18.47-13.14-15.18-4.53-37.01-1.16-53.38Z"/><path class="cls-23" d="M1576.75,402.93c9.49,4.41,26.13,33.92,34.65,43.96,1.66,1.96,7.46,8.8,7.93,9.26-5.4,8-14.09,12.89-13.34,23.96-9.86-2.05-5.72-5.43-7.08-7.91-1.03-1.86-3.27-2.26-3.53-2.75-8.13-15.24-11.55-38.19-29.54-46.29-4.69-2.11-16-3.22-17.77-4.96-1.36-1.33-.24-4.23-.59-4.63,12.06,2.03,12.1-12.37,13.35-13.32.64-.49,15.19,2.34,15.92,2.68Z"/><path class="cls-25" d="M1547.48,413.57c-11.99-13.89-18.54-31.87-27.97-47.84l41.37,6.5,15.87,30.7c-.73-.34-15.28-3.17-15.92-2.68-1.25.96-1.3,15.35-13.35,13.32Z"/><path class="cls-21" d="M541.59,570.58c-.58,4.91.12,10.8,0,15.97-62.2-15-132.99-26.5-180.95-71.85-1.26-3.39-4.03-5.44-5.32-10.64,13.35,7.6,23.52,17.57,37.58,24.95,26.28,13.79,64.21,24.53,93.27,31.8,18.05,4.51,36.83,9.63,55.42,9.78Z"/><path class="cls-19" d="M224.92,416.24c-1.96-8.23,7.5-5.89,11.39-4.76,31.62,9.19,28.36,36.78,41.83,60.64-1.15.29-18.26,9.01-21.29,10.64-.18-15.13-14.88-66.17-31.93-66.53Z"/><path class="cls-1" d="M360.63,437.52c-7.93,11.22-23.45,34.75-34.59,42.58-21.01,14.76-32.47,6.98-13.31-13.31,2.52-.89,16.11-7.8,18.52-9.43,6.32-4.26,15.46-18.16,21.4-19.85,2.07-.59,5.54.4,7.98,0Z"/><path class="cls-16" d="M363.29,405.59l-13.26-1.29,6.62-14.67,2.65,5.35c4.08-13.43,14.99,1.03,16.64,7.28,4.94,18.61-6.6,22.94-15.31,35.26-2.44.4-5.91-.59-7.98,0l-.04-18.61c3.15-.19,8.4-.7,10.68-2.68,4.36-3.79,2.55-8.17,2.63-13.3l-2.63,2.66Z"/><path class="cls-22" d="M448.45,669.04c-.41,5.43-2.3,10.55-2.66,15.97-.03.49-2.49,2.76-2.66,5.32l-18.61-2.73-.02-5.26c5.14-2.71,10.25-7.12,10.64-13.31,4.4.27,8.89-.18,13.31,0Z"/><path class="cls-24" d="M363.29,416.24v-10.64l2.63-2.66c-.08,5.13,1.73,9.52-2.63,13.3Z"/><path class="cls-19" d="M318.06,496.07c-2.56,2.85-4.89,2.29-5.32,2.66l5.32-2.66Z"/><path class="cls-23" d="M1675.21,509.37c11.11.38,24.69-4.77,36.87-3.07l18.98-44.81c-2.18,14.34-5.45,33.85-15.9,43.89,9.19,7.21,12.46,13.23,10.59,25.3l22.25.04,4.34-5.37c1.06,5.87-2.46,6.26-6.66,7.92-13.56,5.36-49.14-1-65.16-2.61-18.99-1.91-32.86-.15-50.37-9.51-2.83-1.51-10.41-8.73-8.17-11.75l10.64-8.02c3.86.8,9.49-.82,13.31,0,7.73,1.66,20.91,7.7,29.27,7.98Z"/><path class="cls-21" d="M1595.38,522.68c-52.98,38.46-120.02,51.09-183.62,61.21-.05-4.31.47-9.2,0-13.31,49.43-8.3,155.43-25.49,188.94-63.87,6.3,2.88-3.06,11.64-5.32,15.97Z"/><path class="cls-12" d="M1470.32,472.1c-.26,27.32,5.51,54.88-31.95,47.93l-2.67-47.93h34.62ZM1459.4,488.36c-1.85-1.27-6.19-.2-8.71.04-6.75,2.1-5.86,19.25-.3,20.96,11.03,3,14.37-17.34,9.02-21Z"/><path class="cls-16" d="M1390.48,549.29c-.4,1.43.27,3.64,0,5.32-32.96-1.43-67.33,1.49-83.01,35.41-4.15,8.98-10.21,32.04-12.79,41.76h-2.66c.17-59.27,40.41-90.66,98.46-82.49Z"/><path class="cls-5" d="M1675.21,509.37c-8.36-.29-21.54-6.32-29.27-7.98,2.33-7.86,10.98-12.8,15.54-20.39,3.2-5.33,3.09-14.45,8.39-16.86-.42,15.25-.36,30.82,5.35,45.23Z"/><path class="cls-1" d="M1257.42,578.56h-2.66c10.59-18.83,16.71-44.98,31.91-61.2.87,4.54-1.42,7.77-2.99,11.62-5.02,12.33-24.21,40.93-26.26,49.58Z"/><path class="cls-16" d="M1257.42,602.51c-7.47-.96-14.2.9-21.29,2.66,4.26-8.63,12.96-16.53,18.63-26.61h2.66c-1.37,5.78.4,16.93,0,23.95Z"/><path class="cls-16" d="M666.66,629.12c5.81,27.36,11.17,73.55,50.56,61.21v2.66c-14.7-1.56-14.07,16.99-31.98,1.38-39.02-34.02-12.98-112.87-63.2-136.38-8.46-3.96-26.16-7.93-35.21-8.7.29-1.28,1.41-2.47,2.66-2.66,20-3.01,47.12,8.11,59.93,23.9,12.48,15.39,13.21,39.62,17.24,58.6Z"/><path class="cls-5" d="M525.63,456.14c1.85,1.85-3.05,46.53-5.98,49.91-4.26,4.92-21.51,4.28-27.09.45-10.04-6.88-7.22-36.72-5.7-47.85l38.77-2.5ZM511.93,472.5h-9.88c-4.35,7.79-3.14,15.03,3.64,20.9,9.68-2.16,10.62-13.6,6.24-20.9Z"/><path class="cls-15" d="M717.22,716.94c.84-.19,1.82.2,2.66,0-2.65,9.26-8.88,20.53-15.97,26.61-.11-5.35-2.84-21.01-2.47-22.29,1.94-6.66,11.33-3.32,15.77-4.32Z"/><path class="cls-19" d="M1496.92,581.22c-.81.67-4.58.38-6.7,2.52-5.62,5.67-7.5,14.51-14.59,18.77-1.68-29.37-44.2-5.03-61.18-7.96-2.73,2.62,5.75,25.72-5.35,23.92.2-10.91,2.8-22.01,2.66-34.59,63.6-10.12,130.64-22.75,183.62-61.21-1.15,2.21.6,5.65-3.76,10.82-8.83,10.48-35.78,23.31-48.98,28.25-20.97,7.84-26.88,3.82-45.72,19.48Z"/><path class="cls-22" d="M1137.67,695.65c-7.19-6.41-.9-17.84,0-23.95-.4,7.92.57,16.06,0,23.95Z"/><path class="cls-7" d="M924.78,631.78c-1.22,6.86,2.32,13.22,2.49,19.87.07,2.87-2.56,6.04-2.49,6.74-8.2.18-18.48-2.15-23.95,5.32-7.16-9.74-22.59-20.16-26.61-34.59,16.91.01,34.52,2.4,50.56,2.66Z"/><path class="cls-22" d="M786.41,626.46c1.78,2.22,1.62,5.95,2.66,7.98l-2.15,1.78-.54,11.53-5.3-2.66c-.77-1.58-7.45-12.74-7.98-13.31h5.32s0-5.32,0-5.32c2.63-.19,5.34.05,7.98,0Z"/><path class="cls-2" d="M778.42,626.46v5.32s-5.32,0-5.32,0c-.21-.22-3.59-1.49-5.32-2.66,3.28-2.29,6.83-2.39,10.64-2.66Z"/><path class="cls-9" d="M1496.92,581.22c.92,12.47,2.02,24.73,2.66,37.26h-23.95c-.79-7.87.3-10.73,0-15.97,7.09-4.26,8.97-13.1,14.59-18.77,2.12-2.14,5.89-1.84,6.7-2.52Z"/><path class="cls-17" d="M1228.15,716.94c5.31.19,10.68-.16,15.98-.01,2.03,12.01-1.69,23.52-2.68,34.61-7.94-9.01-11.41-22.89-13.31-34.59Z"/><path class="cls-9" d="M645.37,722.26c6.04-6.08,37.32-1.35,47.53-2.3,6.41,19.26,6.66,36.02,5.69,55.52-13.19-3.68-14.84-25.95-22.43-34.78-4.12-4.79-23.35-17.06-30.79-18.44Z"/><path class="cls-22" d="M831.65,647.75l-2.66-7.98c.93,2.81,1.82,3.38,2.66,7.98Z"/><path class="cls-22" d="M1563.45,666.38c.13,1.75-.18,3.58,0,5.32h-2.66c.51-3.3-1.65-8.75,2.66-10.64.09,1.76-.13,3.57,0,5.32Z"/><path class="cls-7" d="M1563.45,666.38c-.13-1.76.09-3.56,0-5.32h2.66c-.17,2.25-.07,4.61-2.66,5.32Z"/><path class="cls-16" d="M1459.4,488.36c5.36,3.67,2.02,24-9.02,21-5.55-1.72-6.45-18.87.3-20.96,2.53-.24,6.86-1.31,8.71-.04Z"/><path class="cls-16" d="M511.93,472.5c4.39,7.29,3.45,18.73-6.24,20.9-6.78-5.86-8-13.11-3.64-20.9h9.88Z"/></g></svg>
diff --git a/static/images/events/people-table-working.svg b/static/images/events/people-table-working.svg
new file mode 100644
index 00000000..04e28085
--- /dev/null
+++ b/static/images/events/people-table-working.svg
@@ -0,0 +1 @@
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="1100" zoomAndPan="magnify" viewBox="0 0 824.88 449.999984" height="600" preserveAspectRatio="xMidYMid meet" version="1.0"><defs><clipPath id="326b62e356"><path d="M 0 0.03125 L 824.761719 0.03125 L 824.761719 449.964844 L 0 449.964844 Z M 0 0.03125 " clip-rule="nonzero"/></clipPath><clipPath id="b6643e95a8"><path d="M 12.089844 0.03125 L 812.972656 0.03125 L 812.972656 449.75 L 12.089844 449.75 Z M 12.089844 0.03125 " clip-rule="nonzero"/></clipPath><clipPath id="4901f7966f"><path d="M 617 0.03125 L 620 0.03125 L 620 61 L 617 61 Z M 617 0.03125 " clip-rule="nonzero"/></clipPath><clipPath id="6c904e7290"><path d="M 157 0.03125 L 179 0.03125 L 179 66 L 157 66 Z M 157 0.03125 " clip-rule="nonzero"/></clipPath></defs><g clip-path="url(#326b62e356)"><path fill="#ffffff" d="M 0 0.03125 L 824.878906 0.03125 L 824.878906 449.96875 L 0 449.96875 Z M 0 0.03125 " fill-opacity="1" fill-rule="nonzero"/><path fill="#1b0140" d="M 0 0.03125 L 824.878906 0.03125 L 824.878906 449.96875 L 0 449.96875 Z M 0 0.03125 " fill-opacity="1" fill-rule="nonzero"/></g><g clip-path="url(#b6643e95a8)"><path fill="#1b0140" d="M 812.605469 -0.0195312 L 812.605469 449.683594 L 12.457031 449.683594 L 12.457031 -0.0195312 " fill-opacity="1" fill-rule="nonzero"/></g><path fill="#1b0140" d="M 166.484375 28.898438 L 166.484375 60.882812 C 164.230469 60.863281 161.085938 60.9375 159.121094 62.058594 C 157.277344 63.109375 157.925781 64.21875 157.484375 64.878906 C 157.289062 65.175781 156.003906 65.339844 155.679688 66.539062 C 153.445312 74.796875 157.023438 71.273438 150.484375 78.875 C 131.457031 80.25 109.808594 76.96875 91.097656 79 C 78.90625 80.324219 70.5 87.898438 69.429688 100.324219 C 65.167969 149.917969 72.699219 205.566406 69.464844 255.777344 L 59.464844 253.789062 L 64.457031 277.761719 L 53.457031 276.769531 C 53.238281 289.894531 60.621094 300.78125 70.464844 308.753906 L 70.464844 315.753906 C 68.136719 315.820312 65.785156 315.699219 63.457031 315.75 L 64.414062 332.089844 C 70.542969 333.820312 68.644531 339.132812 70.167969 344.539062 C 71.746094 350.144531 74.535156 354.421875 76.46875 359.730469 C 69.558594 359.949219 62.222656 364.023438 63.464844 371.722656 C 65.777344 385.980469 82.527344 394.292969 95.925781 394.757812 L 714.125 394.75 C 727.15625 393.402344 744.65625 386.195312 746.59375 371.722656 C 746.621094 371.5 747.566406 371.074219 747.429688 369.539062 C 747.113281 365.988281 743.914062 362.269531 741.59375 359.730469 C 741.179688 356.019531 744.109375 340.949219 742.339844 338.9375 C 741.941406 338.488281 740.65625 338.839844 740.59375 338.742188 C 739.578125 337.21875 740.410156 306.808594 740.59375 302.214844 C 740.667969 300.289062 739.5625 298.203125 742.59375 298.761719 C 743.332031 301.046875 742.941406 308.136719 746.589844 307.753906 L 745.59375 296.761719 C 749.746094 294.027344 766.183594 275.074219 769.585938 270.261719 C 770.714844 268.664062 775.824219 260.539062 775.558594 259.347656 C 764.222656 252.3125 750.710938 260.765625 741.589844 267.777344 L 739.589844 178.824219 C 744.933594 168.757812 752.488281 164.125 757.046875 156.789062 C 757.855469 155.488281 760.464844 150.761719 757.078125 150.804688 C 753.273438 150.847656 744.136719 153.230469 740.59375 154.835938 C 739.410156 137.277344 742.191406 117.695312 740.574219 100.378906 C 739.324219 86.964844 730.828125 80.753906 718.078125 78.882812 L 635.574219 78.875 C 634.457031 77.433594 631.867188 76.761719 631.015625 73.929688 C 628.292969 64.933594 633.152344 61.535156 619.570312 60.882812 L 619.570312 28.898438 " fill-opacity="1" fill-rule="nonzero"/><path fill="#1b0140" d="M 754.855469 244.539062 C 758.089844 247.855469 764.542969 242.765625 760.605469 238.28125 C 757.148438 234.34375 751.167969 240.769531 754.855469 244.539062 Z M 754.855469 244.539062 " fill-opacity="1" fill-rule="nonzero"/><path fill="#8d4e9c" d="M 150.484375 78.875 C 143.703125 86.753906 137.070312 94.816406 130.480469 102.851562 C 140.136719 102.894531 149.828125 102.832031 159.484375 102.859375 C 160.769531 109.878906 174.210938 109.867188 175.488281 102.859375 C 185.144531 102.832031 194.835938 102.890625 204.492188 102.851562 L 185.488281 78.875 C 295.160156 78.789062 404.878906 78.984375 514.550781 78.875 C 515.21875 78.875 515.882812 78.875 516.550781 78.875 C 524.871094 78.863281 533.238281 78.886719 541.554688 78.875 C 548.878906 78.863281 556.238281 78.898438 563.558594 78.875 C 565.226562 78.871094 566.894531 78.882812 568.5625 78.875 C 570.226562 78.863281 571.894531 78.882812 573.5625 78.875 C 582.546875 78.820312 591.582031 78.914062 600.566406 78.875 C 594.433594 86.851562 588.21875 95.03125 581.5625 102.859375 C 579.167969 105.675781 576.589844 109.5 574.5625 111.855469 C 566.703125 120.976562 554.714844 135.746094 546.554688 143.839844 C 546.363281 144.03125 544.859375 144.007812 544.039062 144.78125 C 542.847656 145.90625 542.3125 148.28125 540.882812 148.742188 C 539.058594 149.328125 536.296875 147.671875 534.058594 147.75 C 530.234375 147.886719 526.359375 150.261719 522.554688 147.839844 C 524.40625 146.773438 526.132812 146.597656 526.578125 144.359375 C 528.21875 136.195312 525.1875 128.023438 517.25 124.648438 C 512.910156 122.800781 501.9375 121.789062 499.058594 118.839844 C 494.832031 114.503906 498.828125 102.179688 487.800781 100.070312 C 478.035156 98.207031 461.84375 110.511719 471.542969 119.851562 C 471.675781 121.0625 472.304688 121.910156 472.542969 122.851562 C 463.335938 124.589844 458.773438 134.730469 463.542969 142.839844 C 463.234375 142.964844 460.128906 144.914062 459.867188 145.160156 C 454.484375 150.132812 452.097656 170.210938 451.539062 177.824219 C 451.449219 179.082031 451.542969 179.109375 451.539062 179.820312 C 451.53125 180.804688 451.453125 181.847656 451.539062 182.820312 C 448.519531 182.261719 449.605469 184.347656 449.542969 186.269531 C 449.417969 190.15625 449.25 194.074219 450.539062 197.8125 L 450.539062 198.8125 C 439.195312 198.8125 427.769531 199.328125 416.53125 197.8125 C 416.371094 184.355469 410.035156 180.851562 397.09375 182.882812 C 394.023438 183.367188 392.03125 185.429688 389.527344 186.816406 C 389.0625 187.078125 387.582031 186.75 386.011719 187.757812 C 382.972656 189.703125 379.492188 197.09375 377.859375 197.644531 L 364.523438 197.8125 C 364.125 184.695312 363.144531 170.742188 360.523438 157.832031 C 366.203125 154.40625 366.757812 150.773438 367.523438 144.839844 C 367.558594 144.574219 368.582031 143.824219 368.582031 142.414062 C 368.578125 137.859375 367.015625 136.480469 363.523438 134.84375 C 357.4375 131.992188 350.347656 133.339844 346.519531 126.847656 C 347.394531 122.472656 346.472656 114.152344 345.519531 109.859375 C 344.652344 105.953125 345.199219 104.542969 340.867188 102.011719 C 331.707031 96.660156 320.617188 101.78125 317.742188 111.582031 C 317.175781 113.515625 318.03125 116.175781 317.039062 117.875 C 316.027344 119.605469 305.824219 121.3125 302.640625 127.46875 C 299.457031 133.625 302.488281 141.847656 309.898438 141.835938 L 310.503906 143.816406 C 306.964844 144.175781 306.6875 147.816406 305.796875 150.617188 C 302.863281 159.847656 302.523438 171.234375 300.511719 180.816406 C 299.339844 180.820312 295.019531 182.921875 292.503906 181.8125 C 293.242188 186.546875 292.726562 193.414062 293.507812 197.808594 C 285.578125 198.359375 276.203125 199.117188 268.503906 200.808594 C 272.292969 193.726562 269.375 184.996094 270.503906 177.820312 C 270.628906 177.011719 274.167969 172.929688 272.496094 169.824219 C 268.1875 173.628906 266.425781 170.28125 262.949219 169.871094 C 246.417969 167.933594 241.648438 177.441406 246.777344 192.035156 C 247.296875 193.527344 249.449219 195.582031 249.5 195.808594 C 250.097656 198.238281 248.015625 200.214844 247.5 201.804688 C 230.222656 205.234375 180.339844 210.085938 170.65625 225.464844 C 166.449219 232.152344 169.621094 231.925781 170.488281 236.789062 C 170.535156 237.074219 169.832031 237.433594 170.488281 239.785156 C 172.894531 248.457031 178.5625 250.546875 186.277344 254.492188 C 189.5625 256.171875 196.730469 259.804688 199.492188 260.777344 C 198.105469 266.988281 198.011719 273.445312 197.492188 279.765625 C 197 285.71875 196.984375 291.796875 196.492188 297.757812 C 196.480469 297.929688 195.550781 298.878906 195.445312 300.171875 C 195.078125 304.675781 194.824219 309.25 194.492188 313.75 C 184.835938 313.726562 175.140625 313.765625 165.484375 313.75 C 163.113281 301.988281 159.335938 284.214844 154.003906 273.75 C 148.617188 263.167969 139.882812 255.777344 131.480469 247.78125 C 132.035156 244.644531 129.539062 241.515625 131.480469 238.789062 C 131.746094 238.753906 134.734375 237.980469 135.480469 237.789062 L 156.808594 239.636719 C 157.855469 239.28125 161.910156 232.582031 162.472656 231.269531 C 163.660156 228.507812 160.613281 230.808594 160.484375 230.789062 C 159.210938 230.605469 158.390625 230 157.484375 229.789062 C 157.179688 225.675781 163.171875 227.550781 165.476562 226.28125 C 166.765625 225.570312 171.957031 215.261719 171.492188 214.808594 L 166.488281 213.796875 C 165.347656 212.859375 163.042969 213.515625 163.472656 211.300781 C 163.683594 210.199219 167.035156 211.613281 164.507812 209.28125 L 158.480469 208.808594 L 157 204.808594 C 154.863281 206.507812 155.917969 209.167969 154.5625 211.371094 C 153.207031 213.574219 144.449219 220.574219 142.484375 222.792969 C 130.492188 210.269531 138.726562 183.070312 120.480469 177.816406 L 120.613281 172.9375 C 130.976562 176.226562 137.210938 163.152344 135.484375 154.828125 C 138.898438 155.105469 137.273438 154.117188 136.527344 152.289062 C 132.597656 142.671875 122.902344 135.640625 112.472656 140.328125 C 104.511719 143.90625 105.019531 152.542969 100.324219 158.175781 C 97.15625 161.972656 91.320312 164.875 87.96875 168.816406 C 80.394531 177.710938 80.628906 190.203125 88.476562 198.808594 C 87.785156 206.492188 87.640625 225.265625 90.914062 231.847656 C 92.300781 234.644531 96.398438 237.101562 96.492188 237.492188 C 96.957031 239.382812 96.714844 247.367188 96.476562 249.78125 C 95.679688 257.855469 93.828125 259.222656 95.476562 268.773438 C 96.054688 272.132812 96.132812 272.59375 97.476562 275.769531 C 99.445312 280.402344 101.90625 283.199219 105.480469 286.761719 C 105.902344 289.777344 102.707031 291.492188 100.476562 293.757812 C 100.382812 293.859375 99.222656 293.503906 98.441406 294.441406 C 96.140625 297.203125 95.632812 300.574219 94.476562 303.753906 C 94.394531 303.980469 93.613281 304.308594 93.476562 304.753906 C 92.851562 306.785156 92.71875 308.664062 92.472656 310.746094 L 94.476562 310.746094 C 93.511719 313.726562 92.316406 311.988281 92.480469 314.746094 L 111.480469 314.746094 C 97.84375 315.734375 84.285156 315.355469 70.472656 315.75 L 70.472656 308.75 C 75.996094 309.167969 85.996094 317.1875 88.476562 309.75 C 89.675781 306.160156 88.460938 306.492188 87.476562 302.753906 C 89.609375 300.828125 91.148438 301.789062 93.46875 302.753906 C 93.101562 298.355469 94.109375 293.773438 93.476562 289.761719 C 91.304688 275.960938 82.636719 262.277344 69.472656 256.777344 C 69.460938 256.445312 69.480469 256.113281 69.472656 255.777344 C 72.703125 205.5625 65.171875 149.917969 69.4375 100.324219 C 70.511719 87.898438 78.914062 80.320312 91.105469 79 C 109.816406 76.96875 131.46875 80.25 150.492188 78.875 Z M 150.484375 78.875 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 89.472656 372.722656 C 89.566406 377.984375 91.199219 378.359375 95.929688 378.761719 C 113.574219 380.269531 141.023438 379.671875 159.027344 378.761719 C 162.683594 378.578125 169.441406 378.097656 172.804688 377.496094 C 174.628906 377.167969 175.554688 376.191406 176.488281 374.722656 C 181.1875 375.542969 186.046875 375.757812 190.492188 377.71875 L 192.492188 378.71875 C 214.367188 384.769531 231.9375 387.222656 254.503906 386.714844 C 263.078125 386.523438 272.1875 385.726562 280.507812 385.714844 C 288.648438 385.707031 297.851562 386.703125 306.511719 386.714844 C 337.167969 386.753906 367.875 386.730469 398.527344 386.714844 C 398.863281 386.714844 399.195312 386.714844 399.527344 386.714844 C 400.863281 386.714844 402.195312 386.714844 403.53125 386.714844 C 403.863281 386.714844 404.195312 386.714844 404.53125 386.714844 L 545.554688 386.714844 C 563.589844 388.453125 581.726562 382.726562 599.566406 379.71875 C 600.867188 379.5 602.660156 380.097656 603.882812 379.746094 C 605.0625 379.40625 604.433594 377.839844 604.566406 377.71875 C 605.183594 377.148438 614.46875 375.40625 616.570312 374.722656 L 620.019531 377.773438 C 653.890625 375.71875 690.605469 380.328125 724.128906 377.757812 C 726.878906 377.546875 729.816406 376.867188 732.417969 376.007812 C 734.835938 375.210938 734.960938 376.003906 734.589844 372.726562 C 737.605469 372.566406 740.726562 371.710938 744.59375 371.726562 L 745.09375 372.707031 L 745.59375 371.726562 L 746.59375 371.726562 C 744.652344 386.199219 727.15625 393.410156 714.125 394.753906 L 95.925781 394.761719 C 82.527344 394.300781 65.777344 385.984375 63.46875 371.726562 C 71.300781 371.960938 79.210938 371.429688 87.054688 371.6875 C 88.363281 371.726562 89.34375 372.722656 89.472656 372.726562 Z M 89.472656 372.722656 " fill-opacity="1" fill-rule="nonzero"/><path fill="#8d4e9c" d="M 740.59375 154.835938 C 732.441406 158.523438 729.246094 163.601562 725.589844 170.828125 C 725.441406 171.125 724.175781 171.652344 723.535156 173.226562 C 722.59375 175.539062 720.679688 181.546875 720.589844 183.820312 C 719.199219 182.632812 714.097656 181.171875 713.585938 180.820312 C 710.894531 178.972656 710.761719 175.261719 709.585938 172.824219 C 713.054688 156.285156 710.078125 142.941406 690.582031 146.839844 L 666.582031 116.304688 C 665.566406 115.066406 663.6875 114.988281 663.578125 114.855469 C 660.457031 111.070312 657.761719 106.746094 654.578125 102.859375 C 648.179688 95.050781 641.640625 86.691406 635.574219 78.875 L 718.078125 78.882812 C 730.832031 80.753906 739.324219 86.964844 740.574219 100.378906 C 742.191406 117.695312 739.410156 137.277344 740.59375 154.835938 Z M 740.59375 154.835938 " fill-opacity="1" fill-rule="nonzero"/><g clip-path="url(#4901f7966f)"><path fill="#884c99" d="M 619.570312 -5.433594 L 619.570312 60.882812 C 618.90625 60.816406 618.230469 60.863281 617.570312 60.882812 L 617.570312 56.738281 C 617.570312 53.972656 617.570312 51.210938 617.570312 48.449219 " fill-opacity="1" fill-rule="nonzero"/></g><g clip-path="url(#6c904e7290)"><path fill="#884c99" d="M 168.484375 2.648438 L 168.484375 58.6875 C 173.234375 58.859375 176.734375 56.65625 178.488281 65.804688 C 171.519531 65.152344 164.253906 67.496094 157.484375 64.027344 C 157.921875 62.84375 157.277344 60.875 159.121094 59 C 161.085938 57.003906 164.230469 56.871094 166.484375 56.910156 L 166.484375 -0.0195312 " fill-opacity="1" fill-rule="nonzero"/></g><path fill="#fcf7df" d="M 114.476562 314.753906 C 116.488281 315.886719 116.417969 315.679688 116.265625 317.910156 C 115.9375 322.632812 113.566406 327.671875 114.480469 332.75 L 110.351562 333.328125 C 109.316406 338.210938 109.265625 342.632812 107.75 347.519531 C 106.359375 352 103.199219 355.230469 102.46875 359.734375 C 97.84375 360.308594 94.59375 363.96875 88.992188 363.777344 C 84.527344 363.625 79.90625 359.625 76.464844 359.734375 C 74.53125 354.425781 71.746094 350.148438 70.164062 344.542969 C 68.636719 339.136719 70.542969 333.828125 64.410156 332.09375 L 63.453125 315.753906 C 65.78125 315.703125 68.132812 315.824219 70.460938 315.757812 C 84.269531 315.363281 97.832031 315.742188 111.46875 314.757812 C 111.800781 314.730469 112.136719 314.785156 112.46875 314.757812 C 113.125 314.703125 113.8125 314.820312 114.46875 314.757812 Z M 114.476562 314.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fcf7df" d="M 617.570312 60.882812 C 618.230469 60.875 618.90625 60.847656 619.570312 60.882812 C 633.148438 61.539062 628.292969 64.9375 631.015625 73.929688 C 631.867188 76.757812 634.457031 77.433594 635.574219 78.875 C 641.640625 86.691406 648.179688 95.050781 654.578125 102.859375 L 581.5625 102.859375 C 588.21875 95.03125 594.433594 86.851562 600.566406 78.875 C 601.160156 78.101562 601.742188 78.921875 603.566406 75.875 C 606.210938 71.464844 605.015625 72.710938 605.566406 67.878906 C 605.640625 67.234375 605.460938 66.488281 605.566406 65.878906 L 608.566406 61.882812 C 608.828125 61.765625 609.246094 61.980469 609.566406 61.882812 C 612.492188 60.964844 614.570312 60.929688 617.570312 60.882812 Z M 617.570312 60.882812 " fill-opacity="1" fill-rule="nonzero"/><path fill="#7d4399" d="M 178.488281 65.878906 C 180.261719 71.074219 178.652344 77.28125 185.488281 78.875 L 204.492188 102.851562 C 194.835938 102.894531 185.144531 102.832031 175.488281 102.859375 C 170.164062 102.878906 164.804688 102.878906 159.484375 102.859375 C 149.828125 102.832031 140.136719 102.890625 130.480469 102.851562 C 137.070312 94.816406 143.703125 86.753906 150.484375 78.875 C 157.023438 71.273438 153.445312 74.796875 155.679688 66.539062 C 156.003906 65.339844 157.289062 65.175781 157.484375 64.878906 C 164.253906 66.828125 171.519531 65.511719 178.488281 65.878906 Z M 178.488281 65.878906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#9e6ebb" d="M 69.46875 255.78125 C 69.476562 256.117188 69.457031 256.449219 69.46875 256.78125 C 69.46875 256.863281 67.921875 257.070312 68.902344 257.808594 C 74.023438 260.332031 83.21875 268.46875 86.101562 273.132812 C 88.289062 276.671875 89.621094 282.734375 90.984375 286.808594 C 91.527344 288.429688 90.808594 290.34375 93.472656 289.765625 C 94.101562 293.777344 93.097656 298.359375 93.464844 302.757812 C 91.144531 301.792969 89.605469 300.832031 87.472656 302.757812 C 87.210938 302.992188 86.371094 302.601562 86.621094 304.019531 L 88.472656 309.753906 C 85.992188 317.191406 75.988281 309.171875 70.46875 308.757812 C 60.625 300.78125 53.242188 289.894531 53.460938 276.769531 L 64.460938 277.761719 L 59.46875 253.789062 L 69.46875 255.777344 Z M 83.152344 297.117188 C 83.769531 297.664062 84.078125 300.21875 85.449219 299.273438 C 83.539062 296.640625 82.46875 292.023438 78.472656 291.773438 C 78.28125 294.789062 81.460938 295.613281 83.152344 297.121094 Z M 85.972656 300.761719 L 85.972656 301.757812 C 86.621094 301.425781 86.621094 301.09375 85.972656 300.761719 Z M 85.972656 300.761719 " fill-opacity="1" fill-rule="nonzero"/><path fill="#88c0af" d="M 745.59375 296.761719 C 745.460938 296.847656 743.582031 297.335938 742.59375 297.761719 C 740.359375 298.71875 737.054688 299.4375 734.589844 299.761719 C 737.621094 288.898438 737.761719 282.023438 737.59375 270.773438 C 739.671875 270.546875 740.492188 268.621094 741.59375 267.777344 C 750.714844 260.769531 764.226562 252.3125 775.5625 259.347656 C 775.824219 260.539062 770.71875 268.667969 769.589844 270.261719 C 766.1875 275.070312 749.75 294.027344 745.597656 296.761719 Z M 745.59375 296.761719 " fill-opacity="1" fill-rule="nonzero"/><path fill="#7bb9a7" d="M 740.59375 154.835938 C 744.140625 153.230469 753.273438 150.847656 757.078125 150.804688 C 760.46875 150.761719 757.855469 155.488281 757.046875 156.789062 C 752.492188 164.128906 744.933594 168.757812 739.589844 178.824219 C 736.429688 184.769531 734.386719 191.203125 730.585938 196.8125 C 728.679688 193.09375 723.183594 190.570312 721.585938 187.816406 L 725.585938 170.828125 C 729.242188 163.601562 732.4375 158.523438 740.589844 154.835938 Z M 740.59375 154.835938 " fill-opacity="1" fill-rule="nonzero"/><path fill="#c03666" d="M 102.472656 359.730469 C 109.863281 358.808594 118.886719 360.40625 126.476562 359.730469 C 126.1875 361.539062 126.683594 363.824219 126.476562 365.726562 L 102.464844 366.226562 C 102.464844 367.425781 124.175781 366.34375 126.476562 366.726562 C 129.5 367.230469 132.117188 369.972656 134.480469 371.722656 C 123.609375 371.703125 111.785156 372.847656 100.472656 372.722656 C 97.480469 372.691406 94.460938 372.796875 91.472656 372.722656 C 90.804688 372.707031 90.136719 372.742188 89.472656 372.722656 C 89.339844 372.722656 88.363281 371.722656 87.054688 371.683594 C 79.214844 371.425781 71.300781 371.957031 63.464844 371.722656 C 62.222656 364.023438 69.558594 359.949219 76.46875 359.730469 C 79.914062 359.621094 84.539062 363.621094 88.996094 363.773438 C 94.597656 363.964844 97.84375 360.304688 102.472656 359.730469 Z M 100.472656 366.726562 L 75.46875 366.726562 L 75.46875 367.726562 L 100.472656 367.726562 Z M 100.472656 366.726562 " fill-opacity="1" fill-rule="nonzero"/><path fill="#8d4e9c" d="M 741.59375 267.777344 C 740.492188 268.621094 739.671875 270.546875 737.59375 270.773438 C 737.5 264.832031 737.375 251.875 736.164062 246.714844 C 735.429688 243.59375 733.21875 240.460938 729.589844 240.789062 C 732.085938 228.472656 736.429688 208.1875 730.589844 196.8125 C 734.390625 191.203125 736.433594 184.769531 739.59375 178.824219 Z M 741.59375 267.777344 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fbf6de" d="M 720.589844 338.742188 C 723.242188 338.65625 725.929688 338.742188 728.589844 338.742188 L 730.589844 338.742188 C 731.925781 338.742188 733.257812 338.742188 734.589844 338.742188 L 740.59375 338.742188 C 740.65625 338.835938 741.945312 338.488281 742.339844 338.9375 C 744.105469 340.949219 741.179688 356.019531 741.59375 359.730469 C 736.910156 367.539062 727.703125 360.988281 721.597656 364.726562 C 721.457031 363.085938 721.761719 361.363281 721.589844 359.730469 C 721.289062 356.867188 720.6875 350.613281 719.417969 348.367188 C 718.433594 346.628906 716.796875 346.960938 716.589844 346.738281 C 716.289062 346.414062 716.449219 343.757812 713.585938 343.738281 C 713.789062 342.113281 713.4375 340.367188 713.582031 338.738281 C 715.910156 338.683594 718.261719 338.816406 720.589844 338.742188 Z M 720.589844 338.742188 " fill-opacity="1" fill-rule="nonzero"/><path fill="#c03666" d="M 721.589844 359.730469 C 721.761719 361.363281 721.457031 363.085938 721.597656 364.726562 C 727.699219 360.988281 736.910156 367.539062 741.59375 359.730469 C 743.914062 362.269531 747.113281 365.988281 747.429688 369.539062 C 747.570312 371.070312 746.628906 371.5 746.59375 371.722656 L 745.59375 371.722656 C 745.261719 371.722656 744.925781 371.722656 744.59375 371.722656 C 740.726562 371.707031 737.605469 372.5625 734.589844 372.722656 C 730.964844 372.917969 727.226562 372.703125 723.589844 372.722656 C 720.925781 372.738281 718.25 372.75 715.589844 372.722656 C 711.925781 372.691406 708.628906 371.753906 705.585938 371.722656 L 705.585938 369.726562 L 711.585938 359.730469 Z M 721.589844 359.730469 " fill-opacity="1" fill-rule="nonzero"/><path fill="#07032a" d="M 742.59375 297.761719 L 742.59375 298.761719 C 739.5625 298.203125 740.667969 300.289062 740.59375 302.214844 C 740.410156 306.808594 739.578125 337.21875 740.59375 338.742188 L 734.589844 338.742188 C 734.09375 332.636719 734.074219 326.359375 733.582031 320.257812 C 733.277344 316.492188 731.589844 310.105469 731.589844 306.757812 C 731.589844 304.335938 733.996094 301.902344 734.589844 299.761719 C 737.054688 299.4375 740.359375 298.71875 742.59375 297.761719 Z M 742.59375 297.761719 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fbf6de" d="M 754.855469 244.539062 C 751.171875 240.769531 757.152344 234.34375 760.605469 238.28125 C 764.539062 242.765625 758.089844 247.855469 754.855469 244.539062 Z M 754.855469 244.539062 " fill-opacity="1" fill-rule="nonzero"/><path fill="#e3d8d1" d="M 745.59375 296.761719 L 746.589844 307.753906 C 742.945312 308.136719 743.332031 301.046875 742.59375 298.761719 L 742.59375 297.761719 C 743.582031 297.335938 745.460938 296.847656 745.59375 296.761719 Z M 745.59375 296.761719 " fill-opacity="1" fill-rule="nonzero"/><path fill="#904f9c" d="M 546.554688 143.839844 C 549.460938 143.476562 549.257812 147.316406 551.566406 148.332031 C 551.960938 148.507812 559.628906 149.835938 560.058594 149.835938 L 673.078125 149.835938 C 674.683594 149.835938 679.449219 146.964844 681.582031 149.835938 C 676.996094 153.109375 680.019531 160.425781 685.582031 160.832031 C 687.015625 169.632812 687.132812 184.078125 699.582031 179.824219 C 699.511719 181.808594 699.703125 183.835938 699.585938 185.820312 C 697.433594 185.566406 696.167969 186.707031 694.582031 187.816406 C 680.089844 198.015625 686.039062 224.171875 660.578125 215.804688 C 656.710938 214.535156 648.96875 209.796875 645.636719 207.246094 C 640.382812 203.214844 639.253906 198.019531 631.574219 197.8125 L 616.078125 185.808594 C 615.59375 189.628906 621.699219 192.445312 623.625 195.304688 C 624.316406 196.335938 624.292969 197.355469 624.570312 197.8125 C 624.851562 198.269531 624.378906 199.339844 625.558594 200.28125 C 627.8125 202.085938 633.523438 201.046875 631.15625 206.894531 L 627.570312 207.820312 C 626.21875 209.082031 636.511719 211.800781 637.5 212.378906 C 641.628906 214.800781 652.664062 225.007812 656.578125 228.796875 C 656.851562 229.0625 657.277344 231.136719 659.082031 232.785156 C 665.363281 238.515625 676.230469 237.71875 683.578125 234.800781 L 682.582031 252.789062 C 674.027344 253.449219 662.0625 248.460938 657.578125 258.785156 C 653.542969 258.644531 638.289062 258.070312 636.003906 259.714844 C 634.914062 260.496094 632.90625 264.300781 632.054688 265.765625 C 623.445312 280.554688 617.46875 298.863281 608.566406 313.757812 L 599.566406 313.757812 C 599.539062 308.601562 598.863281 303.542969 598.566406 298.765625 C 598.234375 293.40625 597.984375 288.132812 597.566406 282.773438 C 597.078125 276.476562 596.460938 270.117188 596.566406 263.78125 C 599.144531 263.066406 602.796875 261.675781 605.566406 260.785156 C 615.714844 257.519531 632.898438 252.605469 638.574219 242.792969 C 640.855469 238.847656 639.625 238.832031 639.574219 235.796875 C 639.507812 231.804688 640.339844 228.394531 638.035156 224.839844 C 630.445312 213.128906 584.6875 205.199219 570.5625 203.8125 C 567.828125 197.425781 559.804688 179.519531 556.390625 174.496094 C 547.382812 161.222656 528.761719 164.3125 526.5625 179.820312 L 528.054688 177.820312 L 528.554688 179.832031 C 527.742188 187.941406 530.941406 194.863281 534.554688 201.820312 C 528.566406 201.300781 522.589844 200.273438 516.550781 199.820312 C 517.601562 198.042969 518.382812 196.484375 518.578125 194.347656 C 519.4375 184.710938 518.601562 159.730469 515.550781 150.84375 C 517.71875 150.257812 520.644531 148.945312 522.550781 147.847656 C 526.351562 150.269531 530.226562 147.898438 534.054688 147.757812 C 536.292969 147.679688 539.054688 149.335938 540.878906 148.75 C 542.3125 148.289062 542.84375 145.914062 544.035156 144.789062 C 544.855469 144.015625 546.359375 144.039062 546.550781 143.847656 Z M 546.554688 143.839844 " fill-opacity="1" fill-rule="nonzero"/><path fill="#1b0141" d="M 225.558594 37.332031 C 228.324219 39.257812 224.628906 55.964844 227.402344 59.480469 C 229.675781 62.371094 235.453125 59.785156 237.566406 61.316406 C 239.007812 62.359375 237.875 66.703125 241.195312 67.683594 C 243.617188 68.394531 246.503906 67.460938 248.964844 67.917969 C 250.941406 68.277344 251.957031 69.960938 253.449219 70.429688 C 259.496094 72.304688 264.941406 68.011719 271 67.816406 C 292.742188 67.105469 315.050781 67.804688 337.058594 67.839844 C 347.976562 67.859375 349.023438 66.089844 358.105469 64.96875 C 362.335938 64.449219 373.003906 66.679688 374.320312 62.1875 C 374.835938 60.429688 374.851562 55.328125 374.324219 53.585938 " fill-opacity="1" fill-rule="nonzero"/><path fill="#1b0140" d="M 605.695312 56.257812 C 606.722656 59.207031 611.320312 56.164062 610.570312 59.886719 C 609.433594 60.207031 609.464844 60.894531 609.566406 61.886719 C 609.246094 61.984375 608.828125 61.769531 608.566406 61.886719 C 606.53125 62.808594 605.960938 63.734375 605.566406 65.882812 C 605.460938 66.492188 605.640625 67.238281 605.566406 67.882812 L 603.566406 75.878906 C 601.742188 78.925781 601.160156 78.105469 600.566406 78.878906 L 599.675781 74.46875 C 598.980469 73.519531 578.519531 73.402344 576.261719 74.074219 C 574.132812 74.714844 573.375 76.839844 573.5625 78.878906 C 571.894531 78.886719 570.226562 78.871094 568.5625 78.878906 L 568.046875 75.863281 C 565.867188 76.089844 562.945312 76.269531 563.558594 78.878906 C 556.238281 78.902344 548.878906 78.871094 541.554688 78.878906 C 541.457031 71.597656 537.484375 77.121094 534.128906 76.878906 C 529.210938 76.523438 517.886719 68.835938 516.550781 78.878906 C 515.882812 78.878906 515.21875 78.878906 514.550781 78.878906 C 514.699219 76.648438 514.59375 75.355469 512.050781 74.875 C 505.230469 73.589844 495.332031 75.136719 488.546875 73.878906 L 488.546875 45.394531 " fill-opacity="1" fill-rule="nonzero"/><path fill="#1b0140" d="M 598.570312 68.875 C 602.359375 69.601562 604.082031 62.503906 601.050781 61.886719 C 598.035156 61.273438 598.390625 67.066406 598.570312 68.875 Z M 598.570312 68.875 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fbf6de" d="M 450.539062 198.8125 L 453.539062 198.8125 L 453.539062 219.800781 L 506.550781 219.800781 C 505.894531 213.074219 506.242188 210.730469 511.550781 206.808594 L 512.527344 206.308594 L 511.550781 205.808594 C 511.214844 205.828125 510.878906 205.78125 510.550781 205.808594 L 513.550781 199.8125 C 514.542969 199.867188 515.558594 199.738281 516.550781 199.8125 C 522.589844 200.265625 528.566406 201.292969 534.554688 201.8125 C 537.867188 202.097656 541.347656 201.214844 544.617188 202.242188 L 545.554688 207.808594 C 535.625 209.472656 531.398438 215.746094 528.554688 224.796875 L 494.550781 224.796875 C 496.957031 231.308594 498.519531 239.6875 501.546875 245.789062 C 495.316406 243.667969 495.351562 253.121094 498.207031 254.867188 C 503.09375 257.851562 520.6875 257.511719 527.007812 259.742188 C 533.242188 259.355469 536.695312 249.152344 536.554688 243.789062 C 537.4375 243.746094 539.152344 241.296875 539.546875 241.789062 C 539.097656 246.058594 542.152344 251.023438 542.554688 254.785156 C 542.878906 257.804688 542.320312 261.839844 541.554688 264.777344 C 506.398438 267.777344 470.867188 271.414062 435.535156 271.773438 C 432.480469 271.804688 429.410156 271.253906 426.542969 272.773438 L 426.527344 265.773438 C 443.835938 267.527344 438.140625 249.320312 435.238281 238.585938 C 432.339844 227.855469 429.957031 222.734375 418.011719 221.820312 C 416.816406 221.730469 411.992188 221.550781 411.527344 221.804688 C 411.328125 221.394531 410.960938 220.917969 410.527344 220.804688 L 409.527344 213.808594 C 414.957031 210.679688 416.597656 203.625 416.527344 197.816406 C 427.761719 199.332031 439.191406 198.816406 450.535156 198.816406 Z M 465.542969 245.789062 C 465.78125 250.195312 467.523438 255.972656 467.710938 260.601562 L 475.613281 261.34375 L 476.398438 260.128906 C 476.78125 255.210938 477.585938 250.777344 477.542969 245.789062 C 477.542969 245.605469 479.578125 244.40625 477.121094 242.71875 C 474.285156 240.769531 465.292969 241.226562 465.542969 245.789062 Z M 465.542969 245.789062 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fbf6de" d="M 293.507812 197.8125 C 293.746094 199.136719 297.1875 206.203125 296.507812 206.804688 L 292.011719 206.804688 C 292.011719 206.804688 291.523438 208.789062 291.523438 208.789062 C 296.613281 209.382812 296.28125 218.441406 300.210938 219.609375 L 350.527344 219.808594 C 350.425781 218.167969 350.6875 216.441406 350.523438 214.808594 C 353.117188 214.925781 364.511719 204.632812 356.523438 206.8125 L 357.472656 203.894531 L 355.53125 202.824219 C 356.820312 203.167969 357.746094 202.042969 358.527344 201.8125 C 363.015625 200.46875 363.242188 199.320312 364.527344 198.8125 C 365.148438 198.566406 377.101562 198.527344 377.917969 198.75 C 379.203125 202.164062 380.574219 207.324219 385.53125 204.808594 C 385.394531 212.621094 391.695312 215.457031 398.535156 215.804688 L 398.535156 219.800781 C 397.882812 219.867188 397.191406 219.714844 396.53125 219.800781 L 396.53125 221.800781 C 395.855469 221.546875 389.734375 221.628906 388.53125 221.800781 L 387.53125 222.800781 C 375 225.535156 366.058594 237.9375 360.109375 248.871094 C 352.230469 263.355469 368.386719 271.695312 378.515625 260.78125 L 378.535156 271.777344 L 359.527344 272.773438 C 331.585938 269.289062 303.03125 270.378906 275.089844 266.699219 C 273.113281 266.4375 271.296875 265.554688 269.507812 264.777344 C 269.871094 256.9375 273.164062 262.910156 275.777344 264.035156 C 279.457031 265.632812 289.300781 261.355469 293.515625 259.78125 C 297.457031 258.304688 305.171875 257.546875 303.515625 251.785156 C 304.539062 251.84375 305.925781 251.996094 306.839844 251.648438 C 309.121094 250.78125 314.714844 228.859375 315.519531 224.796875 L 283.011719 224.796875 C 281.441406 224.796875 281.199219 231.007812 278.511719 229.796875 C 274.601562 220.777344 273.917969 212.398438 261.507812 210.804688 C 261.5 209.214844 261.003906 208.347656 259.507812 207.808594 C 258.15625 202.554688 264.441406 201.707031 268.507812 200.8125 C 276.207031 199.121094 285.582031 198.363281 293.515625 197.8125 Z M 293.507812 197.8125 " fill-opacity="1" fill-rule="nonzero"/><path fill="#b64c94" d="M 574.5625 111.855469 C 575.0625 120.703125 579.242188 116.882812 584.066406 117.050781 C 606.785156 117.839844 630.3125 121.898438 653.058594 119.832031 C 657.042969 119.46875 661.773438 118.90625 663.578125 114.851562 C 663.6875 114.984375 665.566406 115.0625 666.582031 116.300781 L 690.582031 146.835938 C 688.882812 147.175781 682.652344 149.066406 681.582031 149.832031 C 679.449219 146.960938 674.683594 149.832031 673.078125 149.832031 L 560.058594 149.832031 C 559.628906 149.832031 551.960938 148.503906 551.566406 148.328125 C 549.257812 147.3125 549.460938 143.472656 546.554688 143.835938 C 554.714844 135.742188 566.703125 120.972656 574.5625 111.851562 Z M 574.5625 111.855469 " fill-opacity="1" fill-rule="nonzero"/><path fill="#07032a" d="M 244.5 209.804688 C 248.148438 209.597656 257.730469 210.324219 261.503906 210.804688 C 273.914062 212.398438 274.597656 220.777344 278.507812 229.796875 C 280.792969 235.078125 283.671875 240.027344 285.058594 245.738281 C 285.871094 246.984375 290.316406 249.554688 291.507812 249.785156 C 293.644531 252.855469 293.777344 256.128906 293.507812 259.78125 C 289.296875 261.359375 279.453125 265.632812 275.773438 264.035156 C 273.160156 262.910156 269.871094 256.9375 269.503906 264.777344 C 269.390625 267.242188 270.347656 269.382812 270.511719 271.78125 C 274.082031 269.46875 277.207031 271.480469 280.507812 271.773438 L 280.507812 274.773438 C 277.101562 274.316406 273.675781 274.566406 270.511719 272.773438 C 270.082031 274.878906 271.332031 276.90625 271.503906 278.769531 C 271.65625 280.410156 271.414062 282.128906 271.507812 283.773438 L 232.5 283.773438 C 231.78125 278.816406 231.09375 274.09375 231.355469 268.914062 C 230.375 267.382812 213.640625 264.695312 210.492188 263.773438 C 207.273438 262.832031 202.109375 261.691406 199.492188 260.777344 C 196.726562 259.804688 189.5625 256.175781 186.277344 254.492188 C 178.5625 250.546875 172.898438 248.453125 170.488281 239.785156 C 186.203125 255.464844 209.191406 259.433594 230.007812 264.785156 C 232.492188 265.375 231.429688 261.425781 231.496094 259.777344 C 231.898438 249.871094 229.472656 223.507812 233.648438 216.449219 C 235.9375 212.578125 240.105469 210.046875 244.5 209.800781 Z M 244.5 209.804688 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fbf6de" d="M 247.5 201.8125 C 247.179688 202.800781 247.847656 204.980469 247.5 205.808594 C 247.355469 206.152344 243.910156 207.609375 244.5 209.804688 C 240.105469 210.054688 235.941406 212.585938 233.648438 216.453125 C 229.472656 223.507812 231.898438 249.871094 231.496094 259.78125 C 210.4375 256.140625 187.160156 250.800781 170.488281 236.792969 C 169.621094 231.929688 166.449219 232.15625 170.65625 225.46875 C 180.339844 210.089844 230.222656 205.238281 247.5 201.8125 Z M 247.5 201.8125 " fill-opacity="1" fill-rule="nonzero"/><path fill="#07032a" d="M 136.480469 289.765625 C 139.921875 293.246094 149.199219 295.863281 150.273438 299.464844 C 151.832031 304.699219 147.507812 314.988281 146.480469 320.75 C 145.457031 326.507812 144.328125 343.507812 141.304688 347.59375 C 140.972656 348.042969 139.550781 347.625 139.480469 347.734375 L 130.480469 347.734375 C 129.5 336.746094 128.691406 324.925781 129.480469 313.753906 C 129.617188 311.789062 132.230469 305.625 131.046875 303.757812 C 128.328125 301.632812 124.292969 300.480469 121.476562 298.761719 C 115.980469 295.398438 110.03125 291.3125 105.472656 286.765625 C 101.902344 283.203125 99.441406 280.40625 97.472656 275.773438 C 111.382812 277.738281 123.808594 284.152344 136.480469 289.765625 Z M 136.480469 289.765625 " fill-opacity="1" fill-rule="nonzero"/><path fill="#07032a" d="M 131.480469 247.785156 C 139.882812 255.78125 148.617188 263.171875 154.003906 273.753906 C 159.335938 284.21875 163.113281 301.992188 165.484375 313.753906 C 167.226562 322.394531 168.316406 331 169.488281 339.738281 C 166.457031 339.824219 163.210938 342.605469 160.484375 342.738281 C 158.636719 342.832031 157.804688 342.609375 156.585938 341.152344 C 155.707031 340.113281 148.5625 322.144531 148.484375 320.75 C 148.125 314.398438 154.363281 306.019531 152.035156 298.707031 C 150.359375 293.445312 140.660156 291.617188 136.480469 289.765625 C 132.769531 286.011719 128.664062 283.96875 123.160156 281.585938 C 113.929688 277.601562 101.578125 276.496094 95.472656 268.777344 C 93.824219 259.226562 95.675781 257.859375 96.472656 249.785156 Z M 131.480469 247.785156 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fbf6de" d="M 108.476562 177.824219 C 112.097656 184.890625 113.894531 194.453125 117.601562 201.1875 C 118.519531 202.851562 119.714844 205.84375 121.972656 205.855469 C 127.519531 205.882812 122.300781 196.632812 121.769531 194.023438 C 120.726562 188.917969 120.609375 183.867188 119.472656 178.828125 L 120.472656 177.828125 C 138.71875 183.082031 130.484375 210.28125 142.476562 222.804688 C 142.410156 222.878906 143.296875 223.972656 142.882812 224.8125 C 141.15625 228.292969 133.828125 226.332031 130.476562 226.800781 L 130.476562 211.808594 L 128.476562 211.808594 L 128.476562 226.800781 L 112.972656 226.800781 C 108.96875 226.800781 109.222656 235.089844 109.480469 237.796875 C 114.492188 236.628906 122.90625 236.046875 128.042969 236.714844 C 130.226562 236.996094 128.714844 239.125 131.476562 238.796875 C 129.535156 241.523438 132.03125 244.652344 131.476562 247.792969 L 96.46875 249.789062 C 96.707031 247.375 96.953125 239.390625 96.484375 237.5 C 96.390625 237.109375 92.292969 234.652344 90.90625 231.859375 C 87.632812 225.269531 87.777344 206.496094 88.46875 198.816406 C 89.539062 186.925781 94.9375 177.175781 108.472656 177.828125 Z M 105.6875 222.605469 C 104.5 220.597656 106.957031 215.1875 104.488281 213.8125 C 103.410156 216.808594 103.023438 219.25 104.511719 222.21875 L 101.472656 224.789062 L 108.476562 224.789062 C 108.503906 223.300781 106.078125 223.261719 105.6875 222.605469 Z M 99.972656 224.800781 L 99.972656 225.796875 C 100.625 225.464844 100.625 225.132812 99.972656 224.800781 Z M 99.972656 224.800781 " fill-opacity="1" fill-rule="nonzero"/><path fill="#7d4399" d="M 338.519531 180.820312 C 331.441406 180.535156 323.613281 180.621094 316.515625 180.820312 C 316.265625 182.300781 316.882812 181.753906 317.992188 181.832031 C 324.566406 182.296875 332.328125 181.925781 339.035156 181.839844 C 340.726562 181.820312 343.480469 182.484375 344.523438 180.824219 C 347.597656 181.808594 347.179688 193.015625 347.523438 195.816406 C 348.019531 199.824219 349.09375 203.535156 349.523438 206.8125 C 349.648438 207.769531 349.382812 208.867188 349.523438 209.8125 C 349.574219 210.136719 349.476562 210.480469 349.523438 210.808594 C 349.734375 212.34375 350.441406 213.960938 350.523438 214.808594 C 350.6875 216.441406 350.425781 218.167969 350.527344 219.808594 L 300.210938 219.609375 C 296.28125 218.441406 296.613281 209.382812 291.523438 208.789062 L 292.011719 206.808594 L 296.507812 206.808594 C 297.1875 206.207031 293.746094 199.140625 293.507812 197.816406 C 292.726562 193.421875 293.242188 186.550781 292.503906 181.820312 C 295.019531 182.929688 299.339844 180.828125 300.511719 180.824219 C 305.773438 180.800781 311.15625 180.976562 316.515625 180.824219 C 317.503906 170.339844 319.464844 159.996094 321.992188 149.78125 C 322.242188 148.78125 323.460938 148.0625 323.515625 147.84375 C 330.40625 155.664062 338.863281 151.683594 339.519531 141.84375 C 340.101562 147.332031 339.519531 148.828125 339.519531 153.339844 L 339.519531 171.332031 C 339.519531 173.207031 337.464844 177.851562 338.519531 180.824219 Z M 320.152344 194.972656 C 316.292969 195.675781 315.847656 205.058594 322.878906 202.6875 C 326.476562 201.476562 324.300781 194.214844 320.152344 194.972656 Z M 320.152344 194.972656 " fill-opacity="1" fill-rule="nonzero"/><path fill="#07032a" d="M 345.519531 109.859375 C 342.152344 110.59375 338.65625 112.710938 336.015625 114.855469 C 334.371094 116.191406 333.617188 118.640625 333.417969 118.769531 C 333.113281 118.964844 328.824219 116.160156 326.9375 119.859375 C 326.066406 121.574219 328.484375 122.894531 328.574219 125.292969 C 328.765625 130.5 324.960938 142.113281 323.515625 147.839844 C 323.460938 148.058594 322.242188 148.773438 321.992188 149.777344 C 319.464844 159.996094 317.503906 170.335938 316.515625 180.820312 C 311.15625 180.972656 305.773438 180.796875 300.511719 180.820312 C 302.523438 171.238281 302.867188 159.851562 305.796875 150.621094 C 306.683594 147.820312 306.964844 144.183594 310.503906 143.820312 L 309.898438 141.839844 C 302.484375 141.855469 299.507812 133.546875 302.640625 127.472656 C 305.773438 121.402344 316.027344 119.609375 317.039062 117.878906 C 318.03125 116.179688 317.175781 113.519531 317.742188 111.585938 C 320.617188 101.785156 331.707031 96.664062 340.867188 102.015625 C 345.199219 104.542969 344.652344 105.953125 345.519531 109.863281 Z M 345.519531 109.859375 " fill-opacity="1" fill-rule="nonzero"/><path fill="#07032a" d="M 363.523438 134.84375 C 364.617188 139.617188 358.058594 142.347656 356.992188 144.867188 C 356.472656 146.101562 357.285156 148.363281 357.519531 149.835938 C 358.035156 153.035156 360.269531 156.574219 360.523438 157.832031 C 363.144531 170.742188 364.125 184.695312 364.523438 197.8125 L 364.523438 198.8125 C 363.238281 199.320312 363.011719 200.46875 358.523438 201.8125 C 352.933594 202.359375 353.707031 194.351562 347.519531 195.8125 C 347.171875 193.011719 347.59375 181.804688 344.519531 180.820312 C 342.527344 180.765625 340.511719 180.90625 338.519531 180.820312 C 337.464844 177.847656 339.519531 173.203125 339.519531 171.328125 L 339.519531 153.335938 C 339.519531 148.824219 340.101562 147.324219 339.519531 141.839844 C 339.300781 139.8125 337.984375 134.070312 338.667969 132.992188 C 341.601562 132.296875 345.894531 129.972656 346.519531 126.847656 C 350.347656 133.339844 357.4375 131.992188 363.523438 134.84375 Z M 363.523438 134.84375 " fill-opacity="1" fill-rule="nonzero"/><path fill="#e54976" d="M 608.566406 102.859375 C 611.542969 110.644531 625.042969 111.648438 627.570312 102.859375 L 654.578125 102.859375 C 657.761719 106.746094 660.457031 111.070312 663.578125 114.855469 C 661.773438 118.90625 657.042969 119.472656 653.058594 119.835938 C 630.3125 121.898438 606.785156 117.84375 584.066406 117.054688 C 579.242188 116.886719 575.066406 120.707031 574.5625 111.859375 C 576.589844 109.503906 579.167969 105.679688 581.5625 102.867188 L 608.566406 102.867188 Z M 608.566406 102.859375 " fill-opacity="1" fill-rule="nonzero"/><path fill="#07032a" d="M 88.472656 198.8125 C 80.625 190.207031 80.390625 177.71875 87.964844 168.820312 C 91.316406 164.878906 97.152344 161.976562 100.320312 158.179688 C 105.015625 152.546875 104.507812 143.910156 112.46875 140.332031 C 122.898438 135.644531 132.589844 142.675781 136.523438 152.292969 C 137.269531 154.121094 138.894531 155.109375 135.480469 154.832031 C 135.332031 154.097656 132.625 149.90625 131.984375 149.90625 C 126.273438 153.167969 126.136719 158.742188 118.472656 156.824219 C 118.324219 162.324219 119.65625 168.964844 115.5 173.347656 C 113.585938 175.367188 110.199219 174.867188 110.476562 177.824219 C 109.917969 177.707031 109.128906 177.855469 108.476562 177.824219 C 94.945312 177.171875 89.542969 186.921875 88.472656 198.8125 Z M 88.472656 198.8125 " fill-opacity="1" fill-rule="nonzero"/><path fill="#07032a" d="M 522.550781 147.839844 C 520.644531 148.9375 517.71875 150.25 515.550781 150.835938 C 512.449219 141.804688 500.53125 140.734375 492.546875 138.84375 C 492.578125 136.921875 491.113281 133.144531 491.550781 129.34375 C 491.90625 126.246094 495.253906 121.402344 494.121094 119.796875 L 472.058594 114.839844 C 471.203125 114.832031 471.4375 118.886719 471.546875 119.851562 C 461.847656 110.511719 478.039062 98.207031 487.804688 100.070312 C 498.832031 102.179688 494.835938 114.507812 499.0625 118.839844 C 501.941406 121.789062 512.914062 122.804688 517.253906 124.648438 C 525.191406 128.023438 528.21875 136.195312 526.582031 144.359375 C 526.132812 146.597656 524.410156 146.773438 522.558594 147.839844 Z M 522.550781 147.839844 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 194.492188 313.753906 C 193.535156 326.671875 193.320312 339.769531 192.492188 352.734375 C 192.375 354.558594 191.6875 357.921875 191.492188 360.730469 L 177.488281 360.730469 C 175.652344 357.183594 171.714844 350.613281 170.488281 347.734375 C 169.636719 345.746094 169.78125 341.9375 169.488281 339.738281 C 168.316406 331 167.226562 322.394531 165.484375 313.753906 C 175.140625 313.769531 184.835938 313.734375 194.492188 313.753906 Z M 194.492188 313.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#e54976" d="M 477.542969 139.84375 C 477.320312 142.464844 477.667969 145.199219 477.542969 147.839844 C 476.976562 159.796875 476.476562 171.835938 476.542969 183.820312 C 472.882812 183.832031 469.199219 183.777344 465.542969 183.820312 L 465.03125 157.828125 C 462.710938 157.164062 463.597656 159.972656 463.542969 161.324219 C 463.242188 168.796875 463.757812 176.351562 463.542969 183.820312 C 460.214844 183.878906 456.855469 183.777344 453.535156 183.816406 C 453.5 185.144531 453.570312 186.484375 453.539062 187.816406 L 451.539062 187.824219 C 451.410156 186.175781 451.6875 184.464844 451.539062 182.820312 C 451.453125 181.847656 451.53125 180.804688 451.539062 179.820312 L 452.535156 178.332031 L 451.539062 177.824219 C 452.097656 170.210938 454.480469 150.132812 459.867188 145.160156 C 460.128906 144.914062 463.238281 142.96875 463.542969 142.839844 C 467.074219 141.378906 473.589844 140.457031 477.542969 139.84375 Z M 477.542969 139.84375 " fill-opacity="1" fill-rule="nonzero"/><path fill="#07032a" d="M 416.53125 197.8125 C 416.601562 203.621094 414.960938 210.675781 409.53125 213.804688 C 406.132812 215.757812 402.371094 216 398.527344 215.804688 C 391.691406 215.457031 385.390625 212.621094 385.527344 204.808594 C 385.527344 204.675781 386.515625 203.679688 386.570312 202.394531 C 386.828125 196.390625 386.082031 192.332031 389.527344 186.816406 C 392.03125 185.4375 394.023438 183.367188 397.09375 182.882812 C 410.039062 180.847656 416.371094 184.355469 416.53125 197.8125 Z M 416.53125 197.8125 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f5b499" d="M 142.480469 222.800781 C 144.445312 220.585938 153.25 213.503906 154.558594 211.378906 C 155.867188 209.257812 154.859375 206.515625 156.996094 204.816406 L 158.476562 208.816406 L 164.503906 209.289062 C 167.03125 211.621094 163.683594 210.207031 163.46875 211.308594 C 163.039062 213.527344 165.339844 212.867188 166.484375 213.804688 C 167.585938 217.703125 161.957031 214.726562 160.621094 215.957031 C 160.113281 216.429688 160.867188 218.839844 158.273438 220.085938 C 153.988281 222.140625 151.144531 218.886719 148.515625 226.304688 C 151.023438 229.40625 154.390625 229.066406 157.488281 229.796875 C 158.394531 230.007812 159.214844 230.613281 160.488281 230.796875 C 160.453125 236.574219 149.078125 232.4375 147.542969 233.898438 L 147.488281 236.792969 C 141.96875 234.035156 140.285156 236.558594 135.488281 237.792969 C 134.742188 237.984375 131.753906 238.757812 131.488281 238.792969 C 128.734375 239.121094 130.242188 236.996094 128.054688 236.710938 C 122.917969 236.039062 114.503906 236.625 109.492188 237.792969 C 109.230469 235.085938 108.980469 226.796875 112.984375 226.796875 L 128.488281 226.796875 L 128.488281 211.804688 L 130.488281 211.804688 L 130.488281 226.796875 C 133.839844 226.332031 141.167969 228.289062 142.894531 224.808594 C 143.3125 223.964844 142.421875 222.875 142.488281 222.800781 Z M 142.480469 222.800781 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f5b499" d="M 345.519531 109.859375 C 346.472656 114.152344 347.394531 122.472656 346.519531 126.847656 C 345.894531 129.972656 341.597656 132.296875 338.667969 132.992188 C 337.984375 134.070312 339.304688 139.8125 339.519531 141.839844 C 338.863281 151.679688 330.40625 155.660156 323.515625 147.839844 C 324.964844 142.113281 328.769531 130.5 328.574219 125.292969 C 328.488281 122.886719 326.066406 121.574219 326.9375 119.859375 C 328.820312 116.160156 333.113281 118.964844 333.417969 118.769531 C 333.613281 118.640625 334.371094 116.191406 336.015625 114.855469 C 338.65625 112.714844 342.152344 110.597656 345.519531 109.859375 Z M 345.519531 109.859375 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f5b499" d="M 492.546875 138.84375 C 492.492188 142.09375 491.597656 144.773438 491.546875 147.839844 C 487.554688 151.414062 481.835938 149.90625 477.542969 147.839844 C 477.667969 145.199219 477.320312 142.464844 477.542969 139.84375 C 477.714844 137.867188 479.691406 134.554688 479.421875 133.445312 C 479.164062 132.367188 476.246094 131.246094 475.082031 129.8125 C 473.203125 127.515625 473.1875 125.40625 472.542969 122.851562 C 472.304688 121.910156 471.675781 121.0625 471.542969 119.851562 C 471.433594 118.890625 471.199219 114.832031 472.054688 114.839844 L 494.117188 119.796875 C 495.25 121.402344 491.90625 126.242188 491.546875 129.34375 C 491.109375 133.148438 492.574219 136.925781 492.542969 138.84375 Z M 492.546875 138.84375 " fill-opacity="1" fill-rule="nonzero"/><path fill="#07032a" d="M 249.5 195.8125 C 249.445312 195.589844 247.296875 193.53125 246.777344 192.039062 C 241.652344 177.445312 246.417969 167.9375 262.949219 169.875 C 266.425781 170.285156 268.1875 173.632812 272.496094 169.828125 C 274.167969 172.933594 270.632812 177.015625 270.503906 177.824219 C 267.152344 177.925781 266.179688 183.632812 264.230469 185.542969 C 263.292969 186.464844 261.195312 186.324219 260.699219 187.015625 C 258.738281 189.75 261.460938 194.410156 253.503906 195.8125 C 253.191406 195.867188 252.828125 195.800781 252.5 195.8125 C 251.503906 195.851562 250.5 195.789062 249.5 195.8125 Z M 249.5 195.8125 " fill-opacity="1" fill-rule="nonzero"/><path fill="#7d4399" d="M 121.476562 298.761719 C 117.730469 303.445312 113.171875 308.460938 112.476562 314.753906 C 112.148438 314.78125 111.808594 314.726562 111.476562 314.753906 L 92.476562 314.753906 C 92.3125 311.992188 93.5 313.734375 94.472656 310.753906 C 95.855469 306.507812 96.578125 301.320312 98.324219 297.148438 C 99.023438 295.480469 100.867188 295.8125 100.472656 293.761719 C 102.703125 291.5 105.898438 289.78125 105.472656 286.765625 C 110.03125 291.3125 115.980469 295.398438 121.476562 298.761719 Z M 121.476562 298.761719 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f5b499" d="M 135.480469 154.835938 C 137.207031 163.164062 130.972656 176.234375 120.609375 172.945312 L 120.476562 177.824219 L 119.476562 178.824219 C 117.613281 178.207031 116.613281 180.128906 114.042969 179.851562 C 112.460938 179.679688 111.265625 177.988281 110.476562 177.824219 C 110.199219 174.867188 113.585938 175.371094 115.5 173.347656 C 119.65625 168.964844 118.324219 162.328125 118.472656 156.824219 C 126.136719 158.742188 126.273438 153.167969 131.984375 149.90625 C 132.625 149.90625 135.332031 154.097656 135.480469 154.832031 Z M 135.480469 154.835938 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f5b499" d="M 270.503906 177.824219 C 269.375 185 272.292969 193.730469 268.503906 200.8125 C 264.4375 201.707031 258.152344 202.554688 259.503906 207.808594 C 256.683594 206.789062 250.765625 206.902344 247.5 205.808594 C 247.847656 204.980469 247.179688 202.800781 247.5 201.8125 C 248.011719 200.21875 250.097656 198.242188 249.5 195.8125 C 250.5 195.789062 251.507812 195.851562 252.5 195.8125 L 253.007812 196.796875 L 253.503906 195.8125 C 261.460938 194.410156 258.738281 189.75 260.699219 187.015625 C 261.195312 186.324219 263.292969 186.46875 264.230469 185.542969 C 266.179688 183.628906 267.144531 177.921875 270.503906 177.824219 Z M 270.503906 177.824219 " fill-opacity="1" fill-rule="nonzero"/><path fill="#75458c" d="M 231.496094 259.78125 C 231.429688 261.429688 232.492188 265.378906 230.007812 264.789062 C 209.191406 259.441406 186.203125 255.46875 170.488281 239.792969 C 169.832031 237.4375 170.535156 237.078125 170.488281 236.792969 C 187.160156 250.800781 210.4375 256.140625 231.496094 259.78125 Z M 231.496094 259.78125 " fill-opacity="1" fill-rule="nonzero"/><path fill="#4d3670" d="M 210.492188 263.777344 C 209.523438 270.371094 209.328125 277.175781 208.492188 283.769531 L 197.492188 279.769531 C 198.011719 273.449219 198.105469 266.992188 199.492188 260.78125 C 202.109375 261.695312 207.273438 262.835938 210.492188 263.777344 Z M 210.492188 263.777344 " fill-opacity="1" fill-rule="nonzero"/><path fill="#07032a" d="M 472.542969 122.851562 C 473.1875 125.40625 473.203125 127.515625 475.082031 129.8125 C 476.25 131.246094 479.167969 132.363281 479.421875 133.445312 C 479.691406 134.558594 477.714844 137.867188 477.542969 139.84375 C 473.589844 140.457031 467.074219 141.378906 463.542969 142.839844 C 458.773438 134.730469 463.335938 124.589844 472.542969 122.851562 Z M 472.542969 122.851562 " fill-opacity="1" fill-rule="nonzero"/><path fill="#6b338c" d="M 208.492188 283.769531 C 207.78125 289.398438 206.238281 295.195312 205.492188 300.761719 C 202.042969 301.222656 199.410156 299.148438 196.492188 297.761719 C 196.984375 291.800781 197 285.722656 197.492188 279.769531 Z M 208.492188 283.769531 " fill-opacity="1" fill-rule="nonzero"/><path fill="#17092e" d="M 166.484375 213.804688 L 171.488281 214.816406 C 171.953125 215.265625 166.761719 225.578125 165.472656 226.289062 C 163.171875 227.5625 157.175781 225.691406 157.480469 229.796875 C 154.382812 229.066406 151.015625 229.40625 148.507812 226.304688 C 151.136719 218.886719 153.984375 222.136719 158.261719 220.085938 C 160.859375 218.839844 160.109375 216.425781 160.613281 215.957031 C 161.953125 214.726562 167.578125 217.703125 166.476562 213.804688 Z M 166.484375 213.804688 " fill-opacity="1" fill-rule="nonzero"/><path fill="#75458c" d="M 205.492188 300.761719 C 204.964844 304.707031 205.261719 309.613281 204.492188 313.753906 C 203.613281 313.753906 202.660156 314.753906 202.492188 314.753906 C 199.964844 314.753906 197.496094 313.761719 194.492188 313.753906 C 194.824219 309.253906 195.078125 304.679688 195.445312 300.175781 C 195.550781 298.882812 196.480469 297.933594 196.492188 297.761719 C 199.410156 299.148438 202.042969 301.222656 205.492188 300.761719 Z M 205.492188 300.761719 " fill-opacity="1" fill-rule="nonzero"/><path fill="#1b0141" d="M 573.5625 78.875 C 573.375 76.835938 574.132812 74.707031 576.261719 74.070312 C 578.515625 73.398438 598.980469 73.515625 599.675781 74.464844 L 600.566406 78.875 C 591.582031 78.914062 582.546875 78.820312 573.5625 78.875 Z M 573.5625 78.875 " fill-opacity="1" fill-rule="nonzero"/><path fill="#75458c" d="M 389.527344 186.816406 C 386.082031 192.328125 386.832031 196.390625 386.570312 202.394531 C 386.515625 203.679688 385.527344 204.679688 385.527344 204.808594 C 380.574219 207.324219 379.199219 202.164062 377.914062 198.75 C 377.089844 198.527344 365.144531 198.566406 364.523438 198.8125 L 364.523438 197.8125 L 377.859375 197.644531 C 379.492188 197.09375 382.96875 189.703125 386.011719 187.757812 C 387.582031 186.75 389.0625 187.078125 389.527344 186.816406 Z M 389.527344 186.816406 " fill-opacity="1" fill-rule="nonzero"/><path fill="#9e6ebb" d="M 95.472656 268.777344 C 101.574219 276.5 113.929688 277.601562 123.160156 281.585938 C 128.667969 283.964844 132.777344 286.007812 136.480469 289.765625 C 123.808594 284.152344 111.382812 277.738281 97.472656 275.773438 C 96.128906 272.597656 96.050781 272.136719 95.472656 268.777344 Z M 95.472656 268.777344 " fill-opacity="1" fill-rule="nonzero"/><path fill="#9e6ebb" d="M 148.484375 320.75 L 146.480469 320.75 C 147.503906 314.996094 151.828125 304.699219 150.273438 299.464844 C 149.203125 295.863281 139.925781 293.246094 136.480469 289.765625 C 140.660156 291.617188 150.355469 293.445312 152.035156 298.707031 C 154.363281 306.019531 148.125 314.398438 148.484375 320.75 Z M 148.484375 320.75 " fill-opacity="1" fill-rule="nonzero"/><path fill="#1b0141" d="M 541.554688 78.875 C 533.238281 78.886719 524.867188 78.863281 516.550781 78.875 C 517.886719 68.832031 529.210938 76.519531 534.128906 76.875 C 537.484375 77.117188 541.457031 71.59375 541.554688 78.875 Z M 541.554688 78.875 " fill-opacity="1" fill-rule="nonzero"/><path fill="#17092e" d="M 135.480469 237.792969 C 140.28125 236.558594 141.960938 234.035156 147.476562 236.792969 L 147.535156 233.898438 C 149.074219 232.433594 160.441406 236.570312 160.480469 230.796875 C 160.609375 230.8125 163.65625 228.519531 162.46875 231.277344 C 161.90625 232.585938 157.847656 239.292969 156.804688 239.644531 L 135.476562 237.796875 Z M 135.480469 237.792969 " fill-opacity="1" fill-rule="nonzero"/><path fill="#18013b" d="M 367.523438 144.839844 C 361.890625 143.589844 361.070312 148.9375 357.519531 149.835938 C 357.285156 148.359375 356.46875 146.101562 356.992188 144.867188 C 358.058594 142.347656 364.617188 139.621094 363.523438 134.84375 C 367.015625 136.480469 368.574219 137.855469 368.582031 142.414062 C 368.582031 143.828125 367.5625 144.574219 367.523438 144.839844 Z M 367.523438 144.839844 " fill-opacity="1" fill-rule="nonzero"/><path fill="#1e0442" d="M 367.523438 144.839844 C 366.757812 150.773438 366.203125 154.40625 360.523438 157.832031 C 360.269531 156.574219 358.035156 153.035156 357.519531 149.835938 C 361.070312 148.9375 361.890625 143.589844 367.523438 144.839844 Z M 367.523438 144.839844 " fill-opacity="1" fill-rule="nonzero"/><path fill="#904f9c" d="M 175.488281 102.859375 C 174.210938 109.867188 160.769531 109.878906 159.484375 102.859375 C 164.804688 102.878906 170.164062 102.878906 175.488281 102.859375 Z M 175.488281 102.859375 " fill-opacity="1" fill-rule="nonzero"/><path fill="#b64c94" d="M 451.539062 182.820312 C 451.6875 184.464844 451.410156 186.175781 451.539062 187.824219 L 453.539062 187.816406 C 453.5 189.484375 453.578125 191.148438 453.539062 192.816406 L 451.535156 193.320312 L 451.542969 195.808594 L 453.539062 195.808594 C 453.53125 196.480469 453.542969 197.144531 453.539062 197.8125 L 450.539062 197.8125 C 449.25 194.074219 449.417969 190.160156 449.542969 186.269531 C 449.605469 184.347656 448.515625 182.261719 451.539062 182.820312 Z M 451.539062 182.820312 " fill-opacity="1" fill-rule="nonzero"/><path fill="#e3d8d1" d="M 93.472656 289.765625 C 90.808594 290.34375 91.527344 288.425781 90.984375 286.808594 C 89.621094 282.734375 88.289062 276.671875 86.101562 273.132812 C 83.21875 268.46875 74.023438 260.332031 68.902344 257.808594 C 67.925781 257.074219 69.472656 256.863281 69.46875 256.78125 C 82.632812 262.28125 91.300781 275.964844 93.472656 289.765625 Z M 93.472656 289.765625 " fill-opacity="1" fill-rule="nonzero"/><path fill="#e3d8d1" d="M 100.472656 293.761719 C 100.867188 295.808594 99.019531 295.476562 98.324219 297.148438 C 96.578125 301.328125 95.855469 306.507812 94.472656 310.753906 L 92.46875 310.753906 C 92.710938 308.667969 92.84375 306.789062 93.472656 304.757812 L 94.472656 303.757812 C 95.625 300.578125 96.136719 297.207031 98.4375 294.445312 C 99.21875 293.503906 100.378906 293.863281 100.472656 293.761719 Z M 100.472656 293.761719 " fill-opacity="1" fill-rule="nonzero"/><path fill="#1b0141" d="M 563.558594 78.875 C 562.945312 76.269531 565.863281 76.089844 568.046875 75.859375 L 568.5625 78.875 C 566.894531 78.882812 565.226562 78.871094 563.558594 78.875 Z M 563.558594 78.875 " fill-opacity="1" fill-rule="nonzero"/><path fill="#b64c94" d="M 451.539062 179.820312 C 451.542969 179.109375 451.445312 179.082031 451.539062 177.824219 L 452.535156 178.332031 Z M 451.539062 179.820312 " fill-opacity="1" fill-rule="nonzero"/><path fill="#e3d8d1" d="M 88.472656 309.753906 L 86.621094 304.019531 C 86.371094 302.597656 87.210938 302.992188 87.472656 302.757812 C 88.453125 306.496094 89.671875 306.164062 88.472656 309.753906 Z M 88.472656 309.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#c03666" d="M 453.539062 197.8125 C 453.539062 198.144531 453.539062 198.480469 453.539062 198.8125 L 450.539062 198.8125 L 450.539062 197.8125 Z M 453.539062 197.8125 " fill-opacity="1" fill-rule="nonzero"/><path fill="#9e6ebb" d="M 93.472656 304.757812 C 93.609375 304.3125 94.390625 303.984375 94.472656 303.757812 Z M 93.472656 304.757812 " fill-opacity="1" fill-rule="nonzero"/><path fill="#c9396a" d="M 467.542969 356.730469 C 463.945312 363.886719 461.445312 363.375 455.710938 366.925781 C 455.21875 367.230469 455.648438 368.640625 455.539062 368.726562 C 454.898438 369.214844 451.929688 367.53125 452.546875 370.210938 C 458.449219 375.929688 482.421875 372.148438 479.578125 361.382812 C 479.300781 360.332031 477.605469 360.816406 477.542969 360.730469 C 477.363281 360.488281 477.59375 358.523438 477.542969 357.730469 L 504.546875 358.730469 C 506.007812 360.1875 507.785156 359.660156 509.550781 359.730469 L 510.550781 371.722656 C 509.777344 371.722656 497.179688 377.632812 496.597656 378.269531 C 495.816406 379.125 494.722656 379.449219 496.023438 380.738281 C 503.195312 384.820312 510.851562 382.554688 517.550781 378.71875 L 520.550781 378.71875 C 520.664062 379.699219 520.476562 380.734375 520.550781 381.71875 C 521.34375 384.007812 523.351562 382.46875 524.550781 381.71875 C 527.769531 379.710938 529.050781 367.84375 529.554688 363.726562 C 532.148438 362.285156 535.945312 363.902344 537.820312 363.527344 C 539.988281 363.09375 541.910156 359.5 544.550781 359.738281 C 545.726562 361.078125 542.929688 381.355469 545.554688 384.722656 L 545.554688 386.71875 L 404.53125 386.71875 L 403.53125 385.71875 L 403.53125 373.726562 C 408.347656 372.90625 413.648438 374.488281 418.085938 374.601562 C 418.902344 374.621094 419.363281 373.746094 419.53125 373.726562 C 419.863281 373.683594 420.210938 373.78125 420.53125 373.726562 C 421.152344 373.621094 421.886719 373.796875 422.535156 373.726562 C 422.730469 374.789062 424.328125 384.375 425.527344 382.722656 C 425.757812 378.117188 424.382812 373.65625 423.558594 369.152344 C 423.21875 367.296875 424.699219 365.15625 421.535156 365.730469 C 421.515625 365.429688 420.679688 363.566406 420.53125 361.734375 C 424.761719 362.5625 420.117188 356.191406 421.527344 354.738281 L 467.542969 356.734375 Z M 467.542969 356.730469 " fill-opacity="1" fill-rule="nonzero"/><path fill="#c9396a" d="M 380.527344 354.730469 C 380.179688 357.050781 379.832031 359.410156 379.527344 361.730469 C 378.667969 368.214844 377.96875 374.808594 376.511719 381.207031 C 378.890625 383.566406 378.398438 379.832031 378.523438 379.71875 C 379.429688 378.890625 381.703125 380.300781 380.535156 374.726562 C 385.847656 375.480469 391.359375 372.507812 397.539062 373.71875 L 398.53125 386.714844 C 367.878906 386.730469 337.171875 386.753906 306.515625 386.714844 L 305.515625 383.71875 C 313.003906 383.066406 315.785156 379.0625 307.316406 376.421875 C 303.941406 375.371094 299.488281 373.304688 297.515625 372.722656 C 298.824219 367.789062 299.609375 362.753906 300.515625 357.730469 L 322.519531 357.730469 C 322.636719 360 321.945312 362.222656 323.441406 364.304688 C 325.707031 367.460938 333.230469 369.90625 334.359375 363.980469 C 335.105469 360.0625 332.578125 359.976562 332.519531 359.726562 C 332.445312 359.414062 332.582031 359.046875 332.519531 358.726562 L 341.859375 357.539062 L 342.523438 356.726562 C 345.382812 360.6875 349.488281 361.019531 350.523438 355.726562 C 360.269531 356.957031 370.714844 353.964844 380.53125 354.726562 Z M 380.527344 354.730469 " fill-opacity="1" fill-rule="nonzero"/><path fill="#c03666" d="M 242.5 357.730469 C 241.289062 366.089844 243.390625 377.046875 242.503906 385.71875 L 247.359375 384.074219 C 247.679688 375.632812 247.433594 367.164062 247.5 358.730469 L 263.503906 358.730469 C 263.601562 359.714844 263.417969 360.742188 263.503906 361.730469 C 256.273438 362.3125 261.46875 370.871094 260.082031 372.773438 C 257.5625 374.363281 254.582031 373.476562 251.660156 374.386719 C 245.628906 376.257812 248.480469 381.625 253.847656 381.667969 L 254.5 386.714844 C 231.929688 387.222656 214.363281 384.769531 192.488281 378.71875 C 194.410156 377.988281 194.820312 376.988281 195.425781 375.15625 C 196.578125 371.648438 197.925781 364.511719 198.488281 360.730469 L 220.492188 358.730469 C 220.207031 361.066406 217.667969 381.542969 218.996094 381.722656 C 220.746094 381.925781 221.636719 381.792969 222.277344 380.003906 C 223.988281 375.210938 224.652344 364.4375 225.488281 358.726562 L 242.492188 357.726562 Z M 242.5 357.730469 " fill-opacity="1" fill-rule="nonzero"/><path fill="#c03666" d="M 565.558594 358.730469 C 565.972656 361.753906 568.003906 381.460938 569.128906 381.773438 L 572.554688 381.722656 C 571.847656 374.125 571.546875 366.277344 570.558594 358.730469 L 596.5625 359.730469 C 597.144531 366.175781 599.246094 373.136719 599.5625 379.71875 C 581.722656 382.726562 563.585938 388.453125 545.550781 386.714844 L 545.550781 385.714844 C 547.085938 385.292969 549.371094 387.09375 549.5625 384.25 C 550.117188 376.113281 549.503906 367.003906 549.554688 358.730469 Z M 565.558594 358.730469 " fill-opacity="1" fill-rule="nonzero"/><path fill="#17092e" d="M 392.527344 314.753906 C 398.710938 314.796875 404.832031 313.96875 410.53125 313.753906 C 413.816406 313.628906 417.246094 313.640625 420.53125 313.753906 L 424.476562 314.828125 L 424.535156 316.75 C 424.226562 316.835938 423.84375 316.664062 423.535156 316.75 C 422.027344 317.175781 421.066406 316.789062 418.53125 317.75 C 417.84375 318.011719 416.984375 317.894531 416.53125 318.75 L 415.632812 319.382812 C 415.523438 320.179688 416.5 320.574219 416.53125 320.75 C 418.871094 333.671875 419.464844 348.523438 420.53125 361.730469 C 420.679688 363.5625 421.515625 365.425781 421.535156 365.726562 C 421.601562 366.980469 421.644531 368.496094 421.535156 369.726562 C 421.414062 371.027344 420.738281 372.402344 420.53125 373.722656 C 420.210938 373.777344 419.863281 373.679688 419.53125 373.722656 C 415.328125 373.972656 417.25 374.375 417.019531 371.75 C 416.5 365.769531 416.070312 359.726562 415.53125 353.734375 C 414.492188 342.089844 413.601562 330.386719 412.535156 318.746094 L 404.105469 318.734375 C 403.050781 330.3125 403.53125 342.109375 403.53125 353.734375 C 403.53125 360.382812 403.53125 367.070312 403.53125 373.722656 L 403.53125 386.714844 C 402.195312 386.714844 400.863281 386.714844 399.527344 386.714844 L 399.527344 353.734375 C 399.527344 342.085938 399.527344 330.394531 399.535156 318.746094 L 391.105469 318.691406 C 389.328125 330.152344 387.707031 342.117188 386.527344 353.734375 C 385.859375 360.308594 385.488281 367.101562 385.523438 373.726562 L 381.53125 373.726562 C 381.640625 371.417969 381.339844 369.023438 381.527344 366.726562 C 382.226562 358.105469 383.671875 349.4375 383.527344 340.738281 C 384.144531 339.132812 384.703125 339.265625 384.527344 336.742188 L 384.527344 332.742188 C 385.039062 327.769531 385.90625 322.808594 385.519531 317.757812 C 383.039062 317.667969 379.863281 317.46875 377.523438 316.75 L 377.523438 315.753906 C 377.636719 315.140625 377.449219 314.394531 377.523438 313.753906 C 383 313.40625 387.773438 314.714844 392.527344 314.753906 Z M 392.527344 314.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f9848c" d="M 630.570312 370.722656 C 635.285156 372.40625 642.929688 372.398438 647.574219 370.722656 C 648.574219 370.746094 649.574219 370.703125 650.574219 370.722656 C 651.457031 370.742188 654.066406 371.691406 656.578125 371.722656 C 672.890625 371.949219 689.269531 371.574219 705.585938 371.722656 C 708.628906 371.753906 711.925781 372.691406 715.589844 372.722656 C 717.164062 374.40625 722.054688 374.390625 723.589844 372.722656 C 727.226562 372.703125 730.964844 372.917969 734.589844 372.722656 C 734.960938 376 734.835938 375.210938 732.417969 376.003906 C 729.816406 376.863281 726.875 377.546875 724.125 377.753906 C 690.605469 380.324219 653.890625 375.71875 620.019531 377.769531 L 616.570312 374.71875 C 621.148438 373.230469 621.769531 371.726562 623.570312 370.71875 C 624.097656 370.425781 629.097656 370.757812 630.570312 370.71875 Z M 630.570312 370.722656 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f9848c" d="M 146.480469 371.722656 C 156.128906 371.820312 166.847656 373.042969 176.488281 374.722656 C 175.554688 376.191406 174.628906 377.167969 172.804688 377.496094 C 169.4375 378.097656 162.683594 378.578125 159.027344 378.761719 C 141.023438 379.671875 113.574219 380.269531 95.929688 378.761719 C 91.207031 378.359375 89.566406 377.988281 89.472656 372.722656 C 90.136719 372.742188 90.804688 372.707031 91.472656 372.722656 C 93.335938 374.40625 98.609375 374.40625 100.472656 372.722656 C 111.785156 372.847656 123.609375 371.703125 134.480469 371.722656 C 138.46875 371.730469 142.492188 371.6875 146.480469 371.722656 Z M 146.480469 371.722656 " fill-opacity="1" fill-rule="nonzero"/><path fill="#c9396a" d="M 281.507812 364.726562 C 281.699219 367.359375 281.394531 370.078125 281.507812 372.722656 L 280.507812 385.714844 C 272.1875 385.726562 263.078125 386.523438 254.503906 386.714844 L 253.851562 381.667969 C 248.480469 381.628906 245.632812 376.257812 251.664062 374.386719 C 254.585938 373.476562 257.566406 374.363281 260.085938 372.773438 C 261.46875 370.871094 256.277344 362.3125 263.507812 361.730469 C 263.59375 362.714844 263.433594 363.742188 263.507812 364.726562 C 263.902344 369.835938 264.566406 374.953125 264.460938 380.097656 C 264.710938 381.316406 266.003906 380.519531 266.507812 380.71875 C 267.757812 381.21875 268.617188 382.316406 270.503906 381.722656 C 270.558594 380.066406 270.464844 378.386719 270.507812 376.722656 L 271.503906 375.230469 L 270.507812 374.722656 C 270.585938 374.074219 270.476562 373.382812 270.507812 372.722656 C 270.5625 371.742188 271.929688 370.035156 271.601562 367.175781 C 271.464844 365.960938 267.6875 363.71875 269.511719 359.734375 L 281.511719 364.726562 Z M 281.507812 364.726562 " fill-opacity="1" fill-rule="nonzero"/><path fill="#c03666" d="M 160.484375 359.730469 C 160.96875 362.570312 164.339844 368.183594 164.5 371.71875 C 168.523438 372.554688 165.253906 366.507812 166.976562 364.730469 C 173.140625 372.828125 175.296875 373.542969 185.484375 371.71875 C 186.359375 367.34375 181.695312 367.6875 179.445312 365.257812 C 177.90625 363.59375 178.179688 362.074219 177.484375 360.730469 L 191.488281 360.730469 C 191.089844 366.378906 190.503906 372.046875 190.484375 377.71875 C 186.042969 375.757812 181.183594 375.542969 176.484375 374.722656 C 166.84375 373.042969 156.125 371.820312 146.476562 371.722656 L 150.476562 371.722656 C 150.984375 369.980469 150.125 369.691406 149.480469 368.726562 C 147.050781 365.082031 141.648438 365.398438 139.476562 360.730469 L 160.480469 359.730469 Z M 160.484375 359.730469 " fill-opacity="1" fill-rule="nonzero"/><path fill="#c03666" d="M 633.574219 360.730469 C 632.75 365.722656 626.878906 364.988281 624.167969 366.816406 C 622.738281 367.785156 621.367188 369.761719 623.570312 370.722656 C 621.769531 371.730469 621.148438 373.234375 616.570312 374.722656 C 614.46875 375.40625 605.183594 377.148438 604.566406 377.71875 C 603.285156 371.851562 603.363281 365.734375 603.566406 359.730469 C 612.425781 359.769531 621.3125 359.703125 630.1875 359.660156 C 632.019531 359.652344 633.398438 360.730469 633.574219 360.730469 Z M 633.574219 360.730469 " fill-opacity="1" fill-rule="nonzero"/><path fill="#c03666" d="M 399.527344 353.734375 L 399.527344 386.714844 C 399.195312 386.714844 398.863281 386.714844 398.527344 386.714844 L 397.53125 373.71875 C 391.355469 372.507812 385.847656 375.480469 380.53125 374.726562 C 381.703125 380.300781 379.425781 378.890625 378.519531 379.71875 C 379.257812 375.632812 380.140625 370.804688 380.519531 366.726562 L 381.523438 366.726562 C 381.335938 369.023438 381.636719 371.417969 381.527344 373.726562 L 385.519531 373.726562 C 385.484375 367.097656 385.855469 360.308594 386.523438 353.734375 Z M 399.527344 353.734375 " fill-opacity="1" fill-rule="nonzero"/><path fill="#8d4e9c" d="M 603.566406 351.734375 C 603.117188 353.5625 603.644531 357.445312 603.566406 359.730469 C 603.363281 365.734375 603.285156 371.851562 604.566406 377.71875 C 604.433594 377.84375 605.0625 379.40625 603.882812 379.746094 C 602.660156 380.097656 600.867188 379.5 599.566406 379.71875 C 599.25 373.136719 597.148438 366.175781 596.566406 359.730469 C 596.304688 356.796875 596.75 353.6875 596.566406 350.734375 C 598.242188 351.402344 601.625 351.523438 603.566406 351.734375 Z M 603.566406 351.734375 " fill-opacity="1" fill-rule="nonzero"/><path fill="#904f9c" d="M 192.492188 352.734375 L 192.492188 356.734375 C 196.363281 356.980469 197.234375 357.488281 198.492188 353.734375 C 198.179688 355.890625 198.8125 358.582031 198.492188 360.730469 C 197.925781 364.511719 196.578125 371.648438 195.429688 375.15625 C 194.824219 376.988281 194.421875 377.984375 192.492188 378.71875 L 190.492188 377.71875 C 190.507812 372.046875 191.09375 366.378906 191.492188 360.730469 C 191.6875 357.921875 192.375 354.558594 192.492188 352.734375 Z M 192.492188 352.734375 " fill-opacity="1" fill-rule="nonzero"/><path fill="#c03666" d="M 281.507812 372.722656 C 281.617188 375.292969 280.84375 381.332031 283.175781 382.796875 C 285.480469 384.25 301.777344 384.042969 305.511719 383.71875 L 306.511719 386.714844 C 297.851562 386.703125 288.648438 385.707031 280.507812 385.714844 Z M 281.507812 372.722656 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f9848c" d="M 744.59375 371.722656 C 744.925781 371.722656 745.261719 371.722656 745.59375 371.722656 L 745.09375 372.703125 Z M 744.59375 371.722656 " fill-opacity="1" fill-rule="nonzero"/><path fill="#c03666" d="M 404.53125 386.714844 C 404.195312 386.714844 403.863281 386.714844 403.53125 386.714844 L 403.53125 385.714844 Z M 404.53125 386.714844 " fill-opacity="1" fill-rule="nonzero"/><path fill="#07032a" d="M 720.589844 183.820312 C 720.535156 185.199219 720.898438 186.628906 721.589844 187.816406 C 723.1875 190.570312 728.683594 193.09375 730.589844 196.8125 C 736.429688 208.1875 732.085938 228.472656 729.589844 240.789062 C 728.835938 244.519531 728.417969 248.339844 727.308594 252 C 722.609375 258.839844 722.902344 272.488281 716.527344 277.210938 C 711.417969 280.996094 708.019531 279.214844 702.585938 279.769531 L 700.585938 261.78125 C 702.332031 261.625 705.765625 259.761719 708.582031 260.777344 L 706.578125 247.796875 C 705.082031 247.96875 702.886719 247.457031 701.585938 247.785156 C 702.878906 232.300781 704.210938 216.898438 708.09375 201.820312 C 709.796875 195.214844 713.527344 189.726562 713.585938 182.820312 C 713.589844 182.152344 713.585938 181.488281 713.585938 180.820312 C 714.097656 181.171875 719.199219 182.632812 720.589844 183.820312 Z M 720.589844 183.820312 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f5b499" d="M 709.585938 172.824219 C 710.761719 175.261719 710.894531 178.972656 713.585938 180.820312 C 713.585938 181.488281 713.589844 182.152344 713.585938 182.820312 C 712.128906 184.894531 700.339844 198.558594 698.660156 192.191406 C 698.957031 190.019531 699.453125 188.03125 699.585938 185.820312 C 699.703125 183.835938 699.511719 181.808594 699.582031 179.824219 C 687.132812 184.074219 687.015625 169.632812 685.582031 160.832031 C 688.121094 161.015625 692.171875 159.046875 696.101562 159.824219 C 698.863281 160.371094 698.492188 163.09375 700.269531 163.683594 C 701.445312 164.074219 703.34375 162.683594 704.972656 163.859375 C 707.203125 165.460938 706.660156 168.746094 707.804688 171.148438 C 708.289062 172.175781 709.492188 172.628906 709.582031 172.824219 Z M 709.585938 172.824219 " fill-opacity="1" fill-rule="nonzero"/><path fill="#6b338c" d="M 709.585938 172.824219 C 709.492188 172.628906 708.289062 172.171875 707.808594 171.148438 C 706.664062 168.746094 707.207031 165.460938 704.976562 163.859375 C 703.34375 162.683594 701.449219 164.074219 700.273438 163.683594 C 698.496094 163.09375 698.863281 160.375 696.105469 159.824219 C 692.175781 159.046875 688.128906 161.015625 685.585938 160.832031 C 680.023438 160.425781 677 153.109375 681.585938 149.835938 C 682.65625 149.070312 688.886719 147.179688 690.585938 146.839844 C 710.082031 142.941406 713.058594 156.285156 709.589844 172.824219 Z M 709.585938 172.824219 " fill-opacity="1" fill-rule="nonzero"/><path fill="#88c0af" d="M 721.589844 187.816406 C 720.898438 186.628906 720.535156 185.199219 720.589844 183.820312 C 720.679688 181.546875 722.59375 175.539062 723.535156 173.226562 C 724.171875 171.652344 725.441406 171.125 725.589844 170.828125 Z M 721.589844 187.816406 " fill-opacity="1" fill-rule="nonzero"/><path fill="#1b0141" d="M 617.570312 54.886719 C 617.570312 56.21875 617.570312 57.550781 617.570312 58.882812 C 615.527344 60.070312 612.285156 59.398438 610.570312 59.882812 C 611.320312 56.160156 606.722656 59.203125 605.695312 56.25 " fill-opacity="1" fill-rule="nonzero"/><path fill="#1e0442" d="M 617.570312 58.882812 L 617.570312 60.882812 C 614.570312 60.929688 612.492188 60.964844 609.566406 61.882812 C 609.464844 60.890625 609.433594 60.203125 610.570312 59.882812 C 612.285156 59.398438 615.527344 60.070312 617.570312 58.882812 Z M 617.570312 58.882812 " fill-opacity="1" fill-rule="nonzero"/><path fill="#1b0140" d="M 374.324219 53.582031 C 374.851562 55.324219 374.835938 60.425781 374.320312 62.183594 C 373 66.675781 362.335938 64.441406 358.105469 64.964844 C 349.023438 66.085938 347.976562 67.855469 337.058594 67.835938 C 315.050781 67.800781 292.742188 67.105469 271 67.8125 C 264.941406 68.011719 259.496094 72.300781 253.449219 70.421875 C 251.957031 69.960938 250.941406 68.273438 248.964844 67.914062 C 246.503906 67.460938 243.617188 68.394531 241.195312 67.679688 C 237.875 66.699219 239.007812 62.355469 237.566406 61.3125 C 235.453125 59.777344 229.675781 62.367188 227.402344 59.476562 C 224.628906 55.960938 228.328125 39.253906 225.558594 37.328125 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 129.480469 313.753906 C 128.691406 324.925781 129.5 336.746094 130.480469 347.734375 C 130.710938 350.359375 130.316406 353.09375 130.480469 355.730469 C 130.074219 355.792969 128.929688 356.4375 128.480469 356.730469 C 126.839844 357.796875 126.816406 357.648438 126.476562 359.730469 C 118.886719 360.40625 109.863281 358.808594 102.472656 359.730469 C 103.207031 355.226562 106.367188 351.996094 107.753906 347.515625 C 109.269531 342.625 109.320312 338.207031 110.355469 333.324219 L 114.484375 332.746094 C 113.566406 327.667969 115.941406 322.632812 116.269531 317.90625 C 116.421875 315.679688 116.492188 315.882812 114.480469 314.75 C 114.660156 314.730469 115.59375 313.832031 116.898438 313.707031 C 120.898438 313.320312 125.40625 314.0625 129.484375 313.75 Z M 129.480469 313.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#8d4e9c" d="M 129.480469 313.753906 C 125.402344 314.0625 120.894531 313.324219 116.894531 313.710938 C 115.589844 313.835938 114.652344 314.734375 114.476562 314.753906 C 113.820312 314.816406 113.132812 314.699219 112.476562 314.753906 C 113.171875 308.460938 117.730469 303.445312 121.476562 298.761719 C 124.292969 300.480469 128.328125 301.632812 131.046875 303.757812 C 132.230469 305.625 129.617188 311.789062 129.480469 313.753906 Z M 129.480469 313.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fbf6de" d="M 627.570312 102.859375 C 625.042969 111.648438 611.542969 110.644531 608.566406 102.859375 Z M 627.570312 102.859375 " fill-opacity="1" fill-rule="nonzero"/><path fill="#1e0442" d="M 603.566406 75.875 L 605.566406 67.878906 C 605.015625 72.710938 606.210938 71.464844 603.566406 75.875 Z M 603.566406 75.875 " fill-opacity="1" fill-rule="nonzero"/><path fill="#1e0442" d="M 605.566406 65.878906 C 605.960938 63.730469 606.53125 62.800781 608.566406 61.882812 Z M 605.566406 65.878906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#e3d8d1" d="M 83.152344 297.117188 C 81.460938 295.609375 78.28125 294.785156 78.472656 291.769531 C 82.46875 292.023438 83.539062 296.636719 85.449219 299.269531 C 84.078125 300.214844 83.773438 297.664062 83.152344 297.113281 Z M 83.152344 297.117188 " fill-opacity="1" fill-rule="nonzero"/><path fill="#e3d8d1" d="M 85.972656 300.761719 C 86.621094 301.09375 86.621094 301.425781 85.972656 301.757812 Z M 85.972656 300.761719 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f9848c" d="M 737.59375 270.773438 C 737.761719 282.023438 737.621094 288.898438 734.589844 299.761719 C 733.996094 301.902344 731.589844 304.335938 731.589844 306.757812 C 728.160156 309.644531 724.042969 311.238281 719.589844 311.753906 C 718.632812 311.867188 717.566406 311.738281 716.589844 311.753906 C 715.257812 311.78125 713.917969 311.773438 712.585938 311.753906 C 708.164062 311.691406 702.992188 311.769531 698.585938 311.753906 C 697.25 311.75 695.917969 311.742188 694.585938 311.753906 C 690.078125 311.800781 685.472656 311.476562 680.582031 311.753906 C 676.949219 311.960938 673.226562 311.609375 669.582031 311.75 L 670.578125 304.757812 C 678.207031 304.179688 682.101562 292.09375 682.582031 285.769531 C 682.605469 285.4375 682.566406 285.101562 682.582031 284.769531 C 685.433594 284.5 686.507812 281.625 689.292969 280.976562 C 692.320312 280.277344 698.910156 280.144531 702.585938 279.769531 C 708.019531 279.214844 711.417969 280.996094 716.527344 277.210938 C 722.902344 272.488281 722.605469 258.839844 727.308594 252 C 728.417969 248.339844 728.835938 244.519531 729.589844 240.789062 C 733.21875 240.460938 735.425781 243.59375 736.164062 246.714844 C 737.375 251.871094 737.503906 264.832031 737.59375 270.773438 Z M 737.59375 270.773438 " fill-opacity="1" fill-rule="nonzero"/><path fill="#17092e" d="M 149.484375 368.726562 C 150.128906 369.691406 150.988281 369.980469 150.480469 371.71875 L 146.480469 371.71875 C 142.492188 371.6875 138.46875 371.730469 134.480469 371.722656 C 132.117188 369.972656 129.5 367.230469 126.476562 366.726562 L 126.476562 365.726562 C 126.683594 363.824219 126.1875 361.539062 126.476562 359.730469 C 126.816406 357.648438 126.839844 357.796875 128.480469 356.730469 C 131.984375 366.671875 139.085938 370.222656 149.484375 368.726562 Z M 149.484375 368.726562 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f9848c" d="M 75.46875 366.726562 L 100.472656 366.726562 L 100.472656 367.726562 L 75.46875 367.726562 Z M 75.46875 366.726562 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f9848c" d="M 126.476562 365.726562 L 126.476562 366.726562 C 124.167969 366.34375 102.464844 367.425781 102.464844 366.226562 Z M 126.476562 365.726562 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 100.472656 372.722656 C 98.609375 374.40625 93.335938 374.40625 91.472656 372.722656 C 94.460938 372.796875 97.480469 372.691406 100.472656 372.722656 Z M 100.472656 372.722656 " fill-opacity="1" fill-rule="nonzero"/><path fill="#7d4399" d="M 712.585938 311.753906 C 719.835938 320.152344 717.402344 329.214844 720.589844 338.742188 C 718.261719 338.816406 715.910156 338.683594 713.582031 338.738281 C 713.4375 340.371094 713.792969 342.113281 713.585938 343.738281 C 713.054688 348.066406 711.585938 348.199219 710.585938 350.734375 C 701.410156 353.492188 691.742188 353.488281 682.582031 350.734375 C 683.074219 349.554688 683.023438 347.308594 683.804688 345.46875 C 688.59375 334.175781 693.886719 323.078125 698.585938 311.753906 C 702.992188 311.769531 708.164062 311.691406 712.585938 311.753906 Z M 712.585938 311.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#7bb9a7" d="M 734.589844 338.742188 C 733.257812 338.742188 731.925781 338.742188 730.589844 338.742188 C 729.335938 329.007812 721.464844 321.277344 719.589844 311.753906 C 724.042969 311.238281 728.160156 309.644531 731.589844 306.757812 C 731.589844 310.105469 733.277344 316.492188 733.582031 320.257812 C 734.074219 326.359375 734.09375 332.636719 734.589844 338.742188 Z M 734.589844 338.742188 " fill-opacity="1" fill-rule="nonzero"/><path fill="#7bb9a7" d="M 716.589844 311.753906 L 728.589844 338.742188 C 725.929688 338.742188 723.242188 338.65625 720.589844 338.742188 C 717.402344 329.214844 719.835938 320.152344 712.585938 311.753906 C 713.917969 311.773438 715.257812 311.78125 716.589844 311.753906 Z M 716.589844 311.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 721.589844 359.730469 L 711.585938 359.730469 C 712.523438 355.585938 713.367188 349.445312 716.589844 346.738281 C 716.800781 346.960938 718.433594 346.628906 719.417969 348.367188 C 720.6875 350.613281 721.289062 356.867188 721.589844 359.730469 Z M 721.589844 359.730469 " fill-opacity="1" fill-rule="nonzero"/><path fill="#e3d8d1" d="M 713.585938 343.738281 C 716.449219 343.757812 716.289062 346.414062 716.589844 346.738281 C 713.367188 349.445312 712.523438 355.585938 711.585938 359.730469 L 705.585938 369.726562 C 702.632812 370.632812 703.902344 366.75 704.585938 364.726562 C 704.933594 363.707031 706.035156 361.125 706.585938 359.730469 C 707.625 357.09375 709.324219 353.933594 710.585938 350.734375 C 711.585938 348.199219 713.054688 348.066406 713.585938 343.738281 Z M 713.585938 343.738281 " fill-opacity="1" fill-rule="nonzero"/><path fill="#e3d8d1" d="M 719.589844 311.753906 C 721.464844 321.277344 729.335938 329.007812 730.589844 338.742188 L 728.589844 338.742188 L 716.589844 311.753906 C 717.566406 311.738281 718.632812 311.867188 719.589844 311.753906 Z M 719.589844 311.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#b64c94" d="M 704.585938 364.726562 C 703.902344 366.75 702.632812 370.632812 705.585938 369.726562 L 705.585938 371.722656 C 689.269531 371.574219 672.890625 371.949219 656.578125 371.722656 L 660.03125 369.726562 L 669.574219 368.734375 L 650.574219 368.726562 C 650.824219 367.796875 651.628906 366.933594 652.578125 366.726562 C 654.121094 366.382812 670.785156 366.207031 671.578125 366.726562 C 671.667969 366.785156 671.347656 368.617188 672.074219 368.761719 C 674.820312 369.3125 675.464844 366.871094 676.582031 364.726562 C 681.316406 366.300781 687.054688 363.953125 692.035156 363.679688 C 695.945312 363.464844 700.917969 363.238281 704.585938 364.726562 Z M 704.585938 364.726562 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 723.589844 372.722656 C 722.054688 374.390625 717.164062 374.40625 715.589844 372.722656 C 718.25 372.75 720.925781 372.738281 723.589844 372.722656 Z M 723.589844 372.722656 " fill-opacity="1" fill-rule="nonzero"/><path fill="#07032a" d="M 566.558594 254.785156 C 566.558594 255.085938 567.398438 260.042969 567.558594 260.78125 C 567.894531 262.308594 568.921875 263.855469 568.597656 265.742188 C 579.429688 265.035156 589.980469 262.054688 600.355469 259.023438 C 601.796875 258.601562 603.691406 259.058594 604.566406 258.785156 L 605.566406 260.785156 C 602.796875 261.675781 599.144531 263.066406 596.566406 263.78125 C 592.949219 264.785156 589.183594 265.875 585.5625 266.78125 C 583.203125 267.371094 570.027344 269.128906 569.550781 269.792969 C 571.140625 274.660156 569.855469 284.230469 567.558594 288.769531 C 565.140625 293.558594 556.6875 299.023438 551.410156 300.113281 C 547.226562 300.980469 532.832031 300.027344 528.554688 298.765625 C 528.1875 298.65625 527.195312 297.316406 525.894531 296.96875 C 519.953125 295.386719 513.785156 292.460938 507.535156 294.265625 L 528.550781 299.765625 L 528.691406 303.601562 C 530.238281 305.867188 547.800781 304.28125 551.554688 304.761719 C 558.222656 305.484375 565 304.425781 571.558594 303.761719 L 569.832031 307.761719 L 563.679688 308.871094 C 562.476562 310.777344 564.515625 313.074219 564.558594 313.753906 C 565.613281 329.6875 568.539062 343.308594 570.5625 358.730469 C 571.554688 366.277344 571.851562 374.128906 572.558594 381.722656 L 569.132812 381.773438 C 568.003906 381.460938 565.972656 361.75 565.5625 358.730469 C 563.535156 343.792969 562.027344 328.617188 559.5625 313.753906 C 559.363281 312.539062 559.71875 311.035156 559.566406 309.75 L 550.140625 309.738281 C 549.027344 309.914062 549.625 312.613281 549.558594 313.753906 C 548.746094 327.574219 549.625 342.730469 549.558594 356.730469 C 549.558594 357.398438 549.558594 358.0625 549.558594 358.730469 C 549.507812 367.003906 550.121094 376.113281 549.566406 384.25 C 549.375 387.097656 547.089844 385.292969 545.554688 385.714844 L 545.554688 384.71875 C 545.554688 376.082031 545.777344 367.355469 545.554688 358.730469 C 545.523438 357.398438 545.585938 356.066406 545.554688 354.730469 L 545.546875 309.765625 L 535.628906 308.832031 C 535.503906 310.507812 534.816406 312.113281 534.554688 313.75 C 534.152344 316.253906 533.992188 318.921875 533.554688 321.746094 C 533.332031 323.164062 532.820312 324.644531 532.554688 326.742188 C 532.46875 327.390625 532.617188 328.085938 532.554688 328.742188 C 532.4375 329.929688 532.570312 330.621094 532.554688 330.742188 C 532.394531 332.039062 532.703125 333.433594 532.554688 334.738281 L 530.558594 334.730469 C 530.703125 336.617188 529.78125 339.632812 531.554688 340.734375 C 531.28125 343.105469 530.820312 345.386719 530.554688 347.730469 L 526.550781 348.730469 C 526.632812 348.082031 526.472656 347.382812 526.550781 346.730469 C 526.566406 346.621094 527.351562 346.472656 527.554688 344.734375 C 527.664062 343.757812 527.441406 342.714844 527.554688 341.734375 C 529.128906 341.078125 529.128906 337.394531 527.554688 336.738281 C 528.496094 328.664062 529.148438 323.164062 529.554688 314.75 C 529.59375 313.839844 531.195312 312.363281 530.535156 309.464844 C 530.472656 309.179688 526.886719 305.886719 526.082031 305.730469 C 523.300781 305.203125 519.503906 306.117188 516.546875 305.753906 C 516.277344 308.496094 517.242188 311.078125 517.550781 313.75 C 517.738281 315.375 517.425781 317.105469 517.550781 318.746094 C 517.605469 319.484375 518.546875 319.675781 518.550781 319.746094 C 519.292969 329.039062 519.125 339.335938 519.550781 348.730469 C 519.703125 352.042969 519.375 355.417969 519.550781 358.726562 C 516.300781 359.875 512.945312 359.859375 509.550781 359.726562 C 507.785156 359.65625 506.007812 360.183594 504.546875 358.726562 C 503.398438 344.722656 499.332031 330.765625 498.546875 316.746094 C 498.113281 309.003906 498.101562 301.113281 500.539062 293.757812 C 494.378906 299.257812 497.28125 309.421875 496.546875 316.746094 C 495.570312 326.5 487.261719 340.199219 484.601562 350.027344 C 483.117188 351.867188 479.765625 351.863281 477.542969 351.730469 C 474.597656 351.554688 472.335938 350.316406 469.542969 349.730469 C 469.972656 346.550781 469.8125 344.382812 470.542969 340.734375 C 472.378906 331.566406 474.285156 321.707031 476.542969 312.75 C 478.304688 305.757812 480.511719 297.828125 482.542969 290.761719 C 483.117188 288.769531 488.042969 279.25 486.546875 277.773438 C 484.023438 276.734375 480.878906 278.652344 479.542969 278.765625 C 478.210938 278.882812 476.863281 278.722656 475.542969 278.765625 L 475.042969 277.789062 L 474.542969 278.765625 C 469.960938 278.980469 464.746094 279.625 460.539062 279.765625 C 458.542969 279.832031 456.535156 279.714844 454.539062 279.765625 C 445.230469 280.003906 435.847656 279.589844 426.535156 279.765625 C 426.550781 278.769531 426.480469 277.757812 426.535156 276.769531 C 437.660156 276.222656 448.960938 276.378906 460.082031 275.808594 C 480.140625 274.78125 502.140625 273.65625 522.042969 271.761719 C 526.136719 271.371094 535.421875 270.589844 538.847656 269.566406 C 541.726562 268.710938 541.058594 266.679688 541.554688 264.773438 C 542.324219 261.835938 542.878906 257.796875 542.554688 254.78125 L 566.558594 254.78125 Z M 566.558594 254.785156 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fbf6de" d="M 639.574219 235.792969 C 625.085938 248.914062 604.386719 254.304688 585.578125 258.292969 C 579.648438 259.550781 573.660156 261.132812 567.558594 260.78125 C 567.398438 260.042969 566.558594 255.085938 566.558594 254.785156 C 566.558594 250.972656 572.738281 249.871094 574.039062 246.765625 C 575.957031 242.195312 573.410156 236.5 573.558594 231.792969 L 565.574219 234.792969 C 564.425781 232.949219 565.03125 229.023438 564.558594 227.796875 C 566.652344 228.574219 576.308594 225.503906 576.625 224.132812 C 576.507812 220.609375 575.371094 216.902344 574.28125 213.582031 C 573.429688 210.984375 571.640625 206.328125 570.5625 203.808594 C 584.6875 205.195312 630.445312 213.125 638.035156 224.835938 C 640.335938 228.386719 639.507812 231.800781 639.574219 235.792969 Z M 639.574219 235.792969 " fill-opacity="1" fill-rule="nonzero"/><path fill="#07032a" d="M 657.578125 258.78125 C 659.898438 258.859375 662.265625 258.628906 664.578125 258.78125 C 667.546875 263.1875 659.011719 266.082031 657.503906 268.203125 C 656.65625 269.386719 655.820312 273.269531 654.578125 275.773438 L 636.5625 303.246094 C 636.546875 305.550781 640.203125 301.445312 640.574219 300.761719 C 645.023438 299.425781 649.246094 302.214844 652.578125 302.757812 L 652.578125 338.742188 C 652.0625 344.890625 651.941406 345.4375 650.574219 350.734375 L 637.574219 350.734375 C 637.34375 350.066406 636.1875 349.445312 635.652344 347.183594 C 633.304688 337.261719 633.757812 324.074219 632.570312 313.757812 C 630.746094 313.347656 630.609375 314.3125 629.746094 315.421875 C 625.195312 321.277344 621.210938 330.066406 617.433594 336.589844 C 616.261719 337.328125 612.035156 336.320312 610.574219 335.742188 C 608 334.722656 604.914062 330.773438 601.570312 330.746094 L 608.570312 313.753906 C 617.472656 298.855469 623.445312 280.550781 632.058594 265.761719 C 632.910156 264.300781 634.921875 260.496094 636.007812 259.710938 C 638.289062 258.0625 653.542969 258.640625 657.582031 258.78125 Z M 636.570312 304.769531 L 634.578125 304.769531 L 634.578125 305.75 L 636.570312 305.75 Z M 636.570312 304.769531 " fill-opacity="1" fill-rule="nonzero"/><path fill="#07032a" d="M 570.5625 203.808594 C 571.640625 206.328125 573.429688 210.984375 574.28125 213.582031 C 575.371094 216.898438 576.507812 220.609375 576.625 224.132812 C 576.304688 225.503906 566.652344 228.574219 564.558594 227.796875 C 563.460938 224.9375 553.242188 213.367188 550.558594 207.808594 C 547.4375 201.34375 545.171875 193.839844 544.109375 186.769531 L 542.910156 185.890625 C 536.671875 187.9375 535.0625 180.550781 528.554688 179.820312 L 528.054688 177.808594 L 526.5625 179.8125 C 528.761719 164.300781 547.382812 161.210938 556.390625 174.488281 C 559.804688 179.511719 567.828125 197.417969 570.5625 203.804688 Z M 570.5625 203.808594 " fill-opacity="1" fill-rule="nonzero"/><path fill="#e54976" d="M 515.550781 150.835938 C 518.601562 159.722656 519.441406 184.703125 518.578125 194.339844 C 518.382812 196.476562 517.601562 198.039062 516.550781 199.8125 C 515.558594 199.738281 514.542969 199.867188 513.550781 199.8125 C 510.734375 199.652344 507.847656 200.921875 506.550781 197.8125 C 506.472656 193.160156 506.582031 188.472656 506.550781 183.820312 C 506.488281 175.519531 507.007812 167.070312 506.050781 158.824219 L 504.546875 183.820312 L 491.546875 183.820312 C 491.652344 183.191406 491.390625 182.34375 491.546875 181.820312 C 492.472656 178.710938 491.570312 179.757812 491.546875 178.824219 C 491.289062 168.5625 491.382812 158.105469 491.546875 147.839844 C 491.597656 144.773438 492.492188 142.09375 492.546875 138.84375 C 500.53125 140.734375 512.449219 141.804688 515.550781 150.835938 Z M 515.550781 150.835938 " fill-opacity="1" fill-rule="nonzero"/><path fill="#7bb9a7" d="M 701.585938 247.785156 C 696.035156 249.195312 692.179688 250.925781 685.582031 251.785156 C 687.8125 230.359375 689.34375 208.761719 694.582031 187.816406 C 696.167969 186.707031 697.433594 185.566406 699.585938 185.820312 C 699.457031 188.03125 698.957031 190.019531 698.660156 192.191406 C 700.335938 198.558594 712.128906 184.894531 713.585938 182.820312 C 713.527344 189.726562 709.796875 195.210938 708.09375 201.820312 C 704.214844 216.902344 702.882812 232.304688 701.585938 247.785156 Z M 701.585938 247.785156 " fill-opacity="1" fill-rule="nonzero"/><path fill="#07032a" d="M 685.582031 251.785156 C 684.835938 251.878906 683.769531 252.691406 682.582031 252.785156 L 683.578125 234.796875 C 676.230469 237.71875 665.363281 238.511719 659.082031 232.78125 C 657.277344 231.136719 656.851562 229.058594 656.578125 228.792969 L 658.492188 228.726562 L 660.578125 215.800781 C 686.039062 224.164062 680.089844 198.011719 694.582031 187.8125 C 689.34375 208.757812 687.8125 230.355469 685.582031 251.78125 Z M 685.582031 251.785156 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f5b499" d="M 701.585938 247.785156 C 702.886719 247.457031 705.082031 247.96875 706.578125 247.796875 L 708.582031 260.777344 C 705.765625 259.761719 702.332031 261.625 700.585938 261.78125 C 695.796875 262.199219 688.421875 262.125 683.582031 261.78125 C 677.824219 261.367188 670.546875 259.171875 664.578125 258.78125 C 662.265625 258.628906 659.898438 258.859375 657.578125 258.78125 C 662.0625 248.457031 674.027344 253.445312 682.582031 252.785156 C 683.769531 252.691406 684.835938 251.878906 685.582031 251.785156 C 692.179688 250.925781 696.035156 249.195312 701.585938 247.785156 Z M 701.585938 247.785156 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f5b499" d="M 631.574219 197.8125 C 639.253906 198.019531 640.386719 203.214844 645.636719 207.246094 C 648.96875 209.796875 656.710938 214.535156 660.578125 215.804688 L 658.492188 228.730469 L 656.578125 228.796875 C 652.667969 225.007812 641.632812 214.796875 637.5 212.378906 C 636.511719 211.800781 626.21875 209.082031 627.570312 207.820312 L 631.15625 206.894531 C 633.523438 201.046875 627.8125 202.085938 625.558594 200.28125 C 624.378906 199.335938 624.835938 198.257812 624.570312 197.8125 C 627.089844 199.386719 630.679688 197.789062 631.574219 197.8125 Z M 631.574219 197.8125 " fill-opacity="1" fill-rule="nonzero"/><path fill="#75458c" d="M 638.574219 242.789062 C 638.71875 239.207031 638.046875 241.285156 636.582031 242.296875 C 627.449219 248.582031 615.101562 255.4375 604.566406 258.78125 C 603.691406 259.058594 601.796875 258.597656 600.355469 259.019531 C 589.980469 262.050781 579.433594 265.03125 568.597656 265.734375 C 568.921875 263.855469 567.894531 262.304688 567.558594 260.777344 C 573.660156 261.128906 579.648438 259.542969 585.578125 258.289062 C 604.386719 254.300781 625.09375 248.910156 639.574219 235.789062 C 639.625 238.824219 640.855469 238.835938 638.574219 242.785156 Z M 638.574219 242.789062 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f5b499" d="M 550.558594 207.808594 C 548.96875 207.980469 547.054688 207.558594 545.554688 207.808594 L 544.617188 202.242188 C 541.347656 201.214844 537.863281 202.09375 534.554688 201.8125 C 530.941406 194.855469 527.742188 187.933594 528.554688 179.820312 C 535.058594 180.550781 536.671875 187.941406 542.910156 185.890625 L 544.109375 186.769531 C 545.171875 193.839844 547.4375 201.34375 550.558594 207.808594 Z M 550.558594 207.808594 " fill-opacity="1" fill-rule="nonzero"/><path fill="#4d3670" d="M 596.566406 263.777344 C 596.460938 270.113281 597.078125 276.472656 597.566406 282.769531 C 593.734375 281.128906 590.433594 282.011719 586.5625 282.769531 C 585.964844 277.425781 585.089844 272.214844 585.5625 266.777344 C 589.183594 265.871094 592.949219 264.78125 596.566406 263.777344 Z M 596.566406 263.777344 " fill-opacity="1" fill-rule="nonzero"/><path fill="#6b338c" d="M 597.566406 282.769531 C 597.984375 288.128906 598.234375 293.402344 598.566406 298.761719 C 595.148438 300.046875 591.988281 300.050781 588.5625 298.761719 C 587.925781 293.429688 587.164062 288.09375 586.5625 282.769531 C 590.433594 282.011719 593.734375 281.128906 597.566406 282.769531 Z M 597.566406 282.769531 " fill-opacity="1" fill-rule="nonzero"/><path fill="#75458c" d="M 598.566406 298.761719 C 598.863281 303.539062 599.539062 308.597656 599.566406 313.753906 C 599.566406 314.085938 599.566406 314.417969 599.566406 314.753906 C 596.515625 314.507812 593.652344 313.894531 590.566406 313.753906 C 589.953125 308.777344 589.160156 303.738281 588.5625 298.761719 C 591.988281 300.050781 595.148438 300.046875 598.566406 298.761719 Z M 598.566406 298.761719 " fill-opacity="1" fill-rule="nonzero"/><path fill="#17092e" d="M 638.574219 242.789062 C 632.898438 252.601562 615.714844 257.515625 605.566406 260.78125 L 604.566406 258.78125 C 615.101562 255.4375 627.449219 248.582031 636.582031 242.296875 C 638.046875 241.285156 638.71875 239.207031 638.574219 242.789062 Z M 638.574219 242.789062 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 608.566406 313.753906 L 601.566406 330.746094 L 600.566406 330.746094 C 600.375 327.800781 600.839844 324.660156 600.566406 321.75 C 600.523438 321.296875 600.03125 320.855469 599.566406 320.75 C 599.378906 318.859375 599.585938 316.707031 599.566406 314.753906 C 599.566406 314.417969 599.566406 314.085938 599.566406 313.753906 Z M 608.566406 313.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#75458c" d="M 631.574219 197.8125 C 630.679688 197.789062 627.089844 199.386719 624.570312 197.8125 C 624.292969 197.351562 624.316406 196.328125 623.625 195.304688 C 621.699219 192.445312 615.59375 189.628906 616.078125 185.808594 Z M 631.574219 197.8125 " fill-opacity="1" fill-rule="nonzero"/><path fill="#1b0141" d="M 598.570312 68.875 C 598.390625 67.070312 598.035156 61.273438 601.050781 61.886719 C 604.082031 62.503906 602.359375 69.597656 598.570312 68.875 Z M 598.570312 68.875 " fill-opacity="1" fill-rule="nonzero"/><path fill="#6b338c" d="M 396.527344 221.800781 C 396.746094 221.878906 397.933594 224.300781 399.773438 225.039062 C 403.363281 226.484375 406.992188 226.03125 410.296875 224.109375 C 411.964844 223.136719 411.414062 221.863281 411.53125 221.800781 C 412 221.546875 416.820312 221.726562 418.015625 221.816406 C 429.960938 222.730469 432.398438 228.058594 435.246094 238.582031 C 438.089844 249.105469 443.839844 267.527344 426.53125 265.769531 L 426.546875 272.769531 C 429.414062 271.25 432.480469 271.804688 435.539062 271.769531 L 435.539062 273.761719 C 435.539062 273.761719 426.546875 273.765625 426.546875 273.765625 C 426.488281 274.757812 426.59375 275.773438 426.539062 276.769531 C 426.484375 277.761719 426.554688 278.769531 426.539062 279.765625 C 426.484375 283.179688 425.574219 299.289062 426.539062 300.757812 C 425.925781 301.398438 424.980469 302.027344 424.539062 302.753906 C 412.671875 306.328125 396.523438 307.125 384.269531 304.519531 C 382.214844 304.082031 380.234375 302.09375 378.53125 301.753906 C 378.25 301.703125 377.820312 301.722656 377.527344 301.753906 C 376.515625 294.488281 378.703125 286.722656 378.53125 279.765625 C 378.503906 278.765625 378.574219 277.761719 378.535156 276.769531 C 375.875 276.722656 373.1875 276.828125 370.527344 276.769531 C 370.753906 272.269531 362.429688 275.167969 359.527344 272.769531 L 378.535156 271.773438 L 378.515625 260.777344 C 368.386719 271.691406 352.230469 263.351562 360.109375 248.867188 C 366.054688 237.933594 375 225.527344 387.53125 222.796875 C 387.84375 222.730469 388.269531 221.832031 388.53125 221.796875 C 389.734375 221.625 395.851562 221.542969 396.53125 221.796875 Z M 396.527344 221.800781 " fill-opacity="1" fill-rule="nonzero"/><path fill="#07032a" d="M 463.542969 183.820312 C 464.207031 183.808594 464.875 183.828125 465.542969 183.820312 C 469.199219 183.777344 472.882812 183.832031 476.542969 183.820312 C 481.53125 183.804688 486.558594 183.820312 491.546875 183.820312 L 506.550781 183.820312 C 506.582031 188.472656 506.472656 193.160156 506.550781 197.8125 C 506.597656 200.796875 506.507812 203.816406 506.558594 206.804688 C 506.929688 207.214844 509.589844 205.894531 510.550781 205.808594 C 510.878906 205.78125 511.214844 205.828125 511.550781 205.808594 L 511.550781 206.808594 C 506.242188 210.730469 505.894531 213.074219 506.550781 219.800781 L 453.539062 219.800781 L 453.539062 198.8125 C 453.539062 198.480469 453.539062 198.144531 453.539062 197.8125 C 453.542969 197.144531 453.53125 196.480469 453.539062 195.8125 C 453.550781 194.8125 453.515625 193.816406 453.539062 192.816406 C 453.578125 191.148438 453.5 189.484375 453.539062 187.816406 C 453.570312 186.484375 453.5 185.144531 453.535156 183.816406 C 456.859375 183.777344 460.21875 183.878906 463.542969 183.820312 Z M 477.675781 203.671875 C 479.492188 206.574219 485.859375 202.609375 483.101562 198.753906 C 480.570312 195.207031 475.367188 199.976562 477.675781 203.671875 Z M 477.675781 203.671875 " fill-opacity="1" fill-rule="nonzero"/><path fill="#7bb9a7" d="M 550.558594 207.808594 C 553.242188 213.367188 563.460938 224.9375 564.558594 227.796875 C 565.03125 229.023438 564.425781 232.949219 565.574219 234.792969 L 573.558594 231.792969 C 573.410156 236.5 575.957031 242.195312 574.039062 246.765625 C 572.742188 249.871094 566.558594 250.972656 566.558594 254.785156 L 542.554688 254.785156 C 542.152344 251.027344 539.097656 246.058594 539.546875 241.789062 C 539.15625 241.296875 537.4375 243.746094 536.554688 243.789062 C 535.84375 243.824219 533.679688 242.132812 532.554688 241.789062 C 524.660156 236.835938 526.066406 232.71875 528.554688 224.796875 C 531.398438 215.746094 535.625 209.472656 545.554688 207.808594 C 547.058594 207.558594 548.96875 207.980469 550.558594 207.808594 Z M 550.558594 207.808594 " fill-opacity="1" fill-rule="nonzero"/><path fill="#7d4399" d="M 527.554688 224.800781 C 526.148438 231.640625 521.175781 238.074219 525.550781 244.789062 C 524.761719 245.914062 524.988281 248.113281 523.910156 248.878906 C 520.882812 251.03125 508.5 249.292969 504.207031 249.628906 C 502.652344 249.101562 502.199219 247.101562 501.542969 245.789062 C 498.515625 239.6875 496.953125 231.308594 494.546875 224.804688 L 527.546875 224.804688 Z M 527.554688 224.800781 " fill-opacity="1" fill-rule="nonzero"/><path fill="#75458c" d="M 541.554688 264.777344 C 541.058594 266.6875 541.722656 268.714844 538.847656 269.570312 C 535.421875 270.59375 526.136719 271.375 522.042969 271.765625 C 502.144531 273.660156 480.144531 274.789062 460.082031 275.8125 C 448.960938 276.386719 437.660156 276.226562 426.535156 276.773438 C 426.589844 275.777344 426.484375 274.761719 426.542969 273.769531 L 435.539062 273.769531 C 435.539062 273.769531 435.535156 271.773438 435.535156 271.773438 C 470.867188 271.414062 506.398438 267.777344 541.554688 264.777344 Z M 541.554688 264.777344 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f5b499" d="M 532.554688 241.789062 C 533.679688 242.132812 535.84375 243.824219 536.554688 243.789062 C 536.695312 249.152344 533.242188 259.359375 527.007812 259.742188 C 520.6875 257.511719 503.09375 257.847656 498.207031 254.867188 C 495.351562 253.121094 495.316406 243.664062 501.546875 245.789062 C 502.199219 247.097656 502.65625 249.097656 504.210938 249.628906 C 508.503906 249.292969 520.886719 251.03125 523.914062 248.878906 C 524.996094 248.113281 524.765625 245.917969 525.558594 244.789062 C 525.925781 244.257812 528.914062 241.015625 529.171875 240.941406 C 530.339844 241.015625 531.449219 241.453125 532.558594 241.789062 Z M 532.554688 241.789062 " fill-opacity="1" fill-rule="nonzero"/><path fill="#e54976" d="M 477.542969 245.789062 C 477.582031 250.777344 476.78125 255.210938 476.398438 260.128906 L 475.613281 261.34375 L 467.710938 260.601562 C 467.523438 255.96875 465.78125 250.195312 465.542969 245.789062 Z M 477.542969 245.789062 " fill-opacity="1" fill-rule="nonzero"/><path fill="#9e6ebb" d="M 398.527344 219.800781 C 402.191406 219.425781 406.964844 219.863281 410.53125 220.800781 C 410.964844 220.914062 411.332031 221.390625 411.53125 221.800781 C 411.414062 221.863281 411.964844 223.136719 410.296875 224.109375 C 406.992188 226.03125 403.363281 226.484375 399.773438 225.039062 C 397.933594 224.300781 396.742188 221.882812 396.527344 221.800781 L 396.527344 219.800781 C 397.1875 219.710938 397.878906 219.867188 398.527344 219.800781 Z M 398.527344 219.800781 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f5b499" d="M 410.53125 220.800781 C 406.964844 219.863281 402.191406 219.425781 398.527344 219.800781 L 398.527344 215.804688 C 402.371094 216 406.132812 215.757812 409.53125 213.804688 Z M 410.53125 220.800781 " fill-opacity="1" fill-rule="nonzero"/><path fill="#1e0442" d="M 477.542969 245.789062 L 465.542969 245.789062 C 465.292969 241.230469 474.289062 240.769531 477.121094 242.71875 C 479.578125 244.402344 477.539062 245.605469 477.542969 245.789062 Z M 477.542969 245.789062 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f9848c" d="M 506.550781 197.8125 C 507.847656 200.921875 510.734375 199.652344 513.550781 199.8125 L 510.550781 205.808594 C 509.589844 205.894531 506.925781 207.214844 506.558594 206.804688 C 506.511719 203.816406 506.597656 200.796875 506.550781 197.8125 Z M 506.550781 197.8125 " fill-opacity="1" fill-rule="nonzero"/><path fill="#e3d8d1" d="M 532.554688 241.789062 C 531.445312 241.453125 530.335938 241.015625 529.164062 240.941406 C 528.910156 241.011719 525.921875 244.257812 525.550781 244.789062 C 521.175781 238.074219 526.148438 231.640625 527.554688 224.800781 L 528.554688 224.800781 C 526.066406 232.71875 524.660156 236.835938 532.554688 241.789062 Z M 532.554688 241.789062 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f9848c" d="M 511.550781 206.808594 L 511.550781 205.808594 L 512.53125 206.308594 Z M 511.550781 206.808594 " fill-opacity="1" fill-rule="nonzero"/><path fill="#7d4399" d="M 278.507812 229.796875 C 281.195312 231.007812 281.4375 224.800781 283.007812 224.800781 L 315.511719 224.800781 C 314.710938 228.859375 309.113281 250.78125 306.835938 251.648438 C 305.925781 251.996094 304.539062 251.84375 303.511719 251.785156 C 300.710938 251.621094 299.894531 250.203125 297.949219 249.835938 C 295.84375 249.441406 293.355469 250.152344 291.507812 249.785156 C 290.316406 249.554688 285.875 246.980469 285.058594 245.738281 C 283.671875 240.027344 280.792969 235.078125 278.507812 229.796875 Z M 278.507812 229.796875 " fill-opacity="1" fill-rule="nonzero"/><path fill="#75458c" d="M 359.523438 272.773438 C 362.425781 275.171875 370.75 272.273438 370.523438 276.773438 C 340.957031 276.15625 309.957031 274.441406 280.507812 271.773438 C 277.210938 271.476562 274.082031 269.464844 270.511719 271.78125 C 270.34375 269.386719 269.386719 267.242188 269.503906 264.777344 C 271.296875 265.554688 273.109375 266.4375 275.085938 266.699219 C 303.023438 270.378906 331.582031 269.289062 359.523438 272.773438 Z M 359.523438 272.773438 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f5b499" d="M 358.523438 201.8125 C 357.742188 202.042969 356.816406 203.167969 355.523438 202.824219 L 357.46875 203.894531 L 356.519531 206.8125 C 356.164062 206.914062 353.371094 208.394531 352.519531 208.8125 C 350.863281 209.160156 350.289062 208.058594 349.519531 206.8125 C 349.089844 203.535156 348.015625 199.824219 347.519531 195.816406 C 353.707031 194.355469 352.933594 202.363281 358.523438 201.816406 Z M 358.523438 201.8125 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f5b499" d="M 303.511719 251.785156 C 305.164062 257.546875 297.453125 258.308594 293.507812 259.78125 C 293.777344 256.128906 293.644531 252.855469 291.507812 249.785156 C 293.359375 250.152344 295.84375 249.441406 297.949219 249.835938 C 299.894531 250.203125 300.707031 251.621094 303.511719 251.785156 Z M 303.511719 251.785156 " fill-opacity="1" fill-rule="nonzero"/><path fill="#904f9c" d="M 259.503906 207.808594 C 261 208.347656 261.496094 209.214844 261.503906 210.804688 C 257.730469 210.324219 248.148438 209.597656 244.5 209.804688 C 243.910156 207.609375 247.355469 206.152344 247.5 205.808594 C 250.765625 206.902344 256.683594 206.789062 259.503906 207.808594 Z M 259.503906 207.808594 " fill-opacity="1" fill-rule="nonzero"/><path fill="#17092e" d="M 356.519531 206.808594 C 364.507812 204.628906 353.113281 214.921875 350.519531 214.804688 C 350.4375 213.957031 349.726562 212.339844 349.519531 210.804688 C 349.898438 210.550781 350.183594 210.003906 350.519531 209.804688 C 351.074219 209.480469 351.902344 209.109375 352.519531 208.808594 C 353.371094 208.390625 356.164062 206.90625 356.519531 206.808594 Z M 356.519531 206.808594 " fill-opacity="1" fill-rule="nonzero"/><path fill="#9e6ebb" d="M 387.527344 222.800781 L 388.527344 221.800781 C 388.265625 221.835938 387.839844 222.734375 387.527344 222.800781 Z M 387.527344 222.800781 " fill-opacity="1" fill-rule="nonzero"/><path fill="#6b338c" d="M 308.511719 313.753906 C 306.363281 328.058594 303.101562 343.34375 300.511719 357.730469 C 299.605469 362.753906 298.820312 367.789062 297.511719 372.722656 C 296.648438 372.46875 282.269531 372.472656 281.507812 372.722656 C 281.394531 370.078125 281.699219 367.359375 281.507812 364.726562 C 281.410156 363.40625 281.613281 362.046875 281.507812 360.730469 L 288.511719 303.753906 C 281.199219 303.902344 273.816406 303.5625 266.503906 303.753906 L 248.5 301.753906 C 247.839844 301.722656 247.164062 301.796875 246.5 301.753906 C 241.894531 300.1875 233.777344 293.359375 232.5 288.761719 C 232.152344 287.519531 232.714844 285.265625 232.5 283.765625 L 271.507812 283.765625 C 271.414062 282.125 271.65625 280.40625 271.503906 278.765625 C 281.832031 278.75 308.851562 277.226562 310.535156 291.238281 C 311.316406 297.75 309.515625 307.0625 308.511719 313.75 Z M 308.511719 313.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#8d4e9c" d="M 210.492188 263.777344 C 213.644531 264.699219 230.378906 267.382812 231.355469 268.917969 C 231.09375 274.09375 231.777344 278.820312 232.5 283.769531 C 232.714844 285.269531 232.152344 287.523438 232.5 288.765625 C 223.789062 287.699219 214.097656 290.691406 213.496094 300.761719 C 213.457031 301.414062 213.445312 302.082031 213.507812 302.726562 C 215.582031 302.480469 217.628906 303.570312 219.496094 303.757812 C 220.261719 308.222656 223.984375 306.90625 227.082031 308.6875 C 228.484375 310.601562 226.707031 312.402344 226.496094 313.753906 L 204.492188 313.753906 C 205.261719 309.613281 204.964844 304.707031 205.492188 300.761719 C 206.238281 295.195312 207.78125 289.398438 208.492188 283.769531 C 209.328125 277.175781 209.523438 270.371094 210.492188 263.777344 Z M 210.492188 263.777344 " fill-opacity="1" fill-rule="nonzero"/><path fill="#904f9c" d="M 280.507812 274.773438 C 292.464844 276.386719 303.535156 276.925781 315.511719 277.773438 C 316.480469 288.085938 317.253906 298.472656 318.515625 308.757812 C 318.554688 309.085938 318.472656 309.425781 318.515625 309.753906 C 318.597656 310.40625 318.429688 311.105469 318.515625 311.753906 L 318.523438 313.753906 L 308.511719 313.753906 C 309.515625 307.066406 311.316406 297.753906 310.535156 291.242188 C 308.851562 277.234375 281.828125 278.753906 271.503906 278.769531 C 271.335938 276.90625 270.082031 274.878906 270.511719 272.773438 C 273.675781 274.566406 277.097656 274.316406 280.507812 274.773438 Z M 280.507812 274.773438 " fill-opacity="1" fill-rule="nonzero"/><path fill="#17092e" d="M 370.523438 276.773438 C 373.183594 276.828125 375.871094 276.722656 378.53125 276.773438 C 378.566406 277.765625 378.5 278.769531 378.523438 279.769531 L 360.523438 279.769531 C 359.523438 279.769531 358.523438 279.753906 357.519531 279.769531 C 352.726562 279.851562 347.132812 279.296875 342.519531 279.769531 C 340.574219 279.613281 338.417969 280 336.515625 279.769531 C 332.691406 279.3125 329.59375 279.015625 325.515625 278.769531 C 321.980469 278.558594 318.714844 277.996094 315.511719 277.773438 C 303.535156 276.925781 292.464844 276.386719 280.507812 274.773438 L 280.507812 271.773438 C 309.957031 274.441406 340.957031 276.15625 370.523438 276.773438 Z M 370.523438 276.773438 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 148.484375 320.75 C 148.5625 322.148438 155.707031 340.113281 156.585938 341.152344 C 157.808594 342.609375 158.636719 342.824219 160.484375 342.738281 C 160.007812 345.464844 161.492188 348.175781 161.484375 350.734375 C 161.476562 353.769531 160.007812 356.933594 160.484375 359.730469 L 139.480469 360.730469 C 138.9375 359.566406 138.464844 357.042969 138.480469 355.730469 C 138.488281 354.917969 139.269531 348.078125 139.480469 347.734375 C 139.550781 347.625 140.972656 348.042969 141.304688 347.59375 C 144.328125 343.507812 145.476562 326.414062 146.480469 320.75 Z M 148.484375 320.75 " fill-opacity="1" fill-rule="nonzero"/><path fill="#e3d8d1" d="M 169.488281 339.738281 C 169.78125 341.9375 169.636719 345.746094 170.488281 347.734375 C 169.269531 347.890625 169.339844 349.835938 169.488281 350.734375 L 163.484375 352.734375 C 162.875 352.011719 162.179688 351.367188 161.484375 350.734375 C 161.492188 348.175781 160.007812 345.464844 160.484375 342.738281 C 163.210938 342.605469 166.457031 339.824219 169.488281 339.738281 Z M 169.488281 339.738281 " fill-opacity="1" fill-rule="nonzero"/><path fill="#e54976" d="M 110.476562 177.824219 C 111.265625 177.988281 112.460938 179.679688 114.042969 179.851562 C 116.613281 180.128906 117.613281 178.207031 119.476562 178.824219 C 120.613281 183.863281 120.730469 188.917969 121.773438 194.019531 C 122.308594 196.632812 127.519531 205.878906 121.976562 205.851562 C 119.71875 205.835938 118.523438 202.851562 117.605469 201.183594 C 113.898438 194.449219 112.105469 184.886719 108.480469 177.820312 C 109.132812 177.851562 109.921875 177.703125 110.480469 177.820312 Z M 110.476562 177.824219 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f5b499" d="M 105.6875 222.605469 C 106.078125 223.261719 108.503906 223.300781 108.476562 224.789062 L 101.472656 224.789062 C 101.472656 224.789062 104.511719 222.21875 104.511719 222.21875 C 103.023438 219.25 103.410156 216.808594 104.488281 213.8125 C 106.960938 215.191406 104.5 220.601562 105.6875 222.605469 Z M 105.6875 222.605469 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f5b499" d="M 99.972656 224.800781 C 100.625 225.132812 100.625 225.464844 99.972656 225.796875 Z M 99.972656 224.800781 " fill-opacity="1" fill-rule="nonzero"/><path fill="#9e6ebb" d="M 320.152344 194.972656 C 324.308594 194.214844 326.476562 201.476562 322.878906 202.6875 C 315.847656 205.054688 316.289062 195.675781 320.152344 194.972656 Z M 320.152344 194.972656 " fill-opacity="1" fill-rule="nonzero"/><path fill="#9e6ebb" d="M 338.519531 180.820312 C 340.511719 180.90625 342.527344 180.765625 344.519531 180.820312 C 343.476562 182.480469 340.722656 181.816406 339.03125 181.835938 C 332.328125 181.921875 324.5625 182.296875 317.988281 181.828125 C 316.878906 181.75 316.257812 182.300781 316.507812 180.816406 C 323.609375 180.617188 331.4375 180.53125 338.515625 180.816406 Z M 338.519531 180.820312 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fbf6de" d="M 349.519531 206.808594 C 350.289062 208.054688 350.863281 209.15625 352.519531 208.808594 C 351.902344 209.109375 351.074219 209.480469 350.519531 209.804688 L 349.519531 209.804688 C 349.378906 208.859375 349.644531 207.765625 349.519531 206.808594 Z M 349.519531 206.808594 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f5b499" d="M 349.519531 210.804688 C 349.472656 210.476562 349.570312 210.132812 349.519531 209.804688 L 350.519531 209.804688 C 350.183594 210.003906 349.898438 210.550781 349.519531 210.804688 Z M 349.519531 210.804688 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fbf6de" d="M 133.480469 347.734375 L 133.980469 348.714844 L 134.480469 347.734375 L 139.480469 347.734375 C 139.269531 348.078125 138.488281 354.917969 138.480469 355.730469 C 135.960938 356 132.878906 355.347656 130.480469 355.730469 C 130.316406 353.09375 130.710938 350.359375 130.480469 347.734375 Z M 133.480469 347.734375 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 133.480469 347.734375 L 134.480469 347.734375 L 133.980469 348.71875 Z M 133.480469 347.734375 " fill-opacity="1" fill-rule="nonzero"/><path fill="#7d4399" d="M 202.492188 314.753906 L 202.492188 315.753906 C 202.558594 316.261719 203.484375 316.679688 203.492188 316.75 C 204.394531 324.171875 200.640625 339.558594 199.492188 347.734375 C 199.316406 348.972656 198.765625 350.871094 198.492188 352.734375 C 198.441406 353.058594 198.539062 353.40625 198.492188 353.734375 C 197.234375 357.484375 196.363281 356.980469 192.488281 356.734375 L 192.488281 352.734375 C 193.320312 339.769531 193.535156 326.671875 194.492188 313.753906 C 197.496094 313.761719 199.964844 314.753906 202.492188 314.753906 Z M 202.492188 314.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#17092e" d="M 177.488281 360.730469 C 178.183594 362.074219 177.910156 363.59375 179.449219 365.257812 C 181.703125 367.6875 186.363281 367.34375 185.488281 371.71875 C 175.296875 373.542969 173.144531 372.828125 166.980469 364.730469 C 165.257812 366.507812 168.527344 372.5625 164.503906 371.71875 C 164.34375 368.179688 160.96875 362.570312 160.488281 359.730469 C 160.007812 356.890625 161.480469 353.769531 161.488281 350.734375 C 162.183594 351.367188 162.882812 352.011719 163.488281 352.734375 C 164.738281 354.207031 165.925781 356.023438 167.207031 357.453125 C 167.792969 358.105469 167.144531 359.378906 169.472656 358.726562 C 171.382812 355.160156 169.90625 353.355469 169.488281 350.734375 C 169.339844 349.835938 169.269531 347.890625 170.488281 347.734375 C 171.714844 350.613281 175.652344 357.183594 177.488281 360.730469 Z M 177.488281 360.730469 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fbf6de" d="M 491.546875 147.839844 C 491.382812 158.105469 491.289062 168.5625 491.546875 178.824219 L 491.546875 181.820312 C 491.390625 182.34375 491.652344 183.191406 491.546875 183.820312 C 486.558594 183.820312 481.53125 183.804688 476.542969 183.820312 C 476.476562 171.835938 476.976562 159.796875 477.542969 147.839844 C 481.835938 149.90625 487.554688 151.414062 491.546875 147.839844 Z M 491.546875 147.839844 " fill-opacity="1" fill-rule="nonzero"/><path fill="#c03666" d="M 463.542969 183.820312 C 463.761719 176.347656 463.242188 168.796875 463.542969 161.324219 C 463.59375 159.972656 462.707031 157.164062 465.03125 157.828125 L 465.542969 183.820312 C 464.875 183.828125 464.207031 183.808594 463.542969 183.820312 Z M 463.542969 183.820312 " fill-opacity="1" fill-rule="nonzero"/><path fill="#8d4e9c" d="M 252.5 195.8125 C 252.828125 195.800781 253.191406 195.867188 253.503906 195.8125 L 253.007812 196.796875 Z M 252.5 195.8125 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 204.492188 313.753906 L 226.496094 313.753906 C 224.25 328.484375 222.265625 344.097656 220.496094 358.730469 L 198.492188 360.730469 C 198.8125 358.582031 198.179688 355.890625 198.492188 353.734375 C 198.539062 353.40625 198.441406 353.058594 198.492188 352.734375 C 200.113281 351.878906 199.433594 349.335938 199.492188 347.734375 C 200.640625 339.558594 204.394531 324.171875 203.492188 316.75 L 202.492188 315.753906 L 202.492188 314.753906 C 202.660156 314.753906 203.613281 313.757812 204.492188 313.753906 Z M 204.492188 313.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#e54976" d="M 453.539062 192.816406 C 453.515625 193.816406 453.550781 194.8125 453.539062 195.8125 L 451.542969 195.8125 C 451.542969 195.8125 451.535156 193.320312 451.535156 193.320312 Z M 453.539062 192.816406 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 433.535156 313.753906 C 444.527344 312.605469 457.195312 314.941406 467.542969 314.753906 C 469.984375 318.992188 466.828125 318.511719 466.578125 319.453125 C 465.871094 322.085938 462.710938 342.84375 463.550781 343.734375 L 470.546875 340.738281 C 469.816406 344.386719 469.976562 346.554688 469.546875 349.734375 C 469.066406 353.28125 469.179688 353.484375 467.546875 356.730469 L 421.535156 354.730469 C 420.121094 356.1875 424.765625 362.558594 420.539062 361.730469 C 419.46875 348.523438 418.875 333.671875 416.535156 320.75 L 416.535156 318.75 C 416.988281 317.894531 417.847656 318.011719 418.535156 317.75 C 420.136719 317.691406 422.683594 318.371094 423.539062 316.75 C 423.847656 316.664062 424.230469 316.835938 424.539062 316.75 C 424.871094 316.660156 425.257812 315.816406 425.539062 315.753906 C 428.082031 315.1875 431.351562 313.980469 433.539062 313.753906 Z M 433.535156 313.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 498.546875 316.75 C 499.332031 330.769531 503.398438 344.726562 504.546875 358.730469 L 477.542969 357.730469 C 477.417969 355.75 477.632812 353.722656 477.542969 351.734375 C 479.765625 351.867188 483.117188 351.871094 484.601562 350.03125 C 487.261719 340.203125 495.570312 326.503906 496.546875 316.75 Z M 498.546875 316.75 " fill-opacity="1" fill-rule="nonzero"/><path fill="#c03666" d="M 415.53125 353.734375 C 416.066406 359.722656 416.496094 365.769531 417.019531 371.75 C 417.25 374.378906 415.332031 373.972656 419.53125 373.722656 C 419.363281 373.742188 418.902344 374.617188 418.085938 374.597656 C 413.648438 374.484375 408.347656 372.902344 403.53125 373.722656 C 403.53125 367.070312 403.53125 360.382812 403.53125 353.734375 Z M 415.53125 353.734375 " fill-opacity="1" fill-rule="nonzero"/><path fill="#17092e" d="M 529.554688 352.734375 L 529.554688 350.742188 C 529.554688 350.742188 527.558594 350.742188 527.558594 350.742188 L 527.53125 356.101562 L 529.554688 356.730469 C 529.472656 357.382812 529.632812 358.082031 529.554688 358.730469 C 529.359375 360.355469 529.753906 362.109375 529.554688 363.726562 C 529.050781 367.84375 527.769531 379.710938 524.550781 381.71875 L 522.550781 381.71875 C 522.46875 380.726562 522.613281 379.714844 522.550781 378.71875 C 524.660156 372.582031 523.714844 365.21875 524.550781 358.730469 C 524.953125 355.625 526.1875 351.71875 526.554688 348.734375 L 530.554688 347.734375 C 530.324219 349.769531 529.679688 351.613281 529.554688 352.734375 Z M 529.554688 352.734375 " fill-opacity="1" fill-rule="nonzero"/><path fill="#17092e" d="M 522.550781 378.71875 C 522.230469 379.648438 521.082031 380.785156 520.550781 381.71875 C 520.476562 380.734375 520.664062 379.699219 520.550781 378.71875 C 520.476562 378.070312 520.609375 377.375 520.542969 376.722656 C 520.109375 376.324219 518.164062 378.367188 517.550781 378.71875 C 510.851562 382.554688 503.195312 384.824219 496.023438 380.738281 C 494.722656 379.449219 495.816406 379.125 496.597656 378.269531 C 497.179688 377.632812 509.773438 371.71875 510.550781 371.722656 C 510.710938 371.722656 511.566406 372.859375 513.726562 372.578125 C 515.914062 372.285156 518.492188 370.621094 520.550781 369.726562 C 520.957031 372.15625 522.246094 373.867188 522.550781 378.71875 Z M 522.550781 378.71875 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f5b499" d="M 477.542969 351.734375 C 477.632812 353.722656 477.417969 355.75 477.542969 357.730469 C 477.59375 358.523438 477.363281 360.488281 477.542969 360.730469 C 472.84375 366.425781 462.695312 368.753906 455.539062 368.726562 C 455.652344 368.636719 455.21875 367.230469 455.710938 366.925781 C 461.441406 363.378906 463.941406 363.886719 467.542969 356.730469 C 469.175781 353.484375 469.0625 353.28125 469.542969 349.734375 C 472.335938 350.320312 474.597656 351.558594 477.542969 351.734375 Z M 477.542969 351.734375 " fill-opacity="1" fill-rule="nonzero"/><path fill="#17092e" d="M 477.542969 360.730469 C 477.605469 360.816406 479.296875 360.332031 479.578125 361.382812 C 482.421875 372.148438 458.453125 375.929688 452.546875 370.210938 C 451.929688 367.53125 454.898438 369.214844 455.539062 368.726562 C 462.695312 368.753906 472.84375 366.425781 477.542969 360.730469 Z M 477.542969 360.730469 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f5b499" d="M 519.550781 358.730469 C 519.75 362.511719 519.929688 365.972656 520.550781 369.726562 C 518.492188 370.621094 515.914062 372.285156 513.726562 372.578125 C 511.566406 372.863281 510.710938 371.722656 510.550781 371.722656 L 509.550781 359.730469 C 512.945312 359.863281 516.300781 359.878906 519.550781 358.730469 Z M 519.550781 358.730469 " fill-opacity="1" fill-rule="nonzero"/><path fill="#c03666" d="M 545.554688 358.730469 C 545.777344 367.355469 545.554688 376.082031 545.554688 384.71875 C 542.925781 381.355469 545.726562 361.078125 544.550781 359.734375 C 541.910156 359.496094 539.988281 363.089844 537.820312 363.523438 C 535.945312 363.898438 532.148438 362.285156 529.554688 363.722656 C 529.753906 362.105469 529.359375 360.351562 529.554688 358.726562 L 545.554688 358.726562 Z M 545.554688 358.730469 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 421.535156 365.726562 C 424.699219 365.152344 423.21875 367.296875 423.558594 369.148438 C 424.382812 373.652344 425.757812 378.113281 425.527344 382.71875 C 424.328125 384.371094 422.730469 374.785156 422.535156 373.722656 C 422.3125 372.515625 423.160156 370.441406 421.535156 369.726562 C 421.644531 368.496094 421.601562 366.980469 421.535156 365.726562 Z M 421.535156 365.726562 " fill-opacity="1" fill-rule="nonzero"/><path fill="#c03666" d="M 519.550781 348.734375 C 521.832031 350 519.8125 357.980469 520.546875 358.734375 L 524.550781 358.734375 C 523.714844 365.21875 524.660156 372.582031 522.550781 378.71875 C 522.246094 373.867188 520.957031 372.15625 520.550781 369.726562 C 519.929688 365.972656 519.75 362.511719 519.550781 358.730469 C 519.375 355.421875 519.703125 352.046875 519.550781 348.734375 Z M 519.550781 348.734375 " fill-opacity="1" fill-rule="nonzero"/><path fill="#c03666" d="M 522.550781 378.71875 C 522.613281 379.714844 522.472656 380.726562 522.550781 381.722656 L 524.550781 381.722656 C 523.351562 382.46875 521.34375 384.007812 520.550781 381.722656 C 521.082031 380.789062 522.230469 379.652344 522.550781 378.722656 Z M 522.550781 378.71875 " fill-opacity="1" fill-rule="nonzero"/><path fill="#c03666" d="M 422.535156 373.722656 C 421.886719 373.792969 421.152344 373.617188 420.53125 373.722656 C 420.738281 372.402344 421.414062 371.027344 421.535156 369.726562 C 423.160156 370.441406 422.3125 372.515625 422.535156 373.722656 Z M 422.535156 373.722656 " fill-opacity="1" fill-rule="nonzero"/><path fill="#c03666" d="M 520.550781 378.71875 L 517.550781 378.71875 C 518.164062 378.371094 520.105469 376.328125 520.542969 376.722656 C 520.613281 377.375 520.476562 378.066406 520.550781 378.71875 Z M 520.550781 378.71875 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 360.523438 279.769531 C 362.429688 295.964844 355.226562 310.214844 352.523438 325.742188 C 358.445312 326.679688 369.464844 320.539062 370.523438 314.753906 C 372.9375 314.921875 375.164062 313.902344 377.523438 313.753906 C 377.449219 314.394531 377.636719 315.140625 377.523438 315.753906 C 377.507812 315.835938 376.542969 315.929688 376.542969 316.242188 C 376.722656 316.894531 377.175781 316.648438 377.523438 316.75 C 379.859375 317.46875 383.039062 317.667969 385.519531 317.757812 C 385.90625 322.804688 385.039062 327.765625 384.527344 332.742188 C 384.25 335.425781 384.367188 334.480469 384.527344 336.742188 C 384.703125 339.265625 384.144531 339.132812 383.527344 340.738281 C 381.0625 347.183594 381.464844 348.429688 380.527344 354.730469 C 370.710938 353.96875 360.261719 356.960938 350.519531 355.730469 C 350.363281 355.710938 349.289062 354.964844 348.519531 354.730469 C 348.855469 349.917969 346.378906 345.730469 345.628906 341.132812 C 345.003906 337.304688 347.164062 332.566406 343.519531 330.746094 C 342.917969 323.1875 344.421875 315.933594 346.53125 308.753906 C 350.269531 308.121094 347.359375 310.980469 347.546875 313.183594 C 347.621094 314.023438 348.523438 314.617188 348.523438 314.753906 C 348.507812 319.347656 347.382812 323.308594 347.003906 327.734375 C 346.886719 329.09375 345.332031 331.113281 348.011719 330.753906 C 351.628906 327.082031 349.449219 317.804688 351.523438 314.757812 C 351.582031 314.667969 352.855469 315.152344 353.511719 314.039062 C 358.25 306.003906 357.371094 288.9375 357.527344 279.773438 C 358.527344 279.757812 359.527344 279.773438 360.527344 279.773438 Z M 360.523438 279.769531 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 323.515625 339.738281 C 323.765625 342.132812 323.582031 345.246094 323.515625 347.734375 C 323.441406 350.519531 322.316406 353.804688 322.515625 357.730469 L 300.511719 357.730469 C 303.101562 343.34375 306.363281 328.058594 308.511719 313.753906 L 318.523438 313.753906 C 318.523438 313.753906 318.515625 311.753906 318.515625 311.753906 C 319.664062 320.667969 322.585938 330.914062 323.515625 339.738281 Z M 323.515625 339.738281 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 336.515625 330.746094 C 336.597656 333.398438 336.398438 336.09375 336.515625 338.742188 C 336.765625 344.121094 339.078125 351.96875 342.519531 356.730469 L 341.855469 357.542969 L 332.515625 358.730469 C 331.355469 352.820312 331.667969 345.773438 331.515625 339.738281 C 331.296875 330.773438 331.5625 321.722656 331.515625 312.753906 C 335.011719 312.875 334.28125 313.371094 334.519531 310.304688 C 334.941406 304.957031 334.019531 299.046875 334.519531 293.761719 L 336.5625 317.210938 C 336.605469 321.714844 336.382812 326.25 336.523438 330.746094 Z M 336.515625 330.746094 " fill-opacity="1" fill-rule="nonzero"/><path fill="#07032a" d="M 297.511719 372.722656 C 299.480469 373.308594 303.9375 375.371094 307.3125 376.421875 C 315.785156 379.058594 313.003906 383.0625 305.511719 383.71875 C 301.773438 384.042969 285.476562 384.25 283.175781 382.796875 C 280.847656 381.332031 281.621094 375.292969 281.507812 372.722656 C 282.269531 372.472656 296.648438 372.46875 297.511719 372.722656 Z M 297.511719 372.722656 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f5b499" d="M 331.515625 339.738281 C 331.667969 345.773438 331.355469 352.820312 332.515625 358.730469 C 332.578125 359.050781 332.441406 359.417969 332.515625 359.730469 C 332.160156 361.339844 333.792969 363.839844 330.992188 363.765625 C 323.734375 363.570312 325.878906 352.121094 323.515625 347.734375 C 323.582031 345.246094 323.765625 342.132812 323.515625 339.738281 Z M 331.515625 339.738281 " fill-opacity="1" fill-rule="nonzero"/><path fill="#17092e" d="M 336.515625 338.742188 C 338.941406 338.207031 338.585938 339.976562 339.335938 341.367188 C 340.554688 343.636719 344.15625 352.878906 344.761719 353.503906 C 345.539062 354.316406 347.398438 354.390625 348.519531 354.726562 C 349.289062 354.960938 350.363281 355.707031 350.519531 355.726562 C 349.480469 361.019531 345.378906 360.6875 342.519531 356.726562 C 339.078125 351.964844 336.765625 344.117188 336.515625 338.738281 Z M 336.515625 338.742188 " fill-opacity="1" fill-rule="nonzero"/><path fill="#17092e" d="M 323.515625 347.734375 C 325.882812 352.121094 323.734375 363.574219 330.992188 363.765625 C 333.792969 363.839844 332.160156 361.335938 332.515625 359.730469 C 332.574219 359.976562 335.101562 360.066406 334.355469 363.984375 C 333.230469 369.910156 325.703125 367.460938 323.4375 364.3125 C 321.9375 362.222656 322.628906 360.003906 322.515625 357.734375 C 322.316406 353.808594 323.441406 350.523438 323.515625 347.738281 Z M 323.515625 347.734375 " fill-opacity="1" fill-rule="nonzero"/><path fill="#b64c94" d="M 381.527344 366.726562 L 380.527344 366.726562 C 380.667969 365.210938 380.988281 362.484375 379.527344 361.730469 C 379.832031 359.410156 380.179688 357.050781 380.527344 354.730469 C 381.464844 348.429688 381.0625 347.183594 383.527344 340.738281 C 383.671875 349.4375 382.226562 358.105469 381.527344 366.726562 Z M 381.527344 366.726562 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f5b499" d="M 380.527344 366.726562 C 380.144531 370.804688 379.261719 375.632812 378.523438 379.71875 C 378.398438 379.835938 378.890625 383.566406 376.511719 381.207031 C 377.96875 374.808594 378.671875 368.214844 379.527344 361.730469 C 380.988281 362.484375 380.667969 365.210938 380.527344 366.726562 Z M 380.527344 366.726562 " fill-opacity="1" fill-rule="nonzero"/><path fill="#17092e" d="M 236.5 304.757812 C 246.640625 305.152344 256.746094 304.019531 266.503906 303.757812 C 273.816406 303.5625 281.199219 303.902344 288.511719 303.757812 L 281.507812 360.734375 C 281.414062 359.566406 280.558594 358.371094 280.507812 357.734375 C 279.230469 341.890625 278.074219 329.863281 279.507812 313.757812 C 279.75 311.050781 280.410156 308.476562 280.507812 305.765625 C 276.53125 306.160156 271.785156 305.222656 267.949219 305.691406 C 266.351562 305.886719 264.871094 309.710938 261.535156 308.800781 C 260.800781 310.621094 262.347656 312.503906 262.5 313.757812 C 264.3125 328.761719 266.785156 343.738281 268.5 358.734375 C 269 363.105469 268.507812 368.828125 270.5 372.726562 C 270.46875 373.386719 270.574219 374.078125 270.5 374.726562 C 270.425781 375.375 270.519531 376.066406 270.5 376.726562 C 270.457031 378.386719 270.550781 380.066406 270.496094 381.726562 C 268.609375 382.328125 267.75 381.222656 266.5 380.722656 L 263.5 364.730469 C 263.425781 363.746094 263.585938 362.71875 263.5 361.734375 C 263.414062 360.746094 263.59375 359.71875 263.5 358.734375 C 262.085938 344.160156 260.175781 328.125 257.5 313.757812 C 257.285156 312.613281 258.128906 309.9375 256.914062 309.738281 L 247.488281 309.75 C 247.421875 311.074219 247.574219 312.429688 247.492188 313.753906 C 246.617188 328.210938 247.605469 344.070312 247.492188 358.730469 C 247.429688 367.164062 247.671875 375.632812 247.351562 384.074219 L 242.496094 385.71875 C 243.382812 377.046875 241.277344 366.089844 242.492188 357.730469 L 243.492188 356.730469 C 242.863281 342.613281 244.335938 327.785156 243.492188 313.753906 C 243.414062 312.429688 243.5625 311.074219 243.496094 309.75 L 232.503906 308.746094 C 231.957031 310.363281 231.855469 312.109375 231.488281 313.753906 C 228.34375 327.917969 227.625 344.1875 225.488281 358.730469 C 224.652344 364.4375 223.988281 375.214844 222.273438 380.007812 C 221.632812 381.796875 220.746094 381.929688 218.996094 381.726562 C 217.667969 381.546875 220.207031 361.070312 220.492188 358.734375 C 222.261719 344.101562 224.246094 328.488281 226.492188 313.757812 C 226.695312 312.40625 228.480469 310.609375 227.078125 308.695312 C 223.984375 306.90625 220.257812 308.226562 219.492188 303.761719 C 224.628906 304.269531 231.238281 304.558594 236.496094 304.761719 Z M 236.5 304.757812 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 243.5 313.753906 C 244.347656 327.785156 242.871094 342.613281 243.5 356.730469 C 243.019531 356.839844 242.566406 357.261719 242.5 357.730469 L 225.496094 358.730469 C 227.636719 344.1875 228.351562 327.917969 231.496094 313.753906 Z M 243.5 313.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 257.503906 313.753906 C 260.179688 328.121094 262.089844 344.15625 263.503906 358.730469 L 247.5 358.730469 C 247.613281 344.070312 246.625 328.210938 247.5 313.753906 Z M 257.503906 313.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 590.566406 313.753906 C 591.421875 320.71875 591.925781 327.746094 592.566406 334.742188 C 589.847656 335.761719 590.707031 336.371094 589.304688 337.054688 C 583.566406 339.851562 578.160156 330.515625 571.566406 332.746094 C 571.070312 335.945312 573.96875 337.84375 576.242188 339.5625 C 579.574219 342.082031 592.699219 349.203125 596.566406 350.734375 C 596.75 353.6875 596.304688 356.796875 596.566406 359.730469 L 570.5625 358.730469 C 568.539062 343.308594 565.613281 329.6875 564.558594 313.753906 C 573.191406 314.050781 581.945312 313.351562 590.566406 313.753906 Z M 590.566406 313.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 559.558594 313.753906 C 562.023438 328.617188 563.53125 343.792969 565.558594 358.730469 L 550.558594 358.730469 L 549.558594 356.730469 C 549.625 342.730469 548.746094 327.574219 549.558594 313.753906 Z M 559.558594 313.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#b64c94" d="M 550.558594 358.730469 L 549.558594 358.730469 C 549.558594 358.0625 549.558594 357.398438 549.558594 356.730469 Z M 550.558594 358.730469 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 386.527344 353.734375 C 387.707031 342.117188 389.328125 330.148438 391.105469 318.691406 L 399.535156 318.746094 C 399.523438 330.394531 399.527344 342.085938 399.527344 353.734375 Z M 386.527344 353.734375 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 403.53125 353.734375 C 403.53125 342.105469 403.054688 330.308594 404.105469 318.734375 L 412.535156 318.746094 C 413.601562 330.390625 414.492188 342.089844 415.53125 353.734375 Z M 403.53125 353.734375 " fill-opacity="1" fill-rule="nonzero"/><path fill="#7bb9a7" d="M 433.535156 313.753906 C 431.347656 313.980469 428.078125 315.1875 425.535156 315.753906 L 425.542969 313.753906 C 423.878906 313.6875 422.199219 313.808594 420.53125 313.753906 C 417.246094 313.640625 413.816406 313.628906 410.53125 313.753906 L 410.53125 312.753906 C 418.171875 311.113281 420.628906 309.167969 424.535156 302.757812 C 424.976562 302.03125 425.921875 301.402344 426.535156 300.761719 C 426.734375 301.066406 428.796875 301.472656 429.433594 302.316406 C 431.972656 305.6875 434.191406 309.214844 433.535156 313.753906 Z M 433.535156 313.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#7bb9a7" d="M 377.523438 301.757812 C 377.816406 301.726562 378.246094 301.707031 378.523438 301.757812 C 379.722656 308.796875 386.277344 311.550781 392.527344 312.753906 L 392.527344 314.753906 C 387.773438 314.714844 383 313.40625 377.523438 313.753906 C 375.164062 313.902344 372.9375 314.921875 370.523438 314.753906 C 371.335938 310.320312 370.660156 302.5 377.523438 301.757812 Z M 377.523438 301.757812 " fill-opacity="1" fill-rule="nonzero"/><path fill="#4d3670" d="M 410.53125 312.753906 L 410.53125 313.753906 C 404.832031 313.96875 398.710938 314.796875 392.527344 314.753906 L 392.527344 312.753906 C 399.351562 314.070312 403.71875 314.21875 410.53125 312.753906 Z M 410.53125 312.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#1e0442" d="M 420.53125 313.753906 C 422.199219 313.808594 423.878906 313.6875 425.542969 313.753906 L 425.535156 315.753906 C 425.253906 315.816406 424.867188 316.660156 424.535156 316.75 L 424.476562 314.828125 Z M 420.53125 313.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#1e0442" d="M 423.535156 316.75 C 422.679688 318.371094 420.132812 317.691406 418.53125 317.75 C 421.066406 316.789062 422.027344 317.175781 423.535156 316.75 Z M 423.535156 316.75 " fill-opacity="1" fill-rule="nonzero"/><path fill="#b64c94" d="M 384.527344 336.742188 C 384.367188 334.480469 384.25 335.425781 384.527344 332.742188 Z M 384.527344 336.742188 " fill-opacity="1" fill-rule="nonzero"/><path fill="#1e0442" d="M 416.53125 320.75 C 416.5 320.574219 415.523438 320.179688 415.632812 319.382812 L 416.53125 318.75 Z M 416.53125 320.75 " fill-opacity="1" fill-rule="nonzero"/><path fill="#7bb9a7" d="M 377.523438 316.75 C 377.179688 316.644531 376.722656 316.894531 376.542969 316.242188 C 376.542969 315.929688 377.507812 315.835938 377.523438 315.753906 Z M 377.523438 316.75 " fill-opacity="1" fill-rule="nonzero"/><path fill="#17092e" d="M 640.574219 358.730469 C 642.980469 358.738281 647.039062 359.722656 650.574219 359.730469 C 650.910156 359.730469 651.242188 359.730469 651.574219 359.730469 L 652.578125 366.726562 C 651.628906 366.933594 650.824219 367.796875 650.574219 368.726562 C 650.429688 369.269531 650.675781 370.089844 650.574219 370.722656 C 649.574219 370.703125 648.574219 370.746094 647.574219 370.722656 C 641.953125 370.597656 636.195312 370.578125 630.570312 370.722656 C 629.097656 370.761719 624.097656 370.429688 623.570312 370.722656 C 621.367188 369.765625 622.734375 367.785156 624.167969 366.816406 C 626.878906 364.984375 632.75 365.71875 633.574219 360.730469 C 634.214844 360.730469 638.101562 358.722656 640.574219 358.730469 Z M 640.574219 358.730469 " fill-opacity="1" fill-rule="nonzero"/><path fill="#c03666" d="M 650.574219 368.726562 L 669.574219 368.734375 L 660.03125 369.726562 L 656.578125 371.722656 C 654.066406 371.691406 651.453125 370.742188 650.574219 370.722656 C 650.675781 370.089844 650.429688 369.269531 650.574219 368.726562 Z M 650.574219 368.726562 " fill-opacity="1" fill-rule="nonzero"/><path fill="#b64c94" d="M 647.574219 370.722656 C 642.929688 372.398438 635.285156 372.40625 630.570312 370.722656 C 636.195312 370.578125 641.953125 370.597656 647.574219 370.722656 Z M 647.574219 370.722656 " fill-opacity="1" fill-rule="nonzero"/><path fill="#c03666" d="M 280.507812 357.730469 C 280.558594 358.367188 281.414062 359.5625 281.507812 360.730469 C 281.613281 362.046875 281.410156 363.40625 281.507812 364.726562 L 269.507812 359.734375 C 267.683594 363.722656 271.460938 365.960938 271.597656 367.175781 C 271.921875 370.035156 270.554688 371.734375 270.503906 372.722656 C 268.511719 368.824219 269.003906 363.101562 268.503906 358.730469 C 272.148438 356.855469 276.539062 358.011719 280.507812 357.730469 Z M 280.507812 357.730469 " fill-opacity="1" fill-rule="nonzero"/><path fill="#c03666" d="M 266.503906 380.71875 C 265.996094 380.515625 264.703125 381.316406 264.457031 380.097656 C 264.566406 374.953125 263.898438 369.835938 263.503906 364.726562 Z M 266.503906 380.71875 " fill-opacity="1" fill-rule="nonzero"/><path fill="#c03666" d="M 270.503906 376.722656 C 270.523438 376.0625 270.429688 375.367188 270.503906 374.722656 L 271.5 375.230469 Z M 270.503906 376.722656 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f5b499" d="M 138.480469 355.730469 C 138.464844 357.042969 138.9375 359.566406 139.480469 360.730469 C 141.652344 365.398438 147.054688 365.082031 149.484375 368.726562 C 139.085938 370.222656 131.984375 366.671875 128.480469 356.730469 C 128.929688 356.4375 130.074219 355.792969 130.480469 355.730469 C 132.878906 355.347656 135.960938 356 138.480469 355.730469 Z M 138.480469 355.730469 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 610.570312 335.742188 C 612.03125 336.320312 616.257812 337.328125 617.429688 336.589844 C 621.207031 330.066406 625.195312 321.277344 629.742188 315.421875 C 630.605469 314.3125 630.742188 313.347656 632.5625 313.757812 C 633.75 324.074219 633.300781 337.261719 635.648438 347.183594 C 636.179688 349.445312 637.339844 350.066406 637.570312 350.734375 C 638.515625 353.457031 639.816406 355.957031 640.570312 358.730469 C 638.097656 358.722656 634.210938 360.730469 633.570312 360.730469 C 633.390625 360.730469 632.015625 359.652344 630.183594 359.660156 C 621.308594 359.703125 612.425781 359.769531 603.5625 359.730469 C 603.640625 357.445312 603.113281 353.5625 603.5625 351.734375 C 603.667969 351.308594 606.097656 344.960938 606.5625 343.738281 C 607.597656 341.023438 609.453125 338.453125 610.5625 335.742188 Z M 610.570312 335.742188 " fill-opacity="1" fill-rule="nonzero"/><path fill="#17092e" d="M 596.566406 350.734375 C 592.699219 349.203125 579.574219 342.082031 576.242188 339.5625 C 573.96875 337.84375 571.070312 335.945312 571.566406 332.746094 C 578.164062 330.515625 583.566406 339.851562 589.304688 337.054688 C 590.707031 336.371094 589.84375 335.765625 592.566406 334.742188 C 592.621094 335.328125 592.292969 336.003906 592.726562 336.550781 L 606.566406 343.738281 C 606.101562 344.960938 603.671875 351.308594 603.566406 351.734375 C 601.625 351.523438 598.242188 351.402344 596.566406 350.734375 Z M 596.566406 350.734375 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fbf6de" d="M 700.585938 261.78125 L 702.585938 279.769531 C 698.910156 280.144531 692.320312 280.277344 689.292969 280.976562 C 686.503906 281.621094 685.433594 284.496094 682.582031 284.769531 C 683 277.097656 682.085938 269.398438 683.582031 261.78125 C 688.421875 262.125 695.796875 262.199219 700.585938 261.78125 Z M 700.585938 261.78125 " fill-opacity="1" fill-rule="nonzero"/><path fill="#17092e" d="M 683.582031 261.78125 C 682.085938 269.398438 683 277.097656 682.582031 284.769531 C 682.566406 285.101562 682.605469 285.4375 682.582031 285.769531 L 680.582031 285.769531 C 670.195312 285.769531 659.917969 285.460938 649.574219 284.769531 C 651.511719 281.4375 652.789062 279.378906 654.578125 275.773438 C 655.820312 273.269531 656.65625 269.394531 657.503906 268.203125 C 659.011719 266.082031 667.542969 263.1875 664.578125 258.78125 C 670.546875 259.171875 677.824219 261.367188 683.582031 261.78125 Z M 683.582031 261.78125 " fill-opacity="1" fill-rule="nonzero"/><path fill="#7d4399" d="M 694.585938 311.753906 C 687.957031 323.917969 683.589844 337.140625 678.550781 350.007812 C 678.148438 351.039062 676.625 350.636719 676.582031 350.734375 C 674.429688 351.203125 674.414062 349.582031 673.585938 348.28125 C 666.015625 336.433594 668.167969 323.1875 678.582031 313.753906 C 678.871094 313.492188 681.320312 314.476562 680.582031 311.753906 C 685.472656 311.476562 690.078125 311.800781 694.585938 311.753906 Z M 694.585938 311.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fbf6de" d="M 698.585938 311.753906 C 693.886719 323.078125 688.589844 334.175781 683.804688 345.46875 C 683.023438 347.308594 683.074219 349.554688 682.582031 350.734375 C 681.414062 353.523438 679.847656 356.808594 678.582031 359.730469 C 677.917969 361.257812 677.199219 363.546875 676.582031 364.726562 C 675.460938 366.871094 674.820312 369.3125 672.074219 368.761719 C 671.351562 368.617188 671.667969 366.785156 671.578125 366.726562 C 672.75 364.488281 673.753906 362.113281 674.582031 359.730469 C 675.40625 357.347656 676.367188 351.148438 676.582031 350.734375 C 676.628906 350.644531 678.152344 351.039062 678.550781 350.011719 C 683.589844 337.136719 687.957031 323.917969 694.582031 311.753906 C 695.917969 311.742188 697.25 311.75 698.585938 311.753906 Z M 698.585938 311.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#904f9c" d="M 670.578125 304.757812 L 669.582031 311.75 C 673.226562 311.613281 676.949219 311.960938 680.582031 311.753906 C 681.320312 314.476562 678.871094 313.492188 678.582031 313.753906 L 653.570312 313.753906 C 653.238281 321.222656 654.027344 328.851562 653.617188 336.320312 C 653.546875 337.628906 652.59375 338.550781 652.574219 338.742188 L 652.574219 302.757812 C 652.902344 302.8125 653.25 302.707031 653.578125 302.757812 C 657.71875 303.421875 666.929688 305.03125 670.578125 304.757812 Z M 670.578125 304.757812 " fill-opacity="1" fill-rule="nonzero"/><path fill="#1e0442" d="M 682.582031 285.769531 C 682.101562 292.09375 678.207031 304.179688 670.578125 304.757812 C 666.929688 305.03125 657.71875 303.421875 653.578125 302.757812 C 658.207031 299.476562 669.296875 304.011719 672.949219 301.65625 C 676.359375 299.457031 679.890625 289.894531 680.582031 285.769531 Z M 682.582031 285.769531 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 710.585938 350.734375 C 709.324219 353.933594 707.625 357.09375 706.585938 359.730469 L 678.582031 359.730469 C 679.847656 356.808594 681.414062 353.523438 682.582031 350.734375 C 691.742188 353.488281 701.410156 353.492188 710.585938 350.734375 Z M 710.585938 350.734375 " fill-opacity="1" fill-rule="nonzero"/><path fill="#c03666" d="M 706.585938 359.730469 C 706.035156 361.125 704.933594 363.707031 704.585938 364.726562 C 700.917969 363.238281 695.949219 363.464844 692.035156 363.679688 C 687.054688 363.949219 681.3125 366.296875 676.582031 364.726562 C 677.199219 363.546875 677.917969 361.257812 678.582031 359.730469 Z M 706.585938 359.730469 " fill-opacity="1" fill-rule="nonzero"/><path fill="#c03666" d="M 674.582031 359.730469 C 673.753906 362.113281 672.75 364.488281 671.578125 366.726562 C 670.785156 366.207031 654.121094 366.382812 652.578125 366.726562 L 651.574219 359.730469 C 659.230469 359.792969 666.925781 359.683594 674.582031 359.730469 Z M 674.582031 359.730469 " fill-opacity="1" fill-rule="nonzero"/><path fill="#904f9c" d="M 454.539062 279.769531 C 456.125 284.148438 457.871094 288.644531 460.023438 292.777344 C 460.878906 294.414062 462.164062 298.082031 464.542969 297.761719 C 464.585938 298.085938 464.507812 298.433594 464.542969 298.761719 C 464.644531 299.84375 464.191406 301.242188 465.542969 301.757812 C 466.382812 305.707031 467.757812 310.117188 469.542969 313.753906 C 469.429688 313.761719 468.695312 314.730469 467.542969 314.753906 C 457.195312 314.941406 444.527344 312.605469 433.535156 313.753906 C 434.1875 309.214844 431.972656 305.6875 429.433594 302.316406 C 428.796875 301.472656 426.738281 301.0625 426.535156 300.761719 C 425.570312 299.292969 426.480469 283.1875 426.535156 279.769531 C 435.847656 279.597656 445.230469 280.007812 454.539062 279.769531 Z M 454.539062 279.769531 " fill-opacity="1" fill-rule="nonzero"/><path fill="#904f9c" d="M 585.5625 266.777344 C 585.089844 272.214844 585.964844 277.425781 586.5625 282.769531 C 587.164062 288.113281 587.925781 293.429688 588.5625 298.761719 C 589.160156 303.738281 589.953125 308.777344 590.566406 313.753906 C 581.945312 313.355469 573.191406 314.050781 564.558594 313.753906 C 564.515625 313.070312 562.476562 310.773438 563.679688 308.871094 L 569.832031 307.761719 L 571.558594 303.761719 C 574.8125 303.433594 580.261719 305.035156 582.136719 301.703125 C 582.863281 300.410156 581.566406 299.917969 581.558594 299.765625 C 580.972656 290.394531 575.875 290.28125 567.554688 288.769531 C 569.851562 284.230469 571.136719 274.660156 569.546875 269.792969 C 570.023438 269.128906 583.199219 267.371094 585.558594 266.78125 Z M 585.5625 266.777344 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 534.554688 313.753906 L 544.558594 313.753906 C 544.832031 326.253906 544.210938 338.835938 544.480469 351.351562 C 544.519531 353.152344 545.550781 354.554688 545.554688 354.730469 C 545.585938 356.066406 545.523438 357.398438 545.554688 358.730469 L 529.554688 358.730469 C 529.632812 358.082031 529.472656 357.382812 529.554688 356.730469 C 529.710938 355.433594 529.40625 354.035156 529.554688 352.734375 C 529.679688 351.613281 530.324219 349.769531 530.554688 347.734375 C 530.820312 345.390625 531.28125 343.109375 531.554688 340.738281 C 531.800781 338.585938 532.335938 336.636719 532.554688 334.742188 C 532.703125 333.4375 532.394531 332.042969 532.554688 330.746094 L 532.554688 328.746094 C 532.617188 328.09375 532.46875 327.394531 532.554688 326.746094 C 534.175781 325.894531 533.496094 323.347656 533.554688 321.75 C 533.992188 318.925781 534.152344 316.257812 534.554688 313.753906 Z M 534.554688 313.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f5b499" d="M 474.542969 278.769531 C 474.875 278.753906 475.210938 278.785156 475.542969 278.769531 C 476.863281 278.726562 478.230469 278.886719 479.542969 278.769531 C 478.675781 284.0625 480.160156 286.476562 482.542969 290.765625 C 480.511719 297.832031 478.304688 305.761719 476.542969 312.753906 C 475.917969 312.863281 475.058594 312.59375 474.542969 312.753906 L 471.542969 313.753906 C 470.964844 313.867188 470.199219 313.714844 469.542969 313.753906 C 467.757812 310.117188 466.382812 305.707031 465.542969 301.757812 C 465.328125 300.765625 465.953125 299.3125 464.542969 298.761719 C 464.507812 298.433594 464.585938 298.085938 464.542969 297.761719 C 463.65625 291.660156 461.394531 285.871094 460.539062 279.769531 C 464.746094 279.628906 469.957031 278.984375 474.542969 278.769531 Z M 474.542969 278.769531 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 529.554688 314.753906 C 529.148438 323.167969 528.496094 328.667969 527.554688 336.742188 C 527.367188 338.367188 527.742188 340.109375 527.554688 341.738281 C 527.441406 342.71875 527.664062 343.761719 527.554688 344.738281 L 526.554688 346.738281 C 526.472656 347.386719 526.632812 348.085938 526.554688 348.734375 C 526.1875 351.71875 524.953125 355.625 524.550781 358.730469 L 520.546875 358.730469 C 519.8125 357.980469 521.832031 350 519.550781 348.734375 C 519.125 339.339844 519.292969 329.042969 518.550781 319.75 L 517.550781 318.75 C 517.425781 317.109375 517.738281 315.378906 517.550781 313.753906 C 521.34375 314.25 526.507812 312.558594 529.554688 314.753906 Z M 529.554688 314.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#7bb9a7" d="M 581.5625 299.761719 L 546.5625 302.765625 C 546.347656 303.601562 551.289062 304.730469 551.558594 304.757812 C 547.808594 304.277344 530.242188 305.863281 528.695312 303.597656 L 528.554688 299.761719 L 528.554688 298.761719 C 532.832031 300.023438 547.226562 300.976562 551.410156 300.109375 C 556.6875 299.015625 565.140625 293.554688 567.558594 288.765625 C 575.878906 290.277344 580.976562 290.390625 581.5625 299.761719 Z M 581.5625 299.761719 " fill-opacity="1" fill-rule="nonzero"/><path fill="#6b338c" d="M 476.542969 312.753906 C 474.285156 321.710938 472.378906 331.570312 470.542969 340.738281 L 463.546875 343.734375 C 462.707031 342.839844 465.867188 322.085938 466.574219 319.453125 C 466.828125 318.515625 469.980469 318.992188 467.539062 314.753906 C 468.691406 314.730469 469.425781 313.761719 469.539062 313.753906 C 470.195312 313.714844 470.960938 313.867188 471.539062 313.753906 C 473.109375 313.453125 473.554688 313.054688 474.539062 312.753906 C 475.054688 312.59375 475.914062 312.863281 476.539062 312.753906 Z M 476.542969 312.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#88c0af" d="M 581.5625 299.761719 C 581.570312 299.910156 582.871094 300.402344 582.140625 301.695312 C 580.265625 305.035156 574.816406 303.429688 571.5625 303.757812 C 565.003906 304.421875 558.226562 305.476562 551.558594 304.757812 C 551.289062 304.730469 546.351562 303.605469 546.5625 302.765625 Z M 581.5625 299.761719 " fill-opacity="1" fill-rule="nonzero"/><path fill="#884c99" d="M 517.550781 313.753906 C 517.242188 311.082031 516.28125 308.507812 516.546875 305.757812 C 519.503906 306.121094 523.300781 305.210938 526.082031 305.738281 C 526.886719 305.890625 530.472656 309.183594 530.535156 309.46875 C 531.195312 312.363281 529.59375 313.84375 529.554688 314.753906 C 526.507812 312.558594 521.34375 314.25 517.550781 313.753906 Z M 517.550781 313.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#b64c94" d="M 534.554688 313.753906 C 534.816406 312.117188 535.503906 310.511719 535.628906 308.835938 L 545.546875 309.769531 L 545.554688 354.738281 C 545.554688 354.558594 544.523438 353.164062 544.480469 351.355469 C 544.210938 338.835938 544.832031 326.257812 544.558594 313.75 L 534.554688 313.75 Z M 534.554688 313.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#e54976" d="M 460.539062 279.769531 C 461.394531 285.871094 463.65625 291.660156 464.542969 297.761719 C 462.164062 298.082031 460.878906 294.414062 460.023438 292.777344 C 457.871094 288.644531 456.121094 284.148438 454.539062 279.769531 C 456.535156 279.722656 458.542969 279.835938 460.539062 279.769531 Z M 460.539062 279.769531 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f9848c" d="M 479.542969 278.769531 C 480.882812 278.65625 484.023438 276.738281 486.546875 277.777344 C 488.042969 279.253906 483.117188 288.773438 482.542969 290.765625 C 480.160156 286.476562 478.675781 284.0625 479.542969 278.769531 Z M 479.542969 278.769531 " fill-opacity="1" fill-rule="nonzero"/><path fill="#9e6ebb" d="M 498.546875 316.75 L 496.546875 316.75 C 497.28125 309.425781 494.375 299.261719 500.539062 293.761719 C 498.101562 301.117188 498.113281 309.011719 498.546875 316.75 Z M 498.546875 316.75 " fill-opacity="1" fill-rule="nonzero"/><path fill="#b64c94" d="M 549.558594 313.753906 C 549.625 312.613281 549.027344 309.914062 550.140625 309.738281 L 559.566406 309.75 C 559.714844 311.035156 559.359375 312.539062 559.5625 313.753906 Z M 549.558594 313.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#9e6ebb" d="M 528.554688 298.761719 L 528.554688 299.761719 L 507.539062 294.261719 C 513.789062 292.457031 519.957031 295.382812 525.898438 296.964844 C 527.195312 297.3125 528.191406 298.652344 528.558594 298.761719 Z M 528.554688 298.761719 " fill-opacity="1" fill-rule="nonzero"/><path fill="#17092e" d="M 532.554688 334.742188 C 532.335938 336.636719 531.800781 338.585938 531.554688 340.738281 C 529.78125 339.640625 530.699219 336.621094 530.558594 334.734375 Z M 532.554688 334.742188 " fill-opacity="1" fill-rule="nonzero"/><path fill="#17092e" d="M 532.554688 326.746094 C 532.820312 324.648438 533.332031 323.167969 533.554688 321.75 C 533.496094 323.347656 534.175781 325.894531 532.554688 326.746094 Z M 532.554688 326.746094 " fill-opacity="1" fill-rule="nonzero"/><path fill="#17092e" d="M 527.554688 341.738281 C 527.742188 340.109375 527.367188 338.367188 527.554688 336.742188 C 529.128906 337.398438 529.128906 341.082031 527.554688 341.738281 Z M 527.554688 341.738281 " fill-opacity="1" fill-rule="nonzero"/><path fill="#17092e" d="M 526.554688 346.738281 L 527.554688 344.738281 C 527.351562 346.476562 526.566406 346.625 526.554688 346.738281 Z M 526.554688 346.738281 " fill-opacity="1" fill-rule="nonzero"/><path fill="#17092e" d="M 532.554688 330.746094 C 532.570312 330.625 532.4375 329.933594 532.554688 328.746094 Z M 532.554688 330.746094 " fill-opacity="1" fill-rule="nonzero"/><path fill="#884c99" d="M 518.550781 319.75 C 518.546875 319.679688 517.605469 319.488281 517.550781 318.75 Z M 518.550781 319.75 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f9848c" d="M 475.542969 278.769531 C 475.210938 278.785156 474.875 278.753906 474.542969 278.769531 L 475.042969 277.792969 Z M 475.542969 278.769531 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 678.582031 313.753906 C 668.167969 323.1875 666.019531 336.433594 673.585938 348.28125 C 674.414062 349.582031 674.429688 351.203125 676.582031 350.734375 C 676.367188 351.148438 675.363281 357.46875 674.582031 359.730469 C 666.925781 359.683594 659.230469 359.792969 651.574219 359.730469 C 651.242188 359.730469 650.910156 359.730469 650.574219 359.730469 C 648.894531 357.167969 649.84375 353.582031 650.574219 350.734375 C 651.941406 345.4375 652.0625 344.890625 652.578125 338.742188 C 652.59375 338.550781 653.546875 337.628906 653.617188 336.320312 C 654.027344 328.851562 653.238281 321.222656 653.570312 313.75 L 678.582031 313.75 Z M 678.582031 313.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#6b338c" d="M 680.582031 285.769531 C 679.894531 289.894531 676.359375 299.457031 672.949219 301.65625 C 669.296875 304.011719 658.207031 299.476562 653.578125 302.757812 C 653.25 302.707031 652.902344 302.8125 652.574219 302.757812 C 649.246094 302.214844 645.023438 299.425781 640.574219 300.761719 C 643.421875 295.535156 646.390625 290.246094 649.574219 284.769531 C 659.917969 285.460938 670.195312 285.769531 680.582031 285.769531 Z M 680.582031 285.769531 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f5b499" d="M 610.570312 335.742188 C 609.457031 338.453125 607.601562 341.023438 606.566406 343.738281 L 592.726562 336.550781 C 592.292969 336.003906 592.621094 335.328125 592.566406 334.742188 C 594.933594 333.851562 600.777344 334.371094 600.566406 330.746094 L 601.566406 330.746094 C 604.910156 330.773438 607.996094 334.722656 610.570312 335.742188 Z M 610.570312 335.742188 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f5b499" d="M 650.574219 350.734375 C 649.84375 353.582031 648.894531 357.167969 650.574219 359.730469 C 647.039062 359.722656 642.980469 358.738281 640.574219 358.730469 C 639.820312 355.957031 638.519531 353.457031 637.574219 350.734375 Z M 650.574219 350.734375 " fill-opacity="1" fill-rule="nonzero"/><path fill="#75458c" d="M 649.574219 284.769531 C 646.390625 290.246094 643.421875 295.535156 640.574219 300.761719 C 640.199219 301.445312 636.546875 305.550781 636.5625 303.246094 L 654.578125 275.773438 C 652.789062 279.378906 651.511719 281.4375 649.574219 284.769531 Z M 649.574219 284.769531 " fill-opacity="1" fill-rule="nonzero"/><path fill="#75458c" d="M 634.578125 304.769531 L 636.570312 304.769531 L 636.570312 305.75 L 634.578125 305.75 Z M 634.578125 304.769531 " fill-opacity="1" fill-rule="nonzero"/><path fill="#c03666" d="M 506.550781 183.820312 L 504.546875 183.820312 L 506.050781 158.824219 C 507.007812 167.070312 506.488281 175.523438 506.550781 183.820312 Z M 506.550781 183.820312 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 491.546875 181.820312 L 491.546875 178.824219 C 491.570312 179.757812 492.472656 178.710938 491.546875 181.820312 Z M 491.546875 181.820312 " fill-opacity="1" fill-rule="nonzero"/><path fill="#7d4399" d="M 599.566406 314.753906 C 599.585938 316.707031 599.378906 318.859375 599.566406 320.75 C 599.613281 321.203125 600.09375 321.644531 600.566406 321.75 C 600.839844 324.660156 600.375 327.800781 600.566406 330.746094 C 600.777344 334.371094 594.933594 333.851562 592.566406 334.742188 C 591.925781 327.746094 591.421875 320.71875 590.566406 313.753906 C 593.652344 313.894531 596.515625 314.507812 599.566406 314.753906 Z M 599.566406 314.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#904f9c" d="M 600.566406 321.75 C 600.09375 321.644531 599.613281 321.203125 599.566406 320.75 C 600.03125 320.855469 600.523438 321.296875 600.566406 321.75 Z M 600.566406 321.75 " fill-opacity="1" fill-rule="nonzero"/><path fill="#e54976" d="M 378.523438 279.769531 C 378.699219 286.726562 376.511719 294.492188 377.523438 301.757812 C 370.660156 302.5 371.335938 310.320312 370.523438 314.753906 C 369.464844 320.539062 358.449219 326.679688 352.523438 325.742188 C 355.226562 310.214844 362.429688 295.972656 360.523438 279.769531 Z M 378.523438 279.769531 " fill-opacity="1" fill-rule="nonzero"/><path fill="#07032a" d="M 424.535156 302.757812 C 420.628906 309.167969 418.171875 311.113281 410.53125 312.753906 C 403.71875 314.21875 399.351562 314.070312 392.527344 312.753906 C 386.277344 311.550781 379.722656 308.796875 378.523438 301.757812 C 380.234375 302.097656 382.214844 304.085938 384.265625 304.523438 C 396.519531 307.128906 412.664062 306.332031 424.535156 302.757812 Z M 424.535156 302.757812 " fill-opacity="1" fill-rule="nonzero"/><path fill="#e3d8d1" d="M 477.675781 203.671875 C 475.367188 199.980469 480.570312 195.210938 483.101562 198.753906 C 485.859375 202.609375 479.488281 206.574219 477.675781 203.671875 Z M 477.675781 203.671875 " fill-opacity="1" fill-rule="nonzero"/><path fill="#7bb9a7" d="M 232.5 288.765625 C 233.777344 293.363281 241.894531 300.195312 246.5 301.757812 C 242.265625 301.503906 238.464844 301.316406 233.898438 300.859375 C 227.113281 300.179688 220.164062 299.152344 213.496094 300.761719 C 214.097656 290.691406 223.789062 287.699219 232.5 288.765625 Z M 232.5 288.765625 " fill-opacity="1" fill-rule="nonzero"/><path fill="#88c0af" d="M 246.5 301.757812 C 247.164062 301.800781 247.839844 301.726562 248.5 301.757812 L 248.507812 303.757812 C 247.25 304.699219 238.234375 302.3125 236.5 304.757812 C 231.242188 304.554688 224.632812 304.265625 219.496094 303.757812 C 217.628906 303.574219 215.582031 302.480469 213.507812 302.726562 C 213.445312 302.074219 213.457031 301.414062 213.496094 300.761719 C 220.160156 299.152344 227.113281 300.179688 233.898438 300.859375 C 238.464844 301.316406 242.265625 301.503906 246.5 301.757812 Z M 246.5 301.757812 " fill-opacity="1" fill-rule="nonzero"/><path fill="#7bb9a7" d="M 266.503906 303.757812 C 256.746094 304.019531 246.640625 305.152344 236.5 304.757812 C 238.234375 302.3125 247.25 304.699219 248.507812 303.757812 L 248.5 301.757812 Z M 266.503906 303.757812 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f9848c" d="M 325.515625 278.769531 L 330.515625 279.769531 C 330.617188 288.585938 330.390625 297.441406 330.5 306.269531 C 330.519531 307.960938 329.859375 310.714844 331.515625 311.753906 C 331.515625 312.085938 331.515625 312.421875 331.515625 312.753906 C 331.5625 321.722656 331.296875 330.773438 331.515625 339.738281 L 323.515625 339.738281 C 322.585938 330.914062 319.664062 320.667969 318.515625 311.753906 C 318.429688 311.105469 318.597656 310.40625 318.515625 309.753906 L 319.492188 309.253906 L 318.515625 308.757812 C 317.253906 298.472656 316.480469 288.085938 315.511719 277.773438 C 318.714844 277.996094 321.980469 278.558594 325.515625 278.769531 Z M 325.515625 278.769531 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 318.515625 309.753906 C 318.472656 309.425781 318.554688 309.085938 318.515625 308.757812 L 319.492188 309.253906 Z M 318.515625 309.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f9848c" d="M 357.519531 279.769531 C 357.367188 288.9375 358.242188 306.003906 353.507812 314.035156 C 352.855469 315.148438 351.582031 314.664062 351.519531 314.753906 L 348.519531 314.753906 C 348.519531 314.617188 347.617188 314.019531 347.542969 313.183594 C 347.355469 310.984375 350.265625 308.121094 346.527344 308.753906 C 344.417969 315.941406 342.914062 323.1875 343.515625 330.746094 L 336.511719 330.746094 C 336.375 326.25 336.597656 321.714844 336.554688 317.210938 L 334.511719 293.761719 C 334.703125 291.707031 335.425781 290.4375 335.511719 289.765625 C 335.734375 288.050781 336.441406 286.683594 336.511719 283.769531 C 336.539062 282.769531 336.496094 281.769531 336.511719 280.769531 C 338.707031 281.761719 341.347656 279.890625 342.515625 279.769531 C 347.128906 279.296875 352.71875 279.851562 357.515625 279.769531 Z M 348.511719 306.753906 L 348.511719 304.761719 L 347.53125 304.761719 L 347.53125 306.753906 Z M 348.511719 306.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#b64c94" d="M 336.515625 279.769531 L 336.515625 280.769531 C 336.5 281.769531 336.542969 282.769531 336.515625 283.769531 C 334.75 284.890625 335.664062 287.882812 335.515625 289.765625 C 335.429688 290.4375 334.707031 291.707031 334.515625 293.761719 C 334.019531 299.046875 334.9375 304.957031 334.515625 310.304688 C 334.273438 313.375 335.007812 312.878906 331.511719 312.753906 C 331.511719 312.421875 331.511719 312.085938 331.511719 311.753906 C 331.453125 301.589844 331.539062 291.398438 331.542969 281.21875 L 330.511719 279.769531 L 325.511719 278.769531 C 329.589844 279.015625 332.6875 279.3125 336.511719 279.769531 Z M 336.515625 279.769531 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 342.519531 279.769531 C 341.351562 279.890625 338.710938 281.761719 336.515625 280.769531 L 336.515625 279.769531 C 338.417969 280 340.574219 279.613281 342.519531 279.769531 Z M 342.519531 279.769531 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f5b499" d="M 169.488281 350.734375 C 169.90625 353.355469 171.382812 355.160156 169.472656 358.726562 C 167.144531 359.378906 167.789062 358.105469 167.207031 357.453125 C 165.925781 356.023438 164.734375 354.207031 163.488281 352.734375 L 169.492188 350.734375 Z M 169.488281 350.734375 " fill-opacity="1" fill-rule="nonzero"/><path fill="#904f9c" d="M 198.492188 352.734375 C 198.765625 350.871094 199.316406 348.972656 199.492188 347.734375 C 199.433594 349.335938 200.113281 351.878906 198.492188 352.734375 Z M 198.492188 352.734375 " fill-opacity="1" fill-rule="nonzero"/><path fill="#75458c" d="M 203.492188 316.75 C 203.484375 316.679688 202.558594 316.261719 202.492188 315.753906 Z M 203.492188 316.75 " fill-opacity="1" fill-rule="nonzero"/><path fill="#07032a" d="M 529.554688 356.730469 L 527.53125 356.101562 L 527.558594 350.742188 L 529.546875 350.742188 C 529.546875 350.742188 529.550781 352.738281 529.550781 352.738281 C 529.402344 354.042969 529.707031 355.4375 529.550781 356.734375 Z M 529.554688 356.730469 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f5b499" d="M 343.519531 330.746094 C 347.164062 332.570312 345.003906 337.304688 345.628906 341.132812 C 346.378906 345.730469 348.855469 349.917969 348.519531 354.730469 C 347.398438 354.394531 345.539062 354.320312 344.761719 353.507812 C 344.160156 352.878906 340.558594 343.636719 339.335938 341.371094 C 338.585938 339.976562 338.941406 338.210938 336.515625 338.746094 C 336.398438 336.097656 336.597656 333.402344 336.515625 330.75 L 343.519531 330.75 Z M 343.519531 330.746094 " fill-opacity="1" fill-rule="nonzero"/><path fill="#f5b499" d="M 351.519531 314.753906 C 349.445312 317.804688 351.628906 327.078125 348.007812 330.75 C 345.324219 331.117188 346.882812 329.089844 347 327.730469 C 347.378906 323.300781 348.5 319.34375 348.519531 314.75 L 351.519531 314.75 Z M 351.519531 314.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 279.507812 313.753906 C 278.074219 329.859375 279.230469 341.882812 280.507812 357.730469 C 276.539062 358.011719 272.148438 356.855469 268.503906 358.730469 C 266.789062 343.734375 264.316406 328.757812 262.503906 313.753906 Z M 279.507812 313.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#904f9c" d="M 262.503906 313.753906 C 262.355469 312.5 260.804688 310.617188 261.542969 308.796875 C 264.875 309.707031 266.355469 305.882812 267.953125 305.6875 C 271.792969 305.21875 276.535156 306.15625 280.511719 305.761719 C 280.414062 308.472656 279.75 311.042969 279.511719 313.753906 Z M 262.503906 313.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#904f9c" d="M 231.496094 313.753906 C 231.863281 312.109375 231.964844 310.363281 232.511719 308.746094 L 243.503906 309.75 C 243.570312 311.074219 243.421875 312.429688 243.5 313.753906 Z M 231.496094 313.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#9e6ebb" d="M 247.5 313.753906 C 247.582031 312.429688 247.429688 311.074219 247.496094 309.75 L 256.921875 309.738281 C 258.136719 309.933594 257.292969 312.613281 257.507812 313.757812 L 247.503906 313.757812 Z M 247.5 313.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#904f9c" d="M 242.5 357.730469 C 242.566406 357.261719 243.019531 356.839844 243.5 356.730469 Z M 242.5 357.730469 " fill-opacity="1" fill-rule="nonzero"/><path fill="#e54976" d="M 465.542969 301.757812 C 464.191406 301.242188 464.644531 299.84375 464.542969 298.761719 C 465.953125 299.3125 465.328125 300.765625 465.542969 301.757812 Z M 465.542969 301.757812 " fill-opacity="1" fill-rule="nonzero"/><path fill="#904f9c" d="M 474.542969 312.753906 C 473.558594 313.054688 473.113281 313.453125 471.542969 313.753906 Z M 474.542969 312.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 331.515625 311.753906 C 329.859375 310.71875 330.519531 307.964844 330.5 306.269531 C 330.390625 297.441406 330.617188 288.585938 330.515625 279.769531 L 331.546875 281.21875 C 331.542969 291.398438 331.457031 301.589844 331.515625 311.753906 Z M 331.515625 311.753906 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 335.515625 289.765625 C 335.664062 287.882812 334.75 284.890625 336.515625 283.769531 C 336.445312 286.683594 335.738281 288.050781 335.515625 289.765625 Z M 335.515625 289.765625 " fill-opacity="1" fill-rule="nonzero"/><path fill="#fa8e9b" d="M 347.527344 304.765625 L 348.507812 304.765625 L 348.507812 306.757812 L 347.527344 306.757812 Z M 347.527344 304.765625 " fill-opacity="1" fill-rule="nonzero"/></svg>
diff --git a/static/images/events/pyconus-maintainers-summit-2025.png b/static/images/events/pyconus-maintainers-summit-2025.png
new file mode 100644
index 00000000..d1556065
Binary files /dev/null and b/static/images/events/pyconus-maintainers-summit-2025.png differ
diff --git a/static/images/events/pyconus-maintainers-summit-2025.webp b/static/images/events/pyconus-maintainers-summit-2025.webp
new file mode 100644
index 00000000..056ca80f
Binary files /dev/null and b/static/images/events/pyconus-maintainers-summit-2025.webp differ
diff --git a/static/images/events/scipy-2025/bof-discussions-pyopensci.png b/static/images/events/scipy-2025/bof-discussions-pyopensci.png
new file mode 100644
index 00000000..ffe65096
Binary files /dev/null and b/static/images/events/scipy-2025/bof-discussions-pyopensci.png differ
diff --git a/static/images/events/scipy-2025/bof-discussions-pyopensci.webp b/static/images/events/scipy-2025/bof-discussions-pyopensci.webp
new file mode 100644
index 00000000..ac4f5564
Binary files /dev/null and b/static/images/events/scipy-2025/bof-discussions-pyopensci.webp differ
diff --git a/static/images/events/scipy-2025/lightning-talk-song.png b/static/images/events/scipy-2025/lightning-talk-song.png
new file mode 100644
index 00000000..41a9beed
Binary files /dev/null and b/static/images/events/scipy-2025/lightning-talk-song.png differ
diff --git a/static/images/events/scipy-2025/lightning-talk-song.webp b/static/images/events/scipy-2025/lightning-talk-song.webp
new file mode 100644
index 00000000..cdb91511
Binary files /dev/null and b/static/images/events/scipy-2025/lightning-talk-song.webp differ
diff --git a/static/images/events/scipy-2025/pixi-workshop.png b/static/images/events/scipy-2025/pixi-workshop.png
new file mode 100644
index 00000000..032031ae
Binary files /dev/null and b/static/images/events/scipy-2025/pixi-workshop.png differ
diff --git a/static/images/events/scipy-2025/pixi-workshop.webp b/static/images/events/scipy-2025/pixi-workshop.webp
new file mode 100644
index 00000000..599d8129
Binary files /dev/null and b/static/images/events/scipy-2025/pixi-workshop.webp differ
diff --git a/static/images/events/scipy-2025/pyopensci-python-packaging-workshop.png b/static/images/events/scipy-2025/pyopensci-python-packaging-workshop.png
new file mode 100644
index 00000000..33fd00a3
Binary files /dev/null and b/static/images/events/scipy-2025/pyopensci-python-packaging-workshop.png differ
diff --git a/static/images/events/scipy-2025/pyopensci-python-packaging-workshop.webp b/static/images/events/scipy-2025/pyopensci-python-packaging-workshop.webp
new file mode 100644
index 00000000..206fb982
Binary files /dev/null and b/static/images/events/scipy-2025/pyopensci-python-packaging-workshop.webp differ
diff --git a/static/images/events/sprint-mentor-luiz-meer.png b/static/images/events/sprint-mentor-luiz-meer.png
new file mode 100644
index 00000000..7b67b3d3
Binary files /dev/null and b/static/images/events/sprint-mentor-luiz-meer.png differ
diff --git a/static/images/events/sprint-mentor-luiz-meer.webp b/static/images/events/sprint-mentor-luiz-meer.webp
new file mode 100644
index 00000000..1642f291
Binary files /dev/null and b/static/images/events/sprint-mentor-luiz-meer.webp differ
diff --git a/static/images/events/sprint-people-working.png b/static/images/events/sprint-people-working.png
new file mode 100644
index 00000000..1ea99174
Binary files /dev/null and b/static/images/events/sprint-people-working.png differ
diff --git a/static/images/events/sprint-people-working.webp b/static/images/events/sprint-people-working.webp
new file mode 100644
index 00000000..be7dc931
Binary files /dev/null and b/static/images/events/sprint-people-working.webp differ
diff --git a/static/images/events/sprint-scipy-2024.png b/static/images/events/sprint-scipy-2024.png
new file mode 100644
index 00000000..787f099a
Binary files /dev/null and b/static/images/events/sprint-scipy-2024.png differ
diff --git a/static/images/events/sprint-scipy-2024.webp b/static/images/events/sprint-scipy-2024.webp
new file mode 100644
index 00000000..a936adfd
Binary files /dev/null and b/static/images/events/sprint-scipy-2024.webp differ
diff --git a/static/images/events/sprint-scipy-2025.png b/static/images/events/sprint-scipy-2025.png
new file mode 100644
index 00000000..8ca4409c
Binary files /dev/null and b/static/images/events/sprint-scipy-2025.png differ
diff --git a/static/images/favicon.ico b/static/images/favicon.ico
new file mode 100644
index 00000000..0e7e7d5e
Binary files /dev/null and b/static/images/favicon.ico differ
diff --git a/static/images/foss-free-open-source-software/orphan-python-open-source-packages.png b/static/images/foss-free-open-source-software/orphan-python-open-source-packages.png
new file mode 100644
index 00000000..91951485
Binary files /dev/null and b/static/images/foss-free-open-source-software/orphan-python-open-source-packages.png differ
diff --git a/static/images/foss-free-open-source-software/why-scientists-should-care-open-source.png b/static/images/foss-free-open-source-software/why-scientists-should-care-open-source.png
new file mode 100644
index 00000000..11d7f13e
Binary files /dev/null and b/static/images/foss-free-open-source-software/why-scientists-should-care-open-source.png differ
diff --git a/static/images/foss-free-open-source-software/xkcd-open-source-dependency.png b/static/images/foss-free-open-source-software/xkcd-open-source-dependency.png
new file mode 100644
index 00000000..954f7ce2
Binary files /dev/null and b/static/images/foss-free-open-source-software/xkcd-open-source-dependency.png differ
diff --git a/static/images/full-images/brooke-cagle-unsplash.jpg b/static/images/full-images/brooke-cagle-unsplash.jpg
new file mode 100644
index 00000000..4b8bcad0
Binary files /dev/null and b/static/images/full-images/brooke-cagle-unsplash.jpg differ
diff --git a/static/images/github/codespaces/create-github-codespace-main.png b/static/images/github/codespaces/create-github-codespace-main.png
new file mode 100644
index 00000000..d10a2290
Binary files /dev/null and b/static/images/github/codespaces/create-github-codespace-main.png differ
diff --git a/static/images/github/codespaces/create-github-codespace-main.webp b/static/images/github/codespaces/create-github-codespace-main.webp
new file mode 100644
index 00000000..28c62bae
Binary files /dev/null and b/static/images/github/codespaces/create-github-codespace-main.webp differ
diff --git a/static/images/github/codespaces/reopen-codespace.gif b/static/images/github/codespaces/reopen-codespace.gif
new file mode 100644
index 00000000..ba0987cc
Binary files /dev/null and b/static/images/github/codespaces/reopen-codespace.gif differ
diff --git a/static/images/github/codespaces/reopen-codespace.webp b/static/images/github/codespaces/reopen-codespace.webp
new file mode 100644
index 00000000..c25e2af1
Binary files /dev/null and b/static/images/github/codespaces/reopen-codespace.webp differ
diff --git a/static/images/github/codespaces/resume-github-codespace.png b/static/images/github/codespaces/resume-github-codespace.png
new file mode 100644
index 00000000..481f7e21
Binary files /dev/null and b/static/images/github/codespaces/resume-github-codespace.png differ
diff --git a/static/images/github/codespaces/resume-github-codespace.webp b/static/images/github/codespaces/resume-github-codespace.webp
new file mode 100644
index 00000000..11cb2a85
Binary files /dev/null and b/static/images/github/codespaces/resume-github-codespace.webp differ
diff --git a/static/images/github/codespaces/scipy-fork-repo.gif b/static/images/github/codespaces/scipy-fork-repo.gif
new file mode 100644
index 00000000..28af2680
Binary files /dev/null and b/static/images/github/codespaces/scipy-fork-repo.gif differ
diff --git a/static/images/github/codespaces/scipy-fork-repo.webp b/static/images/github/codespaces/scipy-fork-repo.webp
new file mode 100644
index 00000000..0a52b4d0
Binary files /dev/null and b/static/images/github/codespaces/scipy-fork-repo.webp differ
diff --git a/static/images/github/codespaces/scipy-open-codespace.gif b/static/images/github/codespaces/scipy-open-codespace.gif
new file mode 100644
index 00000000..d3aba971
Binary files /dev/null and b/static/images/github/codespaces/scipy-open-codespace.gif differ
diff --git a/static/images/github/codespaces/scipy-open-codespace.webp b/static/images/github/codespaces/scipy-open-codespace.webp
new file mode 100644
index 00000000..9df3fd87
Binary files /dev/null and b/static/images/github/codespaces/scipy-open-codespace.webp differ
diff --git a/static/images/github/pyopensci-github-help-board.png b/static/images/github/pyopensci-github-help-board.png
new file mode 100644
index 00000000..f964f74c
Binary files /dev/null and b/static/images/github/pyopensci-github-help-board.png differ
diff --git a/static/images/header.png b/static/images/header.png
new file mode 100644
index 00000000..d5658267
Binary files /dev/null and b/static/images/header.png differ
diff --git a/static/images/headers/pyopensci-floral.png b/static/images/headers/pyopensci-floral.png
new file mode 100644
index 00000000..09029ee9
Binary files /dev/null and b/static/images/headers/pyopensci-floral.png differ
diff --git a/static/images/headers/pyopensci-floral.webp b/static/images/headers/pyopensci-floral.webp
new file mode 100644
index 00000000..8ef9f648
Binary files /dev/null and b/static/images/headers/pyopensci-floral.webp differ
diff --git a/static/images/headers/pyopensci-learn-header.png b/static/images/headers/pyopensci-learn-header.png
new file mode 100644
index 00000000..9c6c9a71
Binary files /dev/null and b/static/images/headers/pyopensci-learn-header.png differ
diff --git a/static/images/headers/pyopensci-learn-header.webp b/static/images/headers/pyopensci-learn-header.webp
new file mode 100644
index 00000000..f215fc88
Binary files /dev/null and b/static/images/headers/pyopensci-learn-header.webp differ
diff --git a/static/images/headers/pyopensci-quadratik.png b/static/images/headers/pyopensci-quadratik.png
new file mode 100644
index 00000000..a10ddedb
Binary files /dev/null and b/static/images/headers/pyopensci-quadratik.png differ
diff --git a/static/images/headers/pyopensci-quadratik.webp b/static/images/headers/pyopensci-quadratik.webp
new file mode 100644
index 00000000..9c8b94b4
Binary files /dev/null and b/static/images/headers/pyopensci-quadratik.webp differ
diff --git a/static/images/headers/pyopensci-scipy-2025.png b/static/images/headers/pyopensci-scipy-2025.png
new file mode 100644
index 00000000..51637fc2
Binary files /dev/null and b/static/images/headers/pyopensci-scipy-2025.png differ
diff --git a/static/images/headers/pyopensci-scipy-2025.webp b/static/images/headers/pyopensci-scipy-2025.webp
new file mode 100644
index 00000000..ce6d4545
Binary files /dev/null and b/static/images/headers/pyopensci-scipy-2025.webp differ
diff --git a/static/images/headers/pyopensci-software.png b/static/images/headers/pyopensci-software.png
new file mode 100644
index 00000000..5cdc4af6
Binary files /dev/null and b/static/images/headers/pyopensci-software.png differ
diff --git a/static/images/headers/pyopensci-software.webp b/static/images/headers/pyopensci-software.webp
new file mode 100644
index 00000000..a721c016
Binary files /dev/null and b/static/images/headers/pyopensci-software.webp differ
diff --git a/static/images/headers/pyopensci-sprints-2025.png b/static/images/headers/pyopensci-sprints-2025.png
new file mode 100644
index 00000000..e6ac50c7
Binary files /dev/null and b/static/images/headers/pyopensci-sprints-2025.png differ
diff --git a/static/images/headers/pyopensci-sprints-2025.webp b/static/images/headers/pyopensci-sprints-2025.webp
new file mode 100644
index 00000000..dd1640b7
Binary files /dev/null and b/static/images/headers/pyopensci-sprints-2025.webp differ
diff --git a/static/images/headers/pyopensci-sprints.png b/static/images/headers/pyopensci-sprints.png
new file mode 100644
index 00000000..b3b1c251
Binary files /dev/null and b/static/images/headers/pyopensci-sprints.png differ
diff --git a/static/images/headers/pyopensci-sprints.webp b/static/images/headers/pyopensci-sprints.webp
new file mode 100644
index 00000000..50534f7b
Binary files /dev/null and b/static/images/headers/pyopensci-sprints.webp differ
diff --git a/static/images/headers/pyopensci-sustainability.png b/static/images/headers/pyopensci-sustainability.png
new file mode 100644
index 00000000..9ca5736f
Binary files /dev/null and b/static/images/headers/pyopensci-sustainability.png differ
diff --git a/static/images/headers/pyopensci-sustainability.webp b/static/images/headers/pyopensci-sustainability.webp
new file mode 100644
index 00000000..ecdd0308
Binary files /dev/null and b/static/images/headers/pyopensci-sustainability.webp differ
diff --git a/static/images/headers/pyos-peer-review-header.png b/static/images/headers/pyos-peer-review-header.png
new file mode 100644
index 00000000..2015c3a2
Binary files /dev/null and b/static/images/headers/pyos-peer-review-header.png differ
diff --git a/static/images/headers/pyos-peer-review-header.webp b/static/images/headers/pyos-peer-review-header.webp
new file mode 100644
index 00000000..f55d8769
Binary files /dev/null and b/static/images/headers/pyos-peer-review-header.webp differ
diff --git a/static/images/headers/python-packaging-header.png b/static/images/headers/python-packaging-header.png
new file mode 100644
index 00000000..a8b614dd
Binary files /dev/null and b/static/images/headers/python-packaging-header.png differ
diff --git a/static/images/headers/python-packaging-header.webp b/static/images/headers/python-packaging-header.webp
new file mode 100644
index 00000000..eaf8cea8
Binary files /dev/null and b/static/images/headers/python-packaging-header.webp differ
diff --git a/static/images/headers/scipy-2024-workshop.png b/static/images/headers/scipy-2024-workshop.png
new file mode 100644
index 00000000..a0215e3c
Binary files /dev/null and b/static/images/headers/scipy-2024-workshop.png differ
diff --git a/static/images/headers/scipy-2024-workshop.webp b/static/images/headers/scipy-2024-workshop.webp
new file mode 100644
index 00000000..27ebea34
Binary files /dev/null and b/static/images/headers/scipy-2024-workshop.webp differ
diff --git a/static/images/headers/white-header.png b/static/images/headers/white-header.png
new file mode 100644
index 00000000..9bc626ae
Binary files /dev/null and b/static/images/headers/white-header.png differ
diff --git a/static/images/headers/white-header.webp b/static/images/headers/white-header.webp
new file mode 100644
index 00000000..350a1f50
Binary files /dev/null and b/static/images/headers/white-header.webp differ
diff --git a/static/images/hero-images/james-sprint-2026-scipy.png b/static/images/hero-images/james-sprint-2026-scipy.png
new file mode 100644
index 00000000..4f1b71cc
Binary files /dev/null and b/static/images/hero-images/james-sprint-2026-scipy.png differ
diff --git a/static/images/hero-images/james-sprint-rotation-2.png b/static/images/hero-images/james-sprint-rotation-2.png
new file mode 100644
index 00000000..744be512
Binary files /dev/null and b/static/images/hero-images/james-sprint-rotation-2.png differ
diff --git a/static/images/hero-images/scipy-sprint-working.png b/static/images/hero-images/scipy-sprint-working.png
new file mode 100644
index 00000000..8ec99877
Binary files /dev/null and b/static/images/hero-images/scipy-sprint-working.png differ
diff --git a/static/images/hero-images/scipy-sprint-working.webp b/static/images/hero-images/scipy-sprint-working.webp
new file mode 100644
index 00000000..06fb46be
Binary files /dev/null and b/static/images/hero-images/scipy-sprint-working.webp differ
diff --git a/static/images/hero-images/sprint-mentor-luiz-meer.png b/static/images/hero-images/sprint-mentor-luiz-meer.png
new file mode 100644
index 00000000..7b67b3d3
Binary files /dev/null and b/static/images/hero-images/sprint-mentor-luiz-meer.png differ
diff --git a/static/images/hero-images/sprint-mentor-luiz-meer.webp b/static/images/hero-images/sprint-mentor-luiz-meer.webp
new file mode 100644
index 00000000..1642f291
Binary files /dev/null and b/static/images/hero-images/sprint-mentor-luiz-meer.webp differ
diff --git a/static/images/hero-images/sprint-people-working.png b/static/images/hero-images/sprint-people-working.png
new file mode 100644
index 00000000..1ea99174
Binary files /dev/null and b/static/images/hero-images/sprint-people-working.png differ
diff --git a/static/images/hero-images/sprint-people-working.webp b/static/images/hero-images/sprint-people-working.webp
new file mode 100644
index 00000000..be7dc931
Binary files /dev/null and b/static/images/hero-images/sprint-people-working.webp differ
diff --git a/static/images/hero-images/sprint-scipy-2024.png b/static/images/hero-images/sprint-scipy-2024.png
new file mode 100644
index 00000000..787f099a
Binary files /dev/null and b/static/images/hero-images/sprint-scipy-2024.png differ
diff --git a/static/images/jinx-and-luna.png b/static/images/jinx-and-luna.png
new file mode 100644
index 00000000..dfb06188
Binary files /dev/null and b/static/images/jinx-and-luna.png differ
diff --git a/static/images/landing-pages/community-partnerships.png b/static/images/landing-pages/community-partnerships.png
new file mode 100644
index 00000000..a4e66cb8
Binary files /dev/null and b/static/images/landing-pages/community-partnerships.png differ
diff --git a/static/images/landing-pages/community-partnerships.webp b/static/images/landing-pages/community-partnerships.webp
new file mode 100644
index 00000000..541f4c9b
Binary files /dev/null and b/static/images/landing-pages/community-partnerships.webp differ
diff --git a/static/images/landing-pages/peer-review-people.png b/static/images/landing-pages/peer-review-people.png
new file mode 100644
index 00000000..0aadfe63
Binary files /dev/null and b/static/images/landing-pages/peer-review-people.png differ
diff --git a/static/images/landing-pages/peer-review-people.webp b/static/images/landing-pages/peer-review-people.webp
new file mode 100644
index 00000000..f641b29b
Binary files /dev/null and b/static/images/landing-pages/peer-review-people.webp differ
diff --git a/static/images/landing-pages/peer-review-supports-maintainers.png b/static/images/landing-pages/peer-review-supports-maintainers.png
new file mode 100644
index 00000000..8be47478
Binary files /dev/null and b/static/images/landing-pages/peer-review-supports-maintainers.png differ
diff --git a/static/images/landing-pages/peer-review-supports-maintainers.webp b/static/images/landing-pages/peer-review-supports-maintainers.webp
new file mode 100644
index 00000000..e34b6366
Binary files /dev/null and b/static/images/landing-pages/peer-review-supports-maintainers.webp differ
diff --git a/static/images/landing-pages/peer-review-trusted-software.png b/static/images/landing-pages/peer-review-trusted-software.png
new file mode 100644
index 00000000..e922f0ac
Binary files /dev/null and b/static/images/landing-pages/peer-review-trusted-software.png differ
diff --git a/static/images/landing-pages/peer-review-trusted-software.webp b/static/images/landing-pages/peer-review-trusted-software.webp
new file mode 100644
index 00000000..398a805c
Binary files /dev/null and b/static/images/landing-pages/peer-review-trusted-software.webp differ
diff --git a/static/images/landing-pages/people-working-together.png b/static/images/landing-pages/people-working-together.png
new file mode 100644
index 00000000..8f485728
Binary files /dev/null and b/static/images/landing-pages/people-working-together.png differ
diff --git a/static/images/landing-pages/people-working-together.webp b/static/images/landing-pages/people-working-together.webp
new file mode 100644
index 00000000..8cbd4a91
Binary files /dev/null and b/static/images/landing-pages/people-working-together.webp differ
diff --git a/static/images/landing-pages/pyopensci-joss-partners.png b/static/images/landing-pages/pyopensci-joss-partners.png
new file mode 100644
index 00000000..6a0103ba
Binary files /dev/null and b/static/images/landing-pages/pyopensci-joss-partners.png differ
diff --git a/static/images/landing-pages/pyopensci-joss-partners.webp b/static/images/landing-pages/pyopensci-joss-partners.webp
new file mode 100644
index 00000000..3cfafaee
Binary files /dev/null and b/static/images/landing-pages/pyopensci-joss-partners.webp differ
diff --git a/static/images/landing-pages/pyopensci-joss-partnership.png b/static/images/landing-pages/pyopensci-joss-partnership.png
new file mode 100644
index 00000000..3095e284
Binary files /dev/null and b/static/images/landing-pages/pyopensci-joss-partnership.png differ
diff --git a/static/images/landing-pages/pyopensci-joss-partnership.webp b/static/images/landing-pages/pyopensci-joss-partnership.webp
new file mode 100644
index 00000000..1231e889
Binary files /dev/null and b/static/images/landing-pages/pyopensci-joss-partnership.webp differ
diff --git a/static/images/landing-pages/pyopensci-supports-maintainers.png b/static/images/landing-pages/pyopensci-supports-maintainers.png
new file mode 100644
index 00000000..91b8a5d1
Binary files /dev/null and b/static/images/landing-pages/pyopensci-supports-maintainers.png differ
diff --git a/static/images/landing-pages/pyopensci-supports-maintainers.webp b/static/images/landing-pages/pyopensci-supports-maintainers.webp
new file mode 100644
index 00000000..e12bc53a
Binary files /dev/null and b/static/images/landing-pages/pyopensci-supports-maintainers.webp differ
diff --git a/static/images/landing-pages/pyopensci-working-together.png b/static/images/landing-pages/pyopensci-working-together.png
new file mode 100644
index 00000000..90be3559
Binary files /dev/null and b/static/images/landing-pages/pyopensci-working-together.png differ
diff --git a/static/images/landing-pages/pyopensci-working-together.webp b/static/images/landing-pages/pyopensci-working-together.webp
new file mode 100644
index 00000000..e8a4a8cf
Binary files /dev/null and b/static/images/landing-pages/pyopensci-working-together.webp differ
diff --git a/static/images/landing-pages/scipy-bof-working.png b/static/images/landing-pages/scipy-bof-working.png
new file mode 100644
index 00000000..fae1a6ef
Binary files /dev/null and b/static/images/landing-pages/scipy-bof-working.png differ
diff --git a/static/images/landing-pages/scipy-bof-working.webp b/static/images/landing-pages/scipy-bof-working.webp
new file mode 100644
index 00000000..ede7e395
Binary files /dev/null and b/static/images/landing-pages/scipy-bof-working.webp differ
diff --git a/static/images/landing-pages/scipy-sprint-2026.png b/static/images/landing-pages/scipy-sprint-2026.png
new file mode 100644
index 00000000..f403a587
Binary files /dev/null and b/static/images/landing-pages/scipy-sprint-2026.png differ
diff --git a/static/images/landing-pages/scipy-sprint-2026.webp b/static/images/landing-pages/scipy-sprint-2026.webp
new file mode 100644
index 00000000..60eb2f9f
Binary files /dev/null and b/static/images/landing-pages/scipy-sprint-2026.webp differ
diff --git a/static/images/landing-pages/scipy-sprint-working.png b/static/images/landing-pages/scipy-sprint-working.png
new file mode 100644
index 00000000..8ec99877
Binary files /dev/null and b/static/images/landing-pages/scipy-sprint-working.png differ
diff --git a/static/images/landing-pages/scipy-sprint-working.webp b/static/images/landing-pages/scipy-sprint-working.webp
new file mode 100644
index 00000000..06fb46be
Binary files /dev/null and b/static/images/landing-pages/scipy-sprint-working.webp differ
diff --git a/static/images/landing-pages/simple-python-packaging-header.png b/static/images/landing-pages/simple-python-packaging-header.png
new file mode 100644
index 00000000..ad357cea
Binary files /dev/null and b/static/images/landing-pages/simple-python-packaging-header.png differ
diff --git a/static/images/landing-pages/simple-python-packaging-header.webp b/static/images/landing-pages/simple-python-packaging-header.webp
new file mode 100644
index 00000000..0a6502d7
Binary files /dev/null and b/static/images/landing-pages/simple-python-packaging-header.webp differ
diff --git a/static/images/landing-pages/software-peer-review.png b/static/images/landing-pages/software-peer-review.png
new file mode 100644
index 00000000..5f42a88a
Binary files /dev/null and b/static/images/landing-pages/software-peer-review.png differ
diff --git a/static/images/landing-pages/software-peer-review.webp b/static/images/landing-pages/software-peer-review.webp
new file mode 100644
index 00000000..2bae182f
Binary files /dev/null and b/static/images/landing-pages/software-peer-review.webp differ
diff --git a/static/images/landing-pages/trusted-python-software.png b/static/images/landing-pages/trusted-python-software.png
new file mode 100644
index 00000000..98525077
Binary files /dev/null and b/static/images/landing-pages/trusted-python-software.png differ
diff --git a/static/images/landing-pages/trusted-python-software.webp b/static/images/landing-pages/trusted-python-software.webp
new file mode 100644
index 00000000..2ea8165e
Binary files /dev/null and b/static/images/landing-pages/trusted-python-software.webp differ
diff --git a/static/images/landing-pages/trusted-software.png b/static/images/landing-pages/trusted-software.png
new file mode 100644
index 00000000..edd74d21
Binary files /dev/null and b/static/images/landing-pages/trusted-software.png differ
diff --git a/static/images/landing-pages/trusted-software.webp b/static/images/landing-pages/trusted-software.webp
new file mode 100644
index 00000000..b9f9a1ee
Binary files /dev/null and b/static/images/landing-pages/trusted-software.webp differ
diff --git a/static/images/landing-pages/women-collaborating.png b/static/images/landing-pages/women-collaborating.png
new file mode 100644
index 00000000..9ad2c104
Binary files /dev/null and b/static/images/landing-pages/women-collaborating.png differ
diff --git a/static/images/landing-pages/women-collaborating.webp b/static/images/landing-pages/women-collaborating.webp
new file mode 100644
index 00000000..54d2dca9
Binary files /dev/null and b/static/images/landing-pages/women-collaborating.webp differ
diff --git a/static/images/learn-graphics/community-created.png b/static/images/learn-graphics/community-created.png
new file mode 100644
index 00000000..f4b031f5
Binary files /dev/null and b/static/images/learn-graphics/community-created.png differ
diff --git a/static/images/learn-graphics/community-created.webp b/static/images/learn-graphics/community-created.webp
new file mode 100644
index 00000000..e0a2364c
Binary files /dev/null and b/static/images/learn-graphics/community-created.webp differ
diff --git a/static/images/learn-graphics/github-collaboration.png b/static/images/learn-graphics/github-collaboration.png
new file mode 100644
index 00000000..46e9dd86
Binary files /dev/null and b/static/images/learn-graphics/github-collaboration.png differ
diff --git a/static/images/learn-graphics/github-collaboration.webp b/static/images/learn-graphics/github-collaboration.webp
new file mode 100644
index 00000000..2a95234b
Binary files /dev/null and b/static/images/learn-graphics/github-collaboration.webp differ
diff --git a/static/images/logo.png b/static/images/logo.png
new file mode 100644
index 00000000..ce4c14e8
Binary files /dev/null and b/static/images/logo.png differ
diff --git a/static/images/movingpandas/mp_fig1.png b/static/images/movingpandas/mp_fig1.png
new file mode 100644
index 00000000..db261fdb
Binary files /dev/null and b/static/images/movingpandas/mp_fig1.png differ
diff --git a/static/images/movingpandas/mp_fig2.png b/static/images/movingpandas/mp_fig2.png
new file mode 100644
index 00000000..9f9d47ce
Binary files /dev/null and b/static/images/movingpandas/mp_fig2.png differ
diff --git a/static/images/movingpandas/mp_fig3.png b/static/images/movingpandas/mp_fig3.png
new file mode 100644
index 00000000..1201ffec
Binary files /dev/null and b/static/images/movingpandas/mp_fig3.png differ
diff --git a/static/images/movingpandas/mp_fig4.gif b/static/images/movingpandas/mp_fig4.gif
new file mode 100644
index 00000000..361c6025
Binary files /dev/null and b/static/images/movingpandas/mp_fig4.gif differ
diff --git a/static/images/netlify-badge-dark.svg b/static/images/netlify-badge-dark.svg
new file mode 100644
index 00000000..9ce2fb3a
--- /dev/null
+++ b/static/images/netlify-badge-dark.svg
@@ -0,0 +1 @@
+<svg width="114" height="50" viewBox="0 0 114 50" fill="none" xmlns="http://www.w3.org/2000/svg"><g clip-path="url(#a)"><path fill="#060B10" d="M0 0h114v51H0z"/><g clip-path="url(#b)" fill="#fff"><path d="M44.445 40.302v-7.695l.153-.16h1.853l.154.16v7.695l-.154.16h-1.853l-.153-.16ZM44.445 17.855v-7.696l.153-.159h1.853l.154.16v7.695l-.154.16h-1.853l-.153-.16ZM38.068 34.892h-.254l-1.275-1.323v-.264l2.388-2.482 1.349.002.18.185v1.4l-2.388 2.482ZM36.54 17.227v-.267l1.274-1.32h.254l2.388 2.479v1.398l-.18.19h-1.349l-2.388-2.48ZM28.154 24.107h10.5l.153.16v1.926l-.153.16h-10.5l-.154-.16v-1.927l.154-.16ZM99.844 24.11l.154.159v1.924l-.154.16H89.19l-.153-.16.77-1.924.154-.16h9.883ZM49 29.24h-1.853l-.153-.16v-4.502c0-.802-.303-1.423-1.234-1.443a24.2 24.2 0 0 0-1.613.025l-.089.092v5.826l-.153.16h-1.853l-.154-.16v-7.695l.154-.16h4.169c1.62 0 2.933 1.364 2.933 3.046v4.81l-.154.159v.002ZM57.974 25.871l-.154.16h-4.79l-.154.16c0 .32.31 1.283 1.546 1.283.463 0 .926-.16 1.082-.481l.154-.16h1.852l.154.16c-.154.962-.926 2.407-3.245 2.407-2.625 0-3.861-1.924-3.861-4.172 0-2.248 1.236-4.171 3.708-4.171 2.472 0 3.708 1.924 3.708 4.171v.643Zm-2.319-1.605c0-.16-.153-1.283-1.39-1.283-1.235 0-1.389 1.124-1.389 1.283l.154.16h2.472l.153-.16ZM62.298 26.833c0 .322.154.481.464.481h1.39l.153.16v1.604l-.154.16h-1.39c-1.389 0-2.625-.643-2.625-2.407v-3.529l-.154-.16H58.9l-.154-.159v-1.605l.154-.16h1.082l.154-.159v-1.443l.154-.16h1.852l.154.16v1.443l.154.16h1.699l.153.16v1.604l-.153.16h-1.7l-.153.159v3.529l.002.002ZM68.015 29.24h-1.853l-.153-.16V18.172l.153-.16h1.853l.154.16v10.907l-.154.16v.002ZM72.186 19.935h-1.852l-.154-.16v-1.604l.154-.16h1.852l.154.16v1.605l-.154.16Zm0 9.305h-1.852l-.154-.16v-7.7l.154-.159h1.852l.154.16v7.7l-.154.16ZM79.449 18.171v1.605l-.154.16h-1.39c-.309 0-.463.159-.463.48v.643l.154.16h1.546l.153.16v1.604l-.153.16h-1.546l-.154.159v5.774l-.153.16h-1.853l-.154-.16v-5.774l-.153-.16h-1.083l-.153-.159v-1.605l.153-.16h1.083l.153-.159v-.643c0-1.764 1.236-2.407 2.626-2.407h1.39l.153.16-.002.002ZM85.163 29.4c-.619 1.605-1.236 2.567-3.398 2.567h-.773l-.154-.16v-1.605l.154-.16h.773c.773 0 .926-.159 1.082-.64v-.16l-2.472-6.257v-1.604l.154-.16h1.39l.153.16 1.853 5.455h.153l1.853-5.455.154-.16h1.39l.153.16v1.604l-2.472 6.417.007-.002Z"/></g><path fill="#fff" d="M0 0v50h15V0z"/><path d="M6.518 45.367v-.774H11v.774H6.518Zm0-1.746c0-.44.098-.784.294-1.032.196-.248.474-.372.834-.372.348 0 .622.13.822.39.2.26.3.628.3 1.104l-.336.018c.004-.608.114-1.062.33-1.362.212-.3.524-.45.936-.45.424 0 .748.146.972.438.22.288.33.686.33 1.194v1.242h-.738v-1.152c0-.268-.05-.488-.15-.66a.498.498 0 0 0-.462-.258c-.224 0-.39.088-.498.264-.108.172-.162.39-.162.654v1.146h-.738V43.68c0-.192-.04-.36-.12-.504a.426.426 0 0 0-.396-.216c-.192 0-.33.068-.414.204a.955.955 0 0 0-.126.51v1.116h-.678v-1.17Zm0-2.925v-.774H9.17c.256 0 .472-.04.648-.12a.88.88 0 0 0 .39-.336.926.926 0 0 0 .126-.486.926.926 0 0 0-.126-.486.845.845 0 0 0-.39-.33 1.497 1.497 0 0 0-.648-.126H6.518v-.75h2.664c.604 0 1.068.146 1.392.438.324.288.486.71.486 1.266 0 .56-.162.984-.486 1.272-.324.288-.788.432-1.392.432H6.518Zm0-5.048v-.774H11v.774H6.518Zm0-2.475V32.4H11v.774H6.518Zm3.75-.546v-2.412H11v2.412h-.732Zm-3.69-3.903v-.773H11v.773H6.578Zm-.06 1.41v-3.6h.732v3.6h-.732Zm0-6.98v-.827l3.684-1.056v.318L6.518 20.43v-.888l3.684-1.122v.318L6.518 17.64v-.798L11 18.18v.81l-4.086 1.254v-.438L11 21.097v.756l-4.482 1.302Zm0-7.385v-.774H11v.774H6.518Zm.06-3.283v-.774H11v.774H6.578Zm-.06 1.41v-3.6h.732v3.6h-.732Zm0-4.7v-.773H11v.774H6.518Zm1.572-.545V6.179h.732V8.65H8.09ZM6.518 6.407v-.774H11v.774H6.518Z" fill="#060B10"/></g><rect x="1" y="1" width="112" height="48" rx="3" stroke="#060B10" stroke-width="2"/><defs><clipPath id="a"><rect width="114" height="50" rx="4" fill="#fff"/></clipPath><clipPath id="b"><path fill="#fff" d="M28 10h72v30.462H28z"/></clipPath></defs></svg>
diff --git a/static/images/newsletter/04-2024-newsletter/eomapslogo.png b/static/images/newsletter/04-2024-newsletter/eomapslogo.png
new file mode 100644
index 00000000..1878ccf5
Binary files /dev/null and b/static/images/newsletter/04-2024-newsletter/eomapslogo.png differ
diff --git a/static/images/newsletter/04-2024-newsletter/ms-pycon-2024.png b/static/images/newsletter/04-2024-newsletter/ms-pycon-2024.png
new file mode 100644
index 00000000..3e336934
Binary files /dev/null and b/static/images/newsletter/04-2024-newsletter/ms-pycon-2024.png differ
diff --git a/static/images/newsletter/04-2024-newsletter/peer-review-partners-process.png b/static/images/newsletter/04-2024-newsletter/peer-review-partners-process.png
new file mode 100644
index 00000000..a7be8981
Binary files /dev/null and b/static/images/newsletter/04-2024-newsletter/peer-review-partners-process.png differ
diff --git a/static/images/open-source/pyopensci-contributions-by-quarter.png b/static/images/open-source/pyopensci-contributions-by-quarter.png
new file mode 100644
index 00000000..1f86e449
Binary files /dev/null and b/static/images/open-source/pyopensci-contributions-by-quarter.png differ
diff --git a/static/images/pandera-logo.svg b/static/images/pandera-logo.svg
new file mode 100644
index 00000000..ed266ecd
--- /dev/null
+++ b/static/images/pandera-logo.svg
@@ -0,0 +1 @@
+<svg version="1.1" viewBox="0.0 0.0 1200.0 1200.0" fill="none" stroke="none" stroke-linecap="square" stroke-miterlimit="10" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg"><clipPath id="p.0"><path d="m0 0l1200.0 0l0 1200.0l-1200.0 0l0 -1200.0z" clip-rule="nonzero"/></clipPath><g clip-path="url(#p.0)"><path fill="#000000" fill-opacity="0.0" d="m0 0l1200.0 0l0 1200.0l-1200.0 0z" fill-rule="evenodd"/><path fill="#2ed593" d="m1102.6711 179.23235l-498.17328 291.40143l0 550.14185l498.17328 -291.40143z" fill-rule="evenodd"/><path stroke="#2ed593" stroke-width="24.0" stroke-linejoin="round" stroke-linecap="butt" d="m1102.6711 179.23235l-498.17328 291.40143l0 550.14185l498.17328 -291.40143z" fill-rule="evenodd"/><path fill="#ffffff" d="m97.34953 179.23235l507.1496 291.38788l0 550.1554l-507.1496 -291.38788z" fill-rule="evenodd"/><path stroke="#2ed593" stroke-width="24.0" stroke-linejoin="round" stroke-linecap="butt" d="m97.34953 179.23235l507.1496 291.38788l0 550.1554l-507.1496 -291.38788z" fill-rule="evenodd"/><path fill="#000000" fill-opacity="0.0" d="m97.34953 454.31006l507.1496 291.40155" fill-rule="evenodd"/><path stroke="#2ed593" stroke-width="4.0" stroke-linejoin="round" stroke-linecap="butt" d="m97.34953 454.31006l507.1496 291.40155" fill-rule="evenodd"/><path fill="#000000" fill-opacity="0.0" d="m350.92435 324.92627l0 550.1417" fill-rule="evenodd"/><path stroke="#2ed593" stroke-width="4.0" stroke-linejoin="round" stroke-linecap="butt" d="m350.92435 324.92627l0 550.1417" fill-rule="evenodd"/><path fill="#000000" fill-opacity="0.0" d="m97.315956 326.9754l507.14963 291.37012" fill-rule="evenodd"/><path stroke="#2ed593" stroke-width="4.0" stroke-linejoin="round" stroke-linecap="butt" d="m97.315956 326.9754l507.14963 291.37012" fill-rule="evenodd"/><path fill="#000000" fill-opacity="0.0" d="m97.315956 593.46533l507.14963 291.37006" fill-rule="evenodd"/><path stroke="#2ed593" stroke-width="4.0" stroke-linejoin="round" stroke-linecap="butt" d="m97.315956 593.46533l507.14963 291.37006" fill-rule="evenodd"/></g></svg>
diff --git a/static/images/peer-review/co-development-open-education.png b/static/images/peer-review/co-development-open-education.png
new file mode 100644
index 00000000..aa14fa62
Binary files /dev/null and b/static/images/peer-review/co-development-open-education.png differ
diff --git a/static/images/peer-review/co-development-open-education.webp b/static/images/peer-review/co-development-open-education.webp
new file mode 100644
index 00000000..23eba2df
Binary files /dev/null and b/static/images/peer-review/co-development-open-education.webp differ
diff --git a/static/images/peer-review/peer-review-partners-process.png b/static/images/peer-review/peer-review-partners-process.png
new file mode 100644
index 00000000..a7be8981
Binary files /dev/null and b/static/images/peer-review/peer-review-partners-process.png differ
diff --git a/static/images/peer-review/peer-review-partners-process.webp b/static/images/peer-review/peer-review-partners-process.webp
new file mode 100644
index 00000000..d3d12599
Binary files /dev/null and b/static/images/peer-review/peer-review-partners-process.webp differ
diff --git a/static/images/peer-review/peer-review-submit-issue.gif b/static/images/peer-review/peer-review-submit-issue.gif
new file mode 100644
index 00000000..6d98f8dc
Binary files /dev/null and b/static/images/peer-review/peer-review-submit-issue.gif differ
diff --git a/static/images/peer-review/pyopensci-python-software-peer-review-growth.png b/static/images/peer-review/pyopensci-python-software-peer-review-growth.png
new file mode 100644
index 00000000..790f16c5
Binary files /dev/null and b/static/images/peer-review/pyopensci-python-software-peer-review-growth.png differ
diff --git a/static/images/peer-review/pyopensci-python-software-peer-review-growth.webp b/static/images/peer-review/pyopensci-python-software-peer-review-growth.webp
new file mode 100644
index 00000000..91e078c1
Binary files /dev/null and b/static/images/peer-review/pyopensci-python-software-peer-review-growth.webp differ
diff --git a/static/images/peer-review/pyopensci-software-review-issue-selection.png b/static/images/peer-review/pyopensci-software-review-issue-selection.png
new file mode 100644
index 00000000..bf99ea15
Binary files /dev/null and b/static/images/peer-review/pyopensci-software-review-issue-selection.png differ
diff --git a/static/images/peer-review/pyopensci-software-review-issue-selection.webp b/static/images/peer-review/pyopensci-software-review-issue-selection.webp
new file mode 100644
index 00000000..f13768e2
Binary files /dev/null and b/static/images/peer-review/pyopensci-software-review-issue-selection.webp differ
diff --git a/static/images/peer-review/pyos-eic-rotation-2024.png b/static/images/peer-review/pyos-eic-rotation-2024.png
new file mode 100644
index 00000000..5e99032f
Binary files /dev/null and b/static/images/peer-review/pyos-eic-rotation-2024.png differ
diff --git a/static/images/peer-review/pyos-eic-rotation-2024.webp b/static/images/peer-review/pyos-eic-rotation-2024.webp
new file mode 100644
index 00000000..ed67f497
Binary files /dev/null and b/static/images/peer-review/pyos-eic-rotation-2024.webp differ
diff --git a/static/images/peer-review/pyos-joss-peer-review.png b/static/images/peer-review/pyos-joss-peer-review.png
new file mode 100644
index 00000000..b46906b8
Binary files /dev/null and b/static/images/peer-review/pyos-joss-peer-review.png differ
diff --git a/static/images/peer-review/pyos-joss-peer-review.webp b/static/images/peer-review/pyos-joss-peer-review.webp
new file mode 100644
index 00000000..2de3d83f
Binary files /dev/null and b/static/images/peer-review/pyos-joss-peer-review.webp differ
diff --git a/static/images/peer-review/pyos-partnerships-peer-review.png b/static/images/peer-review/pyos-partnerships-peer-review.png
new file mode 100644
index 00000000..b1868943
Binary files /dev/null and b/static/images/peer-review/pyos-partnerships-peer-review.png differ
diff --git a/static/images/peer-review/pyos-partnerships-peer-review.webp b/static/images/peer-review/pyos-partnerships-peer-review.webp
new file mode 100644
index 00000000..45f8d4e5
Binary files /dev/null and b/static/images/peer-review/pyos-partnerships-peer-review.webp differ
diff --git a/static/images/peer-review/submit-software-ui.png b/static/images/peer-review/submit-software-ui.png
new file mode 100644
index 00000000..c9e2c0c7
Binary files /dev/null and b/static/images/peer-review/submit-software-ui.png differ
diff --git a/static/images/peer-review/submit-software-ui.webp b/static/images/peer-review/submit-software-ui.webp
new file mode 100644
index 00000000..460ce5b7
Binary files /dev/null and b/static/images/peer-review/submit-software-ui.webp differ
diff --git a/static/images/people-building-blocks.jpg b/static/images/people-building-blocks.jpg
new file mode 100644
index 00000000..8d2161db
Binary files /dev/null and b/static/images/people-building-blocks.jpg differ
diff --git a/static/images/people/Inessa-NumFocus-award-fall-2024.png b/static/images/people/Inessa-NumFocus-award-fall-2024.png
new file mode 100644
index 00000000..16112bf6
Binary files /dev/null and b/static/images/people/Inessa-NumFocus-award-fall-2024.png differ
diff --git a/static/images/people/Inessa-NumFocus-award-fall-2024.webp b/static/images/people/Inessa-NumFocus-award-fall-2024.webp
new file mode 100644
index 00000000..2ac69441
Binary files /dev/null and b/static/images/people/Inessa-NumFocus-award-fall-2024.webp differ
diff --git a/static/images/people/anita-graser.png b/static/images/people/anita-graser.png
new file mode 100644
index 00000000..1ad549c4
Binary files /dev/null and b/static/images/people/anita-graser.png differ
diff --git a/static/images/people/anita-graser.webp b/static/images/people/anita-graser.webp
new file mode 100644
index 00000000..e36c4d26
Binary files /dev/null and b/static/images/people/anita-graser.webp differ
diff --git a/static/images/people/bof-scipy-2025.png b/static/images/people/bof-scipy-2025.png
new file mode 100644
index 00000000..cb57cdc3
Binary files /dev/null and b/static/images/people/bof-scipy-2025.png differ
diff --git a/static/images/people/bof-scipy-2025.webp b/static/images/people/bof-scipy-2025.webp
new file mode 100644
index 00000000..b0331e91
Binary files /dev/null and b/static/images/people/bof-scipy-2025.webp differ
diff --git a/static/images/people/brianne-wilhelmi.jpeg b/static/images/people/brianne-wilhelmi.jpeg
new file mode 100644
index 00000000..5473eac7
Binary files /dev/null and b/static/images/people/brianne-wilhelmi.jpeg differ
diff --git a/static/images/people/carlos-ramos.jpg b/static/images/people/carlos-ramos.jpg
new file mode 100644
index 00000000..1cec4058
Binary files /dev/null and b/static/images/people/carlos-ramos.jpg differ
diff --git a/static/images/people/eliot-w-robson.jpg b/static/images/people/eliot-w-robson.jpg
new file mode 100644
index 00000000..717acda3
Binary files /dev/null and b/static/images/people/eliot-w-robson.jpg differ
diff --git a/static/images/people/eric-ma-headshot.jpeg b/static/images/people/eric-ma-headshot.jpeg
new file mode 100644
index 00000000..248d67a5
Binary files /dev/null and b/static/images/people/eric-ma-headshot.jpeg differ
diff --git a/static/images/people/jeremiah-paige.jpg b/static/images/people/jeremiah-paige.jpg
new file mode 100644
index 00000000..00a7a80d
Binary files /dev/null and b/static/images/people/jeremiah-paige.jpg differ
diff --git a/static/images/people/jesse-headshot-bandw.jpg b/static/images/people/jesse-headshot-bandw.jpg
new file mode 100644
index 00000000..cf7c8a39
Binary files /dev/null and b/static/images/people/jesse-headshot-bandw.jpg differ
diff --git a/static/images/people/leah-wasser-pyopensci-leadership.jpg b/static/images/people/leah-wasser-pyopensci-leadership.jpg
new file mode 100644
index 00000000..cc8fbc2b
Binary files /dev/null and b/static/images/people/leah-wasser-pyopensci-leadership.jpg differ
diff --git a/static/images/people/leah-wasser/headshot.jpg b/static/images/people/leah-wasser/headshot.jpg
new file mode 100644
index 00000000..cc8fbc2b
Binary files /dev/null and b/static/images/people/leah-wasser/headshot.jpg differ
diff --git a/static/images/people/mandy-moore-headshot.png b/static/images/people/mandy-moore-headshot.png
new file mode 100644
index 00000000..1e0ffc26
Binary files /dev/null and b/static/images/people/mandy-moore-headshot.png differ
diff --git a/static/images/people/mandy-moore-headshot.webp b/static/images/people/mandy-moore-headshot.webp
new file mode 100644
index 00000000..733bc8e0
Binary files /dev/null and b/static/images/people/mandy-moore-headshot.webp differ
diff --git a/static/images/people/niels-bantilan-pyopensci.jpg b/static/images/people/niels-bantilan-pyopensci.jpg
new file mode 100644
index 00000000..7333da1e
Binary files /dev/null and b/static/images/people/niels-bantilan-pyopensci.jpg differ
diff --git a/static/images/people/patrick-j-roddy.jpg b/static/images/people/patrick-j-roddy.jpg
new file mode 100644
index 00000000..36ecd874
Binary files /dev/null and b/static/images/people/patrick-j-roddy.jpg differ
diff --git a/static/images/people/pycon-2023-mentored-sprints-pyopensci.png b/static/images/people/pycon-2023-mentored-sprints-pyopensci.png
new file mode 100644
index 00000000..d5fc3524
Binary files /dev/null and b/static/images/people/pycon-2023-mentored-sprints-pyopensci.png differ
diff --git a/static/images/people/pycon-2023-mentored-sprints-pyopensci.webp b/static/images/people/pycon-2023-mentored-sprints-pyopensci.webp
new file mode 100644
index 00000000..c29ce320
Binary files /dev/null and b/static/images/people/pycon-2023-mentored-sprints-pyopensci.webp differ
diff --git a/static/images/people/pyopensc-executive-council.png b/static/images/people/pyopensc-executive-council.png
new file mode 100644
index 00000000..4d58d120
Binary files /dev/null and b/static/images/people/pyopensc-executive-council.png differ
diff --git a/static/images/people/pyopensc-executive-council.webp b/static/images/people/pyopensc-executive-council.webp
new file mode 100644
index 00000000..41c57d2f
Binary files /dev/null and b/static/images/people/pyopensc-executive-council.webp differ
diff --git a/static/images/people/pyopensci-sprint-pycon-2023.png b/static/images/people/pyopensci-sprint-pycon-2023.png
new file mode 100644
index 00000000..326f0bbc
Binary files /dev/null and b/static/images/people/pyopensci-sprint-pycon-2023.png differ
diff --git a/static/images/people/pyopensci-sprint-pycon-2023.webp b/static/images/people/pyopensci-sprint-pycon-2023.webp
new file mode 100644
index 00000000..20218a14
Binary files /dev/null and b/static/images/people/pyopensci-sprint-pycon-2023.webp differ
diff --git a/static/images/people/python-packaging-guide.png b/static/images/people/python-packaging-guide.png
new file mode 100644
index 00000000..da5b7013
Binary files /dev/null and b/static/images/people/python-packaging-guide.png differ
diff --git a/static/images/people/python-packaging-guide.webp b/static/images/people/python-packaging-guide.webp
new file mode 100644
index 00000000..686b533e
Binary files /dev/null and b/static/images/people/python-packaging-guide.webp differ
diff --git a/static/images/people/raktim-mukhopadhyay.jpg b/static/images/people/raktim-mukhopadhyay.jpg
new file mode 100644
index 00000000..01592c37
Binary files /dev/null and b/static/images/people/raktim-mukhopadhyay.jpg differ
diff --git a/static/images/people/scipy-sprint-2026.png b/static/images/people/scipy-sprint-2026.png
new file mode 100644
index 00000000..4b1490fe
Binary files /dev/null and b/static/images/people/scipy-sprint-2026.png differ
diff --git a/static/images/people/scipy-sprint-2026.webp b/static/images/people/scipy-sprint-2026.webp
new file mode 100644
index 00000000..cdf66b4d
Binary files /dev/null and b/static/images/people/scipy-sprint-2026.webp differ
diff --git a/static/images/people/testimonial-fatima-pardo.png b/static/images/people/testimonial-fatima-pardo.png
new file mode 100644
index 00000000..565449bb
Binary files /dev/null and b/static/images/people/testimonial-fatima-pardo.png differ
diff --git a/static/images/pyopensci-general/pyopensci-by-the-numbers-2024.png b/static/images/pyopensci-general/pyopensci-by-the-numbers-2024.png
new file mode 100644
index 00000000..cb042ab5
Binary files /dev/null and b/static/images/pyopensci-general/pyopensci-by-the-numbers-2024.png differ
diff --git a/static/images/pyopensci-general/pyopensci-by-the-numbers-2024.webp b/static/images/pyopensci-general/pyopensci-by-the-numbers-2024.webp
new file mode 100644
index 00000000..0a38bcab
Binary files /dev/null and b/static/images/pyopensci-general/pyopensci-by-the-numbers-2024.webp differ
diff --git a/static/images/pyopensci-general/pyopensci-flower-pillars.png b/static/images/pyopensci-general/pyopensci-flower-pillars.png
new file mode 100644
index 00000000..72999193
Binary files /dev/null and b/static/images/pyopensci-general/pyopensci-flower-pillars.png differ
diff --git a/static/images/pyopensci-general/pyopensci-flower-pillars.webp b/static/images/pyopensci-general/pyopensci-flower-pillars.webp
new file mode 100644
index 00000000..e0d31b29
Binary files /dev/null and b/static/images/pyopensci-general/pyopensci-flower-pillars.webp differ
diff --git a/static/images/pyopensci-general/pyopensci-github-prs-issues.png b/static/images/pyopensci-general/pyopensci-github-prs-issues.png
new file mode 100644
index 00000000..ea391b63
Binary files /dev/null and b/static/images/pyopensci-general/pyopensci-github-prs-issues.png differ
diff --git a/static/images/pyopensci-general/pyopensci-github-prs-issues.webp b/static/images/pyopensci-general/pyopensci-github-prs-issues.webp
new file mode 100644
index 00000000..a50528cb
Binary files /dev/null and b/static/images/pyopensci-general/pyopensci-github-prs-issues.webp differ
diff --git a/static/images/pyopensci-general/pyopensci-iterative-evaluation-program-design.png b/static/images/pyopensci-general/pyopensci-iterative-evaluation-program-design.png
new file mode 100644
index 00000000..bb8bb266
Binary files /dev/null and b/static/images/pyopensci-general/pyopensci-iterative-evaluation-program-design.png differ
diff --git a/static/images/pyopensci-general/pyopensci-iterative-evaluation-program-design.webp b/static/images/pyopensci-general/pyopensci-iterative-evaluation-program-design.webp
new file mode 100644
index 00000000..7fd721a2
Binary files /dev/null and b/static/images/pyopensci-general/pyopensci-iterative-evaluation-program-design.webp differ
diff --git a/static/images/pyopensci-general/pyopensci-timeline2019-2024.png b/static/images/pyopensci-general/pyopensci-timeline2019-2024.png
new file mode 100644
index 00000000..9dd953d1
Binary files /dev/null and b/static/images/pyopensci-general/pyopensci-timeline2019-2024.png differ
diff --git a/static/images/pyopensci-general/pyopensci-timeline2019-2024.webp b/static/images/pyopensci-general/pyopensci-timeline2019-2024.webp
new file mode 100644
index 00000000..cc17bce0
Binary files /dev/null and b/static/images/pyopensci-general/pyopensci-timeline2019-2024.webp differ
diff --git a/static/images/pyopensci-general/pyos-by-the-numbers-2024.png b/static/images/pyopensci-general/pyos-by-the-numbers-2024.png
new file mode 100644
index 00000000..1e4d199b
Binary files /dev/null and b/static/images/pyopensci-general/pyos-by-the-numbers-2024.png differ
diff --git a/static/images/pyopensci-open-source-foundation-open-science.png b/static/images/pyopensci-open-source-foundation-open-science.png
new file mode 100644
index 00000000..ecf4bee3
Binary files /dev/null and b/static/images/pyopensci-open-source-foundation-open-science.png differ
diff --git a/static/images/pyopensci-packages/snyk-pandera-python-package-metrics.png b/static/images/pyopensci-packages/snyk-pandera-python-package-metrics.png
new file mode 100644
index 00000000..e286968a
Binary files /dev/null and b/static/images/pyopensci-packages/snyk-pandera-python-package-metrics.png differ
diff --git a/static/images/pyopensci-packages/snyk-pygmt-python-package-metrics.png b/static/images/pyopensci-packages/snyk-pygmt-python-package-metrics.png
new file mode 100644
index 00000000..9f55cdb2
Binary files /dev/null and b/static/images/pyopensci-packages/snyk-pygmt-python-package-metrics.png differ
diff --git a/static/images/pyopensci-pillars-flower.png b/static/images/pyopensci-pillars-flower.png
new file mode 100644
index 00000000..b96824fe
Binary files /dev/null and b/static/images/pyopensci-pillars-flower.png differ
diff --git a/static/images/pyopensci-programs.png b/static/images/pyopensci-programs.png
new file mode 100644
index 00000000..d251f71d
Binary files /dev/null and b/static/images/pyopensci-programs.png differ
diff --git a/static/images/pyopensci-square-logo-dark-purple.png b/static/images/pyopensci-square-logo-dark-purple.png
new file mode 100644
index 00000000..4d58d120
Binary files /dev/null and b/static/images/pyopensci-square-logo-dark-purple.png differ
diff --git a/static/images/pyopensci-stickers.png b/static/images/pyopensci-stickers.png
new file mode 100644
index 00000000..6147117b
Binary files /dev/null and b/static/images/pyopensci-stickers.png differ
diff --git a/static/images/pyos-days-python-environment-failed.png b/static/images/pyos-days-python-environment-failed.png
new file mode 100644
index 00000000..e38e6a76
Binary files /dev/null and b/static/images/pyos-days-python-environment-failed.png differ
diff --git a/static/images/pyos-partnerships.png b/static/images/pyos-partnerships.png
new file mode 100644
index 00000000..1a41672f
Binary files /dev/null and b/static/images/pyos-partnerships.png differ
diff --git a/static/images/python-package-tools-decision-tree.png b/static/images/python-package-tools-decision-tree.png
new file mode 100644
index 00000000..8908e9cf
Binary files /dev/null and b/static/images/python-package-tools-decision-tree.png differ
diff --git a/static/images/python-packages/dont-talk-about-peps-pyopensci.jpeg b/static/images/python-packages/dont-talk-about-peps-pyopensci.jpeg
new file mode 100644
index 00000000..71b6b3b7
Binary files /dev/null and b/static/images/python-packages/dont-talk-about-peps-pyopensci.jpeg differ
diff --git a/static/images/python-packages/lion-meme-pyopensci.jpeg b/static/images/python-packages/lion-meme-pyopensci.jpeg
new file mode 100644
index 00000000..52ca3657
Binary files /dev/null and b/static/images/python-packages/lion-meme-pyopensci.jpeg differ
diff --git a/static/images/python-packages/pyOS-package-guide-contributors.png b/static/images/python-packages/pyOS-package-guide-contributors.png
new file mode 100644
index 00000000..3644c078
Binary files /dev/null and b/static/images/python-packages/pyOS-package-guide-contributors.png differ
diff --git a/static/images/python-packages/pycon-packaging-review-process.png b/static/images/python-packages/pycon-packaging-review-process.png
new file mode 100644
index 00000000..7ca98d46
Binary files /dev/null and b/static/images/python-packages/pycon-packaging-review-process.png differ
diff --git a/static/images/python-packages/python-ecosystem-jake-vanderploss-pycon-2017.png b/static/images/python-packages/python-ecosystem-jake-vanderploss-pycon-2017.png
new file mode 100644
index 00000000..0a95d40a
Binary files /dev/null and b/static/images/python-packages/python-ecosystem-jake-vanderploss-pycon-2017.png differ
diff --git a/static/images/python-packaging-guide.png b/static/images/python-packaging-guide.png
new file mode 100644
index 00000000..f054af43
Binary files /dev/null and b/static/images/python-packaging-guide.png differ
diff --git a/static/images/python-packaging/create-github-environment.gif b/static/images/python-packaging/create-github-environment.gif
new file mode 100644
index 00000000..c279ed96
Binary files /dev/null and b/static/images/python-packaging/create-github-environment.gif differ
diff --git a/static/images/python-packaging/dont-talk-about-peps-pyopensci.jpeg b/static/images/python-packaging/dont-talk-about-peps-pyopensci.jpeg
new file mode 100644
index 00000000..71b6b3b7
Binary files /dev/null and b/static/images/python-packaging/dont-talk-about-peps-pyopensci.jpeg differ
diff --git a/static/images/python-packaging/github-action-environment-pypi.png b/static/images/python-packaging/github-action-environment-pypi.png
new file mode 100644
index 00000000..822ba25a
Binary files /dev/null and b/static/images/python-packaging/github-action-environment-pypi.png differ
diff --git a/static/images/python-packaging/github-action-environment-pypi.webp b/static/images/python-packaging/github-action-environment-pypi.webp
new file mode 100644
index 00000000..ede3925d
Binary files /dev/null and b/static/images/python-packaging/github-action-environment-pypi.webp differ
diff --git a/static/images/python-packaging/have-you-created-python-package-scipy-24.png b/static/images/python-packaging/have-you-created-python-package-scipy-24.png
new file mode 100644
index 00000000..c98da543
Binary files /dev/null and b/static/images/python-packaging/have-you-created-python-package-scipy-24.png differ
diff --git a/static/images/python-packaging/lion-meme-pyopensci.jpeg b/static/images/python-packaging/lion-meme-pyopensci.jpeg
new file mode 100644
index 00000000..52ca3657
Binary files /dev/null and b/static/images/python-packaging/lion-meme-pyopensci.jpeg differ
diff --git a/static/images/python-packaging/packaging-101-outline.png b/static/images/python-packaging/packaging-101-outline.png
new file mode 100644
index 00000000..d3c2053b
Binary files /dev/null and b/static/images/python-packaging/packaging-101-outline.png differ
diff --git a/static/images/python-packaging/packaging-101-outline.webp b/static/images/python-packaging/packaging-101-outline.webp
new file mode 100644
index 00000000..1de6cf31
Binary files /dev/null and b/static/images/python-packaging/packaging-101-outline.webp differ
diff --git a/static/images/python-packaging/publish-python-package-pypi-conda.png b/static/images/python-packaging/publish-python-package-pypi-conda.png
new file mode 100644
index 00000000..953b5666
Binary files /dev/null and b/static/images/python-packaging/publish-python-package-pypi-conda.png differ
diff --git a/static/images/python-packaging/pyOS-package-guide-contributors.png b/static/images/python-packaging/pyOS-package-guide-contributors.png
new file mode 100644
index 00000000..3644c078
Binary files /dev/null and b/static/images/python-packaging/pyOS-package-guide-contributors.png differ
diff --git a/static/images/python-packaging/pycon-packaging-review-process.png b/static/images/python-packaging/pycon-packaging-review-process.png
new file mode 100644
index 00000000..7ca98d46
Binary files /dev/null and b/static/images/python-packaging/pycon-packaging-review-process.png differ
diff --git a/static/images/python-packaging/pyopensci-python-package-tools-word-cloud-2024.png b/static/images/python-packaging/pyopensci-python-package-tools-word-cloud-2024.png
new file mode 100644
index 00000000..07578656
Binary files /dev/null and b/static/images/python-packaging/pyopensci-python-package-tools-word-cloud-2024.png differ
diff --git a/static/images/python-packaging/python-ecosystem-jake-vanderploss-pycon-2017.png b/static/images/python-packaging/python-ecosystem-jake-vanderploss-pycon-2017.png
new file mode 100644
index 00000000..0a95d40a
Binary files /dev/null and b/static/images/python-packaging/python-ecosystem-jake-vanderploss-pycon-2017.png differ
diff --git a/static/images/python-packaging/successfully-created-python-package-scipy-24.png b/static/images/python-packaging/successfully-created-python-package-scipy-24.png
new file mode 100644
index 00000000..e51f3188
Binary files /dev/null and b/static/images/python-packaging/successfully-created-python-package-scipy-24.png differ
diff --git a/static/images/python-packaging/trusted-publisher-form.png b/static/images/python-packaging/trusted-publisher-form.png
new file mode 100644
index 00000000..ffbc33b7
Binary files /dev/null and b/static/images/python-packaging/trusted-publisher-form.png differ
diff --git a/static/images/python-packaging/trusted-publisher-form.webp b/static/images/python-packaging/trusted-publisher-form.webp
new file mode 100644
index 00000000..de45575c
Binary files /dev/null and b/static/images/python-packaging/trusted-publisher-form.webp differ
diff --git a/static/images/python-packaging/trusted-publisher-manage.png b/static/images/python-packaging/trusted-publisher-manage.png
new file mode 100644
index 00000000..6b8c5d5d
Binary files /dev/null and b/static/images/python-packaging/trusted-publisher-manage.png differ
diff --git a/static/images/python-packaging/trusted-publisher-manage.webp b/static/images/python-packaging/trusted-publisher-manage.webp
new file mode 100644
index 00000000..c228afec
Binary files /dev/null and b/static/images/python-packaging/trusted-publisher-manage.webp differ
diff --git a/static/images/python-packaging/trusted-publisher-pypi-github.png b/static/images/python-packaging/trusted-publisher-pypi-github.png
new file mode 100644
index 00000000..b2c5eb11
Binary files /dev/null and b/static/images/python-packaging/trusted-publisher-pypi-github.png differ
diff --git a/static/images/python-packaging/trusted-publisher-pypi-github.webp b/static/images/python-packaging/trusted-publisher-pypi-github.webp
new file mode 100644
index 00000000..fab5edc7
Binary files /dev/null and b/static/images/python-packaging/trusted-publisher-pypi-github.webp differ
diff --git a/static/images/python-software-health/bus-factor-python-package-health.png b/static/images/python-software-health/bus-factor-python-package-health.png
new file mode 100644
index 00000000..ef4647da
Binary files /dev/null and b/static/images/python-software-health/bus-factor-python-package-health.png differ
diff --git a/static/images/python-software-health/healthy-software-repo-file-checks-github.png b/static/images/python-software-health/healthy-software-repo-file-checks-github.png
new file mode 100644
index 00000000..d384716b
Binary files /dev/null and b/static/images/python-software-health/healthy-software-repo-file-checks-github.png differ
diff --git a/static/images/python-software-health/html-proofer-pyopensci-website-checks.png b/static/images/python-software-health/html-proofer-pyopensci-website-checks.png
new file mode 100644
index 00000000..2cd59577
Binary files /dev/null and b/static/images/python-software-health/html-proofer-pyopensci-website-checks.png differ
diff --git a/static/images/quadratik/dash-landing.png b/static/images/quadratik/dash-landing.png
new file mode 100644
index 00000000..7b004e20
Binary files /dev/null and b/static/images/quadratik/dash-landing.png differ
diff --git a/static/images/quadratik/dash-landing.webp b/static/images/quadratik/dash-landing.webp
new file mode 100644
index 00000000..8d2035be
Binary files /dev/null and b/static/images/quadratik/dash-landing.webp differ
diff --git a/static/images/quadratik/dog-cat-segmented.png b/static/images/quadratik/dog-cat-segmented.png
new file mode 100644
index 00000000..d8686611
Binary files /dev/null and b/static/images/quadratik/dog-cat-segmented.png differ
diff --git a/static/images/quadratik/dog-cat-segmented.webp b/static/images/quadratik/dog-cat-segmented.webp
new file mode 100644
index 00000000..a8b70ae9
Binary files /dev/null and b/static/images/quadratik/dog-cat-segmented.webp differ
diff --git a/static/images/quadratik/dog-cat.png b/static/images/quadratik/dog-cat.png
new file mode 100644
index 00000000..47e8a873
Binary files /dev/null and b/static/images/quadratik/dog-cat.png differ
diff --git a/static/images/quadratik/dog-cat.webp b/static/images/quadratik/dog-cat.webp
new file mode 100644
index 00000000..9c2dd37f
Binary files /dev/null and b/static/images/quadratik/dog-cat.webp differ
diff --git a/static/images/quadratik/k-sample-test-results.png b/static/images/quadratik/k-sample-test-results.png
new file mode 100644
index 00000000..f993e1ed
Binary files /dev/null and b/static/images/quadratik/k-sample-test-results.png differ
diff --git a/static/images/quadratik/k-sample-test-results.webp b/static/images/quadratik/k-sample-test-results.webp
new file mode 100644
index 00000000..483b32a3
Binary files /dev/null and b/static/images/quadratik/k-sample-test-results.webp differ
diff --git a/static/images/quadratik/normality-test-results.png b/static/images/quadratik/normality-test-results.png
new file mode 100644
index 00000000..d5501953
Binary files /dev/null and b/static/images/quadratik/normality-test-results.png differ
diff --git a/static/images/quadratik/normality-test-results.webp b/static/images/quadratik/normality-test-results.webp
new file mode 100644
index 00000000..f8e5f294
Binary files /dev/null and b/static/images/quadratik/normality-test-results.webp differ
diff --git a/static/images/quadratik/quadratik-organization.png b/static/images/quadratik/quadratik-organization.png
new file mode 100644
index 00000000..8a2bf6cc
Binary files /dev/null and b/static/images/quadratik/quadratik-organization.png differ
diff --git a/static/images/quadratik/two-sample-test-results.png b/static/images/quadratik/two-sample-test-results.png
new file mode 100644
index 00000000..3f988c7e
Binary files /dev/null and b/static/images/quadratik/two-sample-test-results.png differ
diff --git a/static/images/quadratik/two-sample-test-results.webp b/static/images/quadratik/two-sample-test-results.webp
new file mode 100644
index 00000000..75eb731b
Binary files /dev/null and b/static/images/quadratik/two-sample-test-results.webp differ
diff --git a/static/images/quadratik/uniformity-test-results.png b/static/images/quadratik/uniformity-test-results.png
new file mode 100644
index 00000000..3f5fbde1
Binary files /dev/null and b/static/images/quadratik/uniformity-test-results.png differ
diff --git a/static/images/quadratik/uniformity-test-results.webp b/static/images/quadratik/uniformity-test-results.webp
new file mode 100644
index 00000000..5374c713
Binary files /dev/null and b/static/images/quadratik/uniformity-test-results.webp differ
diff --git a/static/images/quadratik/unit-sphere.png b/static/images/quadratik/unit-sphere.png
new file mode 100644
index 00000000..3799c9e7
Binary files /dev/null and b/static/images/quadratik/unit-sphere.png differ
diff --git a/static/images/quadratik/unit-sphere.webp b/static/images/quadratik/unit-sphere.webp
new file mode 100644
index 00000000..9f724ebc
Binary files /dev/null and b/static/images/quadratik/unit-sphere.webp differ
diff --git a/static/images/quadratik/validation-dog-cat.png b/static/images/quadratik/validation-dog-cat.png
new file mode 100644
index 00000000..84ed2bf5
Binary files /dev/null and b/static/images/quadratik/validation-dog-cat.png differ
diff --git a/static/images/quadratik/validation-dog-cat.webp b/static/images/quadratik/validation-dog-cat.webp
new file mode 100644
index 00000000..32f5f1c8
Binary files /dev/null and b/static/images/quadratik/validation-dog-cat.webp differ
diff --git a/static/images/rdata/dataset.png b/static/images/rdata/dataset.png
new file mode 100644
index 00000000..61e247be
Binary files /dev/null and b/static/images/rdata/dataset.png differ
diff --git a/static/images/rse-2023-packaging-tools.png b/static/images/rse-2023-packaging-tools.png
new file mode 100644
index 00000000..e3451d3c
Binary files /dev/null and b/static/images/rse-2023-packaging-tools.png differ
diff --git a/static/images/sleplet/planck_2018_temp_mask.jpg b/static/images/sleplet/planck_2018_temp_mask.jpg
new file mode 100644
index 00000000..e17cf746
Binary files /dev/null and b/static/images/sleplet/planck_2018_temp_mask.jpg differ
diff --git a/static/images/sleplet/slepian_wavelet_coefficients_homer_3B_2jmin_2j_zoom.png b/static/images/sleplet/slepian_wavelet_coefficients_homer_3B_2jmin_2j_zoom.png
new file mode 100644
index 00000000..36fefd95
Binary files /dev/null and b/static/images/sleplet/slepian_wavelet_coefficients_homer_3B_2jmin_2j_zoom.png differ
diff --git a/static/images/sleplet/slepian_wavelets_south_america_3B_2jmin_2j_L128_res512_real.png b/static/images/sleplet/slepian_wavelets_south_america_3B_2jmin_2j_L128_res512_real.png
new file mode 100644
index 00000000..e5804caf
Binary files /dev/null and b/static/images/sleplet/slepian_wavelets_south_america_3B_2jmin_2j_L128_res512_real.png differ
diff --git a/static/images/swoosh/swoosh-illustrator-bottom.svg b/static/images/swoosh/swoosh-illustrator-bottom.svg
new file mode 100644
index 00000000..43ad0fbe
--- /dev/null
+++ b/static/images/swoosh/swoosh-illustrator-bottom.svg
@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<svg id="Layer_1" xmlns="http://www.w3.org/2000/svg" version="1.1" viewBox="0 0 181 25">
+  <!-- Generator: Adobe Illustrator 30.1.0, SVG Export Plug-In . SVG Version: 2.1.1 Build 136)  -->
+  <path d="M0,19.47V0h181v25s-37.24-12.62-64.83-11.03c-51.37,2.97-35.2,9.13-78.54,4.29" fill="#bdb6d6" isolation="isolate" opacity=".9"/>
+  <path d="M0,0h181v25s-19.06-13.67-62.29-14.66C79.54,12.5,51.71,31.57,0,21.89" fill="#e2dfed"/>
+</svg>
diff --git a/static/images/swoosh/swoosh-illustrator-top.svg b/static/images/swoosh/swoosh-illustrator-top.svg
new file mode 100644
index 00000000..713f5704
--- /dev/null
+++ b/static/images/swoosh/swoosh-illustrator-top.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<svg id="Layer_1" xmlns="http://www.w3.org/2000/svg" version="1.1" viewBox="0 0 181.01 20.87">
+  <!-- Generator: Adobe Illustrator 30.1.0, SVG Export Plug-In . SVG Version: 2.1.1 Build 136)  -->
+  <path d="M14.63,19.26l166.28,1.6.1-20.87c-15.8,4.47-34.85,12.22-69.56,10.46C84.51,9.1,56,1.72,56,1.72c0,0-17.53-2.74-29.97,2.84-12.43,5.58-11.41,14.7-11.41,14.7h0Z" fill="#bdb6d6" isolation="isolate" opacity=".9"/>
+  <path d="M181.01.04c-35.01,7.3-44.47,12.92-64.78,13.27C79.45,13.95,76.55-8.95-2.41,4.75-11.28,6.29.07,20.87.09,20.88h0s180.91-.01,180.91-.01c0,0,.01-13.48,0-20.83" fill="#e2dfed"/>
+  <path d="M181,.75" fill="#e2dfed"/>
+  <g id="flower">
+    <path d="M21.21,5.62c-.06,0-.12-.04-.14-.1-.03-.08.02-.16.09-.18s.16.02.18.09c.02.06,0,.13-.05.16l.1.31c.11-.03.22-.03.32-.01.1-.17.13-.41.05-.64-.13-.38-.81-.5-.81-.5,0,0-.47.5-.35.88.08.23.24.4.43.48.07-.08.16-.14.26-.19l-.1-.31h.02Z" fill="#b4abd8"/>
+    <path d="M20.87,6.63h-.31c-.02.06-.07.1-.14.11-.08,0-.15-.06-.15-.14s.06-.15.14-.15c.06,0,.12.04.14.1h.31c0-.11.04-.22.1-.32-.13-.15-.35-.25-.59-.25-.4,0-.72.62-.72.62,0,0,.33.61.73.6.24,0,.44-.1.58-.24-.02-.04-.04-.08-.06-.13-.02-.07-.03-.13-.04-.2h.01Z" fill="#b4abd8"/>
+    <path d="M21.32,7.57s.07.1.05.16c-.02.08-.11.12-.18.1-.08-.02-.12-.11-.1-.18.02-.06.08-.1.14-.1l.09-.28c-.11-.04-.2-.11-.28-.2-.18.08-.33.26-.4.48-.12.38.36.88.36.88,0,0,.68-.13.8-.51.07-.22.05-.44-.05-.61-.12.03-.24.03-.35,0l-.09.28v-.02Z" fill="#b4abd8"/>
+    <path d="M22.21,6.97l.24.17s.12-.04.17,0c.07.05.08.14.03.2-.05.07-.14.08-.2.03-.05-.04-.07-.1-.05-.16l-.23-.17c-.07.09-.17.17-.28.22.03.19.14.38.33.51.33.23.95-.07.95-.07,0,0,.09-.68-.24-.92-.19-.14-.41-.18-.61-.14,0,.12-.04.23-.1.33h-.01Z" fill="#b4abd8"/>
+    <path d="M22.18,5.37c-.2.14-.31.35-.32.55.1.04.19.11.27.19l.25-.19c-.02-.06,0-.13.05-.16.06-.05.16-.03.2.03.05.06.03.16-.03.2-.05.04-.12.04-.17,0l-.25.18c.04.05.07.11.09.18.02.05.03.09.03.14.19.04.42-.01.61-.15.32-.24.22-.92.22-.92,0,0-.62-.29-.95-.05h0Z" fill="#b4abd8"/>
+    <path d="M21.45,6.18c.23-.08.48.05.55.28s-.05.48-.28.56-.48-.05-.56-.28.05-.48.28-.56M21.4,6.06c-.29.1-.45.42-.35.71s.42.45.71.35.45-.42.35-.71-.42-.45-.71-.35Z" fill="#b4abd8"/>
+    <path d="M37.5,2.53c-.06-.02-.1-.07-.1-.14,0-.08.07-.15.15-.15s.15.07.15.15c0,.07-.04.12-.1.14v.32c.11,0,.22.04.31.09.15-.13.25-.35.25-.59,0-.4-.61-.73-.61-.73,0,0-.61.33-.61.73,0,.24.1.46.25.59.09-.05.2-.09.31-.09v-.32h0Z" fill="#b4abd8"/>
+    <path d="M36.85,3.38l-.3-.1s-.1.07-.16.05c-.08-.03-.12-.11-.09-.18.03-.08.11-.12.18-.09.06.02.1.08.1.14l.3.1c.04-.1.11-.19.19-.26-.08-.19-.25-.35-.48-.42-.38-.12-.88.35-.88.35,0,0,.12.68.51.8.22.07.45.05.62-.05,0-.05,0-.09,0-.14,0-.07,0-.13.03-.2h0Z" fill="#b4abd8"/>
+    <path d="M36.98,4.41s.04.12,0,.17c-.05.07-.14.08-.2.03-.07-.05-.08-.14-.03-.2.04-.05.1-.07.16-.05l.17-.23c-.09-.08-.16-.17-.2-.28-.19.02-.39.14-.53.33-.24.33.06.95.06.95,0,0,.68.09.92-.23.13-.19.18-.4.15-.59-.12,0-.24-.05-.33-.12l-.17.23h0Z" fill="#b4abd8"/>
+    <path d="M38.01,4.12l.17.23c.06-.02.12,0,.16.05.05.07.03.16-.03.2-.07.05-.16.03-.2-.03-.04-.05-.04-.12,0-.17l-.17-.23c-.1.06-.21.1-.33.12-.03.19.02.41.15.59.24.33.92.23.92.23,0,0,.3-.62.06-.95-.14-.19-.33-.3-.53-.33-.04.11-.11.21-.2.28h0Z" fill="#b4abd8"/>
+    <path d="M38.5,2.61c-.23.07-.41.24-.48.42.08.07.15.16.19.26l.3-.1c0-.06.04-.12.1-.14.08-.03.16.02.18.09.03.08-.02.16-.09.18-.06.02-.13,0-.16-.05l-.3.1c.02.06.03.13.03.2,0,.05,0,.1,0,.14.17.1.4.12.62.05.38-.12.51-.8.51-.8,0,0-.5-.48-.88-.35h0Z" fill="#b4abd8"/>
+    <path d="M37.55,3.14c.24,0,.44.2.44.44s-.2.44-.44.44-.44-.2-.44-.44.2-.44.44-.44M37.55,3.02c-.31,0-.56.25-.56.56s.25.56.56.56.56-.25.56-.56-.25-.56-.56-.56Z" fill="#b4abd8"/>
+    <path d="M51.35,6.28s-.08-.1-.06-.16c.02-.08.1-.12.18-.1s.12.1.1.18c-.02.06-.07.1-.14.11l-.09.31c.11.04.2.1.27.17.18-.08.34-.26.41-.5.11-.39-.38-.87-.38-.87,0,0-.68.14-.79.53-.07.23-.03.47.08.64.1-.02.21-.03.32,0l.09-.31h.01Z" fill="#b4abd8"/>
+    <path d="M50.49,6.91l-.26-.17s-.12.04-.17,0c-.07-.05-.08-.14-.04-.2.05-.07.14-.08.2-.04.05.04.08.1.06.16l.26.17c.07-.09.16-.15.26-.2-.02-.2-.15-.4-.35-.54-.33-.23-.95.09-.95.09,0,0-.07.69.26.91.19.13.42.17.61.13,0-.05,0-.09.03-.14.02-.07.05-.13.08-.18h0Z" fill="#b4abd8"/>
+    <path d="M50.33,7.94c.02.06,0,.13-.05.16-.06.05-.16.04-.2-.03-.05-.06-.04-.16.03-.21.05-.04.12-.04.17,0l.23-.18c-.06-.1-.1-.21-.12-.33-.19-.03-.41.02-.6.17-.32.25-.2.93-.2.93,0,0,.63.28.95.03.18-.14.29-.34.31-.53-.11-.04-.21-.12-.29-.2l-.23.18h0Z" fill="#b4abd8"/>
+    <path d="M51.4,7.95l.1.27c.06,0,.12.03.14.1.03.08,0,.16-.09.19s-.16-.01-.19-.09c-.02-.06,0-.13.05-.16l-.1-.27c-.11.03-.23.04-.35.02-.08.17-.1.39-.02.61.14.38.82.48.82.48,0,0,.46-.51.33-.89-.08-.22-.24-.39-.42-.46-.07.09-.17.17-.27.21h0Z" fill="#b4abd8"/>
+    <path d="M52.29,6.63c-.24,0-.46.11-.58.27.06.09.1.2.11.31h.31c.02-.07.07-.11.14-.11.08,0,.15.06.15.14s-.06.15-.14.15c-.06,0-.12-.04-.14-.1h-.31c0,.07,0,.14-.03.21,0,.05-.03.09-.05.13.14.14.35.23.58.22.4-.01.71-.63.71-.63,0,0-.35-.6-.75-.58h0Z" fill="#b4abd8"/>
+    <path d="M51.23,6.88c.23.07.37.31.3.54s-.31.37-.54.3-.37-.31-.3-.54.31-.37.54-.3M51.26,6.76c-.3-.09-.61.08-.69.38s.09.61.38.69.61-.08.69-.38-.08-.61-.38-.69Z" fill="#b4abd8"/>
+  </g>
+</svg>
diff --git a/static/images/talks/david-nicholson-crowsetta-lightning-pycon2023.png b/static/images/talks/david-nicholson-crowsetta-lightning-pycon2023.png
new file mode 100644
index 00000000..8780c0fa
Binary files /dev/null and b/static/images/talks/david-nicholson-crowsetta-lightning-pycon2023.png differ
diff --git a/static/images/talks/intro-slide-david-nicholson-crowsetta-lightning-pycon2023.png b/static/images/talks/intro-slide-david-nicholson-crowsetta-lightning-pycon2023.png
new file mode 100644
index 00000000..e36fc1b9
Binary files /dev/null and b/static/images/talks/intro-slide-david-nicholson-crowsetta-lightning-pycon2023.png differ
diff --git a/static/site.webmanifest b/static/site.webmanifest
new file mode 100644
index 00000000..d1c9bea0
--- /dev/null
+++ b/static/site.webmanifest
@@ -0,0 +1,20 @@
+{
+  "name": "pyOpenSci",
+  "short_name": "pyOpenSci",
+  "description": "pyOpenSci broadens participation in scientific open source.",
+  "icons": [
+    {
+      "src": "/android-chrome-192x192.png",
+      "sizes": "192x192",
+      "type": "image/png"
+    },
+    {
+      "src": "/android-chrome-512x512.png",
+      "sizes": "512x512",
+      "type": "image/png"
+    }
+  ],
+  "theme_color": "#2E6060",
+  "background_color": "#ffffff",
+  "display": "standalone"
+}
diff --git a/themes/clean-hugo/archetypes/blog.md b/themes/clean-hugo/archetypes/blog.md
new file mode 100644
index 00000000..7f79afff
--- /dev/null
+++ b/themes/clean-hugo/archetypes/blog.md
@@ -0,0 +1,12 @@
+---
+title: "How to Create a Full Width Flowing Blog Post or Page with Sections" of Different Colors""
+date: {{ .Date }}
+draft: true
+excerpt: ""
+# JSON-LD: BlogPosting is output automatically for content in the blog section.
+# Optional for richer snippets: author (string), image (src/alt), description (or use excerpt).
+author: "Leah Wasser"
+# image:
+#   src: "images/your-image.webp"
+#   alt: "Description for accessibility"
+---
diff --git a/themes/clean-hugo/archetypes/default.md b/themes/clean-hugo/archetypes/default.md
new file mode 100644
index 00000000..c6f3fcef
--- /dev/null
+++ b/themes/clean-hugo/archetypes/default.md
@@ -0,0 +1,5 @@
++++
+title = '{{ replace .File.ContentBaseName "-" " " | title }}'
+date = {{ .Date }}
+draft = true
++++
diff --git a/themes/clean-hugo/archetypes/documentation.md b/themes/clean-hugo/archetypes/documentation.md
new file mode 100644
index 00000000..cae1ce8b
--- /dev/null
+++ b/themes/clean-hugo/archetypes/documentation.md
@@ -0,0 +1,12 @@
+---
+title: ""
+date: {{ .Date }}
+draft: true
+layout: "docs"
+weight: 0
+excerpt: ""
+header:
+  color: "primaryDark"
+# JSON-LD: TechArticle (article rich results). Set tech_article: true or use cascade in hugo.toml for path.
+tech_article: true
+---
diff --git a/themes/clean-hugo/archetypes/gallery.md b/themes/clean-hugo/archetypes/gallery.md
new file mode 100644
index 00000000..48dd9eb8
--- /dev/null
+++ b/themes/clean-hugo/archetypes/gallery.md
@@ -0,0 +1,20 @@
++++
+title = '{{ replace .File.ContentBaseName "-" " " | title }}'
+date = {{ .Date }}
+excerpt = ""
+groups = [] # Add group names for filtering (e.g., silver, green, variegated, small leaf)
+tags = []
+
+# Populate the hero with a title, excerpt and image
+[ hero ]
+image = "image.jpg"
+subtitle = "A description of this gallery item."
+
+# Optional--explicit list of images
+[image_roles]
+flower = "flower.jpg"
+habit = "habit.jpg"
+images = []
++++
+
+A short summary or notes about this item. Add more details below.
diff --git a/themes/clean-hugo/assets/css/_admonition.scss b/themes/clean-hugo/assets/css/_admonition.scss
new file mode 100644
index 00000000..b393b2c2
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_admonition.scss
@@ -0,0 +1,88 @@
+  /* Admonition Component */
+  .admonition {
+    border-left-width: 4px;
+    border-radius: 0 1rem 1rem 0;
+    padding: 2rem;
+    box-shadow: $shadow-md;
+    border: 1px solid;
+    border-left-width: 4px;
+    margin: 3rem 0;
+    display: flex;
+    gap: 0.75rem;
+
+    @media (max-width: 640px) {
+      padding: 0.875rem;
+      gap: 0.5rem;
+    }
+
+  &__icon {
+    flex-shrink: 0;
+    margin-top: 0.125rem;
+
+    svg {
+      width: 1.75rem;
+      height: 1.75rem;
+
+      @media (max-width: 640px) {
+        width: 1.15rem;
+        height: 1.15rem;
+      }
+    }
+  }
+
+  &__content {
+    flex: 1 1 0%;
+    min-width: 0;
+  }
+
+  &__title {
+    font-weight: 600;
+    margin-bottom: 0.25rem;
+    font-size: clamp(1.3rem, 2vw, 1.4rem);
+  }
+
+  &__body {
+    font-size: clamp(0.99rem, 2vw, 1rem);
+    max-width: none;
+    line-height: 1.6;
+  }
+
+  /* Admonition Type Variants */
+  &--info,
+  &--success,
+  &--warning,
+  &--danger,
+  &--note {
+    background-color: color-mix(in srgb, var(--base-color) 8%, white);
+    border-color: color-mix(in srgb, var(--base-color) 95%, black);
+
+    .admonition__title,
+    .admonition__body {
+      color: color-mix(in srgb, var(--base-color) 25%, black);
+    }
+
+    .admonition__icon {
+      color: color-mix(in srgb, var(--base-color) 90%, black);
+    }
+  }
+
+  &--info {
+    --base-color: var(--color-admonition-info, #3B82F6);
+  }
+
+  &--success {
+    --base-color: var(--color-admonition-success, #22C55E);
+  }
+
+  &--warning {
+    --base-color: var(--color-admonition-warning, #EAB308);
+  }
+
+  &--danger {
+    --base-color: var(--color-admonition-danger, #EF4444);
+  }
+
+  &--note {
+    --base-color: var(--color-admonition-note, #6B7280);
+    }
+  }
diff --git a/themes/clean-hugo/assets/css/_blog-listing.scss b/themes/clean-hugo/assets/css/_blog-listing.scss
new file mode 100644
index 00000000..93e17534
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_blog-listing.scss
@@ -0,0 +1,85 @@
+/* Gallery Blog Components - Using Mixins */
+
+/* Blog gallery listing page */
+.blog-listing {
+  @include container;
+  padding: 4rem 1.5rem;
+
+  .container {
+    width: 100%;
+  }
+
+  h2 {
+    @include responsive(font-size, 1.5rem, 1.875rem, 2.25rem);
+    margin-bottom: 2rem;
+  }
+
+  .blog-grid {
+    @include responsive-grid(1, 2, 3);
+  }
+
+  article {
+    position: relative;
+    display: flex;
+    flex-direction: column;
+    border-radius: $radius-md;
+    overflow: hidden;
+    background-color: var(--color-white);
+    box-shadow: $shadow-lg;
+    @include card-hover(-0.25rem, $shadow-2xl);
+
+    .card-media {
+      @include image-zoom(1.1, $transition-slower);
+      width: 100%;
+
+      img {
+        height: 10rem;
+        object-fit: cover;
+      }
+    }
+
+    .card-body {
+      padding: 1rem;
+      display: flex;
+      flex-direction: column;
+      flex-grow: 1;
+    }
+
+    h3 {
+      margin-top: 0;
+      font-size: 1.125rem;
+      font-weight: 600;
+      line-height: 1.25;
+
+      a {
+        text-decoration: none;
+        color: var(--color-gray-900);
+      }
+    }
+
+    time {
+      display: block;
+      margin-top: 0.5rem;
+      font-size: 0.75rem;
+      color: var(--color-gray-700);
+    }
+
+    .excerpt {
+      margin-top: 0.5rem;
+      font-size: 0.875rem;
+      line-height: 1.625;
+      color: var(--color-gray-600);
+    }
+
+    .stretched-link {
+      @include stretched-link;
+    }
+  }
+
+  .pagination {
+    margin-top: $spacing-section;
+    display: flex;
+    justify-content: center;
+    gap: 0.5rem;
+  }
+}
diff --git a/themes/clean-hugo/assets/css/_blog.scss b/themes/clean-hugo/assets/css/_blog.scss
new file mode 100644
index 00000000..2edea920
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_blog.scss
@@ -0,0 +1,338 @@
+/* Blog card styles are found in  _cards.scss */
+.blog-hero {
+  position: relative;
+  padding: $spacing-xl 0;
+  margin-bottom: $spacing-lg;
+  background-color: var(--color-primary-dark);
+
+  @media (min-width: $breakpoint-md) {
+    padding: $spacing-xl 0;
+  }
+
+  > .container h1 {
+    margin: 0;
+    color: var(--color-white);
+    font-weight: 700;
+    line-height: 1.1;
+    text-shadow: 1px 1px 4px rgba(0, 0, 0, 0.5);
+  }
+
+  &__lead {
+    color: rgba(255, 255, 255, 0.92);
+    font-size: 1.125rem;
+    line-height: 1.5;
+    max-width: 42rem;
+    margin: $spacing-sm 0 0;
+    text-shadow: 1px 1px 4px rgba(0, 0, 0, 0.5);
+  }
+
+  &--overlay {
+    min-height: 11rem;
+    background-size: cover;
+    background-repeat: no-repeat;
+    background-position: center;
+    background-color: var(--color-primary-dark);
+
+    @media (min-width: $breakpoint-md) {
+      min-height: 13rem;
+    }
+
+    &::before {
+      content: "";
+      position: absolute;
+      inset: 0;
+      background: rgba(20, 13, 36, 0.55);
+      pointer-events: none;
+    }
+
+    > .container {
+      position: relative;
+      z-index: 1;
+    }
+  }
+}
+
+/* Blog grid page */
+.blog-index {
+  .filter-btn[aria-pressed="true"] {
+    background-color: var(--color-brand-purple);
+    border-color: var(--color-brand-purple);
+    color: var(--color-white);
+  }
+}
+
+.blog-filter-hidden,
+.blog-filter-section-hidden {
+  display: none !important;
+}
+
+.blog-grid {
+  padding: 3rem 0;
+
+  /* Category filter buttons - uses shared .filter-btn from _filter.scss */
+  > div:first-child {
+    display: flex;
+    flex-wrap: wrap;
+    gap: 0.75rem;
+    margin-bottom: 3rem;
+
+    /* Blog filters use the same .filter-btn class from _filter.scss */
+  }
+}
+
+/* Featured section layout */
+.blog-grid__featured {
+  display: grid;
+  grid-template-columns: 1fr;
+  gap: 2rem;
+  margin-bottom: 4rem;
+  min-height: 0;
+
+  @media (min-width: $breakpoint-lg) {
+    grid-template-columns: repeat(3, 1fr);
+  }
+}
+
+
+/* Sidebar layout */
+.blog-grid__sidebar {
+  display: flex;
+  flex-direction: column;
+  gap: 1.5rem;
+
+  /* .blog-card {
+    flex: 1 1 0%;
+  }
+
+  /* Sidebar card titles - Card-specific: medium size between grid and featured */
+  /* .blog-card > a > div h2 {
+    font-size: 1.5rem;
+  } */
+}
+
+/* Grid layout */
+.blog-grid__posts {
+  display: grid;
+  grid-template-columns: 1fr;
+  gap: 2rem;
+
+  @media (min-width: $breakpoint-md) {
+    grid-template-columns: repeat(2, 1fr);
+  }
+
+  @media (min-width: $breakpoint-lg) {
+    grid-template-columns: repeat(3, 1fr);
+  }
+}
+
+/* Empty state */
+.blog-grid__empty {
+  text-align: center;
+  padding: 4rem 0;
+}
+
+/* Blog single post styles */
+.blog-post__header {
+  position: relative;
+  width: 100%;
+  height: 400px;
+  margin-bottom: 2rem;
+
+  > img {
+    width: 100%;
+    height: 100%;
+    object-fit: cover;
+  }
+
+  > div:first-of-type {
+    position: absolute;
+    inset: 0;
+    background: linear-gradient(to top, rgba(0, 0, 0, 1), rgba(0, 0, 0, 0.5), transparent);
+  }
+
+  > div:nth-of-type(2) {
+    position: absolute;
+    bottom: 0;
+    left: 0;
+    right: 0;
+    color: white;
+    padding: 2rem 1rem;
+    max-width: $container-narrow;
+    margin: 0 auto;
+    word-break: break-word;
+    hyphens: auto;
+    @media (min-width: $breakpoint-md) {
+      padding: 2.5rem 2rem;
+    }
+    h1 {
+      font-size: 2rem;
+      font-weight: 800;
+      line-height: 1.15;
+      margin: 0 0 0.5rem 0;
+      max-width: 100%;
+      word-break: break-word;
+      hyphens: auto;
+      @media (min-width: $breakpoint-md) {
+        font-size: 2.5rem;
+      }
+      @media (min-width: $breakpoint-lg) {
+        font-size: 3rem;
+      }
+    }
+    p {
+      font-size: 1rem;
+      margin: 0;
+      color: var(--color-gray-200);
+    }
+  }
+
+  > div:last-child {
+    position: absolute;
+    bottom: 0.5rem;
+    right: 0.5rem;
+    color: white;
+    font-size: 0.75rem;
+    opacity: 0.75;
+  }
+}
+
+.blog-post__excerpt {
+  max-width: 56rem;
+  margin: 0 auto;
+  padding: 0 2rem;
+  margin-bottom: 2rem;
+  font-weight: 700;
+
+  p {
+    font-size: 1.25rem;
+    line-height: 1.625;
+    color: var(--color-gray-700);
+  }
+}
+
+// Blog content styles now handled by unified .content-main class
+
+/* Blog-specific typography overrides */
+.blog-post__header + .content-main {
+  /* Left align all headings (h2 and below) and ensure sentence case */
+  /* Headings use base typography scale from main.scss, only override alignment */
+  h2, h3, h4, h5, h6 {
+    text-align: left !important;
+    text-transform: none;
+  }
+
+  /* Hugo syntax highlighting wrapper */
+  .highlight {
+    margin-bottom: 1rem;
+
+    pre {
+      margin: 0;
+    }
+  }
+}
+
+.blog-post__tags {
+  max-width: 56rem;
+  margin: 0 auto;
+  padding: 0 2rem;
+  margin-top: 3rem;
+  font-size: 0.875rem;
+  color: var(--color-gray-600);
+
+  a {
+    transition: color 200ms;
+    color: inherit;
+
+    &:hover {
+      color: var(--color-gray-900);
+    }
+  }
+}
+
+/* Last modified date for blog posts */
+.content-main + .content-last-modified {
+  max-width: 65ch;
+  margin: 0 auto;
+  padding: 0 2rem;
+}
+
+/* Blog highlight section (for shortcode - full-width dark background) */
+.blog-highlight {
+  width: 100%;
+  padding: $spacing-section-lg 0 6rem;
+  background-color: var(--color-gray-900);
+
+  .container {
+    @include container($container-max-width, 1.5rem, 2rem);
+  }
+
+  .intro {
+    max-width: $container-wide;
+    margin: 0 auto;
+
+    @media (min-width: $breakpoint-lg) {
+      margin: 0;
+    }
+
+    h2 {
+      @include responsive(font-size, 2.25rem, 3rem);
+      font-weight: 600;
+      letter-spacing: -0.025em;
+      color: var(--color-white);
+    }
+  }
+
+  .highlight-grid {
+    max-width: $container-wide;
+    margin: 2.5rem auto 0;
+    gap: 4rem 2rem;
+    border-top: 1px solid var(--color-gray-700);
+    padding-top: 2.5rem;
+
+    @media (min-width: $breakpoint-sm) {
+      margin-top: 4rem;
+      padding-top: 4rem;
+    }
+
+    @media (min-width: $breakpoint-lg) {
+      max-width: none;
+      margin-inline: 0;
+    }
+  }
+
+  &__actions {
+    margin-top: 2.5rem;
+  }
+}
+
+/* Blog archives section — soft purple band (matches main site) */
+.blog-archives {
+  width: 100vw;
+  max-width: 100vw;
+  margin: 3rem calc(50% - 50vw);
+  padding: 2.5rem clamp(1rem, 4vw, 2rem);
+  box-sizing: border-box;
+  background-color: color-mix(in srgb, var(--color-soft-purple) 35%, transparent);
+
+  > .container > div:first-child {
+    margin-bottom: 1.5rem;
+
+    h2 {
+      color: var(--color-brand-purple);
+    }
+  }
+}
+
+.highlight-grid {
+  display: grid;
+  grid-template-columns: 1fr;
+  gap: 1.5rem;
+
+  @media (min-width: $breakpoint-md) {
+    grid-template-columns: repeat(2, 1fr);
+  }
+
+  @media (min-width: $breakpoint-lg) {
+    grid-template-columns: repeat(3, 1fr);
+  }
+}
diff --git a/themes/clean-hugo/assets/css/_buttons.scss b/themes/clean-hugo/assets/css/_buttons.scss
new file mode 100644
index 00000000..1ac90531
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_buttons.scss
@@ -0,0 +1,235 @@
+/*
+  Buttons — pyOpenSci brand variants
+  Adjust light-fill mix ratios below (higher = more color, lower = more white).
+*/
+$btn-green-mix: 55%;
+$btn-light-purple-mix: 65%;
+
+/* Base */
+.btn {
+  display: inline-flex;
+  align-items: center;
+  justify-content: center;
+  gap: 0.5rem;
+  padding: 0.75rem 1.5rem;
+  font-weight: 600;
+  font-size: 1.3rem;
+  text-decoration: none;
+  text-align: center;
+  line-height: 1.4;
+  border-radius: $radius-lg;
+  border: $btn-bd solid transparent;
+  cursor: pointer;
+  transition: transform $transition-base ease, box-shadow $transition-base ease,
+    background-color $transition-base ease, color $transition-base ease;
+
+  &:hover {
+    transform: translateY(-1px);
+    box-shadow: $shadow-md;
+  }
+
+  &:active {
+    transform: translateY(0);
+  }
+
+  &:focus {
+    @include focus-ring;
+  }
+
+  &:disabled,
+  &[aria-disabled="true"] {
+    opacity: 0.5;
+    cursor: not-allowed;
+    transform: none;
+    box-shadow: none;
+  }
+
+  p {
+    margin: 0;
+    color: inherit;
+  }
+}
+
+/* Dark purple fill — main CTA */
+.btn--dark-purple {
+  background-color: var(--color-brand-purple);
+  color: var(--color-white);
+
+  &,
+  &:hover,
+  &:focus,
+  p {
+    color: var(--color-white);
+  }
+
+  &:hover {
+    background-color: var(--color-brand-purple-dark);
+  }
+
+  &:focus {
+    box-shadow: 0 0 0 2px var(--color-white), 0 0 0 4px var(--color-brand-purple);
+  }
+}
+
+/* White fill — dark purple text */
+.btn--white {
+  background-color: var(--color-white);
+  color: var(--color-brand-purple);
+
+  &:hover {
+    background-color: var(--color-gray-50);
+    color: var(--color-brand-purple);
+  }
+
+  &:focus {
+    box-shadow: 0 0 0 2px var(--color-white), 0 0 0 4px var(--color-brand-purple);
+  }
+}
+
+/* Light green fill — black text, mixed with white for contrast */
+.btn--green {
+  background-color: color-mix(
+    in srgb,
+    var(--color-admonition-success) $btn-green-mix,
+    var(--color-white)
+  );
+  color: var(--color-gray-900);
+
+  &:hover {
+    background-color: color-mix(
+      in srgb,
+      var(--color-admonition-success) calc($btn-green-mix + 10%),
+      var(--color-white)
+    );
+    color: var(--color-gray-900);
+  }
+
+  &:focus {
+    box-shadow: 0 0 0 2px var(--color-white),
+      0 0 0 4px var(--color-admonition-success);
+  }
+}
+
+/* Light purple fill — black text, mixed with white for contrast */
+.btn--light-purple {
+  background-color: color-mix(
+    in srgb,
+    var(--color-light-purple) $btn-light-purple-mix,
+    var(--color-white)
+  );
+  color: var(--color-gray-900);
+
+  &:hover {
+    background-color: color-mix(
+      in srgb,
+      var(--color-light-purple) calc($btn-light-purple-mix + 10%),
+      var(--color-white)
+    );
+    color: var(--color-gray-900);
+  }
+
+  &:focus {
+    box-shadow: 0 0 0 2px var(--color-white),
+      0 0 0 4px var(--color-brand-medium-purple);
+  }
+}
+
+/* Outline — medium purple border, dark purple text */
+.btn--outline {
+  background-color: transparent;
+  color: var(--color-brand-purple);
+  border-color: var(--color-brand-medium-purple);
+
+  &:hover {
+    background-color: color-mix(
+      in srgb,
+      var(--color-brand-medium-purple) 12%,
+      transparent
+    );
+    color: var(--color-brand-purple);
+  }
+
+  &:focus {
+    box-shadow: 0 0 0 2px var(--color-white),
+      0 0 0 4px var(--color-brand-medium-purple);
+  }
+}
+
+/* Hero — white outline on dark purple backgrounds */
+.btn--outline-on-dark {
+  background-color: transparent;
+  color: var(--color-white);
+  border: $btn-bd-thin solid var(--color-white);
+
+  &:hover {
+    background-color: color-mix(in srgb, var(--color-white) 12%, transparent);
+    color: var(--color-white);
+  }
+
+  &:focus {
+    box-shadow: 0 0 0 2px var(--color-brand-purple-dark),
+      0 0 0 4px var(--color-white);
+  }
+}
+
+/* Large */
+.btn--lg,
+.btn--large {
+  padding: 1rem 2rem;
+  font-size: 1.125rem;
+}
+
+/* Groups */
+.btn-group {
+  display: flex;
+  gap: 1rem;
+  flex-wrap: wrap;
+
+  &--center {
+    justify-content: center;
+  }
+
+  &--right {
+    justify-content: flex-end;
+  }
+
+  @media (max-width: $breakpoint-sm) {
+    flex-direction: column;
+
+    .btn {
+      width: 100%;
+    }
+  }
+}
+
+/* Icons */
+.btn--icon {
+  i, svg {
+    flex-shrink: 0;
+  }
+}
+
+/* Legacy aliases — remove when content is fully migrated */
+.btn--primary {
+  @extend .btn--dark-purple;
+}
+
+.btn--secondary {
+  @extend .btn--outline;
+}
+
+.btn--accent {
+  @extend .btn--green;
+}
+
+.btn--success {
+  @extend .btn--green;
+}
+
+.btn--info {
+  @extend .btn--dark-purple;
+}
+
+.btn--outline-on-light {
+  @extend .btn--outline;
+}
diff --git a/themes/clean-hugo/assets/css/_cards.scss b/themes/clean-hugo/assets/css/_cards.scss
new file mode 100644
index 00000000..25ffbe6b
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_cards.scss
@@ -0,0 +1,817 @@
+/* Impact Cards Section - Hero/splash page cards */
+.impact-cards {
+  max-width: $container-max-width;
+  margin: 0 auto;
+  padding: $fluid-space-2xl $fluid-container-padding;
+}
+
+.impact-cards__grid {
+  display: grid;
+  grid-template-columns: 1fr;
+  gap: $card-gap;
+
+  @media (min-width: $breakpoint-md) {
+    grid-template-columns: repeat(2, 1fr);
+  }
+}
+
+/* Opt-in from page front matter: cards_layout: wide */
+.impact-cards--wide {
+  max-width: $container-impact-wide;
+}
+
+.impact-cards__grid--wide {
+  @media (min-width: $breakpoint-lg) {
+    grid-template-columns: repeat(3, 1fr);
+  }
+}
+
+/* Impact cards - fluid padding scales from mobile to desktop */
+.impact-cards .card {
+  padding: $fluid-card-padding-lg;
+  margin: 0;
+
+  /* Consistent typography for all card types */
+  p {
+    font-size: $card-text-size;
+    line-height: $card-line-height;
+    color: $card-text-color;
+  }
+
+  h2, h3 {
+    line-height: 1.25;
+  }
+}
+
+/* Home-only full-bleed programs section */
+.home-programs-full {
+  width: 100vw;
+  position: relative;
+  left: 50%;
+  margin-inline: -50vw;
+  padding: 0 $fluid-container-padding;
+
+  h2 {
+    margin: 0;
+    padding-top: $fluid-space-xl;
+    padding-bottom: 1rem;
+    text-align: left;
+  }
+
+  .impact-cards {
+    max-width: none;
+    margin: 0;
+    padding-inline: 0;
+  }
+}
+
+/* Optional 16:9 image strip above body (e.g. “What we offer” on /events/) */
+.impact-cards .card.card--with-top-image {
+  padding: 0;
+  overflow: hidden;
+
+  .card__top-image {
+    margin: 0;
+    aspect-ratio: 16 / 9;
+    overflow: hidden;
+
+    img {
+      width: 100%;
+      height: 100%;
+      object-fit: cover;
+      display: block;
+      transition: transform $transition-base ease-out;
+    }
+  }
+
+  &:hover .card__top-image img {
+    transform: scale(1.03);
+  }
+
+  > div {
+    @include responsive-padding(1.25rem, 1.25rem, 2.5rem, 2.5rem);
+    flex: 1 1 auto;
+    min-height: 0;
+    display: flex;
+    flex-direction: column;
+  }
+
+  .card__cta {
+    padding: 0 1.25rem 1.25rem;
+    @media (min-width: $breakpoint-md) {
+      padding: 0 2.5rem 2.5rem;
+    }
+  }
+
+  > div > .event-card__type:first-of-type {
+    align-self: flex-start;
+    margin-bottom: 0.25rem;
+  }
+}
+
+  .card--text  {
+    @include card-base();
+    @include responsive-padding(2.5rem, 2.5rem, 3rem, 3rem);
+    display: flex;
+    flex-direction: column;
+    @media (min-width: $breakpoint-md) {
+      min-height: 260px;
+    }
+    > div {
+      @include flex-center;
+      text-align: center;
+      flex: 1;
+      h2 {
+        @include responsive(font-size, 2.25rem, 3.75rem);
+        font-weight: 800;
+        line-height: 1.25;
+        max-width: 32rem;
+        color: var(--color-gray-900);
+        margin-top: 0;
+        margin-bottom: 0;
+        @media (min-width: $breakpoint-md) {
+          font-size: 3rem;
+        }
+      }
+      p {
+        font-size: $card-text-size;
+        line-height: $card-line-height;
+        color: $card-text-color;
+        transition: color $transition-base ease;
+        margin-bottom: 0;
+        @media (min-width: $breakpoint-md) {
+          font-size: 1.25rem;
+        }
+      }
+      > div:last-child {
+        margin-top: 1.5rem;
+      }
+    }
+  }
+
+  /* Unused - kept for potential future use */
+  .card-hover {
+    transition: transform $transition-base ease-in-out;
+    will-change: transform, box-shadow;
+
+    &:hover,
+    &:focus-visible {
+      transform: $card-hover-transform;
+      box-shadow: $shadow-xl;
+    }
+
+    /* ensure hover does NOT change text color */
+    :is(.card__cta, h2, h3, p, li, a) {
+      color: inherit;
+    }
+  }
+
+  /* Unused - kept for potential future use */
+  .card-hover--compact:hover {
+    transform: translateY(-2px);
+    box-shadow: 0 6px 18px rgba(17,24,39,0.06);
+  }
+
+  .card {
+    @include card-base();
+    @include responsive-padding(1.25rem, 1.25rem, 2.5rem, 2.5rem);
+    display: flex;
+    flex-direction: column;
+    h3 {
+      font-size: $card-heading-size;
+      font-weight: 800;
+      line-height: 1.3;
+      margin-bottom: 1rem;
+      transition: color $transition-base ease;
+      margin-top: 0;
+      @media (min-width: $breakpoint-md) {
+        font-size: 1.5rem;
+      }
+    }
+    > div > h3 + div {
+      font-size: $card-text-size;
+      line-height: $card-line-height;
+      color: $card-text-color;
+      transition: color $transition-base ease;
+      @media (min-width: $breakpoint-md) {
+        font-size: 1.125rem;
+      }
+      p {
+        margin-bottom: 0.5rem;
+        &:last-child {
+          margin-bottom: 0;
+        }
+      }
+
+      ul, ol {
+        padding-left: $card-list-padding;
+
+        li {
+          font-size: $card-text-size;
+          line-height: $card-line-height;
+          margin-bottom: 0.5rem;
+        }
+      }
+
+      a {
+        color: var(--color-link);
+        text-decoration: underline;
+        transition: color .2s ease;
+
+        &:hover,
+        &:focus {
+          color: var(--color-link-hover);
+        }
+      }
+
+      strong {
+        color: var(--color-gray-900);
+        font-weight: 600;
+      }
+    }
+  }
+
+  /* Highlight card - can also use bg-primary utility */
+  .card--highlight {
+    background-color: var(--color-primary-light);
+    transition: background-color $transition-base ease-in-out;
+  }
+
+  /* White card variant - plain white background */
+  .card--white {
+    background-color: var(--color-white);
+  }
+
+  .card__icon {
+    font-size: $card-icon-size;
+    margin-bottom: 1rem;
+    display: inline-block; /* Prevent icon from creating extra layout space */
+    margin-top: 0; /* Ensure no top margin */
+  }
+
+  .card__cta {
+    margin-top: 1rem;
+    @include responsive(font-size, 0.875rem, 1rem);
+    color: var(--color-link);
+    transition: color $transition-base ease;
+
+    &:hover,
+    &:focus {
+      color: var(--color-link-hover);
+    }
+  }
+
+/* ==========================================
+   BLOG CARD MODIFIER - Consolidated from _blog.scss
+   ========================================== */
+
+.card--blog {
+  display: flex;
+  flex-direction: column;
+  padding: 0;
+  overflow: hidden;
+
+  a {
+    display: block;
+    height: 100%;
+    border-radius: $radius-md;
+    overflow: hidden;
+    background-color: var(--color-white);
+    box-shadow: $shadow-sm;
+    transition: box-shadow $transition-base ease-in-out, transform $transition-base ease-in-out;
+    text-decoration: none;
+
+    &:focus {
+      outline: none;
+      box-shadow: 0 0 0 2px var(--color-white), 0 0 0 4px var(--color-primary);
+    }
+
+    &:hover {
+      box-shadow: $shadow-lg;
+      transform: translateY(-2px);
+
+      .card--blog__image img,
+      .card--blog__image-placeholder {
+        transform: scale(1.03);
+      }
+    }
+  }
+
+  /* Image container */
+  .card--blog__image,
+  .card--blog__image-placeholder {
+    width: 100%;
+    overflow: hidden;
+    aspect-ratio: 16 / 9;
+    transition: transform $transition-base ease-out;
+    margin: 0;
+  }
+
+  .card--blog__image img {
+    width: 100%;
+    height: 100%;
+    object-fit: cover;
+    transition: transform $transition-base ease-out;
+  }
+
+  /* Content area (featured + sidebar cards) */
+  .card--blog__content {
+    flex: 1 1 0%;
+    display: flex;
+    flex-direction: column;
+    gap: 0.5rem;
+    padding: 1rem;
+
+    .card--blog__badge {
+      font-size: 0.75rem;
+      font-weight: 600;
+      letter-spacing: 0.05em;
+      text-transform: uppercase;
+      display: block;
+      margin-bottom: 0.5rem;
+      color: var(--color-brand-purple);
+      background: color-mix(in srgb, var(--color-soft-purple) 45%, transparent);
+      align-self: flex-start;
+      padding: 0.2rem 0.55rem;
+      border-radius: $radius-full;
+    }
+
+    h2 {
+      font-size: 1.25rem;
+      font-weight: 600;
+      line-height: 1.25;
+      text-align: left;
+      color: var(--color-gray-900);
+      margin-top: 0;
+      margin-bottom: 0;
+    }
+
+    time {
+      font-size: 0.75rem;
+      color: var(--color-gray-600);
+    }
+
+    .card--blog__author {
+      font-size: 0.875rem;
+      color: var(--color-gray-700);
+      margin-bottom: 0;
+    }
+
+    .card--blog__excerpt {
+      font-size: 1rem;
+      line-height: 1.625;
+      color: var(--color-gray-700);
+      margin-bottom: 0;
+    }
+  }
+}
+
+/* Grid blog cards — dark header, white title + date (Jekyll blog index style) */
+.card--blog--grid {
+  .card--blog__link {
+    display: flex;
+    flex-direction: column;
+    height: 100%;
+  }
+
+  .card--blog__media {
+    position: relative;
+    aspect-ratio: 16 / 10;
+    overflow: hidden;
+    display: flex;
+    flex-direction: column;
+    justify-content: flex-end;
+  }
+
+  .card--blog__media-bg,
+  .card--blog__media-fallback {
+    position: absolute;
+    inset: 0;
+    width: 100%;
+    height: 100%;
+    object-fit: cover;
+  }
+
+  .card--blog__media-scrim {
+    position: absolute;
+    inset: 0;
+    z-index: 1;
+    background: linear-gradient(
+      to top,
+      color-mix(in srgb, var(--color-brand-purple) 92%, transparent) 0%,
+      color-mix(in srgb, var(--color-brand-purple) 50%, transparent) 42%,
+      color-mix(in srgb, var(--color-brand-purple) 15%, transparent) 100%
+    );
+  }
+
+  @each $index, $color in (
+    0: var(--color-brand-magenta),
+    1: var(--color-brand-header-purple),
+    2: var(--color-soft-purple),
+    3: var(--color-brand-medium-purple)
+  ) {
+    .card--blog__media-fallback--#{$index} {
+      background-color: #{$color};
+    }
+  }
+
+  .card--blog__image-placeholder {
+    &.card--blog__media-fallback--0 { background-color: var(--color-brand-magenta); }
+    &.card--blog__media-fallback--1 { background-color: var(--color-brand-header-purple); }
+    &.card--blog__media-fallback--2 { background-color: var(--color-soft-purple); }
+    &.card--blog__media-fallback--3 { background-color: var(--color-brand-medium-purple); }
+  }
+
+  .card--blog__media-text {
+    position: relative;
+    z-index: 2;
+    padding: 0.85rem 1rem 1rem;
+
+    h2 {
+      margin: 0 0 0.35rem;
+      font-size: 1.25rem;
+      font-weight: 600;
+      line-height: 1.25;
+      color: var(--color-white);
+    }
+
+    time {
+      font-size: 0.75rem;
+      color: rgba(255, 255, 255, 0.88);
+    }
+  }
+
+  .card--blog__body {
+    display: flex;
+    flex: 1 1 auto;
+    flex-direction: column;
+    gap: 0.45rem;
+    padding: 1rem 1.1rem 1.15rem;
+  }
+
+  .card--blog__badge {
+    align-self: flex-start;
+    padding: 0.2rem 0.55rem;
+    border-radius: $radius-full;
+    font-size: 0.6875rem;
+    font-weight: 600;
+    letter-spacing: 0.04em;
+    text-transform: uppercase;
+    color: var(--color-brand-purple);
+    background: color-mix(in srgb, var(--color-soft-purple) 45%, transparent);
+  }
+
+  .card--blog__excerpt {
+    flex: 1 1 auto;
+    margin: 0;
+    font-size: 0.875rem;
+    line-height: 1.5;
+    color: var(--color-gray-700);
+    display: -webkit-box;
+    -webkit-box-orient: vertical;
+    -webkit-line-clamp: 3;
+    overflow: hidden;
+  }
+
+  a:hover .card--blog__media-bg {
+    transform: scale(1.03);
+  }
+
+  .card--blog__media-bg {
+    transition: transform $transition-base ease-out;
+  }
+}
+
+/* Featured blog card modifier */
+.card--blog--featured {
+  @media (min-width: $breakpoint-lg) {
+    grid-column: span 2 / span 2;
+  }
+
+  .card--blog__content {
+    gap: 0.75rem;
+    padding: 1.5rem;
+
+    h2 {
+      font-size: 2rem;
+      font-weight: 700;
+      text-align: left;
+      letter-spacing: -0.02em;
+      margin-top: 0;
+      margin-bottom: 0;
+
+      @media (min-width: $breakpoint-md) {
+        font-size: 2.25rem;
+      }
+      @media (min-width: $breakpoint-lg) {
+        font-size: 2.5rem;
+      }
+    }
+
+    .card--blog__badge {
+      margin-bottom: 0.75rem;
+    }
+
+    time {
+      font-size: 1rem;
+    }
+
+    .card--blog__excerpt {
+      font-size: 1.125rem;
+      line-height: 1.625;
+      margin-bottom: 0;
+
+      @media (min-width: $breakpoint-md) {
+        font-size: 1.25rem;
+      }
+    }
+  }
+}
+
+/* Sidebar blog card modifier */
+.card--blog--sidebar {
+  .card--blog__content h2 {
+    font-size: 1.5rem;
+  }
+}
+
+/* Shared listing cards used by blog/event archive grids */
+.listing-card {
+  @include card-surface($radius-md, 1px solid var(--color-gray-200), $shadow-sm, var(--color-white));
+  padding: map-get($listing-card-default, padding);
+  display: flex;
+  flex-direction: column;
+  transition: box-shadow $transition-base ease-in-out, transform $transition-base ease-in-out, background-color $transition-base ease-in-out;
+
+  &:hover {
+    box-shadow: $shadow-xl;
+    transform: translateY(-2px);
+  }
+
+  .meta {
+    display: flex;
+    align-items: center;
+    gap: map-get($listing-card-default, meta-gap);
+    margin-bottom: 1rem;
+    font-size: map-get($listing-card-default, meta-font-size);
+    color: var(--color-gray-600);
+
+    time {
+      font-weight: 500;
+    }
+  }
+
+  .category {
+    padding: map-get($listing-card-default, category-padding);
+    border-radius: $radius-sm;
+    font-size: map-get($listing-card-default, category-font-size);
+    font-weight: 600;
+    text-transform: uppercase;
+    letter-spacing: 0.025em;
+  }
+
+  .content {
+    position: relative;
+    display: flex;
+    flex-direction: column;
+    flex-grow: 1;
+  }
+
+  h3 {
+    margin-top: 0;
+    margin-bottom: 0.75rem;
+    font-size: map-get($listing-card-default, title-font-size);
+    line-height: map-get($listing-card-default, title-line-height);
+    color: var(--color-gray-900);
+
+    a {
+      color: inherit;
+      text-decoration: none;
+      transition: color $transition-base ease;
+
+      &::before {
+        content: "";
+        position: absolute;
+        inset: 0;
+      }
+
+      &:hover {
+        color: var(--color-primary);
+      }
+    }
+  }
+
+  .excerpt {
+    line-height: map-get($listing-card-default, excerpt-line-height);
+    margin-bottom: 1rem;
+    font-size: map-get($listing-card-default, excerpt-font-size);
+    color: var(--color-gray-700);
+  }
+
+  .read-more {
+    margin-top: auto;
+    display: inline-flex;
+    align-items: center;
+    gap: 0.5rem;
+    position: relative;
+    z-index: 1;
+    font-weight: 500;
+    font-size: map-get($listing-card-default, read-more-font-size);
+    color: var(--color-link);
+    transition: color $transition-base ease;
+
+    i {
+      font-size: 0.75rem;
+      transition: transform $transition-base ease;
+    }
+
+    &:hover,
+    &:focus {
+      color: var(--color-link-hover);
+
+      i {
+        transform: translateX(0.25rem);
+      }
+    }
+  }
+}
+
+.listing-card--density-compact {
+  padding: map-get($listing-card-compact, padding);
+
+  .meta {
+    gap: map-get($listing-card-compact, meta-gap);
+    margin-bottom: 0.5rem;
+    font-size: map-get($listing-card-compact, meta-font-size);
+  }
+
+  .category {
+    font-size: map-get($listing-card-compact, category-font-size);
+    padding: map-get($listing-card-compact, category-padding);
+  }
+
+  h3 {
+    margin-bottom: 0.4rem;
+    font-size: map-get($listing-card-compact, title-font-size);
+    line-height: map-get($listing-card-compact, title-line-height);
+  }
+
+  .excerpt {
+    margin-bottom: 0.6rem;
+    font-size: map-get($listing-card-compact, excerpt-font-size);
+    line-height: map-get($listing-card-compact, excerpt-line-height);
+  }
+
+  .read-more {
+    font-size: map-get($listing-card-compact, read-more-font-size);
+  }
+}
+
+.listing-card--with-image {
+  padding: 0;
+  overflow: hidden;
+
+  .listing-card__image {
+    margin: 0;
+    aspect-ratio: 16 / 10;
+    overflow: hidden;
+
+    a {
+      display: block;
+      height: 100%;
+    }
+
+    img {
+      width: 100%;
+      height: 100%;
+      object-fit: cover;
+      display: block;
+      transition: transform $transition-base ease-out;
+    }
+  }
+
+  &:hover .listing-card__image img {
+    transform: scale(1.03);
+  }
+
+  .listing-card__body {
+    display: flex;
+    flex-direction: column;
+    flex-grow: 1;
+    padding: map-get($listing-card-default, padding);
+  }
+}
+
+.listing-card--blog-archive {
+  background-color: var(--color-white);
+  border: 1px solid color-mix(in srgb, var(--color-brand-purple) 10%, transparent);
+  box-shadow: 0 2px 6px color-mix(in srgb, var(--color-brand-purple) 6%, transparent);
+
+  &:hover {
+    background-color: var(--color-white);
+    box-shadow: 0 4px 12px color-mix(in srgb, var(--color-brand-purple) 10%, transparent);
+  }
+
+  .meta {
+    flex-wrap: wrap;
+    align-items: center;
+    justify-content: space-between;
+    gap: 0.5rem;
+    width: 100%;
+  }
+
+  .category {
+    margin-left: auto;
+    padding: 0.15rem 0.5rem;
+    border-radius: $radius-full;
+    font-size: map-get($listing-card-default, category-font-size);
+    font-weight: 600;
+    letter-spacing: 0.04em;
+    text-transform: uppercase;
+    background-color: color-mix(in srgb, var(--color-soft-purple) 50%, transparent);
+    color: var(--color-brand-purple);
+  }
+
+  h3 a {
+    color: var(--color-brand-purple);
+    text-decoration: underline;
+    text-decoration-color: color-mix(in srgb, var(--color-brand-purple) 35%, transparent);
+    text-underline-offset: 0.15em;
+
+    &:hover,
+    &:focus {
+      color: var(--color-brand-purple-dark);
+      text-decoration-color: currentColor;
+    }
+  }
+
+  .read-more {
+    color: var(--color-brand-purple);
+    text-decoration: underline;
+    text-decoration-color: color-mix(in srgb, var(--color-brand-purple) 35%, transparent);
+    text-underline-offset: 0.15em;
+
+    &:hover,
+    &:focus {
+      color: var(--color-brand-purple-dark);
+      text-decoration-color: currentColor;
+    }
+  }
+}
+
+.listing-card--on-light {
+  background-color: color-mix(in srgb, var(--color-primary-light) 60%, white 40%);
+  border-color: var(--color-gray-200);
+
+  &:hover {
+    background-color: color-mix(in srgb, white 60%, var(--color-primary-light) 40%);
+  }
+
+  .category {
+    background-color: var(--color-primary-light);
+    color: var(--color-primary-dark);
+  }
+}
+
+.listing-card--on-dark {
+  background-color: var(--color-gray-900);
+  border-color: var(--color-gray-700);
+
+  .meta {
+    color: var(--color-gray-200);
+  }
+
+  .category {
+    color: var(--color-link-on-dark);
+    background-color: color-mix(in srgb, var(--color-link-on-dark) 10%, transparent);
+    border: 1px solid color-mix(in srgb, var(--color-link-on-dark) 20%, transparent);
+    transition: background-color $transition-base ease, border-color $transition-base ease;
+
+    &:hover,
+    &:focus {
+      background-color: color-mix(in srgb, var(--color-link-on-dark) 20%, transparent);
+      border-color: color-mix(in srgb, var(--color-link-on-dark) 30%, transparent);
+    }
+  }
+
+  h3 {
+    color: var(--color-white);
+
+    a:hover {
+      color: var(--color-primary-light);
+    }
+  }
+
+  .excerpt {
+    color: var(--color-gray-200);
+  }
+
+  .read-more {
+    color: var(--color-link-on-dark);
+
+    &:hover,
+    &:focus {
+      color: var(--color-primary-light);
+    }
+  }
+}
diff --git a/themes/clean-hugo/assets/css/_code.scss b/themes/clean-hugo/assets/css/_code.scss
new file mode 100644
index 00000000..437d463a
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_code.scss
@@ -0,0 +1,96 @@
+/* Code block and syntax highlighting styles */
+/* These styles apply globally across all pages (blog, content, packages, etc.) */
+
+code {
+  border-radius: 0.25rem;
+  padding: 0.125rem 0.375rem;
+  font-size: 0.95rem;
+  font-family: $font-family-mono;
+  background-color: rgba(0, 0, 0, 0.05);
+  color: #e83e8c;
+}
+
+/* Code blocks (pre elements) - base and syntax highlighted */
+pre {
+  border-radius: 0.5rem;
+  padding: 1rem;
+  overflow-x: auto;
+  margin-bottom: 1rem;
+  background-color: #272822;
+  color: #f8f8f2;
+  font-size: 0.95rem;
+  line-height: 1.5;
+  font-family: $font-family-mono;
+
+  code {
+    padding: 0;
+    background-color: transparent;
+    color: inherit;
+    font-size: inherit;
+    border-radius: 0;
+  }
+}
+
+/* Hugo syntax highlighting wrapper (.highlight) - used by Chroma */
+.highlight {
+  margin-bottom: 1rem;
+  position: relative;
+
+  pre {
+    margin: 0;
+    padding: 2rem;
+  }
+}
+
+/* Chroma syntax highlighter wrapper */
+.highlight .chroma {
+  background-color: #272822;
+  border-radius: 0.5rem;
+
+  pre {
+    background-color: transparent;
+  }
+}
+
+/* Inline code within paragraphs, lists, and tables */
+p code,
+li code,
+td code {
+  padding: 0.125rem 0.375rem;
+  background-color: rgba(0, 0, 0, 0.05);
+  color: #e83e8c;
+  font-size: 0.875em;
+}
+
+/* Code blocks should not have inline code styling */
+pre code,
+.highlight code,
+.chroma code {
+  background-color: transparent;
+  color: inherit;
+  padding: 0;
+}
+
+/* Ensure code blocks are scrollable on mobile */
+pre,
+.highlight pre,
+.chroma pre {
+  overflow-x: auto;
+  -webkit-overflow-scrolling: touch;
+}
+
+/* Line numbers (if enabled in Hugo config) */
+.highlight .lnt,
+.chroma .lnt {
+  display: inline-block;
+  padding-right: 1em;
+  color: #75715e;
+  user-select: none;
+}
+
+/* Ensure proper spacing for code blocks in content */
+.content-main pre,
+.splash-page__content pre,
+article pre {
+  margin-bottom: 1rem;
+}
diff --git a/themes/clean-hugo/assets/css/_content.scss b/themes/clean-hugo/assets/css/_content.scss
new file mode 100644
index 00000000..0b87d403
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_content.scss
@@ -0,0 +1,300 @@
+
+/* Unified content container and headings (formerly blog styles) */
+.content-container,
+.content-page {
+  max-width: $container-narrow;
+  margin: 0 auto;
+  padding: 0 $fluid-container-padding;
+}
+
+/* Shared base class for all prose content */
+.prose-content {
+  margin: 0 auto;
+  font-size: 1rem;
+  line-height: 1.625;
+  color: var(--color-gray-700);
+
+/* Content links — exclude buttons (variant colors live in _buttons.scss) */
+.content-main a:not(.btn),
+.splash-page__content a:not(.btn),
+.prose-content a:not(.btn) {
+  color: var(--color-link);
+
+  &:hover,
+  &:focus {
+    color: var(--color-link-hover);
+  }
+}
+
+  /* Shared code styling */
+  pre {
+    border-radius: 0.5rem;
+    padding: 1rem;
+    overflow-x: auto;
+    margin-bottom: 1rem;
+    background-color: #272822;
+    color: #f8f8f2;
+    font-size: 0.875rem;
+    line-height: 1.5;
+  }
+
+  code {
+    border-radius: 0.25rem;
+    padding: 0.125rem 0.375rem;
+    font-size: 0.875em;
+    background-color: rgba(0, 0, 0, 0.05);
+    color: #e83e8c;
+  }
+
+  pre code {
+    padding: 0;
+    background-color: transparent;
+    color: inherit;
+    font-size: inherit;
+  }
+
+  /* Responsive font sizing */
+  @media (min-width: $breakpoint-lg) {
+    font-size: 1.25rem;
+  }
+}
+
+.content-title {
+  @include responsive(font-size, 2rem, 2.5rem, 3rem);
+  font-weight: 800;
+  margin-bottom: 1rem;
+}
+
+.content-body {
+  @extend .prose-content;
+  max-width: 65ch;
+
+
+  .highlight {
+    margin-bottom: 1rem;
+    pre {
+      margin: 0;
+    }
+  }
+
+  h1 {
+    font-size: 2rem;
+    font-weight: 800;
+    margin-bottom: 1rem;
+    @media (min-width: $breakpoint-md) {
+      font-size: 2.5rem;
+    }
+    @media (min-width: $breakpoint-lg) {
+      font-size: 3rem;
+    }
+  }
+  h2 {
+    font-size: 1.5rem;
+    font-weight: 700;
+    margin-bottom: 1rem;
+    @media (min-width: $breakpoint-md) {
+      font-size: 1.875rem;
+    }
+    @media (min-width: $breakpoint-lg) {
+      font-size: 2.25rem;
+    }
+  }
+  h3 {
+    font-size: 1.25rem;
+    font-weight: 600;
+    margin-bottom: 1rem;
+    @media (min-width: $breakpoint-md) {
+      font-size: 1.5rem;
+    }
+    @media (min-width: $breakpoint-lg) {
+      font-size: 1.75rem;
+    }
+  }
+  p {
+    font-size: 1.125rem;
+    line-height: 1.625;
+    color: var(--color-gray-700);
+    margin-bottom: 1rem;
+    @media (min-width: $breakpoint-md) {
+      font-size: 1.25rem;
+    }
+  }
+}
+
+.content-date {
+  margin-bottom: 2rem;
+  color: var(--color-gray-600);
+}
+
+// Headings left aligned for all content
+.content-main h2,
+.content-main h3,
+.content-main h4,
+.content-main h5,
+.content-main h6,
+.splash-page__content h2,
+.splash-page__content h3,
+.splash-page__content h4,
+.splash-page__content h5,
+.splash-page__content h6 {
+  text-align: left !important;
+  text-transform: none;
+}
+
+@media (min-width: $breakpoint-lg) {
+  .content-main,
+  .splash-page__content {
+    font-size: 1.25rem;
+  }
+}
+
+// Full-width shortcodes for unified content container
+.content-main > .metrics-bar,
+.content-main > .blog-highlight,
+.content-main > .single-card-wide,
+.content-main > .youtube-container:not(.youtube-container--constrained),
+.content-main > .two-card-row,
+.content-main > .impact-cards,
+.content-main > .swoosh-section,
+.content-main > .swoosh-section__divider-wrap,
+.splash-page__content > .metrics-bar,
+.splash-page__content > .blog-highlight,
+.splash-page__content > .single-card-wide,
+.splash-page__content > .youtube-container:not(.youtube-container--constrained),
+.splash-page__content > .two-card-row,
+.splash-page__content > .impact-cards,
+.splash-page__content > .swoosh-section,
+.splash-page__content > .swoosh-section__divider-wrap {
+  width: 100vw;
+  position: relative;
+  left: 50%;
+  margin-inline: -50vw;
+}
+
+// Unified content container with prose constraints and full-width support
+.content-main {
+  @extend .prose-content;
+  max-width: 65ch;  // Optimal reading width
+  margin: 0 auto;   // Center the constrained content
+
+  // Full-width shortcodes (defined above)
+  // These will break out of the 65ch constraint when needed
+}
+
+/* Splash home: same typography as .content-main but no 65ch cap (cards / grids set their own max-width) */
+.splash-page__content {
+  @extend .prose-content;
+  max-width: 80rem;
+  width: 100%;
+  margin: 0 auto;
+  padding: 0 $fluid-container-padding;
+  box-sizing: border-box;
+}
+
+// List styles for unified content
+.content-main ul,
+.content-main ol,
+.splash-page__content ul,
+.splash-page__content ol {
+  margin-bottom: 1rem;
+}
+.content-main li,
+.splash-page__content li {
+  margin-bottom: 0.5rem;
+}
+.content-main p,
+.splash-page__content p {
+  margin-bottom: 1rem;
+  line-height: 1.625;
+  color: var(--color-gray-700);
+}
+
+/* Section styles for list pages */
+.section-container {
+  padding: 3rem 0;
+}
+
+.section-content {
+  margin-bottom: 1.5rem;
+}
+
+.section-list {
+  display: flex;
+  flex-direction: column;
+  gap: 1.5rem;
+}
+
+.section-item {
+  a {
+    font-size: 1.125rem;
+    font-weight: 500;
+    transition: color 0.2s;
+    color: var(--color-gray-900);
+
+    &:hover,
+    &:focus {
+      text-decoration: underline;
+      color: var(--color-link);
+    }
+  }
+}
+
+.section-item__meta {
+  font-size: 0.875rem;
+  color: var(--color-gray-600);
+}
+
+/* Term/taxonomy listing styles */
+.term-list {
+  display: flex;
+  flex-direction: column;
+  gap: 0.5rem;
+}
+
+.term-item {
+  a {
+    font-size: 1.125rem;
+    transition: color 0.2s;
+    color: var(--color-gray-900);
+
+    &:hover,
+    &:focus {
+      color: var(--color-link);
+    }
+  }
+}
+
+.term-count {
+  font-size: 0.875rem;
+  color: var(--color-gray-700);
+}
+
+.term-description {
+  font-size: 0.875rem;
+  margin-bottom: 1.5rem;
+  color: var(--color-gray-600);
+}
+
+/* Last modified date footer */
+.content-last-modified {
+  margin: 3rem .5rem .5rem .5rem;
+  padding-top: 2rem;
+  border-top: 1px solid;
+  border-color: var(--color-gray-200);
+  font-style: italic;
+
+  p {
+    font-size: 0.875rem;
+    margin-bottom: 0;
+    color: var(--color-gray-600);
+
+    strong {
+      font-weight: 600;
+      color: var(--color-gray-700);
+    }
+
+    time {
+      color: var(--color-gray-600);
+    }
+  }
+}
diff --git a/themes/clean-hugo/assets/css/_docs.scss b/themes/clean-hugo/assets/css/_docs.scss
new file mode 100644
index 00000000..cd468ea0
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_docs.scss
@@ -0,0 +1,512 @@
+/**
+ * Documentation Layout Styles
+ * Using mixins and variables
+ */
+
+/* Documentation Header */
+.docs-header {
+  padding: 1rem 0;
+  margin-bottom: 2rem;
+  background-color: var(--color-primary-dark);
+
+  /* Color variants */
+  &--primary {
+    background-color: var(--color-primary);
+  }
+
+  &--primaryDark {
+    background-color: var(--color-primary-dark);
+  }
+
+  &--secondary {
+    background-color: var(--color-secondary);
+  }
+
+  &--accent {
+    background-color: var(--color-accent);
+  }
+
+  &--neutral {
+    background-color: var(--color-neutral);
+  }
+}
+
+.docs-header__inner {
+  @include container;
+}
+
+.docs-header__title {
+  @include responsive(font-size, 1.5rem, 1.25rem);
+  font-weight: 700;
+  color: white;
+  margin: 0;
+}
+
+.docs-layout {
+  @include container;
+  display: grid;
+  gap: 3rem;
+  padding-block: 2rem;
+  position: relative;
+  grid-template-columns: 1fr;
+
+  @media (min-width: $breakpoint-lg) {
+    grid-template-columns: 280px 1fr;
+    gap: 2rem;
+  }
+}
+
+/* Sidebar Navigation */
+.docs-sidebar {
+  /* Mobile: fixed slide-out drawer */
+  position: fixed;
+  top: 0;
+  left: 0;
+  width: 300px;
+  height: 100vh;
+  background-color: white;
+  padding: 1rem;
+  max-height: 100vh;
+  overflow-y: auto;
+  z-index: 1001;
+  transform: translateX(-300px);
+  transition: transform $transition-fast ease-in-out;
+  box-shadow: $shadow-lg;
+  border-right: 1px solid var(--color-gray-200);
+  @include custom-scrollbar;
+
+  &.open {
+    transform: translateX(0);
+  }
+
+  /* Desktop: static sidebar in layout */
+  @media (min-width: $breakpoint-lg) {
+    position: static;
+    width: auto;
+    height: fit-content;
+    top: 2rem;
+    max-height: calc(100vh - 4rem);
+    padding-right: 1rem;
+    transform: none;
+    box-shadow: none;
+    border-right: none;
+    border-bottom: 2px solid var(--color-gray-200);
+    padding-bottom: 2rem;
+    z-index: auto;
+  }
+}
+
+/* Overlay for mobile sidebar */
+.overlay {
+  position: fixed;
+  top: 0;
+  left: 0;
+  width: 100%;
+  height: 100%;
+  background-color: rgba(0, 0, 0, 0.5);
+  opacity: 0;
+  visibility: hidden;
+  transition: opacity $transition-fast, visibility $transition-fast;
+  z-index: 1000;
+
+  &.open {
+    opacity: 1;
+    visibility: visible;
+  }
+
+  @media (min-width: $breakpoint-lg) {
+    display: none;
+  }
+}
+
+/* Mobile toggle button for sidebar */
+.docs-toggle {
+  position: fixed;
+  top: 1rem;
+  left: 1rem;
+  width: 2.5rem;
+  height: 2.5rem;
+  background-color: var(--color-primary-dark);
+  border: none;
+  border-radius: $radius-md;
+  color: white;
+  cursor: pointer;
+  z-index: 1002;
+  @include flex-center;
+  transition: all $transition-fast;
+  box-shadow: $shadow-md;
+
+  &:hover {
+    background-color: var(--color-primary);
+    box-shadow: $shadow-lg;
+  }
+
+  i {
+    font-size: 1.25rem;
+  }
+
+  @media (min-width: $breakpoint-lg) {
+    display: none;
+  }
+}
+
+/* Section navigation */
+.docs-section-nav {
+  margin-bottom: 1.5rem;
+}
+
+.docs-section-title {
+  font-size: 0.875rem;
+  font-weight: 700;
+  color: var(--color-gray-900);
+  margin-bottom: 0.75rem;
+  text-transform: uppercase;
+  letter-spacing: 0.025em;
+}
+
+.docs-nav-separator {
+  border-top: 1px solid var(--color-gray-200);
+  margin: 1.5rem 0;
+}
+
+.docs-section-list {
+  display: flex;
+  flex-direction: column;
+  gap: 0.25rem;
+}
+
+/* Navigation items generated by JavaScript */
+.docs-nav__list {
+  list-style: none;
+  padding: 0;
+  margin: 0;
+}
+
+.docs-nav__item {
+  margin-bottom: 0.5rem;
+
+  &--sub {
+    margin-bottom: 0.25rem;
+  }
+}
+
+.docs-nav__sublist {
+  list-style: none;
+  padding-left: 1rem;
+  margin: 0.5rem 0;
+  border-left: 2px solid var(--color-gray-200);
+}
+
+.docs-nav__link {
+  display: block;
+  padding: 0.5rem 0.75rem;
+  color: var(--color-gray-700);
+  text-decoration: none;
+  border-radius: $radius-md;
+  transition: all $transition-fast;
+  line-height: 1.375;
+  font-size: 0.875rem;
+
+  &:hover {
+    background-color: var(--color-gray-200);
+    color: var(--color-primary-dark);
+  }
+
+  &--active {
+    font-weight: 600;
+    background-color: var(--color-primary-light);
+    color: var(--color-primary-dark);
+  }
+
+  .docs-nav__item--sub & {
+    padding: 0.375rem 0.75rem;
+    font-size: 0.75rem;
+  }
+}
+
+/* Hugo-generated menu styles */
+.docs-menu__list {
+  list-style: none;
+  padding: 0;
+  margin: 0;
+
+  &--level-2 {
+    padding-left: 1rem;
+    margin-top: 0.5rem;
+    border-left: 2px solid var(--color-gray-200);
+  }
+
+  &--level-3 {
+    padding-left: 1rem;
+    margin-top: 0.25rem;
+  }
+}
+
+.docs-menu__item {
+  margin-bottom: 0.25rem;
+
+  &--expanded {
+    margin-bottom: 0.5rem;
+  }
+}
+
+.docs-menu__link {
+  display: block;
+  padding: 0.5rem 0.75rem;
+  color: var(--color-gray-700);
+  text-decoration: none;
+  border-radius: $radius-md;
+  transition: all $transition-fast;
+  line-height: 1.375;
+  font-size: 0.875rem;
+
+  &:hover {
+    background-color: var(--color-gray-200);
+    color: var(--color-primary-dark);
+  }
+
+  &--active {
+    font-weight: 600;
+    background-color: var(--color-primary-light);
+    color: var(--color-primary-dark);
+  }
+
+  // Icon spacing
+  i {
+    margin-right: 0.5rem;
+    width: 1rem;
+    text-align: center;
+  }
+
+  .docs-menu__list--level-2 & {
+    padding: 0.375rem 0.75rem;
+    font-size: 0.8125rem;
+  }
+
+  .docs-menu__list--level-3 & {
+    padding: 0.25rem 0.75rem;
+    font-size: 0.75rem;
+  }
+}
+
+/* Inline Table of Contents (in sidebar under active page) */
+.toc-items {
+  list-style: none;
+  padding: 0.5rem 0 0 1rem;
+  margin: 0.5rem 0 0 0;
+  border-left: 2px solid var(--color-gray-200);
+}
+
+.toc-item {
+  margin-bottom: 0.25rem;
+
+  &--sub {
+    margin-bottom: 0.125rem;
+  }
+}
+
+.toc-sublist {
+  list-style: none;
+  padding-left: 0.75rem;
+  margin: 0.25rem 0;
+}
+
+.toc-link {
+  display: block;
+  padding: 0.375rem 0.75rem;
+  color: var(--color-gray-600);
+  text-decoration: none;
+  border-radius: $radius-sm;
+  transition: all $transition-fast;
+  line-height: 1.3;
+  font-size: 0.75rem;
+
+  &:hover {
+    background-color: var(--color-gray-100);
+    color: var(--color-primary-dark);
+  }
+
+  &--active {
+    font-weight: 500;
+    color: var(--color-primary-dark);
+    background-color: var(--color-primary-light);
+  }
+
+  .toc-item--sub & {
+    padding: 0.25rem 0.75rem;
+    font-size: 0.6875rem;
+    color: var(--color-gray-500);
+  }
+
+  .toc-item--sub &:hover {
+    color: var(--color-primary-dark);
+  }
+}
+
+/* "On This Page" TOC container */
+#docs-page-toc {
+  margin-top: 1.5rem;
+}
+
+/* Main Content */
+.docs-content {
+  min-width: 0;
+  max-width: $container-narrow;
+
+  h1 {
+    @include responsive(font-size, 2.25rem, 1.875rem);
+    font-weight: 700;
+    color: var(--color-gray-900);
+    margin-bottom: 1rem;
+    line-height: 1.25;
+  }
+
+  h2 {
+    font-size: 1.875rem;
+    font-weight: 700;
+    color: var(--color-gray-900);
+    margin-top: 3rem;
+    margin-bottom: 1rem;
+    padding-bottom: 0.5rem;
+    border-bottom: 2px solid var(--color-gray-200);
+    scroll-margin-top: 2rem;
+
+    &:first-child {
+      margin-top: 0;
+    }
+  }
+
+  h3 {
+    font-size: 1.5rem;
+    font-weight: 600;
+    color: var(--color-gray-900);
+    margin-top: 2rem;
+    margin-bottom: 0.75rem;
+    scroll-margin-top: 2rem;
+  }
+
+  h4 {
+    font-size: 1.25rem;
+    font-weight: 600;
+    color: var(--color-gray-900);
+    margin-top: 1.5rem;
+    margin-bottom: 0.5rem;
+  }
+
+  p {
+    margin-bottom: 1rem;
+    color: var(--color-gray-700);
+    line-height: 1.625;
+  }
+
+  ul, ol {
+    margin-bottom: 1rem;
+    padding-left: 1.5rem;
+    color: var(--color-gray-700);
+
+    li {
+      margin-bottom: 0.5rem;
+    }
+  }
+
+  pre {
+    margin-bottom: 1.5rem;
+    border-radius: $radius-md;
+    overflow-x: auto;
+  }
+
+  code {
+    font-size: 0.875rem;
+    font-family: $font-family-mono;
+  }
+
+  p code,
+  li code {
+    background-color: var(--color-gray-200);
+    padding: 0.125rem 0.375rem;
+    border-radius: $radius-sm;
+    color: var(--color-gray-900);
+  }
+
+  a {
+    text-decoration: underline;
+    color: var(--color-link);
+
+    &:hover {
+      color: var(--color-link-hover);
+    }
+  }
+
+  table {
+    width: 100%;
+    margin-bottom: 1.5rem;
+    border-collapse: collapse;
+
+    th, td {
+      padding: 0.75rem;
+      border: 1px solid var(--color-gray-200);
+      text-align: left;
+    }
+
+    th {
+      background-color: var(--color-gray-200);
+      font-weight: 600;
+    }
+  }
+
+  img {
+    max-width: 100%;
+    height: auto;
+    border-radius: $radius-md;
+    margin: 1.5rem 0;
+  }
+}
+
+.docs-excerpt {
+  font-size: 1.25rem;
+  color: var(--color-gray-600);
+  margin-bottom: 2rem;
+  line-height: 1.625;
+}
+
+/* Scroll to Top Button */
+.docs-scroll-btn {
+  position: fixed;
+  bottom: 2rem;
+  right: 2rem;
+  width: 3rem;
+  height: 3rem;
+  border-radius: $radius-full;
+  border: none;
+  cursor: pointer;
+  @include flex-center;
+  box-shadow: $shadow-lg;
+  opacity: 0;
+  visibility: hidden;
+  transition: all $transition-fast;
+  z-index: $z-fixed;
+  background-color: var(--color-primary-dark);
+  color: white;
+
+  @media (min-width: $breakpoint-md) {
+    bottom: 1rem;
+    right: 1rem;
+    width: 2.5rem;
+    height: 2.5rem;
+  }
+
+  &:hover {
+    transform: translateY(-0.125rem);
+    background-color: var(--color-primary);
+    box-shadow: 0 6px 12px rgba(0, 0, 0, 0.15);
+  }
+
+  &--visible {
+    opacity: 1;
+    visibility: visible;
+  }
+
+  i {
+    @include responsive(font-size, 1.25rem, 1rem);
+  }
+}
diff --git a/themes/clean-hugo/assets/css/_events.scss b/themes/clean-hugo/assets/css/_events.scss
new file mode 100644
index 00000000..aaaa3c17
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_events.scss
@@ -0,0 +1,430 @@
+/* Events listing (/events/) — uses global .container */
+.events-list {
+  padding: 2rem 0 4rem;
+}
+
+.blog-hero .events-list__intro {
+  color: rgba(255, 255, 255, 0.92);
+  font-size: 1.125rem;
+  line-height: 1.5;
+  max-width: 42rem;
+  margin: 0.5rem 0 0;
+}
+
+/* Small caps section label above upcoming cards */
+.events-list__kicker {
+  font-family: $font-family-body;
+  font-size: 0.75rem;
+  font-weight: 600;
+  letter-spacing: 0.14em;
+  text-transform: uppercase;
+  color: var(--color-gray-600);
+  margin: 0 0 1rem;
+}
+
+.events-list__kicker-amp {
+  letter-spacing: 0.08em;
+}
+
+.events-list__heading {
+  margin-top: 2.5rem;
+  margin-bottom: 1.25rem;
+  font-size: 1.75rem;
+
+  &:first-of-type {
+    margin-top: 0;
+  }
+}
+
+/* Upcoming/live: flexible grid for many events */
+.events-list__featured {
+  display: grid;
+  gap: 1.25rem;
+  grid-template-columns: repeat(auto-fill, minmax(16rem, 1fr));
+
+  @media (min-width: $breakpoint-lg) {
+    gap: 1.5rem;
+  }
+}
+
+.events-list__empty {
+  color: var(--color-gray-700);
+  margin-bottom: 2rem;
+}
+
+.events-list__types {
+  margin-top: 3rem;
+  margin-bottom: 1rem;
+}
+
+.events-list__actions {
+  margin-top: 1.5rem;
+  display: flex;
+  justify-content: flex-start;
+}
+
+/* Event archive bands reuse .blog-archives + .listing-card--blog-archive from _blog.scss */
+.events-past-archives {
+  margin-top: 0;
+}
+
+.events-upcoming-archives .events-list__kicker-amp,
+.events-past-archives .events-list__kicker-amp {
+  letter-spacing: 0.08em;
+}
+
+/* Event type pill — colors from hugo.toml CSS variables */
+.event-card__type {
+  display: inline-flex;
+  align-items: center;
+  font-size: 0.75rem;
+  font-weight: 600;
+  padding: 0.3rem 0.7rem;
+  border-radius: 9999px;
+  line-height: 1.2;
+  white-space: nowrap;
+  max-width: 100%;
+}
+
+.event-card__type--training {
+  background-color: var(--color-event-label-training-bg, var(--color-primary-light));
+  color: var(--color-event-label-training-fg, var(--color-primary-dark));
+}
+
+.event-card__type--sprint {
+  background-color: var(--color-event-label-sprint-bg, var(--color-accent-light));
+  color: var(--color-event-label-sprint-fg, var(--color-gray-900));
+}
+
+.event-card__type--community {
+  background-color: var(--color-event-label-community-bg, var(--color-secondary));
+  color: var(--color-event-label-community-fg, var(--color-gray-900));
+}
+
+.event-card__type--talk {
+  background-color: var(--color-event-label-talk-bg, var(--color-admonition-note, #cae4e4));
+  color: var(--color-event-label-talk-fg, var(--color-primary-dark));
+}
+
+.event-card__type--default {
+  background-color: var(--color-gray-200);
+  color: var(--color-gray-700);
+}
+
+/* Featured (upcoming/live) cards — white surface, mock-inspired layout */
+.event-card--featured {
+  > a {
+    display: flex;
+    flex-direction: column;
+    height: 100%;
+    min-height: 12rem;
+    padding: 0;
+    overflow: hidden;
+    text-decoration: none;
+    color: inherit;
+    border-radius: $radius-md;
+    background-color: var(--color-white);
+    box-shadow: $shadow-sm;
+    border: 1px solid var(--color-gray-200);
+    transition: box-shadow $transition-base ease-in-out, transform $transition-base ease-in-out;
+
+    &:hover {
+      box-shadow: $shadow-lg;
+      transform: translateY(-2px);
+
+      .event-card__cta {
+        color: var(--color-link-hover);
+      }
+    }
+  }
+}
+
+.event-card__featured-image {
+  margin: 0;
+  aspect-ratio: 16 / 9;
+  overflow: hidden;
+
+  img {
+    width: 100%;
+    height: 100%;
+    object-fit: cover;
+    display: block;
+    transition: transform $transition-base ease-out;
+  }
+}
+
+.event-card--featured:hover .event-card__featured-image img {
+  transform: scale(1.03);
+}
+
+.event-card__featured-inner {
+  display: flex;
+  flex-direction: column;
+  height: 100%;
+  gap: 0.65rem;
+  min-height: 0;
+  padding: 1.25rem 1.35rem;
+  flex: 1 1 auto;
+}
+
+.event-card--featured:not(.event-card--with-image) > a {
+  padding: 1.25rem 1.35rem;
+}
+
+.event-card__featured-top {
+  display: flex;
+  align-items: flex-start;
+  justify-content: space-between;
+  gap: 0.75rem;
+}
+
+.event-card__date-badge {
+  flex-shrink: 0;
+  min-width: 3.25rem;
+  max-width: 8rem;
+  padding: 0.45rem 0.5rem;
+  border-radius: $radius-sm;
+  background-color: var(--color-event-date-badge-bg, var(--color-accent));
+  color: var(--color-event-date-badge-fg, var(--color-white));
+  text-align: center;
+  display: flex;
+  flex-direction: column;
+  align-items: center;
+  justify-content: center;
+  line-height: 1.15;
+}
+
+.event-card__date-badge-primary {
+  font-size: 1.0625rem;
+  font-weight: 800;
+  letter-spacing: 0.02em;
+}
+
+.event-card__date-badge-secondary {
+  font-size: 0.65rem;
+  font-weight: 700;
+  letter-spacing: 0.08em;
+}
+
+.event-card__date-badge-year {
+  font-size: 0.6rem;
+  font-weight: 600;
+  margin-top: 0.15rem;
+  opacity: 0.95;
+}
+
+.event-card--featured .event-card__title {
+  font-size: 1.25rem;
+  font-weight: 700;
+  line-height: 1.25;
+  margin: 0;
+  color: var(--color-gray-900);
+}
+
+.event-card__meta {
+  margin: 0;
+  font-size: 0.9375rem;
+  line-height: 1.45;
+  color: var(--color-gray-600);
+}
+
+.event-card__cta {
+  margin-top: auto;
+  padding-top: 0.35rem;
+  font-size: 0.875rem;
+  font-weight: 600;
+  color: var(--color-link);
+}
+
+/* Compact past cards (horizontal thumb) */
+.event-card:not(.event-card--featured) {
+  > a {
+    display: block;
+    height: 100%;
+    text-decoration: none;
+    color: inherit;
+    border-radius: $radius-md;
+    overflow: hidden;
+    background-color: var(--color-white);
+    box-shadow: $shadow-sm;
+    border: 1px solid var(--color-gray-200);
+    transition: box-shadow $transition-base ease-in-out, transform $transition-base ease-in-out;
+
+    &:hover {
+      box-shadow: $shadow-lg;
+      transform: translateY(-2px);
+    }
+  }
+}
+
+.event-card__content {
+  display: flex;
+  flex-direction: row;
+  min-height: 0;
+}
+
+.event-card__date {
+  position: relative;
+  flex: 0 0 6.5rem;
+  min-height: 7rem;
+  overflow: hidden;
+}
+
+.event-card__date-background {
+  position: absolute;
+  inset: 0;
+  background-size: cover;
+  background-position: center;
+
+  &--default {
+    background: linear-gradient(145deg, var(--color-primary) 0%, var(--color-primary-dark) 100%);
+  }
+}
+
+.event-card__date-text {
+  position: relative;
+  z-index: 1;
+  display: flex;
+  flex-direction: column;
+  align-items: center;
+  justify-content: center;
+  height: 100%;
+  padding: 0.5rem;
+  color: var(--color-white);
+  text-shadow: 0 1px 2px rgba(0, 0, 0, 0.35);
+  font-weight: 700;
+  line-height: 1.15;
+  text-align: center;
+
+  span {
+    font-size: 0.75rem;
+    font-weight: 600;
+    letter-spacing: 0.02em;
+  }
+
+  span:first-child {
+    font-size: 1.25rem;
+    font-weight: 800;
+  }
+
+  span:nth-child(3) {
+    font-size: 0.7rem;
+    opacity: 0.95;
+  }
+}
+
+.event-card__details {
+  flex: 1;
+  padding: 1rem 1.125rem;
+  display: flex;
+  flex-direction: column;
+  gap: 0.5rem;
+  min-width: 0;
+}
+
+.event-card__type--inline {
+  align-self: flex-start;
+  margin-bottom: 0.15rem;
+}
+
+.event-card__title {
+  font-size: 1.125rem;
+  font-weight: 600;
+  line-height: 1.3;
+  margin: 0;
+  color: var(--color-gray-900);
+}
+
+.event-card__details p {
+  margin: 0;
+  font-size: 0.875rem;
+  line-height: 1.5;
+  color: var(--color-gray-600);
+}
+
+.event-card__button {
+  margin-top: auto;
+  font-size: 0.8125rem;
+  font-weight: 600;
+  color: var(--color-primary);
+}
+
+/* Event detail: instructors (optional front matter) */
+.event-instructors {
+  margin-top: 3rem;
+  padding-top: 2rem;
+  border-top: 1px solid var(--color-gray-200);
+}
+
+.event-instructors__heading {
+  font-size: 1.5rem;
+  margin-bottom: 1.25rem;
+}
+
+.event-instructors__grid {
+  list-style: none;
+  margin: 0;
+  padding: 0;
+  display: grid;
+  gap: 1.5rem;
+  grid-template-columns: 1fr;
+
+  @media (min-width: $breakpoint-md) {
+    grid-template-columns: repeat(2, 1fr);
+  }
+}
+
+.event-instructors__card {
+  display: flex;
+  gap: 1rem;
+  align-items: flex-start;
+  padding: 1rem;
+  border-radius: $radius-md;
+  border: 1px solid var(--color-gray-200);
+  background-color: var(--color-white);
+  box-shadow: $shadow-sm;
+}
+
+.event-instructors__avatar {
+  flex-shrink: 0;
+  width: 5rem;
+  height: 5rem;
+  border-radius: 9999px;
+  object-fit: cover;
+}
+
+.event-instructors__name {
+  margin: 0 0 0.5rem;
+  font-size: 1.125rem;
+}
+
+.event-instructors__bio {
+  margin: 0;
+  font-size: 0.9375rem;
+  line-height: 1.5;
+  color: var(--color-gray-700);
+}
+
+.event-card--compact {
+  .event-card__date {
+    flex-basis: 4.5rem;
+    min-height: 5rem;
+  }
+
+  .event-card__date-text span:first-child {
+    font-size: 1rem;
+  }
+
+  .event-card__details {
+    padding: 0.75rem 0.875rem;
+  }
+
+  .event-card__title {
+    font-size: 0.9375rem;
+  }
+
+  .event-card__type {
+    font-size: 0.65rem;
+    padding: 0.2rem 0.5rem;
+  }
+}
diff --git a/themes/clean-hugo/assets/css/_feature-section.scss b/themes/clean-hugo/assets/css/_feature-section.scss
new file mode 100644
index 00000000..d9588c57
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_feature-section.scss
@@ -0,0 +1,111 @@
+  /* Container classes for both feature and feature-section */
+  .feature,
+  .feature-section {
+    padding: $fluid-space-2xl 0;
+
+    header {
+      @include responsive(margin-bottom, 2.5rem, 3rem);
+      text-align: center;
+
+      h2 {
+        @include responsive(font-size, 2.25rem, 3.75rem);
+        font-weight: 700;
+        margin-bottom: 1rem;
+
+        @media (min-width: $breakpoint-sm) {
+          font-size: 3rem;
+        }
+      }
+
+      p {
+        @include responsive(font-size, 1.125rem, 1.5rem);
+        opacity: 0.8;
+        max-width: 48rem;
+        margin-inline: auto;
+
+        @media (min-width: $breakpoint-sm) {
+          font-size: 1.25rem;
+        }
+      }
+    }
+
+    div {
+      display: grid;
+      grid-template-columns: 1fr;
+      gap: 2rem;
+    }
+  }
+
+  /* Unified feature card — same shell as interactive cards, no hover motion */
+  .feature-card {
+    @include card-surface($bg: var(--color-feature-card));
+    padding: $fluid-card-padding-md;
+  }
+
+  .feature-card h3 {
+    @include responsive(font-size, 1.25rem, 1.875rem);
+    font-weight: 800;
+    margin-top: 2rem;
+    margin-bottom: 1rem;
+
+    @media (min-width: $breakpoint-sm) {
+      font-size: 1.5rem;
+    }
+
+    &:first-child {
+      margin-top: 0;
+    }
+  }
+
+  .feature-card h4 {
+    @include responsive(font-size, 1.125rem, 1.25rem);
+    font-weight: 600;
+    margin-top: 2rem;
+    margin-bottom: 0.75rem;
+  }
+
+  .feature-card .lead {
+    @include responsive(font-size, 1.125rem, 1.25rem);
+    margin-bottom: 1.5rem;
+  }
+
+  .feature-card p {
+    @include responsive(font-size, 1rem, 1.25rem);
+    margin-bottom: 1.5rem;
+
+    @media (min-width: $breakpoint-sm) {
+      font-size: 1.125rem;
+    }
+  }
+
+  .feature-card ul {
+    list-style-type: disc;
+    padding-left: 1.5rem;
+    padding-right: 1rem;
+    @include responsive(font-size, 1rem, 1.125rem);
+    line-height: 1.625;
+
+    > li + li {
+      margin-top: 0.5rem;
+    }
+  }
+
+  .feature-card ul.links a {
+    text-decoration: underline;
+    color: var(--color-link);
+
+    &:hover,
+    &:focus {
+      color: var(--color-link-hover);
+    }
+  }
+
+  .feature-card a {
+    text-decoration: underline;
+    color: currentColor;
+
+    &:hover,
+    &:focus {
+      color: var(--color-link);
+    }
+  }
diff --git a/themes/clean-hugo/assets/css/_figure.scss b/themes/clean-hugo/assets/css/_figure.scss
new file mode 100644
index 00000000..f6f9a4e2
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_figure.scss
@@ -0,0 +1,22 @@
+/* Figure shortcode styles */
+.figure {
+  margin: 1.5rem 0;
+
+  &__link,
+  &__picture {
+    display: block;
+  }
+
+  &__image {
+    width: 100%;
+    height: auto;
+    border-radius: $radius-md;
+  }
+
+  &__caption {
+    margin-top: 0.5rem;
+    font-size: 0.875rem;
+    text-align: center;
+    color: var(--color-gray-600);
+  }
+}
diff --git a/themes/clean-hugo/assets/css/_filter.scss b/themes/clean-hugo/assets/css/_filter.scss
new file mode 100644
index 00000000..162989a7
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_filter.scss
@@ -0,0 +1,56 @@
+/* Filterable grid page container and headings to match blog layout */
+.filterable-grid-container {
+  max-width: $container-narrow;
+  margin: 0 auto;
+  padding: 0 $fluid-container-padding;
+}
+
+.filterable-grid-title {
+  @include responsive(font-size, 2rem, 2.5rem, 3rem);
+  font-weight: 800;
+  margin-bottom: 1rem;
+}
+
+.filterable-grid-body {
+  font-size: 1rem;
+  line-height: 1.625;
+  color: var(--color-gray-700);
+  @media (min-width: $breakpoint-lg) {
+    font-size: 1.25rem;
+  }
+}
+/* Filter Components */
+.filter-row {
+  display: flex;
+  flex-wrap: wrap;
+  gap: 0.75rem;
+  margin-bottom: 2rem;
+  justify-content: center;
+}
+
+.filter-btn {
+  padding: 0.5rem 1rem;
+  border-radius: $radius-full;
+  font-size: 0.875rem;
+  font-weight: 500;
+  border: 1px solid var(--color-gray-200);
+  background-color: var(--color-white);
+  color: var(--color-gray-700);
+  cursor: pointer;
+  transition: all $transition-base;
+
+  &[aria-pressed="true"] {
+    background-color: var(--color-primary);
+    border-color: var(--color-primary);
+    color: white;
+  }
+
+  &[aria-pressed="false"]:hover {
+    background-color: var(--color-gray-50);
+    border-color: var(--color-gray-600);
+  }
+
+  &:focus {
+    @include focus-ring;
+  }
+}
diff --git a/themes/clean-hugo/assets/css/_footer.scss b/themes/clean-hugo/assets/css/_footer.scss
new file mode 100644
index 00000000..59a25b33
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_footer.scss
@@ -0,0 +1,126 @@
+.site-footer {
+  width: 100%;
+  margin-top: $spacing-xl;
+  padding: $spacing-lg $spacing-sm $spacing-lg;
+  color: rgba(255, 255, 255, 0.9);
+  font-family: $font-family-heading;
+  font-size: 0.85rem;
+  line-height: 1.3rem;
+  background-color: color-mix(in srgb, var(--color-brand-purple) 92%, black);
+
+  &__inner {
+    display: flex;
+    flex-direction: column;
+    align-items: center;
+    gap: $spacing-sm;
+    max-width: $container-max-width;
+    margin: 0 auto;
+    padding: 0 $spacing-sm;
+  }
+
+  &__follow {
+    width: 100%;
+    text-align: center;
+
+    .social-icons {
+      display: flex;
+      flex-wrap: wrap;
+      justify-content: center;
+      gap: $spacing-sm;
+      margin: 0;
+      padding: 0;
+      list-style: none;
+    }
+
+    li {
+      display: inline-flex;
+    }
+  }
+
+  &__social-link {
+    position: relative;
+    display: inline-flex;
+    align-items: center;
+    justify-content: center;
+    width: 2.75rem;
+    height: 2.75rem;
+    text-decoration: none;
+    border-radius: $radius-md;
+    transition: color $transition-base;
+
+    i {
+      font-size: 1.75rem;
+      color: color-mix(in srgb, var(--color-white) 42%, var(--color-soft-purple));
+      transition: color $transition-base;
+    }
+
+    &:hover i,
+    &:focus-visible i {
+      color: color-mix(in srgb, var(--color-white) 92%, var(--color-light-purple));
+    }
+
+    &[data-tooltip]::after {
+      content: attr(data-tooltip);
+      position: absolute;
+      bottom: calc(100% + 0.35rem);
+      left: 50%;
+      transform: translateX(-50%);
+      padding: 0.2rem 0.5rem;
+      font-family: $font-family-heading;
+      font-size: 0.7rem;
+      font-weight: 600;
+      line-height: 1.2;
+      white-space: nowrap;
+      color: var(--color-white);
+      background-color: color-mix(in srgb, var(--color-brand-purple) 75%, black);
+      border-radius: $radius-sm;
+      opacity: 0;
+      pointer-events: none;
+      transition: opacity $transition-fast;
+    }
+
+    &:hover::after,
+    &:focus-visible::after {
+      opacity: 1;
+    }
+
+    &:focus-visible {
+      outline: 2px solid var(--color-white);
+      outline-offset: 2px;
+    }
+  }
+
+  &__copyright {
+    width: 100%;
+    max-width: 56.25rem;
+    margin: 0 auto;
+    padding: $spacing-sm;
+    text-align: left;
+    line-height: 1.35;
+
+    p {
+      margin: 0 0 0.5em;
+      color: rgba(255, 255, 255, 0.82);
+    }
+  }
+
+  &__mission {
+    font-size: 0.85rem;
+    line-height: 1.4;
+  }
+
+  &__copyright a {
+    color: rgba(255, 255, 255, 0.82);
+    text-decoration: none;
+
+    &:hover {
+      color: var(--color-white);
+      text-decoration: underline;
+    }
+  }
+
+  &__copy {
+    margin: 0;
+    font-size: 0.68rem;
+  }
+}
diff --git a/themes/clean-hugo/assets/css/_gallery.scss b/themes/clean-hugo/assets/css/_gallery.scss
new file mode 100644
index 00000000..7c46ff1c
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_gallery.scss
@@ -0,0 +1,172 @@
+/* Gallery Components - Using Mixins */
+
+/* Shared container styles - max-width 80rem with responsive padding */
+.gallery-list-wrapper,
+.gallery-grid-container,
+.gallery-images {
+  @include container;
+}
+
+.gallery-images {
+  @include responsive-padding($spacing-section, 1rem);
+}
+
+/* Gallery grid elements with BEM nesting */
+.gallery-grid {
+  &__title {
+    @include responsive(font-size, 1.5rem, 1.875rem);
+    font-weight: 700;
+    margin-bottom: 1rem;
+  }
+
+  &__category-title {
+    @include responsive(font-size, 1.25rem, 1.5rem);
+    font-weight: 600;
+    margin-bottom: 1rem;
+    text-transform: capitalize;
+  }
+
+  &__section {
+    margin-bottom: $spacing-section;
+  }
+
+  &__items {
+    @include grid-auto-fit;
+  }
+}
+
+/* Gallery content wrapper - narrower max-width */
+.gallery-content {
+  @include container($container-narrow);
+  padding: 0 $fluid-container-padding-lg;
+}
+
+/* Gallery header with nested elements */
+.gallery-header {
+  margin-bottom: 2rem;
+
+  h2 {
+    @include responsive(font-size, 1.5rem, 1.875rem, 2.25rem);
+    margin-bottom: 0.5rem;
+  }
+
+  .common-name {
+    font-size: 1.125rem;
+    margin-bottom: 1rem;
+    color: var(--color-gray-600);
+  }
+}
+
+/* Markdown body */
+.gallery-description {
+  max-width: none;
+
+  /* Hide h1 in gallery description - title should only be in hero */
+  h1 {
+    display: none;
+  }
+}
+
+/* Gallery images section heading */
+.gallery-images h2 {
+  @include responsive(font-size, 1.25rem, 1.5rem, 1.875rem);
+  margin-bottom: 1rem;
+}
+
+/* Masonry layout using CSS columns */
+.gallery-masonry {
+    columns: 1;
+    column-gap: clamp(0.5rem, 2vw, 1.5rem);
+    padding: clamp(0.5rem, 2vw, 1.5rem);
+
+  figure {
+    break-inside: avoid;
+    margin-bottom: clamp(0.25rem, 1vw, .5rem);
+    display: block;
+  }
+
+  img {
+    width: 100%;
+    max-width: 100%;
+    height: auto;
+    display: block;
+  }
+
+  a {
+    display: block;
+    &:hover img {
+      transform: scale(1.03);
+    }
+  }
+
+  @media (min-width: $breakpoint-sm) {
+    columns: 2;
+    padding-inline: 0;
+  }
+  @media (min-width: $breakpoint-lg) {
+    columns: 3;
+  }
+
+  img {
+    width: 100%;
+    height: auto;
+    display: block;
+    border-radius: $radius-md;
+    transition: transform $transition-base ease-out;
+    cursor: zoom-in;
+  }
+
+  figcaption {
+    display: block;
+  }
+}
+
+.gallery-caption {
+  padding: 0.625rem;
+  font-size: 0.875rem;
+  color: var(--color-gray-700);
+}
+
+/* Gallery card component with BEM nesting */
+.gallery-card {
+  position: relative;
+  display: flex;
+  flex-direction: column;
+  width: 100%;
+  max-width: 340px;
+  border: 1px solid var(--color-gray-200);
+  border-radius: $radius-lg;
+  overflow: hidden;
+  background-color: var(--color-white);
+  box-shadow: $shadow-md;
+  transition: box-shadow $transition-base ease-out;
+
+  &__link {
+    display: block;
+
+    &:focus {
+      @include focus-ring;
+    }
+  }
+
+  &__image {
+    @include image-zoom;
+    width: 100%;
+    height: 10rem;
+  }
+
+  &__content {
+    display: flex;
+    flex-direction: column;
+    gap: 0.75rem;
+    padding: 1.5rem;
+  }
+
+  &__title {
+    font-family: $font-family-heading;
+    font-weight: 700;
+    font-size: 1.125rem;
+    padding: 0.5rem 0.75rem;
+    color: var(--color-gray-900);
+  }
+}
diff --git a/themes/clean-hugo/assets/css/_hero.scss b/themes/clean-hugo/assets/css/_hero.scss
new file mode 100644
index 00000000..4b576dcd
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_hero.scss
@@ -0,0 +1,152 @@
+/* Hero section components */
+
+.hero {
+  padding: 0.5rem 0;
+  @include flex-center;
+  overflow: hidden;
+  margin-bottom: 3rem;
+  background-color: var(--color-hero-bg);
+  width: 100%;
+  max-width: 100vw;
+
+  /* Direct child .container gets additional padding */
+  > .container {
+    width: 100%;
+    @include responsive(padding-top, 0.875rem, 2rem);
+    @include responsive(padding-bottom, 0.875rem, 2rem);
+  }
+
+  &__grid {
+    display: grid;
+    @include responsive(gap, 1.5rem, 2rem);
+    align-items: center;
+
+    @media (min-width: $breakpoint-md) {
+      grid-template-columns: repeat(12, 1fr);
+    }
+  }
+
+  &__content {
+    order: 2;
+    color: var(--color-white);
+
+    @media (min-width: $breakpoint-md) {
+      order: 1;
+      grid-column: span 12;
+    }
+  }
+
+  &__title {
+    @include responsive(font-size, 2.25rem, 3.75rem);
+    @include responsive(margin-bottom, 1rem, 1.5rem);
+    font-weight: 700;
+    color: white;
+
+    @media (min-width: $breakpoint-sm) {
+      font-size: 3rem;
+    }
+  }
+
+  &__subtitle {
+    @include responsive(font-size, 1.25rem, 1.875rem);
+    @include responsive(margin-bottom, 1rem, 1.5rem);
+    font-weight: 600;
+    color: white;
+
+    @media (min-width: $breakpoint-sm) {
+      font-size: 1.5rem;
+    }
+  }
+
+  &__excerpt {
+    @include responsive(font-size, 1rem, 1.25rem);
+    @include responsive(line-height, 1.5, 1.6);
+    color: white;
+
+    @media (min-width: $breakpoint-sm) {
+      font-size: 1.125rem;
+    }
+  }
+
+  &__actions {
+    @include responsive(margin-top, 1.25rem, 1.75rem);
+
+    &.btn-group {
+      @media (max-width: ($breakpoint-sm - 0.02px)) {
+        flex-direction: row;
+        flex-wrap: wrap;
+
+        .btn {
+          flex: 1 1 auto;
+          min-width: 0;
+          max-width: 100%;
+        }
+      }
+    }
+  }
+
+  &__image-wrapper {
+    order: 1;
+    display: flex;
+    justify-content: center;
+
+    @media (min-width: $breakpoint-md) {
+      order: 2;
+      grid-column: span 4;
+      justify-content: end;
+    }
+  }
+
+  &__image-container {
+    width: clamp(8rem, 25vw, 10rem);
+    height: clamp(8rem, 25vw, 10rem);
+    border-radius: $radius-full;
+    overflow: hidden;
+    border: 8px solid var(--color-white);
+    box-shadow: $shadow-2xl;
+
+    @media (min-width: $breakpoint-sm) {
+      width: 12rem;
+      height: 12rem;
+    }
+
+    @media (min-width: $breakpoint-md) {
+      width: 14rem;
+      height: 14rem;
+    }
+
+    @media (min-width: $breakpoint-lg) {
+      width: 16rem;
+      height: 16rem;
+    }
+  }
+
+  &__image {
+    width: 100%;
+    height: 100%;
+    object-fit: cover;
+  }
+}
+
+/* Square image variant for gallery/plant pages */
+.hero__image-container-square {
+    border-radius: $radius-md;
+    overflow: hidden;
+    border: 4px solid var(--color-white);
+    box-shadow: $shadow-2xl;
+    margin-inline: 0;
+    width: 260px;
+
+    @media (min-width: $breakpoint-sm) {
+      margin-inline: 1rem;
+    }
+
+    @media (min-width: $breakpoint-md) {
+      width: 340px;
+      margin-inline: 2rem;
+    }
+
+    @media (min-width: $breakpoint-lg) {
+      width: 400px;
+    }
+}
diff --git a/themes/clean-hugo/assets/css/_intro-section.scss b/themes/clean-hugo/assets/css/_intro-section.scss
new file mode 100644
index 00000000..43571b06
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_intro-section.scss
@@ -0,0 +1,22 @@
+/* Intro Section Component */
+.intro-section {
+  background-color: transparent;
+  @include responsive(padding, 1.75rem 0, 2.25rem 0, 3rem 0);
+
+  .container div {
+    text-align: center;
+
+    /* Intentionally larger paragraphs for intro sections */
+    p {
+      @include responsive(font-size, 1.25rem, 1.5rem);
+      line-height: 1.625;
+      color: var(--color-gray-700);
+      font-weight: 400;
+    }
+
+    strong {
+      color: var(--color-gray-900);
+      font-weight: 600;
+    }
+  }
+}
diff --git a/themes/clean-hugo/assets/css/_learn-more.scss b/themes/clean-hugo/assets/css/_learn-more.scss
new file mode 100644
index 00000000..5b3f1aa8
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_learn-more.scss
@@ -0,0 +1,60 @@
+  .learn-more {
+    margin: 3rem 0;
+    border-radius: $radius-xl;
+    padding: 2rem;
+    box-shadow: $shadow-lg;
+    background-color: var(--color-gray-50);
+  }
+
+  .learn-more__header {
+    @include flex-center;
+    gap: 0.75rem;
+    margin-bottom: 1.5rem;
+    justify-content: flex-start;
+  }
+
+  .learn-more__title {
+    font-size: 1.5rem;
+    font-weight: 700;
+    margin: 0;
+    color: var(--color-gray-900);
+
+    i {
+      color: var(--color-gray-900);
+    }
+  }
+
+  .learn-more__list {
+    list-style: none;
+    padding: 0;
+    margin: 0;
+
+    > li + li {
+      margin-top: 1rem;
+    }
+  }
+
+  .learn-more__item {
+    a {
+      @include flex-center;
+      gap: 1rem;
+      text-decoration: none;
+      transition: color $transition-base;
+      color: var(--color-gray-900);
+      justify-content: flex-start;
+
+      &:hover,
+      &:focus {
+        color: var(--color-link);
+      }
+    }
+  }
+
+  .learn-more__item-text {
+    font-size: 1.125rem;
+    font-weight: 600;
+
+    i {
+      margin-right: 0.5rem;
+    }
+  }
diff --git a/themes/clean-hugo/assets/css/_mixins.scss b/themes/clean-hugo/assets/css/_mixins.scss
new file mode 100644
index 00000000..cbebf82c
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_mixins.scss
@@ -0,0 +1,231 @@
+/* Card shell — border, radius, shadow, background (no motion) */
+@mixin card-surface(
+  $radius: $radius-lg,
+  $border: 1px solid var(--color-gray-200),
+  $shadow: $shadow-sm,
+  $bg: var(--color-white)
+) {
+  border-radius: $radius;
+  border: $border;
+  box-shadow: $shadow;
+  background-color: $bg;
+}
+
+/* Card base — surface + lift/shadow on hover */
+@mixin card-base(
+  $radius: $radius-lg,
+  $border: 1px solid var(--color-gray-200),
+  $shadow: $shadow-sm,
+  $bg: var(--color-white),
+  $hover-lift: -4px,
+  $hover-shadow: $shadow-xl
+) {
+  @include card-surface($radius, $border, $shadow, $bg);
+  transition: transform $transition-base ease-in-out, box-shadow $transition-base ease-in-out;
+
+  &:hover {
+    transform: translateY($hover-lift);
+    box-shadow: $hover-shadow;
+  }
+}
+
+/* Base heading / prose steps (mobile → md → lg) */
+@mixin type-scale-3($mobile, $tablet, $desktop) {
+  font-size: $mobile;
+
+  @media (min-width: $breakpoint-md) {
+    font-size: $tablet;
+  }
+
+  @media (min-width: $breakpoint-lg) {
+    font-size: $desktop;
+  }
+}
+
+/* Body text: mobile + md only */
+@mixin type-scale-md($mobile, $tablet) {
+  font-size: $mobile;
+
+  @media (min-width: $breakpoint-md) {
+    font-size: $tablet;
+  }
+}
+/**
+ * Reusable SCSS Mixins - Mobile First
+ * Base styles target mobile (320px+), breakpoints enhance for larger screens
+ */
+
+/* Container mixin - centered with max-width and responsive padding */
+@mixin container($max-width: $container-max-width, $padding-mobile: 0.75rem, $padding-tablet: 1.5rem) {
+  max-width: $max-width;
+  margin: 0 auto;
+  padding: 0 $padding-mobile;
+
+  @media (min-width: $breakpoint-md) {
+    padding: 0 $padding-tablet;
+  }
+}
+
+/* Focus ring mixin - consistent focus states */
+@mixin focus-ring($color: var(--color-primary)) {
+  outline: none;
+  box-shadow: 0 0 0 2px var(--color-white), 0 0 0 4px $color;
+}
+
+/* Card hover effect - lift and shadow on hover */
+@mixin card-hover($lift: -2px, $shadow: $shadow-xl) {
+  transition: box-shadow $transition-base ease-in-out, transform $transition-base ease-in-out;
+
+  &:hover {
+    transform: translateY($lift);
+    box-shadow: $shadow;
+  }
+}
+
+/* Responsive property - mobile, tablet, desktop values */
+@mixin responsive($property, $mobile, $tablet: null, $desktop: null) {
+  #{$property}: $mobile;
+
+  @if $tablet {
+    @media (min-width: $breakpoint-md) {
+      #{$property}: $tablet;
+    }
+  }
+
+  @if $desktop {
+    @media (min-width: $breakpoint-lg) {
+      #{$property}: $desktop;
+    }
+  }
+}
+
+/* Responsive padding - mobile base with optional tablet/desktop values */
+@mixin responsive-padding($mobile-y: 1.5rem, $mobile-x: 0.75rem, $tablet-y: null, $tablet-x: 1.5rem) {
+  padding: $mobile-y $mobile-x;
+
+  @if $tablet-y and $tablet-x {
+    @media (min-width: $breakpoint-md) {
+      padding: $tablet-y $tablet-x;
+    }
+  } @else if $tablet-x {
+    @media (min-width: $breakpoint-md) {
+      padding-left: $tablet-x;
+      padding-right: $tablet-x;
+    }
+  }
+}
+
+/* Image hover zoom effect */
+@mixin image-zoom($scale: 1.1, $duration: $transition-slow) {
+  overflow: hidden;
+
+  img {
+    transition: transform $duration ease-out;
+  }
+
+  &:hover img {
+    transform: scale($scale);
+  }
+}
+
+/* Truncate text with ellipsis */
+@mixin truncate {
+  overflow: hidden;
+  text-overflow: ellipsis;
+  white-space: nowrap;
+}
+
+/* Line clamp - limit text to N lines */
+@mixin line-clamp($lines: 3) {
+  display: -webkit-box;
+  -webkit-line-clamp: $lines;
+  -webkit-box-orient: vertical;
+  overflow: hidden;
+}
+
+/* Stretched link - make entire card clickable */
+@mixin stretched-link {
+  &::after {
+    content: "";
+    position: absolute;
+    inset: 0;
+    z-index: 10;
+  }
+}
+
+/* Flexbox centering */
+@mixin flex-center {
+  display: flex;
+  align-items: center;
+  justify-content: center;
+}
+
+/* Grid auto-fit columns */
+@mixin grid-auto-fit($min-width: 250px, $gap: 1.5rem) {
+  display: grid;
+  gap: $gap;
+  grid-template-columns: repeat(auto-fill, minmax($min-width, 1fr));
+}
+
+/* Responsive grid columns */
+@mixin responsive-grid($mobile: 1, $tablet: 2, $desktop: 3, $gap: 2rem) {
+  display: grid;
+  gap: $gap;
+  grid-template-columns: repeat($mobile, 1fr);
+
+  @media (min-width: $breakpoint-md) {
+    grid-template-columns: repeat($tablet, 1fr);
+  }
+
+  @media (min-width: $breakpoint-lg) {
+    grid-template-columns: repeat($desktop, 1fr);
+  }
+}
+
+/* Custom scrollbar styling */
+@mixin custom-scrollbar($width: 0.375rem, $track-color: var(--color-gray-200), $thumb-color: var(--color-gray-600)) {
+  &::-webkit-scrollbar {
+    width: $width;
+  }
+
+  &::-webkit-scrollbar-track {
+    background-color: $track-color;
+    border-radius: $radius-sm;
+  }
+
+  &::-webkit-scrollbar-thumb {
+    background-color: $thumb-color;
+    border-radius: $radius-sm;
+
+    &:hover {
+      background-color: var(--color-gray-700);
+    }
+  }
+}
+
+/* Mobile-first font sizing - base size with optional scaling */
+@mixin fluid-font($mobile-size, $desktop-size: null) {
+  font-size: $mobile-size;
+
+  @if $desktop-size {
+    @media (min-width: $breakpoint-lg) {
+      font-size: $desktop-size;
+    }
+  }
+}
+
+/* Stack to row - mobile stacks, desktop horizontal */
+@mixin stack-to-row($gap: 1rem, $breakpoint: $breakpoint-md) {
+  display: flex;
+  flex-direction: column;
+  gap: $gap;
+
+  @media (min-width: $breakpoint) {
+    flex-direction: row;
+  }
+}
+
+/* Mobile safe area - accounts for notches/home indicators */
+@mixin mobile-safe-padding($padding: 1rem) {
+  padding: max($padding, env(safe-area-inset-top)) max($padding, env(safe-area-inset-right)) max($padding, env(safe-area-inset-bottom)) max($padding, env(safe-area-inset-left));
+}
diff --git a/themes/clean-hugo/assets/css/_navigation.scss b/themes/clean-hugo/assets/css/_navigation.scss
new file mode 100644
index 00000000..4d5bcb35
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_navigation.scss
@@ -0,0 +1,301 @@
+/* Site navigation */
+.site-nav {
+  border-bottom: 1px solid var(--color-gray-200);
+  position: relative;
+  background-color: var(--color-white);
+  z-index: 1000;
+}
+
+.site-nav__container {
+  max-width: $container-max-width;
+  margin: 0 auto;
+  padding: 0.75rem;
+  display: flex;
+  justify-content: space-between;
+  align-items: center;
+
+  @media (min-width: $breakpoint-md) {
+    padding: 1rem;
+  }
+}
+
+.site-nav__brand {
+  font-size: 1.5rem;
+  font-weight: 700;
+  color: var(--color-gray-900);
+  text-decoration: none;
+
+  &:hover {
+    color: var(--color-link);
+  }
+
+  &:focus {
+    color: var(--color-link);
+    outline: 2px solid var(--color-link);
+    outline-offset: 2px;
+  }
+
+  &--logo {
+    display: inline-flex;
+    align-items: center;
+    gap: 0.5rem;
+    font-size: 1rem;
+    font-weight: 600;
+  }
+}
+
+.site-nav__logo {
+  display: block;
+  width: auto;
+  height: clamp(2.75rem, 5vw, 3.25rem);
+  object-fit: contain;
+
+  @media (min-width: $breakpoint-md) {
+    height: clamp(3rem, 4.5vw, 3.75rem);
+  }
+}
+
+/* Hamburger menu toggle button */
+.site-nav__toggle {
+  display: flex;
+  flex-direction: column;
+  justify-content: center;
+  align-items: center;
+  width: 2.5rem;
+  height: 2.5rem;
+  padding: 0.5rem;
+  border: 1px solid var(--color-gray-200);
+  border-radius: 0.25rem;
+  background-color: transparent;
+  cursor: pointer;
+  transition: background-color 0.2s;
+  flex-shrink: 0;
+
+  &:hover {
+    background-color: var(--color-gray-50);
+  }
+
+  &:focus {
+    outline: none;
+    box-shadow: 0 0 0 2px var(--color-link), 0 0 0 4px var(--color-white);
+  }
+
+  &[aria-expanded="true"] {
+    .site-nav__toggle-icon {
+      &:nth-child(1) {
+        transform: rotate(45deg) translate(0.25rem, 0.25rem);
+      }
+
+      &:nth-child(2) {
+        opacity: 0;
+      }
+
+      &:nth-child(3) {
+        transform: rotate(-45deg) translate(0.25rem, -0.25rem);
+      }
+    }
+  }
+}
+
+@media (min-width: $breakpoint-md) {
+  .site-nav__toggle {
+    display: none;
+  }
+}
+
+.site-nav__toggle-icon {
+  display: block;
+  width: 1.25rem;
+  height: 0.125rem;
+  margin-bottom: 0.25rem;
+  background-color: var(--color-gray-900);
+  transition: all 0.2s;
+
+  &:last-child {
+    margin-bottom: 0;
+  }
+}
+
+/* Navigation menu */
+.site-nav__menu {
+  display: none;
+  position: absolute;
+  top: 100%;
+  left: 0;
+  right: 0;
+  flex-direction: column;
+  background-color: white;
+  border-top: 1px solid var(--color-gray-200);
+  box-shadow: 0 10px 15px -3px rgba(0, 0, 0, 0.1);
+  padding-block: 1rem;
+
+  &[aria-expanded="true"],
+  &.site-nav__menu--open {
+    display: flex;
+  }
+}
+
+@media (min-width: $breakpoint-md) {
+  .site-nav__menu {
+    display: flex;
+    position: relative;
+    top: auto;
+    flex-direction: row;
+    align-items: center;
+    gap: 1.5rem;
+    background-color: transparent;
+    border-top: 0;
+    box-shadow: none;
+    padding: 0;
+  }
+}
+
+.site-nav__link {
+  padding: 0.5rem 1rem;
+  font-size: 1.125rem;
+  font-weight: 500;
+  transition: color 0.2s;
+  display: block;
+  color: var(--color-gray-900);
+  text-decoration: none;
+
+  &:hover {
+    color: var(--color-link);
+  }
+
+  &:focus {
+    color: var(--color-link);
+    outline: none;
+    box-shadow: 0 0 0 2px var(--color-link), 0 0 0 4px var(--color-white);
+  }
+}
+
+@media (min-width: $breakpoint-md) {
+  .site-nav__link {
+    display: inline-block;
+  }
+}
+
+/* Dropdown menu */
+.site-nav__dropdown {
+  position: relative;
+}
+
+.site-nav__link--dropdown {
+  display: flex;
+  align-items: center;
+  gap: 0.5rem;
+  background: none;
+  border: none;
+  cursor: pointer;
+  font-family: inherit;
+
+  i {
+    font-size: 0.75rem;
+    transition: transform 0.2s;
+  }
+
+  /* Icon rotation when dropdown is open (mobile) */
+  &[aria-expanded="true"] i {
+    transform: rotate(180deg);
+  }
+}
+
+/* Desktop hover behavior */
+@media (min-width: $breakpoint-md) {
+  .site-nav__dropdown:hover,
+  .site-nav__dropdown:focus-within {
+    .site-nav__link--dropdown i {
+      transform: rotate(180deg);
+    }
+
+    .site-nav__dropdown-menu {
+      display: block;
+    }
+  }
+}
+
+.site-nav__dropdown-menu {
+  display: none;
+  padding-left: 0;
+  padding-top: 0.5rem;
+  list-style: none;
+  padding-right: 0;
+  margin: 0;
+
+  &.site-nav__dropdown-menu--open {
+    display: block;
+  }
+
+  li {
+    width: 100%;
+  }
+}
+
+@media (min-width: $breakpoint-md) {
+  .site-nav__dropdown-menu {
+    position: absolute;
+    top: calc(100% + 0.5rem);
+    left: 0;
+    background-color: white;
+    border: 1px solid var(--color-gray-200);
+    border-radius: 0.5rem;
+    box-shadow: 0 10px 15px -3px rgba(0, 0, 0, 0.1);
+    padding: 0.5rem 0;
+    z-index: 50;
+    min-width: 200px;
+  }
+
+  /* Create an invisible bridge to prevent hover state loss */
+  .site-nav__dropdown-menu::before {
+    content: '';
+    position: absolute;
+    top: -0.5rem;
+    left: 0;
+    right: 0;
+    height: 0.5rem;
+  }
+}
+
+.site-nav__dropdown-link {
+  padding: 0.75rem 1rem;
+  font-size: 1rem;
+  font-weight: 500;
+  transition: background-color 0.3s ease, color 0.3s ease;
+  display: block;
+  width: 100%;
+  color: var(--color-gray-900);
+  text-decoration: none;
+  border-radius: 0.25rem;
+  background-color: transparent;
+
+  i {
+    margin-left: 0.375rem;
+    font-size: 0.75rem;
+  }
+
+  &:hover,
+  &:focus {
+    color: var(--color-gray-900);
+    background-color: var(--color-gray-200);
+    outline: none;
+  }
+}
+
+/* On mobile, make dropdown links indent slightly for hierarchy */
+@media (max-width: 767px) {
+  .site-nav__dropdown-link {
+    padding-left: 2rem;
+  }
+}
+
+/* Navigation CTA Button - uses base button system */
+.site-nav__button {
+  /* Navigation-specific positioning */
+  margin-top: 1rem;
+
+  @media (min-width: $breakpoint-md) {
+    margin-top: 0;
+    margin-left: 1rem;
+  }
+}
diff --git a/themes/clean-hugo/assets/css/_packages.scss b/themes/clean-hugo/assets/css/_packages.scss
new file mode 100644
index 00000000..10c572c2
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_packages.scss
@@ -0,0 +1,233 @@
+  /* Packages Page Layout */
+
+  .packages-page__content {
+    width: 100%;
+    /* Child elements use .container utility class */
+  }
+
+  .packages-page__partner-nav {
+    width: 100%;
+    padding: 1.5rem 0;
+    background-color: var(--color-primary-light);
+    /* Child div uses .container utility class */
+  }
+
+  .packages-page__controls {
+    width: 100%;
+    padding: 2rem 0;
+    margin-bottom: 2rem;
+    background-color: var(--color-gray-50);
+    /* Child div uses .container utility class */
+  }
+
+  .packages-page__section {
+    margin-bottom: 4rem;
+    /* Child div uses .container utility class */
+  }
+
+  /* Archived packages — reuses .blog-archives full-bleed band from _blog.scss */
+  .packages-page__archives {
+    margin-bottom: 4rem;
+
+    .intro p {
+      margin: 0.75rem 0 0;
+      max-width: 42rem;
+      color: var(--color-gray-700);
+      line-height: 1.6;
+    }
+
+    .packages-grid {
+      margin-top: 0;
+    }
+  }
+
+  .packages-page__empty {
+    padding: 3rem 0;
+    text-align: center;
+    /* Uses .container utility class in template */
+  }
+
+  /* Package Filters */
+  .packages-filters {
+    margin-bottom: 2rem;
+
+    input {
+      width: 100%;
+      max-width: 28rem;
+      padding: 0.5rem 1rem;
+      font-size: 1.125rem;
+      border: 1px solid var(--color-gray-200);
+      border-radius: $radius-md;
+      margin-bottom: 1rem;
+
+      &:focus {
+        outline: none;
+        box-shadow: 0 0 0 2px var(--color-primary);
+        border-color: var(--color-primary);
+      }
+    }
+
+    > div {
+      display: flex;
+      flex-wrap: wrap;
+      gap: 0.5rem;
+
+      button {
+        padding: 0.5rem 1rem;
+        border-radius: $radius-md;
+        border: 1px solid var(--color-gray-200);
+        font-weight: 500;
+        transition: all $transition-base;
+        background-color: var(--color-gray-200);
+        color: var(--color-gray-700);
+
+        &:hover {
+          background-color: var(--color-gray-200);
+          transform: translateY(-1px);
+        }
+
+        &.is-checked {
+          background-color: var(--color-primary);
+          border-color: var(--color-primary-dark);
+          color: white;
+        }
+      }
+    }
+  }
+
+  /* Package Grid */
+  .packages-grid {
+    @include responsive-grid($mobile: 1, $tablet: 2, $desktop: 3, $gap: 1.5rem);
+    margin-top: 3rem;
+  }
+
+  /* Package Card */
+  .package_card {
+    display: flex;
+    flex-direction: column;
+
+    > div {
+      border-radius: $radius-md;
+      border: 1px solid var(--color-gray-200);
+      border-top: 4px solid var(--color-primary-dark);
+      box-shadow: $shadow-sm;
+      padding: 1.5rem;
+      display: flex;
+      flex-direction: column;
+      flex: 1;
+      transition: all $transition-base;
+      background-color: var(--color-white);
+
+      &:hover {
+        transform: $card-hover-transform;
+        box-shadow: $shadow-xl;
+      }
+
+      /* Title - Card-specific: smaller than base h3 for card layout */
+      > h3 {
+        font-size: 1.25rem;
+        font-weight: 600;
+        margin-bottom: 0.75rem;
+        color: var(--color-gray-900);
+      }
+
+      /* Meta section (stars, etc) */
+      > .package_card__meta {
+        display: flex;
+        align-items: center;
+        gap: 0.5rem;
+        margin-bottom: 1rem;
+        font-size: 0.875rem;
+        color: var(--color-gray-600);
+        i { color: var(--color-gray-600); }
+      }
+
+      /* Description */
+      > p {
+        flex-grow: 1;
+        margin-bottom: 1rem;
+        color: var(--color-gray-700);
+        line-height: 1.6;
+      }
+
+      /* Links */
+      > ul {
+        list-style: none;
+        margin: 0;
+        padding: 0;
+        padding-top: 1rem;
+        margin-top: auto;
+        border-top: 1px solid var(--color-gray-200);
+
+        li {
+          margin-bottom: 0.5rem;
+
+          a {
+            display: inline-flex;
+            align-items: center;
+            gap: 0.5rem;
+            text-decoration: none;
+            color: var(--color-primary-dark);
+            transition: color $transition-base ease;
+
+            &:hover { color: var(--color-link-hover); }
+            i { font-size: 0.875rem; }
+
+            /* Partner badge styling */
+            img.partner-badge {
+              height: 1.25rem;
+              vertical-align: middle;
+              margin-left: 0.25rem;
+            }
+          }
+        }
+      }
+
+      /* Archived badge */
+      .package_card__archived {
+        display: inline-flex;
+        align-items: center;
+        gap: 0.5rem;
+        color: var(--color-gray-700);
+        font-style: italic;
+      }
+    }
+  }
+
+  /* Partner Navigation Button */
+  .partner-button {
+    display: inline-flex;
+    align-items: center;
+    gap: 0.75rem;
+    padding: 0.75rem 1.5rem;
+    border-radius: $radius-md;
+    font-weight: 600;
+    transition: all $transition-base;
+    text-decoration: none;
+    background-color: white;
+    border: 2px solid var(--color-gray-200);
+    color: var(--color-gray-900);
+
+    &:hover {
+      box-shadow: $shadow-lg;
+      transform: translateY(-2px);
+      border-color: var(--color-primary);
+    }
+
+    img {
+      height: 1.25rem;
+    }
+
+    span {
+      font-size: 1rem;
+    }
+
+    &--astropy {
+      border-color: #FF8C00;
+
+      &:hover {
+        background-color: #FFF5E6;
+        border-color: #FF8C00;
+      }
+    }
+  }
diff --git a/themes/clean-hugo/assets/css/_people.scss b/themes/clean-hugo/assets/css/_people.scss
new file mode 100644
index 00000000..513eadf4
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_people.scss
@@ -0,0 +1,208 @@
+  .people-page__content {
+    width: 100%;
+  }
+
+  .people-page__controls {
+    width: 100%;
+    padding: 2rem 0;
+    margin-bottom: 2rem;
+    background-color: var(--color-gray-50);
+  }
+
+  .people-page__section {
+    margin-bottom: 4rem;
+  }
+
+  .people-page__empty {
+    padding: 3rem 0;
+    text-align: center;
+  }
+
+  .people-filters {
+    margin-bottom: 2rem;
+
+    input {
+      width: 100%;
+      max-width: 28rem;
+      padding: 0.5rem 1rem;
+      font-size: 1.125rem;
+      border: 1px solid var(--color-gray-200);
+      border-radius: $radius-md;
+      margin-bottom: 1rem;
+
+      &:focus {
+        outline: none;
+        box-shadow: 0 0 0 2px var(--color-primary);
+        border-color: var(--color-primary);
+      }
+    }
+
+    > div {
+      display: flex;
+      flex-wrap: wrap;
+      gap: 0.5rem;
+
+      button {
+        padding: 0.5rem 1rem;
+        border-radius: $radius-md;
+        border: 1px solid var(--color-gray-200);
+        font-weight: 500;
+        transition: all $transition-base;
+        background-color: var(--color-gray-200);
+        color: var(--color-gray-700);
+
+        &:hover {
+          background-color: var(--color-gray-200);
+          transform: translateY(-1px);
+        }
+
+        &.is-checked {
+          background-color: var(--color-primary);
+          border-color: var(--color-primary-dark);
+          color: white;
+        }
+      }
+    }
+  }
+
+  .people-grid {
+    display: grid;
+    gap: 1rem;
+    margin-top: 3rem;
+    grid-template-columns: 1fr;
+
+    @media (min-width: $breakpoint-sm) {
+      grid-template-columns: repeat(2, 1fr);
+    }
+
+    @media (min-width: 1000px) {
+      grid-template-columns: repeat(3, 1fr);
+    }
+
+    @media (min-width: 1246px) {
+      grid-template-columns: repeat(4, 1fr);
+    }
+
+    @media (min-width: $breakpoint-2xl) {
+      grid-template-columns: repeat(6, 1fr);
+    }
+  }
+
+  .people_card {
+    display: flex;
+    flex-direction: column;
+
+    > div {
+      border-radius: $radius-md;
+      border: 1px solid var(--color-gray-200);
+      box-shadow: $shadow-sm;
+      display: flex;
+      flex-direction: column;
+      flex: 1;
+      transition: all $transition-base;
+      background-color: var(--color-white);
+      overflow: hidden;
+
+      &:hover {
+        transform: $card-hover-transform;
+        box-shadow: $shadow-xl;
+      }
+    }
+  }
+
+  .people_card__image {
+    width: 100%;
+    overflow: hidden;
+    aspect-ratio: 1;
+    background-color: var(--color-gray-200);
+
+    img {
+      width: 100%;
+      height: 100%;
+      object-fit: cover;
+    }
+  }
+
+  .people_card__content {
+    padding: 1rem;
+    display: flex;
+    flex-direction: column;
+    flex-grow: 1;
+
+    h3 {
+      font-size: 1.125rem;
+      font-weight: 600;
+      margin-bottom: 0.375rem;
+      color: var(--color-gray-900);
+
+      a {
+        text-decoration: none;
+        color: inherit;
+
+        &:hover {
+          color: var(--color-link);
+        }
+      }
+    }
+  }
+
+  .people_card__title {
+    font-size: 0.75rem;
+    margin-bottom: 0.375rem;
+    color: var(--color-gray-600);
+    line-height: 1.4;
+  }
+
+  .people_card__org {
+    font-size: 0.75rem;
+    margin-bottom: 0.75rem;
+    color: var(--color-gray-600);
+    font-style: italic;
+  }
+
+  .people_card__social {
+    display: flex;
+    flex-wrap: wrap;
+    gap: 0.5rem;
+    margin-top: auto;
+    font-size: 0.75rem;
+
+    a {
+      display: inline-flex;
+      align-items: center;
+      gap: 0.25rem;
+      text-decoration: none;
+      color: var(--color-gray-600);
+      transition: color $transition-base ease;
+
+      &:hover {
+        color: var(--color-link);
+      }
+
+      i {
+        font-size: 0.875rem;
+      }
+    }
+  }
+
+  .people-grid-static {
+    display: grid;
+    gap: 1rem;
+    grid-template-columns: 1fr;
+
+    @media (min-width: $breakpoint-sm) {
+      grid-template-columns: repeat(2, 1fr);
+    }
+
+    @media (min-width: 1000px) {
+      grid-template-columns: repeat(3, 1fr);
+    }
+
+    @media (min-width: 1246px) {
+      grid-template-columns: repeat(4, 1fr);
+    }
+
+    @media (min-width: $breakpoint-2xl) {
+      grid-template-columns: repeat(5, 1fr);
+    }
+  }
diff --git a/themes/clean-hugo/assets/css/_quotes.scss b/themes/clean-hugo/assets/css/_quotes.scss
new file mode 100644
index 00000000..53786ff0
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_quotes.scss
@@ -0,0 +1,155 @@
+/*
+  Quotes — change text size here. All quote types use the same size.
+*/
+$quote-font-size: 2rem;
+
+/* Quote text */
+.content-main blockquote:not(.twitter-tweet) p,
+.splash-page__content blockquote:not(.twitter-tweet) p,
+.docs-content blockquote p,
+.pullquote__text,
+.admonition-quote__body,
+.admonition-quote__body p {
+  font-family: $font-family-quote;
+  font-style: italic;
+  font-size: $quote-font-size;
+  line-height: 1.65;
+  color: var(--color-gray-600);
+}
+
+/* Blockquote — left bar + background */
+.content-main blockquote:not(.twitter-tweet),
+.splash-page__content blockquote:not(.twitter-tweet),
+.docs-content blockquote {
+  border-left: 4px solid var(--color-primary);
+  padding: 0.5rem 0 0.5rem 1rem;
+  margin: 1rem 0;
+  background-color: var(--color-gray-50);
+
+  p {
+    margin-bottom: 0;
+  }
+}
+
+/* Pull quote — decorative mark, no sidebar */
+.pullquote {
+  --pullquote-accent: var(--color-primary);
+
+  margin: 4.5rem 0;
+  padding: 0;
+  border: none;
+  background: none;
+
+  &--magenta { --pullquote-accent: var(--color-accent-light); }
+  &--purple  { --pullquote-accent: var(--color-accent); }
+
+  &::before {
+    content: '\201C';
+    display: block;
+    font-size: 4rem;
+    font-weight: 700;
+    color: var(--pullquote-accent);
+    line-height: 0;
+    margin-bottom: 0.15rem;
+    opacity: 0.85;
+  }
+
+  &__text {
+    margin: 0;
+  }
+
+  &__footer {
+    font-family: $font-family-body;
+    font-size: 1rem;
+    text-align: right;
+    font-style: italic;
+    margin: 1rem 0 0;
+    color: var(--color-gray-600);
+  }
+}
+
+/* Admonition quote — colored callout box */
+.admonition-quote {
+  border-left-width: 4px;
+  border-radius: 0 1rem 1rem 0;
+  padding: 2rem;
+  box-shadow: $shadow-md;
+  border: 1px solid;
+  border-left-width: 4px;
+  margin: 3rem 0;
+  display: flex;
+  flex-direction: column;
+  gap: 0.5rem;
+
+  @media (max-width: 640px) {
+    padding: 0.875rem;
+    gap: 0.375rem;
+  }
+
+  &__mark::before {
+    content: '\201C';
+    display: block;
+    font-size: 2.1rem;
+    font-weight: 700;
+    color: var(--base-color, var(--color-primary));
+    line-height: 1;
+    opacity: 0.85;
+  }
+
+  &__title {
+    font-weight: 600;
+    margin-bottom: 0.25rem;
+    font-size: clamp(1.3rem, 2vw, 1.4rem);
+  }
+
+  &__body p:last-child {
+    margin-bottom: 0;
+  }
+
+  &__footer {
+    font-family: $font-family-body;
+    margin: 0.75rem 0 0;
+    font-size: 0.95rem;
+    color: color-mix(in srgb, var(--base-color) 35%, black);
+  }
+
+  &--info,
+  &--success,
+  &--warning,
+  &--danger,
+  &--note {
+    background-color: color-mix(in srgb, var(--base-color) 8%, white);
+    border-color: color-mix(in srgb, var(--base-color) 95%, black);
+
+    .admonition-quote__title,
+    .admonition-quote__body {
+      color: color-mix(in srgb, var(--base-color) 25%, black);
+    }
+
+    .admonition-quote__mark::before {
+      color: color-mix(in srgb, var(--base-color) 90%, black);
+    }
+  }
+
+  &--info    { --base-color: var(--color-admonition-info, #3B82F6); }
+  &--success { --base-color: var(--color-admonition-success, #22C55E); }
+  &--warning { --base-color: var(--color-admonition-warning, #EAB308); }
+  &--danger  { --base-color: var(--color-admonition-danger, #EF4444); }
+  &--note    { --base-color: var(--color-admonition-note, #6B7280); }
+}
+
+/* Training testimonial cards */
+.testimonial-showcase__blockquote {
+  margin: 0;
+  padding: 0;
+  border: 0;
+
+  p {
+    font-family: $font-family-quote;
+    font-style: italic;
+    font-size: $quote-font-size;
+    line-height: 1.55;
+    margin: 0 0 0.75rem;
+    color: var(--color-gray-700);
+  }
+}
diff --git a/themes/clean-hugo/assets/css/_shortcodes.scss b/themes/clean-hugo/assets/css/_shortcodes.scss
new file mode 100644
index 00000000..b8815cbd
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_shortcodes.scss
@@ -0,0 +1,318 @@
+  /* Metrics Bar */
+  .metrics-bar {
+    width: 100%;
+    padding: 6rem 0;
+    margin: 3rem 0 5rem;
+    background-color: color-mix(in srgb, var(--color-primary) 8%, var(--color-gray-50));
+
+    /* Grid container */
+    > div {
+      width: 100%;
+      padding: 0 1.5rem;
+      display: grid;
+      gap: 2rem;
+      grid-template-columns: repeat(2, 1fr);
+      max-width: $container-max-width;
+      margin: 0 auto;
+
+      @media (min-width: $breakpoint-lg) {
+        grid-template-columns: repeat(4, 1fr);
+      }
+
+      /* Items */
+      > div {
+        text-align: center;
+        @include responsive(font-size, 1rem, 1.125rem);
+        line-height: 1.625;
+        color: var(--color-gray-700);
+
+        /* Numbers */
+        strong {
+          display: block;
+          @include responsive(font-size, 2.25rem, 3rem, 3.75rem);
+          @include responsive(margin-bottom, 0.5rem, 0.75rem);
+          font-weight: 900;
+          line-height: 1.25;
+          color: var(--color-gray-900);
+          letter-spacing: -0.02em;
+        }
+      }
+    }
+  }
+
+  /* Two Card Row */
+  .two-card-row {
+    padding: 1.5rem 0;
+    background-color: var(--color-gray-50);
+  }
+
+  .two-card-row__container {
+    @include responsive-grid($mobile: 1, $tablet: 2, $desktop: 2, $gap: 1.5rem);
+    align-items: start;
+    max-width: $container-max-width;
+    margin: 0 auto;
+    padding: 0 $fluid-container-padding;
+  }
+
+  /* Card Shortcode (used in two-card-row) - can use bg-card, bg-primary, or bg-secondary utilities */
+  .card-shortcode {
+    width: 100%;
+    border-radius: $card-border-radius;
+    border: $card-border;
+    box-shadow: $card-shadow;
+    @include responsive-padding(1.5rem, 1.5rem, 2.5rem, 2.5rem);
+    height: 100%;
+    background-color: var(--color-white);
+    @include card-hover($lift: -4px, $shadow: $card-shadow-hover);
+
+    @media (min-width: $breakpoint-md) {
+      width: auto;
+    }
+
+    div {
+      display: flex;
+      flex-direction: column;
+    }
+
+    .card-shortcode__icon {
+      font-size: $card-icon-size;
+      margin-bottom: 1rem;
+
+      i {
+        color: inherit;
+      }
+    }
+
+    h3 {
+      font-size: $card-heading-size;
+      font-weight: 800;
+      line-height: 1.3;
+      margin-bottom: 1.5rem;
+      color: var(--color-gray-900);
+    }
+
+    div div:last-child {
+      font-size: $card-text-size;
+      line-height: $card-line-height;
+      color: $card-text-color;
+
+      ul, ol {
+        padding-left: $card-list-padding;
+
+        li {
+          font-size: $card-text-size;
+          line-height: $card-line-height;
+          margin-bottom: 0.5rem;
+        }
+      }
+
+      a {
+        color: var(--color-link);
+        text-decoration: underline;
+        transition: color .2s ease;
+
+        &:hover,
+        &:focus {
+          color: var(--color-link-hover);
+        }
+      }
+
+      strong {
+        color: var(--color-gray-900);
+        font-weight: 600;
+      }
+    }
+  }
+
+  /* Single Card Wide */
+  .single-card-wide {
+    padding: 2rem 0 4rem;
+    margin: 2.5rem 0 4rem;
+    background-color: var(--color-gray-50);
+
+    .container > div {
+      border-radius: $card-border-radius;
+      border: $card-border;
+      box-shadow: $card-shadow;
+      @include responsive-padding(1.5rem, 1.5rem, 2.5rem, 2.5rem);
+      background-color: color-mix(in srgb, var(--color-primary-dark) 12%, var(--color-primary-light));
+      @include card-hover($lift: -4px, $shadow: $card-shadow-hover);
+    }
+
+    .single-card-wide__icon {
+      font-size: $card-icon-size;
+      margin-bottom: 1rem;
+
+      i {
+        color: inherit;
+      }
+    }
+
+    h3 {
+      font-size: $card-heading-size;
+      font-weight: 800;
+      margin-bottom: 1.5rem;
+      color: var(--color-gray-900);
+    }
+
+    .single-card-wide__body,
+    .container > div > div:last-child {
+      font-size: $card-text-size;
+      line-height: $card-line-height;
+      color: $card-text-color;
+
+      ul {
+        padding-left: $card-list-padding;
+
+        > li + li {
+          margin-top: 0.5rem;
+        }
+      }
+
+      li {
+        font-size: $card-text-size;
+        line-height: $card-line-height;
+      }
+
+      a:not(.btn) {
+        color: var(--color-link);
+        text-decoration: underline;
+        font-weight: 500;
+        transition: color .2s ease;
+
+        &:hover,
+        &:focus {
+          color: var(--color-link-hover);
+        }
+      }
+
+      .btn {
+        margin-top: 1.25rem;
+      }
+
+      strong {
+        color: var(--color-gray-900);
+        font-weight: 600;
+      }
+    }
+  }
+
+  /* YouTube Video Embed */
+  .youtube-container {
+    margin: 2rem 0;
+    /* Automatically breaks out to full-width in blog posts via auto-detection */
+  }
+
+  /* Constrained width variant - stays within content width */
+  .youtube-container--constrained {
+    width: auto !important;
+    position: static !important;
+    inset-inline: auto !important;
+    margin-inline: 0 !important;
+  }
+
+  .youtube-wrapper {
+    position: relative;
+    padding-bottom: 56.25%; /* 16:9 aspect ratio */
+    height: 0;
+    overflow: hidden;
+  }
+
+  .youtube-iframe {
+    position: absolute;
+    top: 0;
+    left: 0;
+    width: 100%;
+    height: 100%;
+    border: 0;
+  }
+
+  /* Section Heading Shortcode */
+  .section-heading {
+    text-align: center;
+    padding: $fluid-space-lg 0 2rem;
+    margin-bottom: 2rem;
+  }
+
+  .section-heading__title {
+    @include responsive(font-size, 2.25rem, 3rem, 3.75rem);
+    font-weight: 700;
+    margin-bottom: 1rem;
+    color: var(--color-gray-900);
+
+    @media (min-width: $breakpoint-xl) {
+      font-size: 4.5rem;
+    }
+  }
+
+  .section-heading__subtitle {
+    text-align: center;
+    @include responsive(font-size, 1.125rem, 1.25rem);
+    opacity: 0.8;
+    color: var(--color-gray-600);
+  }
+
+  /* Theme Colors Shortcode Styling */
+  .theme-colors {
+    @include grid-auto-fit($min-width: 280px, $gap: 1.5rem);
+    margin: 2rem 0;
+
+    > div {
+      display: flex;
+      align-items: center;
+      gap: 1rem;
+      padding: 1rem;
+      border: 1px solid var(--color-gray-200);
+      border-radius: $radius-md;
+      background: var(--color-white);
+      box-shadow: 0 1px 3px rgba(0, 0, 0, 0.1);
+
+      /* Color swatch */
+      > div:first-child {
+        width: 80px;
+        height: 80px;
+        border-radius: $radius-md;
+        border: 2px solid rgba(0, 0, 0, 0.1);
+        flex-shrink: 0;
+      }
+
+      /* Info container */
+      > div:last-child {
+        display: flex;
+        flex-direction: column;
+        gap: 0.25rem;
+        min-width: 0;
+
+        strong {
+          font-size: 1rem;
+          color: var(--color-gray-900);
+          word-break: break-word;
+        }
+
+        code {
+          font-size: 0.875rem;
+          font-family: $font-family-mono;
+          color: var(--color-gray-600);
+          background: var(--color-gray-200);
+          padding: 0.25rem 0.5rem;
+          border-radius: $radius-sm;
+          display: inline-block;
+        }
+      }
+    }
+
+    @media (max-width: $breakpoint-sm) {
+      grid-template-columns: 1fr;
+
+      > div {
+        align-items: flex-start;
+        text-align: left;
+        flex-wrap: wrap;
+
+        > div:first-child {
+          width: 64px;
+          height: 64px;
+        }
+      }
+    }
+  }
diff --git a/themes/clean-hugo/assets/css/_swoosh.scss b/themes/clean-hugo/assets/css/_swoosh.scss
new file mode 100644
index 00000000..c50488a9
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_swoosh.scss
@@ -0,0 +1,109 @@
+/**
+ * Swoosh sections: full-width blocks with optional curved SVG dividers.
+ * Section is always full viewport width; content is constrained in __content.
+ */
+
+/* Full-bleed: section escapes any parent max-width so it's always full width */
+.swoosh-section {
+  width: 100vw;
+  position: relative;
+  left: 50%;
+  margin: 0 -50vw;
+  padding: 0;
+}
+
+.swoosh-section__content {
+  max-width: 80rem; /* 1280px */
+  margin-inline: auto;
+  padding: $fluid-space-2xl $fluid-container-padding;
+}
+
+/* Background modifiers */
+.swoosh-section--white {
+  background-color: var(--color-white, #fff);
+}
+
+.swoosh-section--purple {
+  background-color: var(--swoosh-bg-purple, #e1dfed);
+  --swoosh-fill-1: #bdb6d6;
+  --swoosh-fill-2: #e2dfed;
+}
+
+.swoosh-section--green {
+  background-color: var(--swoosh-bg-green, #d4ebe3);
+  --swoosh-fill-1: #4e7064; /* darker green highlight (a bit lighter than black-mix) */
+  --swoosh-fill-2: #d4ebe3; /* same light green as section, blends */
+}
+
+/* Divider theme: fill vars when divider is outside section (top/bottom partial) */
+.swoosh-section__divider--purple {
+  --swoosh-fill-1: #bdb6d6;
+  --swoosh-fill-2: #e2dfed;
+}
+
+.swoosh-section__divider--green {
+  --swoosh-fill-1: #4e7064; /* darker green highlight (a bit lighter than black-mix) */
+  --swoosh-fill-2: #d4ebe3; /* same light green as section, blends */
+}
+
+.swoosh-section__divider--white {
+  --swoosh-fill-1: var(--color-white, #fff);
+  --swoosh-fill-2: var(--color-white, #fff);
+}
+
+/* Wrapper for standalone divider (above/below section): full width like section */
+.swoosh-section__divider-wrap {
+  width: 100vw;
+  position: relative;
+  left: 50%;
+  margin-inline: -50vw;
+}
+
+/* Contained width (layout="docs"): fill content column only, no sidebar bleed */
+.swoosh-section--docs,
+.swoosh-section__divider-wrap--docs {
+  width: 100%;
+  max-width: 100%;
+  inset-inline: auto;
+  margin-inline: 0;
+}
+
+/* Divider: full width, contains SVG wave */
+.swoosh-section__divider {
+  position: relative;
+  width: 100%;
+  line-height: 0;
+}
+
+.swoosh-section__divider--bottom {
+  margin-top: 0;
+}
+
+.swoosh-section__divider--top {
+  margin-bottom: 0;
+}
+
+.swoosh-section__svg {
+  display: block;
+  width: 100%;
+  height: auto;
+}
+
+/* Wave paths: fill from CSS variables (set by section modifier) */
+.swoosh-section__wave--1 {
+  fill: var(--swoosh-fill-1);
+  opacity: 0.9;
+}
+
+.swoosh-section__wave--2 {
+  fill: var(--swoosh-fill-2);
+}
+
+/* Bottom divider: SVG sits at bottom of its wrapper */
+.swoosh-section__divider--bottom .swoosh-section__svg {
+  vertical-align: bottom;
+}
+
+.swoosh-section__divider--top .swoosh-section__svg {
+  vertical-align: top;
+}
diff --git a/themes/clean-hugo/assets/css/_training-feature.scss b/themes/clean-hugo/assets/css/_training-feature.scss
new file mode 100644
index 00000000..de04ebea
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_training-feature.scss
@@ -0,0 +1,101 @@
+/* Reusable training / promo strip (Params.training_feature + shortcode). */
+
+.training-feature {
+  margin-bottom: $spacing-section-lg;
+
+  @media (min-width: $breakpoint-md) {
+    margin-bottom: 3rem;
+  }
+
+  &__card {
+    display: grid;
+    gap: $fluid-space-md;
+    align-items: center;
+    padding: $fluid-card-padding-md;
+    border-radius: $radius-xl;
+    background-color: color-mix(in srgb, var(--color-primary-light) 55%, var(--color-white));
+    border: 1px solid color-mix(in srgb, var(--color-primary-dark) 12%, transparent);
+
+    @media (min-width: $breakpoint-md) {
+      grid-template-columns: minmax(0, 1.1fr) minmax(0, 0.9fr);
+      gap: $fluid-space-lg;
+      padding: $fluid-card-padding-lg;
+    }
+  }
+
+  &__content {
+    min-width: 0;
+  }
+
+  &__eyebrow {
+    margin: 0 0 0.5rem;
+    font-size: 0.75rem;
+    font-weight: 700;
+    letter-spacing: 0.08em;
+    text-transform: uppercase;
+    color: var(--color-primary-dark);
+  }
+
+  &__badge {
+    margin: 0 0 0.75rem;
+  }
+
+  &__badge-pill {
+    display: inline-block;
+    padding: 0.25rem 0.65rem;
+    font-size: 0.8125rem;
+    font-weight: 600;
+    color: var(--color-gray-700);
+    background-color: var(--color-gray-200);
+    border-radius: $radius-full;
+  }
+
+  &__title {
+    margin: 0 0 0.75rem;
+    @include responsive(font-size, 1.5rem, 1.875rem, 2rem);
+    font-weight: 700;
+    line-height: 1.2;
+    color: var(--color-primary-dark);
+  }
+
+  &__excerpt {
+    margin: 0 0 1rem;
+    @include responsive(font-size, 1rem, 1.0625rem);
+    line-height: 1.55;
+    color: var(--color-gray-700);
+
+    p {
+      margin: 0 0 0.5rem;
+
+      &:last-child {
+        margin-bottom: 0;
+      }
+    }
+  }
+
+  &__actions {
+    margin: 0;
+    padding-top: 0.25rem;
+  }
+
+  &__media {
+    min-width: 0;
+    justify-self: center;
+    width: 100%;
+    max-width: 22rem;
+
+    @media (min-width: $breakpoint-md) {
+      max-width: none;
+      justify-self: end;
+    }
+  }
+
+  &__image {
+    display: block;
+    width: 100%;
+    height: auto;
+    border-radius: $radius-lg;
+    object-fit: cover;
+    box-shadow: $shadow-md;
+  }
+}
diff --git a/themes/clean-hugo/assets/css/_training.scss b/themes/clean-hugo/assets/css/_training.scss
new file mode 100644
index 00000000..b16b3035
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_training.scss
@@ -0,0 +1,350 @@
+/* Training / learn pages — tutorials, university partnerships, testimonials */
+
+.learn-page__tutorials {
+  margin-bottom: 0;
+  padding-bottom: 0.5rem;
+}
+
+.tutorial-grid {
+  display: grid;
+  gap: 1.25rem;
+  grid-template-columns: 1fr;
+  margin-top: 1.5rem;
+  margin-bottom: 0;
+
+  @media (min-width: $breakpoint-sm) {
+    grid-template-columns: repeat(2, minmax(0, 1fr));
+  }
+
+  @media (min-width: $breakpoint-md) {
+    grid-template-columns: repeat(3, minmax(0, 1fr));
+  }
+
+  @media (min-width: $breakpoint-xl) {
+    grid-template-columns: repeat(4, minmax(0, 1fr));
+  }
+
+  align-items: stretch;
+}
+
+.tutorial-grid__card {
+  display: flex;
+  flex-direction: column;
+  height: 100%;
+  border: 1px solid var(--color-gray-200);
+  border-radius: $radius-md;
+  background-color: var(--color-white);
+  box-shadow: $shadow-sm;
+  transition: transform $transition-base ease, box-shadow $transition-base ease;
+
+  &:hover,
+  &:focus-within {
+    transform: translateY(-0.125rem);
+    box-shadow: $shadow-lg;
+  }
+}
+
+.tutorial-grid__body {
+  flex: 1 1 auto;
+  padding: 1.1rem 1rem 0.85rem;
+}
+
+.tutorial-grid__title {
+  margin: 0 0 0.65rem;
+  font-size: 1.125rem;
+  font-weight: 600;
+  color: var(--color-gray-900);
+  line-height: 1.3;
+}
+
+.tutorial-grid__excerpt {
+  margin: 0;
+  font-size: 0.9375rem;
+  line-height: 1.55;
+  color: var(--color-gray-700);
+}
+
+.tutorial-grid__cta {
+  margin-top: auto;
+  border-radius: 0 0 $radius-md $radius-md;
+  justify-content: center;
+  gap: 0.5rem;
+  background-color: var(--color-brand-purple);
+  color: var(--color-white);
+  font-weight: 600;
+  text-decoration: none;
+
+  &:hover,
+  &:focus {
+    background-color: var(--color-brand-purple-dark);
+    color: var(--color-white);
+    transform: translateY(-1px);
+    box-shadow: $shadow-md;
+  }
+
+  .fa-magnifying-glass {
+    color: var(--color-white);
+  }
+}
+
+.benefits-list {
+  list-style: none;
+  margin: 1.5rem 0 0;
+  padding: 0;
+
+  li {
+    margin-bottom: 1.25rem;
+    padding-left: 0;
+    list-style: none;
+
+    .fa-solid {
+      font-size: 1.1rem;
+      color: var(--color-accent);
+      margin-right: 0.4rem;
+    }
+  }
+}
+
+.partnership-cards {
+  display: grid;
+  gap: 1.25rem;
+  grid-template-columns: 1fr;
+  margin: 2rem 0 1.5rem;
+  align-items: stretch;
+
+  @media (min-width: $breakpoint-sm) {
+    grid-template-columns: repeat(2, minmax(0, 1fr));
+  }
+
+  @media (min-width: $breakpoint-md) {
+    grid-template-columns: repeat(3, minmax(0, 1fr));
+  }
+}
+
+.partnership-card {
+  display: flex;
+  flex-direction: column;
+  min-height: 100%;
+  padding: 1.1rem 1rem;
+  border: 1px solid color-mix(in srgb, var(--color-brand-purple) 18%, transparent);
+  border-radius: $radius-md;
+  background-color: var(--color-white);
+  box-shadow: $shadow-sm;
+  transition: transform $transition-base ease, box-shadow $transition-base ease;
+
+  &:hover,
+  &:focus-within {
+    transform: translateY(-0.125rem);
+    box-shadow: $shadow-lg;
+  }
+
+  &__title {
+    margin: 0.6rem 0 1.2rem;
+    color: var(--color-brand-purple);
+    font-size: 1.25rem;
+    font-weight: 600;
+    line-height: 1.25;
+    text-align: center;
+  }
+
+  &__star {
+    color: var(--color-accent-light);
+  }
+
+  p.partnership-card__price {
+    margin: 0 0 0.85rem;
+    color: var(--color-brand-purple);
+    font-size: 1.5rem;
+    font-weight: 700;
+    line-height: 1.2;
+    text-align: center;
+  }
+
+  &__body {
+    flex: 1 1 auto;
+    display: flex;
+    flex-direction: column;
+    min-height: 0;
+  }
+
+  &__main {
+    flex: 1 1 auto;
+    min-height: 0;
+    display: flex;
+    flex-direction: column;
+  }
+
+  .partnership-card__body > p.partnership-card__price {
+    flex-shrink: 0;
+    margin-top: 0;
+    margin-bottom: 0.35rem;
+  }
+
+  a.partnership-card__cta {
+    flex-shrink: 0;
+    align-self: stretch;
+    margin: 1rem 0 0;
+    text-align: center;
+    text-decoration: none;
+  }
+
+  p.partnership-card__lede {
+    margin: 0 0 0.85rem;
+    color: var(--color-gray-700);
+    font-size: 0.9375rem;
+    line-height: 1.55;
+  }
+
+  &__features {
+    list-style: none;
+    margin: 0;
+    padding: 0;
+
+    li {
+      position: relative;
+      margin: 0 0 0.55rem;
+      padding-left: 1.3rem;
+      font-size: 0.875rem;
+      line-height: 1.5;
+      color: var(--color-gray-700);
+      list-style: none;
+
+      &::before {
+        content: "✓";
+        position: absolute;
+        left: 0;
+        top: 0.02rem;
+        color: var(--color-accent);
+        font-weight: 600;
+      }
+
+      &:last-child {
+        margin-bottom: 0;
+      }
+    }
+  }
+
+  &__divider {
+    width: 100%;
+    border: 0;
+    border-top: 1px solid color-mix(in srgb, var(--color-soft-purple) 95%, transparent);
+    margin: 1rem 0 0.7rem;
+  }
+
+  p.partnership-card__subheader {
+    margin: 0.6rem 0 1.2rem;
+    color: color-mix(in srgb, var(--color-brand-purple) 55%, var(--color-soft-purple));
+    font-size: 0.75rem;
+    font-weight: 600;
+    letter-spacing: 0.08em;
+    text-transform: uppercase;
+    line-height: 1.4;
+  }
+}
+
+.partnership-card--featured {
+  border-color: color-mix(in srgb, var(--color-primary-dark) 45%, transparent);
+  box-shadow: $shadow-md;
+}
+
+.testimonial-showcase {
+  margin: 0;
+  padding: 0;
+  display: flex;
+  flex-direction: column;
+  gap: 1.25rem;
+  max-width: 100%;
+}
+
+.testimonial-showcase__featured {
+  display: flex;
+  flex-direction: column;
+  align-items: center;
+  gap: 1rem;
+  margin: 0;
+  padding: 1.25rem 1.25rem 1.35rem;
+  border-radius: $radius-md;
+  background-color: var(--color-white);
+  box-shadow: $shadow-sm;
+  border: 1px solid color-mix(in srgb, var(--color-brand-purple) 12%, transparent);
+  text-align: left;
+
+  @media (min-width: $breakpoint-sm) {
+    flex-direction: row;
+    align-items: flex-start;
+    gap: 1.5rem;
+    padding: 1.5rem 1.5rem 1.6rem;
+  }
+}
+
+.testimonial-showcase__avatar-wrap {
+  flex-shrink: 0;
+}
+
+.testimonial-showcase__avatar {
+  width: 7.5rem;
+  height: 7.5rem;
+  border-radius: $radius-full;
+  object-fit: cover;
+  display: block;
+  border: 3px solid color-mix(in srgb, var(--color-brand-purple) 18%, transparent);
+  box-sizing: border-box;
+}
+
+.testimonial-showcase__featured-body {
+  flex: 1 1 auto;
+  min-width: 0;
+}
+
+.testimonial-showcase__mark {
+  margin: 0 0 0.35rem;
+  line-height: 1;
+  color: var(--color-brand-purple);
+
+  .fa-quote-left {
+    font-size: 1.5rem;
+  }
+
+  &--compact {
+    color: var(--color-accent);
+
+    .fa-quote-left {
+      font-size: 1.25rem;
+    }
+  }
+}
+
+.testimonial-showcase__cite {
+  margin: 0;
+  font-size: 0.875rem;
+  line-height: 1.4;
+  font-style: normal;
+  font-weight: 600;
+  color: var(--color-gray-600);
+}
+
+.testimonial-showcase__grid {
+  display: grid;
+  gap: 1.25rem;
+  grid-template-columns: 1fr;
+
+  @media (min-width: $breakpoint-sm) {
+    grid-template-columns: repeat(2, minmax(0, 1fr));
+  }
+}
+
+.testimonial-showcase__card {
+  margin: 0;
+  padding: 1.1rem 1rem 1.15rem;
+  border-radius: $radius-md;
+  background-color: var(--color-white);
+  box-shadow: $shadow-sm;
+  border: 1px solid color-mix(in srgb, var(--color-brand-purple) 12%, transparent);
+  border-top: 4px solid var(--color-accent);
+  text-align: left;
+}
+
+.training-page__figure {
+  margin: 2rem auto;
+  max-width: 48rem;
+}
diff --git a/themes/clean-hugo/assets/css/_utilities.scss b/themes/clean-hugo/assets/css/_utilities.scss
new file mode 100644
index 00000000..33ac367f
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_utilities.scss
@@ -0,0 +1,84 @@
+/*
+  Accessibility utilities: skip links.
+  Link is visually hidden by default and becomes visible on :focus
+  so keyboard users can jump to main content.
+*/
+
+.skip-links {
+  position: absolute;
+  z-index: 100;
+  margin: 0;
+  padding: 0;
+  list-style: none;
+
+  ul {
+    margin: 0;
+    padding: 0;
+    list-style: none;
+  }
+
+  li {
+    margin: 0;
+  }
+}
+
+.skip-link__link {
+  position: absolute;
+  clip: rect(1px, 1px, 1px, 1px);
+  clip-path: inset(50%);
+  width: 1px;
+  height: 1px;
+  margin: -1px;
+  padding: 0;
+  overflow: hidden;
+  border: 0;
+  white-space: nowrap;
+
+  &:focus {
+    position: fixed;
+    top: 0.5rem;
+    left: 0.5rem;
+    z-index: 10001;
+    clip: auto;
+    clip-path: none;
+    width: auto;
+    height: auto;
+    margin: 0;
+    padding: 0.75rem 1rem;
+    background: var(--color-white, #fff);
+    color: var(--color-link, #2563eb);
+    font-weight: 600;
+    text-decoration: none;
+    box-shadow: 0 0 0 2px currentColor;
+    border-radius: 0.25rem;
+  }
+}
+
+/*
+  Print styles: hide non-content, keep focus on main content.
+*/
+@media print {
+  .skip-links,
+  .site-nav,
+  .site-footer,
+  .docs-toggle,
+  .docs-scroll-btn,
+  .docs-sidebar,
+  button.site-nav__toggle {
+    display: none !important;
+  }
+
+  body {
+    font-size: 12pt;
+    line-height: 1.4;
+  }
+
+  a[href]::after {
+    content: none;
+  }
+
+  main {
+    print-color-adjust: exact;
+    -webkit-print-color-adjust: exact;
+  }
+}
diff --git a/themes/clean-hugo/assets/css/_variables.scss b/themes/clean-hugo/assets/css/_variables.scss
new file mode 100644
index 00000000..490a5ae6
--- /dev/null
+++ b/themes/clean-hugo/assets/css/_variables.scss
@@ -0,0 +1,151 @@
+/**
+ * Theme Variables - Mobile First
+ * Base values target mobile (320px+), use breakpoints to enhance
+ */
+
+/* Typography — font names (@font-face) and stacks (never hardcode fonts elsewhere) */
+$font-name-body: 'Nunito Sans';
+$font-name-heading: 'Poppins';
+$font-name-quote: 'Lora';
+
+$font-family-body: $font-name-body, 'ui-sans-serif', 'system-ui', '-apple-system',
+  'Segoe UI', 'Roboto', 'Helvetica Neue', 'Arial', sans-serif;
+$font-family-heading: $font-name-heading, $font-name-body, 'ui-sans-serif', 'system-ui',
+  sans-serif;
+$font-family-quote: $font-name-quote, 'Georgia', 'Times New Roman', serif;
+$font-family-mono: 'Monaco', 'Menlo', 'Ubuntu Mono', 'Consolas', 'source-code-pro',
+  monospace;
+
+/* Breakpoints - min-width (mobile first) */
+$breakpoint-sm: 640px;            /* Large phones / small tablets */
+$breakpoint-md: 768px;            /* Tablets */
+$breakpoint-lg: 1024px;           /* Desktop */
+$breakpoint-xl: 1280px;           /* Large desktop */
+$breakpoint-2xl: 1536px;          /* Extra large */
+
+/* Container Max Widths */
+$container-max-width: 80rem;      /* 1280px - standard container */
+$container-impact-wide: 96rem;    /* 1536px - optional wide splash / impact card grid */
+$container-narrow: 56rem;         /* 896px - content/blog posts */
+$container-wide: 42rem;           /* 672px - narrow content */
+
+/* Spacing - mobile base values */
+$spacing-xs: 0.5rem;              /* 8px - minimal spacing */
+$spacing-sm: 1rem;                /* 16px - small spacing */
+$spacing-md: 1.5rem;              /* 24px - medium spacing */
+$spacing-lg: 2rem;                /* 32px - large spacing */
+$spacing-xl: 3rem;                /* 48px - extra large spacing */
+$spacing-section: 2rem;           /* Mobile section padding */
+$spacing-section-lg: 3rem;        /* Desktop section padding */
+
+/* Fluid Spacing - Using clamp() for smooth mobile-first scaling */
+$fluid-space-xs: clamp(0.5rem, 1vw, 0.75rem);          /* 8px → 12px */
+$fluid-space-sm: clamp(0.75rem, 2vw, 1.5rem);          /* 12px → 24px */
+$fluid-space-md: clamp(1rem, 3vw, 2rem);               /* 16px → 32px */
+$fluid-space-lg: clamp(1.5rem, 4vw, 3rem);             /* 24px → 48px */
+$fluid-space-xl: clamp(2rem, 6vw, 4rem);               /* 32px → 64px */
+$fluid-space-2xl: clamp(2rem, 8vw, 5rem);              /* 32px → 80px */
+$fluid-space-3xl: clamp(2.5rem, 10vw, 6rem);           /* 40px → 96px */
+
+/* Fluid Container Padding */
+$fluid-container-padding: clamp(0.75rem, 3vw, 1.5rem); /* Container horizontal */
+$fluid-container-padding-lg: clamp(1rem, 4vw, 2rem);   /* Narrow containers */
+
+/* Fluid Card/Component Padding */
+$fluid-card-padding-sm: clamp(1rem, 3vw, 1.5rem);      /* Small cards */
+$fluid-card-padding-md: clamp(1.25rem, 4vw, 2.5rem);   /* Medium cards */
+$fluid-card-padding-lg: clamp(1.5rem, 5vw, 4rem);      /* Large impact cards */
+
+/* Border Radius */
+$radius-sm: 0.25rem;              /* 4px */
+$radius-md: 0.5rem;               /* 8px */
+$radius-lg: 1rem;                 /* 16px */
+$radius-xl: 1.5rem;               /* 24px */
+$radius-full: 9999px;             /* Fully rounded */
+
+/* Outline button border widths (width only; use in `border: … solid …`) */
+$btn-bd-thin: 0.8px; /* hero on dark, .btn--secondary — may paint as 1px on some DPR */
+$btn-bd: 1px;       /* .btn--outline-on-light */
+
+/* Transitions */
+$transition-fast: 150ms;
+$transition-base: 200ms;
+$transition-slow: 300ms;
+$transition-slower: 500ms;
+
+/* Shadows */
+$shadow-sm: 0 1px 2px 0 rgba(0, 0, 0, 0.05);
+$shadow-md: 0 4px 6px -1px rgba(0, 0, 0, 0.1), 0 2px 4px -1px rgba(0, 0, 0, 0.06);
+$shadow-lg: 0 10px 15px -3px rgba(0, 0, 0, 0.1), 0 4px 6px -2px rgba(0, 0, 0, 0.05);
+$shadow-xl: 0 10px 30px rgba(17, 24, 39, 0.08);
+$shadow-2xl: 0 25px 50px -12px rgba(0, 0, 0, 0.25);
+
+/* Z-index scale */
+$z-dropdown: 50;
+$z-sticky: 100;
+$z-fixed: 200;
+$z-overlay: 300;
+$z-modal: 400;
+
+/* Card Typography - Shared across homepage content cards */
+/* (impact cards, two-card-row, single-card-wide) */
+$card-heading-size: clamp(1.7rem, 3vw, 1.875rem);     /* H3 headings */
+$card-text-size: clamp(1.25rem, 2.5vw, 1.5rem);       /* Paragraphs & list items */
+$card-list-padding: clamp(0.25rem, 2.5vw, 1.5rem);    /* List padding-left - minimal on mobile */
+$card-text-color: var(--color-gray-700);              /* Body text color */
+$card-line-height: 1.6;                                /* Text line height */
+
+/* Card Layout & Styling - Shared styles for card components */
+$card-border-radius: $radius-lg;                       /* Card corner rounding */
+$card-border: 1px solid var(--color-gray-200);        /* Card border */
+$card-shadow: $shadow-sm;                              /* Card shadow */
+$card-shadow-hover: $shadow-xl;                        /* Card shadow on hover */
+$card-hover-transform: translateY(-4px);               /* Card lift on hover */
+$card-icon-size: clamp(2.25rem, 4vw, 3rem);           /* Icon size in cards */
+$card-gap: clamp(1.25rem, 3vw, 2.5rem);               /* Gap between cards in grid */
+
+/* Listing card density tokens for blog/event archive cards */
+$listing-card-default: (
+  padding: 1.5rem,
+  meta-font-size: 0.9375rem,
+  meta-gap: 0.75rem,
+  category-font-size: 0.75rem,
+  category-padding: 0.25rem 0.5rem,
+  title-font-size: 1.25rem,
+  title-line-height: 1.4,
+  excerpt-font-size: 1rem,
+  excerpt-line-height: 1.6,
+  read-more-font-size: 0.9375rem
+);
+
+$listing-card-compact: (
+  padding: 0.8rem 0.9rem,
+  meta-font-size: 0.65rem,
+  meta-gap: 0.4rem,
+  category-font-size: 0.55rem,
+  category-padding: 0.16rem 0.36rem,
+  title-font-size: 0.85rem,
+  title-line-height: 1.35,
+  excerpt-font-size: 0.7rem,
+  excerpt-line-height: 1.55,
+  read-more-font-size: 0.65rem
+);
+
+/* Base HTML heading font sizes: mobile, tablet, desktop */
+$heading-font-sizes: (
+  h1: 3rem 3.75rem 4.5rem,
+  h2: 2.25rem 2.25rem 3rem,
+  h3: 1.5rem 1.875rem 2.25rem,
+  h4: 1.25rem 1.5rem 1.875rem,
+  h5: 1.125rem 1.25rem 1.5rem,
+  h6: 1rem 1.125rem 1.25rem,
+);
+
+$heading-meta: (
+  h1: (weight: 700, margin-top: 0, margin-bottom: 0.5rem),
+  h2: (weight: 600, margin-top: 2.8rem, margin-bottom: 0.5rem),
+  h3: (weight: 600, margin-top: 2.3rem, margin-bottom: 0.5rem),
+  h4: (weight: 600, margin-top: 1.8rem, margin-bottom: 0.5rem),
+  h5: (weight: 600, margin-top: 1.55rem, margin-bottom: 0.5rem),
+  h6: (weight: 600, margin-top: 1.3rem, margin-bottom: 0.5rem),
+);
diff --git a/themes/clean-hugo/assets/css/site.scss b/themes/clean-hugo/assets/css/site.scss
new file mode 100644
index 00000000..a754bfab
--- /dev/null
+++ b/themes/clean-hugo/assets/css/site.scss
@@ -0,0 +1,275 @@
+/*
+Breakpoints:
+sm: 640px
+md: 768px
+lg: 1024px
+xl: 1280px
+2xl: 1536px
+*/
+
+/* Variables and Mixins - Import First */
+@import 'variables';
+@import 'mixins';
+
+/* Button System */
+@import 'buttons';
+
+/* Accessibility utilities (skip links) */
+@import 'utilities';
+
+/* Base Styles */
+  /* Universal box-sizing and overflow fix */
+  *, *::before, *::after {
+    box-sizing: border-box;
+  }
+
+  html {
+    overflow-x: hidden;
+  }
+
+  /*
+    Self-hosted font declarations
+    Font files are in themes/clean-hugo/static/fonts/
+  */
+
+  /* Nunito Sans variable font (body text) - regular/roman style */
+  @font-face {
+    font-family: $font-name-body;
+    font-style: normal;
+    font-weight: 200 900;
+    font-display: swap;
+    src: url('../fonts/NunitoSans-VariableFont.woff2') format('woff2');
+  }
+
+  /* Nunito Sans variable font (body text) - italic style */
+  @font-face {
+    font-family: $font-name-body;
+    font-style: italic;
+    font-weight: 200 900;
+    font-display: swap;
+    src: url('../fonts/NunitoSans-Italic-VariableFont.woff2') format('woff2');
+  }
+
+  /* Poppins (headings) */
+  @font-face {
+    font-family: $font-name-heading;
+    font-style: normal;
+    font-weight: 300;
+    font-display: swap;
+    src: url('../fonts/Poppins-Light.woff2') format('woff2');
+  }
+
+  @font-face {
+    font-family: $font-name-heading;
+    font-style: normal;
+    font-weight: 400;
+    font-display: swap;
+    src: url('../fonts/Poppins-Regular.woff2') format('woff2');
+  }
+
+  @font-face {
+    font-family: $font-name-heading;
+    font-style: italic;
+    font-weight: 400;
+    font-display: swap;
+    src: url('../fonts/Poppins-Italic.woff2') format('woff2');
+  }
+
+  @font-face {
+    font-family: $font-name-heading;
+    font-style: normal;
+    font-weight: 500;
+    font-display: swap;
+    src: url('../fonts/Poppins-Medium.woff2') format('woff2');
+  }
+
+  @font-face {
+    font-family: $font-name-heading;
+    font-style: normal;
+    font-weight: 600;
+    font-display: swap;
+    src: url('../fonts/Poppins-SemiBold.woff2') format('woff2');
+  }
+
+  @font-face {
+    font-family: $font-name-heading;
+    font-style: normal;
+    font-weight: 700;
+    font-display: swap;
+    src: url('../fonts/Poppins-Bold.woff2') format('woff2');
+  }
+
+  /* Lora italic variable font (quotations) */
+  @font-face {
+    font-family: $font-name-quote;
+    font-style: italic;
+    font-weight: 400 700;
+    font-display: swap;
+    src: url('../fonts/Lora-Italic-VariableFont_wght.woff2') format('woff2');
+  }
+
+  /*
+    CSS Variables for theme colors
+    All color variables are injected via inline <style> block in baseof.html
+    from site configuration (hugo.toml or theme.toml defaults)
+  */
+
+  body {
+    font-family: $font-family-body;
+    color: var(--color-gray-900);
+    background-color: var(--color-gray-50);
+    margin: 0;
+    width: 100%;
+    max-width: 100vw;
+    overflow-x: hidden;
+  }
+
+  /* Typography System - Base Heading Styles */
+  h1, h2, h3, h4, h5, h6 {
+    font-family: $font-family-heading;
+    color: inherit;
+    line-height: 1.25;
+  }
+
+  @each $tag, $sizes in $heading-font-sizes {
+    $m: map-get($heading-meta, $tag);
+
+    #{$tag} {
+      @include type-scale-3(nth($sizes, 1), nth($sizes, 2), nth($sizes, 3));
+      font-weight: map-get($m, weight);
+      margin-top: map-get($m, margin-top);
+      margin-bottom: map-get($m, margin-bottom);
+    }
+  }
+
+  /* Base Typography - Paragraphs and Lists share the same text size and line-height */
+  p,
+  ul, ol,
+  li {
+    @include type-scale-md(1.125rem, 1.25rem);
+    margin-bottom: 1rem;
+    line-height: 1.75;
+    color: var(--color-gray-700);
+  }
+
+  /* List-specific styling */
+  ul, ol {
+    margin-left: clamp(1rem, 2.5vw, 1.5rem);
+    padding-left: 0;
+  }
+
+  li {
+    margin-bottom: 0.5rem;
+  }
+
+  ul {
+    list-style-type: disc;
+  }
+
+  ol {
+    list-style-type: decimal;
+  }
+
+  /* Horizontal rules */
+  hr {
+    margin: 2rem 0;
+    border-top: 1px solid;
+    border-color: var(--color-gray-200);
+  }
+
+  /* Links - base styles (can be overridden in components) */
+  a:not(.btn) {
+    transition: color 0.2s;
+    color: var(--color-link);
+
+    &:hover,
+    &:focus {
+      color: var(--color-link-hover);
+    }
+  }
+
+  /* Strong and emphasis */
+  strong {
+    font-weight: 600;
+    color: var(--color-gray-900);
+  }
+
+  em {
+    font-style: italic;
+  }
+/* Utility Classes */
+
+  /* Reusable background color utilities - short, generalized class names */
+  .bg-card {
+    background-color: var(--color-feature-card);
+  }
+
+  .bg-primary {
+    background-color: var(--color-primary-light);
+  }
+
+  .bg-secondary {
+    background-color: var(--color-secondary);
+  }
+
+  /* Spacing utilities */
+  .py-12 {
+    padding: 3rem 0;
+  }
+
+  /* Container utilities - standardize container widths across the site */
+  /* Standard container - used throughout site (max-w-7xl) */
+  .container {
+    max-width: 80rem;
+    margin: 0 auto;
+    padding: 0 $fluid-container-padding;
+  }
+
+  /* Narrow container for content (blog posts, etc.) - max-w-4xl */
+  .container-narrow {
+    max-width: 56rem;
+    margin: 0 auto;
+    padding: 0 $fluid-container-padding-lg;
+  }
+
+  /* Wide container for hero sections - fluid padding */
+  .container-wide {
+    max-width: 80rem;
+    margin: 0 auto;
+    padding: 0 $fluid-container-padding;
+  }
+
+  /* Full-width breakout utility - breaks out of constrained containers */
+  /* Use this class on any element that needs to span full viewport width */
+  /* Works within blog posts, packages page, or any constrained container */
+  .full-width {
+    width: 100%;
+    max-width: 100%;
+    margin-inline: calc(-1 * $fluid-container-padding);
+  }
+
+/* Component Imports */
+@import 'navigation';
+@import 'content';
+@import 'blog';
+@import 'learn-more';
+@import 'filter';
+@import 'hero';
+@import 'cards';
+@import 'feature-section';
+@import 'intro-section';
+@import 'training-feature';
+@import 'swoosh';
+@import 'footer';
+@import 'gallery';
+@import 'blog-listing';
+@import 'shortcodes';
+@import 'admonition';
+@import 'quotes';
+@import 'code';
+@import 'figure';
+@import 'packages';
+@import 'events';
+@import 'training';
+@import 'people';
+@import 'docs';
diff --git a/themes/clean-hugo/layouts/404.html b/themes/clean-hugo/layouts/404.html
new file mode 100644
index 00000000..5cb57f53
--- /dev/null
+++ b/themes/clean-hugo/layouts/404.html
@@ -0,0 +1,28 @@
+<!DOCTYPE html>
+<html lang="{{ .Site.LanguageCode | default "en" }}">
+<head>
+  <meta charset="UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
+  <title>Page not found | {{ .Site.Title }}</title>
+  <meta name="robots" content="noindex, nofollow">
+  {{/* Use theme CSS so 404 matches site look */}}
+  {{ $styles := resources.Get "css/site.scss" | toCSS | postCSS | minify | fingerprint }}
+  <link rel="stylesheet" href="{{ $styles.RelPermalink }}">
+</head>
+<body>
+  {{ partial "skip-link.html" . }}
+  <nav id="site-nav" class="site-nav" aria-label="Primary">
+    <div class="site-nav__container">
+      <a href="{{ "" | relURL }}" class="site-nav__brand">{{ .Site.Params.author | default .Site.Title }}</a>
+    </div>
+  </nav>
+  <main id="main">
+    <div class="content-container" style="padding: 2rem 1rem; max-width: 65ch;">
+      <h1>Page not found</h1>
+      <p>The page you're looking for doesn't exist or has moved.</p>
+      <p><a href="{{ "" | relURL }}" class="btn btn--dark-purple">Go to the home page</a></p>
+    </div>
+  </main>
+  {{ partial "footer.html" . }}
+</body>
+</html>
diff --git a/themes/clean-hugo/layouts/_default/baseof.html b/themes/clean-hugo/layouts/_default/baseof.html
new file mode 100644
index 00000000..ac6b8467
--- /dev/null
+++ b/themes/clean-hugo/layouts/_default/baseof.html
@@ -0,0 +1,204 @@
+<!DOCTYPE html>
+<html lang="{{ .Site.LanguageCode | default "en" }}">
+<head>
+  <meta charset="UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
+  <title>{{ if .IsHome }}{{ .Site.Title }}{{ else }}{{ .Title }} | {{ .Site.Title }}{{ end }}</title>
+  <meta name="description" content="{{ with .Description }}{{ . }}{{ else }}{{ .Summary | plainify | truncate 160 }}{{ end }}">
+
+  {{/* SEO: Open Graph, Canonical URLs, and Social Metadata */}}
+  {{ partial "seo.html" . }}
+
+  {{/* Favicons */}}
+  <link rel="icon" type="image/x-icon" href="{{ "favicon.ico" | relURL }}">
+  <link rel="icon" type="image/png" sizes="32x32" href="{{ "favicon-32x32.png" | relURL }}">
+  <link rel="icon" type="image/png" sizes="16x16" href="{{ "favicon-16x16.png" | relURL }}">
+  <link rel="apple-touch-icon" sizes="180x180" href="{{ "apple-touch-icon.png" | relURL }}">
+  <link rel="manifest" href="{{ "site.webmanifest" | relURL }}">
+
+  {{/* Self-hosted fonts via @font-face (defined in site.scss) */}}
+
+  {{/* Font Awesome (CDN) */}}
+  {{ if .Site.Params.theme.enableFontAwesome | default true }}
+    <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.4.0/css/all.min.css" crossorigin="anonymous" referrerpolicy="no-referrer" />
+  {{ end }}
+
+  {{/*
+    Inject CSS variables from theme config (hugo.toml).
+    NOTE: This must be in baseof.html (not SCSS) because:
+    1. SCSS files cannot access Hugo template variables (.Site.Params)
+    2. This inline <style> block loads BEFORE the compiled SCSS, allowing
+       user-defined colors from hugo.toml to override the defaults in site.scss
+    3. This is a standard Hugo pattern for theme customization
+  */}}
+  {{ $colors := .Site.Params.theme.colors | default dict }}
+  <style>
+    :root {
+      {{ with $colors.primary }}--color-primary: {{ . }};{{ end }}
+      {{ with $colors.primaryDark }}--color-primary-dark: {{ . }};{{ end }}
+      {{ with $colors.primaryLight }}--color-primary-light: {{ . }};{{ end }}
+      {{ with $colors.secondary }}--color-secondary: {{ . }};{{ end }}
+      {{ with $colors.accent }}--color-accent: {{ . }};{{ end }}
+      {{ with $colors.accentLight }}--color-accent-light: {{ . }};{{ end }}
+      {{ with $colors.neutral }}--color-neutral: {{ . }};{{ end }}
+      {{ with $colors.heroBg }}--color-hero-bg: {{ . }};{{ end }}
+      {{ with $colors.brandPurple }}--color-brand-purple: {{ . }};{{ end }}
+      {{ with $colors.brandPurpleDark }}--color-brand-purple-dark: {{ . }};{{ end }}
+      {{ with $colors.brandPurpleMedium }}--color-brand-medium-purple: {{ . }};{{ end }}
+      {{ with $colors.brandSoftPurple }}--color-soft-purple: {{ . }};{{ end }}
+      {{ with $colors.brandLightPurple }}--color-light-purple: {{ . }};{{ end }}
+      {{ with $colors.brandMagenta }}--color-brand-magenta: {{ . }};{{ end }}
+      {{ with $colors.brandHeaderPurple }}--color-brand-header-purple: {{ . }};{{ end }}
+      {{ with $colors.white }}--color-white: {{ . }};{{ end }}
+      {{ with $colors.gray50 }}--color-gray-50: {{ . }};{{ end }}
+      {{ with $colors.gray200 }}--color-gray-200: {{ . }};{{ end }}
+      {{ with $colors.gray600 }}--color-gray-600: {{ . }};{{ end }}
+      {{ with $colors.gray700 }}--color-gray-700: {{ . }};{{ end }}
+      {{ with $colors.gray900 }}--color-gray-900: {{ . }};{{ end }}
+      {{ with $colors.link }}--color-link: {{ . }};{{ end }}
+      {{ with $colors.linkOnDark }}--color-link-on-dark: {{ . }};{{ end }}
+      {{ with $colors.linkHover }}--color-link-hover: {{ . }};{{ end }}
+      {{ with $colors.featureCard }}--color-feature-card: {{ . }};{{ end }}
+
+
+      {{ $admonitionInfo := index $colors "admonition-info" }}
+      {{ $admonitionSuccess := index $colors "admonition-success" }}
+      {{ $admonitionWarning := index $colors "admonition-warning" }}
+      {{ $admonitionDanger := index $colors "admonition-danger" }}
+      {{ $admonitionNote := index $colors "admonition-note" }}
+
+      {{ with $admonitionInfo }}--color-admonition-info: {{ . }};{{ end }}
+      {{ with $admonitionSuccess }}--color-admonition-success: {{ . }};{{ end }}
+      {{ with $admonitionWarning }}--color-admonition-warning: {{ . }};{{ end }}
+      {{ with $admonitionDanger }}--color-admonition-danger: {{ . }};{{ end }}
+      {{ with $admonitionNote }}--color-admonition-note: {{ . }};{{ end }}
+
+      {{/* Event listing type pills (/events/) — set in hugo.toml [params.theme.colors] */}}
+      {{ with index $colors "eventLabelTrainingBg" }}--color-event-label-training-bg: {{ . }};{{ end }}
+      {{ with index $colors "eventLabelTrainingFg" }}--color-event-label-training-fg: {{ . }};{{ end }}
+      {{ with index $colors "eventLabelSprintBg" }}--color-event-label-sprint-bg: {{ . }};{{ end }}
+      {{ with index $colors "eventLabelSprintFg" }}--color-event-label-sprint-fg: {{ . }};{{ end }}
+      {{ with index $colors "eventLabelCommunityBg" }}--color-event-label-community-bg: {{ . }};{{ end }}
+      {{ with index $colors "eventLabelCommunityFg" }}--color-event-label-community-fg: {{ . }};{{ end }}
+      {{ with index $colors "eventLabelTalkBg" }}--color-event-label-talk-bg: {{ . }};{{ end }}
+      {{ with index $colors "eventLabelTalkFg" }}--color-event-label-talk-fg: {{ . }};{{ end }}
+      {{ with index $colors "eventDateBadgeBg" }}--color-event-date-badge-bg: {{ . }};{{ end }}
+      {{ with index $colors "eventDateBadgeFg" }}--color-event-date-badge-fg: {{ . }};{{ end }}
+    }
+  </style>
+
+  {{/* Theme styles */}}
+  {{ $styles := resources.Get "css/site.scss" | toCSS | postCSS | minify | fingerprint }}
+  <link rel="stylesheet" href="{{ $styles.RelPermalink }}">
+
+  {{/* Chroma syntax highlighting CSS - generated with: hugo gen chromastyles --style=monokai */}}
+  <link rel="stylesheet" href="{{ "css/syntax.css" | relURL }}">
+
+  {{/* GLightbox CSS for gallery feature */}}
+  {{ if .Site.Params.theme.enableGallery | default true }}
+    <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/glightbox/dist/css/glightbox.min.css">
+  {{ end }}
+
+  {{/* Analytics */}}
+  {{ with .Site.Params.analytics.google }}
+    <!-- Google Analytics -->
+    <script async src="https://www.googletagmanager.com/gtag/js?id={{ . }}"></script>
+    <script>
+      window.dataLayer = window.dataLayer || [];
+      function gtag(){dataLayer.push(arguments);}
+      gtag('js', new Date());
+      gtag('config', '{{ . }}');
+    </script>
+  {{ end }}
+  {{ with .Site.Params.analytics.plausible }}
+    <!-- Plausible Analytics -->
+    <script defer data-domain="{{ . }}" src="https://plausible.io/js/script.js"></script>
+  {{ end }}
+
+  {{/* AlpineJS for interactive components (packages filtering, etc.) */}}
+  <script defer src="https://cdn.jsdelivr.net/npm/alpinejs@3.x.x/dist/cdn.min.js"></script>
+
+  {{/* Package filter component - loads immediately (no defer) to register listener before Alpine initializes */}}
+  <script src="{{ "js/package-filter.js" | relURL }}"></script>
+  {{/* People filter component - loads immediately (no defer) to register listener before Alpine initializes */}}
+  <script src="{{ "js/people-filter.js" | relURL }}"></script>
+</head>
+<body>
+  {{ partial "skip-link.html" . }}
+  <!-- Navigation -->
+  <nav id="site-nav" class="site-nav" aria-label="Primary">
+    <div class="site-nav__container">
+      <a href="{{ "" | relURL }}" class="site-nav__brand{{ with .Site.Params.nav_logo }} site-nav__brand--logo{{ end }}">
+        {{ with .Site.Params.nav_logo }}
+          <img
+            class="site-nav__logo"
+            src="{{ .src | relURL }}"
+            alt="{{ .alt | default (printf "%s logo" $.Site.Title) }}"
+            width="{{ .width | default 56 }}"
+            height="{{ .height | default 56 }}"
+            decoding="async"
+          />
+        {{ else }}
+          {{ .Site.Params.author | default .Site.Title }}
+        {{ end }}
+      </a>
+      <button class="site-nav__toggle" aria-label="Toggle navigation" aria-expanded="false" aria-controls="site-nav-menu">
+        <span class="site-nav__toggle-icon"></span>
+        <span class="site-nav__toggle-icon"></span>
+        <span class="site-nav__toggle-icon"></span>
+      </button>
+      <div class="site-nav__menu" id="site-nav-menu">
+        {{ range .Site.Menus.main }}
+          {{ if .HasChildren }}
+            <div class="site-nav__dropdown">
+              <button class="site-nav__link site-nav__link--dropdown" aria-haspopup="true" aria-expanded="false">
+                {{ .Name }}
+                <i class="fas fa-chevron-down" aria-hidden="true"></i>
+              </button>
+              <ul class="site-nav__dropdown-menu">
+                {{ range .Children }}
+                  {{ $item := . }}
+                  <li>
+                    <a href="{{ $item.URL }}"
+                       class="site-nav__dropdown-link"
+                       {{- if eq $item.URL $.RelPermalink }} aria-current="page"{{ end -}}
+                       {{- with $item.Params.external }}
+                         target="_blank" rel="noopener noreferrer"
+                         aria-label="{{ $item.Name }} (opens in new tab)"
+                       {{- end }}>
+                      {{ $item.Name }}
+                      {{- with $item.Params.icon }}
+                        <i class="{{ . }}" aria-hidden="true"></i>
+                      {{- end }}
+                    </a>
+                  </li>
+                {{ end }}
+              </ul>
+            </div>
+          {{ else }}
+            <a href="{{ .URL }}" class="site-nav__link"{{ if eq .URL $.RelPermalink }} aria-current="page"{{ end }}>{{ .Name }}</a>
+          {{ end }}
+        {{ end }}
+
+        {{/* Optional CTA Button */}}
+        {{ with .Site.Params.nav_button }}
+          <a href="{{ .url }}"
+             class="btn btn--{{ .variant | default "dark-purple" }} site-nav__button{{ with .class }} {{ . }}{{ end }}">
+            {{ .text }}
+          </a>
+        {{ end }}
+      </div>
+    </div>
+  </nav>
+
+  <main id="main">
+    {{ block "main" . }}{{ end }}
+  </main>
+  {{ partial "footer.html" . }}
+
+  {{/* Navigation bar toggle JavaScript */}}
+  <script src="{{ "js/navigation.js" | relURL }}" defer></script>
+
+  {{ block "scripts" . }}{{ end }}
+</body>
+</html>
diff --git a/themes/clean-hugo/layouts/_default/docs.html b/themes/clean-hugo/layouts/_default/docs.html
new file mode 100644
index 00000000..7b67ce9c
--- /dev/null
+++ b/themes/clean-hugo/layouts/_default/docs.html
@@ -0,0 +1,38 @@
+{{ define "main" }}
+{{ $header := .Params.header | default dict }}
+{{ $headerColor := $header.color | default "primaryDark" }}
+{{ $headerTitle := $header.title | default .Title }}
+{{ $isHex := hasPrefix $headerColor "#" }}
+<div class="docs-header {{ if not $isHex }}docs-header--{{ $headerColor }}{{ end }}"{{ if $isHex }} style="background-color: {{ $headerColor }};"{{ end }}>
+  <div class="docs-header__inner">
+    <h1 class="docs-header__title">{{ $headerTitle }}</h1>
+  </div>
+</div>
+
+<div class="overlay"></div>
+
+<button class="docs-toggle" aria-label="Toggle documentation sidebar">
+  <i class="fas fa-bars"></i>
+</button>
+
+<div class="docs-layout">
+  <aside class="docs-sidebar">
+    <nav id="docs-nav">
+      {{- partial "docs-sidebar.html" . -}}
+    </nav>
+  </aside>
+
+  <article class="docs-content">
+    {{ with .Params.excerpt }}<p class="docs-excerpt">{{ . }}</p>{{ end }}
+    {{ .Content }}
+    {{ partial "last-modified.html" . }}
+  </article>
+
+  <button id="scroll-to-top" class="docs-scroll-btn" aria-label="Scroll to top">
+    <i class="fas fa-arrow-up"></i>
+  </button>
+</div>
+
+<script src="{{ "js/docs-nav.js" | relURL }}" defer></script>
+<script src="{{ "js/docs-sidebar.js" | relURL }}" defer></script>
+{{ end }}
diff --git a/themes/clean-hugo/layouts/_default/list.html b/themes/clean-hugo/layouts/_default/list.html
new file mode 100644
index 00000000..9b0c9e61
--- /dev/null
+++ b/themes/clean-hugo/layouts/_default/list.html
@@ -0,0 +1,17 @@
+{{ define "main" }}
+<section class="section-container">
+  <h1 class="section-title">{{ .Title }}</h1>
+  {{ with .Content }}
+    <div class="section-content">{{ . }}</div>
+  {{ end }}
+
+  <div class="section-list">
+    {{ range .Pages }}
+      <article class="section-item">
+        <a href="{{ .Permalink }}">{{ .Title }}</a>
+        <p class="section-item__meta">{{ .Date.Format "Jan 2, 2006" }}</p>
+      </article>
+    {{ end }}
+  </div>
+</section>
+{{ end }}
diff --git a/themes/clean-hugo/layouts/_default/packages-list.html b/themes/clean-hugo/layouts/_default/packages-list.html
new file mode 100644
index 00000000..8cd72c49
--- /dev/null
+++ b/themes/clean-hugo/layouts/_default/packages-list.html
@@ -0,0 +1,69 @@
+{{ define "main" }}
+
+{{ $pkgStats := partial "calculate-package-stats.html" . }}
+
+{{ partial "hero.html" . }}
+
+{{ $stats := slice
+    (printf "**%d** Packages Accepted" $pkgStats.total)
+    (printf "**%d** Published in JOSS" $pkgStats.joss)
+    (printf "**%d** Currently Active" $pkgStats.active)
+    (printf "**%d** Unique Maintainers" $pkgStats.maintainers)
+}}
+{{ partial "metrics-bar-render.html" (dict "stats" $stats) }}
+
+<div class="packages-page__content">
+  <div class="container">
+    {{ .Content }}
+  </div>
+</div>
+
+{{ if .Site.Data.packages }}
+<script>window.pyOpenSciPackages = {{ .Site.Data.packages | jsonify | safeJS }};</script>
+<div x-data="packageFilter()" x-init="initPackages(window.pyOpenSciPackages)">
+
+  <div class="packages-page__partner-nav">
+    <div class="container">
+      <a href="/packages/astropy/" class="partner-button partner-button--astropy">
+        <img src="https://img.shields.io/badge/Affiliated-Astropy-orange.svg?style=flat" alt="Astropy Affiliated" />
+        <span>View Astropy Packages</span>
+      </a>
+    </div>
+  </div>
+
+  <div class="packages-page__controls">
+    <div class="container">
+      {{ partial "packages/filters.html" . }}
+    </div>
+  </div>
+
+  <section class="packages-page__section">
+    <div class="container">
+      <h2>pyOpenSci Accepted Packages</h2>
+      {{ partial "packages/grid.html" (dict "activeOnly" true) }}
+    </div>
+  </section>
+
+  <section
+    class="blog-archives packages-page__archives"
+    aria-labelledby="archived-packages-heading"
+  >
+    <div class="container">
+      <div class="intro">
+        <h2 id="archived-packages-heading">Archived Packages</h2>
+        <p>
+          Archived packages are packages that have successfully completed peer review
+          but are no longer actively maintained.
+        </p>
+      </div>
+      {{ partial "packages/grid.html" (dict "activeOnly" false) }}
+    </div>
+  </section>
+</div>
+{{ else }}
+<div class="packages-page__empty container">
+  <p>No package data found. Add packages to <code>data/packages.yml</code> to display them here.</p>
+</div>
+{{ end }}
+
+{{ end }}
diff --git a/themes/clean-hugo/layouts/_default/single.html b/themes/clean-hugo/layouts/_default/single.html
new file mode 100644
index 00000000..fe7d0240
--- /dev/null
+++ b/themes/clean-hugo/layouts/_default/single.html
@@ -0,0 +1,16 @@
+{{ define "main" }}
+
+{{ partial "hero.html" . }}
+
+<article class="content-container">
+
+  {{ if and (not .Params.hero) (not .Params.hideDate) }}
+    {{/* Only show date at top for pages without hero sections */}}
+    <p class="content-date">{{ .Date.Format "January 2, 2006" }}</p>
+  {{ end }}
+  <div class="content-main">
+    {{ .Content }}
+    {{ partial "last-modified.html" . }}
+  </div>
+</article>
+{{ end }}
diff --git a/themes/clean-hugo/layouts/_default/splash.html b/themes/clean-hugo/layouts/_default/splash.html
new file mode 100644
index 00000000..0a49254a
--- /dev/null
+++ b/themes/clean-hugo/layouts/_default/splash.html
@@ -0,0 +1,9 @@
+{{ define "main" }}
+
+{{ partial "hero.html" . }}
+
+<div class="splash-page__content">
+  {{ .Content }}
+</div>
+
+{{ end }}
diff --git a/themes/clean-hugo/layouts/_default/taxonomy.html b/themes/clean-hugo/layouts/_default/taxonomy.html
new file mode 100644
index 00000000..d3544777
--- /dev/null
+++ b/themes/clean-hugo/layouts/_default/taxonomy.html
@@ -0,0 +1,15 @@
+{{ define "main" }}
+<section class="section-container">
+  <h1 class="section-title">{{ .Title | default "Topics" }}</h1>
+
+  <ul class="term-list">
+    {{ range $term, $data := .Data.Terms }}
+      <li class="term-item">
+        <a href="{{ $data.Page.Permalink }}">
+          {{ $term }} <span class="term-count">({{ $data.Count }})</span>
+        </a>
+      </li>
+    {{ end }}
+  </ul>
+</section>
+{{ end }}
diff --git a/themes/clean-hugo/layouts/_default/term.html b/themes/clean-hugo/layouts/_default/term.html
new file mode 100644
index 00000000..cd56b1ef
--- /dev/null
+++ b/themes/clean-hugo/layouts/_default/term.html
@@ -0,0 +1,15 @@
+{{ define "main" }}
+<section class="section-container">
+  <h1 class="section-title">{{ .Title }}</h1>
+  <p class="term-description">Posts tagged "{{ .Title }}"</p>
+
+  <div class="section-list">
+    {{ range .Pages }}
+      <article class="section-item">
+        <a href="{{ .Permalink }}">{{ .Title }}</a>
+        <p class="section-item__meta">{{ .Date.Format "Jan 2, 2006" }}</p>
+      </article>
+    {{ end }}
+  </div>
+</section>
+{{ end }}
diff --git a/themes/clean-hugo/layouts/blog/list.html b/themes/clean-hugo/layouts/blog/list.html
new file mode 100644
index 00000000..b1b0c1bc
--- /dev/null
+++ b/themes/clean-hugo/layouts/blog/list.html
@@ -0,0 +1,96 @@
+{{ define "main" }}
+{{ partial "section-hero.html" . }}
+
+<div class="blog-index" data-blog-filter-root>
+<section class="blog-grid">
+  <div class="container">
+
+    {{/* Get all blog posts, newest first */}}
+    {{ $allPosts := sort (where .Site.RegularPages "Type" "blog") "Date" "desc" }}
+
+    {{/* Separate recent posts from archive posts */}}
+    {{ $recentPosts := slice }}
+    {{ $archivePosts := slice }}
+    {{ $cutoffDate := time "2025-01-01" }}
+
+    {{ range $allPosts }}
+      {{ $isOld := le (.Date.Unix) ($cutoffDate.Unix) }}
+      {{ $hasNoImage := not .Params.image }}
+      {{ if and $isOld $hasNoImage }}
+        {{ $archivePosts = $archivePosts | append . }}
+      {{ else }}
+        {{ $recentPosts = $recentPosts | append . }}
+      {{ end }}
+    {{ end }}
+
+    {{/* Empty state - no posts */}}
+    {{ if eq (len $allPosts) 0 }}
+    <div class="blog-grid__empty">
+      <p class="blog-grid__empty-message">No blog posts yet. Check back soon!</p>
+    </div>
+    {{ else }}
+
+    {{/* Featured post is always the most recent (first post from recent posts) */}}
+    {{ $featuredPost := false }}
+    {{ $sidebarPosts := slice }}
+    {{ $remainingPosts := slice }}
+
+    {{ if gt (len $recentPosts) 0 }}
+      {{ $featuredPost = index $recentPosts 0 }}
+      {{ $sidebarCount := .Site.Params.blog.sidebar_count | default 2 }}
+      {{ $skipCount := add $sidebarCount 1 }}
+      {{ if gt (len $recentPosts) 1 }}
+        {{ $sidebarPosts = first $sidebarCount (after 1 $recentPosts) }}
+      {{ end }}
+      {{ if gt (len $recentPosts) $skipCount }}
+        {{ $remainingPosts = after $skipCount $recentPosts }}
+      {{ end }}
+    {{ end }}
+
+    {{/* Topic filters — fixed order from data/blog_topics.yml */}}
+    {{ $topicOrder := slice "community" "learn" "software" "updates" }}
+    {{ $topicsData := .Site.Data.blog_topics | default dict }}
+    <div class="filter-row blog-grid__filters" role="group" aria-label="Filter blog posts by topic">
+      <button type="button" class="filter-btn" data-category="all" aria-pressed="true" aria-label="View all blog posts">View All</button>
+      {{ range $topicOrder }}
+        {{ $entry := index $topicsData . }}
+        {{ if $entry }}
+        <button type="button" class="filter-btn" data-category="{{ . }}" aria-pressed="false" aria-label="Filter by {{ $entry.label }} posts">{{ $entry.label }}</button>
+        {{ end }}
+      {{ end }}
+    </div>
+
+    {{/* Featured section: 1 large post + sidebar posts */}}
+    {{ if or $featuredPost (gt (len $sidebarPosts) 0) }}
+    <div class="blog-grid__featured">
+      {{ if $featuredPost }}
+        {{ partial "blog-card.html" (dict "." $featuredPost "modifier" "card--blog--featured" "showExcerpt" true) }}
+      {{ end }}
+
+      <div class="blog-grid__sidebar">
+        {{ range $sidebarPosts }}
+          {{ partial "blog-card.html" (dict "." . "modifier" "card--blog--sidebar" "showExcerpt" false) }}
+        {{ end }}
+      </div>
+    </div>
+    {{ end }}
+
+    {{/* Remaining posts grid */}}
+    {{ if gt (len $remainingPosts) 0 }}
+    <div class="blog-grid__posts">
+      {{ range $index, $post := $remainingPosts }}
+        {{ partial "blog-card.html" (dict "." $post "modifier" "card--blog--grid" "showExcerpt" true "colorIndex" (mod $index 4)) }}
+      {{ end }}
+    </div>
+    {{ end }}
+
+    {{ end }}
+  </div>
+</section>
+
+{{/* Archives section for old posts without images */}}
+{{ partial "blog-archives.html" $archivePosts }}
+</div>
+
+<script src="{{ "js/blog-filter.js" | relURL }}"></script>
+{{ end }}
diff --git a/themes/clean-hugo/layouts/blog/single.html b/themes/clean-hugo/layouts/blog/single.html
new file mode 100644
index 00000000..64972720
--- /dev/null
+++ b/themes/clean-hugo/layouts/blog/single.html
@@ -0,0 +1,72 @@
+{{ define "main" }}
+  <!-- Hero Banner with Title Overlay -->
+<header class="blog-post__header"{{ if not .Params.image }}{{/* Get gradient colors based on category when no image */}}
+    {{ $gradientColors := dict
+      "Open Education" (dict "from" "#71B3B5" "to" "#2E6060")
+      "Open Science" (dict "from" "#EDB88B" "to" "#D6A570")
+      "Community" (dict "from" "#AC87A0" "to" "#8B6A8F")
+      "Science Communication" (dict "from" "#71B3B5" "to" "#5A9A9C")
+    }}
+    {{ $postCategory := .Params.category }}
+    {{ $defaultColors := dict "from" "#71B3B5" "to" "#2E6060" }}
+    {{ $colors := $defaultColors }}
+    {{ if $postCategory }}
+      {{ $colors = index $gradientColors $postCategory | default $defaultColors }}
+    {{ end }}
+    style="background: linear-gradient(135deg, {{ $colors.from }} 0%, {{ $colors.to }} 100%);"
+  {{ end }}>
+    {{ $img := partial "get-image.html" (dict "image" .Params.image "fallbackAlt" .Title "page" .) }}
+    {{ if $img.exists }}
+    <img src="{{ $img.src }}" alt="{{ $img.alt }}" />
+    {{ end }}
+
+    <!-- Dark gradient overlay -->
+    <div></div>
+
+    <!-- Title and metadata overlaid on image -->
+    <div>
+      <h1>{{ .Title }}</h1>
+      <p>{{ .Date.Format "Jan 2, 2006" }}{{ with partial "blog-topic.html" . }}{{ with .label }} • {{ . }}{{ end }}{{ end }}</p>
+    </div>
+
+    <!-- Photo credit in bottom right -->
+    {{ if $img.credit }}
+    <div>
+      {{ $img.credit }}
+    </div>
+    {{ end }}
+  </header>
+<article class="content-container">
+
+
+
+  <!-- Excerpt below banner -->
+  {{ with .Params.excerpt }}
+  <div class="blog-post__excerpt">
+    <p>{{ . | markdownify }}</p>
+  </div>
+  {{ end }}
+
+  <!-- Main content -->
+  <div class="content-main">
+    {{ .Content }}
+
+    {{ partial "learn-more.html" . }}
+  </div>
+
+  <!-- Tags footer -->
+  <footer class="blog-post__tags">
+    {{ with .Params.tags }}Tags: {{ range $i, $t := . }}{{ if $i }}, {{ end }}<a href="{{ "/tags/" | relURL }}{{ urlize $t }}">{{ $t }}</a>{{ end }}{{ end }}
+  </footer>
+
+  <!-- Last modified date -->
+  {{ partial "last-modified.html" . }}
+</article>
+{{ end }}
+
+{{ define "scripts" }}
+  {{/* Load GLightbox only if masonry shortcode was used */}}
+  {{ if .Page.Scratch.Get "hasGallery" }}
+    {{ partial "glightbox-scripts.html" . }}
+  {{ end }}
+{{ end }}
diff --git a/themes/clean-hugo/layouts/events/list.html b/themes/clean-hugo/layouts/events/list.html
new file mode 100644
index 00000000..094a49a3
--- /dev/null
+++ b/themes/clean-hugo/layouts/events/list.html
@@ -0,0 +1,30 @@
+{{ define "main" }}
+{{ partial "section-hero.html" . }}
+
+{{ $today := now.Format "2006-01-02" }}
+{{ $past := slice }}
+{{ range .Pages }}
+  {{ $e := .Params.event }}
+  {{ if and $e $e.start_date }}
+    {{ $start := $e.start_date }}
+    {{ $end := $e.end_date | default $e.start_date }}
+    {{ if gt $today $end }}
+      {{ $past = $past | append . }}
+    {{ end }}
+  {{ end }}
+{{ end }}
+
+{{ partial "events-upcoming.html" (dict "context" . "pages" .Pages) }}
+
+{{ with .Content }}
+  <section class="events-list">
+    <div class="container">
+      <div class="events-list__types prose-content">
+        {{ . }}
+      </div>
+    </div>
+  </section>
+{{ end }}
+
+{{ partial "events-past-archives.html" (sort $past "Params.event.start_date" "desc") }}
+{{ end }}
diff --git a/themes/clean-hugo/layouts/events/single.html b/themes/clean-hugo/layouts/events/single.html
new file mode 100644
index 00000000..f98c120d
--- /dev/null
+++ b/themes/clean-hugo/layouts/events/single.html
@@ -0,0 +1,59 @@
+{{ define "main" }}
+{{ $e := .Params.event }}
+{{ $dateLine := "" }}
+{{ if $e }}
+  {{ $dateLine = partial "event-date-display.html" (dict "event" $e) }}
+  {{ $loc := $e.location_name | default $e.location }}
+  {{ with $loc }}
+    {{ $dateLine = printf "%s · %s" $dateLine . }}
+  {{ end }}
+{{ end }}
+{{ $gradientFrom := "#71B3B5" }}
+{{ $gradientTo := "#2E6060" }}
+{{ if and $e (not .Params.image) }}
+  {{ $t := lower ($e.event_type | default "") }}
+  {{ if eq $t "workshop" }}
+    {{ $gradientFrom = "#71B3B5" }}{{ $gradientTo = "#2E6060" }}
+  {{ else if eq $t "community" }}
+    {{ $gradientFrom = "#AC87A0" }}{{ $gradientTo = "#8B6A8F" }}
+  {{ end }}
+{{ end }}
+<header class="blog-post__header"{{ if not .Params.image }}
+    style="background: linear-gradient(135deg, {{ $gradientFrom }} 0%, {{ $gradientTo }} 100%);"
+  {{ end }}>
+    {{ $img := partial "get-image.html" (dict "image" .Params.image "fallbackAlt" .Title "page" .) }}
+    {{ if $img.exists }}
+    <img src="{{ $img.src }}" alt="{{ $img.alt }}" />
+    {{ end }}
+    <div></div>
+    <div>
+      <h1>{{ .Title }}</h1>
+      {{ if $dateLine }}<p>{{ $dateLine }}</p>{{ end }}
+    </div>
+    {{ if $img.credit }}
+    <div>{{ $img.credit }}</div>
+    {{ end }}
+  </header>
+<article class="content-container">
+  {{ with .Params.excerpt }}
+  <div class="blog-post__excerpt">
+    <p>{{ . | markdownify }}</p>
+  </div>
+  {{ end }}
+  <div class="content-main">
+    {{ .Content }}
+    {{ partial "event-instructors.html" . }}
+    {{ partial "learn-more.html" . }}
+  </div>
+  <footer class="blog-post__tags">
+    {{ with .Params.tags }}Tags: {{ range $i, $t := . }}{{ if $i }}, {{ end }}<a href="{{ "/tags/" | relURL }}{{ urlize $t }}">{{ $t }}</a>{{ end }}{{ end }}
+  </footer>
+  {{ partial "last-modified.html" . }}
+</article>
+{{ end }}
+
+{{ define "scripts" }}
+  {{ if .Page.Scratch.Get "hasGallery" }}
+    {{ partial "glightbox-scripts.html" . }}
+  {{ end }}
+{{ end }}
diff --git a/themes/clean-hugo/layouts/gallery/list.html b/themes/clean-hugo/layouts/gallery/list.html
new file mode 100644
index 00000000..d3a0972d
--- /dev/null
+++ b/themes/clean-hugo/layouts/gallery/list.html
@@ -0,0 +1,37 @@
+{{ define "main" }}
+  {{ partial "hero.html" . }}
+
+  <section class="gallery-list-wrapper">
+    <!-- Build unique group list from pages -->
+    {{ $seen := dict }}
+    {{ range .Pages.ByWeight.Reverse }}
+      {{ with .Params.groups }}
+        {{ range . }}
+          {{ if not (index $seen .) }}
+            {{ $seen = merge $seen (dict . true) }}
+          {{ end }}
+        {{ end }}
+      {{ else }}
+        {{ with .Params.group }}
+          {{ if not (index $seen .) }}
+            {{ $seen = merge $seen (dict . true) }}
+          {{ end }}
+        {{ end }}
+      {{ end }}
+    {{ end }}
+
+    <!-- Filter buttons -->
+    <div class="filter-row" role="tablist" aria-label="Filter gallery by group">
+      <button class="filter-btn" data-filter="all" aria-pressed="true">All</button>
+      {{ range $k, $v := $seen }}
+        <button class="filter-btn" data-filter="{{ $k }}" aria-pressed="false">{{ humanize $k }}</button>
+      {{ end }}
+    </div>
+
+    <!-- Gallery -->
+    {{ partial "gallery-grid.html" (dict "Pages" .Pages.ByWeight.Reverse "Title" .Title "Cols" 3) }}
+  </section>
+
+  <!-- Client-side filter -->
+  {{ partial "gallery-filter.html" (dict "cardSelector" ".gallery-card" "ariaLabel" "Filter gallery by group") }}
+{{ end }}
diff --git a/themes/clean-hugo/layouts/gallery/single.html b/themes/clean-hugo/layouts/gallery/single.html
new file mode 100644
index 00000000..e28c4c94
--- /dev/null
+++ b/themes/clean-hugo/layouts/gallery/single.html
@@ -0,0 +1,36 @@
+{{/* Layout for a single gallery item page */}}
+{{ define "main" }}
+  {{ partial "hero.html" . }}
+
+  <article class="gallery-content">
+    <div class="gallery-description prose">
+      {{ .Content }}
+    </div>
+
+    <section class="gallery-images">
+      <h2>Gallery</h2>
+      <div class="gallery-masonry">
+        {{ $images := .Resources.ByType "image" }}
+        {{ range $images }}
+          {{ $filename := .Name | replaceRE "\\.[^.]+$" "" | replaceRE "-" " " | title }}
+          {{ $caption := printf "%s · %s" $.Title $filename }}
+          <figure>
+            <a href="{{ .RelPermalink }}"
+                class="glightbox"
+                data-gallery="gallery-images"
+                data-glightbox="title: {{ $caption }};">
+              <img src="{{ .RelPermalink }}" alt="{{ or .Title $.Title }}" loading="lazy" style="image-orientation: from-image;">
+            </a>
+            <p class="gallery-caption">
+                {{ $caption }}
+            </p>
+          </figure>
+        {{ end }}
+      </div>
+    </section>
+  </article>
+{{ end }}
+
+{{ define "scripts" }}
+  {{ partial "glightbox-scripts.html" . }}
+{{ end }}
diff --git a/themes/clean-hugo/layouts/packages/list.html b/themes/clean-hugo/layouts/packages/list.html
new file mode 100644
index 00000000..ae330ae1
--- /dev/null
+++ b/themes/clean-hugo/layouts/packages/list.html
@@ -0,0 +1,78 @@
+{{ define "main" }}
+
+{{/* Calculate package metrics using shared partial */}}
+{{ $pkgStats := partial "calculate-package-stats.html" . }}
+
+{{/* Hero section - similar to splash layout */}}
+{{ partial "hero.html" . }}
+
+{{/* Metrics Bar - render with calculated stats TODO Move this to a separate calculation step in the actually website vs here in the template*/}}
+{{ $stats := slice
+    (printf "**%d** Packages Accepted" $pkgStats.total)
+    (printf "**%d** Published in JOSS" $pkgStats.joss)
+    (printf "**%d** Currently Active" $pkgStats.active)
+    (printf "**%d** Unique Maintainers" $pkgStats.maintainers)
+}}
+{{ partial "metrics-bar-render.html" (dict "stats" $stats) }}
+
+{{/* Page content with metrics and intro text - centered with max-width */}}
+<div class="packages-page__content">
+  <div class="container">
+    {{ .Content }}
+  </div>
+</div>
+
+{{/* Packages listing - full width with inner max-width containers */}}
+{{ if .Site.Data.packages }}
+<script>window.pyOpenSciPackages = {{ .Site.Data.packages | jsonify | safeJS }};</script>
+<div x-data="packageFilter()" x-init="initPackages(window.pyOpenSciPackages)">
+
+  {{/* Partner Button - above filters */}}
+  <div class="packages-page__partner-nav">
+    <div class="container">
+      <a href="/packages/astropy/" class="partner-button partner-button--astropy">
+        <img src="https://img.shields.io/badge/Affiliated-Astropy-orange.svg?style=flat" alt="Astropy Affiliated" />
+        <span>View Astropy Packages</span>
+      </a>
+    </div>
+  </div>
+
+  {{/* Filters and Search - contained width */}}
+  <div class="packages-page__controls">
+    <div class="container">
+      {{ partial "packages/filters.html" . }}
+    </div>
+  </div>
+
+  {{/* Active Packages */}}
+  <section class="packages-page__section">
+    <div class="container">
+      <h2>pyOpenSci Accepted Packages</h2>
+      {{ partial "packages/grid.html" (dict "activeOnly" true) }}
+    </div>
+  </section>
+
+  {{/* Archived Packages — full-bleed band (same as blog archives) */}}
+  <section
+    class="blog-archives packages-page__archives"
+    aria-labelledby="archived-packages-heading"
+  >
+    <div class="container">
+      <div class="intro">
+        <h2 id="archived-packages-heading">Archived Packages</h2>
+        <p>
+          Archived packages are packages that have successfully completed peer review
+          but are no longer actively maintained.
+        </p>
+      </div>
+      {{ partial "packages/grid.html" (dict "activeOnly" false) }}
+    </div>
+  </section>
+</div>
+{{ else }}
+<div class="packages-page__empty container">
+  <p>No package data found. Add packages to <code>data/packages.yml</code> to display them here.</p>
+</div>
+{{ end }}
+
+{{ end }}
diff --git a/themes/clean-hugo/layouts/partials/_events.scss b/themes/clean-hugo/layouts/partials/_events.scss
new file mode 100644
index 00000000..c85a03d4
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/_events.scss
@@ -0,0 +1,401 @@
+/* Events listing (/events/) */
+.events-list {
+  padding: 2rem 0 4rem;
+
+  .container {
+    max-width: $container-max-width;
+    margin: 0 auto;
+    padding: 0 $fluid-container-padding;
+  }
+}
+
+.blog-hero .events-list__intro {
+  color: rgba(255, 255, 255, 0.92);
+  font-size: 1.125rem;
+  line-height: 1.5;
+  max-width: 42rem;
+  margin: 0.5rem 0 0;
+}
+
+/* Small caps section label above upcoming cards */
+.events-list__kicker {
+  font-family: $font-family-body;
+  font-size: 0.75rem;
+  font-weight: 600;
+  letter-spacing: 0.14em;
+  text-transform: uppercase;
+  color: var(--color-gray-600);
+  margin: 0 0 1rem;
+}
+
+.events-list__kicker-amp {
+  letter-spacing: 0.08em;
+}
+
+.events-list__heading {
+  margin-top: 2.5rem;
+  margin-bottom: 1.25rem;
+  font-size: 1.75rem;
+
+  &:first-of-type {
+    margin-top: 0;
+  }
+}
+
+/* Upcoming/live: flexible grid for many events */
+.events-list__featured {
+  display: grid;
+  gap: 1.25rem;
+  grid-template-columns: repeat(auto-fill, minmax(16rem, 1fr));
+
+  @media (min-width: $breakpoint-lg) {
+    gap: 1.5rem;
+  }
+}
+
+.events-list__empty {
+  color: var(--color-gray-700);
+  margin-bottom: 2rem;
+}
+
+.events-list__types {
+  margin-top: 3rem;
+  margin-bottom: 1rem;
+  max-width: 65ch;
+}
+
+/* Past events use shared .blog-archives + .highlight-grid from _blog.scss */
+.events-past-archives {
+  margin-top: 0;
+}
+
+/* Event type pill — colors from hugo.toml CSS variables */
+.event-card__type {
+  display: inline-flex;
+  align-items: center;
+  font-size: 0.75rem;
+  font-weight: 600;
+  padding: 0.3rem 0.7rem;
+  border-radius: 9999px;
+  line-height: 1.2;
+  white-space: nowrap;
+  max-width: 100%;
+}
+
+.event-card__type--training {
+  background-color: var(--color-event-label-training-bg, var(--color-primary-light));
+  color: var(--color-event-label-training-fg, var(--color-primary-dark));
+}
+
+.event-card__type--sprint {
+  background-color: var(--color-event-label-sprint-bg, var(--color-accent-light));
+  color: var(--color-event-label-sprint-fg, var(--color-gray-900));
+}
+
+.event-card__type--community {
+  background-color: var(--color-event-label-community-bg, var(--color-secondary));
+  color: var(--color-event-label-community-fg, var(--color-gray-900));
+}
+
+.event-card__type--talk {
+  background-color: var(--color-event-label-talk-bg, var(--color-admonition-note, #cae4e4));
+  color: var(--color-event-label-talk-fg, var(--color-primary-dark));
+}
+
+.event-card__type--default {
+  background-color: var(--color-gray-200);
+  color: var(--color-gray-700);
+}
+
+/* Featured (upcoming/live) cards — white surface, mock-inspired layout */
+.event-card--featured {
+  > a {
+    display: flex;
+    flex-direction: column;
+    height: 100%;
+    min-height: 12rem;
+    text-decoration: none;
+    color: inherit;
+    border-radius: $radius-md;
+    background-color: var(--color-white);
+    box-shadow: $shadow-sm;
+    border: 1px solid var(--color-gray-200);
+    padding: 1.25rem 1.35rem;
+    transition: box-shadow $transition-base ease-in-out, transform $transition-base ease-in-out;
+
+    &:hover {
+      box-shadow: $shadow-lg;
+      transform: translateY(-2px);
+
+      .event-card__cta {
+        color: var(--color-link-hover);
+      }
+    }
+  }
+}
+
+.event-card__featured-inner {
+  display: flex;
+  flex-direction: column;
+  height: 100%;
+  gap: 0.65rem;
+  min-height: 0;
+}
+
+.event-card__featured-top {
+  display: flex;
+  align-items: flex-start;
+  justify-content: space-between;
+  gap: 0.75rem;
+}
+
+.event-card__date-badge {
+  flex-shrink: 0;
+  min-width: 3.25rem;
+  max-width: 8rem;
+  padding: 0.45rem 0.5rem;
+  border-radius: $radius-sm;
+  background-color: var(--color-event-date-badge-bg, var(--color-accent));
+  color: var(--color-event-date-badge-fg, var(--color-white));
+  text-align: center;
+  display: flex;
+  flex-direction: column;
+  align-items: center;
+  justify-content: center;
+  line-height: 1.15;
+}
+
+.event-card__date-badge-primary {
+  font-size: 1.0625rem;
+  font-weight: 800;
+  letter-spacing: 0.02em;
+}
+
+.event-card__date-badge-secondary {
+  font-size: 0.65rem;
+  font-weight: 700;
+  letter-spacing: 0.08em;
+}
+
+.event-card__date-badge-year {
+  font-size: 0.6rem;
+  font-weight: 600;
+  margin-top: 0.15rem;
+  opacity: 0.95;
+}
+
+.event-card--featured .event-card__title {
+  font-size: 1.25rem;
+  font-weight: 700;
+  line-height: 1.25;
+  margin: 0;
+  color: var(--color-gray-900);
+}
+
+.event-card__meta {
+  margin: 0;
+  font-size: 0.9375rem;
+  line-height: 1.45;
+  color: var(--color-gray-600);
+}
+
+.event-card__cta {
+  margin-top: auto;
+  padding-top: 0.35rem;
+  font-size: 0.875rem;
+  font-weight: 600;
+  color: var(--color-link);
+}
+
+/* Compact past cards (horizontal thumb) */
+.event-card:not(.event-card--featured) {
+  > a {
+    display: block;
+    height: 100%;
+    text-decoration: none;
+    color: inherit;
+    border-radius: $radius-md;
+    overflow: hidden;
+    background-color: var(--color-white);
+    box-shadow: $shadow-sm;
+    border: 1px solid var(--color-gray-200);
+    transition: box-shadow $transition-base ease-in-out, transform $transition-base ease-in-out;
+
+    &:hover {
+      box-shadow: $shadow-lg;
+      transform: translateY(-2px);
+    }
+  }
+}
+
+.event-card__content {
+  display: flex;
+  flex-direction: row;
+  min-height: 0;
+}
+
+.event-card__date {
+  position: relative;
+  flex: 0 0 6.5rem;
+  min-height: 7rem;
+  overflow: hidden;
+}
+
+.event-card__date-background {
+  position: absolute;
+  inset: 0;
+  background-size: cover;
+  background-position: center;
+
+  &--default {
+    background: linear-gradient(145deg, var(--color-primary) 0%, var(--color-primary-dark) 100%);
+  }
+}
+
+.event-card__date-text {
+  position: relative;
+  z-index: 1;
+  display: flex;
+  flex-direction: column;
+  align-items: center;
+  justify-content: center;
+  height: 100%;
+  padding: 0.5rem;
+  color: var(--color-white);
+  text-shadow: 0 1px 2px rgba(0, 0, 0, 0.35);
+  font-weight: 700;
+  line-height: 1.15;
+  text-align: center;
+
+  span {
+    font-size: 0.75rem;
+    font-weight: 600;
+    letter-spacing: 0.02em;
+  }
+
+  span:first-child {
+    font-size: 1.25rem;
+    font-weight: 800;
+  }
+
+  span:nth-child(3) {
+    font-size: 0.7rem;
+    opacity: 0.95;
+  }
+}
+
+.event-card__details {
+  flex: 1;
+  padding: 1rem 1.125rem;
+  display: flex;
+  flex-direction: column;
+  gap: 0.5rem;
+  min-width: 0;
+}
+
+.event-card__type--inline {
+  align-self: flex-start;
+  margin-bottom: 0.15rem;
+}
+
+.event-card__title {
+  font-size: 1.125rem;
+  font-weight: 600;
+  line-height: 1.3;
+  margin: 0;
+  color: var(--color-gray-900);
+}
+
+.event-card__details p {
+  margin: 0;
+  font-size: 0.875rem;
+  line-height: 1.5;
+  color: var(--color-gray-600);
+}
+
+.event-card__button {
+  margin-top: auto;
+  font-size: 0.8125rem;
+  font-weight: 600;
+  color: var(--color-primary);
+}
+
+/* Event detail: instructors (optional front matter) */
+.event-instructors {
+  margin-top: 3rem;
+  padding-top: 2rem;
+  border-top: 1px solid var(--color-gray-200);
+}
+
+.event-instructors__heading {
+  font-size: 1.5rem;
+  margin-bottom: 1.25rem;
+}
+
+.event-instructors__grid {
+  list-style: none;
+  margin: 0;
+  padding: 0;
+  display: grid;
+  gap: 1.5rem;
+  grid-template-columns: 1fr;
+
+  @media (min-width: $breakpoint-md) {
+    grid-template-columns: repeat(2, 1fr);
+  }
+}
+
+.event-instructors__card {
+  display: flex;
+  gap: 1rem;
+  align-items: flex-start;
+  padding: 1rem;
+  border-radius: $radius-md;
+  border: 1px solid var(--color-gray-200);
+  background-color: var(--color-white);
+  box-shadow: $shadow-sm;
+}
+
+.event-instructors__avatar {
+  flex-shrink: 0;
+  width: 5rem;
+  height: 5rem;
+  border-radius: 9999px;
+  object-fit: cover;
+}
+
+.event-instructors__name {
+  margin: 0 0 0.5rem;
+  font-size: 1.125rem;
+}
+
+.event-instructors__bio {
+  margin: 0;
+  font-size: 0.9375rem;
+  line-height: 1.5;
+  color: var(--color-gray-700);
+}
+
+.event-card--compact {
+  .event-card__date {
+    flex-basis: 4.5rem;
+    min-height: 5rem;
+  }
+
+  .event-card__date-text span:first-child {
+    font-size: 1rem;
+  }
+
+  .event-card__details {
+    padding: 0.75rem 0.875rem;
+  }
+
+  .event-card__title {
+    font-size: 0.9375rem;
+  }
+
+  .event-card__type {
+    font-size: 0.65rem;
+    padding: 0.2rem 0.5rem;
+  }
+}
diff --git a/themes/clean-hugo/layouts/partials/blog-archives.html b/themes/clean-hugo/layouts/partials/blog-archives.html
new file mode 100644
index 00000000..b80ef858
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/blog-archives.html
@@ -0,0 +1,45 @@
+{{/*
+  Blog Archives Partial
+
+  Parameters:
+  - "." (context): Array of archive posts
+*/}}
+{{ $archivePosts := . }}
+
+{{ if gt (len $archivePosts) 0 }}
+<section class="blog-archives">
+  <div class="container">
+    <div class="intro">
+      <h2>From the Archives</h2>
+    </div>
+
+    <div class="highlight-grid">
+      {{ range $archivePosts }}
+        {{ $topic := partial "blog-topic.html" . }}
+        <article class="listing-card listing-card--blog-archive listing-card--density-default blog-filter-item" data-category="{{ $topic.slug }}">
+          <div class="meta">
+            <time datetime="{{ .Date.Format "2006-01-02" }}">{{ .Date.Format "Jan 2, 2006" }}</time>
+            {{ if $topic.label }}
+              <span class="category">{{ $topic.label }}</span>
+            {{ end }}
+          </div>
+
+          <div class="content">
+            <h3>
+              <a href="{{ .Permalink }}">{{ .Title }}</a>
+            </h3>
+
+            <p class="excerpt">
+              {{ partial "blog-excerpt.html" (dict "." . "length" 200) }}
+            </p>
+
+            <a href="{{ .Permalink }}" class="read-more">
+              Read more <i class="fas fa-arrow-right"></i>
+            </a>
+          </div>
+        </article>
+      {{ end }}
+    </div>
+  </div>
+</section>
+{{ end }}
diff --git a/themes/clean-hugo/layouts/partials/blog-card.html b/themes/clean-hugo/layouts/partials/blog-card.html
new file mode 100644
index 00000000..9b9e0985
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/blog-card.html
@@ -0,0 +1,79 @@
+{{/*
+  Blog Card Partial
+
+  Parameters:
+  - "." (context): The blog post page object (passed as "." in dict)
+  - "modifier" (string): card--blog--featured | card--blog--sidebar | card--blog--grid
+  - "showExcerpt" (bool): Whether to show excerpt
+*/}}
+{{ $post := index . "." }}
+{{ $modifier := .modifier | default "" }}
+{{ $showExcerpt := .showExcerpt | default false }}
+{{ $topic := partial "blog-topic.html" $post }}
+{{ $excerptLength := $post.Site.Params.blog.excerpt_length | default 200 }}
+{{ $isGrid := eq $modifier "card--blog--grid" }}
+{{ $colorIndex := .colorIndex | default 0 }}
+
+<article class="card card--blog {{ $modifier }} blog-filter-item" data-category="{{ $topic.slug }}">
+  <a href="{{ $post.Permalink }}" class="card--blog__link">
+    {{ if $isGrid }}
+    {{/* Grid cards: banner image + scrim, white title + date (Jekyll banner_only) */}}
+    {{ $img := partial "get-image.html" (dict "image" $post.Params.image "fallbackAlt" $post.Title "page" $post) }}
+    <div class="card--blog__media">
+      {{ if $img.exists }}
+      <img
+        class="card--blog__media-bg"
+        src="{{ $img.src }}"
+        alt=""
+        aria-hidden="true"
+        loading="lazy"
+      />
+      {{ else }}
+      <div
+        class="card--blog__media-fallback card--blog__media-fallback--{{ $colorIndex }}"
+        aria-hidden="true"
+      ></div>
+      {{ end }}
+      <div class="card--blog__media-scrim" aria-hidden="true"></div>
+      <div class="card--blog__media-text">
+        <h2>{{ $post.Title }}</h2>
+        <time datetime="{{ $post.Date.Format "2006-01-02" }}">{{ $post.Date.Format "Jan 2, 2006" }}</time>
+      </div>
+    </div>
+    <div class="card--blog__body">
+      {{ if $topic.label }}
+        <span class="card--blog__badge">{{ $topic.label }}</span>
+      {{ end }}
+      {{ if $showExcerpt }}
+        <p class="card--blog__excerpt">
+          {{ partial "blog-excerpt.html" (dict "." $post "length" 130) }}
+        </p>
+      {{ end }}
+    </div>
+    {{ else }}
+    {{ $img := partial "get-image.html" (dict "image" $post.Params.image "fallbackAlt" $post.Title "page" $post) }}
+    {{ if $img.exists }}
+    <figure class="card--blog__image">
+      <img src="{{ $img.src }}" alt="{{ $img.alt }}" loading="lazy" />
+    </figure>
+    {{ else }}
+    <div class="card--blog__image-placeholder card--blog__media-fallback--{{ $colorIndex }}"></div>
+    {{ end }}
+    <div class="card--blog__content">
+      {{ if $topic.label }}
+        <span class="card--blog__badge">{{ $topic.label | upper }}</span>
+      {{ end }}
+      <h2>{{ $post.Title }}</h2>
+      <time datetime="{{ $post.Date.Format "2006-01-02" }}">{{ $post.Date.Format "Jan 2, 2006" }}</time>
+      {{ if $post.Params.show_author }}
+        <p class="card--blog__author">{{ $post.Params.author | default $post.Site.Params.author }}</p>
+      {{ end }}
+      {{ if $showExcerpt }}
+      <p class="card--blog__excerpt">
+        {{ partial "blog-excerpt.html" (dict "." $post "length" $excerptLength) }}
+      </p>
+      {{ end }}
+    </div>
+    {{ end }}
+  </a>
+</article>
diff --git a/themes/clean-hugo/layouts/partials/blog-excerpt.html b/themes/clean-hugo/layouts/partials/blog-excerpt.html
new file mode 100644
index 00000000..8fb9c2c7
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/blog-excerpt.html
@@ -0,0 +1,17 @@
+{{/*
+  Blog Excerpt Partial
+
+  Parameters:
+  - "." (context): The blog post page object (passed as "." in dict)
+  - "length" (int): Character length for truncation (default: 200)
+*/}}
+{{ $post := index . "." }}
+{{ $length := .length | default 200 }}
+
+{{ if $post.Params.excerpt }}
+  {{ $post.Params.excerpt | markdownify | plainify | htmlUnescape | truncate $length }}
+{{ else if $post.Summary }}
+  {{ $post.Summary | plainify | htmlUnescape | truncate $length }}
+{{ else }}
+  {{ $post.Plain | htmlUnescape | truncate $length }}
+{{ end }}
diff --git a/themes/clean-hugo/layouts/partials/blog-list.html b/themes/clean-hugo/layouts/partials/blog-list.html
new file mode 100644
index 00000000..f7815890
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/blog-list.html
@@ -0,0 +1,42 @@
+<section class="blog-highlight">
+  <div class="container">
+    <div class="intro">
+      <h2>{{ .Params.blog_title | default "Recent Thoughts" }}</h2>
+    </div>
+
+    <div class="highlight-grid">
+      {{ $limit := .Params.blog_limit | default 3 }}
+      {{ range first $limit (where .Site.RegularPages "Type" "blog") }}
+        {{ $p := . }}
+        <article class="listing-card listing-card--on-dark listing-card--density-default">
+          <div class="meta">
+            <time datetime="{{ $p.Date.Format "2006-01-02" }}">{{ $p.Date.Format "Jan 2, 2006" }}</time>
+            {{ with $p.Params.category }}
+              <span class="category">{{ . }}</span>
+            {{ end }}
+          </div>
+
+          <div class="content">
+            <h3>
+              <a href="{{ $p.Permalink }}">{{ $p.Title }}</a>
+            </h3>
+
+            <p class="excerpt">
+              {{ if $p.Params.excerpt }}
+                {{ $p.Params.excerpt | markdownify | plainify | truncate 200 }}
+              {{ else if $p.Summary }}
+                {{ $p.Summary | plainify | truncate 200 }}
+              {{ else }}
+                {{ $p.Plain | truncate 200 }}
+              {{ end }}
+            </p>
+
+            <a href="{{ $p.Permalink }}" class="read-more">
+              Read more <i class="fas fa-arrow-right"></i>
+            </a>
+          </div>
+        </article>
+      {{ end }}
+    </div>
+  </div>
+</section>
diff --git a/themes/clean-hugo/layouts/partials/blog-topic.html b/themes/clean-hugo/layouts/partials/blog-topic.html
new file mode 100644
index 00000000..657b9832
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/blog-topic.html
@@ -0,0 +1,13 @@
+{{/*
+  Blog topic label lookup
+
+  Parameters:
+  - "." (context): Blog post page object
+
+  Returns dict: slug, label
+*/}}
+{{ $slug := .Params.blog_topic | default "community" }}
+{{ $topics := site.Data.blog_topics | default dict }}
+{{ $entry := index $topics $slug }}
+{{ $label := $entry.label | default ($slug | humanize) }}
+{{ return (dict "slug" $slug "label" $label) }}
diff --git a/themes/clean-hugo/layouts/partials/calculate-package-stats.html b/themes/clean-hugo/layouts/partials/calculate-package-stats.html
new file mode 100644
index 00000000..caf2a1d7
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/calculate-package-stats.html
@@ -0,0 +1,34 @@
+{{/*
+  Calculate Package Statistics
+  Returns a dict with: total, active, joss, maintainers
+  Usage: {{ $stats := partial "calculate-package-stats.html" . }}
+*/}}
+
+{{ $allMaintainers := slice }}
+{{ $activeCount := 0 }}
+{{ $jossCount := 0 }}
+{{ $totalCount := 0 }}
+
+{{ with .Site.Data.packages }}
+  {{ $totalCount = len . }}
+  {{ range . }}
+    {{ if .active }}
+      {{ $activeCount = add $activeCount 1 }}
+    {{ end }}
+    {{ if .joss }}
+      {{ $jossCount = add $jossCount 1 }}
+    {{ end }}
+    {{ range .all_current_maintainers }}
+      {{ $allMaintainers = $allMaintainers | append .github_username }}
+    {{ end }}
+  {{ end }}
+{{ end }}
+
+{{ $uniqueMaintainers := $allMaintainers | uniq }}
+
+{{ return (dict
+    "total" $totalCount
+    "active" $activeCount
+    "joss" $jossCount
+    "maintainers" (len $uniqueMaintainers)
+) }}
diff --git a/themes/clean-hugo/layouts/partials/cards.html b/themes/clean-hugo/layouts/partials/cards.html
new file mode 100644
index 00000000..8177424e
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/cards.html
@@ -0,0 +1,64 @@
+<!-- This partial renders a card component with an optional Font Awesome icon displayed to the left of the title. -->
+<!-- Reusable card partial.
+     - Use text_only: true in front matter to render a plain white, non-interactive text card.
+     - Otherwise renders the interactive highlight card (supports Font Awesome class strings or raw HTML icons).
+     - Optional image (map: src, alt) renders a 16:9 strip at the top; optional event_type shows the same pill as event cards.
+-->
+
+{{ $icon := .icon }}
+{{ $textOnly := false }}
+{{ if reflect.IsMap . }}
+  {{ if .text_only }}
+    {{ $textOnly = eq .text_only true }}
+  {{ end }}
+{{ end }}
+
+{{ if $textOnly }}
+<article class="card card--text">
+  <div>
+    <div>
+      <h2>
+        {{ .title }}
+      </h2>
+      {{ with .excerpt }}
+        <p>{{ . }}</p>
+      {{ end }}
+      {{ with .url }}
+        <div>
+          <a class="card__cta" href="{{ . }}">{{ $.cta | default "Learn more →" }}</a>
+        </div>
+      {{ end }}
+    </div>
+  </div>
+</article>
+{{ else }}
+{{ $page := index . "page" }}
+{{ $img := partial "get-image.html" (dict "image" .image "fallbackAlt" .title "page" $page) }}
+{{ $kind := lower (urlize (.event_type | default "")) }}
+{{ $typeLabels := dict "training" "Training" "sprint" "Sprint" "community" "Community event" "talk" "Talk" }}
+{{ $typeLabel := index $typeLabels $kind }}
+<article class="card {{ .modifier | default "card--highlight" }}{{ if $img.exists }} card--with-top-image{{ end }}">
+  {{ if $img.exists }}
+  <figure class="card__top-image">
+    <img src="{{ $img.src }}" alt="{{ $img.alt }}" loading="lazy" decoding="async" />
+  </figure>
+  {{ end }}
+  <div>
+    {{ if and $typeLabel (ne $kind "") }}
+      <span class="event-card__type event-card__type--{{ $kind }}">{{ $typeLabel }}</span>
+    {{ end }}
+    <h3>{{ if and $icon (in (printf "%s" $icon) "fa-") }}
+      <i class="card__icon {{ $icon }}" aria-hidden="true" title="{{ $.title }}"></i>
+    {{ else if and $icon (ne (printf "%s" $icon) "") }}
+      <div class="card__icon">{{ $icon | safeHTML }}</div>
+    {{ end }} {{ .title }}</h3>
+    {{ with .excerpt }}
+      <div>{{ . | markdownify }}</div>
+    {{ end }}
+  </div>
+
+  {{ with .url }}
+    <a class="card__cta" href="{{ . }}">{{ $.cta | default "Learn more →" }}</a>
+  {{ end }}
+</article>
+{{ end }}
diff --git a/themes/clean-hugo/layouts/partials/docs-menu-recursive.html b/themes/clean-hugo/layouts/partials/docs-menu-recursive.html
new file mode 100644
index 00000000..0427c8c0
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/docs-menu-recursive.html
@@ -0,0 +1,42 @@
+{{- /*
+  Recursive menu builder for documentation sidebar
+  Usage: {{ partial "docs-menu-recursive.html" (dict "pages" .Pages "context" .) }}
+
+  Parameters:
+  - pages: Collection of pages to render (typically .Pages.ByWeight)
+  - context: Current page context for active state detection
+  - level: Current nesting level (default: 1)
+*/ -}}
+
+{{- $pages := .pages -}}
+{{- $context := .context -}}
+{{- $currentPage := $context -}}
+{{- $level := .level | default 1 -}}
+
+{{- if $pages -}}
+<ul class="docs-menu__list docs-menu__list--level-{{ $level }}">
+  {{- range $pages -}}
+    {{- $isActive := eq $currentPage.RelPermalink .RelPermalink -}}
+    {{- $isAncestor := $currentPage.IsDescendant . -}}
+    {{- $hasChildren := gt (len .Pages) 0 -}}
+    {{- $shouldExpand := or $isActive $isAncestor -}}
+
+    <li class="docs-menu__item{{ if $isActive }} docs-menu__item--active{{ end }}{{ if $shouldExpand }} docs-menu__item--expanded{{ end }}">
+      <a href="{{ .RelPermalink }}" class="docs-menu__link{{ if $isActive }} docs-menu__link--active{{ end }}">
+        {{ .Title }}
+      </a>
+
+      {{- /* Include inline TOC only for the active page */ -}}
+      {{- if $isActive -}}
+        {{- partial "docs-toc.html" . -}}
+      {{- end -}}
+
+      {{- if $hasChildren -}}
+        {{- if $shouldExpand -}}
+          {{- partial "docs-menu-recursive.html" (dict "pages" (.Pages.ByWeight) "context" $currentPage "level" (add $level 1)) -}}
+        {{- end -}}
+      {{- end -}}
+    </li>
+  {{- end -}}
+</ul>
+{{- end -}}
diff --git a/themes/clean-hugo/layouts/partials/docs-sidebar.html b/themes/clean-hugo/layouts/partials/docs-sidebar.html
new file mode 100644
index 00000000..fd11864f
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/docs-sidebar.html
@@ -0,0 +1,59 @@
+{{- /*
+  Documentation sidebar with auto-generated menu
+
+  The sidebar now displays:
+  1. Auto-populated menu from documentation pages (by weight)
+  2. Inline TOC for the active page (nested under the active page link)
+
+  The inline TOC is populated by JavaScript after page load
+*/ -}}
+
+{{- $currentPage := . -}}
+{{- $docSection := .Site.GetPage "/documentation" -}}
+
+{{- if $docSection -}}
+<div class="docs-section-nav">
+  <h4 class="docs-section-title">Documentation</h4>
+
+  <ul class="docs-menu__list docs-menu__list--level-1">
+    {{- /* Add documentation home page with icon */ -}}
+    {{- $isActive := eq $currentPage.RelPermalink $docSection.RelPermalink -}}
+    <li class="docs-menu__item{{ if $isActive }} docs-menu__item--active{{ end }}">
+      <a href="{{ $docSection.RelPermalink }}" class="docs-menu__link{{ if $isActive }} docs-menu__link--active{{ end }}">
+        <i class="fas fa-home"></i> {{ $docSection.Title }}
+      </a>
+      {{- /* Include inline TOC only for the active page */ -}}
+      {{- if $isActive -}}
+        {{- partial "docs-toc.html" $docSection -}}
+      {{- end -}}
+    </li>
+
+    {{- /* Generate menu from documentation child pages */ -}}
+    {{- range $docSection.Pages.ByWeight -}}
+      {{- $isActive := eq $currentPage.RelPermalink .RelPermalink -}}
+      {{- $isAncestor := $currentPage.IsDescendant . -}}
+      {{- $hasChildren := gt (len .Pages) 0 -}}
+      {{- $shouldExpand := or $isActive $isAncestor -}}
+
+      <li class="docs-menu__item{{ if $isActive }} docs-menu__item--active{{ end }}{{ if $shouldExpand }} docs-menu__item--expanded{{ end }}">
+        <a href="{{ .RelPermalink }}" class="docs-menu__link{{ if $isActive }} docs-menu__link--active{{ end }}">
+          {{ .Title }}
+        </a>
+
+        {{- /* Include inline TOC only for the active page */ -}}
+        {{- if $isActive -}}
+          {{- partial "docs-toc.html" . -}}
+        {{- end -}}
+
+        {{- if $hasChildren -}}
+          {{- if $shouldExpand -}}
+            {{- partial "docs-menu-recursive.html" (dict "pages" (.Pages.ByWeight) "context" $currentPage "level" 2) -}}
+          {{- end -}}
+        {{- end -}}
+      </li>
+    {{- end -}}
+  </ul>
+</div>
+
+<div class="docs-nav-separator"></div>
+{{- end -}}
diff --git a/themes/clean-hugo/layouts/partials/docs-toc.html b/themes/clean-hugo/layouts/partials/docs-toc.html
new file mode 100644
index 00000000..5aff5eb0
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/docs-toc.html
@@ -0,0 +1,24 @@
+{{- /*
+  Inline Table of Contents for active documentation page
+  Usage: {{ partial "docs-toc.html" .Page }}
+
+  Generates an inline TOC from H2/H3 headings that appears under the active page
+  in the sidebar navigation. This is populated via JavaScript after page load.
+
+  Parameters:
+  - page: The page context to generate TOC for
+*/ -}}
+
+{{- $page := . -}}
+
+{{- /*
+  The TOC is a placeholder list that will be populated by JavaScript
+  JavaScript will:
+  1. Find all h2/h3 headings in the page content
+  2. Create anchor links to them
+  3. Insert them into the ul.toc-items list below
+*/ -}}
+
+<ul class="toc-items" data-page="{{ $page.RelPermalink }}">
+  {{- /* Placeholder: JavaScript will populate this */ -}}
+</ul>
diff --git a/themes/clean-hugo/layouts/partials/event-card.html b/themes/clean-hugo/layouts/partials/event-card.html
new file mode 100644
index 00000000..641e6706
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/event-card.html
@@ -0,0 +1,110 @@
+{{/*
+  Event card partial. Pass dict:
+    Page (required), compact (bool), variant (optional: "featured" for upcoming/live grid).
+  Front matter: params.event.start_date, optional end_date, location, conference, subtitle,
+  event_type: training | sprint | community | talk
+*/}}
+{{ $p := .Page }}
+{{ $compact := .compact | default false }}
+{{ $variant := .variant | default "" }}
+{{ $featured := and (not $compact) (eq $variant "featured") }}
+{{ $e := $p.Params.event }}
+{{ if not $e }}
+  {{ return }}
+{{ end }}
+{{ $img := partial "get-image.html" (dict "image" $p.Params.image "fallbackAlt" $p.Title "page" $p) }}
+{{ $rootClass := printf "%s%s" (cond $compact "event-card event-card--compact" (cond $featured "event-card event-card--featured" "event-card")) (cond (and $featured $img.exists) " event-card--with-image" "") }}
+{{ $kind := lower (urlize ($e.event_type | default "")) }}
+{{ $typeLabels := dict "training" "Training" "sprint" "Sprint" "community" "Community event" "talk" "Talk" }}
+{{ $typeLabel := index $typeLabels $kind }}
+{{ $start := time $e.start_date }}
+{{ $endStr := $e.end_date | default $e.start_date }}
+{{ $end := time $endStr }}
+{{ $subtitle := $e.subtitle | default "" }}
+{{ if not $subtitle }}
+  {{ with $e.conference }}
+    {{ $subtitle = printf "%s • %s" . ($e.location | default "") }}
+  {{ else }}
+    {{ $subtitle = $e.location | default "" }}
+  {{ end }}
+{{ end }}
+<article class="{{ $rootClass }}">
+  <a href="{{ $p.Permalink }}">
+    {{ if $featured }}
+      {{ if $img.exists }}
+        <figure class="event-card__featured-image">
+          <img src="{{ $img.src }}" alt="{{ $img.alt }}" loading="lazy" decoding="async" />
+        </figure>
+      {{ end }}
+      <div class="event-card__featured-inner">
+        <div class="event-card__featured-top">
+          <div class="event-card__date-badge" aria-hidden="true">
+            {{ with $e.end_date }}
+              {{ if ne $start.Year $end.Year }}
+                <span class="event-card__date-badge-primary">{{ $start.Format "Jan 2" }}–{{ $end.Format "Jan 2" }}</span>
+                <span class="event-card__date-badge-secondary">{{ $end.Format "2006" }}</span>
+              {{ else if or (ne $start.Month $end.Month) (ne $start.Day $end.Day) }}
+                <span class="event-card__date-badge-primary">{{ $start.Format "2" }}–{{ $end.Format "2" }}</span>
+                <span class="event-card__date-badge-secondary">{{ upper ($start.Format "Jan") }}</span>
+              {{ else }}
+                <span class="event-card__date-badge-primary">{{ $start.Format "2" }}</span>
+                <span class="event-card__date-badge-secondary">{{ upper ($start.Format "Jan") }}</span>
+              {{ end }}
+            {{ else }}
+              <span class="event-card__date-badge-primary">{{ $start.Format "2" }}</span>
+              <span class="event-card__date-badge-secondary">{{ upper ($start.Format "Jan") }}</span>
+              {{ if ne ($start.Format "2006") (now.Format "2006") }}
+                <span class="event-card__date-badge-year">{{ $start.Format "2006" }}</span>
+              {{ end }}
+            {{ end }}
+          </div>
+          {{ if and $typeLabel (ne $kind "") }}
+            <span class="event-card__type event-card__type--{{ $kind }}">{{ $typeLabel }}</span>
+          {{ end }}
+        </div>
+        <h3 class="event-card__title">{{ $p.Title }}</h3>
+        {{ if $subtitle }}<p class="event-card__meta">{{ $subtitle }}</p>{{ end }}
+        <span class="event-card__cta">Learn more <span aria-hidden="true">→</span></span>
+      </div>
+    {{ else }}
+      <div class="event-card__content">
+        <div class="event-card__date">
+          {{ if $img.exists }}
+            <div class="event-card__date-background"
+                 style="background-image: url('{{ $img.src }}');"></div>
+          {{ else }}
+            <div class="event-card__date-background event-card__date-background--default"></div>
+          {{ end }}
+          <div class="event-card__date-text">
+            {{ with $e.end_date }}
+              {{ $end2 := time . }}
+              {{ if ne $start.Year $end2.Year }}
+                <span>{{ $start.Format "Jan 2" }}–{{ $end2.Format "Jan 2, 2006" }}</span>
+              {{ else if ne $start.Month $end2.Month }}
+                <span>{{ $start.Format "Jan 2" }}–{{ $end2.Format "Jan 2" }}</span>
+              {{ else if ne $start.Day $end2.Day }}
+                <span>{{ $start.Format "2" }}–{{ $end2.Format "2" }}</span>
+              {{ else }}
+                <span>{{ $start.Format "2" }}</span>
+              {{ end }}
+            {{ else }}
+              <span>{{ $start.Format "2" }}</span>
+            {{ end }}
+            <span>{{ $start.Format "Jan" }}</span>
+            <span>{{ $start.Format "2006" }}</span>
+          </div>
+        </div>
+        <div class="event-card__details">
+          {{ if and $typeLabel (ne $kind "") }}
+            <span class="event-card__type event-card__type--{{ $kind }} event-card__type--inline">{{ $typeLabel }}</span>
+          {{ end }}
+          <h3 class="event-card__title">{{ $p.Title }}</h3>
+          {{ with $p.Summary }}
+            <p>{{ . | plainify | truncate 120 }}</p>
+          {{ end }}
+          <span class="event-card__button">{{ cond $compact "View" "Learn more" }}</span>
+        </div>
+      </div>
+    {{ end }}
+  </a>
+</article>
diff --git a/themes/clean-hugo/layouts/partials/event-date-display.html b/themes/clean-hugo/layouts/partials/event-date-display.html
new file mode 100644
index 00000000..de4e4552
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/event-date-display.html
@@ -0,0 +1,17 @@
+{{/*
+  Human-readable event date (and optional ISO range for <time datetime>).
+  Pass dict: event (required params.event map).
+*/}}
+{{ $e := .event }}
+{{ $start := time $e.start_date }}
+{{ $endStr := $e.end_date | default $e.start_date }}
+{{ $end := time $endStr }}
+{{ if eq $e.start_date $endStr }}
+  {{ $start.Format "Jan 2, 2006" }}
+{{ else if and (eq $start.Year $end.Year) (eq $start.Month $end.Month) }}
+  {{ $start.Format "Jan" }} {{ $start.Format "2" }}–{{ $end.Format "2" }}, {{ $start.Format "2006" }}
+{{ else if eq $start.Year $end.Year }}
+  {{ $start.Format "Jan 2" }} – {{ $end.Format "Jan 2" }}, {{ $start.Format "2006" }}
+{{ else }}
+  {{ $start.Format "Jan 2, 2006" }} – {{ $end.Format "Jan 2, 2006" }}
+{{ end }}
diff --git a/themes/clean-hugo/layouts/partials/event-instructors.html b/themes/clean-hugo/layouts/partials/event-instructors.html
new file mode 100644
index 00000000..4327e86d
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/event-instructors.html
@@ -0,0 +1,25 @@
+{{ with .Params.instructors }}
+<section class="event-instructors" aria-label="Instructors">
+  <h2 class="event-instructors__heading">Instructors</h2>
+  <ul class="event-instructors__grid">
+    {{ range . }}
+      <li class="event-instructors__card">
+        <img
+          class="event-instructors__avatar"
+          src="https://github.com/{{ .github }}.png"
+          width="120"
+          height="120"
+          loading="lazy"
+          alt="GitHub profile photo of {{ .name }}"
+        />
+        <div class="event-instructors__body">
+          <h3 class="event-instructors__name">
+            <a href="https://github.com/{{ .github }}" rel="noopener noreferrer">{{ .name }}</a>
+          </h3>
+          {{ with .bio }}<p class="event-instructors__bio">{{ . | markdownify }}</p>{{ end }}
+        </div>
+      </li>
+    {{ end }}
+  </ul>
+</section>
+{{ end }}
diff --git a/themes/clean-hugo/layouts/partials/events-past-archives.html b/themes/clean-hugo/layouts/partials/events-past-archives.html
new file mode 100644
index 00000000..ec835d72
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/events-past-archives.html
@@ -0,0 +1,61 @@
+{{/*
+  Past events section — same layout/styling as blog "From the Archives"
+  (blog-archives + highlight-grid). Pass a slice of sorted event pages (newest first).
+*/}}
+{{ $pastPages := . }}
+{{ if gt (len $pastPages) 0 }}
+{{ $typeLabels := dict "training" "Training" "sprint" "Sprint" "community" "Community event" "talk" "Talk" }}
+<section class="blog-archives events-past-archives" aria-labelledby="past-events-heading">
+  <div class="container">
+    <div class="intro">
+      <h2 id="past-events-heading">Past events</h2>
+    </div>
+
+    <div class="highlight-grid">
+      {{ range $pastPages }}
+        {{ $e := .Params.event }}
+        {{ $start := time $e.start_date }}
+        {{ $kind := lower (urlize ($e.event_type | default "")) }}
+        {{ $typeLabel := index $typeLabels $kind }}
+        {{ $img := partial "get-image.html" (dict "image" .Params.image "fallbackAlt" .Title "page" .) }}
+        <article class="listing-card listing-card--on-light listing-card--density-compact{{ if $img.exists }} listing-card--with-image{{ end }}">
+          {{ if $img.exists }}
+            <figure class="listing-card__image">
+              <a href="{{ .Permalink }}" tabindex="-1" aria-hidden="true">
+                <img src="{{ $img.src }}" alt="{{ $img.alt }}" loading="lazy" decoding="async" />
+              </a>
+            </figure>
+          {{ end }}
+
+          <div class="listing-card__body">
+            <div class="meta">
+              <time datetime="{{ $e.start_date }}">
+                {{ partial "event-date-display.html" (dict "event" $e) }}
+              </time>
+              {{ if $typeLabel }}
+                <span class="category">{{ $typeLabel }}</span>
+              {{ else }}
+                <span class="category">Event</span>
+              {{ end }}
+            </div>
+
+            <div class="content">
+              <h3>
+                <a href="{{ .Permalink }}">{{ .Title }}</a>
+              </h3>
+
+              <p class="excerpt">
+                {{ partial "blog-excerpt.html" (dict "." . "length" 200) }}
+              </p>
+
+              <a href="{{ .Permalink }}" class="read-more">
+                Read more <i class="fas fa-arrow-right"></i>
+              </a>
+            </div>
+          </div>
+        </article>
+      {{ end }}
+    </div>
+  </div>
+</section>
+{{ end }}
diff --git a/themes/clean-hugo/layouts/partials/events-upcoming.html b/themes/clean-hugo/layouts/partials/events-upcoming.html
new file mode 100644
index 00000000..e289070a
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/events-upcoming.html
@@ -0,0 +1,84 @@
+{{/*
+  Upcoming/live events section.
+  Pass dict:
+    context (required): current page context (.)
+    pages (optional): page collection to classify; defaults to all event pages
+    limit (optional): max items; 0 or unset shows all
+    use_container (optional bool): wrap content in .container (default true)
+    show_kicker (optional bool): render "Upcoming & live" kicker
+    show_view_all (optional bool): render "View all events" button
+    show_empty (optional bool): render empty-state section if no events
+    view_all_url (optional): defaults to /events/
+    section_class (optional): extra class on <section>
+*/}}
+{{ $ctx := .context }}
+{{ $pages := .pages | default (where $ctx.Site.RegularPages "Section" "events") }}
+{{ $today := now.Format "2006-01-02" }}
+{{ $live := slice }}
+{{ $upcoming := slice }}
+{{ $limit := .limit | default 0 }}
+{{ $useContainer := .use_container | default true }}
+{{ $showKicker := .show_kicker | default true }}
+{{ $showViewAll := .show_view_all | default false }}
+{{ $showEmpty := .show_empty | default false }}
+{{ $viewAllURL := .view_all_url | default "/events/" }}
+{{ $sectionClass := .section_class | default "" }}
+
+{{ range $pages }}
+  {{ $e := .Params.event }}
+  {{ if and $e $e.start_date }}
+    {{ $start := $e.start_date }}
+    {{ $end := $e.end_date | default $e.start_date }}
+    {{ if lt $today $start }}
+      {{ $upcoming = $upcoming | append . }}
+    {{ else if and (le $start $today) (le $today $end) }}
+      {{ $live = $live | append . }}
+    {{ end }}
+  {{ end }}
+{{ end }}
+
+{{ $featuredEvents := append
+  (sort $live "Params.event.end_date" "asc")
+  (sort $upcoming "Params.event.start_date" "asc")
+}}
+{{ if gt $limit 0 }}
+  {{ $featuredEvents = first $limit $featuredEvents }}
+{{ end }}
+
+{{ if gt (len $featuredEvents) 0 }}
+  <section class="events-list{{ with $sectionClass }} {{ . }}{{ end }}">
+    <div class="{{ if $useContainer }}container{{ else }}events-list__inner{{ end }}">
+      {{ if $showKicker }}
+        <h2 class="events-list__kicker">
+          Upcoming <span class="events-list__kicker-amp">&amp;</span> live
+        </h2>
+      {{ end }}
+      <div class="events-list__featured">
+        {{ range $featuredEvents }}
+          {{ partial "event-card.html" (dict
+            "Page" .
+            "compact" false
+            "variant" "featured"
+          ) }}
+        {{ end }}
+      </div>
+      {{ if $showViewAll }}
+        <div class="events-list__actions">
+          <a class="btn btn--outline" href="{{ $viewAllURL | relURL }}">
+            View all events
+          </a>
+        </div>
+      {{ end }}
+    </div>
+  </section>
+{{ else if $showEmpty }}
+  <section class="events-list{{ with $sectionClass }} {{ . }}{{ end }}">
+    <div class="{{ if $useContainer }}container{{ else }}events-list__inner{{ end }}">
+      <p class="events-list__empty">
+        No upcoming events right now. Browse
+        <a href="{{ "/events/" | relURL }}">past events</a>
+        or <a href="{{ "/blog/" | relURL }}">read the blog</a> for updates.
+      </p>
+    </div>
+  </section>
+{{ end }}
diff --git a/themes/clean-hugo/layouts/partials/feature-cards.html b/themes/clean-hugo/layouts/partials/feature-cards.html
new file mode 100644
index 00000000..f223d32a
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/feature-cards.html
@@ -0,0 +1,25 @@
+<section class="feature">
+  <header class="feature__header">
+    <h2>{{ .Params.feature_title | default "What I've Built" }}</h2>
+    <p>{{ .Params.feature_subtitle | default "A showcase of my work and achievements" }}</p>
+  </header>
+
+  <div class="feature__grid">
+    {{ $content := .Content }}
+    {{ if $content }}
+      <article class="feature-card">
+        {{ $content | markdownify }}
+      </article>
+    {{ else }}
+      {{/* Fallback: render from params if no content */}}
+      {{ with .Params.features }}
+        {{ range . }}
+          <article class="feature-card">
+            {{ with .title }}<h3>{{ . }}</h3>{{ end }}
+            {{ with .content }}<div>{{ . | markdownify }}</div>{{ end }}
+          </article>
+        {{ end }}
+      {{ end }}
+    {{ end }}
+  </div>
+</section>
diff --git a/themes/clean-hugo/layouts/partials/feature-section.html b/themes/clean-hugo/layouts/partials/feature-section.html
new file mode 100644
index 00000000..6daa1581
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/feature-section.html
@@ -0,0 +1,73 @@
+{{/* Feature section partial - reads from page front matter (.Params.feature_section) */}}
+{{ $feature := .Params.feature_section }}
+{{ if $feature }}
+<section class="feature-section container">
+  <header>
+    <h2>{{ $feature.title | default "Featured Content" }}</h2>
+    {{ with $feature.subtitle }}
+      <p>{{ . }}</p>
+    {{ end }}
+  </header>
+
+  <div>
+    <article class="feature-card">
+      {{ range $feature.sections }}
+        <h3>{{ .title }}</h3>
+        {{ with .lead }}
+          <p class="lead">{{ . }}</p>
+        {{ end }}
+
+        {{ if .items }}
+          {{ $isLinks := false }}
+          {{ range .items }}
+            {{ if .url }}
+              {{ $isLinks = true }}
+              {{ break }}
+            {{ end }}
+          {{ end }}
+
+          <ul{{ if $isLinks }} class="links"{{ end }}>
+            {{ range .items }}
+              <li>
+                {{ if .url }}
+                  <a href="{{ .url }}">{{ .text }}</a>
+                {{ else }}
+                  {{ if .bold }}
+                    <strong>{{ .bold }}</strong>{{ if .text }}{{ .text }}{{ end }}
+                  {{ else }}
+                    {{ .text }}
+                  {{ end }}
+                {{ end }}
+              </li>
+            {{ end }}
+          </ul>
+        {{ end }}
+
+        {{ if .subsections }}
+          {{ range .subsections }}
+            <h4>{{ .title }}</h4>
+            {{ with .content }}
+              <p>{{ . }}</p>
+            {{ end }}
+            {{ if .items }}
+              <ul{{ if .links }} class="links"{{ end }}>
+                {{ range .items }}
+                  <li>
+                    {{ if .url }}
+                      <a href="{{ .url }}">{{ .text }}</a>
+                    {{ else if .bold }}
+                      <strong>{{ .bold }}</strong>{{ if .text }}{{ .text }}{{ end }}
+                    {{ else }}
+                      {{ .text }}
+                    {{ end }}
+                  </li>
+                {{ end }}
+              </ul>
+            {{ end }}
+          {{ end }}
+        {{ end }}
+      {{ end }}
+    </article>
+  </div>
+</section>
+{{ end }}
diff --git a/themes/clean-hugo/layouts/partials/footer.html b/themes/clean-hugo/layouts/partials/footer.html
new file mode 100644
index 00000000..b0924738
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/footer.html
@@ -0,0 +1,30 @@
+<footer id="footer" class="site-footer">
+  <div class="site-footer__inner">
+    <div class="site-footer__follow">
+      <ul class="social-icons">
+        {{ range .Site.Params.footer.links }}
+          <li>
+            <a
+              href="{{ .url }}"
+              class="site-footer__social-link"
+              aria-label="{{ .label }}"
+              data-tooltip="{{ .label }}"
+              {{ if .rel_me }}rel="nofollow noopener noreferrer me"{{ else }}rel="nofollow noopener noreferrer"{{ end }}
+            >
+              <i class="{{ .icon }}" aria-hidden="true"></i>
+            </a>
+          </li>
+        {{ end }}
+      </ul>
+    </div>
+
+    <div class="site-footer__copyright">
+      {{ with .Site.Params.footer.mission }}
+        <p class="site-footer__mission">{{ . | safeHTML }}</p>
+      {{ end }}
+      <p class="site-footer__copy">
+        &copy; {{ now.Format "2006" }} {{ .Site.Title }}
+      </p>
+    </div>
+  </div>
+</footer>
diff --git a/themes/clean-hugo/layouts/partials/gallery-card.html b/themes/clean-hugo/layouts/partials/gallery-card.html
new file mode 100644
index 00000000..2ade76a4
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/gallery-card.html
@@ -0,0 +1,60 @@
+{{ $isVariety := false }}
+{{ $page := . }}
+{{ $item := dict }}
+
+{{ if reflect.IsMap . }}
+    {{ $isVariety = true }}
+    {{ $page = .Page }}
+    {{ $item = .Item }}
+{{ end }}
+
+{{ $groups := "" }}
+{{ with $page.Params.groups }}
+  {{ $groups = delimit . " " }}
+{{ else }}
+  {{ if $page.Params.group }}
+    {{ $groups = $page.Params.group }}
+  {{ end }}
+{{ end }}
+
+<article class="gallery-card" data-groups='{{ $groups }}'>
+  {{ $img := "" }}
+
+  {{ if $isVariety }}
+    <!-- Variety/sub-item: use thumbnail from frontmatter -->
+    {{ with $item.thumbnail }}
+      {{ $img = $page.Resources.GetMatch . }}
+    {{ end }}
+  {{ else }}
+    <!-- Regular page: use hero image or first image -->
+    {{ with $page.Params.hero }}
+      {{ with .image }}
+        {{ $img = $page.Resources.GetMatch . }}
+      {{ end }}
+    {{ end }}
+  {{ end }}
+
+  <!-- Fallback: grab first image -->
+  {{ if not $img }}
+    {{ $all := $page.Resources.Match "*.{png,jpg,jpeg,gif,webp}" }}
+    {{ if gt (len $all) 0 }}
+      {{ $img = index $all 0 }}
+    {{ end }}
+  {{ end }}
+
+  {{ $title := cond $isVariety $item.name $page.Title }}
+
+  <a href="{{ $page.RelPermalink }}" class="gallery-card__link group" aria-label="{{ $title }}">
+    {{ with $img }}
+      {{ $thumb := .Fill "750x500 center" }}
+
+      <div class="gallery-card__image">
+        <img src="{{ $thumb.RelPermalink }}" alt="{{ $title }}" loading="lazy">
+      </div>
+    {{ end }}
+
+    <div class="gallery-card__content">
+      <h3 class="gallery-card__title">{{ $title }}</h3>
+    </div>
+  </a>
+</article>
diff --git a/themes/clean-hugo/layouts/partials/gallery-filter.html b/themes/clean-hugo/layouts/partials/gallery-filter.html
new file mode 100644
index 00000000..08fe7110
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/gallery-filter.html
@@ -0,0 +1,44 @@
+{{/*
+  Gallery/Plant Filter Script Partial
+
+  Parameters:
+  - cardSelector: CSS selector for cards to filter (default: '.gallery-card')
+  - ariaLabel: ARIA label for the filter buttons (default: 'Filter by group')
+*/}}
+{{ $cardSelector := .cardSelector | default ".gallery-card" }}
+{{ $ariaLabel := .ariaLabel | default "Filter by group" }}
+
+<script>
+(function(){
+  const buttons = Array.from(document.querySelectorAll('.filter-btn'));
+  const cards = Array.from(document.querySelectorAll('{{ $cardSelector }}'));
+  if (!buttons.length) return;
+
+  function setActive(btn){
+    buttons.forEach(b => b.setAttribute('aria-pressed','false'));
+    btn.setAttribute('aria-pressed','true');
+  }
+  function filter(group){
+    cards.forEach(c=>{
+      const groups = (c.dataset.groups || '').split(/\s+/).filter(Boolean);
+      if(group === 'all' || groups.includes(group) || groups.length === 0) {
+        c.style.display = '';
+      } else {
+        c.style.display = 'none';
+      }
+    });
+  }
+
+  buttons.forEach(b=>{
+    b.addEventListener('click', ()=>{
+      setActive(b);
+      filter(b.getAttribute('data-filter'));
+    });
+  });
+
+  // Ensure initial state
+  const active = buttons.find(b => b.getAttribute('aria-pressed') === 'true') || buttons[0];
+  setActive(active);
+  filter(active.getAttribute('data-filter') || 'all');
+})();
+</script>
diff --git a/themes/clean-hugo/layouts/partials/gallery-grid.html b/themes/clean-hugo/layouts/partials/gallery-grid.html
new file mode 100644
index 00000000..d93bdae6
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/gallery-grid.html
@@ -0,0 +1,83 @@
+{{ $ctx := . }}
+{{ $pages := .Pages }}
+{{ if reflect.IsMap $ctx }}
+  {{ with $ctx.Pages }}
+    {{ $pages = . }}
+  {{ end }}
+{{ end }}
+
+<div class="gallery-grid-container">
+  {{ if and (reflect.IsMap $ctx) $ctx.Title }}
+    <h2 class="gallery-grid__title">{{ $ctx.Title }}</h2>
+  {{ end }}
+
+  {{/* Step 1: Build species/category map and count items */}}
+  {{ $categoryMap := dict }}
+  {{ $singles := slice }}
+
+  {{ range $pages }}
+    {{ $category := .Params.category | default "" }}
+    {{ if .Params.items }}
+      {{/* Page has varieties/sub-items */}}
+      {{ $itemCount := len .Params.items }}
+      {{ if ge $itemCount 2 }}
+        {{/* 2+ items = gets its own section */}}
+        {{ $existing := slice }}
+        {{ with index $categoryMap $category }}
+          {{ $existing = . }}
+        {{ end }}
+        {{ $categoryMap = merge $categoryMap (dict $category ($existing | append .)) }}
+      {{ else }}
+        {{/* Only 1 item = treat as single */}}
+        {{ $singles = $singles | append . }}
+      {{ end }}
+    {{ else }}
+      {{/* No varieties = single item */}}
+      {{ $singles = $singles | append . }}
+    {{ end }}
+  {{ end }}
+
+  {{/* Step 2: Render grouped sections alphabetically */}}
+  {{ $categoryList := slice }}
+  {{ range $key, $val := $categoryMap }}
+    {{ $categoryList = $categoryList | append $key }}
+  {{ end }}
+  {{ $sortedCategories := sort $categoryList }}
+  {{ range $category := $sortedCategories }}
+    {{ $categoryPages := index $categoryMap $category }}
+    <section class="gallery-grid__section">
+      <h3 class="gallery-grid__category-title">{{ $category }}</h3>
+      <div class="gallery-grid__items">
+        {{ range $categoryPages }}
+          {{ $parentPage := . }}
+          {{/* Sort items by name */}}
+          {{ $sortedItems := sort .Params.items "name" }}
+          {{ range $sortedItems }}
+            {{ partial "gallery-card.html" (dict "Page" $parentPage "Item" . "IsVariety" true) }}
+          {{ end }}
+        {{ end }}
+      </div>
+    </section>
+  {{ end }}
+
+  {{/* Step 3: Render singles */}}
+  {{ if gt (len $singles) 0 }}
+    <section class="gallery-grid__section">
+      <h3 class="gallery-grid__category-title">{{ $ctx.Site.Params.gallery.otherTitle | default "Other Items" }}</h3>
+      <div class="gallery-grid__items">
+        {{ range sort $singles "Title" }}
+          {{ if .Params.items }}
+            {{/* Single variety page */}}
+            {{ $parentPage := . }}
+            {{ range .Params.items }}
+              {{ partial "gallery-card.html" (dict "Page" $parentPage "Item" . "IsVariety" true) }}
+            {{ end }}
+          {{ else }}
+            {{/* Regular single item */}}
+            {{ partial "gallery-card.html" . }}
+          {{ end }}
+        {{ end }}
+      </div>
+    </section>
+  {{ end }}
+</div>
diff --git a/themes/clean-hugo/layouts/partials/get-image.html b/themes/clean-hugo/layouts/partials/get-image.html
new file mode 100644
index 00000000..7997267e
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/get-image.html
@@ -0,0 +1,53 @@
+{{/*
+  Helper partial to extract image src, alt, and credit from nested image front matter
+  Handles both page bundles and static images with path-based convention
+
+  Path Convention:
+    - "filename.jpg" → looks in page bundle first
+    - "images/photo.jpg" → looks in static/images/
+    - "/images/photo.jpg" → looks in static/images/ (absolute)
+
+  Expected front matter format:
+    image:
+      src: "hoya-plant.jpg"  # page bundle
+      src: "images/unsplash-water.webp"  # static/images/
+      alt: "Description of image"
+      credit: "Photo by Jane Doe on Unsplash"  # optional
+*/}}
+
+{{ $image := .image }}
+{{ $fallbackAlt := .fallbackAlt | default "" }}
+{{ $page := .page }}
+{{ $result := dict "src" "" "alt" $fallbackAlt "credit" "" "exists" false }}
+
+
+
+{{ if $image }}
+  {{ if $image.src }}
+    {{ $imageSrc := $image.src }}
+    {{ $isStatic := or (hasPrefix $imageSrc "images/") (hasPrefix $imageSrc "/") }}
+
+    {{/* Try page bundle first if not explicitly a static path */}}
+    {{ if and $page (not $isStatic) }}
+      {{ $resource := $page.Resources.GetMatch $imageSrc }}
+      {{ if $resource }}
+        {{ $imageSrc = $resource.RelPermalink }}
+      {{ else }}
+        {{/* Not found in bundle, treat as static and apply relURL */}}
+        {{ $imageSrc = $imageSrc | relURL }}
+      {{ end }}
+    {{ else }}
+      {{/* Explicitly static path, apply relURL */}}
+      {{ $imageSrc = $imageSrc | relURL }}
+    {{ end }}
+
+    {{ $result = dict
+      "src" $imageSrc
+      "alt" ($image.alt | default $fallbackAlt)
+      "credit" ($image.credit | default "")
+      "exists" true
+    }}
+  {{ end }}
+{{ end }}
+
+{{ return $result }}
diff --git a/themes/clean-hugo/layouts/partials/glightbox-scripts.html b/themes/clean-hugo/layouts/partials/glightbox-scripts.html
new file mode 100644
index 00000000..4ce0cb5a
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/glightbox-scripts.html
@@ -0,0 +1,23 @@
+{{/*
+  GLightbox Scripts Partial
+
+  Loads GLightbox JavaScript and initializes it.
+  Only call this partial on pages that actually use galleries.
+
+  Usage in layout:
+  {{ define "scripts" }}
+    {{ partial "glightbox-scripts.html" . }}
+  {{ end }}
+*/}}
+
+{{ if .Site.Params.theme.enableGallery | default true }}
+  <script src="https://cdn.jsdelivr.net/npm/glightbox/dist/js/glightbox.min.js"></script>
+  <script>
+    GLightbox({
+      selector: '.glightbox',
+      touchNavigation: true,
+      loop: false,
+      autoplayVideos: true
+    });
+  </script>
+{{ end }}
diff --git a/themes/clean-hugo/layouts/partials/hero.html b/themes/clean-hugo/layouts/partials/hero.html
new file mode 100644
index 00000000..4a193ce9
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/hero.html
@@ -0,0 +1,77 @@
+{{ $hero := .Params.hero | default dict }}
+{{/* Determine hero background color: default to theme token, allow per-page override */}}
+{{ $heroColorParam := $hero.color }}
+{{ $heroColor := "var(--color-hero-bg)" }}
+{{ if $heroColorParam }}
+  {{/* Support token names (primary, primary-dark, accent, heroBg) or raw CSS colors */}}
+  {{ $colorTokens := dict
+      "primary" "var(--color-primary)"
+      "primarydark" "var(--color-primary-dark)"
+      "primary-dark" "var(--color-primary-dark)"
+      "primarylight" "var(--color-primary-light)"
+      "primary-light" "var(--color-primary-light)"
+      "secondary" "var(--color-secondary)"
+      "accent" "var(--color-accent)"
+      "accentlight" "var(--color-accent-light)"
+      "accent-light" "var(--color-accent-light)"
+      "neutral" "var(--color-neutral)"
+      "herobg" "var(--color-hero-bg)"
+      "hero" "var(--color-hero-bg)"
+    }}
+  {{ $normalized := lower (replace $heroColorParam " " "") }}
+  {{ $lookup := index $colorTokens $normalized }}
+  {{ if $lookup }}
+    {{ $heroColor = $lookup }}
+  {{ else }}
+    {{ $heroColor = $heroColorParam }}
+  {{ end }}
+{{ end }}
+{{ $isGallery := or (eq .Section "gallery") (eq .Section "plants") }}
+{{/* For plant pages, always use main front matter title; otherwise use hero.title if available */}}
+{{ $title := "" }}
+{{ if $isGallery }}
+  {{ $title = .Title }}
+{{ else }}
+  {{ $title = $hero.title | default .Title }}
+{{ end }}
+{{/* Final fallback to ensure title always exists */}}
+{{ if not $title }}{{ $title = .Title }}{{ end }}
+{{ $subtitle := $hero.subtitle }}
+{{ $excerpt := $hero.excerpt }}
+{{ $buttons := $hero.buttons }}
+{{ $heroSquareImg := $hero.square_image }}
+{{/* Get hero image using helper partial */}}
+{{ $heroImg := partial "get-image.html" (dict "image" $hero.image "fallbackAlt" ($title | default (printf "Image for %s" .Title))) }}
+
+<section class="hero" style="background-color: {{ $heroColor }};">
+  <div class="container">
+    <div class="hero__grid">
+      <div class="hero__content">
+        <h1 class="hero__title">{{ $title }}</h1>
+        {{ with $subtitle }}<p class="hero__subtitle">{{ . }}</p>{{ end }}
+        {{ with $excerpt }}<p class="hero__excerpt">{{ . }}</p>{{ end }}
+        {{ with $buttons }}
+          <div class="hero__actions btn-group" role="group" aria-label="Primary actions">
+            {{ range . }}
+              {{ $href := .url }}
+              {{ if not (hasPrefix $href "http") }}
+                {{ $href = relURL $href }}
+              {{ end }}
+              {{ $variant := .variant | default "outline-on-dark" }}
+              <a class="btn btn--{{ $variant }} btn--lg" href="{{ $href }}">{{ .label }}</a>
+            {{ end }}
+          </div>
+        {{ end }}
+      </div>
+
+    <!-- Right side circle with photo - only render if image exists -->
+    {{- if $heroImg.exists -}}
+      <div class="hero__image-wrapper">
+        <div class="hero__image-container {{ if or $isGallery $heroSquareImg }}hero__image-container-square{{ end }}">
+          <img src="{{ $heroImg.src | relURL }}" alt="{{ $heroImg.alt }}" class="hero__image">
+        </div>
+      </div>
+    {{- end -}}
+    </div>
+  </div>
+</section>
diff --git a/themes/clean-hugo/layouts/partials/highlight-cards.html b/themes/clean-hugo/layouts/partials/highlight-cards.html
new file mode 100644
index 00000000..c54ca2df
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/highlight-cards.html
@@ -0,0 +1,15 @@
+<!-- Display a section with highlight cards arranged in a grid layout.
+ Content grabbed from yaml front matter-->
+
+<section class="highlight">
+  <div class="highlight__grid">
+    {{ $cards := .Params.cards }}
+    {{ if $cards }}
+      {{ range $i, $c := $cards }}
+        <div class="{{ $c.grid | default "" }}">
+          {{ partial "cards.html" $c }}
+        </div>
+      {{ end }}
+    {{ end }}
+  </div>
+</section>
diff --git a/themes/clean-hugo/layouts/partials/impact-cards.html b/themes/clean-hugo/layouts/partials/impact-cards.html
new file mode 100644
index 00000000..b21bae27
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/impact-cards.html
@@ -0,0 +1,15 @@
+<!-- Display a section with impact cards arranged in a grid layout.
+ Content grabbed from yaml front matter.
+ Optional: cards_layout: wide — wider max-width and 3 columns from $breakpoint-lg up. -->
+
+{{ $wide := eq (lower (default "" .Params.cards_layout)) "wide" }}
+<section class="impact-cards{{ if $wide }} impact-cards--wide{{ end }}">
+  <div class="impact-cards__grid{{ if $wide }} impact-cards__grid--wide{{ end }}">
+    {{ $cards := .Params.cards }}
+    {{ if $cards }}
+      {{ range $i, $c := $cards }}
+        {{ partial "cards.html" (merge $c (dict "page" $)) }}
+      {{ end }}
+    {{ end }}
+  </div>
+</section>
diff --git a/themes/clean-hugo/layouts/partials/intro-section.html b/themes/clean-hugo/layouts/partials/intro-section.html
new file mode 100644
index 00000000..1274bec6
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/intro-section.html
@@ -0,0 +1,11 @@
+{{/* Intro section partial - reads from page front matter (.Params.intro_section) */}}
+{{ $intro := .Params.intro_section | default dict }}
+{{ if $intro.text }}
+<section class="intro-section">
+  <div class="container">
+    <div>
+      {{ $intro.text | markdownify }}
+    </div>
+  </div>
+</section>
+{{ end }}
diff --git a/themes/clean-hugo/layouts/partials/last-modified.html b/themes/clean-hugo/layouts/partials/last-modified.html
new file mode 100644
index 00000000..bf7d09be
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/last-modified.html
@@ -0,0 +1,19 @@
+{{/* Last Modified Date Partial
+  Uses GitInfo.Lastmod if available (requires enableGitInfo = true),
+  otherwise falls back to .Lastmod (file system modification time)
+*/}}
+{{ $lastmod := .Lastmod }}
+{{ if .GitInfo }}
+  {{ $lastmod = .GitInfo.Lastmod }}
+{{ end }}
+
+{{ if $lastmod }}
+  <footer class="content-last-modified">
+    <p>
+      <strong>Last modified:</strong>
+      <time datetime="{{ $lastmod.Format "2006-01-02" }}">
+        {{ $lastmod.Format "January 2, 2006" }}
+      </time>
+    </p>
+  </footer>
+{{ end }}
diff --git a/themes/clean-hugo/layouts/partials/learn-more.html b/themes/clean-hugo/layouts/partials/learn-more.html
new file mode 100644
index 00000000..47e931a0
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/learn-more.html
@@ -0,0 +1,23 @@
+{{ $resources := .Params.learn_more }}
+{{ $defaultIcon := .Params.learn_more_icon | default "fa-book" }}
+{{ $title := .Params.learn_more_title | default "Learn More" }}
+
+{{ if $resources }}
+<div class="learn-more">
+  <div class="learn-more__header">
+    <h3 class="learn-more__title"><i class="fas fa-graduation-cap"></i> {{ $title }}</h3>
+  </div>
+
+  <ul class="learn-more__list">
+    {{ range $resources }}
+    <li class="learn-more__item">
+      <a href="{{ .url }}"
+         target="_blank"
+         rel="noopener">
+        <span class="learn-more__item-text"><i class="fas {{ .icon | default $defaultIcon }}"></i> {{ .title }}</span>
+      </a>
+    </li>
+    {{ end }}
+  </ul>
+</div>
+{{ end }}
diff --git a/themes/clean-hugo/layouts/partials/listing-card-event.html b/themes/clean-hugo/layouts/partials/listing-card-event.html
new file mode 100644
index 00000000..e2e39123
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/listing-card-event.html
@@ -0,0 +1,52 @@
+{{/*
+  Event listing card — same markup/classes as blog archive cards
+  (listing-card--blog-archive on .blog-archives light purple band).
+  Optional params.image renders a 16:9 strip above the card body.
+  Pass the event page as context (.).
+*/}}
+{{ $p := . }}
+{{ $e := $p.Params.event }}
+{{ if not $e }}
+  {{ return }}
+{{ end }}
+{{ $typeLabels := dict "training" "Training" "sprint" "Sprint" "community" "Community event" "talk" "Talk" }}
+{{ $kind := lower (urlize ($e.event_type | default "")) }}
+{{ $typeLabel := index $typeLabels $kind }}
+{{ $endStr := $e.end_date | default $e.start_date }}
+{{ $img := partial "get-image.html" (dict "image" $p.Params.image "fallbackAlt" $p.Title "page" $p) }}
+<article class="listing-card listing-card--blog-archive listing-card--density-default{{ if $img.exists }} listing-card--with-image{{ end }}">
+  {{ if $img.exists }}
+    <figure class="listing-card__image">
+      <a href="{{ $p.Permalink }}" tabindex="-1" aria-hidden="true">
+        <img src="{{ $img.src }}" alt="{{ $img.alt }}" loading="lazy" decoding="async" />
+      </a>
+    </figure>
+  {{ end }}
+
+  <div class="listing-card__body">
+    <div class="meta">
+      <time datetime="{{ $e.start_date }}/{{ $endStr }}">
+        {{ partial "event-date-display.html" (dict "event" $e) }}
+      </time>
+      {{ if $typeLabel }}
+        <span class="category">{{ $typeLabel }}</span>
+      {{ else }}
+        <span class="category">Event</span>
+      {{ end }}
+    </div>
+
+    <div class="content">
+      <h3>
+        <a href="{{ $p.Permalink }}">{{ $p.Title }}</a>
+      </h3>
+
+      <p class="excerpt">
+        {{ partial "blog-excerpt.html" (dict "." $p "length" 200) }}
+      </p>
+
+      <a href="{{ $p.Permalink }}" class="read-more">
+        Read more <i class="fas fa-arrow-right"></i>
+      </a>
+    </div>
+  </div>
+</article>
diff --git a/themes/clean-hugo/layouts/partials/metrics-bar-render.html b/themes/clean-hugo/layouts/partials/metrics-bar-render.html
new file mode 100644
index 00000000..33bbcb7f
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/metrics-bar-render.html
@@ -0,0 +1,17 @@
+{{/*
+  Metrics Bar Renderer
+  A partial that renders the metrics bar HTML structure within a layout
+  Usage: {{ partial "metrics-bar-render.html" (dict "stats" (slice "**5** Packages" "**10** Users")) }}
+*/}}
+
+{{ $stats := .stats | default slice }}
+
+<div class="metrics-bar">
+  <div>
+    {{ range $stats }}
+      {{ if . }}
+      <div>{{ . | markdownify }}</div>
+      {{ end }}
+    {{ end }}
+  </div>
+</div>
diff --git a/themes/clean-hugo/layouts/partials/packages/card-static.html b/themes/clean-hugo/layouts/partials/packages/card-static.html
new file mode 100644
index 00000000..98aabdb3
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/packages/card-static.html
@@ -0,0 +1,41 @@
+{{/* Static package card for Hugo-rendered grids (no Alpine). */}}
+<div class="package_card">
+  <div>
+    <h3>{{ .package_name }}</h3>
+
+    <div class="package_card__meta">
+      <i class="fas fa-feather" aria-hidden="true"></i>
+      <span>
+        {{ range $i, $m := .all_current_maintainers }}
+          {{ if $i }}, {{ end }}{{ $m.name | default $m.github_username }}
+        {{ end }}
+      </span>
+    </div>
+
+    <p>{{ .package_description }}</p>
+
+    <ul>
+      {{ with .repository_link }}
+        <li><a href="{{ . }}" target="_blank" rel="noopener noreferrer"><i class="fab fa-github"></i> View Code</a></li>
+      {{ end }}
+
+      {{ if .active }}
+        {{ with .gh_meta }}
+          {{ with .documentation }}
+            <li><a href="{{ . }}" target="_blank" rel="noopener noreferrer"><i class="fas fa-book-open"></i> View Docs</a></li>
+          {{ end }}
+        {{ end }}
+        {{ with .issue_link }}
+          <li><a href="{{ . }}" target="_blank" rel="noopener noreferrer"><i class="fa-solid fa-user-pen"></i> View Review</a></li>
+        {{ end }}
+        {{ with .joss }}
+          <li><a href="{{ $.archive | default . }}" target="_blank" rel="noopener noreferrer"><i class="fas fa-bookmark"></i> JOSS Approved</a></li>
+        {{ end }}
+      {{ else }}
+        <li class="package_card__archived">
+          <i class="fa-solid fa-box-archive"></i> Archived
+        </li>
+      {{ end }}
+    </ul>
+  </div>
+</div>
diff --git a/themes/clean-hugo/layouts/partials/packages/filters.html b/themes/clean-hugo/layouts/partials/packages/filters.html
new file mode 100644
index 00000000..5cbae0f1
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/packages/filters.html
@@ -0,0 +1,48 @@
+{{/*
+  Package Filters Partial
+  Category filter buttons for package grid
+  Usage: {{ partial "packages/filters.html" . }}
+*/}}
+
+<div class="packages-filters">
+  <input type="text"
+         id="quicksearch"
+         placeholder="Search packages..."
+         aria-label="Search packages"
+         x-model="searchQuery" />
+
+  <div>
+    <button @click="activeFilter = '*'"
+            :class="{ 'is-checked': activeFilter === '*' }">
+      show all
+    </button>
+    <button @click="activeFilter = 'data-munging'"
+            :class="{ 'is-checked': activeFilter === 'data-munging' }">
+      data munging
+    </button>
+    <button @click="activeFilter = 'data-extraction'"
+            :class="{ 'is-checked': activeFilter === 'data-extraction' }">
+      data extraction
+    </button>
+    <button @click="activeFilter = 'data-retrieval'"
+            :class="{ 'is-checked': activeFilter === 'data-retrieval' }">
+      data retrieval
+    </button>
+    <button @click="activeFilter = 'data-visualization'"
+            :class="{ 'is-checked': activeFilter === 'data-visualization' }">
+      data visualization
+    </button>
+    <button @click="activeFilter = 'education'"
+            :class="{ 'is-checked': activeFilter === 'education' }">
+      education
+    </button>
+    <button @click="activeFilter = 'geospatial'"
+            :class="{ 'is-checked': activeFilter === 'geospatial' }">
+      geospatial
+    </button>
+    <button @click="activeFilter = 'reproducibility'"
+            :class="{ 'is-checked': activeFilter === 'reproducibility' }">
+      reproducibility
+    </button>
+  </div>
+</div>
diff --git a/themes/clean-hugo/layouts/partials/packages/grid.html b/themes/clean-hugo/layouts/partials/packages/grid.html
new file mode 100644
index 00000000..6d8b8085
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/packages/grid.html
@@ -0,0 +1,90 @@
+{{/*
+  Package Grid Partial
+  Grid container with AlpineJS filtering
+  Usage: {{ partial "packages/grid.html" (dict "activeOnly" true) }}
+  Note: Must be used within parent x-data="packageFilter()" context
+
+  ⚠️ IMPORTANT: Card markup below is DUPLICATED in layouts/partners/single.html
+  If you update the card structure, links, badges, or styling:
+  1. Update THIS file (AlpineJS version with x-text, :href)
+  2. Update layouts/partners/single.html (Hugo version with {{ .field }})
+  See: /blog/2025-12-25-package-architecture/ for architecture details
+*/}}
+
+{{ $activeOnly := .activeOnly | default true }}
+{{ $propName := cond $activeOnly "activePackages" "archivedPackages" }}
+
+<div class="packages-grid">
+  <template x-for="pkg in {{ $propName }}" :key="pkg.package_name">
+    <div class="package_card">
+      <div>
+
+        {{/* Title */}}
+        <h3 x-text="pkg.package_name"></h3>
+
+        {{/* Maintainers */}}
+        <div class="package_card__meta">
+          <i class="fas fa-feather" aria-hidden="true"></i>
+          <span x-text="pkg.all_current_maintainers?.map(m => m.name || m.github_username).join(', ') || pkg.submitting_author?.name || pkg.submitting_author?.github_username"></span>
+        </div>
+
+        {{/* Description */}}
+        <p x-html="pkg.package_description"></p>
+
+        {{/* Links */}}
+        <ul>
+          <template x-if="pkg.repository_link">
+            <li>
+              <a :href="pkg.repository_link" target="_blank">
+                <i class="fab fa-github"></i> View Code
+              </a>
+            </li>
+          </template>
+
+          {{/* Only show these links for active packages */}}
+          <template x-if="pkg.active === true && pkg.gh_meta?.documentation">
+            <li>
+              <a :href="pkg.gh_meta.documentation" target="_blank">
+                <i class="fas fa-book-open"></i> View Docs
+              </a>
+            </li>
+          </template>
+
+          <template x-if="pkg.active === true && pkg.issue_link">
+            <li>
+              <a :href="pkg.issue_link" target="_blank">
+                <i class="fa-solid fa-user-pen"></i> View Review
+              </a>
+            </li>
+          </template>
+
+          <template x-if="pkg.active === true && pkg.joss">
+            <li>
+              <a :href="pkg.archive" target="_blank">
+                <i class="fas fa-bookmark"></i> JOSS Approved
+              </a>
+            </li>
+          </template>
+
+          {{/* Astropy partner badge */}}
+          <template x-if="pkg.partners?.includes('astropy')">
+            <li>
+              <a href="#astropy" target="_blank" aria-label="Astropy affiliated package">
+                <i class="fa-solid fa-check-double"></i>
+                <img src="https://img.shields.io/badge/Affiliated-Astropy-orange.svg?style=flat" alt="Astropy Affiliated" class="partner-badge" />
+              </a>
+            </li>
+          </template>
+
+          {{/* Archived badge for archived packages */}}
+          <template x-if="pkg.active === false">
+            <li class="package_card__archived">
+              <i class="fa-solid fa-box-archive"></i> Archived
+            </li>
+          </template>
+        </ul>
+
+      </div>
+    </div>
+  </template>
+</div>
diff --git a/themes/clean-hugo/layouts/partials/packages/sort-by-date-accepted.html b/themes/clean-hugo/layouts/partials/packages/sort-by-date-accepted.html
new file mode 100644
index 00000000..fac194a2
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/packages/sort-by-date-accepted.html
@@ -0,0 +1,29 @@
+{{/*
+  Sort packages by date_accepted (newest first).
+  Rows with missing or invalid date_accepted sort last.
+  Usage: {{ $sorted := partial "packages/sort-by-date-accepted.html" (dict "packages" $packages) }}
+*/}}
+{{ $packages := .packages }}
+{{ $enriched := slice }}
+{{ range $packages }}
+  {{ $sortDate := "0000-01-01" }}
+  {{ $accepted := .date_accepted }}
+  {{ if and $accepted (ne $accepted "missing") }}
+    {{ $clean := replace (replace $accepted " " "") "-" "-" }}
+    {{ $parts := split $clean "-" }}
+    {{ if ge (len $parts) 3 }}
+      {{ $month := index $parts 1 }}
+      {{ $day := index $parts 2 }}
+      {{ if eq (len $month) 1 }}{{ $month = printf "0%s" $month }}{{ end }}
+      {{ if eq (len $day) 1 }}{{ $day = printf "0%s" $day }}{{ end }}
+      {{ $sortDate = printf "%s-%s-%s" (index $parts 0) $month $day }}
+    {{ end }}
+  {{ end }}
+  {{ $enriched = $enriched | append (dict "pkg" . "sortDate" $sortDate) }}
+{{ end }}
+{{ $sorted := sort $enriched "sortDate" "desc" }}
+{{ $result := slice }}
+{{ range $sorted }}
+  {{ $result = $result | append .pkg }}
+{{ end }}
+{{ return $result }}
diff --git a/themes/clean-hugo/layouts/partials/partnership-cards.html b/themes/clean-hugo/layouts/partials/partnership-cards.html
new file mode 100644
index 00000000..b7d41a85
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/partnership-cards.html
@@ -0,0 +1,126 @@
+<div class="partnership-cards">
+  <article class="partnership-card">
+    <div class="partnership-card__body">
+      <div class="partnership-card__main">
+        <h4 class="partnership-card__title">AcceleratorESSENTIALS</h4>
+        <p class="partnership-card__lede">
+          Get your researchers trained in open source workflows and Python
+          packaging with expert-backed course materials and train-the-trainer
+          materials.
+        </p>
+        <hr class="partnership-card__divider">
+        <p class="partnership-card__subheader">What's Included</p>
+        <ul class="partnership-card__features">
+          <li>10-day On-Demand Asynchronous Course Access: Ship It: Python Packaging in the GenAI Era</li>
+          <li>6 Months On Demand Course Access</li>
+          <li>~150 course seats</li>
+          <li>Train the trainer materials</li>
+          <li>Foundational workflows for sustainable software</li>
+          <li>1 Peer Review Webinar</li>
+          <li>Content sponsored by Open Source at Stanford University</li>
+        </ul>
+        <hr class="partnership-card__divider">
+        <p class="partnership-card__subheader">Course details</p>
+        <ul class="partnership-card__features">
+          <li>Asynchronous training access for research teams</li>
+          <li>27 videos across 10 modules</li>
+          <li>Python expert insights and videos</li>
+          <li>Course Certificate upon completion</li>
+          <li>GitHub badge upon completion</li>
+        </ul>
+      </div>
+      <p class="partnership-card__price">$2,500</p>
+    </div>
+    <a
+      href="mailto:media@pyopensci.org?subject=pyOpenSci%20university%20membership%20inquiry"
+      class="partnership-card__cta btn btn--dark-purple"
+    >Contact us</a>
+  </article>
+
+  <article class="partnership-card partnership-card--featured">
+    <div class="partnership-card__body">
+      <h4 class="partnership-card__title">AcceleratorCORE</h4>
+      <p class="partnership-card__lede">
+        Everything in Supporting Partner, plus cohort connection for your learners
+        through our online course community, open webinars, and access to
+        pyOpenSci's global network of scientists and open source maintainers.
+      </p>
+      <hr class="partnership-card__divider">
+      <p class="partnership-card__subheader">What's Included</p>
+      <ul class="partnership-card__features">
+        <li>10-day On-Demand Asynchronous Course Access: Ship It: Python Packaging in the GenAI Era</li>
+        <li>1 Year On Demand Course Access</li>
+        <li>~500 course seats</li>
+        <li>Train the trainer materials</li>
+        <li>Foundational workflows for sustainable software</li>
+        <li>1 Peer Review Webinar</li>
+        <li>2-3 Open Source Skills Webinar</li>
+        <li>Content sponsored by Open Source at Stanford University</li>
+      </ul>
+      <hr class="partnership-card__divider">
+      <p class="partnership-card__subheader">Course details</p>
+      <ul class="partnership-card__features">
+        <li>Asynchronous training access for research teams</li>
+        <li>27 videos across 10 modules</li>
+        <li>Python expert insights and videos</li>
+        <li>Course Certificate upon completion</li>
+        <li>GitHub badge upon completion</li>
+      </ul>
+    </div>
+    <a
+      href="mailto:media@pyopensci.org?subject=pyOpenSci%20university%20membership%20inquiry"
+      class="partnership-card__cta btn btn--dark-purple"
+    >Contact us</a>
+  </article>
+
+  <article class="partnership-card">
+    <div class="partnership-card__body">
+      <h4 class="partnership-card__title">
+        <i class="fa-solid fa-star partnership-card__star" aria-hidden="true"></i>
+        AcceleratorPRO
+      </h4>
+      <p class="partnership-card__lede">
+        Everything in Community Partner, plus a pyOpenSci curated course learning
+        experience with hands-on expert support during the course, gamified
+        course activities, and curriculum advisory. Course will be branded to
+        include your institution's name.
+      </p>
+      <hr class="partnership-card__divider">
+      <p class="partnership-card__subheader">What's Included</p>
+      <ul class="partnership-card__features">
+        <li>10-day On-Demand Asynchronous Course Access: Ship It: Python Packaging in the GenAI Era</li>
+        <li>1 Year On Demand Course Access</li>
+        <li>2 expert-supported course cohorts</li>
+        <li>Gamified activities facilitated by open source experts</li>
+        <li>Unlimited course seats</li>
+        <li>Train the trainer materials</li>
+        <li>Foundational workflows for sustainable software</li>
+        <li>2 Peer Review Webinars</li>
+        <li>Expert-lead packaging and open source webinars (up to 3)</li>
+        <li>Community access</li>
+        <li>Curriculum Advisory</li>
+        <li>Customized course branding for your institution</li>
+        <li>Content sponsored by Open Source at Stanford University</li>
+      </ul>
+      <hr class="partnership-card__divider">
+      <p class="partnership-card__subheader">Course details</p>
+      <ul class="partnership-card__features">
+        <li>Asynchronous training access for research teams</li>
+        <li>27 videos across 10 modules</li>
+        <li>Python expert insights and videos</li>
+        <li>Course Certificate upon completion</li>
+        <li>GitHub badge upon completion</li>
+      </ul>
+      <ul class="partnership-card__features">
+        <li>Leadership programming for research software champions</li>
+        <li>Institution-wide strategy sessions and advisory support</li>
+        <li>Visibility across pyOpenSci community channels</li>
+        <li>Long-term partnership planning and impact tracking</li>
+      </ul>
+    </div>
+    <a
+      href="mailto:media@pyopensci.org?subject=pyOpenSci%20university%20membership%20inquiry"
+      class="partnership-card__cta btn btn--dark-purple"
+    >Contact us</a>
+  </article>
+</div>
diff --git a/themes/clean-hugo/layouts/partials/people/card.html b/themes/clean-hugo/layouts/partials/people/card.html
new file mode 100644
index 00000000..a5e8d4a2
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/people/card.html
@@ -0,0 +1,62 @@
+{{/* People Card - Hugo template for static sections */}}
+
+<div class="people_card">
+  <div>
+    {{ if .github_image_id }}
+      <div class="people_card__image">
+        <img src="https://avatars1.githubusercontent.com/u/{{ .github_image_id }}?s=400&v=4"
+             alt="GitHub photo of {{ .name | default .github_username }}">
+      </div>
+    {{ end }}
+
+    <div class="people_card__content">
+      <h3>
+        {{ if .github_username }}
+          <a href="https://github.com/{{ .github_username }}" rel="noopener noreferrer">
+            {{ .name | default (printf "@%s" .github_username) }}
+          </a>
+        {{ else }}
+          {{ .name }}
+        {{ end }}
+      </h3>
+
+      {{ if .title }}
+        <div class="people_card__title">
+          {{ if reflect.IsSlice .title }}{{ delimit .title ", " }}{{ else }}{{ .title }}{{ end }}
+        </div>
+      {{ end }}
+
+      {{ if .organization }}
+        <div class="people_card__org">{{ .organization }}</div>
+      {{ end }}
+
+      <div class="people_card__social">
+        {{ if .twitter }}
+          <a href="https://www.twitter.com/{{ .twitter }}" rel="noopener noreferrer" aria-label="Twitter">
+            <i class="fab fa-twitter" aria-hidden="true"></i>
+          </a>
+        {{ end }}
+        {{ if .github_username }}
+          <a href="https://github.com/{{ .github_username }}" rel="noopener noreferrer" aria-label="GitHub">
+            <i class="fab fa-github" aria-hidden="true"></i>
+          </a>
+        {{ end }}
+        {{ if .website }}
+          <a href="{{ .website }}" rel="noopener noreferrer" aria-label="Website">
+            <i class="fas fa-blog" aria-hidden="true"></i>
+          </a>
+        {{ end }}
+        {{ if .orcidid }}
+          <a href="https://orcid.org/{{ .orcidid }}" rel="noopener noreferrer" aria-label="ORCID">
+            <i class="fab fa-orcid" aria-hidden="true"></i>
+          </a>
+        {{ end }}
+        {{ if .mastodon }}
+          <a href="{{ .mastodon }}" rel="noopener noreferrer" aria-label="Mastodon">
+            <i class="fab fa-mastodon" aria-hidden="true"></i>
+          </a>
+        {{ end }}
+      </div>
+    </div>
+  </div>
+</div>
diff --git a/themes/clean-hugo/layouts/partials/people/filters.html b/themes/clean-hugo/layouts/partials/people/filters.html
new file mode 100644
index 00000000..18160298
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/people/filters.html
@@ -0,0 +1,44 @@
+{{/* People Filters - Category filter buttons */}}
+
+<div class="people-filters">
+  <input type="text"
+         id="quicksearch"
+         placeholder="Search people..."
+         aria-label="Search people"
+         x-model="searchQuery" />
+
+  <div>
+    <button @click="activeFilter = '*'"
+            :class="{ 'is-checked': activeFilter === '*' }">
+      show all
+    </button>
+    <button @click="activeFilter = 'leadership'"
+            :class="{ 'is-checked': activeFilter === 'leadership' }">
+      leadership
+    </button>
+    <button @click="activeFilter = 'editor'"
+            :class="{ 'is-checked': activeFilter === 'editor' }">
+      editorial team
+    </button>
+    <button @click="activeFilter = 'reviewer'"
+            :class="{ 'is-checked': activeFilter === 'reviewer' }">
+      reviewers
+    </button>
+    <button @click="activeFilter = 'maintainer'"
+            :class="{ 'is-checked': activeFilter === 'maintainer' }">
+      maintainers
+    </button>
+    <button @click="activeFilter = 'peer-review-guide'"
+            :class="{ 'is-checked': activeFilter === 'peer-review-guide' }">
+      peer review guide
+    </button>
+    <button @click="activeFilter = 'package-guide'"
+            :class="{ 'is-checked': activeFilter === 'package-guide' }">
+      packaging guide
+    </button>
+    <button @click="activeFilter = 'web-contrib'"
+            :class="{ 'is-checked': activeFilter === 'web-contrib' }">
+      website
+    </button>
+  </div>
+</div>
diff --git a/themes/clean-hugo/layouts/partials/people/grid.html b/themes/clean-hugo/layouts/partials/people/grid.html
new file mode 100644
index 00000000..c5d240e7
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/people/grid.html
@@ -0,0 +1,63 @@
+{{/* People Grid - AlpineJS filterable grid */}}
+
+<div class="people-grid">
+  <template x-for="person in filteredPeople" :key="person.github_username || person.name">
+    <div class="people_card">
+      <div>
+        <template x-if="person.github_image_id">
+          <div class="people_card__image">
+            <img :src="`https://avatars1.githubusercontent.com/u/${person.github_image_id}?s=400&v=4`"
+                 :alt="`GitHub photo of ${person.name || person.github_username}`">
+          </div>
+        </template>
+
+        <div class="people_card__content">
+          <h3>
+            <template x-if="person.github_username">
+              <a :href="`https://github.com/${person.github_username}`" rel="noopener noreferrer" x-text="person.name || `@${person.github_username}`"></a>
+            </template>
+            <template x-if="!person.github_username">
+              <span x-text="person.name"></span>
+            </template>
+          </h3>
+
+          <template x-if="person.title">
+            <div class="people_card__title" x-text="Array.isArray(person.title) ? person.title.join(', ') : person.title"></div>
+          </template>
+
+          <template x-if="person.organization">
+            <div class="people_card__org" x-text="person.organization"></div>
+          </template>
+
+          <div class="people_card__social">
+            <template x-if="person.twitter">
+              <a :href="`https://www.twitter.com/${person.twitter}`" rel="noopener noreferrer" aria-label="Twitter">
+                <i class="fab fa-twitter" aria-hidden="true"></i>
+              </a>
+            </template>
+            <template x-if="person.github_username">
+              <a :href="`https://github.com/${person.github_username}`" rel="noopener noreferrer" aria-label="GitHub">
+                <i class="fab fa-github" aria-hidden="true"></i>
+              </a>
+            </template>
+            <template x-if="person.website">
+              <a :href="person.website" rel="noopener noreferrer" aria-label="Website">
+                <i class="fas fa-blog" aria-hidden="true"></i>
+              </a>
+            </template>
+            <template x-if="person.orcidid">
+              <a :href="`https://orcid.org/${person.orcidid}`" rel="noopener noreferrer" aria-label="ORCID">
+                <i class="fab fa-orcid" aria-hidden="true"></i>
+              </a>
+            </template>
+            <template x-if="person.mastodon">
+              <a :href="person.mastodon" rel="noopener noreferrer" aria-label="Mastodon">
+                <i class="fab fa-mastodon" aria-hidden="true"></i>
+              </a>
+            </template>
+          </div>
+        </div>
+      </div>
+    </div>
+  </template>
+</div>
diff --git a/themes/clean-hugo/layouts/partials/plant-card.html b/themes/clean-hugo/layouts/partials/plant-card.html
new file mode 100644
index 00000000..c7666d47
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/plant-card.html
@@ -0,0 +1,61 @@
+{{/* Compatibility partial for plants - uses same styling as gallery-card but with plant-specific structure */}}
+{{ $isVariety := false }}
+{{ $page := . }}
+{{ $plant := dict }}
+
+{{ if reflect.IsMap . }}
+    {{ $isVariety = true }}
+    {{ $page = .Page }}
+    {{ $plant = .Plant }}
+{{ end }}
+
+{{ $groups := "" }}
+{{ with $page.Params.groups }}
+  {{ $groups = delimit . " " }}
+{{ else }}
+  {{ if $page.Params.group }}
+    {{ $groups = $page.Params.group }}
+  {{ end }}
+{{ end }}
+
+<article class="gallery-card plant-card" data-groups='{{ $groups }}'>
+  {{ $img := "" }}
+
+  {{ if $isVariety }}
+    <!-- Variety: use thumbnail from frontmatter -->
+    {{ with $plant.thumbnail }}
+      {{ $img = $page.Resources.GetMatch . }}
+    {{ end }}
+  {{ else }}
+    <!-- Regular page: use hero image or first image -->
+    {{ with $page.Params.hero }}
+      {{ with .image }}
+        {{ $img = $page.Resources.GetMatch . }}
+      {{ end }}
+    {{ end }}
+  {{ end }}
+
+  <!-- Fallback: grab first image -->
+  {{ if not $img }}
+    {{ $all := $page.Resources.Match "*.{png,jpg,jpeg,gif,webp}" }}
+    {{ if gt (len $all) 0 }}
+      {{ $img = index $all 0 }}
+    {{ end }}
+  {{ end }}
+
+  {{ $title := cond $isVariety $plant.name $page.Title }}
+
+  <a href="{{ $page.RelPermalink }}" class="gallery-card__link group" aria-label="{{ $title }}">
+    {{ with $img }}
+      {{ $thumb := .Fill "750x500 center" }}
+
+      <div class="gallery-card__image">
+        <img src="{{ $thumb.RelPermalink }}" alt="{{ $title }}" loading="lazy">
+      </div>
+    {{ end }}
+
+    <div class="gallery-card__content">
+      <h3 class="gallery-card__title">{{ $title }}</h3>
+    </div>
+  </a>
+</article>
diff --git a/themes/clean-hugo/layouts/partials/plant-gallery.html b/themes/clean-hugo/layouts/partials/plant-gallery.html
new file mode 100644
index 00000000..7484eddc
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/plant-gallery.html
@@ -0,0 +1,84 @@
+{{/* Compatibility partial for plants section - uses plant-card instead of gallery-card */}}
+{{ $ctx := . }}
+{{ $pages := .Pages }}
+{{ if reflect.IsMap $ctx }}
+  {{ with $ctx.Pages }}
+    {{ $pages = . }}
+  {{ end }}
+{{ end }}
+
+<div class="gallery-grid-container">
+  {{ if and (reflect.IsMap $ctx) $ctx.Title }}
+    <h2 class="gallery-grid__title">{{ $ctx.Title }}</h2>
+  {{ end }}
+
+  {{/* Step 1: Build species map and count plants */}}
+  {{ $speciesMap := dict }}
+  {{ $singles := slice }}
+
+  {{ range $pages }}
+    {{ $species := .Params.category | default "" }}
+    {{ if .Params.plants }}
+      {{/* Page has varieties */}}
+      {{ $plantCount := len .Params.plants }}
+      {{ if ge $plantCount 2 }}
+        {{/* 2+ plants = gets its own section */}}
+        {{ $existing := slice }}
+        {{ with index $speciesMap $species }}
+          {{ $existing = . }}
+        {{ end }}
+        {{ $speciesMap = merge $speciesMap (dict $species ($existing | append .)) }}
+      {{ else }}
+        {{/* Only 1 plant = treat as single */}}
+        {{ $singles = $singles | append . }}
+      {{ end }}
+    {{ else }}
+      {{/* No varieties = single plant */}}
+      {{ $singles = $singles | append . }}
+    {{ end }}
+  {{ end }}
+
+  {{/* Step 2: Render grouped sections alphabetically */}}
+  {{ $speciesList := slice }}
+  {{ range $key, $val := $speciesMap }}
+    {{ $speciesList = $speciesList | append $key }}
+  {{ end }}
+  {{ $sortedSpecies := sort $speciesList }}
+  {{ range $species := $sortedSpecies }}
+    {{ $speciesPages := index $speciesMap $species }}
+    <section class="gallery-grid__section">
+      <h3 class="gallery-grid__category-title">{{ $species }}</h3>
+      <div class="gallery-grid__items">
+        {{ range $speciesPages }}
+          {{ $parentPage := . }}
+          {{/* Sort plants by name */}}
+          {{ $sortedPlants := sort .Params.plants "name" }}
+          {{ range $sortedPlants }}
+            {{ partial "plant-card.html" (dict "Page" $parentPage "Plant" . "IsVariety" true) }}
+          {{ end }}
+        {{ end }}
+      </div>
+    </section>
+  {{ end }}
+
+  {{/* Step 3: Render singles as "Other Hoyas" */}}
+  {{ if gt (len $singles) 0 }}
+    <section class="gallery-grid__section">
+      <h3 class="gallery-grid__category-title">{{ .Site.Params.gallery.otherTitle | default "Other Hoyas" }}</h3>
+      <div class="gallery-grid__items">
+        {{ range sort $singles "Title" }}
+          {{ if .Params.plants }}
+            {{/* Single variety page */}}
+            {{ $parentPage := . }}
+            {{ range .Params.plants }}
+              {{ partial "plant-card.html" (dict "Page" $parentPage "Plant" . "IsVariety" true) }}
+            {{ end }}
+          {{ else }}
+            {{/* Regular single plant */}}
+            {{ partial "plant-card.html" . }}
+          {{ end }}
+        {{ end }}
+      </div>
+    </section>
+  {{ end }}
+</div>
diff --git a/themes/clean-hugo/layouts/partials/section-hero.html b/themes/clean-hugo/layouts/partials/section-hero.html
new file mode 100644
index 00000000..baee5889
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/section-hero.html
@@ -0,0 +1,14 @@
+{{/*
+  Section listing hero — shared by blog and events index pages.
+  Expects .Params.header.overlay_image, .Title, .Description.
+*/}}
+{{ $headerImg := .Params.header.overlay_image | default "" }}
+<section
+  class="blog-hero{{ if $headerImg }} blog-hero--overlay{{ end }}"
+  {{ with $headerImg }}style="background-image: url('{{ . | relURL }}');"{{ end }}
+>
+  <div class="container">
+    <h1>{{ .Title }}</h1>
+    {{ with .Description }}<p class="blog-hero__lead">{{ . }}</p>{{ end }}
+  </div>
+</section>
diff --git a/themes/clean-hugo/layouts/partials/seo.html b/themes/clean-hugo/layouts/partials/seo.html
new file mode 100644
index 00000000..9784741f
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/seo.html
@@ -0,0 +1,484 @@
+{{/*
+  SEO Partial - Open Graph, Canonical URLs, and Article Metadata
+
+  Provides rich metadata for social sharing (LinkedIn, Discord, Slack, Mastodon, Bluesky, etc.)
+  and search engines.
+*/}}
+
+{{/* Determine page title */}}
+{{ $title := .Title }}
+{{ if .IsHome }}
+  {{ $title = .Site.Title }}
+{{ else }}
+  {{ $title = printf "%s | %s" .Title .Site.Title }}
+{{ end }}
+
+{{/* Determine description */}}
+{{ $description := .Description }}
+{{ if not $description }}
+  {{ if .Summary }}
+    {{ $description = .Summary | plainify | truncate 160 }}
+  {{ else }}
+    {{ $description = .Site.Params.tagline | default .Site.Params.description }}
+  {{ end }}
+{{ end }}
+
+{{/* Determine image for social sharing */}}
+{{ $img := partial "get-image.html" (dict "image" .Params.image "fallbackAlt" .Title) }}
+{{ $image := "" }}
+{{ $imageAlt := .Title }}
+{{ if $img.exists }}
+  {{ $image = $img.src | absURL }}
+  {{ $imageAlt = $img.alt }}
+{{ else if .Site.Params.seo.default_image }}
+  {{ $image = .Site.Params.seo.default_image | absURL }}
+{{ end }}
+
+{{/* Canonical URL */}}
+<link rel="canonical" href="{{ .Permalink }}">
+
+{{/* Noindex: set noindex: true in front matter to exclude page from search engines (default: indexed) */}}
+{{ with .Params.noindex }}
+  <meta name="robots" content="noindex, nofollow">
+{{ end }}
+
+{{/* Open Graph / Social Media Meta Tags */}}
+<meta property="og:title" content="{{ $title }}">
+<meta property="og:description" content="{{ $description }}">
+<meta property="og:url" content="{{ .Permalink }}">
+<meta property="og:site_name" content="{{ .Site.Title }}">
+<meta property="og:locale" content="{{ .Site.LanguageCode | default "en_US" }}">
+
+{{ if $image }}
+<meta property="og:image" content="{{ $image }}">
+<meta property="og:image:alt" content="{{ $imageAlt }}">
+{{ end }}
+
+{{/* Content type specific tags */}}
+{{ if .IsPage }}
+  {{ if eq .Section "blog" }}
+    <meta property="og:type" content="article">
+    <meta property="article:published_time" content="{{ .Date.Format "2006-01-02T15:04:05Z07:00" }}">
+    {{ with .Lastmod }}
+      <meta property="article:modified_time" content="{{ .Format "2006-01-02T15:04:05Z07:00" }}">
+    {{ end }}
+    {{ with .Params.author }}
+      <meta property="article:author" content="{{ . }}">
+    {{ end }}
+    {{ with .Params.category }}
+      <meta property="article:section" content="{{ . }}">
+    {{ end }}
+    {{ range .Params.tags }}
+      <meta property="article:tag" content="{{ . }}">
+    {{ end }}
+  {{ else }}
+    <meta property="og:type" content="website">
+  {{ end }}
+{{ else }}
+  <meta property="og:type" content="website">
+{{ end }}
+
+{{/* Additional SEO meta tags */}}
+{{ with .Site.Params.author }}
+  <meta name="author" content="{{ . }}">
+{{ end }}
+
+{{ if .IsPage }}
+  <meta name="date" content="{{ .Date.Format "2006-01-02" }}">
+  {{ with .Lastmod }}
+    <meta name="last-modified" content="{{ .Format "2006-01-02" }}">
+  {{ end }}
+{{ end }}
+
+{{/* Keywords if provided */}}
+{{ with .Params.tags }}
+  <meta name="keywords" content="{{ delimit . ", " }}">
+{{ end }}
+
+{{/*
+  JSON-LD structured data (Organization or Person).
+  Current practice: Schema.org types with url, logo (Organization), sameAs for social links.
+  Set params.social.type to "Organization" (default) or "Person".
+  For Person, set params.social.name; sameAs is built from params.social URL values (github, linkedin, etc.).
+*/}}
+{{ $schemaType := .Site.Params.social.type | default "Organization" }}
+{{ $sameAs := slice }}
+{{ range $key, $val := .Site.Params.social }}
+  {{ $v := printf "%v" $val }}
+  {{ if and (ne $key "type") (ne $key "name") (or (hasPrefix $v "http://") (hasPrefix $v "https://")) }}
+    {{ $sameAs = $sameAs | append $v }}
+  {{ end }}
+{{ end }}
+
+{{ $schemaName := .Site.Title }}
+{{ if eq $schemaType "Person" }}
+  {{ $schemaName = .Site.Params.social.name | default .Site.Title }}
+{{ end }}
+{{ $schema := dict "@context" "https://schema.org" "@type" $schemaType "name" $schemaName "url" ("" | absURL) }}
+{{ if $sameAs }}
+  {{ $schema = merge $schema (dict "sameAs" $sameAs) }}
+{{ end }}
+{{ if and (eq $schemaType "Organization") .Site.Params.seo.default_image }}
+  {{ $schema = merge $schema (dict "logo" (.Site.Params.seo.default_image | absURL)) }}
+{{ end }}
+
+<script type="application/ld+json">
+  {{ $schema | jsonify | safeJS }}
+</script>
+
+{{/*
+  BlogPosting JSON-LD for blog posts. Enables article rich results in Google (image, date, author in search).
+  See: https://developers.google.com/search/docs/appearance/structured-data/article
+*/}}
+{{ if and .IsPage (eq .Section "blog") }}
+  {{ $authorName := .Params.author | default .Site.Params.author | default .Site.Title }}
+  {{ $publisher := dict "@type" "Organization" "name" .Site.Title }}
+  {{ with .Site.Params.seo.default_image }}
+    {{ $publisher = merge $publisher (dict "logo" (dict "@type" "ImageObject" "url" (. | absURL))) }}
+  {{ end }}
+  {{ $article := dict "@context" "https://schema.org" "@type" "BlogPosting" "headline" .Title "url" .Permalink "datePublished" (.Date.Format "2006-01-02T15:04:05Z07:00") "author" (dict "@type" "Person" "name" $authorName) "publisher" $publisher }}
+  {{ with .Lastmod }}
+    {{ $article = merge $article (dict "dateModified" (.Format "2006-01-02T15:04:05Z07:00")) }}
+  {{ end }}
+  {{ if $image }}
+    {{ $article = merge $article (dict "image" $image) }}
+  {{ end }}
+  {{ with .Description }}
+    {{ $article = merge $article (dict "description" .) }}
+  {{ else }}
+    {{ with .Summary }}
+      {{ $article = merge $article (dict "description" (. | plainify | truncate 160)) }}
+    {{ end }}
+  {{ end }}
+<script type="application/ld+json">
+  {{ $article | jsonify | safeJS }}
+</script>
+{{ end }}
+
+{{/*
+  TechArticle JSON-LD for doc/tutorial pages. Enables article-style rich results.
+  Set tech_article: true on a page, or use [cascade] in hugo.toml to apply to whole paths (e.g. /lessons/, /peer-review/peer-review-guide/).
+  See: https://schema.org/TechArticle and https://developers.google.com/search/docs/appearance/structured-data/article
+*/}}
+{{ if and .IsPage .Params.tech_article }}
+  {{ $authorName := .Params.author | default .Site.Params.author | default .Site.Title }}
+  {{ $publisher := dict "@type" "Organization" "name" .Site.Title }}
+  {{ with .Site.Params.seo.default_image }}
+    {{ $publisher = merge $publisher (dict "logo" (dict "@type" "ImageObject" "url" (. | absURL))) }}
+  {{ end }}
+  {{ $tech := dict "@context" "https://schema.org" "@type" "TechArticle" "headline" .Title "url" .Permalink "datePublished" (.Date.Format "2006-01-02T15:04:05Z07:00") "author" (dict "@type" "Person" "name" $authorName) "publisher" $publisher }}
+  {{ with .Lastmod }}
+    {{ $tech = merge $tech (dict "dateModified" (.Format "2006-01-02T15:04:05Z07:00")) }}
+  {{ end }}
+  {{ if $image }}
+    {{ $tech = merge $tech (dict "image" $image) }}
+  {{ end }}
+  {{ with .Description }}
+    {{ $tech = merge $tech (dict "description" .) }}
+  {{ else }}
+    {{ with .Summary }}
+      {{ $tech = merge $tech (dict "description" (. | plainify | truncate 160)) }}
+    {{ end }}
+  {{ end }}
+<script type="application/ld+json">
+  {{ $tech | jsonify | safeJS }}
+</script>
+{{ end }}
+
+{{/*
+  HowTo JSON-LD for docs/tutorials with step-by-step content. Set howto: true and steps in front matter.
+  See: https://developers.google.com/search/docs/appearance/structured-data/how-to
+  Each step: name (required) and text or url (optional but recommended).
+*/}}
+{{ if and .IsPage .Params.howto .Params.steps }}
+  {{ $howToSteps := slice }}
+  {{ range $i, $s := .Params.steps }}
+    {{ $step := dict "@type" "HowToStep" "position" (add $i 1) "name" ($s.name | default (printf "Step %d" (add $i 1))) }}
+    {{ with $s.text }}
+      {{ $step = merge $step (dict "text" .) }}
+    {{ end }}
+    {{ with $s.url }}
+      {{ $step = merge $step (dict "url" (. | absURL)) }}
+    {{ end }}
+    {{ $howToSteps = $howToSteps | append $step }}
+  {{ end }}
+  {{ $howTo := dict "@context" "https://schema.org" "@type" "HowTo" "name" .Title "url" .Permalink "step" $howToSteps }}
+  {{ with .Description }}
+    {{ $howTo = merge $howTo (dict "description" .) }}
+  {{ else }}
+    {{ with .Summary }}
+      {{ $howTo = merge $howTo (dict "description" (. | plainify | truncate 160)) }}
+    {{ end }}
+  {{ end }}
+  {{ if $image }}
+    {{ $howTo = merge $howTo (dict "image" $image) }}
+  {{ end }}
+  {{ with .Params.total_time }}
+    {{ $howTo = merge $howTo (dict "totalTime" .) }}
+  {{ end }}
+<script type="application/ld+json">
+  {{ $howTo | jsonify | safeJS }}
+</script>
+{{ end }}
+
+{{/*
+  LearningResource JSON-LD for lessons/tutorials with educational metadata.
+  Set learning_resource: true and optional skill_level, duration, prerequisites (and optionally teaches, learning_resource_type, educational_use) in front matter.
+  See: https://schema.org/LearningResource
+*/}}
+{{ if and .IsPage .Params.learning_resource }}
+  {{ $lr := dict "@context" "https://schema.org" "@type" "LearningResource" "name" .Title "url" .Permalink }}
+  {{ with .Description }}
+    {{ $lr = merge $lr (dict "description" .) }}
+  {{ else }}
+    {{ with .Summary }}
+      {{ $lr = merge $lr (dict "description" (. | plainify | truncate 160)) }}
+    {{ end }}
+  {{ end }}
+  {{ with .Params.skill_level }}
+    {{ $lr = merge $lr (dict "educationalLevel" .) }}
+  {{ end }}
+  {{ with .Params.duration }}
+    {{ $lr = merge $lr (dict "timeRequired" .) }}
+  {{ end }}
+  {{ with .Params.prerequisites }}
+    {{ $lr = merge $lr (dict "competencyRequired" .) }}
+  {{ end }}
+  {{ with .Params.author }}
+    {{ $lr = merge $lr (dict "author" (dict "@type" "Person" "name" .)) }}
+  {{ else }}
+    {{ with .Site.Params.author }}
+      {{ $lr = merge $lr (dict "author" (dict "@type" "Person" "name" .)) }}
+    {{ end }}
+  {{ end }}
+  {{ $lr = merge $lr (dict "datePublished" (.Date.Format "2006-01-02T15:04:05Z07:00")) }}
+  {{ with .Lastmod }}
+    {{ $lr = merge $lr (dict "dateModified" (.Format "2006-01-02T15:04:05Z07:00")) }}
+  {{ end }}
+  {{ if $image }}
+    {{ $lr = merge $lr (dict "image" $image) }}
+  {{ end }}
+  {{ with .Params.teaches }}
+    {{ $lr = merge $lr (dict "teaches" .) }}
+  {{ end }}
+  {{ with .Params.learning_resource_type }}
+    {{ $lr = merge $lr (dict "learningResourceType" .) }}
+  {{ end }}
+  {{ with .Params.educational_use }}
+    {{ $lr = merge $lr (dict "educationalUse" .) }}
+  {{ end }}
+<script type="application/ld+json">
+  {{ $lr | jsonify | safeJS }}
+</script>
+{{ end }}
+
+{{/*
+  SoftwareApplication JSON-LD for reviewed/listed packages (e.g. pyOpenSci packages, distinct from PyPI).
+  Set software_application: true and optional package_name, application_category, operating_system, software_version, same_as (PyPI/repo URL), author.
+  See: https://schema.org/SoftwareApplication
+*/}}
+{{ if and .IsPage .Params.software_application }}
+  {{ $name := .Params.package_name | default .Title }}
+  {{ $sa := dict "@context" "https://schema.org" "@type" "SoftwareApplication" "name" $name "url" .Permalink }}
+  {{ with .Description }}
+    {{ $sa = merge $sa (dict "description" .) }}
+  {{ else }}
+    {{ with .Summary }}
+      {{ $sa = merge $sa (dict "description" (. | plainify | truncate 160)) }}
+    {{ end }}
+  {{ end }}
+  {{ with .Params.application_category }}
+    {{ $sa = merge $sa (dict "applicationCategory" .) }}
+  {{ end }}
+  {{ with .Params.application_subcategory }}
+    {{ $sa = merge $sa (dict "applicationSubCategory" .) }}
+  {{ end }}
+  {{ with .Params.operating_system }}
+    {{ $sa = merge $sa (dict "operatingSystem" .) }}
+  {{ end }}
+  {{ with .Params.software_version }}
+    {{ $sa = merge $sa (dict "softwareVersion" .) }}
+  {{ end }}
+  {{ with .Params.same_as }}
+    {{ $sa = merge $sa (dict "sameAs" .) }}
+  {{ end }}
+  {{ with .Params.author }}
+    {{ $sa = merge $sa (dict "author" (dict "@type" "Person" "name" .)) }}
+  {{ else }}
+    {{ with .Site.Params.author }}
+      {{ $sa = merge $sa (dict "author" (dict "@type" "Organization" "name" .)) }}
+    {{ end }}
+  {{ end }}
+  {{ if $image }}
+    {{ $sa = merge $sa (dict "image" $image) }}
+  {{ end }}
+  {{ if .Params.offers_free }}
+    {{ $sa = merge $sa (dict "offers" (dict "@type" "Offer" "price" "0" "priceCurrency" "USD")) }}
+  {{ end }}
+<script type="application/ld+json">
+  {{ $sa | jsonify | safeJS }}
+</script>
+{{ end }}
+
+{{/*
+  VideoObject JSON-LD for pages with embedded YouTube/tutorial videos.
+  Set video_url (YouTube watch or youtu.be URL) or video_embed_url; optional video_title, video_description, video_upload_date, video_duration, video_thumbnail.
+  See: https://schema.org/VideoObject
+*/}}
+{{ if and .IsPage (or .Params.video_url .Params.video_embed_url) }}
+  {{ $embedUrl := .Params.video_embed_url }}
+  {{ $videoId := "" }}
+  {{ if .Params.video_url }}
+    {{ $ids := findRE "[a-zA-Z0-9_-]{11}" .Params.video_url }}
+    {{ if $ids }}{{ $videoId = index $ids 0 }}{{ end }}
+    {{ if and (not $embedUrl) $videoId }}
+      {{ $embedUrl = printf "https://www.youtube.com/embed/%s" $videoId }}
+    {{ end }}
+  {{ end }}
+  {{ if and $embedUrl (not $videoId) }}
+    {{ $ids := findRE "[a-zA-Z0-9_-]{11}" $embedUrl }}
+    {{ if $ids }}{{ $videoId = index $ids 0 }}{{ end }}
+  {{ end }}
+  {{ if $embedUrl }}
+    {{ $vo := dict "@context" "https://schema.org" "@type" "VideoObject" "name" (.Params.video_title | default .Title) "embedUrl" $embedUrl "url" .Permalink }}
+    {{ with .Params.video_description }}
+      {{ $vo = merge $vo (dict "description" .) }}
+    {{ else }}
+      {{ with .Description }}
+        {{ $vo = merge $vo (dict "description" .) }}
+      {{ else }}
+        {{ with .Summary }}
+          {{ $vo = merge $vo (dict "description" (. | plainify | truncate 160)) }}
+        {{ end }}
+      {{ end }}
+    {{ end }}
+    {{ with .Params.video_upload_date }}
+      {{ $vo = merge $vo (dict "uploadDate" .) }}
+    {{ end }}
+    {{ with .Params.video_duration }}
+      {{ $vo = merge $vo (dict "duration" .) }}
+    {{ end }}
+    {{ with .Params.video_thumbnail }}
+      {{ $vo = merge $vo (dict "thumbnailUrl" .) }}
+    {{ else }}
+      {{ if $videoId }}
+        {{ $vo = merge $vo (dict "thumbnailUrl" (printf "https://img.youtube.com/vi/%s/hqdefault.jpg" $videoId)) }}
+      {{ else }}
+        {{ if $image }}
+          {{ $vo = merge $vo (dict "thumbnailUrl" $image) }}
+        {{ end }}
+      {{ end }}
+    {{ end }}
+<script type="application/ld+json">
+  {{ $vo | jsonify | safeJS }}
+</script>
+  {{ end }}
+{{ end }}
+
+{{/*
+  ItemList JSON-LD for packages section index: lists all child pages that have software_application: true.
+  Enables "list of packages" rich result; only output on the section list page when it has such children.
+  See: https://schema.org/ItemList
+*/}}
+{{ if and .IsNode .Pages (eq .Section "packages") }}
+  {{ $packagePages := where .Pages "Params.software_application" true }}
+  {{ if gt (len $packagePages) 0 }}
+    {{ $listItems := slice }}
+    {{ range $i, $p := $packagePages }}
+      {{ $listItems = $listItems | append (dict "@type" "ListItem" "position" (add $i 1) "name" $p.Title "url" $p.Permalink) }}
+    {{ end }}
+    {{ $itemList := dict "@context" "https://schema.org" "@type" "ItemList" "name" (printf "%s - Accepted Packages" .Title) "numberOfItems" (len $listItems) "itemListElement" $listItems }}
+<script type="application/ld+json">
+  {{ $itemList | jsonify | safeJS }}
+</script>
+  {{ end }}
+{{ end }}
+
+{{/*
+  Event JSON-LD for event pages (workshops, meetups, conferences).
+  Use nested front matter under event: (start_date required; optional end_date, title, location_name, location_address, offers_free, price, organizer, topic, status).
+  See: https://schema.org/Event
+*/}}
+{{ $e := .Params.event }}
+{{ if and .IsPage $e $e.start_date }}
+  {{ $ev := dict "@context" "https://schema.org" "@type" "Event" "name" ($e.title | default .Title) "url" .Permalink "startDate" $e.start_date }}
+  {{ with $e.end_date }}
+    {{ $ev = merge $ev (dict "endDate" .) }}
+  {{ end }}
+  {{ with $e.location_name }}
+    {{ $location := dict "@type" "Place" "name" . }}
+    {{ with $e.location_address }}
+      {{ $location = merge $location (dict "address" (dict "@type" "PostalAddress" "streetAddress" .)) }}
+    {{ end }}
+    {{ $ev = merge $ev (dict "location" $location) }}
+  {{ else }}
+    {{ with $e.location }}
+      {{ $ev = merge $ev (dict "location" (dict "@type" "Place" "name" .)) }}
+    {{ end }}
+  {{ end }}
+  {{ if $e.offers_free }}
+    {{ $ev = merge $ev (dict "offers" (dict "@type" "Offer" "price" "0" "priceCurrency" "USD" "availability" "https://schema.org/InStock" "url" .Permalink)) }}
+  {{ else }}
+    {{ with $e.price }}
+      {{ $ev = merge $ev (dict "offers" (dict "@type" "Offer" "price" (printf "%v" .) "priceCurrency" ($e.price_currency | default "USD") "availability" "https://schema.org/InStock" "url" $.Permalink)) }}
+    {{ end }}
+  {{ end }}
+  {{ with $e.organizer }}
+    {{ $ev = merge $ev (dict "organizer" (dict "@type" "Organization" "name" .)) }}
+  {{ else }}
+    {{ with .Site.Params.author }}
+      {{ $ev = merge $ev (dict "organizer" (dict "@type" "Organization" "name" .)) }}
+    {{ end }}
+  {{ end }}
+  {{ with .Description }}
+    {{ $ev = merge $ev (dict "description" .) }}
+  {{ else }}
+    {{ with .Summary }}
+      {{ $ev = merge $ev (dict "description" (. | plainify | truncate 160)) }}
+    {{ end }}
+  {{ end }}
+  {{ if $image }}
+    {{ $ev = merge $ev (dict "image" $image) }}
+  {{ end }}
+  {{ with $e.status }}
+    {{ $ev = merge $ev (dict "eventStatus" .) }}
+  {{ end }}
+  {{ with $e.topic }}
+    {{ $ev = merge $ev (dict "about" (dict "@type" "Thing" "name" .)) }}
+  {{ end }}
+<script type="application/ld+json">
+  {{ $ev | jsonify | safeJS }}
+</script>
+{{ end }}
+
+{{/*
+  BreadcrumbList JSON-LD for all pages. Enables breadcrumb trail in search results.
+  See: https://developers.google.com/search/docs/appearance/structured-data/breadcrumb
+  .Ancestors is ordered from immediate parent toward root (home can appear last); we add Home first, then non-home ancestors, then current page.
+*/}}
+{{ $crumbItems := slice (dict "@type" "ListItem" "position" 1 "name" .Site.Title "item" ("" | absURL)) }}
+{{ $pos := 2 }}
+{{ range .Ancestors }}
+  {{ if not .IsHome }}
+    {{ $crumbItems = $crumbItems | append (dict "@type" "ListItem" "position" $pos "name" .Title "item" .Permalink) }}
+    {{ $pos = add $pos 1 }}
+  {{ end }}
+{{ end }}
+{{ if not .IsHome }}
+  {{ $crumbItems = $crumbItems | append (dict "@type" "ListItem" "position" $pos "name" .Title "item" .Permalink) }}
+{{ end }}
+{{ $breadcrumbSchema := dict "@context" "https://schema.org" "@type" "BreadcrumbList" "itemListElement" $crumbItems }}
+<script type="application/ld+json">
+  {{ $breadcrumbSchema | jsonify | safeJS }}
+</script>
+
+{{/*
+  Site verification (optional). Add verification codes in hugo.toml under [params.seo].
+  Google and Bing only.
+*/}}
+{{ with .Site.Params.seo.google_site_verification }}
+  <meta name="google-site-verification" content="{{ . }}">
+{{ end }}
+{{ with .Site.Params.seo.bing_site_verification }}
+  <meta name="msvalidate.01" content="{{ . }}">
+{{ end }}
diff --git a/themes/clean-hugo/layouts/partials/skip-link.html b/themes/clean-hugo/layouts/partials/skip-link.html
new file mode 100644
index 00000000..6b40b9c9
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/skip-link.html
@@ -0,0 +1,17 @@
+{{/*
+  Skip links for keyboard and screen-reader users.
+  Visually hidden until focused; targets main, nav, and footer.
+*/}}
+<nav class="skip-links" aria-label="Skip links">
+  <ul>
+    <li>
+      <a href="#site-nav" class="skip-link__link">Skip to primary navigation</a>
+    </li>
+    <li>
+      <a href="#main" class="skip-link__link">Skip to main content</a>
+    </li>
+    <li>
+      <a href="#footer" class="skip-link__link">Skip to footer</a>
+    </li>
+  </ul>
+</nav>
diff --git a/themes/clean-hugo/layouts/partials/swoosh-divider-bottom.html b/themes/clean-hugo/layouts/partials/swoosh-divider-bottom.html
new file mode 100644
index 00000000..ef52f0ff
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/swoosh-divider-bottom.html
@@ -0,0 +1,10 @@
+{{/* Curved divider at bottom of a swoosh section (wave down into next section). Pass theme: "purple" or "green" so fill matches the section above. SVG matches pyOpenSci div_purple_bottom (exact viewBox and paths). */}}
+{{ $theme := .theme | default "purple" }}
+<div class="swoosh-section__divider swoosh-section__divider--bottom swoosh-section__divider--{{ $theme }}" aria-hidden="true">
+  <svg class="swoosh-section__svg" viewBox="-0.042 0.1 180.142 24.439" xmlns="http://www.w3.org/2000/svg">
+    <g transform="matrix(1, 0, 0, 1, -18.298843383789062, -77.97396087646484)">
+      <path class="swoosh-section__wave swoosh-section__wave--1" d="M 31.874 78.826 L 191.94 77.978 L 192.165 98.254 C 192.165 98.254 160.131 84.016 132.538 85.529 C 110.196 86.754 77.759 95.255 77.759 95.255 C 77.759 95.255 55.729 98.884 43.288 93.365 C 30.846 87.847 31.874 78.826 31.874 78.826 Z"/>
+      <path class="swoosh-section__wave swoosh-section__wave--2" d="M 18.128 77.905 L 198.538 77.812 L 198.581 102.395 C 198.581 102.395 155.475 74.57 125.105 82.707 C 94.736 90.844 93.457 92.674 77.476 95.264 C 59.89 98.114 35.933 103.412 24.039 94.23 C 21.427 92.213 18.428 89.779 18.362 86.673 C 18.133 75.848 18.128 77.905 18.128 77.905 Z"/>
+    </g>
+  </svg>
+</div>
diff --git a/themes/clean-hugo/layouts/partials/swoosh-divider-top.html b/themes/clean-hugo/layouts/partials/swoosh-divider-top.html
new file mode 100644
index 00000000..33f72674
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/swoosh-divider-top.html
@@ -0,0 +1,8 @@
+{{/* Curved divider at top of a swoosh section (wave down from previous section). Pass theme: "purple" or "green" so fill matches the section below. */}}
+{{ $theme := .theme | default "purple" }}
+<div class="swoosh-section__divider swoosh-section__divider--top swoosh-section__divider--{{ $theme }}" aria-hidden="true">
+  <svg class="swoosh-section__svg" viewBox="0 0 181 21" xmlns="http://www.w3.org/2000/svg" preserveAspectRatio="none">
+    <path class="swoosh-section__wave swoosh-section__wave--1" d="m14.6 18.5 160 .9 6.4-16.8s-31.8 12.8-59.4 11.3c-22.3-1.2-54.8-9.7-54.8-9.7s-16.4-4.4-28.8 1.2-11.4 14.7-11.4 14.7Z"/>
+    <path class="swoosh-section__wave swoosh-section__wave--2" d="M.1 20.9h180.9V0c-1.2.6-43.5 22.4-73.4 13.7C77.2 6.8 53.3.2 39.6 0 21.4-.2.1 8.5 0 11.9c0 0 .1 9 .1 9Z"/>
+  </svg>
+</div>
diff --git a/themes/clean-hugo/layouts/partials/training-feature.html b/themes/clean-hugo/layouts/partials/training-feature.html
new file mode 100644
index 00000000..e7947b5e
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/training-feature.html
@@ -0,0 +1,52 @@
+{{/*
+  Promotional training / cohort strip. Reads Params.training_feature from the
+  page passed as "." (typically .Page). Use shortcode {{< training-feature />}}.
+  Fields: title (required), eyebrow, badge, excerpt, button_label, button_url,
+  image (src + alt), enabled (optional, default true).
+*/}}
+{{ $t := .Params.training_feature | default dict }}
+{{ if eq $t.enabled false }}{{ return }}{{ end }}
+{{ if not $t.title }}{{ return }}{{ end }}
+{{ $img := partial "get-image.html" (dict "image" $t.image "fallbackAlt" $t.title "page" .) }}
+{{ $btnHref := "" }}
+{{ with $t.button_url }}
+  {{ $btnHref = . }}
+  {{ if not (hasPrefix $btnHref "http") }}
+    {{ $btnHref = relURL $btnHref }}
+  {{ end }}
+{{ end }}
+
+<section class="training-feature" aria-labelledby="training-feature-title">
+  <div class="container">
+    <div class="training-feature__card">
+      <div class="training-feature__content">
+        {{ with $t.eyebrow }}
+          <p class="training-feature__eyebrow">{{ . }}</p>
+        {{ end }}
+        {{ with $t.badge }}
+          <p class="training-feature__badge"><span class="training-feature__badge-pill">{{ . }}</span></p>
+        {{ end }}
+        <h2 id="training-feature-title" class="training-feature__title">{{ $t.title }}</h2>
+        {{ with $t.excerpt }}
+          <div class="training-feature__excerpt">{{ . | markdownify }}</div>
+        {{ end }}
+        {{ if and $t.button_label $t.button_url }}
+          <p class="training-feature__actions">
+            <a class="btn btn--outline btn--lg" href="{{ $btnHref }}">{{ $t.button_label }}</a>
+          </p>
+        {{ end }}
+      </div>
+      {{ if $img.exists }}
+        <div class="training-feature__media">
+          <img
+            class="training-feature__image"
+            src="{{ $img.src | relURL }}"
+            alt="{{ $img.alt }}"
+            loading="lazy"
+            decoding="async"
+          />
+        </div>
+      {{ end }}
+    </div>
+  </div>
+</section>
diff --git a/themes/clean-hugo/layouts/partials/university-benefits-list.html b/themes/clean-hugo/layouts/partials/university-benefits-list.html
new file mode 100644
index 00000000..f6c061a3
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/university-benefits-list.html
@@ -0,0 +1,44 @@
+<ul class="benefits-list">
+  <li>
+    <i class="fa-solid fa-award" aria-hidden="true"></i>
+    <strong>Enhance grant competitiveness and compliance.</strong>
+    In the age of open science, funders increasingly require researchers to
+    publish code, data, and other artifacts openly to accelerate discovery. We
+    help your researchers learn practices that make scientific open source
+    reusable, maintainable, and easier for others to build upon, improving the
+    longevity and impact of research outputs.
+  </li>
+  <li>
+    <i class="fa-solid fa-robot" aria-hidden="true"></i>
+    <strong>Support the shift to responsible AI adoption.</strong>
+    Researchers increasingly rely on generative AI for scientific software
+    development, but many use these tools as workhorses instead of thoughtful
+    junior collaborators. Our courses help your researchers accelerate open
+    source innovation while preserving community trust and maintainer
+    sustainability. By collaborating with pyOpenSci, your institution stands
+    alongside industry experts to define best practices for generative AI in
+    open science.
+  </li>
+  <li>
+    <i class="fa-solid fa-people-group" aria-hidden="true"></i>
+    <strong>Learn alongside a global expert network.</strong>
+    Connect your community to a global network of experienced developers and
+    maintainers who build and maintain scientific Python packages, as well as
+    the researchers and professionals who use these tools every day.
+  </li>
+  <li>
+    <i class="fa-solid fa-hand-holding-heart" aria-hidden="true"></i>
+    <strong>Get real world, cross disciplinary support.</strong>
+    Receive guidance from experienced maintainers who regularly build and
+    maintain research software. Our training includes regular office hours that
+    facilitate hands on support so learners can ask questions and get help with
+    the problems that matter most to their work.
+  </li>
+  <li>
+    <i class="fa-solid fa-graduation-cap" aria-hidden="true"></i>
+    <strong>Complete a trusted curriculum.</strong>
+    Our programs have already supported more than 200 researchers with
+    practical open source development, contribution, and software development
+    skills through hands on, beginner friendly, and inclusive workshops.
+  </li>
+</ul>
diff --git a/themes/clean-hugo/layouts/partials/university-testimonials.html b/themes/clean-hugo/layouts/partials/university-testimonials.html
new file mode 100644
index 00000000..2e8973dc
--- /dev/null
+++ b/themes/clean-hugo/layouts/partials/university-testimonials.html
@@ -0,0 +1,62 @@
+{{- /* Flush-left HTML — indented output breaks when nested in swoosh_section RenderString */ -}}
+<section class="testimonial-showcase" aria-label="Quotes from Ship It course participants">
+<article class="testimonial-showcase__featured">
+<div class="testimonial-showcase__avatar-wrap">
+<img
+class="testimonial-showcase__avatar"
+src="{{ "images/people/testimonial-fatima-pardo.png" | relURL }}"
+width="160"
+height="160"
+alt="Portrait of Fatima, a Ship It course participant."
+loading="lazy"
+decoding="async"
+>
+</div>
+<div class="testimonial-showcase__featured-body">
+<p class="testimonial-showcase__mark" aria-hidden="true">
+<i class="fa-solid fa-quote-left"></i>
+</p>
+<blockquote class="testimonial-showcase__blockquote">
+<p>
+This week I presented my Python package 'PDBCleanV2' at the Structural
+Biology Departmental Retreat. It was well received by attendees and,
+overall, a great experience. I wanted to thank you because pyOpenSci
+was a great influence in getting my package in shape.
+</p>
+</blockquote>
+<p class="testimonial-showcase__cite">Fatima · Stanford University OSPO</p>
+</div>
+</article>
+<div class="testimonial-showcase__grid">
+<figure class="testimonial-showcase__card">
+<p class="testimonial-showcase__mark testimonial-showcase__mark--compact" aria-hidden="true">
+<i class="fa-solid fa-quote-left"></i>
+</p>
+<blockquote class="testimonial-showcase__blockquote">
+<p>
+My favorite part of the course has been the step-by-step guidance and
+the hands-on experience of building a package. I also really liked the
+videos where the mentor shares the challenges they faced — it made the
+process feel more real and relatable. Testing classmates' packages was
+another highlight, as it helped me learn from others and see different
+approaches.
+</p>
+</blockquote>
+<figcaption class="testimonial-showcase__cite">Course participant · Ship It cohort</figcaption>
+</figure>
+<figure class="testimonial-showcase__card">
+<p class="testimonial-showcase__mark testimonial-showcase__mark--compact" aria-hidden="true">
+<i class="fa-solid fa-quote-left"></i>
+</p>
+<blockquote class="testimonial-showcase__blockquote">
+<p>
+I attended a conference during this course (full day for two days) and
+was still able to complete the course once the conference ended. I
+appreciate the structure of the course, and the flexibility was also
+needed.
+</p>
+</blockquote>
+<figcaption class="testimonial-showcase__cite">Course participant · Ship It cohort</figcaption>
+</figure>
+</div>
+</section>
diff --git a/themes/clean-hugo/layouts/partners/single.html b/themes/clean-hugo/layouts/partners/single.html
new file mode 100644
index 00000000..68259e8f
--- /dev/null
+++ b/themes/clean-hugo/layouts/partners/single.html
@@ -0,0 +1,166 @@
+{{ define "main" }}
+
+{{/*
+  ⚠️ IMPORTANT: Package card markup in this file is DUPLICATED from layouts/partials/packages/grid.html
+  If you update card structure, links, badges, or styling:
+  1. Update layouts/partials/packages/grid.html (AlpineJS version with x-text, :href)
+  2. Update THIS file (Hugo version with {{ .field }})
+  See: /blog/2025-12-25-package-architecture/ for architecture details
+*/}}
+
+{{/* Get partner ID from front matter */}}
+{{ $partnerId := .Params.partner_id }}
+{{ $partnerName := .Params.partner_name | default $partnerId }}
+
+{{/* Filter packages for this partner */}}
+{{ $partnerPackages := slice }}
+{{ range .Site.Data.packages }}
+  {{ if and .partners (in .partners $partnerId) }}
+    {{ $partnerPackages = $partnerPackages | append . }}
+  {{ end }}
+{{ end }}
+
+{{/* Calculate metrics for partner packages */}}
+{{ $totalPackages := len $partnerPackages }}
+{{ $activePackages := 0 }}
+{{ $jossPackages := 0 }}
+{{ range $partnerPackages }}
+  {{ if .active }}{{ $activePackages = add $activePackages 1 }}{{ end }}
+  {{ if .joss }}{{ $jossPackages = add $jossPackages 1 }}{{ end }}
+{{ end }}
+
+{{/* Hero section */}}
+{{ partial "hero.html" . }}
+
+{{/* Metrics Bar */}}
+{{ $stats := slice
+    (printf "**%d** %s Packages" $totalPackages $partnerName)
+    (printf "**%d** Currently Active" $activePackages)
+    (printf "**%d** Published in JOSS" $jossPackages)
+}}
+{{ partial "metrics-bar-render.html" (dict "stats" $stats) }}
+
+{{/* Page content */}}
+<div class="packages-page__content">
+  <div class="container">
+    {{ .Content }}
+  </div>
+</div>
+
+{{/* Partner Packages Grid */}}
+{{ if gt $totalPackages 0 }}
+<section class="packages-page__section">
+  <div class="container">
+    <h2>{{ $partnerName }} Affiliated Packages</h2>
+
+    <div class="packages-grid">
+      {{ range $partnerPackages }}
+        {{ if .active }}
+          <div class="package_card">
+            <div>
+              <h3>{{ .package_name }}</h3>
+
+              <div class="package_card__meta">
+                <i class="fas fa-feather" aria-hidden="true"></i>
+                <span>
+                  {{ range $i, $m := .all_current_maintainers }}
+                    {{ if $i }}, {{ end }}{{ $m.name | default $m.github_username }}
+                  {{ end }}
+                </span>
+              </div>
+
+              <p>{{ .package_description }}</p>
+
+              <ul>
+                {{ with .repository_link }}
+                  <li><a href="{{ . }}" target="_blank"><i class="fab fa-github"></i> View Code</a></li>
+                {{ end }}
+
+                {{ with .gh_meta.documentation }}
+                  <li><a href="{{ . }}" target="_blank"><i class="fas fa-book-open"></i> View Docs</a></li>
+                {{ end }}
+
+                {{ with .issue_link }}
+                  <li><a href="{{ . }}" target="_blank"><i class="fa-solid fa-user-pen"></i> View Review</a></li>
+                {{ end }}
+
+                {{ with .joss }}
+                  <li><a href="{{ . }}" target="_blank"><i class="fas fa-bookmark"></i> JOSS Approved</a></li>
+                {{ end }}
+
+                {{ if in .partners "astropy" }}
+                  <li>
+                    <a href="https://www.astropy.org/affiliated/" target="_blank">
+                      <i class="fa-solid fa-check-double"></i>
+                      <img src="https://img.shields.io/badge/Affiliated-Astropy-orange.svg?style=flat" alt="Astropy Affiliated" class="partner-badge" />
+                    </a>
+                  </li>
+                {{ end }}
+              </ul>
+            </div>
+          </div>
+        {{ end }}
+      {{ end }}
+    </div>
+
+    {{/* Show archived packages if any */}}
+    {{ $archivedCount := 0 }}
+    {{ range $partnerPackages }}
+      {{ if not .active }}{{ $archivedCount = add $archivedCount 1 }}{{ end }}
+    {{ end }}
+
+    {{ if gt $archivedCount 0 }}
+      <h2 class="mt-12">Archived {{ $partnerName }} Packages</h2>
+      <p class="text-gray-600 mb-6">
+        Archived packages are no longer actively maintained but successfully completed peer review.
+      </p>
+      <div class="packages-grid">
+        {{ range $partnerPackages }}
+          {{ if not .active }}
+            <div class="package_card">
+              <div>
+                <h3>{{ .package_name }}</h3>
+
+                <div class="package_card__meta">
+                  <i class="fas fa-feather" aria-hidden="true"></i>
+                  <span>
+                    {{ range $i, $m := .all_current_maintainers }}
+                      {{ if $i }}, {{ end }}{{ $m.name | default $m.github_username }}
+                    {{ end }}
+                  </span>
+                </div>
+
+                <p>{{ .package_description }}</p>
+
+                <ul>
+                  {{ with .repository_link }}
+                    <li><a href="{{ . }}" target="_blank"><i class="fab fa-github"></i> View Code</a></li>
+                  {{ end }}
+
+                  <li class="package_card__archived">
+                    <i class="fa-solid fa-box-archive"></i> Archived
+                  </li>
+                </ul>
+              </div>
+            </div>
+          {{ end }}
+        {{ end }}
+      </div>
+    {{ end }}
+  </div>
+</section>
+{{ else }}
+<section class="packages-page__section">
+  <div class="container">
+    <p class="text-center text-gray-600">No packages found for this partner.</p>
+  </div>
+</section>
+{{ end }}
+
+<div class="container my-12 text-center">
+  <a href="/packages/" class="site-nav__button site-nav__button--primary">
+    View All Packages
+  </a>
+</div>
+
+{{ end }}
diff --git a/themes/clean-hugo/layouts/people/list.html b/themes/clean-hugo/layouts/people/list.html
new file mode 100644
index 00000000..9603d6b4
--- /dev/null
+++ b/themes/clean-hugo/layouts/people/list.html
@@ -0,0 +1,96 @@
+{{ define "main" }}
+
+{{ partial "hero.html" . }}
+
+<div class="people-page__content">
+  <div class="container">
+    {{ .Content }}
+  </div>
+</div>
+
+{{ if .Site.Data.contributors }}
+<div x-data="peopleFilter()" x-init="initPeople({{ .Site.Data.contributors | jsonify }})">
+
+  {{ $board := where .Site.Data.contributors "board" true }}
+  {{ if $board }}
+    <section class="people-page__section">
+      <div class="container">
+        <h2>Executive Council, Leadership & Staff</h2>
+        <div class="people-grid-static">
+          {{ range sort $board "sort" }}
+            {{ partial "people/card.html" . }}
+          {{ end }}
+        </div>
+      </div>
+    </section>
+  {{ end }}
+
+  {{ $advisory := where .Site.Data.contributors "advisory" true }}
+  {{ if $advisory }}
+    <section class="people-page__section">
+      <div class="container">
+        <h2>Advisory Council</h2>
+        <p>Advisory council members are volunteer experts who provide high-level guidance on the development of the organization.</p>
+        <div class="people-grid-static">
+          {{ range sort $advisory "sort" }}
+            {{ partial "people/card.html" . }}
+          {{ end }}
+        </div>
+      </div>
+    </section>
+  {{ end }}
+
+  {{ $editorial := where .Site.Data.contributors "editorial_board" true }}
+  {{ if $editorial }}
+    <section class="people-page__section">
+      <div class="container">
+        <h2>Editorial Board</h2>
+        <div class="people-grid-static">
+          {{ range sort $editorial "sort" }}
+            {{ partial "people/card.html" . }}
+          {{ end }}
+        </div>
+      </div>
+    </section>
+  {{ end }}
+
+  {{ $totalPeople := len .Site.Data.contributors }}
+  <section class="people-page__section">
+    <div class="container">
+      <h2>Community Contributors</h2>
+      <p>Our diverse and vibrant community! To date, <strong>{{ $totalPeople }}</strong> wonderful people have contributed.</p>
+
+      <div class="people-page__controls">
+        <div class="container">
+          {{ partial "people/filters.html" . }}
+        </div>
+      </div>
+
+      <div class="container">
+        {{ partial "people/grid.html" . }}
+      </div>
+    </div>
+  </section>
+
+  {{ $emeritus := where .Site.Data.contributors "emeritus_advisory" true }}
+  {{ if $emeritus }}
+    <section class="people-page__section full-width bg-primary">
+      <div class="container py-12">
+        <h2>Emeritus Leadership</h2>
+        <p>We are deeply grateful to these community members who have served on our Executive Council, Advisory Council, and Editorial Board. Their dedication and expertise have been instrumental in shaping our organization.</p>
+        <div class="people-grid-static">
+          {{ range sort $emeritus "sort" }}
+            {{ partial "people/card.html" . }}
+          {{ end }}
+        </div>
+      </div>
+    </section>
+  {{ end }}
+</div>
+{{ else }}
+<div class="people-page__empty container">
+  <p>No contributor data found. Add contributors to <code>data/contributors.yml</code> to display them here.</p>
+</div>
+{{ end }}
+
+{{ end }}
diff --git a/themes/clean-hugo/layouts/plants/list.html b/themes/clean-hugo/layouts/plants/list.html
new file mode 100644
index 00000000..48a4e768
--- /dev/null
+++ b/themes/clean-hugo/layouts/plants/list.html
@@ -0,0 +1,38 @@
+{{/* Compatibility layer: plants section uses gallery layouts */}}
+{{ define "main" }}
+  {{ partial "hero.html" . }}
+
+  <section class="gallery-list-wrapper">
+    <!-- Build unique group list from pages -->
+    {{ $seen := dict }}
+    {{ range .Pages.ByWeight.Reverse }}
+      {{ with .Params.groups }}
+        {{ range . }}
+          {{ if not (index $seen .) }}
+            {{ $seen = merge $seen (dict . true) }}
+          {{ end }}
+        {{ end }}
+      {{ else }}
+        {{ with .Params.group }}
+          {{ if not (index $seen .) }}
+            {{ $seen = merge $seen (dict . true) }}
+          {{ end }}
+        {{ end }}
+      {{ end }}
+    {{ end }}
+
+    <!-- Filter buttons -->
+    <div class="filter-row" role="tablist" aria-label="Filter plants by group">
+      <button class="filter-btn" data-filter="all" aria-pressed="true">All</button>
+      {{ range $k, $v := $seen }}
+        <button class="filter-btn" data-filter="{{ $k }}" aria-pressed="false">{{ humanize $k }}</button>
+      {{ end }}
+    </div>
+
+    <!-- Gallery - using plant-card for compatibility -->
+    {{ partial "plant-gallery.html" (dict "Pages" .Pages.ByWeight.Reverse "Title" .Title "Cols" 3) }}
+  </section>
+
+  <!-- Client-side filter -->
+  {{ partial "gallery-filter.html" (dict "cardSelector" ".gallery-card, .plant-card" "ariaLabel" "Filter plants by group") }}
+{{ end }}
diff --git a/themes/clean-hugo/layouts/plants/single.html b/themes/clean-hugo/layouts/plants/single.html
new file mode 100644
index 00000000..3ff193d7
--- /dev/null
+++ b/themes/clean-hugo/layouts/plants/single.html
@@ -0,0 +1,36 @@
+{{/* Compatibility layer: plants section uses gallery single layout */}}
+{{ define "main" }}
+  {{ partial "hero.html" . }}
+
+  <article class="gallery-content">
+    <div class="gallery-description prose">
+      {{ .Content }}
+    </div>
+
+    <section class="gallery-images">
+      <h2>Gallery</h2>
+      <div class="gallery-masonry">
+        {{ $images := .Resources.ByType "image" }}
+        {{ range $images }}
+          {{ $filename := .Name | replaceRE "\\.[^.]+$" "" | replaceRE "-" " " | title }}
+          {{ $caption := printf "%s · %s" $.Title $filename }}
+          <figure>
+            <a href="{{ .RelPermalink }}"
+                class="glightbox"
+                data-gallery="gallery-images"
+                data-glightbox="title: {{ $caption }};">
+              <img src="{{ .RelPermalink }}" alt="{{ or .Title $.Title }}" loading="lazy" style="image-orientation: from-image;">
+            </a>
+            <p class="gallery-caption">
+                {{ $caption }}
+            </p>
+          </figure>
+        {{ end }}
+      </div>
+    </section>
+  </article>
+{{ end }}
+
+{{ define "scripts" }}
+  {{ partial "glightbox-scripts.html" . }}
+{{ end }}
diff --git a/themes/clean-hugo/layouts/robots.txt b/themes/clean-hugo/layouts/robots.txt
new file mode 100644
index 00000000..d912046d
--- /dev/null
+++ b/themes/clean-hugo/layouts/robots.txt
@@ -0,0 +1,8 @@
+User-agent: *
+{{ if hugo.IsProduction }}
+Allow: /
+{{ else }}
+Disallow: /
+{{ end }}
+
+Sitemap: {{ "sitemap.xml" | absURL }}
diff --git a/themes/clean-hugo/layouts/shortcodes/admonition-quote.html b/themes/clean-hugo/layouts/shortcodes/admonition-quote.html
new file mode 100644
index 00000000..764dfb99
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/admonition-quote.html
@@ -0,0 +1,22 @@
+{{- $type := .Get "type" | default "note" -}}
+{{- $title := .Get "title" -}}
+{{- $author := .Get "author" -}}
+{{- $event := .Get "event" -}}
+{{- $typeClass := printf "admonition-quote--%s" $type -}}
+
+<div class="admonition-quote {{ $typeClass }}">
+  <div class="admonition-quote__mark" aria-hidden="true"></div>
+  <div class="admonition-quote__content">
+    {{- if $title -}}
+      <div class="admonition-quote__title">{{ $title }}</div>
+    {{- end -}}
+    <div class="admonition-quote__body">
+      {{ .Inner | markdownify }}
+    </div>
+    {{- if or $author $event -}}
+      <footer class="admonition-quote__footer">
+        {{- with $author -}}~ <strong>{{ . }}</strong>{{- end -}}{{- with $event -}}, <em>{{ . }}</em>{{- end -}}
+      </footer>
+    {{- end -}}
+  </div>
+</div>
diff --git a/themes/clean-hugo/layouts/shortcodes/admonition.html b/themes/clean-hugo/layouts/shortcodes/admonition.html
new file mode 100644
index 00000000..797c9afe
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/admonition.html
@@ -0,0 +1,30 @@
+{{- $type := .Get "type" | default "note" -}}
+{{- $title := .Get "title" -}}
+{{- $content := .Inner | markdownify -}}
+
+{{- $icons := dict
+  "info" `<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M13 16h-1v-4h-1m1-4h.01M21 12a9 9 0 11-18 0 9 9 0 0118 0z"></path></svg>`
+  "success" `<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M9 12l2 2 4-4m6 2a9 9 0 11-18 0 9 9 0 0118 0z"></path></svg>`
+  "warning" `<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M12 9v2m0 4h.01m-6.938 4h13.856c1.54 0 2.502-1.667 1.732-3L13.732 4c-.77-1.333-2.694-1.333-3.464 0L3.34 16c-.77 1.333.192 3 1.732 3z"></path></svg>`
+  "danger" `<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M10 14l2-2m0 0l2-2m-2 2l-2-2m2 2l2 2m7-2a9 9 0 11-18 0 9 9 0 0118 0z"></path></svg>`
+  "note" `<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M9 12h6m-6 4h6m2 5H7a2 2 0 01-2-2V5a2 2 0 012-2h5.586a1 1 0 01.707.293l5.414 5.414a1 1 0 01.293.707V19a2 2 0 01-2 2z"></path></svg>`
+-}}
+
+{{- $icon := index $icons $type | default (index $icons "note") -}}
+{{- $typeClass := printf "admonition--%s" $type -}}
+
+<div class="admonition {{ $typeClass }}">
+  <div class="admonition__icon">
+    {{ $icon | safeHTML }}
+  </div>
+  <div class="admonition__content">
+    {{- if $title -}}
+      <div class="admonition__title">
+        {{ $title }}
+      </div>
+    {{- end -}}
+    <div class="admonition__body">
+      {{ $content }}
+    </div>
+  </div>
+</div>
diff --git a/themes/clean-hugo/layouts/shortcodes/blog-list.html b/themes/clean-hugo/layouts/shortcodes/blog-list.html
new file mode 100644
index 00000000..d1c4d036
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/blog-list.html
@@ -0,0 +1,53 @@
+{{/*
+  Blog List Shortcode
+
+  Usage: {{< blog-list title="Recent Thoughts" limit=3 >}}
+
+  Parameters:
+  - title: Title for the blog section (default: "Recent Thoughts")
+  - limit: Number of posts to display (default: 3)
+*/}}
+<section class="blog-highlight">
+  <div class="container">
+    <div class="intro">
+      <h2>{{ .Get "title" | default "Recent Thoughts" }}</h2>
+    </div>
+
+    <div class="highlight-grid">
+      {{ $limit := .Get "limit" | default 3 | int }}
+      {{ $posts := sort (where .Site.RegularPages "Type" "blog") "Date" "desc" }}
+      {{ range first $limit $posts }}
+        {{ $topic := partial "blog-topic.html" . }}
+        <article class="listing-card listing-card--on-dark listing-card--density-default">
+          <div class="meta">
+            <time datetime="{{ .Date.Format "2006-01-02" }}">{{ .Date.Format "Jan 2, 2006" }}</time>
+            {{ with $topic.label }}
+              <span class="category">{{ . }}</span>
+            {{ end }}
+          </div>
+
+          <div class="content">
+            <h3>
+              <a href="{{ .Permalink }}">{{ .Title }}</a>
+            </h3>
+
+            <p class="excerpt">
+              {{ partial "blog-excerpt.html" (dict "." . "length" 200) }}
+            </p>
+
+            <a href="{{ .Permalink }}" class="read-more">
+              Read more <i class="fas fa-arrow-right"></i>
+            </a>
+          </div>
+        </article>
+      {{ end }}
+    </div>
+
+    <p class="blog-highlight__actions">
+      <a class="btn btn--green" href="{{ "/blog/" | relURL }}">
+        View more on the blog
+        <i class="fas fa-arrow-right" aria-hidden="true"></i>
+      </a>
+    </p>
+  </div>
+</section>
diff --git a/themes/clean-hugo/layouts/shortcodes/button.html b/themes/clean-hugo/layouts/shortcodes/button.html
new file mode 100644
index 00000000..73380201
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/button.html
@@ -0,0 +1,59 @@
+{{/*
+  Button Shortcode
+
+  Usage:
+    {{< button href="/packages/" variant="dark-purple" >}}View packages{{< /button >}}
+    {{< button href="/about/" variant="outline" size="lg" >}}Learn more{{< /button >}}
+    {{< button href="#" variant="green" icon="arrow-right" >}}Get started{{< /button >}}
+
+  Parameters:
+    - href (required): URL the button links to
+    - variant: dark-purple (default), white, green, light-purple, outline
+    - size: lg (optional; omit for default)
+    - icon: Font Awesome icon name (optional)
+    - iconPosition: left (default), right
+    - class: Additional CSS classes (optional)
+    - target: _blank for external links (optional)
+    - rel: Link relationship (optional, defaults to "noopener noreferrer" for target="_blank")
+*/}}
+
+{{ $href := .Get "href" | default "#" }}
+{{ $variant := .Get "variant" | default "dark-purple" }}
+{{ $size := .Get "size" | default "" }}
+{{ $icon := .Get "icon" | default "" }}
+{{ $iconPosition := .Get "iconPosition" | default "left" }}
+{{ $customClass := .Get "class" | default "" }}
+{{ $target := .Get "target" | default "" }}
+{{ $rel := .Get "rel" | default "" }}
+
+{{ if and (eq $target "_blank") (eq $rel "") }}
+  {{ $rel = "noopener noreferrer" }}
+{{ end }}
+
+{{ $classes := slice "btn" }}
+{{ $classes = $classes | append (printf "btn--%s" $variant) }}
+{{ if $size }}
+  {{ $classes = $classes | append (printf "btn--%s" $size) }}
+{{ end }}
+{{ if $icon }}
+  {{ $classes = $classes | append "btn--icon" }}
+{{ end }}
+{{ $brandIcons := slice "github" "gitlab" "bitbucket" "twitter" "x-twitter" "linkedin" "youtube" "mastodon" "orcid" "bluesky" }}
+{{ $iconPrefix := "fa-solid" }}
+{{ if in $brandIcons $icon }}{{ $iconPrefix = "fa-brands" }}{{ end }}
+{{ if $customClass }}
+  {{ $classes = $classes | append $customClass }}
+{{ end }}
+
+<a href="{{ $href }}"
+   class="{{ delimit $classes " " }}"
+   {{ with $target }}target="{{ . }}"{{ end }}
+   {{ with $rel }}rel="{{ . }}"{{ end }}>
+  {{ if and $icon (eq $iconPosition "left") }}
+    <i class="{{ $iconPrefix }} fa-{{ $icon }}" aria-hidden="true"></i>
+  {{ end }}
+  {{ .Inner }}
+  {{ if and $icon (eq $iconPosition "right") }}
+    <i class="{{ $iconPrefix }} fa-{{ $icon }}" aria-hidden="true"></i>
+  {{ end }}
+</a>
diff --git a/themes/clean-hugo/layouts/shortcodes/card.html b/themes/clean-hugo/layouts/shortcodes/card.html
new file mode 100644
index 00000000..13e18d2c
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/card.html
@@ -0,0 +1,24 @@
+{{/* Card shortcode - used inside two-card-row or standalone */}}
+{{ $title := .Get "title" | default "" }}
+{{ $icon := .Get "icon" | default "" }}
+{{ $content := .Inner }}
+
+<div class="card-shortcode">
+  <div>
+    {{ if $icon }}
+    <div class="card-shortcode__icon">
+      {{ if in $icon "fa-" }}
+        <i class="{{ $icon }}" aria-hidden="true"></i>
+      {{ else }}
+        {{ $icon }}
+      {{ end }}
+    </div>
+    {{ end }}
+    {{ if $title }}
+    <h3>{{ $title }}</h3>
+    {{ end }}
+    <div>
+      {{ $content | markdownify }}
+    </div>
+  </div>
+</div>
diff --git a/themes/clean-hugo/layouts/shortcodes/contributors.html b/themes/clean-hugo/layouts/shortcodes/contributors.html
new file mode 100644
index 00000000..865b7bfa
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/contributors.html
@@ -0,0 +1,7 @@
+{{ range sort .Site.Data.contributors "sort" }}
+    {{ $title := .title }}
+    {{ if reflect.IsSlice .title }}
+    {{ $title = delimit .title ", " }}
+    {{ end }}
+    {{ printf "* (%d) %s (%s)" .sort .name $title | markdownify }}
+{{ end }}
diff --git a/themes/clean-hugo/layouts/shortcodes/editorial-board.html b/themes/clean-hugo/layouts/shortcodes/editorial-board.html
new file mode 100644
index 00000000..f6794c3e
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/editorial-board.html
@@ -0,0 +1,43 @@
+{{/* Editorial board grids from data/contributors.yml */}}
+{{ $editorial := where .Site.Data.contributors "editorial_board" true }}
+{{ $emeritus := where .Site.Data.contributors "emeritus_editor" true }}
+
+{{ if $editorial }}
+<section class="people-page__section">
+  <div class="container">
+    <h2>Meet our editorial board</h2>
+    <p>
+      The pyOpenSci software peer review process is led by a volunteer team of
+      editors from the scientific Python community. Editors find reviewers from
+      diverse backgrounds, oversee each review, support authors and reviewers,
+      and decide whether a package is accepted into the pyOpenSci ecosystem.
+    </p>
+    <p>
+      <a class="btn btn--outline"
+         href="https://www.pyopensci.org/software-peer-review/how-to/editors-guide.html"
+         target="_blank" rel="noopener noreferrer">
+        Learn about the editor role
+      </a>
+    </p>
+    <div class="people-grid-static">
+      {{ range sort $editorial "sort" }}
+        {{ partial "people/card.html" . }}
+      {{ end }}
+    </div>
+  </div>
+</section>
+{{ end }}
+
+{{ if $emeritus }}
+<section class="people-page__section">
+  <div class="container">
+    <h2>Emeritus &amp; guest editors</h2>
+    <p>We are deeply grateful for those who served on our editorial board previously!</p>
+    <div class="people-grid-static">
+      {{ range sort $emeritus "sort" }}
+        {{ partial "people/card.html" . }}
+      {{ end }}
+    </div>
+  </div>
+</section>
+{{ end }}
diff --git a/themes/clean-hugo/layouts/shortcodes/feature-section.html b/themes/clean-hugo/layouts/shortcodes/feature-section.html
new file mode 100644
index 00000000..7ed55319
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/feature-section.html
@@ -0,0 +1,2 @@
+{{/* Shortcode to include feature section anywhere in content */}}
+{{ partial "feature-section.html" .Page }}
diff --git a/themes/clean-hugo/layouts/shortcodes/figure.html b/themes/clean-hugo/layouts/shortcodes/figure.html
new file mode 100644
index 00000000..3d68d132
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/figure.html
@@ -0,0 +1,19 @@
+{{- $src := .Get "src" -}}
+{{- $alt := .Get "alt" | default "" -}}
+{{- $caption := .Get "caption" -}}
+{{- $link := .Get "link" | default $src -}}
+
+{{- $base := replaceRE "\\.(jpg|jpeg|png|gif)$" "" $src -}}
+{{- $webp := printf "%s.webp" $base -}}
+
+<figure class="figure">
+  <a href="{{ $link | relURL }}" class="figure__link">
+    <picture class="figure__picture">
+      <source srcset="{{ $webp | relURL }}" type="image/webp">
+      <img src="{{ $src | relURL }}" alt="{{ $alt }}" class="figure__image">
+    </picture>
+  </a>
+  {{- if $caption -}}
+  <figcaption class="figure__caption">{{ $caption | markdownify }}</figcaption>
+  {{- end -}}
+</figure>
diff --git a/themes/clean-hugo/layouts/shortcodes/home-programs-full.html b/themes/clean-hugo/layouts/shortcodes/home-programs-full.html
new file mode 100644
index 00000000..01890d39
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/home-programs-full.html
@@ -0,0 +1,5 @@
+{{ $title := .Get "title" | default "Our programs are community powered" }}
+<section class="home-programs-full">
+  <h2>{{ $title }}</h2>
+  {{ partial "impact-cards.html" .Page }}
+</section>
diff --git a/themes/clean-hugo/layouts/shortcodes/impact-cards.html b/themes/clean-hugo/layouts/shortcodes/impact-cards.html
new file mode 100644
index 00000000..337ad90e
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/impact-cards.html
@@ -0,0 +1,2 @@
+{{/* Shortcode to include impact cards section anywhere in content */}}
+{{ partial "impact-cards.html" .Page }}
diff --git a/themes/clean-hugo/layouts/shortcodes/intro-section.html b/themes/clean-hugo/layouts/shortcodes/intro-section.html
new file mode 100644
index 00000000..d13b3a6a
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/intro-section.html
@@ -0,0 +1,2 @@
+{{/* Shortcode to include intro section anywhere in content */}}
+{{ partial "intro-section.html" .Page }}
diff --git a/themes/clean-hugo/layouts/shortcodes/masonry.html b/themes/clean-hugo/layouts/shortcodes/masonry.html
new file mode 100644
index 00000000..7d538963
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/masonry.html
@@ -0,0 +1,25 @@
+{{/*
+  Masonry Gallery Shortcode with Lightbox
+  Creates a responsive masonry layout for images using CSS columns
+  Includes GLightbox for click-to-zoom and image navigation
+
+  Usage:
+  {{< masonry >}}
+  ![Alt text](image1.jpg)
+  ![Alt text](image2.jpg)
+  {{< /masonry >}}
+
+  The shortcode will:
+  - Render images in a responsive masonry layout
+  - Add GLightbox classes for lightbox functionality with navigation
+  - Auto-orient images based on EXIF data
+  - Load GLightbox CSS/JS if not already loaded
+*/}}
+
+{{ .Page.Scratch.Set "hasGallery" true }}
+
+<div class="gallery-masonry">
+  {{ $content := .Inner | .Page.RenderString }}
+  {{ $content = replaceRE `<img src="([^"]+)" alt="([^"]*)"([^>]*)>` `<figure><a href="$1" class="glightbox" data-gallery="masonry-gallery" data-glightbox="title: $2"><img src="$1" alt="$2"$3 style="image-orientation: from-image;"></a></figure>` $content }}
+  {{ $content | safeHTML }}
+</div>
diff --git a/themes/clean-hugo/layouts/shortcodes/metrics-bar.html b/themes/clean-hugo/layouts/shortcodes/metrics-bar.html
new file mode 100644
index 00000000..f45584fe
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/metrics-bar.html
@@ -0,0 +1,8 @@
+{{/* Metrics bar shortcode - displays up to 4 stats with bold numbers and smaller text */}}
+{{ $stat1 := .Get "stat1" | default "" }}
+{{ $stat2 := .Get "stat2" | default "" }}
+{{ $stat3 := .Get "stat3" | default "" }}
+{{ $stat4 := .Get "stat4" | default "" }}
+
+{{ $stats := slice $stat1 $stat2 $stat3 $stat4 }}
+{{ partial "metrics-bar-render.html" (dict "stats" $stats) }}
diff --git a/themes/clean-hugo/layouts/shortcodes/partnership-cards.html b/themes/clean-hugo/layouts/shortcodes/partnership-cards.html
new file mode 100644
index 00000000..2b89dc83
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/partnership-cards.html
@@ -0,0 +1 @@
+{{ partial "partnership-cards.html" .Page }}
diff --git a/themes/clean-hugo/layouts/shortcodes/pullquote.html b/themes/clean-hugo/layouts/shortcodes/pullquote.html
new file mode 100644
index 00000000..2728c3bb
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/pullquote.html
@@ -0,0 +1,12 @@
+{{- $color := .Get "color" | default "teal" -}}
+{{- $author := .Get "author" -}}
+{{- $event := .Get "event" -}}
+
+<figure class="pullquote pullquote--{{ $color }}">
+  <p class="pullquote__text">{{ .Inner | markdownify }}</p>
+  {{ if or $author $event }}
+  <figcaption class="pullquote__footer">
+    {{ with $author }}<strong>~ {{ . }}</strong>{{ end }}{{ with $event }}, <em>{{ . }}</em>{{ end }}
+  </figcaption>
+  {{ end }}
+</figure>
diff --git a/themes/clean-hugo/layouts/shortcodes/recent-packages.html b/themes/clean-hugo/layouts/shortcodes/recent-packages.html
new file mode 100644
index 00000000..3f127800
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/recent-packages.html
@@ -0,0 +1,23 @@
+{{/* Recent accepted packages grid. Usage: {{< recent-packages limit="3" >}} */}}
+{{ $limit := .Get "limit" | default 3 | int }}
+{{ $packages := where .Site.Data.packages "active" true }}
+{{ $sorted := partial "packages/sort-by-date-accepted.html" (dict "packages" $packages) }}
+{{ $recent := first $limit $sorted }}
+
+{{ if gt (len $recent) 0 }}
+<section class="packages-page__section">
+  <div class="container">
+    <h2>Recently accepted Python packages</h2>
+    <div class="packages-grid">
+      {{ range $recent }}
+        {{ partial "packages/card-static.html" . }}
+      {{ end }}
+    </div>
+    <p>
+      <a class="btn btn--dark-purple" href="{{ "/python-packages/" | relURL }}">
+        View all accepted packages
+      </a>
+    </p>
+  </div>
+</section>
+{{ end }}
diff --git a/themes/clean-hugo/layouts/shortcodes/section-heading.html b/themes/clean-hugo/layouts/shortcodes/section-heading.html
new file mode 100644
index 00000000..b95def8c
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/section-heading.html
@@ -0,0 +1,10 @@
+{{/* Section heading shortcode - creates a prominent centered heading with subtitle */}}
+{{ $title := .Get "title" | default "Section Title" }}
+{{ $subtitle := .Get "subtitle" | default "" }}
+
+<div class="section-heading container">
+  <h2 class="section-heading__title">{{ $title }}</h2>
+  {{ if $subtitle }}
+  <div class="section-heading__subtitle">{{ $subtitle }}</div>
+  {{ end }}
+</div>
diff --git a/themes/clean-hugo/layouts/shortcodes/single-card-wide.html b/themes/clean-hugo/layouts/shortcodes/single-card-wide.html
new file mode 100644
index 00000000..0f91a14f
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/single-card-wide.html
@@ -0,0 +1,24 @@
+{{/* Single-card-wide shortcode - full-width card matching two-card-row width */}}
+{{ $title := .Get "title" | default "" }}
+{{ $icon := .Get "icon" | default "" }}
+<div class="single-card-wide">
+  <div class="container">
+    <div>
+      {{ if $icon }}
+      <div class="single-card-wide__icon">
+        {{ if in $icon "fa-" }}
+          <i class="{{ $icon }}" aria-hidden="true"></i>
+        {{ else }}
+          {{ $icon }}
+        {{ end }}
+      </div>
+    {{ end }}
+    {{ if $title }}
+    <h3>{{ $title }}</h3>
+    {{ end }}
+    <div class="single-card-wide__body">
+      {{ .Inner }}
+    </div>
+    </div>
+  </div>
+</div>
diff --git a/themes/clean-hugo/layouts/shortcodes/swoosh_section.html b/themes/clean-hugo/layouts/shortcodes/swoosh_section.html
new file mode 100644
index 00000000..8ddaa655
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/swoosh_section.html
@@ -0,0 +1,32 @@
+{{/* Block shortcode: full-width section with optional curved divider above/below.
+    Use layout="docs" for contained width (content column only; no sidebar bleed).
+    Inner content: markdown, shortcodes, or raw HTML. Use angle brackets. */}}
+{{- $bg := .Get "background" | default "white" -}}
+{{- $swoosh := .Get "swoosh" | default "none" -}}
+{{- $layout := .Get "layout" | default "" -}}
+{{- $theme := $bg -}}
+{{- $docsClass := "" -}}
+{{- if eq $layout "docs" }}{{ $docsClass = " swoosh-section--docs" }}{{ end -}}
+{{- $wrapDocsClass := "" -}}
+{{- if eq $layout "docs" }}{{ $wrapDocsClass = " swoosh-section__divider-wrap--docs" }}{{ end -}}
+
+{{- $inner := trim .Inner " \n\t\r" -}}
+{{- if eq $swoosh "top" -}}
+  <div class="swoosh-section__divider-wrap{{ $wrapDocsClass }}">
+    {{ partial "swoosh-divider-top.html" (dict "theme" $theme) }}
+  </div>
+{{- end -}}
+
+{{- if $inner -}}
+<section class="swoosh-section swoosh-section--{{ $bg }}{{ $docsClass }}">
+  <div class="swoosh-section__content">
+    {{ .Inner | .Page.RenderString }}
+  </div>
+</section>
+{{- end -}}
+
+{{- if eq $swoosh "bottom" -}}
+  <div class="swoosh-section__divider-wrap{{ $wrapDocsClass }}">
+    {{ partial "swoosh-divider-bottom.html" (dict "theme" $theme) }}
+  </div>
+{{- end -}}
diff --git a/themes/clean-hugo/layouts/shortcodes/theme-colors.html b/themes/clean-hugo/layouts/shortcodes/theme-colors.html
new file mode 100644
index 00000000..d8468eb1
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/theme-colors.html
@@ -0,0 +1,72 @@
+{{- /*
+  Renders all theme colors defined in the hugo.toml as color swatches.
+*/ -}}
+
+{{- $colors := .Site.Params.theme.colors | default dict -}}
+
+{{- /* Generate dynamic color classes for each theme color */ -}}
+<style>
+{{- range $name, $hex := $colors }}
+.color-{{ $name | urlize }} { background-color: {{ $hex }}; }
+{{- end }}
+</style>
+
+<h2>Base theme colors</h2>
+<div class="theme-colors">
+{{- range $name, $hex := $colors }}
+{{- if and (not (hasPrefix $name "admonition-")) (not (hasPrefix $name "link")) (not (hasPrefix $name "gray")) }}
+  <div>
+    <div class="color-{{ $name | urlize }}"></div>
+    <div>
+      <strong>{{ $name }}</strong>
+      <code>{{ $hex }}</code>
+    </div>
+  </div>
+{{- end }}
+{{- end }}
+</div>
+
+<h2>Link colors</h2>
+<div class="theme-colors">
+{{- range $name, $hex := $colors }}
+{{- if hasPrefix $name "link" }}
+  <div>
+    <div class="color-{{ $name | urlize }}"></div>
+    <div>
+      <strong>{{ $name }}</strong>
+      <code>{{ $hex }}</code>
+    </div>
+  </div>
+{{- end }}
+{{- end }}
+</div>
+
+<h2>Grey palette</h2>
+<div class="theme-colors">
+{{- range $name, $hex := $colors }}
+{{- if hasPrefix $name "gray" }}
+  <div>
+    <div class="color-{{ $name | urlize }}"></div>
+    <div>
+      <strong>{{ $name }}</strong>
+      <code>{{ $hex }}</code>
+    </div>
+  </div>
+{{- end }}
+{{- end }}
+</div>
+
+<h2>Admonition theme colors</h2>
+<div class="theme-colors">
+{{- range $name, $hex := $colors }}
+{{- if hasPrefix $name "admonition-" }}
+  <div>
+    <div class="color-{{ $name | urlize }}"></div>
+    <div>
+      <strong>{{ $name }}</strong>
+      <code>{{ $hex }}</code>
+    </div>
+  </div>
+{{- end }}
+{{- end }}
+</div>
diff --git a/themes/clean-hugo/layouts/shortcodes/training-feature.html b/themes/clean-hugo/layouts/shortcodes/training-feature.html
new file mode 100644
index 00000000..5c458c91
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/training-feature.html
@@ -0,0 +1 @@
+{{ partial "training-feature.html" .Page }}
diff --git a/themes/clean-hugo/layouts/shortcodes/tutorial-grid.html b/themes/clean-hugo/layouts/shortcodes/tutorial-grid.html
new file mode 100644
index 00000000..14f2f6f4
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/tutorial-grid.html
@@ -0,0 +1,30 @@
+{{/*
+  Tutorial grid — packaging tutorials from data/tutorials.yml
+  Usage: {{< tutorial-grid />}}
+*/}}
+{{ $tutorials := sort .Site.Data.tutorials "order" "asc" }}
+{{ if gt (len $tutorials) 0 }}
+<div class="tutorial-grid">
+  {{ range $tutorials }}
+  <article class="tutorial-grid__card">
+    <div class="tutorial-grid__body">
+      <h3 class="tutorial-grid__title">{{ .title }}</h3>
+      {{ with .excerpt }}
+      <p class="tutorial-grid__excerpt">{{ . }}</p>
+      {{ end }}
+    </div>
+    {{ with .link }}
+    <a
+      class="tutorial-grid__cta btn btn--dark-purple btn--lg"
+      href="{{ . }}"
+      target="_blank"
+      rel="noopener noreferrer"
+    >
+      <i class="fa-solid fa-magnifying-glass" aria-hidden="true"></i>
+      View tutorial
+    </a>
+    {{ end }}
+  </article>
+  {{ end }}
+</div>
+{{ end }}
diff --git a/themes/clean-hugo/layouts/shortcodes/two-card-row.html b/themes/clean-hugo/layouts/shortcodes/two-card-row.html
new file mode 100644
index 00000000..fd08b11a
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/two-card-row.html
@@ -0,0 +1,6 @@
+{{/* Two-card-row shortcode - wrapper for 2 cards side by side */}}
+<div class="two-card-row">
+  <div class="two-card-row__container container">
+    {{ .Inner }}
+  </div>
+</div>
diff --git a/themes/clean-hugo/layouts/shortcodes/university-benefits-list.html b/themes/clean-hugo/layouts/shortcodes/university-benefits-list.html
new file mode 100644
index 00000000..a6ecf572
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/university-benefits-list.html
@@ -0,0 +1 @@
+{{ partial "university-benefits-list.html" .Page }}
diff --git a/themes/clean-hugo/layouts/shortcodes/university-testimonials.html b/themes/clean-hugo/layouts/shortcodes/university-testimonials.html
new file mode 100644
index 00000000..9f22832d
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/university-testimonials.html
@@ -0,0 +1 @@
+{{ partial "university-testimonials.html" .Page }}
diff --git a/themes/clean-hugo/layouts/shortcodes/upcoming-events.html b/themes/clean-hugo/layouts/shortcodes/upcoming-events.html
new file mode 100644
index 00000000..5a071cad
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/upcoming-events.html
@@ -0,0 +1,8 @@
+{{ $limit := .Get "limit" | default 3 }}
+{{ $showViewAll := .Get "view_all" | default true }}
+{{ partial "events-upcoming.html" (dict
+  "context" .Page
+  "limit" (int $limit)
+  "show_kicker" false
+  "show_view_all" $showViewAll
+) }}
diff --git a/themes/clean-hugo/layouts/shortcodes/youtube.html b/themes/clean-hugo/layouts/shortcodes/youtube.html
new file mode 100644
index 00000000..d2a880a7
--- /dev/null
+++ b/themes/clean-hugo/layouts/shortcodes/youtube.html
@@ -0,0 +1,31 @@
+{{/* YouTube shortcode - supports full-width (default) or constrained width */}}
+{{ $fullWidth := .Get "full" | default "true" }}
+{{ $videoId := .Get "id" }}
+
+{{ if eq $fullWidth "false" }}
+  {{/* Constrained width - stays within content width */}}
+  <div class="youtube-container youtube-container--constrained">
+    <div class="youtube-wrapper">
+      <iframe
+        class="youtube-iframe"
+        src="https://www.youtube.com/embed/{{ $videoId }}"
+        frameborder="0"
+        allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+        allowfullscreen>
+      </iframe>
+    </div>
+  </div>
+{{ else }}
+  {{/* Full-width - breaks out of container */}}
+  <div class="youtube-container">
+    <div class="youtube-wrapper">
+      <iframe
+        class="youtube-iframe"
+        src="https://www.youtube.com/embed/{{ $videoId }}"
+        frameborder="0"
+        allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+        allowfullscreen>
+      </iframe>
+    </div>
+  </div>
+{{ end }}
diff --git a/themes/clean-hugo/layouts/splash.html b/themes/clean-hugo/layouts/splash.html
new file mode 100644
index 00000000..cefeeda9
--- /dev/null
+++ b/themes/clean-hugo/layouts/splash.html
@@ -0,0 +1,11 @@
+{{ define "main" }}
+
+
+{{ partial "hero.html" . }}
+
+<!-- Full-width body: not .content-main (65ch) so impact cards / metrics can use theme widths -->
+<div class="splash-page__content">
+  {{ .Content }}
+</div>
+
+{{ end }}
diff --git a/themes/clean-hugo/static/android-chrome-192x192.png b/themes/clean-hugo/static/android-chrome-192x192.png
new file mode 100644
index 00000000..d893ca4b
Binary files /dev/null and b/themes/clean-hugo/static/android-chrome-192x192.png differ
diff --git a/themes/clean-hugo/static/android-chrome-512x512.png b/themes/clean-hugo/static/android-chrome-512x512.png
new file mode 100644
index 00000000..0b8f9c2d
Binary files /dev/null and b/themes/clean-hugo/static/android-chrome-512x512.png differ
diff --git a/themes/clean-hugo/static/apple-touch-icon.png b/themes/clean-hugo/static/apple-touch-icon.png
new file mode 100644
index 00000000..fcc8b837
Binary files /dev/null and b/themes/clean-hugo/static/apple-touch-icon.png differ
diff --git a/themes/clean-hugo/static/css/syntax.css b/themes/clean-hugo/static/css/syntax.css
new file mode 100644
index 00000000..29203319
--- /dev/null
+++ b/themes/clean-hugo/static/css/syntax.css
@@ -0,0 +1,86 @@
+/* Background */ .bg { color: #f8f8f2; background-color: #272822; }
+/* PreWrapper */ .chroma { color: #f8f8f2; background-color: #272822; }
+/* Other */ .chroma .x {  }
+/* Error */ .chroma .err { color: #960050; background-color: #1e0010 }
+/* CodeLine */ .chroma .cl {  }
+/* LineLink */ .chroma .lnlinks { outline: none; text-decoration: none; color: inherit }
+/* LineTableTD */ .chroma .lntd { vertical-align: top; padding: 0; margin: 0; border: 0; }
+/* LineTable */ .chroma .lntable { border-spacing: 0; padding: 0; margin: 0; border: 0; }
+/* LineHighlight */ .chroma .hl { background-color: #ffffcc }
+/* LineNumbersTable */ .chroma .lnt { white-space: pre; -webkit-user-select: none; user-select: none; margin-right: 0.4em; padding: 0 0.4em 0 0.4em;color: #7f7f7f }
+/* LineNumbers */ .chroma .ln { white-space: pre; -webkit-user-select: none; user-select: none; margin-right: 0.4em; padding: 0 0.4em 0 0.4em;color: #7f7f7f }
+/* Line */ .chroma .line { display: flex; }
+/* Keyword */ .chroma .k { color: #66d9ef }
+/* KeywordConstant */ .chroma .kc { color: #66d9ef }
+/* KeywordDeclaration */ .chroma .kd { color: #66d9ef }
+/* KeywordNamespace */ .chroma .kn { color: #f92672 }
+/* KeywordPseudo */ .chroma .kp { color: #66d9ef }
+/* KeywordReserved */ .chroma .kr { color: #66d9ef }
+/* KeywordType */ .chroma .kt { color: #66d9ef }
+/* Name */ .chroma .n {  }
+/* NameAttribute */ .chroma .na { color: #a6e22e }
+/* NameBuiltin */ .chroma .nb {  }
+/* NameBuiltinPseudo */ .chroma .bp {  }
+/* NameClass */ .chroma .nc { color: #a6e22e }
+/* NameConstant */ .chroma .no { color: #66d9ef }
+/* NameDecorator */ .chroma .nd { color: #a6e22e }
+/* NameEntity */ .chroma .ni {  }
+/* NameException */ .chroma .ne { color: #a6e22e }
+/* NameFunction */ .chroma .nf { color: #a6e22e }
+/* NameFunctionMagic */ .chroma .fm {  }
+/* NameLabel */ .chroma .nl {  }
+/* NameNamespace */ .chroma .nn {  }
+/* NameOther */ .chroma .nx { color: #a6e22e }
+/* NameProperty */ .chroma .py {  }
+/* NameTag */ .chroma .nt { color: #f92672 }
+/* NameVariable */ .chroma .nv {  }
+/* NameVariableClass */ .chroma .vc {  }
+/* NameVariableGlobal */ .chroma .vg {  }
+/* NameVariableInstance */ .chroma .vi {  }
+/* NameVariableMagic */ .chroma .vm {  }
+/* Literal */ .chroma .l { color: #ae81ff }
+/* LiteralDate */ .chroma .ld { color: #e6db74 }
+/* LiteralString */ .chroma .s { color: #e6db74 }
+/* LiteralStringAffix */ .chroma .sa { color: #e6db74 }
+/* LiteralStringBacktick */ .chroma .sb { color: #e6db74 }
+/* LiteralStringChar */ .chroma .sc { color: #e6db74 }
+/* LiteralStringDelimiter */ .chroma .dl { color: #e6db74 }
+/* LiteralStringDoc */ .chroma .sd { color: #e6db74 }
+/* LiteralStringDouble */ .chroma .s2 { color: #e6db74 }
+/* LiteralStringEscape */ .chroma .se { color: #ae81ff }
+/* LiteralStringHeredoc */ .chroma .sh { color: #e6db74 }
+/* LiteralStringInterpol */ .chroma .si { color: #e6db74 }
+/* LiteralStringOther */ .chroma .sx { color: #e6db74 }
+/* LiteralStringRegex */ .chroma .sr { color: #e6db74 }
+/* LiteralStringSingle */ .chroma .s1 { color: #e6db74 }
+/* LiteralStringSymbol */ .chroma .ss { color: #e6db74 }
+/* LiteralNumber */ .chroma .m { color: #ae81ff }
+/* LiteralNumberBin */ .chroma .mb { color: #ae81ff }
+/* LiteralNumberFloat */ .chroma .mf { color: #ae81ff }
+/* LiteralNumberHex */ .chroma .mh { color: #ae81ff }
+/* LiteralNumberInteger */ .chroma .mi { color: #ae81ff }
+/* LiteralNumberIntegerLong */ .chroma .il { color: #ae81ff }
+/* LiteralNumberOct */ .chroma .mo { color: #ae81ff }
+/* Operator */ .chroma .o { color: #f92672 }
+/* OperatorWord */ .chroma .ow { color: #f92672 }
+/* Punctuation */ .chroma .p {  }
+/* Comment */ .chroma .c { color: #75715e }
+/* CommentHashbang */ .chroma .ch { color: #75715e }
+/* CommentMultiline */ .chroma .cm { color: #75715e }
+/* CommentSingle */ .chroma .c1 { color: #75715e }
+/* CommentSpecial */ .chroma .cs { color: #75715e }
+/* CommentPreproc */ .chroma .cp { color: #75715e }
+/* CommentPreprocFile */ .chroma .cpf { color: #75715e }
+/* Generic */ .chroma .g {  }
+/* GenericDeleted */ .chroma .gd { color: #f92672 }
+/* GenericEmph */ .chroma .ge { font-style: italic }
+/* GenericError */ .chroma .gr {  }
+/* GenericHeading */ .chroma .gh {  }
+/* GenericInserted */ .chroma .gi { color: #a6e22e }
+/* GenericOutput */ .chroma .go {  }
+/* GenericPrompt */ .chroma .gp {  }
+/* GenericStrong */ .chroma .gs { font-weight: bold }
+/* GenericSubheading */ .chroma .gu { color: #75715e }
+/* GenericTraceback */ .chroma .gt {  }
+/* GenericUnderline */ .chroma .gl {  }
+/* TextWhitespace */ .chroma .w {  }
diff --git a/themes/clean-hugo/static/favicon-16x16.png b/themes/clean-hugo/static/favicon-16x16.png
new file mode 100644
index 00000000..82b13d97
Binary files /dev/null and b/themes/clean-hugo/static/favicon-16x16.png differ
diff --git a/themes/clean-hugo/static/favicon-32x32.png b/themes/clean-hugo/static/favicon-32x32.png
new file mode 100644
index 00000000..34714b5d
Binary files /dev/null and b/themes/clean-hugo/static/favicon-32x32.png differ
diff --git a/themes/clean-hugo/static/favicon.ico b/themes/clean-hugo/static/favicon.ico
new file mode 100644
index 00000000..a0ca25a0
Binary files /dev/null and b/themes/clean-hugo/static/favicon.ico differ
diff --git a/themes/clean-hugo/static/fonts/Itim-Regular.woff2 b/themes/clean-hugo/static/fonts/Itim-Regular.woff2
new file mode 100644
index 00000000..bdde555b
Binary files /dev/null and b/themes/clean-hugo/static/fonts/Itim-Regular.woff2 differ
diff --git a/themes/clean-hugo/static/fonts/Lora-Italic-VariableFont_wght.woff2 b/themes/clean-hugo/static/fonts/Lora-Italic-VariableFont_wght.woff2
new file mode 100644
index 00000000..ef18fc47
Binary files /dev/null and b/themes/clean-hugo/static/fonts/Lora-Italic-VariableFont_wght.woff2 differ
diff --git a/themes/clean-hugo/static/fonts/NunitoSans-Italic-VariableFont.woff2 b/themes/clean-hugo/static/fonts/NunitoSans-Italic-VariableFont.woff2
new file mode 100644
index 00000000..425c6213
Binary files /dev/null and b/themes/clean-hugo/static/fonts/NunitoSans-Italic-VariableFont.woff2 differ
diff --git a/themes/clean-hugo/static/fonts/NunitoSans-VariableFont.woff2 b/themes/clean-hugo/static/fonts/NunitoSans-VariableFont.woff2
new file mode 100644
index 00000000..e7abd657
Binary files /dev/null and b/themes/clean-hugo/static/fonts/NunitoSans-VariableFont.woff2 differ
diff --git a/themes/clean-hugo/static/fonts/Poppins-Bold.woff2 b/themes/clean-hugo/static/fonts/Poppins-Bold.woff2
new file mode 100644
index 00000000..13e0e28b
Binary files /dev/null and b/themes/clean-hugo/static/fonts/Poppins-Bold.woff2 differ
diff --git a/themes/clean-hugo/static/fonts/Poppins-Italic.woff2 b/themes/clean-hugo/static/fonts/Poppins-Italic.woff2
new file mode 100644
index 00000000..0f4fa9bb
Binary files /dev/null and b/themes/clean-hugo/static/fonts/Poppins-Italic.woff2 differ
diff --git a/themes/clean-hugo/static/fonts/Poppins-Light.woff2 b/themes/clean-hugo/static/fonts/Poppins-Light.woff2
new file mode 100644
index 00000000..7eba2c4f
Binary files /dev/null and b/themes/clean-hugo/static/fonts/Poppins-Light.woff2 differ
diff --git a/themes/clean-hugo/static/fonts/Poppins-Medium.woff2 b/themes/clean-hugo/static/fonts/Poppins-Medium.woff2
new file mode 100644
index 00000000..406acb66
Binary files /dev/null and b/themes/clean-hugo/static/fonts/Poppins-Medium.woff2 differ
diff --git a/themes/clean-hugo/static/fonts/Poppins-Regular.woff2 b/themes/clean-hugo/static/fonts/Poppins-Regular.woff2
new file mode 100644
index 00000000..964d6d2f
Binary files /dev/null and b/themes/clean-hugo/static/fonts/Poppins-Regular.woff2 differ
diff --git a/themes/clean-hugo/static/fonts/Poppins-SemiBold.woff2 b/themes/clean-hugo/static/fonts/Poppins-SemiBold.woff2
new file mode 100644
index 00000000..9e4d0c0e
Binary files /dev/null and b/themes/clean-hugo/static/fonts/Poppins-SemiBold.woff2 differ
diff --git a/themes/clean-hugo/static/js/blog-filter.js b/themes/clean-hugo/static/js/blog-filter.js
new file mode 100644
index 00000000..7c94d0cd
--- /dev/null
+++ b/themes/clean-hugo/static/js/blog-filter.js
@@ -0,0 +1,96 @@
+/**
+ * Blog category filter — scoped to [data-blog-filter-root]
+ */
+(function() {
+  'use strict';
+
+  const HIDDEN_ITEM = 'blog-filter-hidden';
+  const HIDDEN_SECTION = 'blog-filter-section-hidden';
+
+  function sectionHasVisibleItems(section, category) {
+    if (!section) {
+      return false;
+    }
+
+    return Array.from(section.querySelectorAll('.blog-filter-item')).some((item) => {
+      const itemCategory = item.getAttribute('data-category') || '';
+      return category === 'all' || itemCategory === category;
+    });
+  }
+
+  function announceFilterChange(category) {
+    let liveRegion = document.getElementById('blog-filter-announcement');
+    if (!liveRegion) {
+      liveRegion = document.createElement('div');
+      liveRegion.id = 'blog-filter-announcement';
+      liveRegion.setAttribute('role', 'status');
+      liveRegion.setAttribute('aria-live', 'polite');
+      liveRegion.setAttribute('aria-atomic', 'true');
+      liveRegion.className = 'sr-only';
+      document.body.appendChild(liveRegion);
+    }
+
+    const visibleCount = document.querySelectorAll(
+      '.blog-filter-item:not(.' + HIDDEN_ITEM + ')'
+    ).length;
+    const label = category === 'all' ? 'all categories' : category.replace(/-/g, ' ');
+    liveRegion.textContent = 'Filtered to ' + label + '. Showing ' + visibleCount +
+      ' post' + (visibleCount !== 1 ? 's' : '') + '.';
+  }
+
+  function applyFilter(root, category) {
+    const buttons = root.querySelectorAll('.filter-btn[data-category]');
+    const items = root.querySelectorAll('.blog-filter-item');
+    const featuredSection = root.querySelector('.blog-grid__featured');
+    const gridSection = root.querySelector('.blog-grid__posts');
+    const archivesSection = root.querySelector('.blog-archives');
+
+    items.forEach((item) => {
+      const itemCategory = item.getAttribute('data-category') || '';
+      const show = category === 'all' || itemCategory === category;
+      item.classList.toggle(HIDDEN_ITEM, !show);
+    });
+
+    [featuredSection, gridSection, archivesSection].forEach((section) => {
+      if (!section) {
+        return;
+      }
+      section.classList.toggle(HIDDEN_SECTION, !sectionHasVisibleItems(section, category));
+    });
+
+    announceFilterChange(category);
+  }
+
+  function initBlogFilter() {
+    document.querySelectorAll('[data-blog-filter-root]').forEach((root) => {
+      const buttons = root.querySelectorAll('.filter-btn[data-category]');
+      const items = root.querySelectorAll('.blog-filter-item');
+
+      if (buttons.length === 0 || items.length === 0) {
+        return;
+      }
+
+      root.addEventListener('click', (event) => {
+        const button = event.target.closest('.filter-btn[data-category]');
+        if (!button || !root.contains(button)) {
+          return;
+        }
+
+        event.preventDefault();
+        const category = button.getAttribute('data-category');
+
+        buttons.forEach((btn) => {
+          btn.setAttribute('aria-pressed', btn === button ? 'true' : 'false');
+        });
+
+        applyFilter(root, category);
+      });
+    });
+  }
+
+  if (document.readyState === 'loading') {
+    document.addEventListener('DOMContentLoaded', initBlogFilter);
+  } else {
+    initBlogFilter();
+  }
+})();
diff --git a/themes/clean-hugo/static/js/docs-nav.js b/themes/clean-hugo/static/js/docs-nav.js
new file mode 100644
index 00000000..0d3dbdbc
--- /dev/null
+++ b/themes/clean-hugo/static/js/docs-nav.js
@@ -0,0 +1,149 @@
+/**
+ * Documentation Sidebar Navigation
+ * Automatically generates a table of contents from h2 and h3 headings
+ * and highlights the current section as you scroll
+ *
+ * Note: The main sidebar menu is now generated by Hugo partials
+ * This script handles the inline TOC that appears under the active page in the sidebar
+ */
+
+document.addEventListener('DOMContentLoaded', function() {
+  const docsContent = document.querySelector('.docs-content');
+  const scrollToTopBtn = document.getElementById('scroll-to-top');
+
+  if (!docsContent) return;
+
+  // Generate inline TOC from headings
+  function generateInlineToc() {
+    const tocContainer = document.querySelector('.toc-items');
+    if (!tocContainer) return; // Exit if inline TOC container doesn't exist
+
+    const headings = docsContent.querySelectorAll('h2, h3');
+    if (headings.length === 0) return;
+
+    let currentH2Item = null;
+    let currentH3List = null;
+
+    headings.forEach((heading, index) => {
+      // Add ID to heading if it doesn't have one
+      if (!heading.id) {
+        heading.id = `heading-${index}`;
+      }
+
+      const link = document.createElement('a');
+      link.href = `#${heading.id}`;
+      link.textContent = heading.textContent;
+      link.className = 'toc-link';
+
+      const listItem = document.createElement('li');
+      listItem.className = 'toc-item';
+      listItem.appendChild(link);
+
+      if (heading.tagName === 'H2') {
+        // Top level item
+        tocContainer.appendChild(listItem);
+        currentH2Item = listItem;
+        currentH3List = null;
+      } else if (heading.tagName === 'H3' && currentH2Item) {
+        // Nested item under h2
+        if (!currentH3List) {
+          currentH3List = document.createElement('ul');
+          currentH3List.className = 'toc-sublist';
+          currentH2Item.appendChild(currentH3List);
+        }
+        listItem.className = 'toc-item toc-item--sub';
+        currentH3List.appendChild(listItem);
+      }
+
+      // Smooth scroll on click
+      link.addEventListener('click', function(e) {
+        e.preventDefault();
+        const target = document.getElementById(heading.id);
+        if (target) {
+          target.scrollIntoView({ behavior: 'smooth', block: 'start' });
+          // Update URL without jumping
+          history.pushState(null, null, `#${heading.id}`);
+          // Update active state
+          updateActiveLink(link);
+        }
+      });
+    });
+  }
+
+  // Update active link based on scroll position
+  function updateActiveLink(activeLink = null) {
+    const tocContainer = document.querySelector('.toc-items');
+    if (!tocContainer) return; // Exit if inline TOC container doesn't exist
+
+    const links = tocContainer.querySelectorAll('.toc-link');
+
+    if (activeLink) {
+      // Manually set active link
+      links.forEach(link => link.classList.remove('toc-link--active'));
+      activeLink.classList.add('toc-link--active');
+      return;
+    }
+
+    // Auto-detect based on scroll position
+    const headings = docsContent.querySelectorAll('h2, h3');
+    let currentHeading = null;
+
+    headings.forEach(heading => {
+      const rect = heading.getBoundingClientRect();
+      if (rect.top <= 100) {
+        currentHeading = heading;
+      }
+    });
+
+    links.forEach(link => {
+      link.classList.remove('toc-link--active');
+      if (currentHeading && link.getAttribute('href') === `#${currentHeading.id}`) {
+        link.classList.add('toc-link--active');
+      }
+    });
+  }
+
+  // Show/hide scroll to top button
+  function toggleScrollButton() {
+    if (window.pageYOffset > 300) {
+      scrollToTopBtn.classList.add('docs-scroll-btn--visible');
+    } else {
+      scrollToTopBtn.classList.remove('docs-scroll-btn--visible');
+    }
+  }
+
+  // Scroll to top functionality
+  if (scrollToTopBtn) {
+    scrollToTopBtn.addEventListener('click', function() {
+      window.scrollTo({ top: 0, behavior: 'smooth' });
+    });
+  }
+
+  // Initialize - generate inline TOC
+  generateInlineToc();
+  updateActiveLink();
+
+  // Update on scroll (throttled)
+  let scrollTimeout;
+  window.addEventListener('scroll', function() {
+    if (scrollTimeout) {
+      window.cancelAnimationFrame(scrollTimeout);
+    }
+    scrollTimeout = window.requestAnimationFrame(function() {
+      updateActiveLink();
+      if (scrollToTopBtn) {
+        toggleScrollButton();
+      }
+    });
+  });
+
+  // Handle initial hash in URL
+  if (window.location.hash) {
+    setTimeout(function() {
+      const target = document.querySelector(window.location.hash);
+      if (target) {
+        target.scrollIntoView({ behavior: 'smooth' });
+      }
+    }, 100);
+  }
+});
diff --git a/themes/clean-hugo/static/js/docs-sidebar.js b/themes/clean-hugo/static/js/docs-sidebar.js
new file mode 100644
index 00000000..a7620612
--- /dev/null
+++ b/themes/clean-hugo/static/js/docs-sidebar.js
@@ -0,0 +1,81 @@
+/**
+ * Documentation Sidebar Mobile Toggle
+ * Handles slide-out drawer functionality on mobile devices (<768px)
+ *
+ * Features:
+ * - Toggle sidebar visibility with button
+ * - Semi-transparent overlay behind sidebar
+ * - Close on overlay click or ESC key
+ * - Desktop sidebar remains always visible (separate from mobile drawer)
+ */
+
+document.addEventListener('DOMContentLoaded', function() {
+  const docsSidebar = document.querySelector('.docs-sidebar');
+  const docsToggle = document.querySelector('.docs-toggle');
+  const overlay = document.querySelector('.overlay');
+
+  if (!docsSidebar || !docsToggle || !overlay) return;
+
+  /**
+   * Toggle sidebar and overlay visibility
+   */
+  function toggleSidebar() {
+    docsSidebar.classList.toggle('open');
+    overlay.classList.toggle('open');
+  }
+
+  /**
+   * Close sidebar and overlay
+   */
+  function closeSidebar() {
+    docsSidebar.classList.remove('open');
+    overlay.classList.remove('open');
+  }
+
+  /**
+   * Handle toggle button click
+   */
+  docsToggle.addEventListener('click', function(e) {
+    e.stopPropagation();
+    toggleSidebar();
+  });
+
+  /**
+   * Close sidebar when clicking overlay
+   */
+  overlay.addEventListener('click', function(e) {
+    e.stopPropagation();
+    closeSidebar();
+  });
+
+  /**
+   * Close sidebar when clicking links in the sidebar
+   */
+  const sidebarLinks = docsSidebar.querySelectorAll('a');
+  sidebarLinks.forEach(link => {
+    link.addEventListener('click', function() {
+      closeSidebar();
+    });
+  });
+
+  /**
+   * Close sidebar on ESC key press
+   */
+  document.addEventListener('keydown', function(e) {
+    if (e.key === 'Escape') {
+      closeSidebar();
+    }
+  });
+
+  /**
+   * Close sidebar when clicking on main content
+   */
+  const docsContent = document.querySelector('.docs-content');
+  if (docsContent) {
+    docsContent.addEventListener('click', function() {
+      if (overlay.classList.contains('open')) {
+        closeSidebar();
+      }
+    });
+  }
+});
diff --git a/themes/clean-hugo/static/js/navigation.js b/themes/clean-hugo/static/js/navigation.js
new file mode 100644
index 00000000..595128eb
--- /dev/null
+++ b/themes/clean-hugo/static/js/navigation.js
@@ -0,0 +1,64 @@
+/**
+ * Navigation JavaScript
+ * Handles mobile menu toggle and dropdown menu interactions
+ */
+
+(function() {
+  'use strict';
+
+  const toggle = document.querySelector('.site-nav__toggle');
+  const menu = document.querySelector('#site-nav-menu');
+
+  if (!toggle || !menu) {
+    return; // Navigation elements not found
+  }
+
+  // Toggle main menu
+  toggle.addEventListener('click', function() {
+    const isExpanded = toggle.getAttribute('aria-expanded') === 'true';
+    toggle.setAttribute('aria-expanded', !isExpanded);
+    menu.classList.toggle('site-nav__menu--open');
+  });
+
+  // Handle dropdown menus
+  const dropdowns = menu.querySelectorAll('.site-nav__dropdown');
+  dropdowns.forEach(function(dropdown) {
+    const dropdownToggle = dropdown.querySelector('.site-nav__link--dropdown');
+    const dropdownMenu = dropdown.querySelector('.site-nav__dropdown-menu');
+
+    if (dropdownToggle && dropdownMenu) {
+      dropdownToggle.addEventListener('click', function(e) {
+        // On mobile, toggle dropdown
+        if (window.innerWidth < 768) {
+          e.preventDefault();
+          const isOpen = dropdownMenu.classList.contains('site-nav__dropdown-menu--open');
+          // Toggle menu visibility
+          dropdownMenu.classList.toggle('site-nav__dropdown-menu--open');
+          // Toggle aria-expanded and update it based on new state
+          const newState = !isOpen;
+          dropdownToggle.setAttribute('aria-expanded', newState.toString());
+        }
+        // On desktop, let hover handle it
+      });
+    }
+  });
+
+  // Close menu when clicking outside
+  document.addEventListener('click', function(event) {
+    if (!toggle.contains(event.target) && !menu.contains(event.target)) {
+      toggle.setAttribute('aria-expanded', 'false');
+      menu.classList.remove('site-nav__menu--open');
+    }
+  });
+
+  // Close menu when clicking on a non-dropdown link (mobile)
+  const menuLinks = menu.querySelectorAll('.site-nav__link:not(.site-nav__link--dropdown), .site-nav__dropdown-link');
+  menuLinks.forEach(function(link) {
+    link.addEventListener('click', function() {
+      if (window.innerWidth < 768) {
+        toggle.setAttribute('aria-expanded', 'false');
+        menu.classList.remove('site-nav__menu--open');
+      }
+    });
+  });
+})();
diff --git a/themes/clean-hugo/static/js/package-filter.js b/themes/clean-hugo/static/js/package-filter.js
new file mode 100644
index 00000000..ad2a3388
--- /dev/null
+++ b/themes/clean-hugo/static/js/package-filter.js
@@ -0,0 +1,95 @@
+/**
+ * Package Filter - AlpineJS component
+ * Handles filtering and searching of cards that contain package data
+ *
+ * IMPORTANT: This script must load WITHOUT 'defer' attribute so it executes
+ * immediately and registers the 'alpine:init' listener before Alpine.js initializes.
+ */
+
+function normalizeAcceptanceDate(pkg) {
+  const accepted = pkg?.date_accepted;
+  if (accepted && accepted !== 'missing') {
+    const clean = String(accepted).replace(/\s/g, '');
+    const match = clean.match(/^(\d{4})-(\d{1,2})-(\d{1,2})/);
+    if (match) {
+      const [, year, month, day] = match;
+      return `${year}-${month.padStart(2, '0')}-${day.padStart(2, '0')}`;
+    }
+  }
+  return '0000-01-01';
+}
+
+function sortPackagesByAcceptanceDate(packages) {
+  return [...packages].sort((a, b) =>
+    normalizeAcceptanceDate(b).localeCompare(normalizeAcceptanceDate(a))
+  );
+}
+
+document.addEventListener('alpine:init', () => {
+  Alpine.data('packageFilter', () => ({
+    packages: [],
+    searchQuery: '',
+    activeFilter: '*',
+
+    initPackages(packageData) {
+      if (typeof packageData === 'string') {
+        try {
+          packageData = JSON.parse(packageData);
+        } catch (e) {
+          packageData = [];
+        }
+      }
+      this.packages = Array.isArray(packageData) ? packageData : [];
+    },
+
+    get activePackages() {
+      return this.filterPackages(true);
+    },
+
+    get archivedPackages() {
+      // Archived packages are never filtered - always show all
+      return this.packages.filter(pkg => pkg.active === false);
+    },
+
+    categoryMatches(pkg, filter) {
+      const cats = pkg.categories || [];
+      if (filter === 'data-munging') {
+        return cats.some(cat =>
+          cat === 'data-munging' ||
+          cat.includes('data-processing-munging')
+        );
+      }
+      if (filter === 'data-visualization') {
+        return cats.some(cat => cat.includes('data-visualization'));
+      }
+      return cats.some(cat =>
+        cat.includes(filter) ||
+        cat === filter.replace(/-/g, '_')
+      );
+    },
+
+    filterPackages(activeOnly) {
+      let filtered = this.packages;
+      filtered = filtered.filter(pkg => pkg.active === activeOnly);
+
+      if (this.activeFilter !== '*') {
+        filtered = filtered.filter(pkg => this.categoryMatches(pkg, this.activeFilter));
+      }
+
+      if (this.searchQuery.trim() !== '') {
+        const query = this.searchQuery.toLowerCase();
+        filtered = filtered.filter(pkg => {
+          const nameMatch = pkg.package_name?.toLowerCase().includes(query);
+          const descMatch = pkg.package_description?.toLowerCase().includes(query);
+          const maintainerMatch = pkg.all_current_maintainers?.some(m =>
+            m.name?.toLowerCase().includes(query) ||
+            m.github_username?.toLowerCase().includes(query)
+          );
+          return nameMatch || descMatch || maintainerMatch;
+        });
+      }
+
+      return sortPackagesByAcceptanceDate(filtered);
+    }
+  }));
+});
diff --git a/themes/clean-hugo/static/js/people-filter.js b/themes/clean-hugo/static/js/people-filter.js
new file mode 100644
index 00000000..3f6aa868
--- /dev/null
+++ b/themes/clean-hugo/static/js/people-filter.js
@@ -0,0 +1,52 @@
+/**
+ * People Filter - AlpineJS component
+ * Must load WITHOUT 'defer' to register before Alpine initializes
+ */
+
+document.addEventListener('alpine:init', () => {
+  Alpine.data('peopleFilter', () => ({
+    people: [],
+    searchQuery: '',
+    activeFilter: '*',
+
+    initPeople(peopleData) {
+      this.people = peopleData || [];
+    },
+
+    get filteredPeople() {
+      return this.filterPeople();
+    },
+
+    filterPeople() {
+      let filtered = this.people;
+
+      if (this.activeFilter !== '*') {
+        filtered = filtered.filter(person => {
+          return person.contributor_type && person.contributor_type.some(type =>
+            type === this.activeFilter || type === this.activeFilter.replace(/-/g, '_')
+          );
+        });
+      }
+
+      if (this.searchQuery.trim() !== '') {
+        const query = this.searchQuery.toLowerCase();
+        filtered = filtered.filter(person => {
+          const nameMatch = person.name?.toLowerCase().includes(query);
+          const orgMatch = person.organization?.toLowerCase().includes(query);
+          const titleMatch = person.title?.some(t => t.toLowerCase().includes(query));
+          const githubMatch = person.github_username?.toLowerCase().includes(query);
+          return nameMatch || orgMatch || titleMatch || githubMatch;
+        });
+      }
+
+      // Sort by sort field (default to 9 if not present)
+      filtered = filtered.sort((a, b) => {
+        const sortA = a.sort !== undefined ? Number(a.sort) : 9;
+        const sortB = b.sort !== undefined ? Number(b.sort) : 9;
+        return sortA - sortB;
+      });
+
+      return filtered;
+    }
+  }));
+});
diff --git a/themes/clean-hugo/static/site.webmanifest b/themes/clean-hugo/static/site.webmanifest
new file mode 100644
index 00000000..58154e26
--- /dev/null
+++ b/themes/clean-hugo/static/site.webmanifest
@@ -0,0 +1,20 @@
+{
+  "name": "Clean Hugo Theme",
+  "short_name": "Clean Hugo",
+  "description": "A modern, customizable Hugo theme",
+  "icons": [
+    {
+      "src": "/android-chrome-192x192.png",
+      "sizes": "192x192",
+      "type": "image/png"
+    },
+    {
+      "src": "/android-chrome-512x512.png",
+      "sizes": "512x512",
+      "type": "image/png"
+    }
+  ],
+  "theme_color": "#71B3B5",
+  "background_color": "#ffffff",
+  "display": "standalone"
+}
diff --git a/themes/clean-hugo/theme.toml b/themes/clean-hugo/theme.toml
new file mode 100644
index 00000000..595de63a
--- /dev/null
+++ b/themes/clean-hugo/theme.toml
@@ -0,0 +1,65 @@
+name = "clean-hugo"
+license = "BSD-3-Clause"
+licenselink = "https://github.com/lwasser/clean-hugo/blob/main/LICENSE"
+description = "A clean, modern Hugo theme with configurable colors and optional gallery feature"
+tags = ["blog", "gallery", "minimal", "modern", "hugo", "scss"]
+features = ["blog", "gallery", "responsive", "customizable"]
+min_version = "0.118.2"
+
+[author]
+  name = "Leah A. Wasser"
+  homepage = "https://leahwasser.com"
+
+[original]
+  author = "Leah A. Wasser"
+  homepage = "https://leahwasser.com"
+  repo = "https://github.com/lwasser/clean-hugo"
+
+# Default theme parameters (can be overridden in site's hugo.toml)
+[params.theme.colors]
+  # Brand colors (defaults) — can be overridden in site hugo.toml
+  primary = "#2E6060"
+  primaryDark = "#142929"
+  primaryLight = "#D6E3E3"
+  secondary = "#F1E0A6"
+  accent = "#42213D"
+  accentLight = "#E4B8C6"
+  neutral = "#395E66"
+
+  # Base/Text colors
+  white = "#FFFFFF"
+
+  # Gray scale (for theme customization)
+  gray50 = "#F9FAFB"
+  gray200 = "#E5E7EB"
+  gray600 = "#4B5563"
+  gray700 = "#374151"
+  gray900 = "#111827" # Used for dark background for blog highlights
+
+  # Semantic colors
+  link = "#2E6060"
+  linkOnDark = "#2DD4BF"
+  linkHover = "#1F4345"
+  featureCard = "#EBC1D3"
+
+  # Section backgrounds (kept as references for semantic clarity)
+  "heroBg" = "#2E6060"
+
+  # Admonition colors
+  "admonition-info" = "#53354F"      # deep purple
+  "admonition-success" = "#71B3B5"   # brighter teal
+  "admonition-warning" = "#E4B8C6"   # Soft blossom
+  "admonition-danger" = "#F1E0A6"    # yellow custard
+  "admonition-note" = "#CAE4E4"      # soft teal
+
+  # Event listing pills (/events/) — background + text for each event_type
+  eventLabelTrainingBg = "#D6E3E3"
+  eventLabelTrainingFg = "#142929"
+  eventLabelSprintBg = "#E4B8C6"
+  eventLabelSprintFg = "#111827"
+  eventLabelCommunityBg = "#F1E0A6"
+  eventLabelCommunityFg = "#111827"
+  eventLabelTalkBg = "#CAE4E4"
+  eventLabelTalkFg = "#142929"
+  eventDateBadgeBg = "#42213D"
+  eventDateBadgeFg = "#FFFFFF"