Skip to content
Event landing page template

An event site that takes registration requests.

Public schedule, speakers and tickets pages, a registration request form with capacity and waitlist checks, and an admin area where you approve each request. Your AI replaces the sample event with yours. See an event demo and launch checks.

Updated

What is in the template

Checked against the template routes, database seed and registration code (template manifest event-template-manifest-r8).

  • Home

    /

    Hero with register buttons, a ticket summary, the programme, speakers and a closing register button. Until the event is published it shows a not-published message instead.

  • Schedule, Speakers, Tickets

    /schedule, /speakers, /tickets

    Public pages read from the event database, so edits in the admin area appear on the site.

  • Register

    /register

    The registration request form: name, email and ticket type required; company, role and dietary requirements optional.

  • Dashboard

    /dashboard

    Signed-in views for attendee, check-in and organizer roles, including a check-in screen.

  • Admin

    /admin

    Overview, Registrations, Team, Tickets, Schedule, Speakers, Communications and Settings, including publishing and opening registration.

How a registration request works

The form records a reservation request. It does not take payment or issue a ticket.

  1. A visitor sends a request. They choose a ticket type and fill in the form. No payment is collected.
  2. The server checks it. The event must be published with registration open, and the ticket type must be within its sales window. A full ticket type adds the request to its waitlist if one is enabled, otherwise the form says registration is closed. A repeat request for the same ticket and email returns the existing reservation instead of a duplicate.
  3. The visitor gets a reservation code. The receipt says the request is waiting for organizer approval, or is on the waitlist. An acknowledgement email is attempted when the site email capability is available. Otherwise the receipt says email delivery is still pending.
  4. You decide in the admin area. In Registrations you confirm, waitlist, promote or cancel each request and can export a CSV. No decision email is sent automatically, so use Communications to email registrants by status, ticket type or check-in.
Read the plugins guide

What to check before launch

  • No payment, checkout or issued tickets. A confirmed registration is a status in your admin area.
  • The receipt tells visitors they will receive a decision by email, but the template sends none automatically. Send it from Communications or change that line.
  • All emails depend on the site email capability. Send a test before launch.
  • Public account signup is turned off in the template settings.
  • The seeded Signal Summit event, dates, venue, ticket types, sessions and speakers are sample data. Replace or delete all of it, including speaker employers, before publishing.

Details to replace first

The template ships a sample date, venue and format so its pages render. Replace them with your confirmed details in the admin Settings page before you publish.

Date and time

Add your confirmed date and time

Location

Add your venue or online link

Format

In person, online, or hybrid

Copy the prompts

Use the first prompt to start from the template, then the second to adapt it by event type. Paste into ChatGPT or Claude with Boomlink connected. They are sample instructions, not a record of a finished build.

Start from the template

Start from the Boomlink event template and edit it for my event.

The template ships public Home, Schedule, Speakers, Tickets and Register pages, a registration request form with capacity and waitlist checks, and an admin area for registrations, tickets, schedule, speakers, communications and settings. It seeds a sample event called Signal Summit. It does not take payment or issue tickets.

Replace the sample event with my details:
- Event name, summary and type: [launch, webinar, meetup, or workshop]
- Date, time, timezone and venue: [your confirmed details]
- Ticket types and capacity: [names, capacity, and whether each has a waitlist]
- Schedule sessions: [titles, times, rooms]
- Speakers: [names and roles, only if confirmed]

Remove every sample speaker and session I do not confirm. Do not invent dates, venues, speaker names, employers or attendance numbers. Keep the wording that a request is not a confirmed ticket. Send a test registration with non-sensitive data, show me the preview, and wait for my approval before publishing.

Adapt by event type

Adapt my Boomlink event site for a specific event type.

- For a product launch: emphasise what is launching and the first-look value.
- For a webinar: emphasise the topic, the takeaway, and that it is online.
- For a meetup: emphasise the community and the in-person location.
- For a workshop: emphasise the hands-on outcome and any prerequisites.

Keep date, location, and speaker details unchanged until I confirm new ones.

Event landing page FAQ