new-pagelisted

# New page The repo is the current directory. A page is a file: `content/pages/<slug>.yaml` with its `seo` block (the route, permanent once pushed), its `jsonld` block and its sections in order, rendered through the section registry. A page made of existing section types needs no code. ## Read first `content/README.md` "Add a page", `content/_templates/page.yaml`, `content/README.md` § Fields › `pages` (every section type and its fields), one existing file in `content/pages/` as a worked example, `src/lib/seo/README.md` (the head, the structured data, the OG image; the engine's docs, under `node_modules/agentic-cms/` on a site that installs the package), `content/VOICE.md`, `src/config/site.ts`. ## Steps 1. **The route and the sections.** Confirm `seo.path` with the user and list the sections by type, chosen from the registry tables only. A section type that does not exist is code (a schema, a component, a registry entry; the repo's design document says how): stop and say so. 2. **The file.** Copy the template to `content/pages/<slug>.yaml`. `seo`: `title` of 60 characters or fewer and unique across pages, `description` of 70–160, `ogImage`, `updated` today (quoted), `breadcrumb`; `jsonld` by page type; sections with real copy under `content/VOICE.md` (the brand as it spells it; eyebrows as the existing pages carry them). Card counts are part of the design where the build says "must have exactly N". 3. **The images.** The OG image as the engine