[P01] Browse Events
Summary
A visitor looks for an event on a multi-event site: what is coming up, what is open for entry, and what has happened. The list is the site’s front door to its event pages.
Actor & Context
Actor: Visitor
Frequency: Every visit to a multi-event site; the most-used public view
Precondition: None; no sign-in
Entry point: The site’s home page, an Events menu item, or any page carrying an event list part
Main Flow
-
The site shows upcoming events, soonest first: name, date, venue, registration status, link.
-
The visitor narrows the list by series, discipline or event type, or switches between list, grid and month calendar.
-
The visitor opens an event, arriving at its event page (P02).
Alternative Flows
-
AF-1: No upcoming events: the list says so in plain words and links to past events.
-
AF-2: Past events: the visitor switches to past events, most recent first, filtered by year, each linking to its page with results (P04).
-
AF-3: Calendar feed: the visitor subscribes to the site’s event feed in their calendar application.
Acceptance Criteria
-
Upcoming events appear in date order with their registration status (PS-EL-01)
-
Filters and views work without a page reload being required for correctness (PS-EL-03)
-
An empty list explains itself and offers past events (PS-EL-04)
-
A subscribable feed lists the site’s events (PS-EL-05)
API Surface
The calls below are named by purpose; their exact form is defined in the public site design.
| Call | Purpose |
|---|---|
GET event list for the site’s organisation, with filters |
Events and their status |
Design Anchors
-
Public Site Requirements — PS-EL-01 to 05, PS-PP-11, PS-PP-12