Runtime fingerprintToken readout from the active provider chain.
Live DS
Runtime
PlatformRottay
Rottay / ModernPlatform Flagship
Primary
#FFFFFFSecondary #A0A0A5
Radius
Compact runtime evidence across 3+ token signals.
Published DS package ยท System Layer ยท Rottay / modernShared route metadata for the active runtime, kept inline so the shell reads like a thin header band.
Shadows define hierarchy, but the real work is separation and focus.
Premium documentation needs depth that clarifies layers instead of adding mud. Our engines keep the same elevation semantics, while each one interprets them differently.
Default activemdPanels, dropdowns, and card focus states.
Maximum liftxlUsed sparingly for high-attention overlays.
Engine-awareTone shiftedCorporate, bold, or whisper-light depth.
Elevation ladder
Use contrast in small doses; clarity comes from progression.
sm
smtokens.shadows.sm
Cards at rest, low-emphasis modules, and contained utility chrome.var(--ds-elevation-1)
md
mdtokens.shadows.md
Default elevation for active cards, menus, and common overlays.var(--ds-elevation-2)
lg
lgtokens.shadows.lg
Prominent lift for modals, drawers, and command surfaces.var(--ds-elevation-3)
xl
xltokens.shadows.xl
Maximum emphasis for spotlight or high-focus overlay layers.var(--ds-elevation-4)
Engine comparison
Same elevation semantics
Shadow heuristics
Prefer border + subtle shadow for dense admin tables.
Lift interactives from sm to md on hover instead of inventing custom values.
Use lg and xl for modal families, command palettes, and editorial spotlight modules.
Dark or colorful backgrounds may need stronger surface contrast before stronger shadows.
Shadow usagePaste-ready example that shows the base contract first.