Demo: Digital-Garden Slice¶

This is a mock slice of the site if it leaned harder into digital-garden exploration. The emphasis is on wandering through related notes, not on following a single prescribed reading order.

You Arrived At¶

Nav2 Architecture¶

Nav2 is easier to learn when you treat it as a connected cluster of notes rather than one giant subsystem page. From here, a reader would typically branch in several directions depending on the problem they are actually trying to solve.

Nearby Notes¶

If Your Real Problem Is...¶

"The robot plans but moves badly": jump to Nav2 Controller Selection Guide
"The robot localizes badly": jump to Localization, State Estimation, and Frame Discipline
"The robot sees obstacles wrong": jump to Nav2 Costmap Architecture and Plugin Order
"The recovery behavior feels brittle": jump to Nav2 Behavior Server and Recovery Actions

Trails You Might Follow¶

Nav2 Architecture -> Costmaps -> Range Sensor Layer -> Denoise Layer
Nav2 Architecture -> Behavior Trees -> BT Action Nodes -> Custom BT Plugins
Nav2 Architecture -> Localization -> AMCL Tuning -> Localization Recovery

Backlinks-Style Context¶

This page would feel more like a note in a web of notes. Instead of asking the reader to stay inside one official section, it would encourage movement across Navigation, Foundations, Hardware, and Perception as soon as the problem requires it.

Likely product traits:

lighter sense of chapter order
heavier use of related links and backlinks
more note-like landing pages
more acceptance that readers arrive in the middle

Reader Experience¶

Good fit if you want:

a knowledge-base feel
exploratory browsing
more serendipitous discovery
weaker boundaries between sections

Risk:

new readers may feel less guided
section ownership becomes fuzzier
public URLs and hierarchy matter a bit less than note connectivity