The desktop shell pairs Menu with Breadcrumb. Use one source of navigation items and expose the current path in both views. The page content remains a separate landmark.
Responsive behavior
At narrow widths, move navigation into the shared Drawer so it receives dialog focus management and scroll containment. Keep the open action visible, make the drawer title meaningful, and provide an explicit close action. Keep breadcrumbs available to explain the current location after the desktop rail is hidden.
Accessibility
Give the navigation landmark a concise label and expose the active link with aria-current="page".
Keep breadcrumb parent locations as links and mark only the current location as the page.
Use the Drawer focus trap and return-focus behavior; do not leave a second hidden navigation tab sequence active.
Allow long navigation lists to scroll inside their bounded drawer body.
Do and don’t
Do
Keep navigation data and the current route consistent across desktop and mobile presentations.
Don’t
Hide the current page or make a mobile drawer the only way to understand the location hierarchy.
The example uses fixture links only and makes no route or network requests. Its Preview and Code/Copy tabs use src/components/design/examples/source/navigation-shell-pattern.tsx; there is no pattern-level property playground.