Consider using a different technolgy since Jupyter-book does not support versioning
What we want: Like every software project we want different versions of the docs online at the same time, i.e from the development version as well as the latest stable version as well as for most past releases. Ideally the development docs version should be deployed continuously.
This is natively supported by sphinx and readthedocs does this automatically on top. Currently, jupyter-book does not support this. Only if deployed directly through readthedocs, which became only recently possible See https://github.com/executablebooks/jupyter-book/issues/683
The docs of Jupyter-book is deployed this way. But if we do not want to move away from github pages, this is not an option for us.
They do not seem so fast in development. So maybe we should move to the usual/older docs software stack (mkdocs or sphinx) instead, while we can keep the books-theme.
Fiona proposed using https://docusaurus.io/, which would offer the capabilities to write much richer documentation websites. A tryout porting to this is currently https://codebase.helmholtz.cloud/hmc/hmc-public/unhide/documentation/-/tree/docusaurus_migration?ref_type=heads