Tracking: Project Pythia Support

[rowanc1]

Over the last week Project Pythia has started an upgrade from JupyterBook to mystmd. The organization experimenting with that is here:

https://github.com/projectpythia-mystmd

The website is hosted on github pages: https://projectpythia-mystmd.github.io/

@agoose77, myself as well as @fwkoch and @stevejpurves (in the background of the conference) were helping out from the EBP core team. It was very very exciting to see the progress that the team was able to make on bringing together a full workflow from landing pages to all of the cookbooks that the community creates. The exciting features that we highlighted were:

• the ability to centralize configuration for the entire project (via the new inheritance @fwkoch worked on recently #1215)
• the ability to cross-reference content between their "foundations" content into the other projects (via #1180, last month)

https://github.com/executablebooks/mystmd/assets/913249/5050301f-e17c-4dd2-bfbd-f0806645e78f

There were also examples of creating plugins via python and galleries by @agoose77 and @jmunroe, based in part on my prototyping here a while back.

The infrastructure group talked about limitations of the current stack that are blocking adoption, as well as UX papercuts and UI improvements that we should prioritize.

Improvements and Features

• [x] Write a blog post about the week (@choldgraf @rowanc1 @agoose77) 📖 https://github.com/executablebooks/meta/pull/1192
• [x] Logos (light and dark mode inherited) #1296
• [x] Add tags to project frontmatter #1289
• [ ] Favicon needs to work on static sites #1296
• [ ] Contact icons in header (youtube, twitter, github)
• [ ] Nav logo URL needs to be configurable (right now it points to root site)
• [ ] Copyright info at the bottom of the page
• [ ] Footer (including the double footer concept)
• [ ] Banners for landing page
• [ ] Support for "tags" UI element (currently a span with style, and we can do better out of the box)
• [x] #1298
• [ ] #100 (could be algolia to start with potentially)
• [ ] Filtering in the galleries
• [ ] Launch buttons #1235 (buttons need improved UX and the launch doesn’t get you to the right notebook internally)
• [ ] Improved blog support (cards, tags, tag pages)

I would like to encourage folks from ProjectPythia to jump in here and add anything else that we are missing and ways that we can help support you. :)

cc @jukent @kafitzgerald @brian-rose @dcamron @mgrover1 @ktyle @anissa111 @matakleo @jmunroe @jnywong

[choldgraf]

We need to write a blog post about this

[brian-rose]

I'm not sure how in-scope this is here, but one key feature of the existing Pythia infrastructure is the ability to route notebook execution to an arbitrary Binder service at build time (for context, see this Pangeo Discourse post).

We got this working for Pythia Cookbooks with an ugly hack of the jupyter-book build command on GitHub Actions, see here.

Support for a more flexible separation between the computational environments for the book build and the notebook code execution would be very very useful for Project Pythia, and presumably for a much broader community as well.

[rowanc1]

Hi all -- the blog post from ExecutableBooks is here:

https://executablebookproject--1192.org.readthedocs.build/en/1192/blog/2024-06-14-project-pythia-mystmd/

The PR is if you have any further edits: https://github.com/executablebooks/meta/pull/1192

Aiming to get that out early this week! Thanks @agoose77 and @brian-rose for feedback on the blog!

[rowanc1]

Hi all - the ExecutableBooks blog is live: https://executablebooks.org/en/latest/blog/2024-06-14-project-pythia-mystmd/

[dcamron]

1323 for a.) the option to flatten nested glob'd notebooks in the toc and b.) converting existing patterns in the upgrade process is potentially big for a few specific Cookbooks' use-cases

[dcamron]

Support for .. bibliography:: style rendering of a full list of citations across an entire book/from a single bibtex would be valuable for multiple Cookbooks.