Welcome! From all of the GeoServer users and developers, we are happy to see that you have an interest in contributing to the GeoServer documentation. Whether it’s the fix of a typo or a whole new collection of pages, all contributions are appreciated. With your help we can make GeoServer documentation helpful and robust, and thus make GeoServer a better product.
GeoServer documentation written in reStructuredText, a lightweight markup syntax, and built into HTML and PDF content using Sphinx, a documentation framework written by the developers of Python. In this way, the documentation could be merged with the source code of GeoServer itself, and exist in the same repository. With this merge, version control follows naturally, so documentation can now be version specific.
We handle changes to the documentation in the same way as we do changes to the code base, so you need to make a branch for your change and submit it as a “pull request” to the main repository, this is all explained in the Workflow section later.
Since the repository requires authentication to make changes, authors who plan large changes can be granted access so they are able to directly contribute to the documentation. While this does slightly raise the barrier to entry, the ability to control the quality of the documentation was seen as a greater benefit.
Prior to the use of Sphinx GeoServer documentation was created using a wiki as part of the GeoServer home page. While this allowed anyone to sign up and contribute documentation we ended up with problems of vandalism and lacked features we now enjoy (Version control, PDF export).
Read on to find out Contributing.