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.
Event Management in Evnto balances premium presentation with live-event clarity.
Event management is the planning spine of Evnto. These views define the event, its timing, and the operational shape the rest of the product must support. 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 rows4Named modules that anchor this category's product story.
Unique parts14Distinct structures, patterns, and primitives in this category.
Dominant archetypeConfiguration flowThe 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
Event List
Event directory with calendar and list views, status filters, and quick creation.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix1P / 1S / 3Pr
Inspect forCheck whether scanning rhythm, action placement, and row density still feel safe and fast.
Supporting partsRepresentative pieces behind this scenario lane.
PatternDataTable
CollectionHeader
Badge
Calendar
+1 more
02
Scenario module
Event Editor
Full event creation form with date/time pickers, venue selector, and media upload.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix0P / 0S / 5Pr
Inspect forCheck whether grouping, spacing, and field hierarchy still feel calm when the runtime changes.
Supporting partsRepresentative pieces behind this scenario lane.
FormBuilder
DatePicker
TimePicker
Upload
+1 more
03
Scenario module
Recurring Events
Recurrence pattern builder with weekly, monthly, and custom repeat schedules.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix0P / 0S / 5Pr
Inspect forCheck whether grouping, spacing, and field hierarchy still feel calm when the runtime changes.
Supporting partsRepresentative pieces behind this scenario lane.
FormBuilder
Select
DatePicker
Checkbox
+1 more
04
Scenario module
Event Timeline
Day-of schedule with draggable time blocks, speaker assignments, and break periods.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix0P / 0S / 5Pr
Inspect forCheck whether sequence, progress cues, and handoff points remain easy to follow.
Supporting partsRepresentative pieces behind this scenario lane.
Event-product flows showing how the system flexes for experience-heavy UIs.
Runtime controls
TenantRottay
EngineModern
Operators
OrganizersProducersOps leads
The category has to stay legible for these roles even when a different tenant runtime shifts density or contrast.
Tempo and pressurePlanning and pre-event configurationUse the scenario rows below to verify that hierarchy and control placement still hold up at this pace.
Design principles3 guardrails
Principle 01Keep chronology legible.
Principle 02Separate setup from live operations.
Principle 03Support rich configuration without visual clutter.
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 stableEvent Management still needs to feel native for Organizers, Producers, and 1 more even while the provider changes the surrounding chrome.
Stress pointPlanning and pre-event configuration means hierarchy, action placement, and contrast cannot become ambiguous under a different runtime.
Read as one laneConfiguration flow should feel like one coherent chapter here rather than a stack of isolated component demos.