wiki maintenance
the wiki must change when product behavior changes. docs that drift from the app are worse than no docs because ai tools will repeat the wrong behavior.
quick answer
update the wiki in the same work as the feature change.
use this for
- adding a feature
- changing limits, plans, routes, or setup steps
- shipping public product changes
steps
- find the affected feature page.
- update the source in `scripts/wiki_generate.py`.
- regenerate the wiki.
- run sitemap generation.
- run seo and transition lint.
- include wiki files with the feature commit when the change is user-facing.
details to know
- new wiki pages should be text-first and image-free.
- every page needs a quick answer, steps, details, limits, and related pages.
- new docs should be linked from the wiki index and `llms.txt` when important.
- clean `/wiki/...` routes must keep working before the public-document fallback.
limits and edge cases
- do not hand-edit generated wiki pages unless the generator is updated too.
- do not add screenshots unless the no-image rule is explicitly changed.
ready to use the product instead of reading about it?
open app