Sidebar & Navigation Rail — Learning Bundle
This learning bundle compares two different navigation patterns. A sidebar is wider and has labels or tools. A navigation rail is narrow and often uses icons. The bundle is not one standard interface term.
A real example
A wide dashboard shows a sidebar with labels. At medium width, it changes to an icon rail.
Main parts
- 01Current location
- 02Destination labels
- 03Focus order
- 04Responsive behavior
Use it when
Use this guide to choose a Sidebar or Navigation Rail. Check the number of places, screen width, and need for labels.
Do not use it when
Never remove labels when people may not know what the icons mean.
Name used in code
<aside> / <nav> Before you ship
Check that every member concept has its own name and link. Show all members in the same situation. Give a visible rule for when each one applies and which groups are valid. Never present the bundle as one canonical pattern or as parts that can be swapped freely.
Outcome: Use Sidebar & Navigation Rail — Learning Bundle to compare its member concepts. Keep their boundaries clear, then decide which members apply and which can work together. User context: A wide dashboard shows a sidebar with labels. At medium width, it changes to an icon rail. Learning bundle to unpack: Sidebar & Navigation Rail — Learning Bundle. Canonical members: Sidebar Navigation, Navigation Rail Why this comparison helps: Use this guide to choose a Sidebar or Navigation Rail. Check the number of places, screen width, and need for labels. Do not treat the bundle as one pattern when: Never remove labels when people may not know what the icons mean. Comparison requirements: Name every member concept on its own. Explain its job and limits. Show every member in the same real situation. Give a visible sign for when to use, combine, or leave out each member. Decision quality: Keep platform and evidence limits clear. Show which members can work together. Point out false matches, unsafe swaps, and cases that need another concept. Acceptance criteria: A reader can explain each member in one sentence and tell them apart in the example. They can defend the chosen member or valid group and open every canonical guide. Evidence and limits (evidence boundary): This is not a normative standard. Its name, limits, and expected behavior can change from one source to another. Unknowns to confirm: Target platform, decision setting, limits, and evidence needed to use, combine, or leave out members.
Check this request
Review the current use of Sidebar & Navigation Rail — Learning Bundle. Definition: This learning bundle compares two different navigation patterns. A sidebar is wider and has labels or tools. A navigation rail is narrow and often uses icons. The bundle is not one standard interface term. Release checks: Check that every member concept has its own name and link. Show all members in the same situation. Give a visible rule for when each one applies and which groups are valid. Never present the bundle as one canonical pattern or as parts that can be swapped freely. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.