Merge pull request #3 from jupyter-book/agoose77/feat-initial-post

🏠 Add initial blog post about Jupyter Book project

myst.yml

@@ -3,12 +3,40 @@ version: 1
 extends:
   - https://raw.githubusercontent.com/jupyter-book/meta/refs/heads/main/myst.yml
 project:
-  title: 'Jupyter Book: Blog'
+  title: "Jupyter Book: Blog"
   description: Updates from the Jupyter Book subproject.
   keywords:
     - Jupyter
     - JupyterBook
     - MyST Markdown
+  authors:
+    - name: Angus Hollands
+      orcid: 0000-0003-0788-3814
+      affiliations:
+        - Jupyter Book
+        - 2i2c
+    - name: Chris Holdgraf
+      orcid: 0000-0002-2391-0678
+      affiliations:
+        - Jupyter Book
+        - 2i2c
+    - name: Rowan Cockett
+      orcid: 0000-0002-7859-8394
+      affiliations:
+        - Jupyter Book
+        - Curvenote
+    - name: Franklin Koch
+      orcid: 0000-0002-6393-7058
+      affiliations:
+        - Jupyter Book
+        - Curvenote
+    - name: Steve Purves
+      orcid: 0000-0002-0760-5497
+      affiliations:
+        - Jupyter Book
+        - Curvenote
+  references:
+    jpy-gov: https://jupyter.org/governance/
   github: https://github.com/jupyter-book/blog
   # To autogenerate a Table of Contents, run "myst init --write-toc"
   license: CC0-1.0

posts/2024-11-11-jupyter-book-org.md

@@ -0,0 +1,31 @@
+---
+title: Jupyter Book Becomes a Jupyter Subproject
+subtitle: Jupyter Book joins the ranks of other Jupyter Subprojects such as JupyterLab and JupyterHub.
+date: 2024-11-11
+license: CC-BY-4.0
+---
+
+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][plan]).
+During this time, we identified a strong distinction between the tools developed for the legacy Sphinx application and the new [MyST Engine][mystmd]-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][book-jep] 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.
+>
+> -- [Jupyter Enhancement Proposal #122](https://github.com/jupyter/enhancement-proposals/pull/123)
+
+To facilitate creating a new Jupyter Subproject, we've created a [new `jupyter-book` GitHub Organisation][jbp]. This new organisation is distinct from the [Executable Books organisation][ebp] that served as the home for previous releases of Jupyter Book.
+[`github.com/jupyter-book`](https://github.com/jupyter-book) will act as the hub for all future development and discussion surrounding Jupyter Book development.[^1]
+
+[^1]: And [`github.com/executablebooks`](https://github.com/executablebooks) will continue to serve as the home of the Sphinx-based stack, and will be developed independently.
+
+For more news about Jupyter Book, such as the upcoming Jupyter Book 2 alpha release, please keep an eye on this blog!
+
+[jbp]: https://github.com/jupyter-book
+[ebp]: https://github.com/executablebooks
+[plan]: https://executablebooks.org/en/latest/blog/2024-05-20-jupyter-book-myst/
+[book-jep]: https://github.com/jupyter/enhancement-proposals/pull/123
+[mystmd]: https://mystmd.org