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 ยท Tenant Showcase ยท 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
Back to Evnto
Staff3 scenario rowsTier mix 1P / 0S / 14Pr
Scenario summary
Staff in Evnto balances premium presentation with live-event clarity.
Staff tooling aligns people, roles, and shifts across the event lifecycle so on-site execution stays coordinated. These scenarios stay Evnto-specific in workflow and copy, but the live visuals should still come from the active docs runtime instead of a local preset.
Scenario rows3Named modules that anchor this category's product story.
Unique parts11Distinct structures, patterns, and primitives in this category.
Dominant archetypeOperational indexThe prevailing interaction shape across these modules.
Scenario rows
Scenario modules
Each row below captures a product-grade module, the component spread behind it, and what to scrutinize when the runtime changes.
Read orderStart with the title and archetype, then inspect composition balance and the part sample.
Proof checkConfirm the lane still reads like one product module after the runtime changes tone, density, and contrast.
01
Scenario module
Staff Roster
Event staff directory with role badges, contact info, and availability status.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix1P / 0S / 4Pr
Inspect forCheck whether scanning rhythm, action placement, and row density still feel safe and fast.
Supporting partsRepresentative pieces behind this scenario lane.
PatternDataTable
Avatar
Badge
Tag
+1 more
02
Scenario module
Shift Manager
Shift scheduling grid with drag-and-drop assignment and overtime tracking.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix0P / 0S / 5Pr
Inspect forCheck whether scanning rhythm, action placement, and row density still feel safe and fast.
Supporting partsRepresentative pieces behind this scenario lane.
Table
Card
Badge
Avatar
+1 more
03
Scenario module
Check-In Tracker
Real-time staff check-in/check-out with GPS validation and time logging.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix0P / 0S / 5Pr
Inspect forCheck whether chart emphasis, contrast, and labels stay legible under the active provider.
Supporting partsRepresentative pieces behind this scenario lane.
Event-product flows showing how the system flexes for experience-heavy UIs.
Runtime controls
TenantRottay
EngineModern
Operators
Staff coordinatorsOps leadsSupervisors
The category has to stay legible for these roles even when a different tenant runtime shifts density or contrast.
Tempo and pressureScheduling and live verificationUse the scenario rows below to verify that hierarchy and control placement still hold up at this pace.
Design principles3 guardrails
Principle 01Make staffing gaps visible.
Principle 02Keep role state concise.
Principle 03Support fast check-in and attendance verification.
Active provider
Runtime audit
Rottay is rendering this appendix.
Use this page as a reference sheet: the scenario modules stay constant, while contrast, shell tone, and component personality respond to the active docs runtime.
Runtime
PlatformRottay
Rottay / ModernPlatform Flagship
Primary
#FFFFFFSecondary #A0A0A5
Radius
Compact runtime evidence across 3+ token signals.
14pxxl 18px
Density
normalBorder-light cards
Accent
Badge
roundedtop bar ยท solid dividers
Motion
springHover lift 2px
Keep stableStaff still needs to feel native for Staff coordinators, Ops leads, and 1 more even while the provider changes the surrounding chrome.
Stress pointScheduling and live verification means hierarchy, action placement, and contrast cannot become ambiguous under a different runtime.
Read as one laneOperational index should feel like one coherent chapter here rather than a stack of isolated component demos.