Markdown reference

Markdown gives wiki pages consistent formatting without custom components. You need access to the admin editor or a Markdown file in the repository. Use headings, links, code fences, and tables as shown below.

Headings

Use ## for sections and ### for subsections. The page title is already the main heading, so avoid adding a second level-one heading in the body.

Links and emphasis

**Important detail** and *short emphasis*.
[Installation guide](/docs/getting-started/installation/)

Use paths starting with / for internal links. This keeps links predictable when a page moves between sections.

Code

Add a language after the opening fence to enable syntax highlighting. For example:

```yaml
example:
  enabled: true
```

Documentation code blocks include a copy button automatically.

Tables

| Setting | Purpose |
| --- | --- |
| Example | Explain what the reader needs to know. |

Images

Use the editor’s media picker, then add a meaningful description. Uploaded images are stored under /uploads/. Describe the information in a screenshot in nearby text too.