New release: More reliable static content, dark mode improvements, and more!

We’re pleased to announce the latest releases of mystmd (v1.10.1) and myst-theme (v1.3.1). We improved the static asset resolution, the dark mode experience, and the theme experience among others. Read below for some of the bigger improvements and fixes that we made!

What’s new¶

Improved Support for Static Content. One of the most important updates in this release is improved handling of project static files across the MyST ecosystem. When the theme encounters a route that does not resolve to a MyST page, it now checks the content server to determine whether the requested path corresponds to a static asset. If a matching file is found, the request is redirected and served directly by the content server. Alongside this work, we’ve expanded the documentation around static file behavior to make it easier for users and contributors.
Better Dark Mode Experience. Dark mode continues to be an important part of the reading experience for many users. This release improves compatibility with Mermaid diagrams when dark mode is enabled, ensuring that diagrams remain readable and visually consistent across themes. We have also refined theme behavior by improving logo rendering in dark mode.
Other theme improvements. This release includes several refinements to the user interface that help create a smoother and more polished experience for readers. Among others, we have improved theme behavior by preventing unnecessary theme-transition animations, reducing visual distractions and making transitions feel more natural. We also fixed vertical height for stacked buttons, ensuring that interactive elements display consistently.

Changelogs¶

You can also read about this release at jupyterbook.org/releases. For more details, see mystmd release notes and myst-theme release notes.

Upgrade notes¶

To upgrade mystmd:
npm install -g mystmd (or pip install -U mystmd)
To upgrade myst-theme:
Delete _build and it downloads on the next build

Try it out!¶

We’d love your feedback. Try the new release and let us know what works well and where we can improve.

Thank you contributors!¶

This release would not have been possible without the help of our community. Thanks to everyone who contributed discussions, ideas, code, and review across this release, especially: @agoose77, @chad-earthscope, @choldgraf, @joequant, @pancakereport, @parmentelat, @rowanc1, @stefanv, and @stevejpurves.