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>
9.8 KiB
Execution Plan — Homepage Sections
Detailed Analysis Summary
Transformation Scope
- Transformation Type: Single component (application change inside
web/), plus the static design reference and LAYOUT.md - Primary Changes: six new homepage section components, a reusable contact form, shared section building blocks (section heading, scroll reveal), new content types and static content, new images
- Related Components:
routes/index.tsx,content/types.ts,content/*,lib/*,test/arbitraries.ts,design/andreaslop-static/index.html+style.css,LAYOUT.md
Change Impact Assessment
- User-facing changes: Yes — the homepage gains six sections below the hero
- Structural changes: No — the shell, routing and hosting stay the same
- Data model changes: Yes (front-end only) — new content interfaces (
PricingPackage,Testimonial,GalleryPhoto,InstagramContent, section texts) and the contact payload shape - API changes: No live API; the contact payload is designed for the future
POST /api/contact - NFR impact: Yes, contained — accessibility (carousel, form, overlay), performance (lazy images within the Lighthouse budget), security (no new third parties, CSP unchanged)
Component Relationships
graph LR
Home["routes/index.tsx"] --> Sections["New section components (6)"]
Sections --> Shared["Shared: SectionHeading, useReveal, LinkButton"]
Sections --> Content["content/ (types + static data)"]
Prices["Prijzen"] -->|"package list + preselect"| Contact["Contact form"]
Contact --> Lib["lib/ (validation, honeypot, time check)"]
Contact --> Site["siteContent.email"]
Design["design/andreaslop-static + LAYOUT.md"] -.->|"reference"| Sections
classDef route fill:#f6e05e,stroke:#c05621,stroke-width:1px,color:#000;
classDef comp fill:#63b3ed,stroke:#2b6cb0,stroke-width:1px,color:#000;
classDef data fill:#9ae6b4,stroke:#2f855a,stroke-width:1px,color:#000;
classDef ref fill:#e2e8f0,stroke:#4a5568,stroke-width:1px,stroke-dasharray:5 5,color:#000;
class Home route;
class Sections,Shared,Prices,Contact comp;
class Content,Lib,Site data;
class Design ref;
Text alternative: the home route renders six new sections that use shared building blocks and content data; Prijzen feeds the package list and preselection into the contact form, which uses pure helpers in lib/ and the site e-mail; the static design is the reference.
| Component | Change Type | Priority |
|---|---|---|
routes/index.tsx |
Minor (adds sections) | Critical |
| New section components | Major (new) | Critical |
content/types.ts, new content modules |
Minor (additive) | Critical |
lib/ new helpers |
Minor (additive) | Important |
design/andreaslop-static, LAYOUT.md |
Minor | Important (gate for React work) |
config/securityHeaders.ts |
None (unchanged) | — |
Risk Assessment
- Risk Level: Low — additive changes on one page, no infrastructure or dependency changes
- Rollback Complexity: Easy — revert the merge
- Testing Complexity: Moderate — carousel and form behaviour, overlay/inert, property-based tests for helpers, Lighthouse budget
Workflow Visualization
flowchart TD
Start(["User Request"])
subgraph INCEPTION["🔵 INCEPTION PHASE"]
WD["Workspace Detection<br/><b>COMPLETED</b>"]
RE["Reverse Engineering<br/><b>COMPLETED</b>"]
RA["Requirements Analysis<br/><b>COMPLETED</b>"]
US["User Stories<br/><b>SKIP</b>"]
WP["Workflow Planning<br/><b>IN PROGRESS</b>"]
AD["Application Design<br/>+ static design update<br/><b>EXECUTE</b>"]
UG["Units Generation<br/><b>EXECUTE</b>"]
end
subgraph CONSTRUCTION["🟢 CONSTRUCTION PHASE (per unit)"]
FD["Functional Design<br/><b>EXECUTE for Prijzen, Lieve woorden, Contact</b>"]
NFRA["NFR Requirements<br/><b>SKIP</b>"]
NFRD["NFR Design<br/><b>SKIP</b>"]
ID["Infrastructure Design<br/><b>SKIP</b>"]
CG["Code Generation<br/>(Planning + Generation)<br/><b>EXECUTE</b>"]
BT["Build and Test<br/><b>EXECUTE</b>"]
end
Start --> WD
WD --> RE
RE --> RA
RA -.-> US
RA --> WP
WP --> AD
AD --> UG
UG --> FD
FD --> CG
UG --> CG
CG -.->|"next unit"| FD
CG --> BT
BT --> End(["Complete (Operations decided at Build and Test)"])
style WD fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
style RE fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
style RA fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
style WP fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
style CG fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
style BT fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
style US fill:#BDBDBD,stroke:#424242,stroke-width:2px,stroke-dasharray: 5 5,color:#000
style NFRA fill:#BDBDBD,stroke:#424242,stroke-width:2px,stroke-dasharray: 5 5,color:#000
style NFRD fill:#BDBDBD,stroke:#424242,stroke-width:2px,stroke-dasharray: 5 5,color:#000
style ID fill:#BDBDBD,stroke:#424242,stroke-width:2px,stroke-dasharray: 5 5,color:#000
style AD fill:#FFA726,stroke:#E65100,stroke-width:3px,stroke-dasharray: 5 5,color:#000
style UG fill:#FFA726,stroke:#E65100,stroke-width:3px,stroke-dasharray: 5 5,color:#000
style FD fill:#FFA726,stroke:#E65100,stroke-width:3px,stroke-dasharray: 5 5,color:#000
style INCEPTION fill:#BBDEFB,stroke:#1565C0,stroke-width:3px,color:#000
style CONSTRUCTION fill:#C8E6C9,stroke:#2E7D32,stroke-width:3px,color:#000
style Start fill:#CE93D8,stroke:#6A1B9A,stroke-width:3px,color:#000
style End fill:#CE93D8,stroke:#6A1B9A,stroke-width:3px,color:#000
linkStyle default stroke:#333,stroke-width:2px
Text alternative: Inception runs Application Design (including the static design update) and Units Generation, skipping User Stories; Construction loops per unit through Functional Design (only for Prijzen, Lieve woorden and Contact) and Code Generation, skipping the NFR and Infrastructure stages, then Build and Test; Operations is omitted until decided at Build and Test.
Phases to Execute
🔵 INCEPTION PHASE
- Workspace Detection (COMPLETED)
- Reverse Engineering (COMPLETED — refresh)
- Requirements Analysis (COMPLETED)
- User Stories (SKIPPED — single visitor persona, concrete requirements)
- Execution Plan (IN PROGRESS)
- Application Design — EXECUTE
- Rationale: new components (six sections, reusable ContactForm, testimonial carousel, SectionHeading,
useReveal), new content interfaces and one cross-section interaction (Prijzen → Contact preselection). This stage also delivers FR-HP-01: the Lieve woorden design and the live content indesign/andreaslop-staticplus the updated LAYOUT.md, so the design can be reviewed in the browser before any React work.
- Rationale: new components (six sections, reusable ContactForm, testimonial carousel, SectionHeading,
- Units Generation — EXECUTE
- Rationale: the user asked for one unit per block; this stage fixes the six units, their order and dependencies, and where the shared building blocks land.
🟢 CONSTRUCTION PHASE
Proposed unit order: 1 Lifestyle fotografie (also introduces the shared SectionHeading, useReveal and image conventions) → 2 Over mij → 3 Prijzen → 4 Lieve woorden → 5 Contact (needs the package list from Prijzen) → 6 Instagram.
- Functional Design — EXECUTE for Prijzen, Lieve woorden and Contact; SKIP for Lifestyle fotografie, Over mij and Instagram
- Rationale: those three contain logic (package → shoot options and preselection; carousel index and announcements; validation, honeypot, time check, overlay/toggle, submit states) and need PBT-01 property identification. The other three are presentational: content + layout already defined by the design and the application design.
- NFR Requirements — SKIP
- Rationale: NFRs are fully set at requirements level (NFR-HP-01…06); the tech stack is fixed and no new dependencies are added.
- NFR Design — SKIP
- Rationale: no new NFR patterns beyond what Functional Design and the code plans cover (inert overlay, lazy images, reduced motion).
- Infrastructure Design — SKIP
- Rationale: no infrastructure changes; the CSP and server configs stay unchanged.
- Code Generation — EXECUTE (ALWAYS), per unit
- Build and Test — EXECUTE (ALWAYS)
🟡 OPERATIONS PHASE
- Deployment Setup, Monitoring Setup, Production Readiness Validation — UNDECIDED
- Rationale: Operations Configuration = Undecided; asked again at Build and Test. The existing pipeline already deploys to test on merge to master.
Package Change Sequence
Single package (web/). Sequence inside it: static design + LAYOUT.md (Application Design) → shared building blocks (unit 1) → units 2–6 in order. Feature branch feature/homepage-sections, created before the first Code Generation.
Estimated Timeline
- Total Stages to execute: Application Design, Units Generation, 3× Functional Design, 6× Code Generation, Build and Test
- Estimated Duration: several working sessions; one unit per session is a comfortable pace
Success Criteria
- Primary Goal: the homepage shows all six sections below the hero, matching the (updated) design, with live-site content
- Key Deliverables: updated static design + LAYOUT.md; six section components; reusable ContactForm with overlay, validation and browser-side anti-spam; content modules; images; tests
- Quality Gates:
pnpm checkgreen (lint, format, tests incl. PBT and axe, build, audits, Lighthouse: accessibility/best practices 1.0, home mobile performance ≥ 0.8); Security Baseline and PBT compliance per stage; CI green on the PR - Integration Testing: home route renders all sections in order; "Boek je shoot" → contact preselection works across sections