Organize project documentation
Help readers find the right procedure without breaking useful links.
What to have ready
- Reader tasks, documentation scope, navigation/entry links, ownership/generation rules and proposal versus implementation scope.
When you run it
- Rendered verification needs the project renderer and browser where available; route compatibility requires actual host support.
A task to start with
Help readers find the right version of a useful procedure.
An illustrative request
Use the documentation-navigation workflow with these pages, reader tasks and hosting constraints. Preserve useful links and version context while proposing focused navigation improvements.
How to check the result
Follow affected entry links and anchors, including older paths and supported versions.
This preview explains the task and checking approach. It is not a demonstrated customer outcome or a guarantee.
See what a useful orientation looks like.
The free worked example includes source files, an actual entry-point trace and executed checks you can compare with the code.
Open the worked example