Adds the inception docs and design for the homepage sections

Refreshes the shared reverse engineering docs, adds the requirements,
application design and units for the homepage-sections feature, and
updates the static design: live prices and form fields, the new
Lieve woorden block and the coming-soon gate over the contact form.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-19 23:46:30 +02:00
co-authored by Claude Opus 5.5
parent 38c5c3e262
commit c81dcd3979
33 changed files with 2354 additions and 275 deletions
@@ -0,0 +1,52 @@
# Unit of Work Plan — homepage-sections
The decomposition itself is already decided: one unit per homepage block (user request), in the order approved in the execution plan, with the shared building blocks introduced by the first unit that needs them. This plan fixes the boundaries and asks how the units are delivered.
## Plan
- [x] 1. Answer the questions below
- [x] 2. Analyze answers for ambiguities (follow-up questions if needed)
- [x] 3. Generate `unit-of-work.md` — the six units, their scope (components, content, helpers, images, tests) and where shared pieces land
- [x] 4. Generate `unit-of-work-dependency.md` — dependency matrix and order
- [x] 5. Generate `unit-of-work-story-map.md` — no user stories were written, so this maps every requirement (FR-HP / NFR-HP) to its unit(s)
- [x] 6. Validate boundaries and dependencies; check that every requirement is assigned
## Already decided (no question needed)
| # | Unit | Brings in (besides the section itself) |
| --- | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1 | Lifestyle fotografie | `HomeSection`, `SectionHeading`, `Reveal` + `useReveal`, `ContentImage` and `HomeContent` types, `homeContent.ts`, image conventions (download, resize, dimensions) |
| 2 | Over mij | `FramedImage` |
| 3 | Prijzen | `PricingPackage`, `packages.ts`, `formatPrice`, `packageFromSearch`, `validateSearch` on `/` |
| 4 | Lieve woorden | `Testimonial`, `testimonials.ts`, `slideLabel`, Chakra Carousel styling |
| 5 | Contact | `ContactForm` + `ContactFormGate`, `contact/` types and adapter, `shootOptions`, `validateContact`, `toContactPayload`, `isLikelySpam`, `siteContent.contactForm`, field styling |
| 6 | Instagram | profile URL derived from `siteContent.socials` |
- Work happens on one branch, `feature/homepage-sections`, created before the first Code Generation.
- Each unit adds its section to `routes/index.tsx`, so the homepage grows unit by unit and is never broken in between.
---
## Questions
Vul per vraag de letter in na `[Answer]:`. Past geen enkele optie, kies dan de laatste (Anders) en licht toe. Waar ik een voorkeur heb staat **(aanbevolen)**.
## Vraag 1: Opleveren per unit of per feature
Een merge naar `master` gaat automatisch naar test.andreaslop.nl.
- A) **Eén pull request voor de hele feature.** Per unit één of meer commits op `feature/homepage-sections`; aan het eind één PR naar `master`. Test krijgt de homepage pas als hij af is. Een unit tussendoor op test bekijken kan via de handmatige run "Deploy to Test" op de branch. (aanbevolen)
- B) **Een pull request per unit.** Na elke unit een PR naar `master`, dus de homepage groeit stap voor stap op test. Meer PR's en CI-runs, maar kleinere reviews.
- X) Anders (beschrijf hieronder na de [Answer]:-tag)
[Answer]: A
## Vraag 2: Controle na elke unit
Elke unit wordt na het genereren automatisch gebouwd en getest. Hoe zwaar is die controle?
- A) **Volledige `pnpm check` per unit**, inclusief Lighthouse. Een unit met grote foto's die het performancebudget van de homepage overschrijdt, valt dan meteen op en niet pas aan het eind. Kost een paar minuten per unit. (aanbevolen)
- B) Lint, opmaak, tests en build per unit; Lighthouse alleen bij Build and Test
- X) Anders (beschrijf hieronder na de [Answer]:-tag)
[Answer]: A