DS
Published-package documentation wired to the real DS runtime so the same routes reveal how tenant and engine reshape identical component contracts.
Rottay / modernPublished package
Premium Docs

Design System Showroom

Primary
#FFFFFF
Rottay
Radius
14px
Surface shape
DensitynormalPlatform Flagship
NavigatorLibrary map
8 sections212 routes
Foundations first, then primitives, patterns, structures, and surfaces. Keep this rail legible enough to scan without hunting.
Foundations4 documented routes
4
Tokens
Themes
109
93
49
36
3
1
2
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 · Page Structure · Rottay / modernShared route metadata for the active runtime, kept inline so the shell reads like a thin header band.
Palette
#FFFFFFRottay
Chrome
Modernrenderer posture
Radius
14pxsurface shape
Density
normalPlatform Flagship
Structures/Headers
HeadersStructure3 engines
FormHeader

Form Header

Headers group export for page-level framing around reusable tasks.
What it framesHeader for form pages with step indicator and submit
What it should proveHeaders establish page tone, hierarchy, count, and action priority in the first few seconds.
Engines
Icons
Primitives93 documented routes
Display
Inputs
Feedback
Layout
Navigation
Overlay
Patterns49 documented routes
Data
Forms
Visualization
Communication
Feedback
Workflow
Navigation
Commerce
Customization
Identity
Shell
StructuresCurrent section
24
Headers
Mobile Header
Collection Header
Surfaces36 documented routes
Admin
Data
Experience
Forms
Operations
Workspace
Verticals3 documented routes
Platform
Bit Hire
Evnto
Playground1 documented routes
Playground
Developers2 documented routes
Developers
14pxxl 18px
Density
normalBorder-light cards
Accent
Badge
roundedtop bar · solid dividers
StructuresHeadersForm Header

Form Header

Active profilePlatform Flagship
Runtime postureRottay / modern
Structures reference for Form Header.
Runtime controls
TenantRottay
EngineModern
LayerStructure tierPage framing around reusable tasks.
GroupHeadersShares the same audit lens and pairing rules as its group.
Enginesclassic / modern / rusticExpect parity in spacing, priority, and section rhythm.
Audit trayUse this page to judge whether the structure creates hierarchy before the surrounding surface starts doing the heavy lifting.
Review 01context signalShould be obvious on the first scan without relying on surface chrome for rescue.
Review 02primary action emphasisShould stay clear once actions, counts, and support context compete for attention.
Review 03space efficiencyShould keep dense content readable instead of turning the screen into a flat stack.
Common pairings
stats gridsdetail panelscommands
Usually lands in
DashboardSurfaceListSurfaceDetailSurface

Live preview

Compare rhythm, action placement, and supporting context across engines while the active tenant remains real.
classicmodernrustic
Compare enginesLook for spacing, action placement, and section rhythm before brand flavor.
Ignore wrappersJudge the structure itself, not route-level surface chrome or page copy.
Escalate laterMove higher only when the route contract or workflow packaging is the missing piece.
Engine comparisonForm Header render checkEach engine gets the same structure with the same tenant. Focus on spacing, hierarchy, and action cadence rather than wrapper chrome.
Rottay3 live engines

Review checklist

These are the checks that should feel obvious on the first pass, before you audit the surrounding surface or route-level content.
Check 01context signalShould be obvious on the first scan without relying on surface chrome for rescue.
Check 02primary action emphasisShould stay clear once actions, counts, and support context compete for attention.
Check 03space efficiencyShould keep dense content readable instead of turning the screen into a flat stack.
Layer fitStructures arrange page framing around reusable tasks. They should create order without taking over the whole surface contract.
Primitives

Import and usage

The structure should stay easy to consume from the published package: one import, one usage shape, and no page-local wrapper assumptions.
Consumer contract
Import onceConsumers should get the structure from the published package without extra page-local wrappers.
Stay declarativePass data, actions, and slots. Avoid hiding layout decisions inside screen-specific glue code.
Let surfaces finishStructures frame the page. Surface-level route shells should still own the broader contract.
Dashboard Header
Detail Header
Edit Header
Form Header
Workspace
Shell
Record
Dashboard
Feedback
Same tenant, isolated engine
ClassicAnt Design
Live provider
Header structure
Check whether the page starts with context, count, and action priority in the right order.
Back to members
  1. Workspace
  2. /
  3. Members
  4. /
  5. New member
ModernDaisyUI
Live provider
Header structure
Check whether the page starts with context, count, and action priority in the right order.
Back to members
3 required fieldsInvite sends immediately
RusticVanilla CSS
Live provider
Header structure
Check whether the page starts with context, count, and action priority in the right order.
Back to members
Workspace/ Members/ New member
Patterns
Structures
Surfaces
Stay here whenThe missing piece is section rhythm, chrome placement, or page-level context.
Escalate whenYou need reusable workflow behavior or a full route shell beyond the framing.
Common pairings
stats gridsdetail panelscommands
Usually lands in
DashboardSurfaceListSurfaceDetailSurface
ImportPublished package entrypoint, ready to copy.
tsx
1 line
Consumption
Runtime-aware snippet
ImportTSX
Quick copy
import { FormHeader } from '@rottay/design-system';
UsagePaste-ready example that shows the base contract first.
tsx
5 lines
Consumption
Runtime-aware snippet
<FormHeader
  config={config}
  slots={slots}
  actions={actions}
/>
OnboardingCreate teammate profileStart with workspace identity, access level, and routing preferences.
3 required fields
Invite sends immediately
The header carries route context, action intent, and field expectations before the form begins.
  1. Workspace
  3. Members
  5. New member
OnboardingCreate teammate profileStart with workspace identity, access level, and routing preferences.
The header carries route context, action intent, and field expectations before the form begins.
Save draft
Create member
OnboardingCreate teammate profileStart with workspace identity, access level, and routing preferences.
3 required fields
Invite sends immediately
The header carries route context, action intent, and field expectations before the form begins.
UsageTSX
Quick copy