Public Site Design
Overview
This module holds the design of customers' public websites that is common to every CMS implementation. It answers how the Public Site Requirements are met in terms of EMS services and the contract a CMS implementation must honour, so that the WordPress implementation and a later EmDash implementation behave the same and the payment provider can change without touching the sites.
CMS-specific design (blocks, shortcodes, settings screens, packaging) is documented with each implementation, in its own repository.
Contents
This module is being written alongside the redesign. Each topic below becomes a page as it is settled:
| Topic | Covers |
|---|---|
Page parts |
The catalogue of parts, their properties and output, shared by every implementation |
Event page |
Templates, how parts and the editor’s content are arranged, and how a part’s output is annotated |
Site and EMS contract |
The calls a site makes to EMS and EMS makes to a site, and how both directions are authenticated |
Onboarding |
The enrolment code, what EMS creates, and the end-of-set-up checks |
Configuration |
Sources of settings, their precedence, and values fixed by the hosting environment |
Observability and remote operation |
Telemetry the site reports, and the remote-operation interface used over MCP |
Payment provider |
The site’s role when it runs the store, and what changes when EMS takes payment |