Continuous Integration / check (pull_request) Successful in 2m20s
Continuous Integration / build-test (pull_request) Skipped
Continuous Integration / deploy-test (pull_request) Skipped
Continuous Integration / lighthouse (pull_request) Successful in 8m55s
Continuous Integration / deploy-production (pull_request) Skipped
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
4.0 KiB
4.0 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
d449e76is undone: the form is closed unless the build setsVITE_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 prerendereddist/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.jsonholds 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).
Hero
- The hero module is on
masterand the CMS host of the target environment has the hero module and the injection (HERO-HTML,HERO-PRELOAD,heroin the data block). - ASF-test: the hero is seeded (Bryan runs the seed, admin password) and the home page checked on phone and desktop; the assumption list
aidlc-docs/features/hero-module/assumptions-and-open-questions.mdis read. - Production: ASF-production is served by the CMS host (the IIS pipeline, later) and holds the real hero. Until then production shows the baked hero in
src/content/heroContent.ts; check that it is the one you want.
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()inprivacyContent.tsreturns 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.