Event basics.

Basics is the copy people read before they decide to come. It is the first checklist step for a reason: a schedule and a ticket tier are no use if nobody can tell what the event is.

Open Basics from the Setup group in the event sidebar.

Name

The name shown everywhere: the events list, the public page, the ticket email, the PDF ticket.

Changing the name here changes what people see. It does not change the event's web address, which is fixed when the event is created. If you rename Summer Fest to Sunset Sessions, the link stays /event/summer-fest, so rename early if the address matters to you.

Event details

The long description, written in a rich editor. This is the body of your public event page: what the event is, who it is for, what to bring, what time to turn up, whether there is parking.

Write it for someone who has never heard of you. The two questions worth answering explicitly are what the ticket includes, and what happens if they cannot make it.

Formatting available to you covers headings, bold and italic, lists, and links. Keep the structure simple. It has to read well on a phone held in one hand at a bus stop, which is where most people will read it.

What uses this copy

• The public event page shows the name and the full details.
• The registration form shows the name and the schedule summary.
• The acknowledgment and ticket emails carry the name.
• The PDF ticket and badge carry the name.

One consequence: fixing a typo here fixes it everywhere at once, including on tickets already issued, because tickets are rendered when they are opened rather than frozen at purchase.

When to write it

The setup checklist counts basics as done once the event has both a name and details. Until then, the Overview page stays in setup mode.

You do not have to finish the copy before you build the rest of the event. Most people put a rough paragraph in, build the tiers and schedules, then come back and write it properly before sharing the link.