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 · Tenant Showcase · Rottay / modernShared route metadata for the active runtime, kept inline so the shell reads like a thin header band.
Palette
#0A0A0ARottay
Chrome
Modernrenderer posture
Radius
14pxsurface shape
Density
normalPlatform Flagship
Evnto
Ticketing
Ticketing
Active profilePlatform Flagship
Runtime postureRottay / modern
Event-product flows showing how the system flexes for experience-heavy UIs.
Runtime controls
TenantRottay
Back to Evnto
Ticketing
4 scenario rows
Tier mix 2P / 1S / 17Pr
Scenario summary
Ticketing in Evnto balances premium presentation with live-event clarity.
Ticketing interfaces are where commercial strategy becomes product UX. They need to feel premium while staying precise enough for pricing and rules. 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 parts12Distinct structures, patterns, and primitives in this category.
Dominant archetypeAnalytics surfaceThe prevailing interaction shape across these modules.
Operators
Revenue managers
Organizers
Marketing teams
The category has to stay legible for these roles even when a different tenant runtime shifts density or contrast.
Tempo and pressure
Commercial configuration and monitoring
Use the scenario rows below to verify that hierarchy and control placement still hold up at this pace.
Design principles
3 guardrails
Principle 01Show pricing logic clearly.
Principle 02Keep promotional rules traceable.
Principle 03Surface revenue impact next to controls.
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
Ticket Types
Ticket tier management with pricing, quantity limits, and early-bird schedules.
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.
02
Scenario module
Pricing Builder
Dynamic pricing configuration with time-based tiers and bundle options.
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.
03
Scenario module
Promo Codes
Discount code management with usage limits, validity periods, and tracking.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix1P / 0S / 4Pr
Inspect forCheck whether chart emphasis, contrast, and labels stay legible under the active provider.
04
Scenario module
Sales Dashboard
Real-time ticket sales metrics with revenue projections and channel breakdown.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix0P / 1S / 4Pr
Inspect forCheck whether chart emphasis, contrast, and labels stay legible under the active provider.
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
Platform
Rottay
Rottay / ModernPlatform Flagship
Primary
#0A0A0ASecondary #6B6B6B
Radius
14pxxl 18px
Density
normalBorder-light cards
Accent
Badge
Motion
Compact runtime evidence across 3+ token signals.
roundedtop bar · solid dividers
springHover lift 2px
Keep stableTicketing still needs to feel native for Revenue managers, Organizers, and 1 more even while the provider changes the surrounding chrome.
Stress pointCommercial configuration and monitoring means hierarchy, action placement, and contrast cannot become ambiguous under a different runtime.
Read as one laneAnalytics surface should feel like one coherent chapter here rather than a stack of isolated component demos.