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

Minimum Viable Product of Jupyter Book functionality with MyST #1106

Open
16 of 37 tasks
Tracked by #1000
choldgraf opened this issue Apr 16, 2024 · 0 comments
Open
16 of 37 tasks
Tracked by #1000

Minimum Viable Product of Jupyter Book functionality with MyST #1106

choldgraf opened this issue Apr 16, 2024 · 0 comments

Comments

@choldgraf
Copy link
Member

choldgraf commented Apr 16, 2024

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

Minimal functionality needed to use Jupyter Book with MyST

Here's a starting point, we can change or update this as we wish:

MyST engine

Documentation

Book theme

Operations

  • Create a preview version of the new MyST backend for Jupyter Book
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Progress
Development

No branches or pull requests

1 participant