Event
Event
Event workspaces
Each EventStation event has its own workspace: public microsite, content, assets, program, registration settings, communications, and operations readiness.
One EventStation instance can support multiple event workspaces in parallel while each event keeps its own identity, content, and operational context.
Event
EventStation multi-event map
One EventStation instance connects multiple distinct event workspaces.
Demo suite
#10 EventStation Training Showcase
Purpose: Explains EventStation with EventStation.
Focus: submissions, review, program, registration, operations.
#20 Quรฉbec Destination Library
Purpose: Shows a rich destination microsite.
Focus: destination content, public assets, visitor experience.
#30 Montrรฉal Experience
Purpose: Shows a second independent public event.
Focus: multi-event proof, separate identity, separate content.
Isolated per event
Each event can evolve independently.
Content
Pages and copy stay scoped to the selected event.
Branding
Hero, colors, identity, and page tone can differ by event.
Assets
Media and public files remain tied to the event context.
Program
Days, sessions, rooms, tracks, and schedule are event-specific.
Registration
Products and participant paths belong to the event.
Communications
Templates, audience state, and history stay event-scoped.
Operations
Readiness, visual review, and launch controls are separate per event.
Shared platform foundation
EventStation provides the shared foundation while each event keeps its own context.
Admin shell
Operators work from a shared admin surface.
User access
Access can be governed by event context.
Demo Manager
Demo-suite controls stay centralized and deliberate.
Visual QA
Visual review can compare multiple public events.
Architecture Atlas
Architecture references stay shared across event work.
Operational patterns
Safe command boundaries apply across the platform.
Built with EventStation. This training showcase keeps real email and real payments outside the public journey.