A conference site whose speakers and schedule stay editable as they change
A conference site is never finished until the event is over. Speakers confirm late, sessions swap rooms, a sponsor joins in the last month. The structure should be settled early and the moving parts, speakers and sessions above all, should live somewhere you can edit in minutes without touching the layout.
The pages a conference needs
| Page | Audience | Must answer |
|---|---|---|
| Home | Everyone | What, when, where, who it's for, ticket button |
| Speakers | Attendees, press | Who's speaking, on what, with a photo and short bio |
| Schedule | Attendees | Session times, rooms or tracks, breaks |
| Venue and travel | Attendees | Address, access, nearby hotels, how to get there |
| Tickets | Buyers and their managers | Prices, what each ticket includes, refunds, invoices |
| Sponsors | Current and prospective sponsors | Who's sponsoring, packages, how to enquire |
| Code of conduct | Everyone | Expected behaviour, how to report, who responds |
| FAQ | Everyone | Recordings, food, Wi-Fi, accessibility, childcare |
The ticket page is often read by someone's manager, so make it printable and plain: what's included, VAT or tax status, and how to get an invoice.
Speakers and sessions as collections
Hard-coding speakers into a page means every late change is a layout edit. Anticode's CMS lets a project hold collections with typed fields, edited in the dashboard, with each collection listed at /<collection>/ and each entry at its own address beneath it. Two collections cover most conferences:
- Speakers
- Name, role and organisation, photo, short bio, talk title, links. Each speaker gets a page at an address like
/speakers/maya-chen, which speakers will share themselves. - Sessions
- Title, speaker name, start time, length, room or track, level, abstract. Editing one session's time is a single field change.
Agree the fields early with whoever will maintain them, and decide how you'll show times: one time zone, written out, on every session. The update an event schedule workflow covers who edits what in the final weeks.
Tickets
Anticode doesn't sell tickets itself. There's one payment link per account, so every ticket button opens the same checkout from your own provider, such as Stripe Payment Links, PayPal, Lemon Squeezy, Shopify or Whop; set it up there to offer each ticket type. That covers simple paid tickets well. If you need seat limits, ticket transfers, QR check-in or discount codes per attendee, use a ticketing service and link to its pages from the Tickets page.
The code of conduct is a working page
A code of conduct only helps if attendees can act on it during the event. Beyond the expected behaviour, give a named contact team, a phone number staffed on the day, what happens after a report and how reporters are protected. Link it from the footer of every page and from the ticket page, so buying a ticket means having seen it.
Call for speakers and sponsor enquiries
Two forms matter before the event. A call-for-speakers form asks for name, talk title, abstract, level and any previous talks; sponsor enquiries ask for company, contact, budget range and the package of interest. The built-in contact form only asks for a name, email and message, so forms with these fields are custom forms tied to a site function, with up to 30 plain-text fields. Both are saved in your dashboard, sealed at rest, and can be routed by connector: proposals into Airtable or Notion for the programme committee to review, sponsor enquiries into HubSpot or a Slack channel. The run a call for speakers workflow covers the review side.
How Anticode builds a conference site
As a conference website builder, Anticode works from a brief like "a site for DataCraft North, a one-day data engineering conference in Manchester on 4 November, two tracks, about 300 attendees, with speakers, schedule, venue, tickets, sponsors and code of conduct". The Architect turns that into a plan with separate pages and asks where the answer changes the build. Then set up the speaker and session collections, add the first entries, and refine the look.
For a sense of what's possible, the template gallery includes FORM/26, a design conference site with kinetic type. Using a template copies it into your project with no model call and nothing off your limits, and you can change its words from there. It's an app build written by Anticode's model, so a design-engine site in a similar style is the other route. Technical (IBM Plex Sans) and Swiss (Inter Tight) suit most tech conferences; Brutalist (Archivo) suits design and arts events.
Limits
- No ticketing system. Payment links only; no seat caps, transfers or check-in.
- No personal agendas or attendee logins. Visitors can't save sessions or sign in.
- No live streaming or embedded video players. Link to the stream on its own platform.
- English only. International conferences can't publish translated versions from Anticode.
Questions people ask
Can several organisers edit the speakers?
Yes, in a Team workspace. Owners, admins and members can work on the project; members can't delete projects or take sites down.
Can I reuse the site next year?
Yes. Keep the project, replace the session and speaker entries in their collections, and change the dates. Version history keeps your most recent saves, so export a copy if you want this year's site kept in full.
Is a smaller event better as a single page?
For one evening with three talks, yes; see the event website guide. Multi-page structure pays off with tracks, many speakers and sponsors.