Manual Maintenance

The manual is deliberately split into small Markdown files. Keep user documentation here and technical/change documentation in the project Docs/ folder.

Page recipe

For a mature module page, prefer: what it does → quick start → controls → inputs/outputs → examples → tips → see also. Add screenshots only when they explain something that text does badly.

Crosslinks

Link concepts on first useful mention. Avoid turning every noun into a link; this is a manual, not Wikipedia after three coffees.

Updating

When a module changes, update its page and any tutorial that depends on the changed behaviour. Keep filenames stable so external links survive.