There is a separate devshell called docs
which is provided for working with the docs locally.
It can be entered by running: nix develop .#docs
--8<-- "nix/devshells/docs.nix"
The docs are based on MkDocs and the MkDocs Material theme. You will find its configuration and content in the following locations:
mkdocs.yaml
./docs
To serve the docs locally run mkdocs serve
from the root of the repository:
❯ mkdocs serve
INFO - Building documentation...
INFO - Cleaning site directory
WARNING - The following pages exist in the docs directory, but are not included in the "nav" configuration:
- index.md
INFO - Documentation built in 0.26 seconds
INFO - [16:22:36] Watching paths for changes: 'docs/content', 'mkdocs.yml'
INFO - [16:22:36] Serving on http://127.0.0.1:8000/treefmt/
Versioning of the docs is managed through mike.
It is responsible for managing the structure of the gh-pages
branch in the repository, which Github Pages is
configured to serve from.
!!! note
More information about versioning with [MkDocs Material] and [mike] can be found [here](https://squidfunk.github.io/mkdocs-material/setup/setting-up-versioning/).
There is a github workflow, .github/workflows/gh-pages.yml
which is responsible for publishing the docs.
It does the following:
- On merge to
main
, the docs version main is updated. - When a new tag is created of the form
v.<major>.<minor>.<patch>
a docs versionv<major>.<minor>
is created and the latest alias is updated to point to this.
The idea is that users will land on the latest released version of the docs by default, with main
being available if
they wish to read about unreleased features and changes.
To preview the versions locally you can use mike serve
instead of mkdocs serve
.
!!! warning
Be sure to have fetched the latest changes for the `gh-pages` branch first.
This is especially important if you are using `mike` locally to make manual changes to the published site.