Files
AndreaSlopFotografie/docs/go-live-checklist.md
T
SluijsensandClaude Sonnet 5.5 6ff415e1bc Documents the CMS packages, banners, deploy flow and go-live conditions
Adds docs/cms-integration.md, docs/deploy-and-ci.md and
docs/go-live-checklist.md, fills in the README (set-up and commands) and
points AGENTS.md at the docs so they are kept up to date.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-15 00:07:51 +01:00

2.7 KiB

Go-live checklist

What must be true before the CMS-driven parts of the site go to production. Bryan gives the explicit go for each; nothing here is done by merging alone. The per-feature record is in aidlc-docs/features/contact-form-cms/operations/production-readiness-checklist.md and aidlc-docs/features/asf-packages-cms/.

Before merging to master

  • Revert the TEST ONLY commit d449e76 and check contactForm.enabled is false (deploy-and-ci.md).
  • Merge order: feature/contact-form-cms, then feature/asf-packages-cms.
  • The nightly test build only starts after the packages feature is on master (schedules run from the default branch).

Packages and banners

  • Production hosting (IIS) in place and /api/v1/* reverse-proxied to a production CMS host for ASF, or the CMS host serving the site (cms-integration.md). Without it production keeps the committed snapshot and the console shows a 404 per page view.
  • web/src/content/offerings.snapshot.json holds the real, current packages (production builds use it).
  • The production CMS holds the real packages. The test CMS prices must never end up in the production artifact (it is built without OFFERINGS_URL).

Contact form

  • All conditions in the contact-form production readiness checklist (server module, recipient, sender, retention 1 year / 30 days spam, proxies, CSP frame-src, a real mail from the production host).
  • Captcha decision: off at go-live until a paid Friendly Captcha plan exists; the EU endpoint changes the CSP and the privacy text.
  • Then, in its own reviewed change, siteContent.contactForm.enabled = true.

Privacy statement (page /privacyverklaring)

The statement is a separate feature on branch feature/privacy-statement (a draft; nothing of it is live). It may only go live when:

  • Bryan has approved the text.
  • The hosting and mail provider (MijnHostingPartner) is confirmed as processor, a processing agreement (verwerkersovereenkomst) exists, and data and mail processing in the Netherlands is confirmed.
  • The response time ("binnen een maand") is confirmed.
  • The captcha paragraph matches the captcha decision above (the paragraph is hidden while captcha is off).
  • No [OPEN: marker is left in a visible section (unresolvedPlaceholders() in privacyContent.ts returns an empty list).
  • The retention periods in the statement match the server settings (1 year, 30 days for spam).

The contact form must not go live before the statement does.

Other open items

  • ASF production hosting on IIS (separate feature).
  • First ASF administrator and removal of the setup token (CMS).
  • Messages created by the Playwright test run in the ASF test CMS are archived by Bryan.