Skip to article content

This page discusses high-level questions about the MyST Markdown ecosystem, history of mystmd, various ecosystem implementations, and explains a few decisions made in the project.

History of MyST Markdown and mystmd

MyST Markdown (Markedly Structured Text) is a markup language that builds on standard markdown and is designed to create publication-quality documents, books, presentations, and websites written entirely in Markdown. The ExecutableBooks team received a grant from the Sloan Foundation to build, enhance, and promote a new path to document creation and publishing for next-generation scientific textbooks and lectures (Grant #9231).

The initial use case driving the development and design of MyST Markdown has been JupyterBook, which allows you to create educational online textbooks and tutorials with Jupyter Notebooks and narrative content written in MyST. The extensions and design of MyST is inspired by the Sphinx and reStructuredText (RST) ecosystems. Jupyter Book is considered a distribution of Sphinx, and builds on the Sphinx and Docutils Python packages.

MyST Markdown enables rich content generation and is a powerful textual format for scientific and technical communication with potential for broad adoption in modern publishing workflows. In 2022, the Executable Books team started work to document the specification behind the markup language, called myst-spec, this work has enabled other tools and implementations in the scientific ecosystem to build on MyST Markdown (e.g. scientific authoring tools, and documentation systems).

The mystmd[2] command line tools were developed as a collaboration between Curvenote, 2i2c and the ExecutableBooks team. The initial version was release by Curvenote as the Curvenote CLI under the MIT license, and later transferred to the ExecutableBooks team. The goal of the project is to enable the same rich content and authoring experiences that Sphinx allows for software documentation, with a focus on web-first technologies (Javascript), interactivity, accessibility, scientific references (e.g. DOIs and other PIDs), and professional PDF outputs.

How do Jupyter Book and mystmd relate?

The current toolchain used by JupyterBook is based on Sphinx, which is an open-source documentation system used in many software projects, especially in the Python ecosystem. mystmd is a similar tool to Sphinx, however, designed for scientific and technical content. In addition to building websites, mystmd can also help you create scientific PDFs, Microsoft Word documents, and presentations.

mystmd uses existing, modern web-frameworks in place of the Sphinx build system. These tools come out-of-the-box with prefetching for faster navigation, smaller network payloads through modern web-bundlers, image optimization, partial-page refresh through single-page application. Many of these features and performance improvements are difficult (if not impossible) to create inside of the Sphinx build system.

The javascript packages in the mystmd ecosystem also help power web-native extensions, such as JupyterLab-myst, which renders MyST markup directly in JupyterLab.

mystmd can render JupyterBook content, however, it cannot work with custom extensions or themes developed for Sphinx. As mystmd continues to improve, we will ensure smooth paths for content authors to choose between these different rendering engines.

Can I use JupyterBook and mystmd together?

Yes! There is overlap in functionality for creating websites, however, you can also use mystmd with your JupyterBook content to:

If you want, you can also try a mystmd website to view your JupyterBook (try the online tool provided by Curvenote, to test with your JupyterBook). mystmd provides improved interactivity around cross-linking content, performance and accessibility improvements.

JupyterBook and mystmd both use MyST Markdown for content and read Jupyter Notebooks, and we ensure that your content can be read equally by both renderers. However, no custom Sphinx extensions that you may have added to your JupyterBooks will work. If you find something that doesn’t work with mystmd from your JupyterBook content, please let us know on GitHub and we will try to support it!

Jupyter Books are an excellent medium for tutorials, textbooks & software documentation but are currently less well suited to content such as blogs, lab-websites, and journal articles. Additionally, JupyterBook cannot create scientific PDFs that are submission ready.

How do mystmd and Sphinx relate?

Sphinx is an open-source documentation system used in many software projects, especially in the Python ecosystem. The Sphinx ecosystem has excellent support for Python documentation, referencing content, as well as externally providing an inventory of references known as intersphinx. You can use your mystmd projects with intersphinx references, and also exposes information (i.e. an objects.inv) to allow Sphinx documentation to reference your project.

At this time mystmd does not support software documentation[1], as such, if your project is documenting Python software we suggest that you use Sphinx. If your project is primarily tutorials, educational textbooks (including with Jupyter Notebooks), a presentation, or scientific paper we hope that you find a better fit with mystmd!

  1. Originally mystmd was called mystjs, but was changed as we matured the command-line interfaces.

  2. In the future, mystmd may offer support for Python and Javascript documentation, and if you want to contribute please reach out!

MyST MarkdownMyST Markdown
Community-driven tools for the future of technical communication and publication