Summary
Build a separate Lite event creation page that captures essential setup data (teams, supervisors, posts, schedule, equipment) and creates a local event record with a browser-generated event ID.
Motivation
Lite mode intentionally has no backend persistence and no venue presets. Users should be able to create an event from scratch in-browser and immediately move to dispatch.
Proposed solution
- Add /lite/create page with setup fields:
- Event name/date
- Teams
- Supervisors
- Posts (text locations only)
- Posting schedule
- Equipment
- Do not include venue presets or map UI.
- Generate local event ID in-browser.
- Persist event setup locally (IndexedDB preferred).
- Route to /lite/events/[localEventId]/dispatch after create.
- Keep form behavior similar to cloud create flow where possible, but fully local.
Alternatives considered
- Reuse current cloud create page with mode toggles. Rejected due to direct backend coupling and draft-event key assumptions.
- Skip setup and jump directly to dispatch. Rejected due to missing staffing/schedule context.
Mockups / Examples
- User clicks “Start Lite Mode”
- User completes Lite event setup form
- User continues to Lite dispatch page with prefilled setup data
Acceptance criteria
- Lite create page works with no auth and no backend reads/writes.
- Local event ID is generated client-side.
- Required setup fields persist locally and survive page refresh.
- User can proceed directly from Lite create to Lite dispatch.
- No cloud create flow regressions.
Priority
High
Additional context
Parent issue: #1
Depends on: #2
Summary
Build a separate Lite event creation page that captures essential setup data (teams, supervisors, posts, schedule, equipment) and creates a local event record with a browser-generated event ID.
Motivation
Lite mode intentionally has no backend persistence and no venue presets. Users should be able to create an event from scratch in-browser and immediately move to dispatch.
Proposed solution
Alternatives considered
Mockups / Examples
Acceptance criteria
Priority
High
Additional context
Parent issue: #1
Depends on: #2