Minimum Viable Product of Jupyter Book functionality with MyST

[choldgraf]

We're tracking a laundry list of MyST functionality in this issue. There's a lot of functionality in there, and that issue doesn't prioritize or define the essential vs. "nice to have" functionality we'd want to see.

In order to move forward the initiative on a myst backend for Jupyter Book , I think we should define the minimal functionality that makes "Jupyter Book via the MyST engine" safe to try. That can be the guiding principle to drive @agoose77's work once we've finished up the launch initiative .

Principles to guide this work

• Principles to guide the Jupyter Book transition from Sphinx to MyST #1113

Where to track this work

• Jupyter Book and MyST Team Priorities

[choldgraf]

I've updated the project board a little bit to have three columns:

• Needed for alpha: Issues that we need to resolve before we can release an alpha version of Jupyter Book 2.0. For these issues, releasing v2 without resolving them should significantly degrade the user experience so much it's not worth releasing.
• Needed for beta: Issues that are important but not critical for getting JB2 out for feedback
• Nice to have: Issues that we've explicitly decided aren't required for a JB2 launch.

[haroldcampbell]

This needs to be on product board so we won't be tracking this here.