Pilot the headless CMS with one client site #4974

🤖 Generated by the Agentic Engineer (interactive Claude Code session)

Part of #4927 — increment 3. Written for the CMS proposed in #4972 (Payload, one instance per client).

Problem

The epic's goal is a client updating their own site without the maintainer. Until a real owner has done it, we do not know whether the editor, the login and the way changes go live work for a non-technical person.

Proposal

1. Declare one CMS instance for one SvelteKit client site, using the building block from Deploy the chosen headless CMS as an off-by-default, per-client platform capability #4973, with a content model for the pages that client wants to edit.
2. Move that content out of the site's code into the CMS. The site reads published content at request time from its instance, so an edit is live at once.
3. Create the owner's editor account, give a short walkthrough, and let them change a text and an image in Danish and English.
4. Record what the owner found easy and hard.

Hypothesis: after one short walkthrough, the owner can change a text and an image on the live site without the maintainer changing code.
Success signal: the owner makes at least one real edit within two weeks of the walkthrough. Guardrail: no content is lost, and the site stays as available as before.

Acceptance criteria

• The client's site shows its editable content from its own CMS instance.
• The owner has made at least one edit that went live without a code change.
• The instance's backups run, and the restore procedure from Deploy the chosen headless CMS as an off-by-default, per-client platform capability #4973 works for it.
• The owner's feedback is recorded on this issue, and follow-up issues are filed for what it finds.

Size

Medium.

🤖 Generated with Claude Code