# Jupyter Book blog post on re-building on top of the MyST Markdown engine

**URL:** <https://openplanetary.discourse.group/t/jupyter-book-blog-post-on-re-building-on-top-of-the-myst-markdown-engine/784>\
**Category:** Programming and Workflows\
**Created:** [May 23, 2024, 9:33am UTC](https://openplanetary.discourse.group/t/jupyter-book-blog-post-on-re-building-on-top-of-the-myst-markdown-engine/784 "2024-05-23T09:33:49Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![cmarmo](https://yyz2.discourse-cdn.com/free1/user_avatar/openplanetary.discourse.group/cmarmo/32/271_2.png) [@cmarmo](https://openplanetary.discourse.group/u/cmarmo)\
**Post date:** [May 23, 2024, 9:33am UTC](https://openplanetary.discourse.group/t/jupyter-book-blog-post-on-re-building-on-top-of-the-myst-markdown-engine/784/1 "2024-05-23T09:33:49Z")

</div>

Cross-posting here as this may be of some interest for our audience too.

> **[Jupyter Book blog post on re-building on top of the MyST Markdown engine](https://discourse.jupyter.org/t/jupyter-book-blog-post-on-re-building-on-top-of-the-myst-markdown-engine/25861/1)**
>
> A quick update from the Jupyter Book team (which is not technically part of Jupyter, though there’s an open JEP to re-incorporate as a Jupyter subproject) 🎉 Until now, the Jupyter Book project was built on top of Sphinx. We’re excited to announce...