HTML Python JavaScript CSS PHP Makefile Shell
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
_static Kleine Änderungen Mar 28, 2018
_theme Adde static sphinx_rtd_theme files Mar 19, 2018
de Change links to references where a warning occured during the build Aug 8, 2018
en
figures Merge pull request #58 from mapbender/feature/translation2 Aug 8, 2018
output Moved documentation into it's own repository. Jan 24, 2013
.editorconfig Added entry for *.json files Feb 22, 2018
.gitignore Merge branch 'release/3.0.6' into feature/rtd_theme Mar 19, 2018
404.rst add 404 page May 2, 2018
Makefile Makefile: make documentation faster with j4. Apr 10, 2018
README.md Removed the submodule command from the Readme. Feb 16, 2018
conf.py Add parameters for View on Github link in every page Mar 19, 2018
generate.sh Moved documentation into it's own repository. Jan 24, 2013
index.rst Remove dead links and glossary Jul 12, 2018
static404.html Add static404 page. Jul 9, 2018
tox.ini Added Tox for easy building with Python2 Jul 4, 2014

README.md

Mapbender Documentation

This is the Mapbender documentation repository.

You find the compiled pages of the latest released version at https://doc.mapbender.org/. Other versions of the documentation are also available at https://docs.mapbender.org/.

The current working branch is release/3.0.6. The released versions are based on the master branch and merged from release/3.0.6.

The website code is generated using Sphinx, therefore the documentation source is written in Restructured Text.

You find a documentation about how the documentation is structured in the documentation itself in chapter How to write Mapbender Documentation? or directly here in this Git-Repository.

To build the website locally, you need to install Sphinx. Install it in Debian-based distributions via

$ apt install python-sphinx

You can then build the documentation by running:

$ make

To participate in the documentation, create a fork, work on the release/3.0.6 branch and create a Pull-Request with the release/3.0.6 branch as base.

Have fun!