-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracking: Project Pythia Support #1320
Comments
We need to write a blog post about this |
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 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. |
Hi all -- the blog post from ExecutableBooks is here: The PR is if you have any further edits: Aiming to get that out early this week! Thanks @agoose77 and @brian-rose for feedback on the blog! |
Hi all - the ExecutableBooks blog is live: |
#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 |
Support for |
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:
extends
field to myst.yml for composing multiple yamls #1215)pythia.mp4
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
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
The text was updated successfully, but these errors were encountered: