Events

Drafting, publishing, and what each visibility tier actually means.

The editor is the page

An event in Studio is not a form beside a preview. It is the event page itself, and you change a part of it by clicking that part. The title you click is the title people will read; when you are done, there is nothing to translate in your head between the two.

Four states, and what each one means

  • draft is yours alone. Nobody else can open it, it is not listed anywhere, and it does not appear in search. Work in it for as long as you like.
  • unlisted is reachable by anyone holding the link, but Venued never puts it in a feed, a listing or a search result. This is the state for a private party, a soft launch, or a test.
  • public is the ordinary published state: listed, searchable, and eligible to be recommended.
  • cancelled keeps the page alive and says clearly that the event is off. It is not a delete, on purpose: people who bought a ticket or made plans need somewhere to land.

Where it happens

An event has one location, chosen from venues Venued already knows or added by you. Picking a venue that is on Venued links the two: the event shows up on the venue’s own page, and the venue’s details fill themselves in.

An event with no physical location is online, which is a real answer rather than a missing one. Mark it online and you can store the joining link with it: Zoom, Google Meet or Microsoft Teams. Venued holds a link you already have. It does not create the meeting for you.

Repeating events

An event that happens again is a series. Each occurrence is its own event with its own date, tickets and door, and they are grouped so that somebody browsing sees the thing rather than twelve copies of it.

Events through the API

Everything above is Studio. The same events are readable and writable with an API key: GET/v1/events for your events, GET/v1/events/{eventId} for one of them, POST/v1/events to draft a new one and PATCH/v1/events/{eventId} to change it.