Skip to article frontmatterSkip to article content
Site not loading correctly?

This may be due to an incorrect BASE_URL configuration. See the MyST Documentation for reference.

Writing, editing and storing content

Updated: 27 Mar 2026

Here we briefly described the various ways of storing and writing content. In the subsequent sections we describe these in more detail.

There are multiple ways to write, edit and store content for Jupyter Book projects, and showing your content to the world (or not). In the table below, we have summarized various possibilities, specified the requirements and highlighted their pros and cons. In the next chapters, each of these options is elaborated on, providing step-by-step instructions to get started.

Storing

Local
GitHub
GitLab

Description:
You can write, edit and store your source files locally. If you want to see the output of the content in either web- or pdf-format, you’ll need to have installed software (see below).

Pros:

  • Not visible to outside world when in development

  • Not supporting big tech with feeding data

Cons:

  • Not available to others

  • Back ups not automated

  • No version control

Writing and editing

Here we merely summarize the different ways of writing and editing your content. Information for how to use / enable it is covered in the subsequent chapters.

Local with VSC
Web editor
Overleaf
Jupyter Lab
GitLab
WYSIIWYG editor

You can edit your project on your local machine.

requirementsproscons
pythonFull control over project and environmentRequires installation and setup
JBWorks offlineEasy to use extensions for writing and editing
Node
code editor (e.g., VS Code)Not visible to others until deployed