Event page — /e/{slug}

Who opens it: anybody with the link — shared in a WhatsApp group, printed on a flyer, forwarded twice.

What they came to do: work out whether this is for them, when and where it is, and then register. Usually on a phone, often with a toddler in the room, sometimes on a bad connection at the back of a hall.

True when they leave: they either registered, or they know exactly when and where the event is and how to register later. Nothing they needed was behind a click they did not notice.

Decisions already made

• Sections are switches, not content (events.public_page.sections): the schedule is the event's days, the map is its venue, "about" is its description. Only what exists nowhere else — what to bring, FAQ — is carried as copy.
• A section with nothing in it is not rendered. An empty heading looks broken; its absence looks finished.
• An event whose page was never configured still shows about, schedule, map and register, so a link handed out by an organizer who never opened the editor is still usable.
• Server-rendered. The page has to work before JavaScript does.
• Counted server-side (L10); the beacon only reports installs, so a blocked script cannot hide a visit.

Open questions

• Capacity: show_capacity exists, but "12 places left" is pressure and "full" is a dead end. Which is honest?
• Multiple public registration forms (volunteer / special groups) currently render as stacked buttons. Does that read as a choice?
• No OG image until week 17. Is a text-only card enough for a WhatsApp forward, which is how most people will meet it?