Navigation rail
The app's primary navigation, on the chrome tier.
Quick usage
Import the shared component; never copy its markup into a feature. The Web TSX tab beside the live stage has a complete, working example.
import NavRail from '@/shared/components/NavRail';Live stage and code
The live component and its controls on the left, the code on the right; change a control and the code follows: Web TSX (the component in a working example), Tailwind and HTML (the markup it renders, with its data attributes), React Native, SwiftUI and Jetpack Compose. The header theme switch drives every stage.
Props
Read from the component's source when the docs build: names and defaults from its signature, types and descriptions from its JSDoc. A blank type means the prop has no JSDoc yet.
| Prop | Type | Default | Description |
|---|---|---|---|
items | - | - | - |
value | string | - | - |
onChange | (id: string) => void | - | - |
label | string | 'Main' | Accessible name of the rail. |
Source: frontend/src/shared/components/NavRail/NavRail.js
DOM contract
What the rendered element carries: the data attributes its styles key on, its roles and ARIA, its focus style, and whether its stylesheet draws the 44px hit boundary. Also read from the source.
| Data attributes | data-ds |
| Roles | Native element semantics only |
| ARIA | aria-currentaria-label |
| Focus | Styles :focus-visible in its own stylesheet |
| 44px hit boundary | Yes: a ::after in NavRail.module.css |
Accessibility and touch
Rows are 36px with full-width targets.
Visible height 28px. The ::after boundary adds 8px above and below, so a gloved finger lands on a 44px target while the row keeps its density.
Rules and constraints
Use it for
- Top-level destinations and the current job's sections.
Avoid
- Never more than one level of nesting in the rail.
Constraints
- --bg-chrome; 24px header icons; the active row steps to --bg-active.