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

2.5 KiB

Application Design — redesign-modern-timetravel (consolidated)

Details: components.md · component-methods.md · services.md · component-dependency.md · contact-api-contract.md

Decisions (user, 2026-11-09)

# Decision Source
D1 Shared layer (content, data hooks, form logic) + separate presentation for B and E; E lazy-loaded Design Q1-A
D2 Variant is app state only, not in the URL, not persisted; every visit starts in B Design Q2-A, Req Q3-A
D3 Headless form logic is written first in this repo in a movable folder src/cms-client/, then handed over to SlpModularCms Design Q3-B
D4 One frontend package cms-client with separately importable parts (subpaths); offerings moves in later Follow-up decision
D5 API module Contact/Forms in SlpModularCms built by SLS Software - CMS Req Q10-A/Q11-B
D6 Mode (light/dark) follows system preference, overridable and persisted Req Q5-B

Architecture overview

graph LR
    subgraph FE[slp-software-frontend]
      TP[ThemeProvider variant x mode] --> VR[VariantRenderer]
      VR --> B[Variant B eager]
      VR -.lazy.-> E[Variant E chunk]
      B --> S[shared logic]
      E --> S
      B --> CC[src/cms-client movable]
      E --> CC
    end
    CC --> API[SlpModularCms API: Contact/Forms module and Offerings category]
    S --> API
    classDef fe fill:#63b3ed,stroke:#2b6cb0,color:#000;
    classDef pkg fill:#f6e05e,stroke:#c05621,color:#000;
    classDef ext fill:#9ae6b4,stroke:#2f855a,color:#000;
    class TP,VR,B,E,S fe;
    class CC pkg;
    class API ext;

Text alternative: the theme provider drives a variant renderer that shows eager B or lazy E; both use shared logic and the movable cms-client folder, which talks to the CMS API.

Design validation

  • Requirements coverage: FR-1..FR-6 (theme, variants, nav buttons, mode rules) → ThemeProvider, ModeToggle, VariantToggle, VariantRenderer, LandingB/E. FR-7..FR-12 (packages) → usePackagesQuery/usePackageFilter/useSwipeRow + PackagesB/E. FR-13..FR-19 (form) → cms-client/contact, form skins, contract. NFR-1..8 → usePrefersReducedMotion, code split, boundary lint rule, scrubbing, tests.
  • Consistency: all component names in methods/dependency docs exist in components.md; contract field names equal the hook payload.
  • Open items are listed in contact-api-contract.md § 9 and are owned by the CMS sessions.