Community documentation with Jupyter Book#
Community documentation is a great way to spread learning and knowledge across your user base. You can share workflows, tutorials, examples meant for re-use, and topics to help others understand the key ideas in your community.
Where to find examples of community books
Check out Project Pythia and the CryoCloud for real-world examples of community books.
2i2c recommends communities use Jupyter Book 2, which uses the MyST Document Engine, a next-generation engine for technical documentation and computational narratives. Both are developed by the Jupyter Book
subproject of Jupyter. See the MyST Ecosystem Overview for more information about MyST and Jupyter Book.
Jupyter Book integrations with 2i2c infrastructure is experimental
This feature is an experimental addition by 2i2c. It may change as we learn more about how communities are using it.
Get started with Jupyter Book#
Using the 2i2c community documentation template, you can get started by customising an existing bare-bones Jupyter Book. This template includes examples of:
Basic configuration for a Jupyter Book.
A landing page.
Authoring content that uses a Python Jupyter kernel.
Using rich cross-referencing features to create a knowledge base.
Why not start by adding your own glossary, or adding your own logo? See Learn how to author content with Jupyter Book and MyST Markdown for more tips about authoring content with Jupyter Book 2 and the MyST Engine.
Deploy your Jupyter Book as a website#
To deploy a Jupyter Book online, we recommend the following steps:
The Community Representative should use the 2i2c-org/community-docs-template template to create their own repository.[1]
For a custom domain next to your hub, provide the 2i2c team with temporary owner access to the repository. We will ensure that various configuration such as the custom domain and GitHub Actions are set up correctly.
Use GitHub Pages to host your book content online.[2] See the MyST Engine guide to GitHub Pages for more documentation (it uses MyST, which behaves very similarly to Jupyter Book 2).
Get a dedicated docs URL next to your hub#
Once your documentation is deployed online, 2i2c can give your community a special URL that makes your documentation more memorable and easier to find. If your hub is located at <COMMUNITY>.2i2c.cloud
, then your documentation will be hosted at the subdomain:
docs.<COMMUNITY>.2i2c.cloud
To enable this, first get your Jupyter Book hosted online, then open a support ticket with the 2i2c team requesting that this be done.