Private Pro category · 8 compositions
Navbars
Responsive site and product navigation with honest hierarchy. These records are manifest-derived and source-free; an implemented status does not imply manual verification, release readiness, entitlement protection, or availability for purchase.
Manifest items
All 8 records currently carry implemented status. A dedicated detail becomes internally discoverable only after release readiness and a reviewed public preview.
Documentation rail
Category contract
- Purpose
- Responsive site and product navigation with honest hierarchy.
- Declared dependencies
- gummy-navigation-menu, gummy-button, gummy-sheet
- Required review
- light, dark, responsive, keyboard-reviewed, rtl-reviewed, reduced-motion
How to evaluate Navbars blocks
Select a navbar for the real hierarchy of the site or product, not for the number of menu effects it demonstrates. Primary destinations, account actions, and contextual navigation should remain distinguishable, with less important routes placed in a predictable secondary structure.
Connect navigation to canonical route data and preserve the current-page signal, focus return, escape behavior, and scroll handling. Responsive menus need a deliberate close strategy, correct labelling, and no hidden focusable content. Avoid using a menu when a simple list of links is clearer.
Exercise every route, submenu, sign-in state, language direction, keyboard path, viewport, zoom level, and history transition. Confirm that product status and pricing links reflect reality, external destinations are identified where useful, and no paid-source location appears in public markup.
Define route labels, hierarchy, current-page matching, signed-in variants, permission visibility, external destinations, and the owner of each group in one navigation record. Provide explicit responsive behavior rather than leaving items to disappear by available width. A hidden link is not an authorization control, so server access rules remain a separate implementation requirement.
Boundary
Public pages contain only approved names, purposes, dependency aliases, requirements, status, and any future reviewed image preview. Editable paid source, test paths, release locations, and entitlement details remain private.