Demo: Traditional Docs Slice¶
This is a mock slice of the site if it leaned harder into a traditional docs structure. The emphasis is on orientation, hierarchy, and a clearer recommended path.
Section¶
Navigation
Subsection¶
Nav2 Basics
Page¶
Nav2 Architecture and Tuning Guide¶
Use this page as the entry point for the Navigation section. It gives the reader the system overview first, then sends them into narrower pages in a deliberate order.
Recommended Reading Order¶
- Nav2 Architecture and Tuning Guide
- Nav2 Servers and Data Flow
- Nav2 Costmap Architecture and Plugin Order
- Nav2 Planner Selection Guide
- Nav2 Controller Selection Guide
- Nav2 Behavior Server and Recovery Actions
Prerequisites¶
- Coordinate Frames, REP 105, and Navigation
- TF2 Transforms and Lookups in Practice
- Localization, State Estimation, and Frame Discipline
After This Page¶
- If you are tuning planning quality, continue to Nav2 Planner Selection Guide
- If you are tuning path tracking, continue to Nav2 Controller Selection Guide
- If you are debugging recoveries, continue to Nav2 Behavior Server and Recovery Actions
Why This Feels Different¶
This version assumes the site should behave more like a curated manual. The reader is given a section, a place within that section, and a clearer next step.
Likely product traits:
- stronger navigation hierarchy
- more curated landing pages
- clearer prerequisites and next steps
- more stable public structure for teaching and linking
Reader Experience¶
Good fit if you want:
- a documentation-site feel
- easier onboarding for newer readers
- clearer ownership of sections
- more predictable URLs and section names
Risk:
- less exploratory discovery
- harder to surface cross-cutting topics without adding more structure
- readers may stay inside one section longer than is actually ideal for robotics problem-solving