User journeys

Six canonical journeys flow through the Calendar — three discovery (find an event), two action (apply / register), one submission (submit an event). Every entry path either funnels into details + outbound action, or into a coverage planning conversation for the editorial team.

Discovery journeys

1. Casual browse: home > /calendar (landing) > scroll rails (this week / closing soon / by country / by category) > pick event > details > website/registration outbound.
2. Country-deep dive: /calendar > country chip (e.g. "Egypt") > /calendar/events/countries/egypt > filtered grid > details.
3. Search-driven: external SERP > schema.org Event JSON-LD click > directly to /calendar/events/:slug (details).

Action journeys

1. Register for an event: details > "Register" CTA > registrationUrl (analytics event: calendar.register.click).
2. Apply to a program: details > "Apply" CTA > applyUrl (analytics event: calendar.apply.click). For accelerator/incubator categories with applicationDeadline ≤ 7 days, the CTA is upgraded to "Apply (closing soon)".

Submission journey

Organizer flow: /calendar/submit form > paste organizer details + dates + source URL > submit > admin queue (verificationStatus=pending) > editorial verification (3 gates) > publish (verificationStatus=verified) OR request more info (verificationStatus=needs_info) OR reject (verificationStatus=rejected). Submitter is emailed at every state transition.