Files
AndreaSlopFotografie/docs/go-live-checklist.md
T
SluijsensandClaude Sonnet 5.5 b12ae37f29 Removes the nightly test build: the CMS host injects current data into the HTML
The schedule trigger and its conditions in the jobs are gone; docs say that a
content change needs no rebuild (NFR-10) and that production gets the same
only once it is served by the CMS host.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-17 08:32:52 +01:00

3.4 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

  • The TEST ONLY commit d449e76 is undone: the form is closed unless the build sets VITE_CONTACT_FORM_ENABLED=true (only the test build does; deploy-and-ci.md).
  • Merge: the CMS PR first, then feature/asf-packages-cms (which carries the contact-form commits).

Packages and banners

  • Production hosting in place with the CMS host as the one entry of the website: IIS passes ALL requests to the CMS host (not only /api/v1/*) and serves no static files itself; the prerendered dist/ is deployed to the CMS host (cms-integration.md, "Hosting"). The generated IIS config and the production upload script are updated for this. Without it production keeps the committed snapshot and the console shows a 404 per page view for the API.
  • 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, with Bryan's explicit go (after the captcha decision), the production build gets VITE_CONTACT_FORM_ENABLED=true, in its own reviewed change. Until then the production artifact has the form closed.
  • Operations for the form are part of this joint production checklist (no separate steps; the rebuild-trigger question lapses because the CMS host shows changes at once, NFR-10).

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: CMS host behind IIS pass-through (separate feature, see above).
  • Host injection of CMS data into the prerendered pages (plan: aidlc-docs/features/asf-cms-host-injection/plan.md, after the current merges).
  • 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.