👋 Thanks for opening this PR! The Cookbook will be automatically built with GitHub Actions. To see the status of your deployment, click below.
🔍 Git commit SHA: ba8d12c
✅ Deployment Preview URL: https://projectpythia.github.io/_preview/542

Preview link to most relevant file: https://projectpythia.org/_preview/542/posts/mystification

Not something that needs to be solved now, but I'm curious if there's a good way to add author metadata for folks who's info isn't already propagating from the upstream config.

I suppose we could add that in the MyST config for this repo, but not sure if there's an article/post level option.

There is, but we should take this opportunity to add people upstream since that will simply all future posts. I'll open a PR for that.

Not something that needs to be solved now, but I'm curious if there's a good way to add author metadata for folks who's info isn't already propagating from the upstream config.

I suppose we could add that in the MyST config for this repo, but not sure if there's an article/post level option.

The answer to your question is that the authors: field in the page frontmatter can have an arbitrary list of authors objects which can each contain full metadata: https://mystmd.org/guide/frontmatter#frontmatter-authors

The shortcut here is that we're just giving the id field, which has been set upstream to be identical to each person's GitHub handle. But there's no reason we couldn't mix and match short id references and full author records in the page frontmatter if we wanted to, to my knowledge.

Upstream PR: ProjectPythia/pythia-config#16

once that is merged, we can regenerate the preview here and make sure everyone is showing up correctly.

Hi from SciPy! The post is looking very nice. Note that in the list of authors, Julia needs to come after Angus to follow last-name alphabetical sorting.

It turns out that MyST doesn't know how to interpret the family-names and given-names in the author yaml. I'll go fix that upstream so that @dcamron's actually appears.

Closing and reopening one more time to fix the authors list.

I tried a collapsible-by-year navbar and it isn't working

  toc:
    - file: index.md
    - file: about.md
    - title: Blog
      children:
        - title: 2025
          children:
            - file: posts/2025/mystification.md
            - file: posts/2025/cookoff2025-website.md
            - file: posts/2025/binderhub_status.md
            - file: posts/2025/new-cookbooks.md
        - title: 2024
          children:
            - file: posts/2024/cookoff2024-website.md
        - title: 2023
          children:
            - file: posts/2023/cookoff2024-savethedate.md
            - file: posts/2023/fundraiser.md
            - file: posts/2023/cookoff2023.md
    - file: contributing.md
    - file: cookbook-guide.md
    - file: quick-cookbook-guide.md
    - file: metrics.md

I'm not pressed on it though.

What are your thoughts on the new directory structure @brian-rose ?

I think it all looks good. We can work on improved blog navigation in a separate PR.

If you are looking for inspiration/examples, Chris Holdgraf's site uses myst and has a nice structure around it!
https://chrisholdgraf.com/blog

Here is a link to his blog post about building it
https://chrisholdgraf.com/blog/2024/mystmd-with-the-blog

Thanks for this link @mgrover1 I'll look into implementing this after this PR is merged! I was thinking of using the same type of gallery extension we use elsewhere, will look at what his method is this afternoon.

In light of our link checker being too strict - it is stalled on a call to localhost. There are many incomplete/template links in the contribution guides and elsewhere that aren't meant to be clickable.