Runtime fingerprintToken readout from the active provider chain.
Live DS
Runtime
Platform
Rottay
Rottay / ModernPlatform Flagship
Primary
#0A0A0ASecondary #6B6B6B
Radius
14pxxl 18px
Density
normalBorder-light cards
Accent
Badge
Compact runtime evidence across 3+ token signals.
Published DS package · Pattern Library · Rottay / modernShared route metadata for the active runtime, kept inline so the shell reads like a thin header band.
Navigation patterns should compress a lot of capability into a small footprint without becoming cryptic.
How to read this pageUse the showroom switchers in the sidebar to change engine and tenant. The comparison grid below keeps the active tenant and swaps engines so we can inspect the pattern instead of page-local editorial chrome.
TierPatternReusable workflow or composition contract.
GroupNavigationStart with discoverability.
Best paired withSearchCommandBarUsually lands inside CollectionWorkspaceSurface.
Live preview
Compare the same pattern across engines
Sidebar tenant drives this
Shortcuts Overlay
This comparison is the documentation surface. If the pattern only reads well inside local chrome, we should fix the pattern or its preview runtime before teams style around it.
Preview heuristics
3 items
Compare density, action placement, and state readability before aesthetic flavor.
Judge the pattern itself, not any showroom-local framing around it.
If the pattern only works with extra chrome, the pattern or preview runtime still needs work.
Structure pairing
3 items
SearchCommandBar
PageShell
WorkbenchHeader
Navigation pattern
ShortcutsOverlay
Check discoverability, mode switching, and whether overlay patterns are rendered through the active runtime rather than mocked locally.
Consumption
Import and usage
Treat the pattern as a reusable task contract. Keep route-specific business rules outside and use these snippets as the fast-reading baseline.
Consumption contract
Usage notes
3 items
Import from the published package rather than building route-local wrappers first.
Pass data, config, and callbacks while keeping product semantics in the consuming app.
Escalate to a surface only once the whole screen contract is stable, not just the task module.
Surface fit
3 items
CollectionWorkspaceSurface
CommandCenterSurface
RecordWorkbenchSurface
API surface
Props
6 rows
Shortcuts Overlay propsProp contracts stay readable across dark-first and light-first tenants.
6 props
1 required
5 optional
Fast readStart with required props, then scan defaults before dropping to per-row details.
Contract postureThis reference stays intentionally concise so the primitive contract remains scannable.