Add sections on day 1 and 2

content/blog/2024/project-pythia-cookoff/index.md

@@ -17,17 +17,44 @@ draft: true
 
 ## What did 2i2c do?
 
-Jenny, James and Angus from the 2i2c team participated in the annual [Project Pythia Cook-off 2024](https://projectpythia.org/pythia-cookoff-2024/), a hackathon where cookbook authors and collaborators can spend dedicated time on creating and maintaining their content using [Jupyter Book](https://jupyterbook.org/en/stable/intro.html) (see the latest blog post on [Jupyter Book 2.0 will use MyST](../myst-jupyter-book/index)) and publishing their cookbooks with GitHub actions.
+Jenny, James and Angus from the 2i2c team participated in the annual [Project Pythia Cook-off 2024](https://projectpythia.org/pythia-cookoff-2024/), a hackathon where cookbook authors and collaborators can spend dedicated time on creating and maintaining their content using [Jupyter Book](https://jupyterbook.org/en/stable/intro.html) and publishing their cookbooks with GitHub actions.
 
-Prior to the hackathon, 2i2c deployed a JupyterHub with a *binderhub-service* that allowed participants to "self-serve" containers for their software environment, which were specified by including a list of packages in an `environment.yml` file placed in their Git repository.
+2i2c teamed up with the infrastructure breakout group during the hackathon, led by Katelyn FitzGerald (UCAR) and Kevin Tyle (University at Albany), and members of the [Curvenote](https://curvenote.com/) team also joined the group.
+
+## Day 1
+
+2i2c deployed and demonstrated a dedicated BinderHub service for Project Pythia that allowed hackathon participants to "self-serve" images of their software environment, which were specified by including a list of packages in an `environment.yml` file placed in their GitHub cookbook repository. Participants could then pull the image from a container registry into their 2i2c hub (or indeed, any other JupyterHub server) to share and reproduce their computational environments with ease.
+
+![Screenshot of Project Pythia BinderHub service](binder.png)
 
 <!-- TBC: number of participants, how many used the JupyterHub, cost $$$ to run the service -->
 
-2i2c teamed up with the infrastructure breakout group during the hackathon, led by Katelyn FitzGerald (UCAR) and Kevin Tyle (University at Albany), and members of the [Curvenote](https://curvenote.com/) team also joined the group.
+## Day 2
 
-## Day 1
+During the first half of the day, we quickly identified a number of issues that were proving to be a maintenance headache for the Project Pythia infrastructure group:
+
+- [ ] Configuration files for each cookbook were difficult to update at scale. Project Pythia currently have a gallery of over 30 cookbooks!
+- [ ] Changes to Sphinx-based themes inherited from upstream were prone to breaking custom Project Pythia branding downstream.
+- [ ] Executable content was not able to run on the Project Pythia's dedicated BinderHub hosted on [JetStream2](https://jetstream-cloud.org/index.html) (operated by NSF).
+- [ ] Cookbooks frequently cross-referenced materials from other cookbooks to build upon pre-existing knowledge, but this was not easy to author and the user experience was not a smooth as it could be.
+
+Following the recent announcement that [Jupyter Book 2.0 will use MyST](../myst-jupyter-book/index), Rowan (Curvenote) and Angus (2i2c) delivered a compelling demonstration of the [MyST](https://mystmd.org/) ecosystem.
+
+In the second half of the day, we decided to use the hackathon to explore migrating the Pythia cookbooks from using a Sphinx-based to a MyST-based document structure and engine. Within one afternoon, the group migrated four cookbooks to use MyST MD
+
+1. [Pythia Foundations](https://projectpythia-mystmd.github.io/pythia-foundations/)
+1. [High Resolution Rapid Refresh on AWS](https://projectpythia-mystmd.github.io/HRRR-AWS-cookbook/)
+1. [Radar Cookbook](https://projectpythia-mystmd.github.io/radar-cookbook/)
+1. [Advanced Visualization](https://projectpythia-mystmd.github.io/advanced-viz-cookbook/).
+
+![Screenshot of a side by side comparison of the Sphinx (left) and MyST (right) based cookbook.](side-by-side.png)
+
+This was exciting! It was evident that MyST MD supported backwards compatible content out of the box, which alleviated fears of sunk cost into existing Sphinx-based cookbooks.
+
+Another amazing outcome was the tight feedback loop amongst the team so that we were able to quickly expose small bugs ([e.g. support for HTML video tags](https://github.com/executablebooks/mystmd/issues/1297)) in the MyST MD tooling, which were immediately fixed upstream and released within minutes.
+
+## Day 3
 
-We quickly identified a number of issues that were proving to be a maintenance headache for Project Pythia:
+We spent this day tackling support for managing a gallery of Project Pythia cookbooks.
 
-- [ ] Configuration files for each cookbook were difficult to update at scale. Project Pythia currently have a collection of over 30 cookbooks!
-- [ ] Changes to Sphinx-based themes inherited from upstream were prone to breaking custom Project Pythia branding.
+## Day 4