Eventyay concepts
=================

An **event** is the central object. It contains the public event experience
and the organiser configuration for ticketing, sessions, schedules, and other
enabled features.

An **organiser** owns events and can grant team members access. A **ticket
product**, **quota**, **order**, and **attendee** describe the registration
workflow. A **proposal** becomes a **session** when it is accepted and can be
placed on a public **schedule**. **Badges** and **check-in lists** support
onsite operations.

Public event pages are attendee-facing. Organiser pages are used to configure
an event. Platform administration pages configure the Eventyay installation as
a whole.