2 min readAn original planning guide. Use the linked primary documentation for platform details and the supported procedure for your environment.
Inventory pages and tasks
List the information and actions visitors need, then identify the main destinations. Separate primary tasks from occasional administrative links.
Create understandable groups
Use labels that describe destination content. Avoid categories that overlap so much that a reader cannot predict where a page belongs.
Check real journeys
Walk through a new visitor's question, a returning customer's task, and a reader arriving deep in the site. Include paths back to parent sections.
Verify responsive access
Review keyboard navigation, visible focus, menu state, and narrow-screen controls when implemented. Keep all important destinations reachable.
Worked scenario
See the plan in practice.
A reader lands directly on a DNS term. Breadcrumbs and a topic link help them discover related guides without returning to the homepage.
Review your result
Your acceptance checklist
Labels predictive- Deep entries supported
- Menus testable
Use these checks to identify gaps in your navigation map. Assign an owner to any unresolved item before the next dependent step.
The terms behind the task
Primary references
For the underlying concepts and current platform details:
