Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bring MyST document engine up to feature parity with Jupyter Book, with the intent of offering MyST as a backend to Jupyter Book #1000

Open
1 of 2 tasks
choldgraf opened this issue Mar 18, 2024 · 0 comments
Labels

Comments

@choldgraf
Copy link
Collaborator

choldgraf commented Mar 18, 2024

Goal

Jupyter Book users should be able to utilize the new MyST document engine with no significant degradation in functionality or UX.

Outcome and measures

  • Most users of Jupyter Book can use the MyST build engine without any errors with less than 30 minutes of conversion work.
  • Key Jupyter Book user communities report no blocking problems with the MyST build engine

Reference

List of feature comparisons here:

Initiatives

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant