Opens the contact form through a build switch instead of the TEST ONLY commit; closes the AI-DLC records
Continuous Integration / check (pull_request) Successful in 2m25s
Continuous Integration / build-test (pull_request) Skipped
Continuous Integration / deploy-test (pull_request) Skipped
Continuous Integration / lighthouse (pull_request) Successful in 9m2s
Continuous Integration / deploy-production (pull_request) Skipped

The form is closed unless the build sets VITE_CONTACT_FORM_ENABLED=true (only
the test build does), so d449e76 no longer has to be undone before the merge.
Status files of contact-form-cms, asf-packages-cms, asf-cms-host-injection and
asf-translation-files are closed; Build and Test summary added.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-16 12:01:29 +01:00
co-authored by Claude Sonnet 5.5
parent e7bae5edd7
commit db86332c1f
19 changed files with 209 additions and 45 deletions
+4 -3
View File
@@ -4,8 +4,8 @@ What must be true before the CMS-driven parts of the site go to production. Brya
## Before merging to master
- [ ] Revert the TEST ONLY commit `d449e76` and check `contactForm.enabled` is `false` ([deploy-and-ci.md](deploy-and-ci.md)).
- [ ] Merge order: `feature/contact-form-cms`, then `feature/asf-packages-cms`.
- [x] 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](deploy-and-ci.md)).
- [ ] Merge: the CMS PR first, then `feature/asf-packages-cms` (which carries the contact-form commits).
- [ ] The nightly test build only starts after the packages feature is on `master` (schedules run from the default branch).
## Packages and banners
@@ -18,7 +18,8 @@ What must be true before the CMS-driven parts of the site go to production. Brya
- [ ] 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`.
- [ ] 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`)