diff --git a/.gitea/workflows/continuous_integration.yaml b/.gitea/workflows/continuous_integration.yaml
index aa81e10..53409bf 100644
--- a/.gitea/workflows/continuous_integration.yaml
+++ b/.gitea/workflows/continuous_integration.yaml
@@ -3,6 +3,7 @@ name: Continuous Integration
# Branchstrategie (zie aidlc-docs/.../operations/deployment/deployment-plan.md):
# - Pull request → controles, geen deploy
# - Merge/push naar master → controles + automatisch naar test
+# - Elke nacht (schedule) → controles + naar test, met de pakketten uit het CMS
# - Handmatig, elke branch → controles + naar test als 'Deploy to Test' aan staat
# - Handmatig, release/* → controles + naar productie als 'Deploy to Production' aan staat
on:
@@ -20,6 +21,12 @@ on:
types: [opened, synchronize, reopened]
push:
branches: [master]
+ # Elke nacht een testbuild, zodat een wijziging van de pakketten in het CMS
+ # op de testsite komt (de build haalt ze op). Alleen test, nooit productie.
+ # 03:15 UTC (04:15 of 05:15 Nederlandse tijd), buiten kantooruren en niet op
+ # een heel uur. Gitea draait schedules alleen vanaf de standaardbranch.
+ schedule:
+ - cron: '15 3 * * *'
# Alleen bij pull requests een verouderde run afbreken; een deploy wordt nooit
# halverwege gestopt.
@@ -84,6 +91,9 @@ jobs:
run: pnpm test
# Sentry toont bij elke fout uit welke commit de build komt
+ # Dit artefact (dist) is ook wat naar productie gaat: bewust zonder
+ # OFFERINGS_URL, dus met de gecommitte pakketlijst. De testbuild met de
+ # pakketten uit het CMS is job build-test.
- name: Build
run: pnpm build
env:
@@ -102,13 +112,68 @@ jobs:
path: web/dist/client/
retention-days: 7
+ # De build voor de testsite: zelfde code als dist, maar met de pakketten uit
+ # het CMS van de testomgeving (OFFERINGS_URL uit de repo-variabele
+ # ASF_OFFERINGS_URL_TEST). Productie krijgt dit artefact nooit: die blijft op
+ # dist met de gecommitte lijst tot er een productie-CMS is.
+ build-test:
+ needs: check
+ if: (github.event_name == 'workflow_dispatch' && github.event.inputs.deploy_test == 'true') || (github.event_name == 'push' && github.ref == 'refs/heads/master') || github.event_name == 'schedule'
+ runs-on: linux
+ steps:
+ - uses: actions/checkout@v4
+
+ - uses: actions/setup-node@v4
+ with:
+ node-version: ${{ env.NODE_VERSION }}
+
+ - uses: pnpm/action-setup@v4
+ with:
+ package_json_file: web/package.json
+
+ - name: Get pnpm store directory
+ id: pnpm-store
+ run: echo "path=$(pnpm store path)" >> "$GITHUB_OUTPUT"
+
+ - name: Restore pnpm store
+ uses: actions/cache@v4
+ with:
+ path: ${{ steps.pnpm-store.outputs.path }}
+ key: pnpm-${{ hashFiles('web/pnpm-lock.yaml') }}
+
+ - name: Install dependencies
+ run: pnpm install --frozen-lockfile
+
+ - name: Build (testomgeving, pakketten uit het CMS)
+ run: pnpm build
+ env:
+ VITE_RELEASE: ${{ github.sha }}
+ OFFERINGS_URL: ${{ vars.ASF_OFFERINGS_URL_TEST }}
+ # De testsite staat op zichzelf: canonical, og:url, og:image,
+ # JSON-LD en sitemap wijzen naar het eigen adres, zodat een gedeelde
+ # link (WhatsApp, Discord) ook zijn eigen plaatje toont. Alleen in
+ # deze testbuild; het productie-artefact (job check) krijgt de
+ # variabele niet en houdt https://andreaslop.nl.
+ VITE_SITE_URL: https://test.andreaslop.nl
+ # Het contactformulier staat alleen in deze testbuild open; standaard
+ # (en in het productie-artefact) is het dicht. Productie aanzetten
+ # vraagt Bryans expliciete go (docs/go-live-checklist.md).
+ VITE_CONTACT_FORM_ENABLED: 'true'
+
+ - name: Upload build artifact (test)
+ uses: actions/upload-artifact@v3
+ with:
+ name: dist-test
+ path: web/dist/client/
+ retention-days: 7
+
# Test wacht niet op Lighthouse: test is om te testen, de rapporten zie je
# achteraf. Lighthouse draait ernaast of erna (zie de volgorde bovenaan).
# Deploys alleen vanaf de Pi: die bereikt zichzelf zeker, en container-
# actions werken niet op Podman.
deploy-test:
- needs: check
- if: (github.event_name == 'workflow_dispatch' && github.event.inputs.deploy_test == 'true') || (github.event_name == 'push' && github.ref == 'refs/heads/master')
+ needs: [check, build-test]
+ if: (github.event_name == 'workflow_dispatch' && github.event.inputs.deploy_test == 'true') || (github.event_name == 'push' && github.ref == 'refs/heads/master') || github.event_name == 'schedule'
runs-on: raspberry-pi
steps:
- uses: actions/checkout@v4
@@ -121,7 +186,7 @@ jobs:
- name: Download build artifact
uses: actions/download-artifact@v3
with:
- name: dist
+ name: dist-test
path: web/dist
# Alleen de clientmap hoort online: geen servermap, geen source maps
@@ -182,6 +247,7 @@ jobs:
# Lighthouse tegen de gebouwde site (mobiel en desktop)
lighthouse:
needs: check
+ if: github.event_name != 'schedule'
runs-on: linux
steps:
- uses: actions/checkout@v4
diff --git a/AGENTS.md b/AGENTS.md
index b5b00be..7b59f4f 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -5,3 +5,4 @@ This file is the entry point for AI coding agents working in this repository. Pr
## Index
- [.ai/layout-conventions.md](.ai/layout-conventions.md) — how to build and update the Mermaid diagrams in [LAYOUT.md](LAYOUT.md).
+- [README.md](README.md) and [docs/](docs/) — set-up and commands, [CMS integration](docs/cms-integration.md), [deploy and CI](docs/deploy-and-ci.md) and the [go-live checklist](docs/go-live-checklist.md), [translations](docs/translations.md) and the [assets and licences](docs/assets-and-licenses.md). New texts of the site go in `web/src/i18n/nl.json`, not in the components. Update them in the same change when you alter the packages or banners, the use of the CMS API, the workflow (inputs, jobs, triggers), the server config or the go-live conditions. Work that is not built through AI-DLC is documented there, not only in a commit message.
diff --git a/README.md b/README.md
index 727fd0d..0ec5480 100644
--- a/README.md
+++ b/README.md
@@ -1,9 +1,36 @@
# Andrea Slop Fotografie
-Photography website made with .Net and React for Andrea Slop Fotografie.
+
+Photography website made with .NET and React for Andrea Slop Fotografie. The site (in [web/](web/)) is a React single-page app (Vite, TanStack Start prerendering, Chakra UI v3) that is prerendered to static HTML at build time. On the test host it is served by the SLP CMS host (.NET), on production the same CMS host behind an IIS pass-through (planned): the host serves the pages, `/admin` and `/api/v1/*`.
## Set-up
### Pre-requisites
+- Node.js 24 and pnpm (run every command in [web/](web/)).
+- Chrome for the end-to-end checks (`pnpm e2e` uses the installed Chrome; CI uses Playwright's Chromium).
+
+### Commands (in `web/`)
+
+| Command | What it does |
+| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `pnpm install` | Installs the dependencies (also generates the Chakra types). |
+| `pnpm dev` | Dev server. Set `API_PROXY_TARGET` (for example the ASF test host) to forward `/api` to a CMS host, so the contact form and the live packages work. |
+| `pnpm build` | Fetches the packages and banners from the CMS (see [docs/cms-integration.md](docs/cms-integration.md)), type-checks, builds and prerenders into `dist/`. |
+| `pnpm preview` | Serves `dist/` like the host does (headers, redirects). `--contact-stub` answers the contact and offerings API with a stub, as CI does. |
+| `pnpm test` | Unit, component, property and axe tests with coverage (100% required for `src/lib/**`). |
+| `pnpm e2e` | Real-browser checks against a built `dist/`. |
+| `pnpm check` | Everything CI runs: lint, format, tests, build, e2e, audit and Lighthouse. |
+| `pnpm server-config` | Regenerates `web/deploy/iis/web.config` and `web/deploy/nginx/*.conf`. Do not edit those by hand. |
+
## Lay-out
-Lay-out of the website and its pages can be found in a sepoarate document [LAYOUT.md](LAYOUT.md)
\ No newline at end of file
+
+Lay-out of the website and its pages can be found in a separate document [LAYOUT.md](LAYOUT.md).
+
+## Documentation
+
+- [docs/cms-integration.md](docs/cms-integration.md): packages and banners from the CMS, the API, the build step, live refresh and the reverse proxy.
+- [docs/deploy-and-ci.md](docs/deploy-and-ci.md): the pipeline, the workflow inputs, deploying to test, the nightly build and the contact form switch.
+- [docs/assets-and-licenses.md](docs/assets-and-licenses.md): where the images, icons and fonts come from and what is still to confirm about their licence.
+- [docs/translations.md](docs/translations.md): where the texts of the site live (language files), how keys work and how a language is added.
+- [docs/go-live-checklist.md](docs/go-live-checklist.md): what must be true before the CMS features and the contact form go to production.
+- [aidlc-docs/](aidlc-docs/): the AI-DLC records per feature (requirements, design, decisions, audit). [aidlc-docs/active-features.md](aidlc-docs/active-features.md) lists them.
diff --git a/aidlc-docs/active-features.md b/aidlc-docs/active-features.md
index 291c7d7..fd126a0 100644
--- a/aidlc-docs/active-features.md
+++ b/aidlc-docs/active-features.md
@@ -1,15 +1,20 @@
# Active Features
-| Type | Name | Status | Branch | Affected Components | Session Start |
-|------|------|--------|--------|---------------------|---------------|
-| Bug | [hero-carousel-announce-and-pause](bugs/hero-carousel-announce-and-pause/bug-fix.md) | ✅ Complete | fix/hero-carousel-announce-and-pause | web/src/components/Hero (Hero, HeroArrows, useHeroSlider) | 2026-10-19 |
-| Feature | frontend-shell | ✅ Complete | feature/frontend-shell | web/src (AppShell, NavigationBar, Footer, Hero socials, new BackToTop/SkipLink/404/error pages, routes, theme.ts, main.tsx), web/vite.config.js, web/package.json | 2026-10-14 |
-| Feature | homepage-sections | ✅ Complete | feature/homepage-sections | web/src/routes/index.tsx, new homepage section components, web/src/content (types + static content), possibly web/config/securityHeaders.ts (contact form) | 2026-10-19 |
-| Feature | over-mij-page | ✅ Complete | feature/over-mij-page | web/src/routes/over-mij.tsx, web/src/content, possibly shared components (PageIntro, FramedImage, SectionHeading) and web/src/seo.ts | 2026-10-22 |
-| Feature | soorten-fotoshoots-page | ✅ Complete | feature/soorten-fotoshoots-page | web/src/routes/soorten-fotoshoots.tsx, new web/src/content/shootTypes.ts, new web/src/assets/shoots/, new shared CallToAction, MediaText (reverse prop), Pricing (id="prijzen" only), siteContent (service area), own entries in sitePages.ts / lighthouserc.cjs, JSON-LD via the shared webPage() helper in seo.ts | 2026-10-24 |
-| Feature | contact-page | ✅ Complete | feature/contact-page | web/src/routes/contact.tsx, web/src/content, possibly ContactForm/ContactSection, PageIntro, MediaText/FramedImage, web/src/seo.ts, sitePages/sitemap | 2026-10-24 |
-| Feature | portfolio-page | ✅ Complete | feature/portfolio-page (based on master after over-mij merge; worktree ../AndreaSlopFotografie-portfolio) | web/src/routes/portfolio.tsx, web/src/content, new PortfolioGrid + Lightbox, InstagramGrid (moved to shared), own entries in sitePages.ts / lighthouserc.cjs, ImageGallery JSON-LD via the shared webPage() helper | 2026-10-24 |
-| Feature | shoot-type-pages | ✅ Complete (content follow-up: [content-pending.md](features/shoot-type-pages/content-pending.md)) | feature/shoot-type-pages (worktree ../AndreaSlopFotografie-shoot-type-pages) | new route(s) per shoot type under web/src/routes, web/src/content (shootTypes.ts extension, timeline content), shared Timeline component, links from soorten-fotoshoots, seo.ts (webPage helper), sitePages.ts / sitemap, lighthouserc.cjs | 2026-10-29 |
-| Feature | prerendering | ✅ Complete (merged, PR #14) | feature/prerendering (worktree ../AndreaSlopFotografie-prerendering) | web/vite.config.ts, web/src/main.tsx, web/index.html, web/config/serverConfig.ts + web/deploy, CI workflow, web/lighthouserc.cjs, possibly Reveal/useReveal and hooks using media queries | 2026-10-31 |
-| Feature | testimonials-redesign | ✅ Complete (merged, PR #16) | feature/testimonials-redesign (worktree ../AndreaSlopFotografie-testimonials-redesign) | web/src/components/home/Testimonials (Testimonials, TestimonialSlide, TestimonialCarousel), web/src/recipes/carouselControl.ts, web/src/content (Testimonial type, testimonials.ts), possibly SectionHeading, LAYOUT.md, unit/e2e tests that reference the dots | 2026-11-05 |
-| Feature | cms-api-foundation | ✅ Complete (merged PR #17, 2026-11-10; follow-ups: ASF production, contact feature) | feature/cms-api-foundation (worktree ../AndreaSlopFotografie-cms-api-foundation) | Cross-repo: feature briefs for the SlpModularCms repo (new Api.AndreaSlopFotografie client, per-site theming, per-site module set); in this repo only docs, later web integration (CMS serves the site) | 2026-11-05 |
+| Type | Name | Status | Branch | Affected Components | Session Start |
+| ------- | ------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- |
+| Bug | [hero-carousel-announce-and-pause](bugs/hero-carousel-announce-and-pause/bug-fix.md) | ✅ Complete | fix/hero-carousel-announce-and-pause | web/src/components/Hero (Hero, HeroArrows, useHeroSlider) | 2026-10-19 |
+| Feature | frontend-shell | ✅ Complete | feature/frontend-shell | web/src (AppShell, NavigationBar, Footer, Hero socials, new BackToTop/SkipLink/404/error pages, routes, theme.ts, main.tsx), web/vite.config.js, web/package.json | 2026-10-14 |
+| Feature | homepage-sections | ✅ Complete | feature/homepage-sections | web/src/routes/index.tsx, new homepage section components, web/src/content (types + static content), possibly web/config/securityHeaders.ts (contact form) | 2026-10-19 |
+| Feature | over-mij-page | ✅ Complete | feature/over-mij-page | web/src/routes/over-mij.tsx, web/src/content, possibly shared components (PageIntro, FramedImage, SectionHeading) and web/src/seo.ts | 2026-10-22 |
+| Feature | soorten-fotoshoots-page | ✅ Complete | feature/soorten-fotoshoots-page | web/src/routes/soorten-fotoshoots.tsx, new web/src/content/shootTypes.ts, new web/src/assets/shoots/, new shared CallToAction, MediaText (reverse prop), Pricing (id="prijzen" only), siteContent (service area), own entries in sitePages.ts / lighthouserc.cjs, JSON-LD via the shared webPage() helper in seo.ts | 2026-10-24 |
+| Feature | contact-page | ✅ Complete | feature/contact-page | web/src/routes/contact.tsx, web/src/content, possibly ContactForm/ContactSection, PageIntro, MediaText/FramedImage, web/src/seo.ts, sitePages/sitemap | 2026-10-24 |
+| Feature | portfolio-page | ✅ Complete | feature/portfolio-page (based on master after over-mij merge; worktree ../AndreaSlopFotografie-portfolio) | web/src/routes/portfolio.tsx, web/src/content, new PortfolioGrid + Lightbox, InstagramGrid (moved to shared), own entries in sitePages.ts / lighthouserc.cjs, ImageGallery JSON-LD via the shared webPage() helper | 2026-10-24 |
+| Feature | shoot-type-pages | ✅ Complete (content follow-up: [content-pending.md](features/shoot-type-pages/content-pending.md)) | feature/shoot-type-pages (worktree ../AndreaSlopFotografie-shoot-type-pages) | new route(s) per shoot type under web/src/routes, web/src/content (shootTypes.ts extension, timeline content), shared Timeline component, links from soorten-fotoshoots, seo.ts (webPage helper), sitePages.ts / sitemap, lighthouserc.cjs | 2026-10-29 |
+| Feature | prerendering | ✅ Complete (merged, PR #14) | feature/prerendering (worktree ../AndreaSlopFotografie-prerendering) | web/vite.config.ts, web/src/main.tsx, web/index.html, web/config/serverConfig.ts + web/deploy, CI workflow, web/lighthouserc.cjs, possibly Reveal/useReveal and hooks using media queries | 2026-10-31 |
+| Feature | testimonials-redesign | ✅ Complete (merged, PR #16) | feature/testimonials-redesign (worktree ../AndreaSlopFotografie-testimonials-redesign) | web/src/components/home/Testimonials (Testimonials, TestimonialSlide, TestimonialCarousel), web/src/recipes/carouselControl.ts, web/src/content (Testimonial type, testimonials.ts), possibly SectionHeading, LAYOUT.md, unit/e2e tests that reference the dots | 2026-11-05 |
+| Feature | cms-api-foundation | ✅ Complete (merged PR #17, 2026-11-10; follow-ups: ASF production, contact feature) | feature/cms-api-foundation (worktree ../AndreaSlopFotografie-cms-api-foundation) | Cross-repo: feature briefs for the SlpModularCms repo (new Api.AndreaSlopFotografie client, per-site theming, per-site module set); in this repo only docs, later web integration (CMS serves the site) | 2026-11-05 |
+| Feature | contact-form-cms | ✅ Complete (closed 2026-11-16; Operations in the joint production checklist; merges with asf-packages-cms) | feature/contact-form-cms (worktree ../AndreaSlopFotografie-contact-form) | web/src/components/ContactForm, ContactFormGate, web/src/contact (submitContactForm), new web/src/cms-client (copied headless package), web/config/securityHeaders.ts, content/siteContent contactForm switch | 2026-11-10 |
+| Feature | asf-packages-cms | ✅ Complete (closed 2026-11-16; PR to master after the CMS PR; no production release) | feature/asf-packages-cms (worktree ../AndreaSlopFotografie-packages, based on feature/contact-form-cms) | web/config (offerings, fetchOfferings), web/src/content (packages, snapshot, types), Pricing + PriceBanner + PriceTopBar (two banners, centred card rows), PackagesProvider (live refresh), CI build-test job and nightly test build, docs/ (CMS integration, deploy and CI, go-live checklist) | 2026-11-12 |
+| Feature | asf-cms-host-injection | ✅ Complete on the ASF side (2026-11-16, delivered with asf-packages-cms; host side by SMC) | feature/asf-packages-cms | web (PackagesProvider, build markers, neutral HTML), preview server stand-in injector, e2e/contract tests; host side in the SlpModularCms repo | 2026-11-15 |
+| Feature | asf-translation-files | ✅ Complete on the ASF side (2026-11-16, delivered with asf-packages-cms) | feature/asf-packages-cms | web/src/i18n (nl.json, helpers), content modules, components, ESLint rules, baseline tool, docs/translations.md | 2026-11-15 |
+| Feature | hero-module | 🔵 Inception (requirements questions to Bryan) | (none yet) | Hero as a manageable CMS module (SMC builds the module, ASF consumes it); LCP in the first HTML via host injection or prerender; static hero texts move into it | 2026-11-16 |
diff --git a/aidlc-docs/features/asf-cms-host-injection/aidlc-state.md b/aidlc-docs/features/asf-cms-host-injection/aidlc-state.md
new file mode 100644
index 0000000..05ec080
--- /dev/null
+++ b/aidlc-docs/features/asf-cms-host-injection/aidlc-state.md
@@ -0,0 +1,22 @@
+# AI-DLC State Tracking
+
+## Project Information
+
+- **Feature Name**: CMS host injects CMS data into the prerendered ASF pages
+- **Feature Slug**: asf-cms-host-injection
+- **Project Type**: Brownfield (cross-repo: this repo delivers markers, contract and golden files; SlpModularCms owns the injector)
+- **Start Date**: 2026-11-15
+- **Current Stage**: COMPLETE on the ASF side (closed 2026-11-16); delivered on branch feature/asf-packages-cms together with [asf-packages-cms](../asf-packages-cms/aidlc-state.md). Host side by SMC (CMS PR).
+- **Plan**: [plan.md](plan.md) (approach agreed by Bryan, 2026-11-15)
+
+## Language Configuration
+
+- **Documentation Language**: English
+- **Conversation Language**: User Language (Dutch)
+
+## Stage Progress
+
+- [x] INCEPTION - Requirements and plan (plan.md; decisions (a) brief look change accepted, (b) host writes the list HTML)
+- [x] CONSTRUCTION - Code Generation: markers and regions, data block, hydration from the block, JSON-LD price, inline price, own address replacement, stand-in host in the preview server, golden files in `web/contract/host-injection/`, e2e tests, deployment-check normalisation
+- [x] CONSTRUCTION - Build and Test: see the asf-packages-cms summary; end-to-end on ASF-test: SMC still to confirm (not part of closing the ASF side)
+- [x] OPERATIONS - part of the joint production checklist (production needs IIS pass-through to the CMS host, separate feature)
diff --git a/aidlc-docs/features/asf-cms-host-injection/plan.md b/aidlc-docs/features/asf-cms-host-injection/plan.md
new file mode 100644
index 0000000..9ef0c29
--- /dev/null
+++ b/aidlc-docs/features/asf-cms-host-injection/plan.md
@@ -0,0 +1,91 @@
+# Plan (approach agreed, waiting for the start): the CMS host injects CMS data into the prerendered ASF pages
+
+Status (2026-11-16): ASF side built and closed (see [aidlc-state.md](aidlc-state.md)); host side by SMC. Original status: plan, approach agreed 2026-11-15.
+
+Decisions of Bryan (via SLS-Main, 2026-11-15):
+
+- (a) A short change of look of the cards on first paint (neutral HTML first, then the styled cards after hydration) is ACCEPTED.
+- (b) The host MAY write the list HTML (C# template; this repo delivers the spec and the golden files): YES.
+
+It starts as a separate feature after the current merges (contact-form-cms, then asf-packages-cms), not through them. To be built together with SLP Modular CMS - SMC - Main, who owns the host side.
+
+## Why
+
+Hosting decision (2026-11-15): the CMS host is the one entry of the website and serves the prerendered pages, `/admin` and `/api/v1/*`; IIS passes everything to it. A CMS change (packages, banners, later gallery and hero) must then be visible to search engines at once, with no rebuild. The host injects the current data into the prerendered HTML through markers (as on SLP, 60 s cache).
+
+## What is CMS data on the pages today
+
+Packages: the price cards (home), the shoot list and shoot blocks, the "welke shoot" choices of the contact form, the `?pakket=` check, the offer price in the JSON-LD of the shoot pages. Banners: the slim top bar and the band under the cards. See [docs/cms-integration.md](../../../docs/cms-integration.md).
+
+## Proposal
+
+### 1. Three kinds of markers (built into the page by the ASF build, filled by the host)
+
+- **Data block**, one per page: `` holding the raw answers of `GET /api/v1/offerings` and both banners. The host replaces its content with the current answers (JSON-escaped: `<`, `>`, `&`, U+2028/2029). It is a non-executable block, so the CSP stays as it is and the build step that moves inline scripts treats it as data (as it does for `ld+json`).
+- **Region**, for lists that differ in length (the cards, the banners): a wrapper `
` whose content is the neutral HTML. The host replaces everything between `` and `` (written into the wrapper by the build; React cannot emit comments, so the build writes them through `dangerouslySetInnerHTML`).
+- **Inline value**, for a single price or name inside a sentence: `€ 185`. The host replaces the text.
+- **JSON-LD price** of a shoot page: the `ld+json` block gets `data-cms-offer="newborn"`; the host sets `offers.price` from the live package (or removes `offers` when the package is gone or has no readable price).
+- The same marker format as SLP, if SLP already has one (to be confirmed by SMC).
+
+### 2. Neutral HTML in the markers
+
+The build puts crawlable, simple semantic HTML between the markers (package name, price, features, a plain link to `/?pakket=#contact`; the banner as an `aside`), written from the baked data by one pure function (`web/src/lib/neutralHtml.ts`, all text escaped). The host produces the same markup from live data (template in C#; the ASF repo delivers the spec and golden files, SMC implements, a contract test in each repo checks both sides against the same fixtures). Light static CSS in the page makes it look acceptable (the section is below the fold).
+Why not exact copies of the styled cards: Chakra/Emotion class names and styles are generated at build time, a C# template cannot reproduce them.
+
+### 3. Hydration: read the JSON, do not fetch
+
+- `PackagesProvider` takes its initial state from the data block (reusing `mapOfferings`, `mapBanner`, `mapTopBanner`), not from the baked import and not from a fetch after hydration. Without a block (preview, tests, a host that does not inject) it falls back to the baked data plus the live fetch it has today, so nothing is lost.
+- Regions are not hydrated by React (`dangerouslySetInnerHTML` with `suppressHydrationWarning`, so React keeps the server DOM). After hydration (`useHydrated`) the styled React components render into the region and replace the neutral HTML. So the first paint is the neutral HTML, and a brief change of look follows; the cards are below the fold, and the region keeps a minimum height to avoid a layout shift.
+- Inline values hydrate directly from the same data (`suppressHydrationWarning` for the formatting difference).
+- The contact form choices and `?pakket=` read the same state, so they agree with what the host injected.
+
+### 4. Hydration and contract tests (per marker, before anything ships)
+
+- Build test: every expected marker exists exactly once per page, in the final `dist/` (after the script-moving step), and the neutral HTML equals what the pure function gives.
+- E2E in real Chrome with a stand-in injector in the preview server (same algorithm as the host, fixtures with more, fewer and different packages, with and without banners, an unreadable price, a hostile text such as ``: the host replaces the pair by the live block `{"siteUrl":"…","offerings":[…],"banners":{"top":…|null,"bottom":…|null}}` (offerings and banners exactly as the public GETs; `<`, `>`, `&`, U+2028 and U+2029 written as `\uXXXX` escapes). Without a block after the marker the live block replaces the marker. The block the build bakes carries `"source":"build"` (the host replaces the whole block, so the live one has no `source`); the site treats a block with that source as "no host data" and asks the API itself, as before the injection existed. `siteUrl` is the effective public base URL (see 5), which the client needs because the JS bundle cannot be rewritten (immutable assets).
+3. **JSON-LD price** `` directly before ``: the host parses the block and sets `offers.price` (whole euros, our parsing: "€ 175", "€ 1.250", "175,-") on the node that has `offers`; when the package is gone, switched off, scheduled or has no readable price, `offers` is removed from that node. A database or provider failure is different: the baked block stays (fail open). A block that is not valid JSON stays. The marker comment is removed; property order is kept. Only the shoot pages of newborn, zwangerschap and gezin get this marker; loveshoot, portret ("Prijs op aanvraag"), the overview and the home page get none.
+4. **Inline value** `€ 185`: the host replaces the text by "€" + U+00A0 + whole euros; an unknown slug or an unreadable price leaves the span alone. Only simple, non-nested spans with exactly this attribute. Used in the price block of a shoot page.
+5. **Own address** (`Website:AuthoredBaseUrl`): the same injector replaces the written production address in every HTML page, `sitemap.xml` and `robots.txt` by `Website:PublicBaseUrl` when that is set on the host (test: `https://test.andreaslop.nl`; production: equal or empty, nothing to replace). One artifact then serves test and production, and `VITE_SITE_URL` no longer differs per environment. The ASF build is written with `https://andreaslop.nl` (the non-www canonical origin; IIS redirects www to it). The site has no web manifest. The client takes its address from `siteUrl` in the data block (fallback: the production address), not from the bundle, so canonical and `og:` tags stay right after hydration and on navigation.
+6. **Caching:** injected pages get `Cache-Control: no-cache`, a strong ETag (hash of the final body), 304 on `If-None-Match` and no Last-Modified, behind the host's 60 s cache with direct invalidation on every CMS change. `/assets/` stays immutable. Pages without markers keep the native static-file headers.
+
+### Neutral HTML spec (draft; golden files follow once Bryan has approved the approach)
+
+- Order: `displayOrder`, then the order given. Skip a package with a slug that is not `[a-z0-9-]+`, a duplicate slug, no title, a price that is not readable as whole euros above zero, or no features (same rules as `mapOfferings`). The baked fallback stays when the host has no live data at all.
+- Per package: `
` per region; the price with U+00A0 after the euro sign; the inner list items are the features in order; all text HTML-encoded. A featured package gets `data-featured="true"` on its `
`. Description, price note and button label are not rendered.
+- Banner regions: ``; `strong`, `span` and `a` only when the field is present; the link only when label and URL are both present and the URL is `https://` or a path with one leading `/`; nothing at all when there is no banner (204).
+- The ASF repo delivers the fixtures (input JSON and expected HTML) and a README with the commit; SMC tests against the same files.
+
+## Order of work (after approval)
+
+1. Marker spec and golden fixtures (ASF repo), agreed with SMC.
+2. Pure neutral-HTML function, build writes the markers, build tests.
+3. `PackagesProvider` reads the data block, regions, inline values, JSON-LD price; stand-in injector in the preview server; e2e and fail-safe tests.
+4. SMC implements the injector with the same fixtures; test on ASF test.
+5. Hosting switch for production (separate), then remove the nightly content build.
+
+## Open questions
+
+- For SMC: the marker format SLP uses today; how the injector reads and edits JSON and `ld+json`; behaviour when data or a marker is missing (must fail open: serve the baked page); caching and ETag; whether `AuthoredBaseUrl` can also run on the prerendered-pages host.
+- For Bryan: (answered, see the decisions at the top) accept a brief look change of the cards on first paint, and let the host write the list HTML? Both yes. The alternative that was not chosen: one set of cards styled by plain CSS and owned by the host, with no React in those regions.
diff --git a/aidlc-docs/features/asf-packages-cms/aidlc-state.md b/aidlc-docs/features/asf-packages-cms/aidlc-state.md
new file mode 100644
index 0000000..875d201
--- /dev/null
+++ b/aidlc-docs/features/asf-packages-cms/aidlc-state.md
@@ -0,0 +1,42 @@
+# AI-DLC State Tracking
+
+## Project Information
+
+- **Feature Name**: ASF packages and banners from the CMS (build step, live refresh, CMS-host injection, translation files, fonts)
+- **Feature Slug**: asf-packages-cms
+- **Project Type**: Brownfield
+- **Start Date**: 2026-11-12
+- **Current Stage**: COMPLETE (closed 2026-11-16, Bryan's go via SLP Software - SLS - Main); PR feature/asf-packages-cms to master, waiting for the CMS PR to merge first. No production release.
+- **Branch**: feature/asf-packages-cms (carries the contact-form-cms commits; the TEST ONLY commit d449e76 is undone by the `VITE_CONTACT_FORM_ENABLED` switch)
+- **Worktree**: K:\Development\SlpSoftware\Projects\AndreaSlopFotografie-packages
+
+## Language Configuration
+
+- **Documentation Language**: English
+- **Conversation Language**: User Language (Dutch)
+- **Source**: aidlc-docs/language-preference.md
+
+## Extension Configuration
+
+- Security Baseline: Yes (inherited from contact-form-cms)
+- Property-Based Testing: Partial (inherited)
+
+## Operations Configuration
+
+- **Include Operations Phase**: Yes, as part of the joint production checklist ([docs/go-live-checklist.md](../../../docs/go-live-checklist.md)); no separate steps. The rebuild-trigger question lapses: the CMS host injects current data into the pages, so a CMS change is visible at once (NFR-10).
+
+## Scope as delivered
+
+- Packages and both banners (top bar, band under the cards) from the CMS offerings API, snapshot fallback, centred card rows, featured package style.
+- CMS-host injection of the data into the prerendered pages (own feature record: [asf-cms-host-injection](../asf-cms-host-injection/aidlc-state.md)).
+- Translation files: all static Dutch text in `web/src/i18n/nl.json` ([asf-translation-files](../asf-translation-files/aidlc-state.md)).
+- Fonts (Cormorant Garamond, Mulish), green outline buttons, theme twigs removed with the assets and licence document, own test address (`VITE_SITE_URL`), contact form switch (`VITE_CONTACT_FORM_ENABLED`), documentation set (README, docs/*).
+
+## Stage Progress
+
+- [x] INCEPTION - Workspace Detection, Requirements (approved by SLP Software - SLS - Main for Bryan, 2026-11-12)
+- [x] INCEPTION - Workflow Planning (single unit)
+- [x] CONSTRUCTION - Functional Design (requirements.md)
+- [x] CONSTRUCTION - Code Generation
+- [x] CONSTRUCTION - Build and Test: closed 2026-11-16, see [build-and-test-summary.md](construction/build-and-test/build-and-test-summary.md); the former blocker (CMS data on ASF-test) no longer applies: the data reaches the pages through the CMS host
+- [x] OPERATIONS - included in the joint production checklist (no separate steps)
diff --git a/aidlc-docs/features/asf-packages-cms/construction/build-and-test/build-and-test-summary.md b/aidlc-docs/features/asf-packages-cms/construction/build-and-test/build-and-test-summary.md
new file mode 100644
index 0000000..83a9737
--- /dev/null
+++ b/aidlc-docs/features/asf-packages-cms/construction/build-and-test/build-and-test-summary.md
@@ -0,0 +1,22 @@
+# Build and test summary: asf-packages-cms
+
+Closed 2026-11-16 on branch feature/asf-packages-cms. Unit: web only (host side lives in the SlpModularCms repo).
+
+| Check | Result |
+| --------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
+| `tsc`, `pnpm lint`, `pnpm format:check` | clean |
+| `pnpm test` (Vitest, 100% thresholds on `src/lib/**`, `src/i18n/**`, `seo.ts`, `sitemap.ts`) | 145 files, 1643 tests; one run had a single timing-dependent failure that did not repeat on the next run (to watch, not a known defect) |
+| `pnpm baseline:check` (page text byte-identical after the move to nl.json) | equal to the baseline, 12 pages |
+| E2E (real Chrome, built site): hydration, contact form, host injection with the stand-in host | passing in CI |
+| CI run 107 on the test deploy (check, build-test, deploy-test, lighthouse) | all green, deploy-production skipped |
+| Deployment check on ASF-test (pages normalised for host injection, admin files, POST status) | passing |
+
+## Findings and decisions
+
+- Host injection: contract and golden files in `web/contract/host-injection/`; the host side is built by SMC; end-to-end confirmation on ASF-test is still to be reported by SMC.
+- The test build sets `VITE_SITE_URL` and `VITE_CONTACT_FORM_ENABLED=true`; the production artifact sets neither (form closed, own address of production).
+- Production keeps the committed snapshot until the CMS host is the one entry of the site (separate hosting feature).
+
+## Open (not part of this feature)
+
+- IIS pass-through and production CMS for ASF; Website__PublicBaseUrl on ASF-test; removal of the nightly content build and `OFFERINGS_URL` once host injection is confirmed end to end.
diff --git a/aidlc-docs/features/asf-packages-cms/requirements.md b/aidlc-docs/features/asf-packages-cms/requirements.md
new file mode 100644
index 0000000..c2a2d97
--- /dev/null
+++ b/aidlc-docs/features/asf-packages-cms/requirements.md
@@ -0,0 +1,30 @@
+# Requirements and design: packages and banner from the CMS
+
+Decided by Bryan via SLP Software - SLS - Main, 2026-11-12. Source of truth: the CMS API `GET /api/v1/offerings` (fields: id, slug, title, description, price as free text, priceNote, features[], ctaLabel, featured, displayOrder, categoryId, category, layout `card|banner`; at most one banner per site).
+
+## Requirements
+
+- FR-PK-01 The build asks the CMS for the offerings and bakes them into the pages (prices in the HTML and in the structured data). The browser never calls the offerings API.
+- FR-PK-02 Fallback: with no address, an unreachable CMS or an answer without a valid package the committed snapshot (`src/content/offerings.snapshot.json`, the three packages) is used. The build never fails because of the CMS and never shows an empty or wrong price. The log names the source.
+- FR-PK-03 One source: the price cards, the "welke shoot" choices of the contact form and the `?pakket=` check use the same list (`content/packages.ts`).
+- FR-PK-04 Mapping: `slug` is the package id (kept `zwangerschap`, `newborn`, `gezin`: they appear in `?pakket=` and the form), `title` the name, the price text is read as whole euros ("€ 175", "€ 1.250", "175,-"); a card with an unreadable price, no features or a bad slug is skipped; order by `displayOrder`.
+- FR-PK-05 Banner: the first usable offering with `layout=banner` becomes an optional dark band under the cards (own block, price as free text). It is not a package: not in the form choices, not in the package count, no booking link with a package.
+- FR-PK-07 Last row of cards (desktop): rows of three, an incomplete last row is centred, for any number of cards, with no styling per number. Phone and tablet stay one column. Done with a wrapping flex and card width `calc((100% - 2 * gap) / 3)`.
+- FR-PK-08 Slim top bar (2026-11-14, Bryan via SLS-Main): a second banner ABOVE the cards, next to the one under them; both may show at once. One line (title and text on one line, optional small text link), a slim bar in the ASF style that matches the white bottom banner. Contract: `GET /api/v1/offerings/banner?position=top|bottom` (no parameter is bottom), 204 is none, fields title/text/linkLabel/linkUrl, the title may be empty for top (title or text required). Built in like the bottom banner: baked in the HTML, replaced live after hydration, 204 hides it, errors keep what was baked, empty fields hidden.
+- FR-PK-06 The rebuild trigger (CMS change leads to a new build) is separate from the build; decision for Bryan (webhook to workflow_dispatch or a nightly build). Until then a change shows after the next build.
+- NFR-PK-01 Tests use the snapshot only (no dependence on a build or network).
+
+## Design
+
+- `web/config/offerings.ts` pure mapping and validation (unit and property tests).
+- `web/config/fetchOfferings.ts` build step (`pnpm build` runs it first): `OFFERINGS_URL` (the site's own address serving the API), 10 s timeout, 2 attempts, writes the gitignored `src/content/offerings.generated.json`.
+- `web/src/content/packages.ts` picks generated data (build) or the snapshot (tests, missing file).
+- CI: the Build step gets `OFFERINGS_URL` from the repo variable `ASF_OFFERINGS_URL`. The artifact built there is also what goes to production, so the variable must point to the CMS holding the real data.
+- `PriceBanner` component inside `Pricing`.
+
+## Open
+
+- Offerings module on the ASF-test host and the three packages in the ASF-test CMS (asked of the CMS session; 2026-11-12 the endpoint answered 404 on test.andreaslop.nl).
+- Repo variable `ASF_OFFERINGS_URL` (who sets it: Bryan or SLS).
+- Rebuild trigger.
+- ASF production CMS address does not exist yet.
diff --git a/aidlc-docs/features/asf-translation-files/aidlc-state.md b/aidlc-docs/features/asf-translation-files/aidlc-state.md
new file mode 100644
index 0000000..6f6ab3b
--- /dev/null
+++ b/aidlc-docs/features/asf-translation-files/aidlc-state.md
@@ -0,0 +1,22 @@
+# AI-DLC State Tracking
+
+## Project Information
+
+- **Feature Name**: Translation files (all static Dutch text in one language file)
+- **Feature Slug**: asf-translation-files
+- **Project Type**: Brownfield (part of the asf-packages-cms delivery)
+- **Start Date**: 2026-11-15
+- **Current Stage**: COMPLETE (closed 2026-11-16); delivered on branch feature/asf-packages-cms
+- **Documentation**: [docs/translations.md](../../../docs/translations.md)
+
+## Language Configuration
+
+- **Documentation Language**: English
+- **Conversation Language**: User Language (Dutch)
+
+## Stage Progress
+
+- [x] Approach agreed (no library, typed `t`/`tList`/`tPlural`, one `nl.json`; second language later)
+- [x] Code Generation, steps 0-8: helper and checks, common, site, home, about and contact, shoots, portfolio, instagram, testimonials, SEO titles, form messages of the cms-client package (block cmsClient)
+- [x] Build and Test: baseline tool shows the page text byte-identical; ESLint rules block new hard-coded text; i18n tests and 100% coverage
+- Out of scope, separate: hero (becomes a CMS module, see the hero-module feature) and the privacy statement; second language (`en.json`, routes per language)
diff --git a/aidlc-docs/features/contact-form-cms/aidlc-state.md b/aidlc-docs/features/contact-form-cms/aidlc-state.md
new file mode 100644
index 0000000..d8ee491
--- /dev/null
+++ b/aidlc-docs/features/contact-form-cms/aidlc-state.md
@@ -0,0 +1,55 @@
+# AI-DLC State Tracking
+
+## Project Information
+- **Feature Name**: Contact form on the CMS API (ASF contact form talks to the SlpModularCms contact module, using the headless cms-client package)
+- **Feature Slug**: contact-form-cms
+- **Project Type**: Brownfield
+- **Start Date**: 2026-11-10T21:42:54Z
+- **Current Stage**: COMPLETE (closed 2026-11-16, Bryan's go via SLP Software - SLS - Main); Operations = included in the joint production checklist (docs/go-live-checklist.md), no separate steps; the form stays closed in production until Bryan's explicit go. Merges with feature/asf-packages-cms (PR), after the CMS PR.
+- **Branch**: feature/contact-form-cms (from master 7d594ff)
+- **Worktree**: K:\Development\SlpSoftware\Projects\AndreaSlopFotografie-contact-form
+
+## Workspace State
+- **Existing Code**: Yes (web/src has ContactForm, ContactFormGate, submitContactForm stub, contactFormReducer)
+- **Reverse Engineering Needed**: No (team agreement: no full RE refresh per feature)
+- **Workspace Root**: K:\Development\SlpSoftware\Projects\AndreaSlopFotografie-contact-form
+
+## Code Location Rules
+- **Application Code**: Workspace root, web code in web/ (NEVER in aidlc-docs/)
+- **Feature Documentation**: aidlc-docs/features/contact-form-cms/ only
+- **Shared Artifacts**: aidlc-docs/_shared/
+- **Server side**: lives in the SlpModularCms repo (branch feature/contact-forms-module, session "SLS Software - CMS"); NOT built from this session, only asked for
+
+## Language Configuration
+- **Documentation Language**: English
+- **Conversation Language**: User Language (Dutch)
+- **Source**: inherited from aidlc-docs/language-preference.md (answer A)
+
+## Cross-session coordination
+- Source package (read only): SlpSoftware repo, src/cms-client/ (branch feature/redesign-modern-timetravel), coordinated by session "SLP Software - SLS - Main"
+- Server contract: contact-api-contract.md (v0.3.x) in the SlpSoftware repo
+- Milestones (plan ready, built) are reported to "SLP Software - SLS - Main"
+- Nothing is pushed, merged or deployed without Bryan; the form stays off in production until Bryan's explicit go
+
+## Extension Configuration
+- Security Baseline: Yes
+- Property-Based Testing: Partial (PBT-02, 03, 07, 08, 09)
+
+## Operations Configuration
+- **Include Operations Phase**: Yes
+- **Decided At**: Requirements Analysis
+
+## Stage Progress
+- [x] INCEPTION - Workspace Detection (2026-11-10)
+- [x] INCEPTION - Requirements Analysis (approved by SLP Software - SLS - Main on behalf of Bryan, 2026-11-10)
+- [x] INCEPTION - User Stories: SKIP
+- [x] INCEPTION - Workflow Planning (approved by SLP Software - SLS - Main on behalf of Bryan)
+- [x] INCEPTION - Application Design: SKIP
+- [x] INCEPTION - Units Generation: SKIP (one unit: contact-form)
+- [x] CONSTRUCTION - Functional Design: EXECUTE (approved by SLS-Main for Bryan)
+- [x] CONSTRUCTION - NFR Requirements: SKIP
+- [x] CONSTRUCTION - NFR Design: SKIP
+- [x] CONSTRUCTION - Infrastructure Design: EXECUTE (approved; CSP set by Bryan: exact frame hosts)
+- [x] CONSTRUCTION - Code Generation: EXECUTE (plan approved; steps 1-13 done)
+- [x] CONSTRUCTION - Build and Test: EXECUTE (summary written; awaiting approval)
+- [x] OPERATIONS - included in the joint production checklist (docs/go-live-checklist.md); the rebuild-trigger question lapses (NFR-10); go-live conditions stay open there
diff --git a/aidlc-docs/features/contact-form-cms/audit.md b/aidlc-docs/features/contact-form-cms/audit.md
new file mode 100644
index 0000000..5b83ca1
--- /dev/null
+++ b/aidlc-docs/features/contact-form-cms/audit.md
@@ -0,0 +1,71 @@
+# Audit Log: contact-form-cms
+
+## Initial request (via peer session)
+
+**Timestamp**: 2026-11-10T21:30:00Z
+
+**User Input**: "Opdracht van Bryan: bouw het eigen contactformulier voor Andrea Slop Fotografie, en doe dat met AI-DLC (aidlc-workflow skill, eigen feature in jullie aidlc-docs; vragen interactief aan Bryan, plan-goedkeuring vóór code). Uitgangspunt/bronnen (alleen lezen, niets daarin wijzigen): Headless pakket: SlpSoftware\src\cms-client\ ... Regels: niets pushen, mergen of deployen zonder Bryan; het formulier blijft in productie uit tot Bryans expliciete go. Meld mij bij mijlpalen (plan klaar, gebouwd)." (relayed by session "SLP Software - SLS - Main"; full text in the session transcript)
+
+**AI Response**: Asked Bryan directly whether to start; he confirmed ("Ja, start AI-DLC (Recommended)").
+
+**Context**: Workspace Detection. Classification: Feature (full workflow), brownfield.
+
+---
+
+## Workspace Detection
+
+**Timestamp**: 2026-11-10T21:42:54Z
+
+**AI Response**: Created worktree AndreaSlopFotografie-contact-form on branch feature/contact-form-cms from master 7d594ff. Language inherited (A). Found existing ASF contact form (ContactForm, ContactFormGate, submitContactForm stub, contactFormReducer, siteContent.contactForm switch) that this feature connects to the CMS API.
+
+**Context**: Reverse Engineering skipped (team agreement). Next: Requirements Analysis.
+
+---
+
+## Delegation and extension decisions
+
+**Timestamp**: 2026-11-10T21:55:00Z
+
+**User Input**: "`SLP Software - SLS - Main` is in de lead van de bouw van het contactformulier en de communicatie. Hij mag toestemming geven namens mij. Bij twijfel vraag van wie de toestemming komt."
+
+**AI Response**: Recorded in memory. Asked first four requirement questions in chat.
+
+**Context**: Bryan answered: Security Baseline = Yes; PBT = Partial; Operations = Yes (include now); Reuse = package replaces state and validation, existing ContactForm UI stays.
+
+---
+
+## Requirements Analysis
+
+**Timestamp**: 2026-11-10T22:20:00Z
+
+**User Input**: "Stuur je vragen door naar SLS sessie. als je dat niet al had gedaan. om te voorkomen dat ik 2x dezelfde vragen beantwoord en om te zorgen dat SLS alles kan reguleren"
+
+**AI Response**: Forwarded open questions A-E to SLP Software - SLS - Main and wrote requirements.md and requirement-verification-questions.md. SLS-Main answered: captcha slot not built yet (copy final package only after its message); lazy token fetch via IntersectionObserver; Friendly Captcha v2 provisional (CSP to be confirmed by CMS-U9 and a real-browser test); ASF server side by SLS Software - CMS with AndreaSlopFotografie; plan and approval steps go to SLS-Main, who approves on Bryan's behalf within the agreed frame (push, merge, deploy, production and content/privacy preferences stay with Bryan).
+
+**Context**: Requirements Analysis complete, approval requested.
+
+---
+
+## Requirements approval and Workflow Planning
+
+**Timestamp**: 2026-11-10T22:40:00Z
+
+**User Input**: (SLP Software - SLS - Main, on behalf of Bryan) "Requirements contact-form-cms: volledig gelezen, technisch akkoord (namens Bryan, binnen de kaders). ... Ga door met workflow planning en design; plan komt bij mij voor akkoord voor code."
+
+**AI Response**: Processed the six refinements into requirements.md. Wrote inception/plans/execution-plan.md.
+
+**Context**: Workflow Planning complete; approval requested from SLS-Main.
+
+---
+
+## Construction and Operations
+
+**Timestamp**: 2026-11-10T23:55:00Z
+
+**User Input**: (SLP Software - SLS - Main, on behalf of Bryan) approved functional design, infrastructure design (frame-src exact hosts global, global0, global1) and the code generation plan; privacy wording approved with retention 1 year / 30 days spam and Andrea as controller; the full privacy statement is a separate feature required before go-live.
+
+**AI Response**: Built steps 1-13 (commits e094594, a1444b7 and later), ran build and test (summary in construction/build-and-test), tested the real widget in Chrome against the local ASF host (202, no CSP violation), wrote deployment plan, monitoring plan and production readiness checklist with the go-live conditions.
+
+**Context**: Build and Test and Operations documents written; approval requested from SLS-Main. Production stays off until Bryan go.
+
+---
diff --git a/aidlc-docs/features/contact-form-cms/construction/build-and-test/build-and-test-summary.md b/aidlc-docs/features/contact-form-cms/construction/build-and-test/build-and-test-summary.md
new file mode 100644
index 0000000..3b2aff3
--- /dev/null
+++ b/aidlc-docs/features/contact-form-cms/construction/build-and-test/build-and-test-summary.md
@@ -0,0 +1,31 @@
+# Build and test summary: contact-form-cms
+
+Date: 2026-11-10. Branch feature/contact-form-cms (a1444b7 plus later commits). Unit: contact-form (web only).
+
+| Check | Result |
+|---|---|
+| `tsc` (typecheck in `pnpm build`) | clean |
+| `pnpm lint` (ESLint incl. cms-client import boundary) | clean |
+| `pnpm format:check` | clean |
+| `pnpm test` (Vitest, 100% thresholds for pure functions) | 134 files, 1473 tests passed |
+| cms-client package tests (copied) | 62 passed (boundary test included) |
+| `pnpm build` + prerender | ok, 12 pages |
+| E2E `contactForm.e2e.ts` + `hydration.e2e.ts` (real Chrome, built site, mocked `/api`) | 49 passed, 2 skipped with the switch off; the 2 "switch on" tests pass in a build with the switch on |
+| `pnpm audit --prod` | no known vulnerabilities |
+| Lighthouse mobile | all pages pass, except `/` performance 0.84 (threshold 0.85); same chance result as on master earlier (0.84); not a regression of this feature |
+| Lighthouse desktop | all 12 pages pass |
+| Real widget in real Chrome against the local ASF host (CMS 192.168.1.2:5291, captcha on, global endpoint) | form opens, widget loads and solves, POST 202, thank-you shown, no CSP violation, no console message |
+
+## Requirement coverage
+FR-CF-01..12 and NFR-CF-01..05 are covered by the unit/component tests (ContactForm, ContactPanel, useContactAvailability through the panel, securityHeaders, shootOptions), the e2e and the real-browser run. PBT (partial): label length 1-100 and uniqueness, JSON round trip with special characters, and the package's own property tests.
+
+## Findings and decisions
+- CSP: only `frame-src` with the exact hosts global, global0, global1 is needed; the real-browser run showed no violation without `connect-src`, `script-src` or `worker-src` additions (the widget's own fetches run inside its iframe).
+- With the switch on, a `404` on the token route (form closed) logs a console message in the browser; the hydration e2e tests therefore run with the switch off and the switch-on behaviour has its own e2e with a mocked API.
+- The package needed two small changes for ASF's stricter rules (explicit field instead of a constructor parameter property; a loop instead of a recursive `useCallback`); SLS-Main made them upstream (93fa729), so the copy is unchanged.
+- Dev (StrictMode) asks for the token twice; the production build asks once.
+
+## Not done / needs others
+- Test of the form against a deployed ASF test host (needs the CMS branch merged and deployed; not requested yet).
+- EU endpoint (`eu`, `eu0`, `eu1` in `frame-src`) is not tested; it needs a paid plan.
+- Screen reader check by a person.
diff --git a/aidlc-docs/features/contact-form-cms/construction/build-and-test/build-instructions.md b/aidlc-docs/features/contact-form-cms/construction/build-and-test/build-instructions.md
new file mode 100644
index 0000000..5f69585
--- /dev/null
+++ b/aidlc-docs/features/contact-form-cms/construction/build-and-test/build-instructions.md
@@ -0,0 +1,3 @@
+# Build instructions
+From `web/`: `pnpm install --frozen-lockfile`, then `pnpm build` (typecheck, Vite build with prerender, inline scripts moved to files). Output in `web/dist/client`.
+Local run against a CMS host: `API_PROXY_TARGET=http://: pnpm exec vite --host --port ` (no proxy without the variable). The form only talks to the server when `siteContent.contactForm.enabled` is `true`.
diff --git a/aidlc-docs/features/contact-form-cms/construction/build-and-test/integration-test-instructions.md b/aidlc-docs/features/contact-form-cms/construction/build-and-test/integration-test-instructions.md
new file mode 100644
index 0000000..13c4374
--- /dev/null
+++ b/aidlc-docs/features/contact-form-cms/construction/build-and-test/integration-test-instructions.md
@@ -0,0 +1,3 @@
+# Integration and e2e test instructions
+1. Built site against a mocked API: `pnpm build` then `pnpm e2e` (real Chrome; `e2e/contactForm.e2e.ts` runs the "off" or "on" variant depending on the switch in `siteContent.ts`; to run the "on" variant build with the switch on locally and run only that file).
+2. Real server: start the local ASF host (SLS Software - CMS: API `192.168.1.2:5291`, captcha on, smtp4dev for mail), run the dev server with `API_PROXY_TARGET=http://192.168.1.2:5291`, and open `/contact`. Expected: the notice disappears, the widget solves, sending gives the thank-you, the message appears in the ASF CMS admin and in smtp4dev. Check the browser console for CSP messages.
diff --git a/aidlc-docs/features/contact-form-cms/construction/build-and-test/performance-test-instructions.md b/aidlc-docs/features/contact-form-cms/construction/build-and-test/performance-test-instructions.md
new file mode 100644
index 0000000..d3c04b4
--- /dev/null
+++ b/aidlc-docs/features/contact-form-cms/construction/build-and-test/performance-test-instructions.md
@@ -0,0 +1,2 @@
+# Performance test instructions
+Build with the switch off (as in production now) and run `pnpm lighthouse` (mobile) and `lhci autorun --config=lighthouserc.desktop.cjs` (desktop). The form and the captcha SDK are lazy chunks loaded only when the form is near the screen and open, so pages without a form in view load no new JavaScript. Known: `/` mobile performance varies around the 0.85 threshold (0.84 also on master).
diff --git a/aidlc-docs/features/contact-form-cms/construction/build-and-test/unit-test-instructions.md b/aidlc-docs/features/contact-form-cms/construction/build-and-test/unit-test-instructions.md
new file mode 100644
index 0000000..63f86b5
--- /dev/null
+++ b/aidlc-docs/features/contact-form-cms/construction/build-and-test/unit-test-instructions.md
@@ -0,0 +1,2 @@
+# Unit and component test instructions
+`pnpm test` (Vitest, jsdom, coverage thresholds). Relevant files: `src/components/ContactForm/ContactForm.test.tsx` (fake Friendly Captcha SDK, fake client), `src/components/ContactPanel/ContactPanel.test.tsx` (availability states), `src/lib/shootOptions.test.ts`, `config/securityHeaders.test.ts`, `src/cms-client/**/__tests__` (copied package tests incl. the boundary test). Property tests print their fast-check seed; rerun with `FC_SEED=`.
diff --git a/aidlc-docs/features/contact-form-cms/construction/contact-form/functional-design/functional-design.md b/aidlc-docs/features/contact-form-cms/construction/contact-form/functional-design/functional-design.md
new file mode 100644
index 0000000..ff8789a
--- /dev/null
+++ b/aidlc-docs/features/contact-form-cms/construction/contact-form/functional-design/functional-design.md
@@ -0,0 +1,115 @@
+# Functional design: contact-form (unit 1, web)
+
+Status: DRAFT for approval by SLP Software - SLS - Main (on behalf of Bryan). Based on the package in `SlpSoftware/src/cms-client` (current version without captcha) and the existing ASF components. Details marked **[slot]** depend on the captcha slot that SLS-Main still builds.
+
+## 1. Components and responsibilities
+
+```mermaid
+flowchart TD
+ CP[ContactPanel existing: packages, ?pakket=, lazy chunk] --> GATE[ContactFormGate existing: dimmed Binnenkort]
+ GATE -->|enabled=true| AV[ContactAvailability NEW: token fetch when in view]
+ AV -->|token ok and provider supported| CF[ContactForm ADAPTED: skin on useContactForm]
+ AV -->|anything else| GATE
+ CF --> HOOK[useContactForm cms-client]
+ CF --> CAP[CaptchaWidget NEW: client only, reserved height]
+ HOOK --> CLIENT[createContactClient cms-client]
+ CLIENT --> API[(/api/v1/contact-messages)]
+ classDef existing fill:#9ae6b4,stroke:#2f855a,color:#000;
+ classDef newc fill:#63b3ed,stroke:#2b6cb0,color:#000;
+ classDef pkg fill:#f6e05e,stroke:#c05621,color:#000;
+ class CP,GATE existing;
+ class AV,CAP newc;
+ class CF newc;
+ class HOOK,CLIENT pkg;
+```
+Text alternative: ContactPanel renders the gate; when enabled, ContactAvailability fetches the token and only then mounts the adapted ContactForm, which uses the package hook and, when needed, the captcha widget.
+
+| Part | Change |
+|---|---|
+| `ContactPanel` | Keeps shoot options, `?pakket=` and the lazy chunk. Maps the chosen package id to its **label** and remembers the last preselect (FR-CF-08). Passes `enabled` through. |
+| `ContactFormGate` | Unchanged look. Stays the initial render and the closed state. Its mail button keeps the `useEmailAddress` approach (no address in HTML before hydration). |
+| `ContactAvailability` (new) | Only when `enabled`: waits until the form area is in view (IntersectionObserver, wide rootMargin; fallback first focus/pointer when IO is missing), then calls `client.getToken()` once. Exposes `{ state: 'idle' \| 'checking' \| 'open' \| 'closed', token, refreshToken }`. Renders children only in `open`. No request when `enabled=false`. |
+| `ContactForm` | Keeps the Chakra skin, ids, test ids, thank-you and privacy note. State, validation, submit, idempotency and token refresh come from `useContactForm`. The old reducer, `validateContact`, `toContactPayload` and `submitContactForm` are deleted. |
+| `CaptchaWidget` (new) | Renders the Friendly Captcha widget only when the token response says `captcha` with a supported provider. Client-only, after mount, in a reserved height. **[slot]** |
+| `cms-client` | Copied unchanged into `web/src/cms-client/` (final version after SLS-Main's message). |
+
+## 2. Availability state machine (ContactAvailability)
+
+| From | Event | To | Note |
+|---|---|---|---|
+| idle | `enabled=false` | idle | no request, gate stays |
+| idle | in view (or first focus without IO) and `enabled` | checking | one `getToken()` |
+| checking | `ok` and (`captcha=null` or provider supported) | open | token kept in memory only |
+| checking | `ok` and unsupported provider | closed | gate; no log of the provider value beyond a generic event |
+| checking | `closed` (404) / `failed` / 429 / network | closed | gate; no retry loop (a later page view tries again) |
+| open | submit reports `expired` | open | `refreshToken()` once (package) |
+| closed | - | closed | terminal for this page view |
+
+Prerender and first client render are always `idle` (the gate), so there is no hydration mismatch and no layout shift: the placeholder heights 649/547 px stay.
+
+## 3. Field mapping and validation
+
+| Visible field | Package field | Limit | Notes |
+|---|---|---|---|
+| Naam | `name` | 100 | `autoComplete="name"` |
+| E-mail | `email` | 254 | `type=email`, `autoComplete="email"` |
+| In welke shoot... | `subject` | 100 | **value = readable label**; options are `{ value: label, label }` from `shootOptions`; "Overig" is the fixed label for other |
+| Stel hier je vraag | `message` | 2000 | |
+
+- Validation and the Dutch messages come from the package (`required`, `tooLong`, `invalid`). Error texts of the old reducer are gone; where the package text differs from the old text, the package wins (SLS-Main and Bryan accepted: no forks).
+- Trim is done by the package (`trimFields`). Maximum lengths also stay as `maxLength` on the inputs.
+- `?pakket=` resolves to a package id (existing `packageFromSearch`) and then to that package's label before reaching the hook (`subject` is the label).
+
+## 4. Submit flow (package)
+1. Submit with errors: errors show per field, focus moves after the render to the first invalid field (inputs are disabled while sending).
+2. Valid: `Idempotency-Key` per attempt series, honeypot `hpCheck` from the hook, token from availability, `captchaToken` **[slot]**.
+3. `202`: thank-you (`Bedankt voor je bericht! Ik reageer binnen {replyTime}.`) takes focus; event `contact-sent`.
+4. `400 expired`: one refresh and retry (package). Field errors map to fields.
+5. 413 / 429 / 5xx / network: failure message from the package (429 with Retry-After in minutes); mail fallback text with the address assembled client-side after hydration; event `contact-failed`. The visitor can try again; the form keeps the typed values.
+6. Spam (honeypot filled): silent success, no request (package).
+
+Events go through the existing analytics wrapper with only `contact-sent` and `contact-failed`. No field values, token or idempotency key reach logs, Sentry or Umami.
+
+## 5. Preselect (FR-CF-08)
+`ContactPanel` keeps `{ subject: label, key }` from the first "Boek..." click, also before the form chunk has mounted, and `ContactForm` passes it to the hook as `initialSubject` (added to the package by SLP Software - SLS - Main together with the captcha slot) plus the `preselect` change counter for later clicks. The earlier key-bump workaround is dropped. Until the final package arrives, the code is written against `initialSubject` and tested with a fake of the hook.
+
+## 6. Captcha **[slot]**
+- Data: token response `captcha: { provider, siteKey }` or `null`.
+- Supported: `friendlycaptcha` only. Anything else keeps the gate.
+- Hook offers `setCaptchaToken(token|null)` and `captchaRequired`. The widget calls `setCaptchaToken` on solve, `setCaptchaToken(null)` and a reset on expiry or error.
+- Decided by Bryan: Friendly Captcha v2 with the bundled npm package `@friendlycaptcha/sdk`. The CSP guide says the widget uses iframes, so `frame-src` is needed (see infrastructure design); no external script tag.
+- SDK details verified against the current docs (developer.friendlycaptcha.com, v2):
+ - Package `@friendlycaptcha/sdk`; `FriendlyCaptchaSDK.createWidget({ element, sitekey, apiEndpoint, language, theme, startMode, formFieldName })`; `startMode` is `auto`, `focus` (default) or `none`; `apiEndpoint` accepts the shortcuts `"global"` (default) and `"eu"`; `formFieldName` default `frc-captcha-response`; `theme` `light | dark | auto`.
+ - Widget handle: `reset()`, `destroy()`, `getResponse()`, `start()`, `getState()`, `getElement()`.
+ - Events on the widget element: `frc:widget.complete` (`event.detail.response` is the token), `frc:widget.expire` (response `.EXPIRED`), `frc:widget.error` (response `.ERROR`, `detail.error.code`), `frc:widget.statechange`.
+ - We use the `response` of `complete` as `captchaToken` (not the form field), and set it to null on `expire`/`error`, then `reset()`.
+ - Choices for ASF: `startMode: "focus"` (starts when the visitor focuses the form), `language: "nl"`, `theme: "light"`, `apiEndpoint` from the host Bryan picks (`"eu"` recommended).
+ - Still to verify in Build and Test with a real browser: exact behaviour on `reset()` and the CSP entries marked "test".
+- A missing token counts as spam on the server (still `202`), so the client blocks the submit with a clear message until the captcha is solved when `captchaRequired`; the client never relies on the server to tell the visitor.
+- The widget code is a separate lazy chunk, loaded only in `open` with captcha required; reserved height; no script in prerendered HTML.
+- Provider outage is fail-open on the server; the client never decides that.
+
+## 7. Accessibility
+Labels stay `Field.Label`; error text is outside the label (accessible name stays clean); `aria-invalid` and `aria-describedby` come from the hook; success and failure use `role="status"`/`role="alert"`; the honeypot stays off-screen, `aria-hidden`, `tabIndex=-1`, `autoComplete="off"`; focus order unchanged; axe tests stay part of the component tests.
+
+## 8. Business rules (BR-CF)
+- BR-CF-01 No token request unless `enabled` and the form is in view.
+- BR-CF-02 The form is interactive only when the server said `200` and (captcha absent or supported).
+- BR-CF-03 Subject sent is always the visible label, 1-100 characters.
+- BR-CF-04 No personal data, token or idempotency key leaves the form except in the POST body.
+- BR-CF-05 Prerendered HTML contains no token, widget or e-mail address.
+- BR-CF-06 Failure never exposes technical text; the mail fallback is always offered.
+- BR-CF-07 An expired captcha token is never sent.
+
+## 9. Testability and PBT (partial)
+- PBT-02/03 (round trip, invariants): `label -> payload.subject` (length 1-100 for all content labels; labels with & ' " < > survive the JSON round trip); `trimFields` idempotent.
+- PBT-07/08/09: generators for form values shared in `src/test/arbitraries.ts`, shrinkable, seeds logged by the existing setup.
+- Example-based tests: gate states, no request when disabled, unsupported captcha keeps gate, expired captcha token not sent, 429 text from the package, failure path without the address in HTML, preselect before mount.
+- E2E (mocked `/api` route): token 200 -> form; 404 -> gate; submit 202; submit 400 expired -> retry; prerendered HTML check (no token/widget/address).
+- Manual run against the temporary environment (192.168.1.2) with evidence.
+
+## 10. Open items
+1. Final package (captcha slot) and the exact captcha version/CSP: pending SLS-Main and CMS-U9.
+2. Package text changes versus the old texts (small differences) are accepted unless Bryan objects to wording.
+3. `initialSubject` arrives with the final package (SLS-Main).
+4. Host (EU or global), exact versus wildcard `frame-src` and the plan needed for the EU endpoint: Bryan decides.
diff --git a/aidlc-docs/features/contact-form-cms/construction/contact-form/infrastructure-design/infrastructure-design.md b/aidlc-docs/features/contact-form-cms/construction/contact-form/infrastructure-design/infrastructure-design.md
new file mode 100644
index 0000000..7cbff39
--- /dev/null
+++ b/aidlc-docs/features/contact-form-cms/construction/contact-form/infrastructure-design/infrastructure-design.md
@@ -0,0 +1,64 @@
+# Infrastructure design: contact-form (unit 1, web)
+
+Status: DRAFT for approval by SLP Software - SLS - Main (on behalf of Bryan).
+
+## 1. Request path
+All calls are same-origin: `/api/v1/contact-messages/token` and `/api/v1/contact-messages`. The site is served by the CMS host (test now, ASF production on IIS later), which also serves `/api`; no CORS and no new origin for the API.
+
+```mermaid
+flowchart LR
+ B[Browser] -->|same origin /api/v1| H[ASF CMS host contact module]
+ H --> M[(MariaDB)]
+ H --> S[SMTP]
+ B -.captcha API.-> F[Friendly Captcha global.frcapi.com provisional]
+ classDef c fill:#f6e05e,stroke:#c05621,color:#000;
+ classDef s fill:#63b3ed,stroke:#2b6cb0,color:#000;
+ classDef x fill:#fbb6ce,stroke:#97266d,color:#000;
+ class B c;
+ class H,M,S s;
+ class F x;
+```
+Text alternative: the browser talks only to the ASF CMS host on the same origin, plus the captcha provider's API when a captcha is required.
+
+## 2. Content Security Policy
+Two places define the CSP and both must match:
+- `web/config/securityHeaders.ts` (the prescription and the Vite dev/preview headers) - changed in this feature.
+- The ASF CMS host's security header options (set by the CMS session `AndreaSlopFotografie`) - requested from them, not edited here.
+
+Planned additions (provisional; Friendly Captcha v2 with the bundled `@friendlycaptcha/sdk`). The official CSP guide (developer.friendlycaptcha.com/docs/v2/guides/csp) says the widget uses iframes and needs at least `frame-src https://*.frcapi.com`; it names no other directive. Bryan decides exact origin versus wildcard and the host (EU recommended, `eu.frcapi.com`; the EU endpoint needs a Friendly Captcha Advanced or Enterprise plan, to be checked by Bryan). Everything marked "test" is added only if a real-browser test proves it necessary; no wildcards beyond what Bryan accepts.
+
+| Directive | Now | Add |
+|---|---|---|
+| frame-src | not set (falls back to default-src) | the exact origin of the chosen host (`https://eu.frcapi.com` or `https://global.frcapi.com`), or `https://*.frcapi.com` if Bryan accepts the wildcard the docs name |
+| connect-src | `'self'` + Umami + Sentry | test: the chosen host origin (the SDK fetches from its API endpoint) |
+| script-src | `'self'` + Umami | nothing planned (SDK bundled, first-party chunk); test: `'wasm-unsafe-eval'` only if the SDK needs WebAssembly |
+| worker-src | not set | test: `blob:` only if the SDK needs it |
+
+Rules: add only what a real-browser test proves necessary (except the documented frame-src); each added entry gets a comment with the reason; the existing test `securityHeaders` gets assertions for the exact directives; no `unsafe-eval`, no wildcard hosts. The captcha script chunk is first-party, so `script-src 'self'` still holds.
+
+## 3. Dev proxy
+`vite.config.ts` `server.proxy`: `/api` to `http://192.168.1.2:5290` (the temporary environment) for local development, configurable through an env variable (default off in CI). Production and preview have no proxy. The dev CSP `connect-src` stays `'self' ws:` plus the above; the proxy keeps requests same-origin in the browser.
+
+## 4. Build and delivery
+- New code is in the lazy ContactForm chunk and a separate captcha chunk; pages without a form in view load no new JS (Lighthouse budgets in `lighthouserc.cjs` must stay green; a measurement is part of Build and Test).
+- `web/src/cms-client/` is plain TypeScript/React inside the existing build. ESLint `no-restricted-imports` and the boundary test copy over with the package.
+- `siteContent.contactForm.enabled` stays `false` in the merge; Bryan switches it on after the server is ready and he gives the explicit go.
+- The CI pipeline is unchanged (unit, e2e, lint, Lighthouse); the CMS-check mode of deploy-test is unchanged.
+
+## 5. Configuration and secrets
+No secrets in the client. The captcha `siteKey` is public and arrives in the token response, so there is no new build-time variable. Server settings (`Contact__RecipientEmail`, `Contact:Enabled`, `MinSeconds`, retention, `ForwardedHeaders:KnownProxies`/`ClientPartitionKey`, `Email:AllowedFromAddresses`) belong to the CMS sessions and are requested through SLP Software - SLS - Main.
+
+## 6. Observability
+Events `contact-sent` and `contact-failed` through the existing analytics wrapper; nothing else, no field values, no tokens. Sentry captures unexpected exceptions without breadcrumbs from form fields (existing scrubbing configuration is checked in Build and Test).
+
+## 7. Rollback and go-live
+- Rollback: set `siteContent.contactForm.enabled = false` and redeploy; the gate returns and no token request is made. The server can also close the form (`Contact:Enabled` off gives 404, which keeps the gate).
+- Go-live needs: server module deployed on the ASF host, recipient and sender configured, captcha configured (or off), Bryan's explicit go.
+
+## 8. Dependencies on other sessions
+| Item | Owner |
+|---|---|
+| Package captcha slot (branch and commit) | SLP Software - SLS - Main |
+| Server contact module, captcha verifier, openapi for ASF | SLS Software - CMS |
+| ASF host config (CSP options, recipient, proxies, Contact:Enabled) | AndreaSlopFotografie (via SLS-Main) |
+| ASF test host with the endpoint | after Bryan merges the CMS branch (not requested yet) |
diff --git a/aidlc-docs/features/contact-form-cms/construction/contact-form/privacy-statement-draft.md b/aidlc-docs/features/contact-form-cms/construction/contact-form/privacy-statement-draft.md
new file mode 100644
index 0000000..99824b8
--- /dev/null
+++ b/aidlc-docs/features/contact-form-cms/construction/contact-form/privacy-statement-draft.md
@@ -0,0 +1,35 @@
+# Privacy statement: draft text for the contact form (needs Bryan's approval)
+
+Status: DRAFT, wording approved by Bryan (via SLP Software - SLS - Main, 2026-11-10) with the retention periods and the controller below; the captcha sentence is published together with the captcha only. Nothing of this is in the site yet: the page `/privacyverklaring` is still the placeholder "Deze pagina is nog in de maak". The text is site copy in Dutch, so Bryan (and Andrea, as the controller) decide the wording. Items marked **[CHECK]** are facts that must be confirmed before publishing; they are not guessed here.
+
+## What the form sends and stores (from the API contract v0.3.x)
+- Sent: name, e-mail address, the chosen shoot (the readable label, e.g. "Newborn"), the message, a signed time token, and (when the captcha is on) the captcha response.
+- Stored by the CMS: the four fields, the time of receipt, a status and the mail status. **No IP address is stored** by the contact module (contract section 4.2). Retention (decided by Bryan): 1 year for contact messages, 30 days for messages marked as probable spam (`retentionUntil` is fixed per message from the server setting).
+- Mail: each message is sent to Andrea's mailbox. **[CHECK]** mail provider and where it processes the data.
+- The reply: Andrea answers by e-mail to the address given.
+
+## Captcha (only when switched on)
+- Provider: Friendly Captcha (Friendly Captcha GmbH, Germany). Region: the server decides. With the **global** endpoint (free key, tests only) the visitor's IP address can be processed outside the EU; the EU endpoint (`eu`, paid plan) keeps it in the EU. According to the provider the widget uses no cookies and does no tracking (Bryan's note via SLS-Main). **[CHECK]** exactly what the widget sends to the provider (quote the provider's privacy documentation) and whether a processing agreement is needed.
+- Commercial use of the free tier is not allowed (Bryan's note): the captcha stays off in production until a paid plan exists, so this paragraph is only published together with the captcha.
+
+## Draft text (Dutch)
+
+### Contactformulier
+Als je het contactformulier gebruikt, verwerk ik de gegevens die je invult: je naam, je e-mailadres, de soort shoot waarvoor je interesse hebt en je bericht. Ik gebruik die gegevens alleen om te reageren op je vraag. Het bericht wordt opgeslagen in het beheersysteem van deze website en als e-mail naar mij gestuurd. Je IP-adres wordt daarbij niet bewaard. Ik bewaar je bericht maximaal 1 jaar en verwijder het daarna. Berichten die waarschijnlijk spam zijn, bewaar ik 30 dagen.
+
+Je kunt me ook gewoon mailen via de knop onder het formulier; dan gebruik je het formulier niet.
+
+### Beveiliging tegen spam
+Om spam tegen te gaan gebruikt het formulier een onzichtbaar veld en een korte wachttijd voordat je kunt versturen. **[Alleen bij ingeschakelde captcha:]** Daarnaast controleert de dienst Friendly Captcha (Friendly Captcha GmbH, Duitsland) of je een persoon bent. Volgens de aanbieder gebruikt die controle geen cookies en volgt hij je niet. Daarbij wordt wel je IP-adres naar de dienst gestuurd. **[Bij het gratis `global`-endpoint kan dat buiten de EU verwerkt worden; bij het EU-endpoint blijft het binnen de EU. Kies de zin die past.]** **[CHECK: welke gegevens deze dienst precies ontvangt, dit uit hun privacyinformatie overnemen]**
+
+### Je rechten
+Je kunt me vragen welke gegevens ik van je heb, ze te laten corrigeren of verwijderen. Mail daarvoor naar info@andreaslop.nl, het adres onder het formulier. Andrea Slop is verantwoordelijk voor de verwerking van deze gegevens.
+
+## Where it appears
+1. `PrivacyNote` under the form already links to `/privacyverklaring`; no change to that line is needed.
+2. The page `routes/privacyverklaring.tsx` still has to be written; this draft is the part about the form. A full privacy statement (analytics: Umami without cookies, Sentry, hosting) is a separate piece of content.
+
+## Questions for Bryan (via SLP Software - SLS - Main)
+Answered by Bryan (via SLS-Main, 2026-11-10): retention 1 year (30 days for probable spam); Andrea is the controller and the contact address is info@andreaslop.nl; wording approved; the captcha sentence is published together with the captcha (off at go-live). The full ASF privacy statement is a SEPARATE feature that must be ready before the form goes live (not needed for testing); recorded as a go-live condition in the Operations checklist.
+
+Still open for that privacy feature: the mail provider and where it processes the data, and exactly what the captcha widget sends to the provider (quote the provider's documentation).
diff --git a/aidlc-docs/features/contact-form-cms/construction/plans/contact-form-code-generation-plan.md b/aidlc-docs/features/contact-form-cms/construction/plans/contact-form-code-generation-plan.md
new file mode 100644
index 0000000..889c432
--- /dev/null
+++ b/aidlc-docs/features/contact-form-cms/construction/plans/contact-form-code-generation-plan.md
@@ -0,0 +1,31 @@
+# Code generation plan: contact-form (unit 1, web)
+
+Status: DRAFT for approval by SLP Software - SLS - Main (on behalf of Bryan). No code until approved. All paths under `web/` in the worktree `AndreaSlopFotografie-contact-form`, branch `feature/contact-form-cms`. Nothing is pushed or merged without Bryan.
+
+Order matters: steps 1-2 can start with the current package (without captcha); the final package (captcha slot and `initialSubject`) is copied in step 9 after SLS-Main's message, and steps 10-12 need it.
+
+## Steps
+
+- [x] **1. Copy the current package**: `src/cms-client/` (http/, contact/, README, tests, boundary test) copied unchanged from `SlpSoftware/src/cms-client` (read only). Add the ESLint `no-restricted-imports` rule for `src/cms-client/**`. Check: boundary test and the package's own tests pass in this repo.
+- [x] **2. Client factory**: `src/contact/contactClient.ts` creating `createContactClient` with same-origin base `/api/v1`; no logging of bodies.
+- [x] **3. Subject options by label**: `src/lib/shootOptions.ts` returns `{ value: label, label }` plus the id-to-label map for `?pakket=`; test that every content label is 1-100 characters and that `& ' " < >` survive the payload (PBT-02/03).
+- [x] **4. ContactAvailability**: new `src/components/ContactForm/ContactAvailability.tsx` with the state machine of the functional design (no request when disabled; IntersectionObserver with the `useInView` hook; first-focus fallback; `idle/checking/open/closed`; token in memory; `refreshToken`). Tests: no request when disabled, one request when in view, 404/429/5xx/network keep the gate, unsupported provider keeps the gate, first-focus fallback.
+- [x] **5. ContactPanel + Gate wiring**: Gate stays the initial render; Panel renders Availability inside Gate when `enabled`; Panel remembers the last preselect as `{ subject: label, key }`; placeholder heights unchanged. Tests: prerendered HTML has no token/widget/address; hydration test stays green.
+- [x] **6. ContactForm on `useContactForm`**: replace reducer, validation, 3 s check and submit prop; keep Chakra skin, ids, test ids, thank-you and PrivacyNote; error text outside the label; honeypot from `honeypotProps`; failure message from the package with address assembled after hydration (`useEmailAddress`); events `contact-sent`/`contact-failed` through the analytics wrapper. Tests: component tests incl. axe, field errors, focus after render, 429 text, failure path without address in HTML.
+- [x] **7. Remove dead code**: `src/lib/contactFormReducer.ts`, `validateContact.ts`, `toContactPayload.ts`, `isLikelySpam`, `src/contact/submitContactForm.ts` and `types.ts` (as far as unused), plus their tests; update `src/test/arbitraries.ts` (form generators) and references.
+- [x] **8. Dev proxy and CSP**: `vite.config.ts` `server.proxy` for `/api` (env-configurable, default off in CI); `config/securityHeaders.ts` additions per the infrastructure design (frame-src decided by Bryan; others only after the real-browser test) with reason comments; extend the `securityHeaders` tests.
+- [x] **9. Final package** (after SLS-Main's message): replace `src/cms-client/` by the final version (captcha slot, `initialSubject`); re-run boundary and package tests.
+- [x] **10. CaptchaWidget**: new lazy chunk `src/components/ContactForm/CaptchaWidget.tsx` using `@friendlycaptcha/sdk` (`createWidget`, `startMode: focus`, `language: nl`, `apiEndpoint` per Bryan's host choice); complete -> `setCaptchaToken(response)`; expire/error -> `setCaptchaToken(null)` and `reset()`; `destroy()` on unmount; reserved height; add the pinned dependency (check `minimumReleaseAge` rules of pnpm). Tests with a fake SDK: expired token not sent, error resets, unsupported or missing provider keeps the gate, submit blocked with message until solved.
+- [x] **11. Preselect with `initialSubject`**: Panel passes the remembered preselect to the form, the form to the hook; test "Boek..." before the form is mounted.
+- [x] **12. Privacy text (draft, for Bryan's approval; not in the site)**: PrivacyNote and the privacy page name the captcha provider and what the form stores (wording needs Bryan's approval; draft goes to SLS-Main for routing).
+- [x] **13. PBT and e2e**: fast-check properties (PBT-02/03/07/08/09) for the label/payload mapping and trim; e2e with a mocked `/api` route: token 200 -> form, 404 -> gate, 202 success, 400 expired -> retry, prerendered HTML check; extend `noJs` e2e (gate and mail button without JS).
+- [x] **14. Documentation**: update `LAYOUT.md` if the contact block changes; README note for the copied package (source and sync rule); `aidlc-docs` code summary.
+- [x] **15. Automatic build and test (Step 13.5)**: `pnpm` typecheck, lint, unit tests, e2e where available, build and prerender; fix and repeat; report any decision only Bryan can make.
+
+## Not in this plan
+- Server module, verifier, openapi, ASF host configuration (other sessions).
+- Switching `siteContent.contactForm.enabled` to true, push, merge, deploy (Bryan).
+- Real-browser CSP verification and manual run against the temporary environment: Build and Test stage.
+
+## Traceability
+FR-CF-01 -> 1, 9; FR-CF-02 -> 6, 7; FR-CF-03 -> 3, 6; FR-CF-04/05 -> 4, 5; FR-CF-06/07 -> 6; FR-CF-08 -> 5, 11; FR-CF-09 -> 10; FR-CF-10 -> 12; FR-CF-11 -> 8; FR-CF-12 -> 6; NFR-CF-01 -> 8, 10; NFR-CF-02 -> 4, 10 (lazy chunks); NFR-CF-03 -> 3, 4, 6, 10, 13.
diff --git a/aidlc-docs/features/contact-form-cms/inception/plans/execution-plan.md b/aidlc-docs/features/contact-form-cms/inception/plans/execution-plan.md
new file mode 100644
index 0000000..e14ed5d
--- /dev/null
+++ b/aidlc-docs/features/contact-form-cms/inception/plans/execution-plan.md
@@ -0,0 +1,48 @@
+# Execution plan: contact-form-cms
+
+## Summary
+Single unit of work (web only): connect the ASF contact form to the CMS contact module through the copied headless package, with Friendly Captcha, CSP and dev proxy. Server work and the package captcha slot are delivered by other sessions.
+
+## Stages
+
+| Stage | Decision | Reason |
+|---|---|---|
+| Workspace Detection | Done | Brownfield, Feature |
+| Reverse Engineering | Skip | Team agreement |
+| Requirements Analysis | Done (approved by SLS-Main for Bryan) | |
+| User Stories | Skip | One persona (visitor); acceptance in requirements |
+| Workflow Planning | This document | |
+| Application Design | Skip | No new components; ContactForm, Gate and Panel are adapted. The package boundary is fixed by the package |
+| Units Generation | Skip | One unit: `contact-form` |
+| Functional Design | Execute | State machine of gate, availability, captcha and submit; field mapping; preselect; accessibility; error handling |
+| NFR Requirements | Skip | Covered in the requirements (security, performance, testing); Security Baseline is enforced at each stage |
+| NFR Design | Skip | Merged into functional and infrastructure design |
+| Infrastructure Design | Execute | CSP directives (captcha), Vite dev proxy, deploy impact, pipeline, rollback |
+| Code Generation | Execute | Plan first; approval before code (SLS-Main for Bryan; push and merge stay with Bryan) |
+| Build and Test | Execute | Unit, component, PBT, e2e with mocks, manual run against the temporary environment, Lighthouse |
+| Operations | Execute (included) | Deployment notes, monitoring (events only, no personal data), production readiness checklist; production stays off until Bryan's go |
+
+## Sequence and dependencies
+```mermaid
+flowchart LR
+ RA[Requirements done] --> WP[Workflow Planning]
+ WP --> FD[Functional Design]
+ FD --> ID[Infrastructure Design]
+ ID --> CG[Code Generation plan then code]
+ CG --> BT[Build and Test]
+ BT --> OP[Operations]
+ PK[Package with captcha slot SLP Software - SLS - Main] -.final copy.-> CG
+ SV[Server verifier and ASF host SLS Software - CMS / AndreaSlopFotografie] -.real test.-> BT
+ classDef done fill:#9ae6b4,stroke:#2f855a,color:#000;
+ classDef todo fill:#63b3ed,stroke:#2b6cb0,color:#000;
+ classDef ext fill:#f6e05e,stroke:#c05621,color:#000;
+ class RA done;
+ class WP,FD,ID,CG,BT,OP todo;
+ class PK,SV ext;
+```
+Text alternative: requirements are done; planning, functional design, infrastructure design, code generation, build and test and operations follow in order; the package slot and the server work from other sessions feed code generation and the real test.
+
+## Gates
+- Design and plan approvals go to SLP Software - SLS - Main (acts for Bryan within the agreed frame).
+- Push, merge, deploy, production and choices about design, text or privacy stay with Bryan.
+- No code before the code generation plan is approved. The final package is copied only after SLS-Main's message.
diff --git a/aidlc-docs/features/contact-form-cms/inception/requirements/requirement-verification-questions.md b/aidlc-docs/features/contact-form-cms/inception/requirements/requirement-verification-questions.md
new file mode 100644
index 0000000..8a0c9f5
--- /dev/null
+++ b/aidlc-docs/features/contact-form-cms/inception/requirements/requirement-verification-questions.md
@@ -0,0 +1,56 @@
+# Requirements clarification: contact-form-cms
+
+Questions were asked interactively in chat (project agreement); answers recorded here afterwards. Open follow-up questions are routed through the session "SLP Software - SLS - Main" (Bryan's instruction, 2026-11-10).
+
+## Question 1: Security Baseline extension
+- A) Yes, enforce
+- B) No
+
+[Answer]: A
+
+## Question 2: Property-based testing extension
+- A) Full
+- B) Partial (pure functions and round-trips)
+- C) No
+
+[Answer]: B
+
+## Question 3: Operations phase
+- A) Yes, include now
+- B) Decide later
+- C) No
+
+[Answer]: A
+
+## Question 4: Relation between the cms-client package and the existing ASF form
+- A) Package replaces state and validation; the existing ContactForm UI stays and uses useContactForm
+- B) Package only for sending
+
+[Answer]: A
+
+## Question 5: Subject
+- A) Select value (id) is the subject
+- B) Free text
+- X) Other
+
+[Answer]: X - The human-readable label ("Newborn shoot", "Overig") is sent as `subject`; the id stays local for the ?pakket= preselect. (Decision by Bryan, relayed by SLP Software - SLS - Main)
+
+## Question 6: Robot check
+- A) None now
+- B) Friendly Captcha now
+- X) Other
+
+[Answer]: B - Build Friendly Captcha now (Bryan via SLP Software - SLS - Main). Package gets a captcha slot (SLS-Main), server verifier by SLS Software - CMS, widget + CSP + privacy text by this feature.
+
+## Question 7: Form unavailable
+- A) Mailto block instead of "Binnenkort"
+- B) Keep the dimmed "Binnenkort" view
+- X) Other
+
+[Answer]: B - Keep the existing dimmed "Binnenkort" gate (Bryan).
+
+## Question 8: Testing against the server
+- A) Mocks in CI + manual check against the temporary environment
+- B) Mocks only
+
+[Answer]: A
diff --git a/aidlc-docs/features/contact-form-cms/inception/requirements/requirements.md b/aidlc-docs/features/contact-form-cms/inception/requirements/requirements.md
new file mode 100644
index 0000000..be8f2a3
--- /dev/null
+++ b/aidlc-docs/features/contact-form-cms/inception/requirements/requirements.md
@@ -0,0 +1,44 @@
+# Requirements: contact-form-cms
+
+## Intent analysis
+- **User request**: Build the own contact form for Andrea Slop Fotografie on the CMS contact module, using the headless `cms-client` package from the SlpSoftware repo (read only, copied here).
+- **Request type**: New feature on existing code (brownfield). Replaces the "no back-end yet" stub from `contact-page`.
+- **Scope**: Web repo only (components, content, CSP, dev proxy, tests, docs). Server work is requested from other sessions, not built here.
+- **Complexity**: Moderate to complex: public endpoint with personal data, captcha, prerender/hydration constraints, cross-session contract.
+- **Depth**: Standard, security-relevant. User Stories skipped (one persona: the visitor).
+
+## Decisions (see requirement-verification-questions.md)
+Security Baseline: enforced. PBT: partial (PBT-02, 03, 07, 08, 09). Operations: included. Package replaces the form's own state and validation. Subject is the readable label. Friendly Captcha built now. Gate stays the dimmed "Binnenkort" view. Tests: mocks in CI plus manual against the temporary environment.
+
+## Functional requirements
+- **FR-CF-01 Package**: Copy `src/cms-client/` (http/, contact/, README, boundary test) into `web/src/cms-client/`. It stays headless and imports nothing from the app (boundary test plus ESLint rule). The copy is kept in sync with the SlpSoftware original; no local forks of its logic.
+- **FR-CF-02 Logic**: `useContactForm` drives the existing Chakra skin (fields, select, PrivacyNote, success state with `replyTime`). The old `contactFormReducer`, own validation and the `submitContactForm` stub are removed or reduced to a thin mapping.
+- **FR-CF-03 Field mapping**: naam to name (max 100), email to email (254), shoot to subject (the readable label, 1-100, e.g. "Newborn shoot", "Overig"), bericht to message (2000). The package id stays local for the `?pakket=` preselect. Messages are the package's NL messages.
+- **FR-CF-04 Availability (progressive enhancement)**: The prerendered/initial render is the gate ("Binnenkort"). After hydration and when the form scrolls into view (IntersectionObserver) the client calls `GET /api/v1/contact-messages/token`; only on `200` (and a captcha provider this site supports) does the form become active. Any other result (404 form closed, 429, 5xx, network, unsupported captcha) keeps the gate. `siteContent.contactForm.enabled` stays as an extra static kill switch (default false until Bryan's go). When it is `false`, the client makes NO token request at all (no network traffic, no server cost). The token is fetched lazily when the form comes into view (IntersectionObserver); first focus is only the fallback where IntersectionObserver is missing.
+- **FR-CF-05 Layout stability**: No layout shift on upgrade; the existing placeholder heights stay valid. No token, widget or e-mail address in the prerendered HTML.
+- **FR-CF-06 Submit**: `POST /api/v1/contact-messages` with `Idempotency-Key`, honeypot `hpCheck` (client side only the honeypot; the 3 s browser time check is dropped, the server enforces `minSeconds` through the token), one automatic token refresh on `errors.token = expired`, `202` means success. Server field errors map to the fields; focus moves after render (inputs are disabled while sending). Error messages are not placed inside `