Author SHA1 Message Date
SluijsensandClaude Sonnet 5.5 9433ec4285 Docs: privacy statement may move to JSON in the IIS pipeline feature
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-17 22:45:50 +01:00
Sluijsens 440a298cc7 Hero: no pause on hover, slow zoom on the first photo
Continuous Integration / check (push) Successful in 2m4s
Continuous Integration / build-test (push) Successful in 1m1s
Continuous Integration / deploy-test (push) Successful in 1m17s
Continuous Integration / lighthouse (push) Successful in 9m10s
Continuous Integration / deploy-production (push) Skipped
2026-11-17 11:17:47 +01:00
+1
View File
@@ -42,6 +42,7 @@ 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).
- Privacy statement as JSON (Bryan, 2026-11-17): `web/src/content/privacyContent.ts` may become a JSON file, but not now. Do it in the feature that sets up the production pipeline on IIS, together with the text itself (the `[OPEN:]` points, the captcha paragraph, the final wording). Keep the `PLACEHOLDER_MARK` check (`unresolvedPlaceholders()`), the captcha section (`onlyWithCaptcha`) and their tests. Put this in the plan of that feature.
- 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.