Additional Event Pages

Sometimes an event needs more than the standard registration and schedule screens — a code of conduct, a travel/accommodation guide, an FAQ, sponsor terms, or a "What to expect" page. The Additional Event Page DocType lets you attach these extra, event-specific pages to a single event without touching any templates or code.

Each Additional Event Page belongs to one event, carries its own rich-text content, and is reachable at its own URL underneath that event.

Before you start

You need an existing event to attach the page to. If you haven't created one yet, see Create an Event.

By default, only users with the System Manager role can create or edit Additional Event Pages.

Create an additional page

1. In Desk, go to Additional Event Page and click New (/app/additional-event-page/new).
2. Fill in the fields:
   • Title (required) — the page heading, e.g. Code of Conduct.
   • Event (required) — the Buzz Event this page belongs to.
   • Route — the URL slug for the page. Leave it blank to have one generated for you (see below).
   • Content (required) — the body of the page, edited in the rich-text editor.
   • Is Published? — turn this on when the page is ready to go live.
3. Save.

How the route is set

The Route is the slug that appears in the page's URL. You can type your own (for example code-of-conduct), or leave it empty.

When you save a page with Is Published? turned on and no route filled in, Buzz generates one automatically from the Title: the title is slugified and underscores are converted to dashes. So a title of Travel & Stay becomes a route like travel-stay.

Tip: pick short, lowercase, dash-separated routes. If you want a specific URL, set the route yourself before publishing rather than relying on the generated one.

Route uniqueness

Routes only have to be unique within a single event — two different events can each have a faq page without clashing. If you try to save a page whose route matches another page on the same event, Buzz stops you with:

An Additional Event Page with the same route already exists for this event.

If you hit this, change the Route to something not already used by that event and save again.

Where the page appears

Each published page lives under its event on the public event site, at:

/events/<event-route>/<page-route>

where <event-route> is the event's own route and <page-route> is this page's route. For example, a code-of-conduct page on an event whose route is pyconf-2026 is served at /events/pyconf-2026/code-of-conduct.

When the page is published, the Additional Event Page form shows a web link pointing to this URL, so you can jump straight to the live page from Desk to preview it.

Publishing and unpublishing

• A page is only live when Is Published? is on.
• Unchecking Is Published? takes the page back offline without deleting it or its content.
• Because the route is auto-filled on publish, double-check the Route value after the first publish so the final URL is what you expect.

Related

• Create an Event — set up the parent event and its route.