Primitive usage
Composable modules for workspace-level dashboard pages.
- PageHeader: Use once per page to define heading hierarchy and context badge.
- SectionShell: Wrap each functional block in a titled section card.
- StatusCard: Render loading, empty, error, and success states with consistent badge tones.
- ActionGrid: Present 2-4 primary actions with equal visual priority.
Accessibility checks
Minimum checks before shipping workspace UI updates.
- Keyboard flow: tab order should move from page header actions to section actions with no focus traps.
- Labels: each actionable control requires clear, descriptive label text and optional aria-label for context.
- Focus order: primary actions should appear before secondary actions in DOM order.
- Status semantics: state labels should be visible and not rely on icon color alone.
Adoption links
Apply these primitives across key workspace pages.
Templates page
Reference implementation for state patterns and action grids.
Design system page
Example of governance-focused content with shared primitives.
Members page
Membership workflows with reusable state and action cards.
Connections page
Integration management route using the same structural system.
