Files
SluijsensandClaude Sonnet 5.5 1047c738b5 AI-DLC: inception en ontwerp voor redesign B/E met contactformulier
Requirements, application design (incl. concept-API-contract voor het contactformulier), units en functional design voor U1.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-09 21:06:25 +01:00

43 lines
2.2 KiB
Markdown

# Application Design Plan — redesign-modern-timetravel
## Steps
- [x] Analyze context (requirements.md, execution-plan.md, RE artifacts, replies from SLS Software - CMS and CMS & API)
- [x] Resolve design questions (asked interactively in chat at the user's request, answers below)
- [x] Generate components.md
- [x] Generate component-methods.md
- [x] Generate services.md
- [x] Generate component-dependency.md
- [x] Generate contact-api-contract.md (draft contract for the CMS sessions)
- [x] Generate application-design.md (consolidated)
- [x] Validate design completeness and consistency
## Design Questions and Answers (asked interactively, 2026-11-09)
## Question 1 — How do B and E share content and logic?
- A) Shared layer + separate presentation per variant (E lazy-loaded)
- B) Two fully separate component trees
- C) One component set, variant via CSS only
- X) Other
[Answer]: A
## Question 2 — Is the variant visible in the URL?
- A) App state only; always start in B; E stays a surprise
- B) Shareable link to E (e.g. `/#/?v=tijdreis`); still not remembered
- X) Other
[Answer]: A
## Question 3 — How is the form UI built before the cms-client package exists?
- A) Contract adapter + mock; replace when the CMS repo delivers the package
- B) Pre-build the headless form logic here (based on the ASF form), then hand over to the CMS repo
- C) Wait for the package (start U4 later)
- X) Other
[Answer]: B
## Decisions derived from the answers
- Q1-A: shared `content`, data hooks and form logic; per-variant presentational components under `src/variants/b` and `src/variants/e`; `React.lazy` boundary for E.
- Q2-A: variant lives only in React context; no URL parameter; not persisted. Only the mode (light/dark) is persisted.
- Q3-B: the headless form logic is written **in this repo** inside a self-contained folder `src/cms-client/` (subpaths `contact/`, later `offerings/`), with an enforced import boundary (it may not import from the rest of the app), so it can be moved to SlpModularCms as the package `cms-client` without rewriting. `SLS Software - CMS` builds the API module and takes over the package afterwards; the API contract in `contact-api-contract.md` is the shared source of truth until then.