Adds the contact-form-cms feature docs (requirements, execution plan, functional and infrastructure design, code generation plan) and an optional Vite dev proxy for /api through API_PROXY_TARGET. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
1.7 KiB
1.7 KiB
Requirements clarification: contact-form-cms
Questions were asked interactively in chat (project agreement); answers recorded here afterwards. Open follow-up questions are routed through the session "SLP Software - SLS - Main" (Bryan's instruction, 2026-11-10).
Question 1: Security Baseline extension
- A) Yes, enforce
- B) No
Question 2: Property-based testing extension
- A) Full
- B) Partial (pure functions and round-trips)
- C) No
Question 3: Operations phase
- A) Yes, include now
- B) Decide later
- C) No
Question 4: Relation between the cms-client package and the existing ASF form
- A) Package replaces state and validation; the existing ContactForm UI stays and uses useContactForm
- B) Package only for sending
Question 5: Subject
- A) Select value (id) is the subject
- B) Free text
- X) Other
Answer: X - The human-readable label ("Newborn shoot", "Overig") is sent as subject; the id stays local for the ?pakket= preselect. (Decision by Bryan, relayed by SLP Software - SLS - Main)
Question 6: Robot check
- A) None now
- B) Friendly Captcha now
- X) Other
Answer: B - Build Friendly Captcha now (Bryan via SLP Software - SLS - Main). Package gets a captcha slot (SLS-Main), server verifier by SLS Software - CMS, widget + CSP + privacy text by this feature.
Question 7: Form unavailable
- A) Mailto block instead of "Binnenkort"
- B) Keep the dimmed "Binnenkort" view
- X) Other
Answer: B - Keep the existing dimmed "Binnenkort" gate (Bryan).
Question 8: Testing against the server
- A) Mocks in CI + manual check against the temporary environment
- B) Mocks only