Private Pro category · 1 compositions
Sidebars
Product workspace navigation with dense state and responsive collapse. 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 1 records currently carry implemented status. A dedicated detail becomes internally discoverable only after release readiness and a reviewed public preview.
Category contract
- Purpose
- Product workspace navigation with dense state and responsive collapse.
- Declared dependencies
- gummy-sidebar, gummy-tooltip, gummy-dropdown-menu
- Required review
- light, dark, responsive, keyboard-reviewed, rtl-reviewed, reduced-motion
How to evaluate Sidebars blocks
A sidebar is appropriate for a dense workspace with stable sibling destinations and contextual status. Organise items by customer task, keep the current location obvious, and avoid using persistent side navigation when a short linear flow would be easier to understand.
Connect groups, permissions, badges, and collapse behavior to real application state. Preserve content order, keyboard access, tooltips for icon-only states, and a usable small-screen alternative. Counts and alerts should have text equivalents and should not leak unauthorized workspace information.
Exercise collapsed and expanded modes, long labels, deep nesting, empty groups, restricted routes, notification changes, zoom, RTL, and phone navigation. Verify focus return after overlays and ensure responsive transformation does not create duplicate controls or unreachable page content.
List the canonical destinations, group order, permission rules, current-route matching, badge sources, and mobile transformation before implementation. State what remains visible when a group is empty or access changes during a session. Counts should come from authorized summaries and should degrade to unavailable, not zero, when the service cannot prove their value. Document focus return when a temporary mobile drawer closes after navigation or cancellation.
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.