[P08] Build an Event Page
Summary
A site editor creates the page for a new event: chooses the EMS event, writes the narrative, and places page parts. The parts fill from EMS, so the editor writes only what EMS does not hold.
Actor & Context
Actor: Site editor
Frequency: Per event; a few to dozens a year per site
Precondition: The editor is signed in to the site; the event exists in EMS
Entry point: New event page in the site’s editor
Main Flow
-
The editor chooses the EMS event from a list; the page starts from the event page template, whose parts fill from EMS at once.
-
The editor writes content anywhere on the page and moves, removes or adds parts, choosing each part’s properties from lists.
-
The editor previews the page with live EMS data and publishes it.
Alternative Flows
-
AF-1: Note on a part: the editor adds a remark to a part (for example under the fees) without replacing the data.
-
AF-2: Part on another page: the editor places a part on a page that is not an event page by naming the event.
Acceptance Criteria
-
Choosing the event fills the template’s parts without typing ids (PS-ED-01)
-
Parts are inserted through the CMS’s editor with properties chosen from lists (PS-ED-02)
-
Preview shows EMS data (PS-ED-03)
-
Parts placed by the template can be moved and removed (PS-EP-02, PS-ED-04)
API Surface
The calls below are named by purpose; their exact form is defined in the public site design.
| Call | Purpose |
|---|---|
GET events for the organisation |
Event picker |
GET part data for preview |
As P02 |
Design Anchors
-
Public Site Requirements — PS-ED-01 to 04, PS-PP-20, PS-PP-21