Adds the feature's inception documents (requirements, execution plan, application design), the code generation plan and summary of unit 1, its state and audit log, and its row in the active features list. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
12 KiB
Execution Plan — Soorten fotoshoots Page
Detailed Analysis Summary
Transformation Scope (Brownfield)
- Transformation Type: Single component (
web/), application-level only - Primary Changes: replace the
/soorten-fotoshootsplaceholder with the real page (five shoot blocks, closing call to action); a new shoot-types content list; areverseoption on the sharedMediaText; a new sharedCallToAction; an anchor on the homepage pricing section; a shared service area for the structured data; page-specific SEO (indexing, description,WebPage+ItemListofServiceJSON-LD, own preview image) - Related Components:
web/src/routes/soorten-fotoshoots.tsx,web/src/components/{MediaText,CallToAction (new),home/Pricing},web/src/content/{shootTypes.ts (new),siteContent.ts,types.ts},web/src/seo.ts,web/src/sitePages.ts,web/lighthouserc*.cjs,web/public/,web/src/assets/shoots/(new), LAYOUT.md
Change Impact Assessment
- User-facing changes: Yes. A new page; the homepage gets an invisible anchor on the pricing section; homepage and Over mij must otherwise look and behave exactly as before
- Structural changes: Minor. One new shared component, one backwards-compatible option on an existing one; no architectural change
- Data model changes: Yes (small). New
ShootTypetype with optionalpackageId; newserviceAreafield inSiteContent - API changes: No external API;
MediaTextgets an optional prop - NFR impact: Yes. SEO (indexed, structured data,
areaServedof the business changes on every page), accessibility (article structure, five similar links with distinct accessible names), performance (five new photos; Lighthouse budget 0.9)
Component Relationships
graph TD
Route["routes/soorten-fotoshoots.tsx"] --> PageIntro["PageIntro (existing)"]
Route --> PageSection["PageSection (existing)"]
Route --> MediaText["MediaText (+ reverse option)"]
Route --> Cta["CallToAction (new, shared)"]
Route --> Shoots["content/shootTypes.ts (new)"]
Shoots --> Packages["content/packages.ts (existing ids)"]
Shoots --> Assets["assets/shoots/ (new photos)"]
Route --> Seo["seo.ts + sitePages.ts"]
Seo --> Site["content/siteContent.ts (+ serviceArea)"]
Seo --> Lhci["lighthouserc*.cjs (indexed paths)"]
Cta --> Pricing["home/Pricing (+ id prijzen)"]
About["home/AboutBlock + about/AboutIntro"] --> MediaText
classDef newpart fill:#FFA726,stroke:#E65100,stroke-width:1px,color:#000;
classDef changed fill:#63b3ed,stroke:#2b6cb0,stroke-width:1px,color:#000;
classDef existing fill:#e2e8f0,stroke:#4a5568,stroke-width:1px,color:#000;
class Route,Cta,Shoots,Assets newpart;
class MediaText,Seo,Site,Lhci,Pricing changed;
class PageIntro,PageSection,Packages,About existing;
Text alternative: the new route composes PageIntro, PageSection, MediaText (new reverse option) and the new CallToAction from the new shoot-types content (which refers to package ids and new photos); SEO uses the extended site content and Lighthouse config; the call to action links to the pricing section, which gets an anchor; the existing MediaText callers stay unchanged.
- Primary Component:
web(front-end SPA) - Shared Components:
MediaText(Minor, optional prop),CallToAction(new),seo.ts(Minor:areaServedfromserviceArea, new page JSON-LD),siteContent/types.ts(Minor, new fields) - Dependent Components: homepage
AboutBlock, Over mijAboutIntro(must render unchanged); every page's business JSON-LD (newareaServed) - Supporting Components: Lighthouse CI config (Configuration-only), LAYOUT.md (documentation)
Parallel Feature Coordination
- contact-page owns the generic
webPage()helper inseo.ts. Unit 2 needs it for the JSON-LD. If it does not exist yet when unit 2 starts, this feature asks contact-page whether to add it to the agreed signature itself (contact-page then rebases on it). - Commits for others: the shoot photos plus
shootTypes.tsgo in an assets/content-only commit (hash to portfolio-page);serviceArea+professionalServicego in a small separate commit (hash to contact-page). - Hot files (
sitePages.ts,lighthouserc*.cjs,active-features.md): own entries only.
Risk Assessment
- Risk Level: Low
- Rollback Complexity: Easy (one branch, small separate commits)
- Testing Complexity: Simple. Existing component and route tests guard the homepage and Over mij; new page tests, PBT for link derivation and structured data, and Lighthouse cover the page
Workflow Visualization
flowchart TD
Start(["User Request"])
subgraph INCEPTION["🔵 INCEPTION PHASE"]
WD["Workspace Detection<br/><b>COMPLETED</b>"]
RE["Reverse Engineering<br/><b>SKIP</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/><b>EXECUTE</b>"]
UG["Units Generation<br/><b>SKIP</b>"]
end
subgraph CONSTRUCTION["🟢 CONSTRUCTION PHASE"]
FD["Functional Design<br/><b>EXECUTE (unit 2)</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 --> RA
RA --> WP
WP --> AD
AD --> FD
FD --> CG
CG --> BT
BT --> End(["Complete"])
style WD 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 AD 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 RE fill:#BDBDBD,stroke:#424242,stroke-width:2px,stroke-dasharray: 5 5,color:#000
style US fill:#BDBDBD,stroke:#424242,stroke-width:2px,stroke-dasharray: 5 5,color:#000
style UG 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 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: completed Workspace Detection and Requirements Analysis lead to Workflow Planning, then Application Design, Functional Design (unit 2 only), Code Generation per unit and Build and Test; Reverse Engineering, User Stories, Units Generation, NFR Requirements, NFR Design, Infrastructure Design and the Operations phase are skipped.
Phases to Execute
🔵 INCEPTION PHASE
- Workspace Detection (COMPLETED)
- Reverse Engineering (SKIPPED)
- Rationale:
_shared/reverse-engineering/already covers the over-mij blocks; per team agreement only this feature's own lines are updated (during Code Generation)
- Rationale:
- Requirements Analysis (COMPLETED)
- User Stories (SKIPPED)
- Rationale: one persona (the visitor), concrete FRs with exact texts and link targets; stories would restate the requirements
- Execution Plan (IN PROGRESS)
- Application Design - EXECUTE (minimal depth)
- Rationale: a new shared component (
CallToAction) and a new option on a shared one (MediaTextreverse) need agreed props before code, plus theShootTypemodel, where the contact-link derivation lives, and how the page JSON-LD builds onwebPage()andserviceArea
- Rationale: a new shared component (
- Units Generation - SKIP
- Rationale: the split is obvious and fixed below (two units)
🟢 CONSTRUCTION PHASE
- Functional Design - EXECUTE for unit 2 only (minimal depth)
- Rationale: the link derivation and the structured data have rules (known routes only,
?pakket=only with existing ids, oneServiceper shoot in order, no e-mail, sharedareaServed) and PBT-01 requires their properties to be identified in design. Unit 1 has nothing to design beyond Application Design
- Rationale: the link derivation and the structured data have rules (known routes only,
- NFR Requirements - SKIP
- Rationale: NFRs are set at requirements level (NFR-SF-01..07) and the stack is fixed
- NFR Design - SKIP
- Rationale: no new NFR patterns; existing ones (DeferredImage, Reveal, theme focus ring, jsonLdScript, packageFromSearch) are reused
- Infrastructure Design - SKIP
- Rationale: static assets only; no server config, CSP or deployment changes
- Code Generation - EXECUTE (ALWAYS, per unit)
- Rationale: implementation and tests
- Build and Test - EXECUTE (ALWAYS)
- Rationale: full
pnpm checkincl. Lighthouse for/,/over-mijand/soorten-fotoshoots
- Rationale: full
🟡 OPERATIONS PHASE
- Deployment Setup, Monitoring Setup, Production Readiness Validation - SKIP
- Rationale: Operations Configuration = No (decided at Requirements Analysis); the existing pipeline deploys to test
Units of Work (in order)
| # | Unit | Scope | Requirements |
|---|---|---|---|
| 1 | Shared blocks and content | MediaText reverse option (existing callers unchanged); new shared CallToAction; id="prijzen" on the homepage pricing section; shoot photos (download, resize, alt texts) + ShootType + content/shootTypes.ts (assets/content-only commit for portfolio-page); serviceArea in siteContent and areaServed in professionalService (separate commit for contact-page) |
FR-SF-03 (anchor), FR-SF-06, FR-SF-07, SEO-SF-03 (service area), NFR-SF-02, NFR-SF-06 |
| 2 | Soorten fotoshoots page | Page composition (intro, five shoot blocks, call to action); contact-link derivation; JSON-LD WebPage + ItemList of Service via webPage(); indexed, description, preview image, Lighthouse indexed paths; LAYOUT.md; delta lines in _shared/reverse-engineering/ |
FR-SF-01..05, FR-SF-08, SEO-SF-01..05, NFR-SF-01, 03..05, 07 |
Unit 1 goes first because unit 2 builds on its components and content, and because its two separate commits unblock the parallel features early. Each unit: full pnpm check (incl. Lighthouse) before its completion message; one PR to master at the end.
Estimated Timeline
- Total Stages to execute from here: 5 (Application Design, Functional Design for unit 2, Code Generation ×2 units, Build and Test)
- Estimated Duration: one to two working sessions, plus waiting time on
webPage()from contact-page if unit 2 gets there first
Success Criteria
- Primary Goal: a finished, indexed Soorten fotoshoots page that matches the design with the live texts and the new Gezin block
- Key Deliverables:
/soorten-fotoshootspage;CallToAction;MediaTextreverse;shootTypes.tsand five resized photos;serviceArea; page JSON-LD with tests; a 1200×630 preview image; updated LAYOUT.md and Lighthouse config - Quality Gates:
pnpm checkpasses (lint, format, tests with coverage thresholds, build, audits, Lighthouse: accessibility 1.0, best practices 1.0, performance ≥ 0.9 for/soorten-fotoshoots, other budgets unchanged); axe clean; homepage and Over mij output unchanged apart from the pricing anchor - Integration Testing: route tests render
/soorten-fotoshootsin the shell; links to/?pakket=…#contactpreselect the package and land on the contact section;/#prijzenlands on the pricing section below the fixed header