# Documentation Guidelines¶

The EnMAP-Box documentation is written in the reStructuredText(reST) format, coupled with some external libraries, e.g. Sphinx. To keep things consistent, the following chapter contains guidelines on how to style the EnMAP-Box documentation.

## Writing Guidelines¶

Using the reST format for the documentation, allows to create several webpages with chapters, sections and subsections. To see the general style guidelines, follow the QGIS documentation guidelines.

The section For Authors guides you through the most important general rules for contributing to documentation, including the design of headings, inline tags and the insertion of captions and references.

The Documentation section in the Pythons Developer’s Guide summarises how to use Python to write documentation. It describes the first steps in writing documentation and also gives some examples of how to include source code or hyperlinks.

In addition to the two guidelines mentioned above, we have developed some simple rules for EnMap Box documentation, which are described below.

### 1. reStructuredText¶

#### Basic inline markup¶

Use

• on asterisk for italic text (*italic text*) to emphasize something
• two asterisk for bold text (**bold text**) to emphasize something strongly
• two backquotes for code examples (code examples), variables, filenames, etc.

In addition, when describing a workflow of some algorithm or tool, use the following instructions.

Element Style Markup Example
Labels describing an interaction GUI label :guilabel:text  Drag and drop the file from your file manager into the Data Sources panel.
Describing an algorithm in general bold **text** The EnMAP-Box offers Spectral Library Windows for visualizing spectra.
Captions of images, screenshots, etc. italic *text* Fig. 2: Example of adding a screenshot with explanation.
Including files, samples, variables file label + backquotes :file: text  Vector = agb_sonoma.gpkg

#### Numbering¶

Use numbering to describe individual steps. This makes it is easier to distinguish between information and actual steps and to follow them easily:

Workflow example with numbering

### 2. Figures & Screenshots¶

#### Screenshots with explanations¶

• Font: Verdana
• Size: 14 pt
• Text color: RGB – 61-61-61
• Line color: RGB – 192-0-0
• Line width: 1 pt
• Description to the left of the screenshot at the level of the function to be explained
• Description text in box right-aligned

Example of adding a screenshot with explanation.

#### Positioning of info boxes and images¶

Info boxes, tooltips and notes should be aligned with the preceding text, i.e., if the info box follows a bulleted list, the box should also be indented.

Example of placing info boxes within / after bullet points.

Images should always be centred, but can vary in size (adjust according to readability). Also add a caption to the image if it is not placed between two bullet points.

Placement of images for (a) within bullet points, (b) after body text