Create an event website with every fact attendees need and a form that registers them
An event page has to answer five questions without making anyone scroll for them: what it is, when (with the time zone), where, what happens, and how to register. Get those right, send each registration somewhere your team will see it, and most of the emails you'd otherwise answer never get sent.
The facts, stated so they can't be misread
- Date
- Day of the week as well as the date: "Thursday 12 March 2027". The weekday catches typos.
- Time and time zone
- Start and finish, with the zone written out: "18:30 to 21:00 GMT". For online events, add one or two other zones your audience lives in, or say "UK time" in words.
- Place
- Venue name, full address, which entrance and which floor. For online events, say which platform and when the joining link is sent.
- Who it's for
- One line, so the wrong people don't register and the right ones don't hesitate.
- Cost
- Free, or the price and what it includes. If there's a ticket link, put it next to the price.
- Access
- Step-free access, toilets, seating, captions for online sessions. People who need this information won't register without it.
The agenda
Even a two-hour meetup benefits from a short running order: doors, talks, break, close. It tells people whether they can arrive late or leave early, and it's the part most often shared in a group chat. Keep times in the same zone as the header. For a multi-day programme with several tracks, give the schedule its own page, or look at the conference website guide, which deals with speakers and sessions that change.
Registration: what to ask
Ask only what you'll use on the day or soon after:
- Name and email, always.
- Organisation or role, if it helps you plan badges or seating.
- Access or dietary needs, as a free-text field.
- How they heard about it, only if you'll actually act on the answer.
The built-in contact form asks only for a name, email and message, so a registration form with these questions is a custom form tied to a site function, with up to 30 plain-text fields. Describe the form you want when you write the request, then check the preview to make sure it asks those questions; adjust with a change request if not. A confirmation line under the form ("You'll get a reminder the day before") helps, but only promise what you'll send yourself, because Anticode doesn't email registrants.
Sending each registration to Slack or a spreadsheet
Each registration is saved in your dashboard, sealed at rest, and can be emailed to you. From the dashboard you can also add connectors, so every sign-up goes where the organising team already works:
| Destination | Good for |
|---|---|
| Slack or Discord | A live feed in the organisers' channel; good for small events where someone greets each sign-up |
| Google Sheets | A running headcount and a list to print on the day; works through an Apps Script web app |
| Airtable or Notion | Combining registrations with speakers, volunteers and tasks |
| Mailchimp or Kit | A separate newsletter sign-up on the page; these two take newsletter sign-ups only, not registrations |
| A webhook | Your own system, or an automation tool |
Connectors send each submission once, without retries. The dashboard copy is the record; reconcile the two before you print badges. The guides to form submissions to Slack and to Google Sheets cover setup.
Building it with Anticode
Using Anticode as an event website builder, start with the facts in one go: "an event site for Leeds Data Night, Thursday 12 March 2027, 18:30 to 21:00 GMT at the Corn Exchange, three talks and drinks, free registration with name, email and access needs". The Architect checks the plan and asks where the answer changes the build, such as whether the agenda should be a separate page. Pick a design system that suits the tone: Technical (IBM Plex Sans) for a tech meetup, Playful (Fredoka) for a family day, Brutalist (Archivo) for an arts night.
If the event has several parts, ask for separate pages such as an agenda, a venue page and an FAQ. After the event, change the page to a short write-up with photos rather than leaving a past date at the top.
Limits
- No ticketing. For paid events, point the ticket button at a payment link from Stripe Payment Links, PayPal or another supported provider. There are no seat limits, ticket types or QR check-in.
- No capacity cap on the form. The form doesn't close itself when full; take it down or change the wording when you hit your number.
- No reminders or calendar invites. Send those from your email tool.
- Free plan allowance. Submissions over the free plan's monthly allowance are held until you upgrade; check before a big launch.
Questions people ask
Can I put several events on one site?
Yes. A CMS collection can hold events with typed fields such as date, place and description, each served at its own address. See the community events calendar page.
Do attendees need an account to register?
No. The registration form is on a public page and needs nothing from attendees but the answers.
Can I use my own domain for one event?
Yes, on a paid plan, including a subdomain such as datanight.example.org.