Hierarchy depth
Use a simple NavigationMenu for a short list and TreeView for a genuinely nested structure.
Pair a stable hierarchy with a focused detail view.
Use for a document browser, customer workspace or service console where a persistent navigation pane supports a focused detail area.
Select a state to see what the interface should communicate. These are illustrative snapshots; try the live component below.
Customers / Atlas Labs
Highlight the active destination and keep its name in the content heading. Navigation should explain where the person is.
Try the working example ↓Navigation and details share the available width.
Choose useful minimum widths. Keep both panes usable and expose the divider to keyboard users.
Try the working example ↓Navigation collapsed · Atlas Labs
Keep a discoverable way to restore navigation. Collapsing a pane should preserve its content and the active draft.
Try the working example ↓Customer details
On narrow screens, offer a clear switch between navigation and details. Preserve the active record and draft across the switch.
Try the working example ↓Type a note in the detail pane. Resize the divider, collapse the first pane, then expand it. Check that your note remains. Focus the divider to try its keyboard controls.
Use a simple NavigationMenu for a short list and TreeView for a genuinely nested structure.
After opening a new view, make the destination clear. Restore focus to a useful trigger when returning.
Prioritize the current task. Avoid squeezing two desktop panes into unreadable columns.
The examples demonstrate interaction using sample data. Your application owns the real records, permissions and persistence.