Jupyter Book Becomes a Jupyter Subproject
Jupyter Book joins the ranks of other Jupyter Subprojects such as JupyterLab and JupyterHub.
Over the last ten months, the Jupyter Book team have been hard at work building the next major version of Jupyter Book (see the blog post about using the MyST engine). During this time, we identified a strong distinction between the tools developed for the legacy Sphinx application and the new MyST Engine-powered version.
We decided that it’s best if these two projects are developed independently due to their significantly different technical stacks and visions. This was recently confirmed with a Jupyter Enhancement Proposal to incorporate Jupyter Book as a Jupyter Subproject.
Under the Jupyter organisation, the Jupyter Book team has found
a longer-lasting and organizationally-neutral home for the vision, strategy, tools, and standards of this modern version of the Jupyter Book toolchain.
To facilitate creating a new Jupyter Subproject, we’ve created a new jupyter-book GitHub Organisation. This new organisation is distinct from the Executable Books organisation that served as the home for previous releases of Jupyter Book.
github.com/jupyter-book will act as the hub for all future development and discussion surrounding Jupyter Book development.[1]
For more news about Jupyter Book, such as the upcoming Jupyter Book 2 alpha release, please keep an eye on this blog!
And
github.com/executablebookswill continue to serve as the home of the Sphinx-based stack, and will be developed independently.