Context

We're currently focusing on developing the new version of Jupyter Book. This uses the newMyST Document Engine and involves a total re-write of Jupyter Book's back-end. We are prioritizing Jupyter Book 2.0 issues.

Where is Jupyter Book 2 developed?

Currently onthenext branch.

How can I try it out?

There's an alpha release already available! Just do:

pip install -U jupyter-book>=2.0.0a0

What are your development priorities?

Weuse this GitHub project for our priorities.

You can also follow this issue tracking a feature comparison between JB 1 and 2:

• Audit of Features missing in JupyterBook mystmd#189

What will the release cadence be?

The majoralpha andbeta labels in ourGitHub project correspond to promises about minimum features. Meanwhile, we will continually update the latest family of releases to pull in new upstream MyST engine fixes.

Stay tuned for information about the release date for Jupyter Book 2 Beta.

Where can I learn more about Jupyter Book 2 and this process?

Moving forward we'll post updates onthe new Jupyter Book blog. TheExecutable Books Blog also has some relevant historical posts. Here are a few links to help you get started:

• Executable Books blog describing our plans to shift focus to the MyST document engine
• Announcing the new Jupyter Book sub-project
• Announcing the Jupyter Book 2 alpha
• GitHub Discussion describing the relationship between the various MyST repositories

What about Jupyter Book 1.0 issues?

Issues that aren't related to Jupyter Book 2.0 (and specifically on the project board above) are going to be de-prioritized. We'll do our best to fix bugs for 1.x issues, but cannot make any promises.

Sorry about this - but we've got very limited resources to maintain and develop this project! We welcome contributions that make progress towardsthe issues on the 2.0 project board