7e3ede02f7
I added info about installing front ends from the development branch I also rearanged the list of exceptions (what's different than "normal" installation) so the order is closer to how you'd encounter things in the installation docs + small fixes |
||
|---|---|---|
| .. | ||
| docs | ||
| theme/partials | ||
| Makefile | ||
| mkdocs.yml | ||
| Pipfile | ||
| Pipfile.lock | ||
| README.md | ||
| requirements.txt | ||
Building the docs
You don't need to build and test the docs as long as you make sure the syntax is correct. But in case you do want to build the docs, feel free to do so.
You'll need to install mkdocs for which you can check the mkdocs installation guide. Generally it's best to install it using pip. You'll also need to install the correct dependencies.
Example using a Debian based distro
1. Install pipenv and dependencies
pip install pipenv
pipenv sync
2. (Optional) Activate the virtual environment
Since dependencies are installed in a virtual environment, you can't use them directly. To use them you should either prefix the command with pipenv run, or activate the virtual environment for current shell by executing pipenv shell once.
3. Build the docs using the script
[pipenv run] make all
4. Serve the files
A folder site containing the static html pages will have been created. You can serve them from a server by pointing your server software (nginx, apache...) to this location. During development, you can run locally with
[pipenv run] mkdocs serve
This handles setting up an http server and rebuilding when files change. You can then access the docs on http://127.0.0.1:8000