Page Builder

Every page in the CMS is a CmsPage document containing an ordered array of typed blocks. Each block has a discriminated type (`hero`, `text`, `image`, `gallery`, `video`, `map`, `embed`, `form`, `columns`, plus the dynamic data blocks from F18.11) and a JSON config that the renderer maps to a React component. The admin page builder presents these as draggable cards in a left-rail palette; editors drop them onto a stacked canvas, reorder by drag, and edit inline.

Page templates jump-start common layouts — homepage, about, contact page, competition landing, news listing — by hydrating a fresh CmsPage with a curated block sequence that the editor can then mutate. URLs are derived from a slug field (validated for SEO friendliness — lowercase, hyphenated, no stop-words enforced) and combined with the page's parent path to form `/<parent>/<slug>`. The publish workflow uses a state machine: draft → review → published, with optional schedule_at timestamps that the publisher job picks up every minute and flips to published when due.

Versioning snapshots the entire block array on every publish, so editors can diff or roll back. Reusable block components — typically headers, footers, sponsor strips and call-to-action banners — are stored as standalone CmsBlock documents and referenced by id from any page; editing the source block updates every page that includes it. The Next.js renderer revalidates each page on a 60-second ISR window, so a publish is visible within a minute without a full rebuild.