b386737d08
Signed-off-by: Tilman Vatteroth <tilman.vatteroth@tu-dortmund.de>
(cherry picked from commit eaeb88401d)
Signed-off-by: David Mehren <git@herrmehren.de>
1.7 KiB
Documentation
Our documentation is build with mkdocs.
Writing
All documentation files are found in the docs/content directory of
the hedgedoc/hedgedoc repo. These files are just normal markdown files with
nothing special about them.
The configuration for mkdocs lies in the docs folder in a file called mkdocs.yml. With that file the theme and menu
- amoung others - can be configured. Please note: Any new files need to be linked to by other files or put in the navigation or the files will be very hard to find on the documentation website.
Building
To build the documentation locally you need to perform the following steps:
- Make sure you have python3 installed.
- Go into the
docsfolder. - Install all the dependencies (E.g. with a venv)
with
pip install -r requirements.txt - Start the mkdocs dev server (
mkdocs serve) or build the documentation (mkdocs build).
Deployment
The documentation is deployed with Messor Structor.
The necessary Dockerfile and version menu template and also the github action to build the whole documentation can be found in the docs.hedgedoc.org repo. This repo is also used to deploy the actuall website to github.io.
Messor Structor builds and deploys the documentation by finding all branches that follow the pattern v*. For each
branch the docs are generated separately by first installing the dependencies from requirements.txt and then running
mkdocs. Afterwards the menu go template is used to include a version switcher in the theme.