Wiki articles support Markdown, a lightweight way to make readable guides without writing HTML. Raw HTML is shown as text for safety.

Headings and emphasis

• Start a line with ## for a section heading.
• Use ### for a smaller section heading.
• Surround words with ** for bold, or * for italic.
• Use ~~old wording~~ when explaining text that has been replaced.

Links and images

• Use [Open Aniimo](/pages/aniimo_profile.php) for a clickable link.
• Use ![Screenshot description](https://example.com/image.webp) for a picture. Only trusted HTTPS or approved site-local image addresses are accepted.
• Always describe what a screenshot shows so readers understand it if the image does not load.

Lists and steps

1. Numbered lists work well for instructions.
2. Put each action on its own line.
3. Mention exactly which button the user should click.

For a checklist, start a list item with [ ] (not done) or [x] (done).

Tables

For comparisons, write pipe-separated headers, then a separator row:

| Setting | What it does |
| --- | --- |
| Caught before | Records discovery |
| Owned quantity | Counts current copies |

Notes, tips, and warnings

A callout starts with a block quote marker and a label:

> [!TIP]
> Save all your Aniimo tracker edits together.

You can use NOTE, TIP, IMPORTANT, or WARNING. Longer code examples go between triple backticks.

Warning Never include passwords, API keys, private messages, or account recovery information in a public wiki guide.