Pakketblok: elk aantal pakketten, filterchips, swipe-rij op mobiel en optionele banner

Pure logica (splitsen, chips, filter, labels), useSwipeRow en usePackageFilter,
ContactPreselect voor het formulier, kaarten in stijl B en tests.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-10 10:34:09 +01:00
co-authored by Claude Sonnet 5.5
parent e1d950cd33
commit 9661b64635
28 changed files with 1353 additions and 137 deletions
@@ -586,3 +586,63 @@
**Context**: CMS phase 2 unblocked pending the merge; U2 Code Generation starts.
---
## U2 Code Generation Complete
**Timestamp**: 2026-11-10T11:00:00Z
**User Input**: "Approve plan."
**AI Response**: "Executed all 9 steps of b-modern-sections-code-generation-plan.md. Tests 10 files/56 tests before, 13 files/122 tests after, all passed; lint 0 errors (2 pre-existing warnings); build OK, Sora/Instrument Sans removed from dist. Code commit on feature/redesign-modern-timetravel, no push. Deviations flagged in construction/b-modern-sections/code/summary.md (display headline from the design, panel filler text, no browser screenshots possible)."
**Context**: Code Generation U2 complete; awaiting the user's approval before U3.
---
## Correction: ASF Branch Merge NOT Authorized
**Timestamp**: 2026-11-10T11:30:00Z
**User Input**: "(cross-session message from CMS & API relaying Bryan's correction: feature/identity-email-notifications may NOT go to master yet; Bryan wants to test first; a merge follows only after his explicit go; a merge on Bryan's behalf is only passed on if he says so himself)"
**AI Response**: "Earlier today the AI read the user's remark 'ik denk dat de cms sessie ook wel kan mergen ...' as authorization to merge and relayed it to AndreaSlopFotografie, the builder and CMS & API. That was a misreading. Retracted to AndreaSlopFotografie and to the builder (SLS Software - CMS): no merge, no rebase, no phase 2; builder stays on stand-by. No merge had taken place. Lesson: ask for explicit confirmation before relaying an action as a decision when the wording is ambiguous."
**Context**: CMS phase 2 remains blocked on Bryan's explicit go.
---
## U2 Approved; U3 Functional Design Question Answered
**Timestamp**: 2026-11-10T12:30:00Z
**User Input**: "Akkoord, ga naar u3" / "Ik wil beide methoden kunnen gebruiken. Ik denk namelijk dat ik bij SLP Software begin met de op maat aanpak als p0akket, maar deze methode is voor Andrea Slop Fotografie mogelijk wel handig."
**AI Response**: "U2 approved, starting U3 (packages-block) Functional Design. Banner question: both presentations must be possible. Decision: a package can be shown as a normal card or as the black 'Past er niets bij?' banner under the cards, chosen per site by a frontend setting (bannerSlugs in content.ts, empty for SLP: Maatwerk stays a card); a later additive API field (layout: card|banner, CMS extension, not now) can take over the choice per offering. Chips from 4 packages are independent of the banner."
**Context**: Functional Design U3.
---
## U3 Functional Design Complete
**Timestamp**: 2026-11-10T13:10:00Z
**User Input**: "(none)"
**AI Response**: "Generated packages-block-functional-design-plan.md, packages-block-fd-questions.md and construction/packages-block/functional-design/{domain-entities, business-rules (BR-U3-1..12), business-logic-model, frontend-components}.md with Mermaid diagrams. Key decisions: any number of packages; banner vs card chosen per site by packagesSettings.bannerSlugs (empty for SLP so Maatwerk stays a card; fallback banner texts; later additive API field layout); chips from 4 card packages with categories; swipe row below sm with snap, dots as buttons, featured scrolled into view; skeleton/error with retry/empty states; CTA sets preselect (slug, key) and scrolls to #contact. Completion message presented; awaiting approval."
**Context**: Functional Design U3 complete; next is Code Generation plan for U3.
---
## U3 Functional Design Approved; Code Generation Plan Ready
**Timestamp**: 2026-11-10T13:30:00Z
**User Input**: "ga verder"
**AI Response**: "U3 Functional Design approved. Created construction/plans/packages-block-code-generation-plan.md (7 steps). Plan approval prompt presented."
**Context**: Code Generation Part 1 for U3.
---