Records unit 1 of the Soorten fotoshoots page as generated

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>
This commit is contained in:
2026-10-25 08:26:06 +01:00
co-authored by Claude Opus 5.5
parent 6cf909564b
commit 166e5d32bb
15 changed files with 1366 additions and 0 deletions
@@ -0,0 +1,88 @@
# AI-DLC State Tracking
## Project Information
- **Feature Name**: Soorten fotoshoots page (`/soorten-fotoshoots`)
- **Feature Slug**: soorten-fotoshoots-page
- **Project Type**: Brownfield
- **Start Date**: 2026-10-24T19:30:00Z
- **Current Stage**: CONSTRUCTION - Code Generation unit 1 Shared blocks and content (generated, awaiting approval)
- **Branch**: feature/soorten-fotoshoots-page (fast-forwarded to master 11a5224 after over-mij-page merged, PR #7)
- **Worktree**: K:\Development\SlpSoftware\Projects\AndreaSlopFotografie-soorten-fotoshoots
## Workspace State
- **Existing Code**: Yes
- **Programming Languages**: TypeScript (React/TSX)
- **Build System**: pnpm + Vite (`tsc && vite build`), Gitea Actions CI
- **Project Structure**: Single front-end SPA in `web/`; static HTML design reference in `design/andreaslop-static/`; `api/` folder present but empty (.NET back-end planned)
- **Reverse Engineering Needed**: No (artifacts in `_shared/` already include the over-mij shared blocks as of e152153; per team agreement only the lines about this feature's own route/components are updated, no full refresh)
- **Workspace Root**: K:\Development\SlpSoftware\Projects\AndreaSlopFotografie-soorten-fotoshoots
## Code Location Rules
- **Application Code**: Workspace root (NEVER in aidlc-docs/) — front-end lives in `web/`
- **Feature Documentation**: aidlc-docs/features/soorten-fotoshoots-page/ only
- **Shared Artifacts**: aidlc-docs/_shared/
- **Structure patterns**: See code-generation.md Critical Rules
## Language Configuration
- **Documentation Language**: English
- **Conversation Language**: User Language (Dutch)
- **Source**: inherited from aidlc-docs/language-preference.md (answer A); user may override
## Parallel Work Agreements
Agreed with the parallel sessions (contact-page, portfolio-page, over-mij-page) on 2026-10-24:
- One worktree per feature; nobody switches branches in a shared checkout
- No full RE refresh; each feature updates only its own lines in `_shared/reverse-engineering/`
- Hot files (`sitePages.ts`, `lighthouserc.cjs`, `active-features.md`): own entry/row only
- `seo.ts`: contact-page owns a generic `webPage(type: WebPageType, path, extra)` helper (separate commit, cherry-picked by the others); this feature builds its JSON-LD on it, no own `xxxPage()`
- `PageIntro` is used by everyone: message the others before changing it
- Claims of this feature: `content/shootTypes.ts`, shared `CallToAction` band, backwards-compatible `reverse` prop on `MediaText`
- contact-page does not touch `Pricing.tsx`; an `id="prijzen"` anchor there is fine with it. Until its `/contact?onderwerp=` format is final, shoot links use `/#contact` (with `?pakket=` where a package exists)
- Each entry in `shootTypes.ts` gets a `slug` plus an optional `packageId` (a `packages.ts` id), so the links work with either option contact-page is still deciding on: `/contact?pakket=<packageId>` (its recommendation) or `/contact?onderwerp=<slug>`
- Photos: this feature owns the shoot photos in `web/src/assets/shoots/`; portfolio-page uses none of them (no overlap) and processes its own 10 photos into `web/src/assets/portfolio/`
- `shootTypes.ts` is also used by portfolio-page (filters per shoot type, lightbox captions). Agreed shape `{ id: ShootTypeId; name; shootLabel; paragraphs; image; packageId? }`, ids `newborn | zwangerschap | gezin | loveshoot | portret` stay stable. Delivered as the **first commit of unit 1** (types + shootTypes.ts + assets/shoots/), hash goes to portfolio-page, which cherry-picks it
- Possible extra (pending both users): portfolio filter in the URL `/portfolio?shoot=<id>`, so shoot blocks could link to "Bekijk meer …foto's". New scope for this page, put it to the user once portfolio-page confirms
- contact-page's final preselect format: `/contact?pakket=<packageId>` (unknown values ignored; shoot types without `packageId` link to plain `/contact`)
- Shared service area (`areaServed`) in `siteContent` and its use in `professionalService`: owned by this feature, in a separate small commit (siteContent + seo.ts + tests). No waiting on each other: different functions in `seo.ts`, so whoever commits first sends the hash and the other rebases on top. contact-page follows the approved wording (send it once the user approves)
- If this feature reaches Code Generation before contact-page's `webPage()` commit exists: ask contact-page first whether this feature should add `webPage()` exactly to the agreed signature (then contact-page rebases on it), rather than writing a page-specific function
- contact-page also changes `content/types.ts` and `siteContent.ts` (its unit 2): `SocialLink.label?`, `SiteContent.contactForm = { enabled, replyTime }`. Different fields from `serviceArea`; whoever commits second resolves the small textual conflict
- Lighthouse (`pnpm check`, preview on port 4173 `--strictPort`): send "claim 4173" to the other sessions before starting and "4173 free" when done; no heavy runs (full vitest with coverage, build) while someone else's Lighthouse runs
- Claims of others: contact-page — ContactForm generalisation, contact-details block, `/contact?onderwerp=` (pending its user's decision); portfolio-page — PortfolioGrid, Lightbox, InstagramGrid move to shared
- over-mij-page sends the merge commit once merged; all stacked features then rebase onto master
## Extension Configuration
| Extension | Enabled | Decided At |
|---|---|---|
| Security Baseline | Yes | Requirements Analysis |
| Property-Based Testing | Yes (full enforcement) | Requirements Analysis |
## Operations Configuration
- **Include Operations Phase**: No
- **Decided At**: Requirements Analysis
## Stage Progress
### 🔵 INCEPTION PHASE
- [x] Workspace Detection
- [x] Reverse Engineering - SKIP (shared artifacts current; delta lines only)
- [x] Requirements Analysis (approved)
- [x] User Stories - SKIP
- [x] Workflow Planning (approved)
- [x] Application Design - EXECUTE (minimal) — approved
- [x] Units Generation - SKIP
### 🟢 CONSTRUCTION PHASE
- [ ] Functional Design - EXECUTE (unit 2) / SKIP (unit 1)
- [x] NFR Requirements - SKIP
- [x] NFR Design - SKIP
- [x] Infrastructure Design - SKIP
- [~] Code Generation - EXECUTE (per unit): 1 Shared blocks and content (generated, commits eb23536 / befe97a / 6cf9095, awaiting approval) → 2 Soorten fotoshoots page
- [ ] Build and Test - EXECUTE
### 🟡 OPERATIONS PHASE
- [x] Deployment Setup, Monitoring Setup, Production Readiness Validation - SKIP (Operations = No)
## Execution Plan Summary
- **Stages to Execute**: Application Design (minimal), Functional Design (unit 2 only), Code Generation (2 units), Build and Test
- **Stages to Skip**: Reverse Engineering (shared artifacts current), User Stories (single persona, concrete FRs), Units Generation (split fixed in the plan), Functional Design for unit 1, NFR Requirements and NFR Design (set at requirements level), Infrastructure Design (static assets only), Operations (decided No)
- **Units**: 1 Shared blocks and content → 2 Soorten fotoshoots page
- **Delivery**: branch feature/soorten-fotoshoots-page, separate commits for portfolio-page (assets/content) and contact-page (service area), full `pnpm check` per unit, one PR at the end
@@ -0,0 +1,181 @@
# AI-DLC Audit Log — soorten-fotoshoots-page
## Initial User Request
**Timestamp**: 2026-10-24T19:30:00Z
**User Input**: "Ik wil een nieuwe feature starten voor het bouwen van de \"Soorten Fotoshoots\" pagina. Wederom met aandacht voor SEO, accessibility en reusability van code elementen, chakra en theming. Net zoals voorgaande feature."
**AI Response**: "Started AI-DLC workflow (existing multi-feature workspace). Classified as Feature. over-mij-page was still in Build and Test and unmerged; saved a feature-selection prompt (now inception/feature-selection.md)."
**Context**: INCEPTION - Workspace Detection (start, feature resolution)
---
## Feature Resolution
**Timestamp**: 2026-10-24T19:35:00Z
**User Input**: "B"
**AI Response**: "Created branch feature/soorten-fotoshoots-page from feature/over-mij-page (ae769cb). Detected that other sessions (portfolio-page, contact-page) were working in the same checkout; the branch switch had moved HEAD away from feature/contact-page. Restored the main checkout to feature/contact-page (nothing committed in between) and moved this feature into its own worktree K:\\Development\\SlpSoftware\\Projects\\AndreaSlopFotografie-soorten-fotoshoots. Asked the user how to proceed (wait for RE from portfolio / own refresh / pause)."
**Context**: INCEPTION - Workspace Detection (branch + worktree)
---
## Coordination With Parallel Features
**Timestamp**: 2026-10-24T19:41:00Z
**User Input**: "kan je niet verde rin eeen worktree en zorgen dat je die update zodra over mij klaar is? Ik heb meerdere features gestart omdat ik die tegelijk wilden gaan oppakken. Kan je daarmee werken? OM wel te zorgen dat er geen dubbel werk gedaan wordt? Alsof je met teamgenoten praat?"
**AI Response**: "Continued in the worktree. Coordinated with the parallel sessions via cross-session messages (see aidlc-state.md § Parallel Work Agreements): no full RE refresh, own entries only in hot files, contact-page's generic webPage() helper for JSON-LD, claims per feature. over-mij-page will message the merge commit; this branch then rebases onto master. Verified that _shared/reverse-engineering already covers the over-mij blocks (MediaText, PhotoDuo, PageSection in component-inventory/code-structure, last changed in e152153), so Reverse Engineering is skipped. Language configuration inherited (English docs, Dutch conversation)."
**Context**: INCEPTION - Workspace Detection (complete). Parallel features: over-mij-page (Build and Test), portfolio-page (Inception), contact-page (Inception). Conflicts: hot files sitePages.ts, lighthouserc.cjs, seo.ts, active-features.md, handled by the agreements.
---
## Requirements Analysis — Questions
**Timestamp**: 2026-10-24T19:50:00Z
**User Input**: (none — questions file created)
**AI Response**: "Compared the design (design/andreaslop-static/soorten-fotoshoots.html) with the live page (andreaslop.nl/soorten-fotoshoots) and the homepage packages. Created inception/requirements/requirement-verification-questions.md with 11 content questions plus the two extension opt-ins and the Operations question."
**Context**: INCEPTION - Requirements Analysis (awaiting answers)
---
## Requirements Analysis — Answers and Requirements
**Timestamp**: 2026-10-24T20:15:00Z
**User Input**: "ik heb de vragen beantwoord" (answers in the file: Q1 A, Q2 A, Q3 A, Q4 A, Q5 B, Q6 B, Q7 A, Q8 \"B, want optie A omvat niet alle shoots en de shoot skunnen ook in de beschrijving.\", Q9 \"A, werkgevbied is Huizen en omgeving of Huizen en Gooi en Vechstreek, maar hoeft daar niet beperkt te blijven en zou in theorie heel Nederland kunnen zijn. Wat is handig om daarvoor te doen?\", Q10 A, Q11 A, Q12 A, Security A, PBT A, Operations B)
**AI Response**: "No contradictions; Q5 = B overrides the labels part of Q1 = A. Gezin placement (after Zwangerschap) and draft text, and the service-area advice for Q9 (Huizen + Gooi en Vechtstreek, shared with the business, not Nederland; Google Business Profile as the bigger lever) are proposed in requirements.md for approval instead of a second question round. Agreed photo ownership with portfolio-page (this feature owns assets/shoots/, assets-only commit). Wrote requirements.md; extension and operations configuration recorded in aidlc-state.md."
**Context**: INCEPTION - Requirements Analysis (awaiting approval)
---
## Branch Update After over-mij-page Merge
**Timestamp**: 2026-10-24T20:30:00Z
**User Input**: (none — message from the over-mij session: merged as 11a5224, PR #7)
**AI Response**: "The branch had no own commits, so it was fast-forwarded from ae769cb to master 11a5224 (the extra commits are docs only). The uncommitted work was stashed as 'soorten-wip' and restored; the expected conflict in active-features.md was resolved by keeping master's ✅ Complete over-mij row and adding this feature's row. All restored files verified identical to the stash. Dropping the now-redundant stash was blocked by the permission classifier (the stash list is shared by all worktrees); left in place for the user."
**Context**: INCEPTION - Requirements Analysis (awaiting approval)
---
## Requirements Analysis — Approval
**Timestamp**: 2026-10-24T20:50:00Z
**User Input**: "Gooi de stash weg wanneer dat wel kan. Gef het desnoods door aan de andere sessies. Als dat echt niet lukt moet je het laten weten dan probee rik het zelf zodra alle features klaar zijn.\n\nIk heb de requirements gezien. Akkoord en ga verder"
**AI Response**: "With the user's explicit approval, dropped the redundant 'soorten-wip' stash by name (stash@{0}, 8713041). Requirements approved, including the Gezin draft text and placement and the service area (Huizen + Gooi en Vechtstreek). Started Workflow Planning: wrote inception/plans/execution-plan.md (Application Design minimal, Functional Design unit 2, Code Generation in two units, Build and Test)."
**Context**: INCEPTION - Requirements Analysis (approved) → Workflow Planning (awaiting approval)
---
## Workflow Planning — Approval
**Timestamp**: 2026-10-24T21:00:00Z
**User Input**: "akkoord, ga verder"
**AI Response**: "Execution plan approved. Started Application Design (minimal): wrote inception/plans/application-design-plan.md with the decisions taken from requirements and earlier features, and 2 questions (photo without frame in MediaText; CallToAction interface). Found that the design's shoot photos have no sand frame, unlike MediaText's FramedImage."
**Context**: INCEPTION - Workflow Planning (approved) → Application Design (awaiting answers)
---
## Application Design — Clarification of Question 1
**Timestamp**: 2026-10-24T21:10:00Z
**User Input**: "Ik weet niet zo goed wat je met vraag 1 bedoeld. kan je dat toelichten?"
**AI Response**: "Explained the sand-coloured block behind the photo (homepage About block, Over mij intro) and options A/B/C."
**Context**: INCEPTION - Application Design (answers pending)
---
## Application Design — Answers and Follow-up Questions
**Timestamp**: 2026-10-24T21:20:00Z
**User Input**: "ik heb de vragen beantwoord" — in the plan file Q1: "X, in het live design heb je op deze pagina een soortgelijk kader, maar per shoot een andere kleur. Kan je het kader niet laten staan, maar dan een kleur opgeven voor het kader met als standaard de kleurdie nu wordt gebruikt? Dus houden wat er nu is, maar de kleur kunnen meegeven."; Q2: "A"
**AI Response**: "Q1: keep the block, make its colour configurable, default sand (the current colour). Checked the live page: block colours #ABA699 (Newborn), #975030 (Zwangerschap), #A18679 (Loveshoot), #84847C (Portretten), none in the theme; live photos are landscape 3:2 while the design crops 4:5. Portfolio-page confirmed /portfolio?shoot=<id>. Added three follow-up questions to the plan: colours, photo orientation, portfolio link."
**Context**: INCEPTION - Application Design (awaiting follow-up answers)
---
## Application Design — Follow-up Answers and Artifacts
**Timestamp**: 2026-10-24T21:40:00Z
**User Input**: "Ik heb de vragen beantwoord" (follow-up 1: A, follow-up 2: B, follow-up 3: A)
**AI Response**: "Frame colours become theme tokens (frame.stone/rust/taupe/olive, Gezin accent); portrait 4:5 crop chosen per photo and shown to the user first; portfolio links to /portfolio?shoot=<id>, rendered only once /portfolio is indexed. Updated requirements.md (FR-SF-02 photo crop and frame colours, new FR-SF-04b, FR-SF-07 frameColor and RichParagraph move, decisions table). Generated application-design/ (components, component-methods, services, component-dependency, application-design). ShootType gains photosLabel and frameColor (announced to portfolio-page)."
**Context**: INCEPTION - Application Design (awaiting approval)
---
## Application Design — Approval
**Timestamp**: 2026-10-24T22:00:00Z
**User Input**: "ga verder"
**AI Response**: "Application Design approved (incl. the proposal to show portfolio links only for shoot types with portfolio photos, via portfolio-page's helper). Functional Design is skipped for unit 1 per plan. Started Code Generation Part 1 for unit 1: wrote construction/plans/shared-blocks-and-content-code-generation-plan.md (23 steps in three commits: A shoot types + photos for portfolio-page, B service area for contact-page, C shared blocks) and asked for plan approval."
**Context**: INCEPTION - Application Design (approved) → CONSTRUCTION - Code Generation unit 1, Part 1 (awaiting plan approval)
---
## Code Generation Unit 1 — Plan Approval and Photo Checkpoint
**Timestamp**: 2026-10-24T22:30:00Z
**User Input**: "approve plan"
**AI Response**: "Plan approved; Part 2 started. Step 1: downloaded the four live shoot photos (all landscape). Step 2: Gezin candidates from the live portfolio: F41A7138 (parents with baby, preferred) and F41A1579 (brother kissing baby); portfolio-page confirmed both are among its 10 portfolio photos but processes them uncropped in other sizes, so no duplicate work; whether the same photo may appear on both pages is the user's choice. Step 3: 4:5 crops (960×1200) made with a one-off scratchpad script; newborn focus adjusted to 0.44; the alternative Gezin crop cuts the boy's head off. Presented the crops to the user for approval (checkpoint)."
**Context**: CONSTRUCTION - Code Generation unit 1, Step 3 checkpoint (awaiting crop approval)
---
## Code Generation Unit 1 — Crops Approved
**Timestamp**: 2026-10-24T23:30:00Z
**User Input**: "Kan je uitsneden-ter-goedkeuring.jpg sturen." then "1. De uitsneden zijn goed\n2. #3, is betere foto om gezin te representeren en #4 is sowieso niet goed uitgesneden"
**AI Response**: "Sent the contact sheet. Crops approved; Gezin = F41A7138 (also in portfolio-page's set, overlap accepted). Wrote the crops to web/src/assets/shoots/, alt texts, theme frame tokens, ShootType types, shootTypes.ts with tests and arbitraries; commit A eb23536 (hash sent to portfolio-page). Service area: types, siteContent, areaServed() in seo.ts with example and PBT tests; commit B befe97a (hash sent to contact-page, which will not cherry-pick)."
**Context**: CONSTRUCTION - Code Generation unit 1, Steps 4-14
---
## Code Generation Unit 1 — Shared Blocks, Verification
**Timestamp**: 2026-10-25T08:30:00Z
**User Input**: "Ga verder waar je gebleven was"
**AI Response**: "FramedImage/MediaText frameColor and reverse, RichParagraph moved to shared, CallToAction, Pricing id=prijzen, test helper cssRulesFor. First pnpm check stopped because portfolio-page's Lighthouse run was using port 4173; agreed the 'claim 4173 / 4173 free' protocol with both peers and cleaned up the orphaned vitest processes of this worktree. After portfolio's '4173 free': full pnpm check passed (290 tests, build, audits, Lighthouse). Visual check with puppeteer-core against the preview: homepage and Over mij unchanged, #prijzen lands below the header. Commit C 6cf9095. Removed this session's duplicate memory note in favour of the peer's more complete one."
**Context**: CONSTRUCTION - Code Generation unit 1 (complete, awaiting approval)
---
@@ -0,0 +1,59 @@
# Code Generation Plan — Unit 1: Shared blocks and content
Single source of truth for code generation of this unit. Workspace root: `K:\Development\SlpSoftware\Projects\AndreaSlopFotografie-soorten-fotoshoots` (worktree); code in `web/`. Branch `feature/soorten-fotoshoots-page` (on master `11a5224`).
## Unit Context
- **Requirements**: FR-SF-02 (photos, frame colours), FR-SF-03 (anchor), FR-SF-06, FR-SF-07, SEO-SF-03 (service area), NFR-SF-02, NFR-SF-06
- **Design**: [application-design.md](../../inception/application-design/application-design.md), [component-methods.md](../../inception/application-design/component-methods.md). No Functional Design for this unit (plan decision).
- **Depends on**: nothing new; reuses `PageSection`, `Reveal`, `DeferredImage`, theme.
- **Used by**: unit 2 (the page); portfolio-page (commit A); contact-page (commit B).
- **Behavioural contract for existing pages**: homepage and Over mij render exactly as before, except the invisible `id="prijzen"` on the pricing section and the new `areaServed` in the business JSON-LD on every page.
The unit is delivered as **three commits**, in this order, so the parallel features can cherry-pick early (worktrees share the repository, so a local commit hash is enough; no push needed for that).
## Steps
### Commit A — Shoot types and photos (hash → portfolio-page)
- [x] **Step 1** — Download the four live shoot photos from andreaslop.nl into the scratchpad (not the repo): `2026/07/F41A8700_websize.jpg` (Newborn), `2026/07/F41A7856_websize.jpg` (Zwangerschap), `2025/08/e77ff000dce5a31c0a38c5d824bfdb95.jpeg` (Loveshoot), `2024/09/DSC_0433-1-scaled.jpg` (Portretten). Check which photo belongs to which shoot by looking at them.
- [x] **Step 2** — Gezin photo: collect candidates from the live site (portfolio, homepage), look at them, check with portfolio-page that the candidate is not one of its 10 portfolio photos (or reuse its file if it is), and propose one to the user.
- [x] **Step 3** — Write a one-off resize script in the scratchpad (PowerShell/System.Drawing as in earlier features, EXIF orientation, cover crop with `-FocusX`/`-FocusY`, JPEG quality 80). Make a 4:5 crop per photo (960×1200) with a chosen focus point and a contact sheet of the five crops. **Checkpoint: show the crops to the user and adjust focus points or swap a photo until approved** (FR-SF-02).
- [x] **Step 4** — Write the approved crops to `web/src/assets/shoots/{newborn,zwangerschap,gezin,loveshoot,portret}.jpg`; record exact sizes.
- [x] **Step 5** — Look at each final crop and write a descriptive Dutch alt text (for Andrea to review).
- [x] **Step 6** — `theme.ts`: colour tokens `frame.stone` `#ABA699`, `frame.rust` `#975030`, `frame.taupe` `#A18679`, `frame.olive` `#84847C` (English comments).
- [x] **Step 7** — `content/types.ts`: `ShootTypeId`, `FrameColor`, `ShootType` (as in component-methods.md).
- [x] **Step 8** — `content/shootTypes.ts`: the five shoot types in page order with the approved texts (FR-SF-02; Gezin marked in a comment as a draft pending Andrea's approval), photos, frame colours (Newborn `frame.stone`, Zwangerschap `frame.rust`, Gezin `accent`, Loveshoot `frame.taupe`, Portretten `frame.olive`) and `packageId` for newborn, zwangerschap and gezin.
- [x] **Step 9** — `content/shootTypes.test.ts`: ids unique and in the agreed order, every `packageId` exists in `packages.ts`, every `frameColor` exists as a theme token, alt texts non-empty, images 4:5. A `shootType` arbitrary in `test/arbitraries.ts` for unit 2's properties.
- [x] **Step 10** — Run the affected tests, lint and type check; commit A ("Adds the shoot types and their photos"); send the hash to portfolio-page.
### Commit B — Service area (hash → contact-page)
- [x] **Step 11** — `content/types.ts`: `ServiceArea`, `SiteContent.serviceArea`; `content/siteContent.ts`: `[{ type: 'City', name: 'Huizen' }, { type: 'AdministrativeArea', name: 'Gooi en Vechtstreek' }]`. Update any `SiteContent` fixtures and the `siteContent` arbitrary.
- [x] **Step 12** — `seo.ts`: pure `areaServed(areas)` → schema.org items (`{ '@type': type, name }`), used by `professionalService` instead of the fixed `Place` Huizen.
- [x] **Step 13** — `seo.test.ts`: example test for the real content; PBT: one item per area, order kept, `@type` only `City`/`AdministrativeArea`, names unchanged, the business JSON-LD still contains no e-mail address; `jsonLdScript` output stays escaped.
- [x] **Step 14** — Run the affected tests, lint and type check; commit B ("Shares the service area in the structured data"); send the hash to contact-page.
### Commit C — Shared blocks
- [x] **Step 15** — `FramedImage`: optional `frameColor` (default `sand`) on the offset block + test (default unchanged, colour applied, block stays decorative).
- [x] **Step 16** — `MediaText`: optional `reverse` (photo in the second column from `lg`, on top when stacked) and `frameColor` passed through + tests (default order unchanged, reversed order, DOM order photo-first in both cases so reading order stays the same).
- [x] **Step 17** — Move `components/about/RichParagraph/` → `components/RichParagraph/` (component and test, `git mv`), update the import in `AboutIntro`.
- [x] **Step 18** — `components/CallToAction/CallToAction.tsx` + test: section named by its h2, `paper.alt`, narrow centred column, tight spacing, lead and children rendered, `Reveal`, axe.
- [x] **Step 19** — `home/Pricing`: `id="prijzen"` on its `PageSection` + test (the section has the id; the anchor lands below the fixed header via the existing `scrollMarginTop`).
- [x] **Step 20** — `pnpm check` (lint, format, tests incl. coverage thresholds, build, audits, Lighthouse) with nothing else heavy running on the machine.
- [x] **Step 21** — Visual check: homepage (About block, pricing) and `/over-mij` against master at desktop, tablet and phone widths; only invisible changes expected.
- [x] **Step 22** — Write `construction/shared-blocks-and-content/code/code-summary.md` (files, resize commands, image sizes, alt texts, commit hashes).
- [x] **Step 23** — Commit C ("Extends the shared blocks for the shoot types page"). Push only when asked.
## Extension Compliance (unit 1)
| Rule | Status | Rationale |
|---|---|---|
| SECURITY-04 | Compliant | CSP unchanged; only self-hosted images |
| SECURITY-10 | Compliant | No new dependencies; image processing is a one-off local step |
| SECURITY-11 | Compliant | JSON-LD through `jsonLdScript`; no e-mail (PBT, Step 13) |
| SECURITY-13 | Compliant | No external resources at runtime |
| Other SECURITY rules | N/A | No data stores, endpoints, auth or infrastructure |
| PBT-01 | Compliant | Properties for `areaServed` listed in Step 13; unit 2's in its Functional Design |
| PBT-02 | Compliant | `jsonLdScript` round-trip already tested |
| PBT-03 | Planned | `areaServed` invariants (Step 13) |
| PBT-04, PBT-05, PBT-06 | N/A | No idempotent, oracle or stateful logic in this unit |
| PBT-07 | Planned | `shootType` arbitrary, `serviceArea` in the `siteContent` arbitrary (Steps 9, 11) |
| PBT-08, PBT-09 | Compliant | Existing seed logging and fast-check setup |
| PBT-10 | Planned | Example-based component tests alongside PBT |
@@ -0,0 +1,43 @@
# Code Summary — Unit 1: Shared blocks and content
Plan: [shared-blocks-and-content-code-generation-plan.md](../../plans/shared-blocks-and-content-code-generation-plan.md). Branch `feature/soorten-fotoshoots-page`, worktree `AndreaSlopFotografie-soorten-fotoshoots`.
## Commits
| Commit | Hash | For | Contents |
|---|---|---|---|
| A — Adds the shoot types and their photos | `eb23536` | portfolio-page (cherry-picks in its unit 3) | `ShootTypeId`, `FrameColor`, `ShootType` in `content/types.ts`; `content/shootTypes.ts` + test; `assets/shoots/*.jpg`; theme tokens `frame.*`; arbitraries `shootTypeId`, `shootType`, `uniqueShootTypes` |
| B — Shares the service area in the structured data | `befe97a` | contact-page (does not cherry-pick; whoever merges second keeps both blocks) | `ServiceArea`, `SiteContent.serviceArea`, value in `siteContent.ts`; `areaServed()` in `seo.ts`, used by `professionalService`; tests (example + PBT); `serviceArea` in `anySiteContent` |
| C — Extends the shared blocks for the shoot types page | `6cf9095` | — | see below |
## Files (commit C)
- Modified: `web/src/components/FramedImage/FramedImage.tsx` (+ test): optional `frameColor`, default `sand`
- Modified: `web/src/components/MediaText/MediaText.tsx` (+ test): optional `reverse` (CSS `order: 2` from `lg`, DOM order unchanged) and `frameColor`
- Moved: `web/src/components/about/RichParagraph/` → `web/src/components/RichParagraph/` (component and test unchanged); import in `about/AboutIntro/AboutIntro.tsx` updated
- Created: `web/src/components/CallToAction/CallToAction.tsx` (+ test)
- Modified: `web/src/components/home/Pricing/Pricing.tsx` (+ test): `id="prijzen"`
- Created: `web/src/test/cssRules.ts`: test helper that returns the generated CSS rules for an element, including media queries, since jsdom applies neither responsive styles nor pseudo-elements
## Images
Originals from andreaslop.nl (all landscape): `2026/07/F41A8700_websize.jpg` (1600×1067, Newborn), `2026/07/F41A7856_websize.jpg` (1600×1067, Zwangerschap), `2026/04/F41A7138_websize.jpg` (1067×1600, Gezin; also one of portfolio-page's 10 photos, approved by the user), `2025/08/e77ff000dce5a31c0a38c5d824bfdb95.jpeg` (2048×1365, Loveshoot), `2024/09/DSC_0433-1-scaled.jpg` (2560×1702, Portretten).
One-off cover crop to 4:5, 960×1200, JPEG quality 80, with a scratchpad script (`crop-image.ps1`, PowerShell/System.Drawing, EXIF orientation applied). Crops approved by the user on a contact sheet before they were fixed.
| File | Focus | Size |
|---|---|---|
| `newborn.jpg` | x 0.44 | 88 KB |
| `zwangerschap.jpg` | x 0.41 | 123 KB |
| `gezin.jpg` | centre | 142 KB |
| `loveshoot.jpg` | x 0.55 | 183 KB |
| `portret.jpg` | x 0.42 | 116 KB |
## Alt texts (for Andrea to review)
- Newborn: "Een pasgeboren baby in een gestreept pakje slaapt met het hoofdje opzij"
- Zwangerschap: "Een zwangere vrouw en haar partner kijken elkaar lachend aan op een zandvlakte, zijn hand op haar buik"
- Gezin: "Vader en moeder kijken samen naar hun pasgeboren baby in de armen van de vader"
- Loveshoot: "Een stel ligt in de zon op een plaid in het gras, met de hoofden tegen elkaar"
- Portretten: "Een vrouw met lang bruin haar in een witte blouse kijkt glimlachend omlaag, met bomen op de achtergrond"
## Verification
- Commits A and B: type check, lint, Prettier and the affected tests passed before each commit.
- Commit C: full `pnpm check` passed, after waiting for portfolio-page's Lighthouse run ("claim 4173" agreement): lint, Prettier, 62 test files / 290 tests (coverage thresholds met), build, `audit:deps` clean (`audit:dev` reports 17 findings in dev tooling, non-blocking per NFR-SEC-05), Lighthouse mobile and desktop assertions passed.
- Visual check against the production build (`vite preview` on port 4180, headless Chrome via `puppeteer-core` with reduced motion, scratchpad script): homepage at 1440 and 390 px unchanged (About block keeps its sand block); `/over-mij` at desktop, tablet and phone widths unchanged; `/#prijzen` lands on the pricing section right below the fixed header.
@@ -0,0 +1,48 @@
# Application Design — Soorten fotoshoots Page
Consolidated design. Details: [components.md](components.md), [component-methods.md](component-methods.md), [services.md](services.md), [component-dependency.md](component-dependency.md). Decisions: [application-design-plan.md](../plans/application-design-plan.md).
## Decisions
| # | Decision |
|---|---|
| Q1 | The offset block behind the photo stays; `FramedImage`/`MediaText` take an optional `frameColor`, default `sand` (existing callers unchanged) |
| Q2 | `CallToAction` is layout with fixed slots: `title`, `titleId`, `lead` (`ReactNode`), action as `children` |
| F1 | Live frame colours become theme tokens `frame.stone/rust/taupe/olive`; Gezin uses `accent`; content names the token |
| F2 | Photos cropped to portrait 4:5; crop point chosen per photo and shown to the user before it is fixed |
| F3 | "Bekijk meer …foto's" links to `/portfolio?shoot=<id>`, rendered only once `/portfolio` is indexed |
| — | Page parts in `components/shoots/` (`ShootList`, `ShootBlock`); `RichParagraph` moves to shared; contact and portfolio targets derived by pure functions in `lib/shootLinks.ts`; JSON-LD via contact-page's `webPage()` with a `shootServices()` builder; `serviceArea` in `siteContent` |
## Page composition
```mermaid
graph TD
Head["PageIntro: Mogelijkheden / h1 Soorten fotoshoots / intro"] --> List["ShootList (PageSection flushTop)"]
List --> B1["ShootBlock Newborn (photo left, stone)"]
List --> B2["ShootBlock Zwangerschap (photo right, rust)"]
List --> B3["ShootBlock Gezin (photo left, accent)"]
List --> B4["ShootBlock Loveshoot (photo right, taupe)"]
List --> B5["ShootBlock Portretten (photo left, olive)"]
List --> Cta["CallToAction: Benieuwd naar de prijzen?"]
classDef head fill:#e76f51,stroke:#ad533d,color:#000;
classDef shoot fill:#f4a261,stroke:#b77a49,color:#000;
classDef cta fill:#b56576,stroke:#884c59,color:#000;
class Head head;
class List,B1,B2,B3,B4,B5 shoot;
class Cta cta;
```
Text alternative: the page head is followed by a list of five alternating shoot blocks, each with its own frame colour, and the closing call to action.
## Units
- **Unit 1 Shared blocks and content**: `FramedImage`/`MediaText` options, theme frame tokens, `CallToAction`, `RichParagraph` move, `Pricing` anchor; first commit `ShootType` + `shootTypes.ts` + `assets/shoots/` (hash to portfolio-page); separate commit `serviceArea` + `professionalService` (hash to contact-page).
- **Unit 2 Soorten fotoshoots page**: `shootLinks.ts`, `ShootList`/`ShootBlock`, page content, route with head and JSON-LD, SEO registry and Lighthouse entries, preview image, LAYOUT.md, RE delta lines.
## Open dependencies on parallel features
- `webPage()` (contact-page): needed in unit 2.
- `/portfolio` `?shoot=` search validation (portfolio-page): `validateSearch` returns `{ shoot?: ShootTypeId }`, so the link type-checks once that route is in master; until then the link is switched off anyway.
- A shoot type without portfolio photos falls back to "Alles" on the portfolio page. Proposed: show the "Bekijk meer …foto's" link only for types that have photos, using a pure helper portfolio-page will export from `lib/` (working name `shootTypesWithPhotos(photos)`). Wired in when that helper is in master; until then the links are off anyway (FR-SF-04b).
- `/contact?pakket=` (contact-page): `shootContactLink` switches in one place when the contact page lands.
## Extension compliance (design level)
- **Security Baseline**: no new inputs, endpoints or third parties; query parameters only built from our own ids (SECURITY-05, -11 compliant); other rules N/A as at requirements level.
- **PBT**: properties to be identified in Functional Design for `shootLinks` and `shootServices`/`areaServed` (PBT-01 planned); generators for `ShootType` added to `src/test/arbitraries.ts` (PBT-07 planned).
@@ -0,0 +1,51 @@
# Component Dependencies — Soorten fotoshoots Page
## Dependency graph
```mermaid
graph TD
Route["routes/soorten-fotoshoots.tsx"] --> PageIntro["PageIntro"]
Route --> ShootList["shoots/ShootList"]
Route --> Cta["CallToAction"]
Route --> Seo["seo.ts: webPage + shootServices"]
Route --> Live["lib/shootLinks: isPortfolioLive"]
ShootList --> ShootBlock["shoots/ShootBlock"]
ShootBlock --> MediaText["MediaText (reverse, frameColor)"]
ShootBlock --> Links["lib/shootLinks: contact + portfolio"]
MediaText --> Framed["FramedImage (frameColor)"]
Cta --> PageSection["PageSection"]
Cta --> Rich["RichParagraph (moved)"]
ShootList --> PageSection
Links --> Packages["content/packages.ts ids"]
Live --> Pages["sitePages.ts"]
Seo --> Site["siteContent.serviceArea"]
Route --> Shoots["content/shootTypes.ts"]
Portfolio["portfolio-page (parallel)"] -.-> Shoots
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;
classDef other fill:#CE93D8,stroke:#6A1B9A,stroke-width:1px,color:#000;
class Route,ShootList,ShootBlock,Cta,Links,Live,Shoots newpart;
class MediaText,Framed,Rich,Seo,Site changed;
class PageIntro,PageSection,Packages,Pages existing;
class Portfolio other;
```
Text alternative: the route composes PageIntro, ShootList (which renders ShootBlocks on MediaText and FramedImage) and CallToAction (on PageSection and RichParagraph); link helpers read package ids and the page registry; SEO reads the service area; portfolio-page also reads shootTypes.ts.
## Dependency matrix
| Component | Depends on | Used by |
|---|---|---|
| `FramedImage` | `DeferredImage`, theme tokens | `MediaText` |
| `MediaText` | `FramedImage`, `Reveal` | `AboutBlock`, `AboutIntro`, `ShootBlock` |
| `CallToAction` | `PageSection`, `Reveal` | route (first use) |
| `RichParagraph` | `RouterLink`, `Link` | `AboutIntro`, route (`CallToAction` lead) |
| `ShootList` | `PageSection`, `ShootBlock` | route |
| `ShootBlock` | `MediaText`, `shootLinks`, `VisuallyHidden` | `ShootList` |
| `shootLinks` | `packages` ids, `sitePages` | `ShootBlock`, route |
| `shootTypes.ts` | assets, `ShootType` | route, portfolio-page |
| `seo.ts` | `siteContent`, `sitePages`, `webPage()` (contact-page) | route heads, `siteHead` |
## Communication
Props only, top-down. No context, no global state. Links are plain router links; the homepage reads `?pakket=` with the existing `packageFromSearch`, the portfolio page reads `?shoot=` with its own validation.
@@ -0,0 +1,119 @@
# Component Methods — Soorten fotoshoots Page
Props and function signatures. Business rules (exact link rules, structured data rules, properties for PBT) follow in Functional Design for unit 2.
## Types (`content/types.ts`)
```ts
export type ShootTypeId = 'newborn' | 'zwangerschap' | 'gezin' | 'loveshoot' | 'portret';
// Colour tokens allowed behind a framed photo
export type FrameColor = 'sand' | 'accent' | 'frame.stone' | 'frame.rust' | 'frame.taupe' | 'frame.olive';
export interface ShootType {
id: ShootTypeId; // stable; also used by portfolio-page and in URLs
name: string; // heading / short name: 'Newborn' … 'Portretten'
shootLabel: string; // 'Newbornshoot' … 'Portretshoot'
photosLabel: string; // "newbornfoto's" … "portretfoto's" (portfolio link)
paragraphs: string[];
image: ContentImage; // 4:5 crop
frameColor: FrameColor;
packageId?: PricingPackage['id'];
}
export interface ShootTypesPageContent {
head: { eyebrow: string; title: string; intro: string };
closing: { title: string; lead: RichText; buttonLabel: string };
}
export interface SiteContent {
// … existing fields
serviceArea: ServiceArea[];
}
export interface ServiceArea {
type: 'City' | 'AdministrativeArea';
name: string;
}
```
`photosLabel` and `frameColor` are additions to the shape agreed with portfolio-page; both are additive and announced to it.
## Shared components
```ts
// FramedImage
type FramedImageProps = {
image: ContentImage;
aspectRatio: string;
priority?: boolean;
frameColor?: FrameColor; // default 'sand'
};
// MediaText
type MediaTextProps = {
image: ContentImage;
aspectRatio: string;
priority?: boolean;
reverse?: boolean; // default false
frameColor?: FrameColor; // default 'sand'
'data-testid'?: string;
children: ReactNode;
};
// CallToAction
type CallToActionProps = {
title: string;
titleId: string; // names the section
lead?: ReactNode;
'data-testid'?: string;
children: ReactNode; // the action, e.g. a LinkButton
};
// RichParagraph (moved, same props)
type RichParagraphProps = { paragraph: RichText };
```
## Page components
```ts
// ShootList
type ShootListProps = {
shoots: ShootType[];
portfolioLive: boolean;
};
// ShootBlock
type ShootBlockProps = {
shoot: ShootType;
reverse: boolean;
priority: boolean;
portfolioLive: boolean;
};
```
## Logic
```ts
// lib/shootLinks.ts — router link props, so routes and search stay type-checked
export function shootContactLink(shoot: ShootType):
| { to: '/'; search: { pakket: string }; hash: 'contact' }
| { to: '/'; hash: 'contact' };
export function shootPortfolioLink(shoot: ShootType):
{ to: '/portfolio'; search: { shoot: ShootTypeId } };
// The portfolio links show once the page is live (indexed in sitePages)
export function isPortfolioLive(pages: Record<RoutePath, PageMeta>): boolean;
```
When contact-page lands, `shootContactLink` switches to `{ to: '/contact', search?: { pakket } }`; nothing else changes. The `/portfolio` route must accept `?shoot=` in its search validation (portfolio-page's route); until it does, the link type is guarded by the `isPortfolioLive` switch and the typed route check is added when portfolio-page's route is in master.
```ts
// seo.ts
export function areaServed(area: ServiceArea[]): object[]; // schema.org Place items
export function professionalService(content: SiteContent): object; // now uses areaServed(content.serviceArea)
export function shootServices(shoots: ShootType[], content: SiteContent): object; // ItemList of Service
// Used in the route head:
// webPage('WebPage', '/soorten-fotoshoots', { mainEntity: shootServices(shootTypes, siteContent) })
```
@@ -0,0 +1,64 @@
# Components — Soorten fotoshoots Page
Status per component: **new**, **changed** (backwards compatible) or **reused** (unchanged).
## Shared components (`web/src/components/`)
### `FramedImage` (changed)
- **Purpose**: photo with the offset block behind its lower left corner (design `.about__media`).
- **Change**: optional `frameColor` (a colour token), default `sand`. Existing callers pass nothing and render exactly as before.
### `MediaText` (changed)
- **Purpose**: framed photo next to a text column; stacked below `lg`.
- **Change**: optional `reverse` (photo in the second column from `lg`; stacked it stays on top) and `frameColor` (passed to `FramedImage`). Defaults keep `AboutBlock` and `AboutIntro` unchanged.
### `CallToAction` (new)
- **Purpose**: closing block of a page (design `.section--alt.section--tight` + `.container--narrow.text-center`): h2, lead, action.
- **Responsibilities**: the section frame (`PageSection` with `tone="alt"`, `width="narrow"`, `spacing="tight"`, named by its h2), heading style (`sectionTitle`), lead style, the space above the action, centring, `Reveal`.
- **Interface**: layout with fixed slots: `title`, `titleId`, `lead` (`ReactNode`), action as `children` (Application Design Q2 = A).
### `RichParagraph` (moved, unchanged)
- **Purpose**: a paragraph of text pieces and inline links (`RichText`).
- **Change**: moves from `components/about/` to `components/RichParagraph/`; Over mij's `AboutIntro` updates its import. Used here for the lead of `CallToAction`.
### Reused
`PageIntro`, `PageSection`, `Reveal`, `LinkButton` (`accent`), `RouterLink`, Chakra `Link` (`underline`), `VisuallyHidden`, `DeferredImage`.
## Page components (`web/src/components/shoots/`)
### `ShootList` (new)
- **Purpose**: the five shoot blocks in one `PageSection` (`spacing="flushTop"`, directly below the page head).
- **Responsibilities**: order, alternation (every second block `reverse`), the hairline between consecutive blocks (`line` token), which block gets the high-priority photo (the first).
### `ShootBlock` (new)
- **Purpose**: one shoot (design `.shoot`): an `article` named by its h2.
- **Responsibilities**: `MediaText` with the shoot photo (4:5, frame colour from the content), the h2 (shoot `name`), the paragraphs, and the links: "Stuur een berichtje" (always) and "Bekijk meer …foto's" (only when the portfolio is live). Visible link texts are completed for screen readers with `VisuallyHidden` parts, as on the price cards.
## Content (`web/src/content/`)
### `ShootType`, `ShootTypeId`, `FrameColor` (new types in `types.ts`)
- Shape agreed with portfolio-page; see component-methods.md.
### `shootTypes.ts` (new)
- The five shoot types in page order: texts, photo, frame colour token, optional package id. Also consumed by portfolio-page (filters, captions).
### `shootTypesPage` content (new, e.g. `shootTypesPageContent.ts`)
- Page texts: page head (eyebrow, title, intro) and the closing block (title, lead as `RichText`, button label).
### `siteContent.ts` / `SiteContent` (changed)
- New `serviceArea`: the places the business serves, used by all structured data.
## Logic (`web/src/lib/`, `web/src/seo.ts`)
### `shootLinks.ts` (new)
- Pure functions that derive router link props from a shoot type: contact target and portfolio target, plus whether the portfolio link is shown.
### `seo.ts` (changed)
- `professionalService` reads `areaServed` from `serviceArea`.
- New pure builder for the page's `ItemList` of `Service` items, passed as `extra` into contact-page's `webPage()`.
## Theme (`web/src/theme.ts`)
- New colour tokens for the frames: `frame.stone` `#ABA699`, `frame.rust` `#975030`, `frame.taupe` `#A18679`, `frame.olive` `#84847C`. `sand` and `accent` already exist.
## Homepage (`web/src/components/home/Pricing`)
- `Pricing` passes `id="prijzen"` to its `PageSection` (anchor for "de pakketten"). Nothing else changes.
@@ -0,0 +1,17 @@
# Services — Soorten fotoshoots Page
The SPA has no service layer. Orchestration happens in the route, the same pattern as the homepage and Over mij.
## Route `routes/soorten-fotoshoots.tsx`
- **`head()`**: `pageHead('/soorten-fotoshoots')` (title, description, canonical, `og:image`, no `noindex` once indexed) plus one `application/ld+json` script: `structuredDataScript(webPage('WebPage', '/soorten-fotoshoots', { mainEntity: shootServices(shootTypes, siteContent) }))`.
- **`component`**: composes, in page order:
1. `PageIntro` with the page head texts (eyebrow, h1, intro).
2. `ShootList` with `shootTypes` and `portfolioLive = isPortfolioLive(sitePages)`.
3. `CallToAction` with the closing title, the lead as `RichParagraph` (link "de pakketten" → `/#prijzen`) and a `LinkButton variant="accent"` "Boek je shoot" → `/#contact`.
## Data flow
Static content modules (later the CMS API) → route → components via props. Components never import content directly, so tests can pass any content and the API can replace the modules 1-to-1.
## External dependency
`webPage()` comes from contact-page (separate commit). If unit 2 starts before that commit exists, this feature asks contact-page whether to add it to the agreed signature itself (see aidlc-state.md § Parallel Work Agreements).
@@ -0,0 +1,23 @@
# 🔍 Feature Resolution
I found an existing AI-DLC workspace with the following work:
| # | Type | Name | Status | Branch |
|---|------|------|--------|--------|
| 1 | Bug | hero-carousel-announce-and-pause | ✅ Complete | fix/hero-carousel-announce-and-pause |
| 2 | Feature | frontend-shell | ✅ Complete | feature/frontend-shell |
| 3 | Feature | homepage-sections | ✅ Complete | feature/homepage-sections |
| 4 | Feature | over-mij-page | 🟢 Construction — Build and Test (started, not finished) | feature/over-mij-page |
New request: build the "Soorten fotoshoots" page (`/soorten-fotoshoots`, currently a PageIntro placeholder; design reference `design/andreaslop-static/soorten-fotoshoots.html`).
**Note**: over-mij-page has not been merged yet. Its shared blocks (PageSection rename, shared media+text block) are likely building blocks for the new page.
**What would you like to do?**
- A) Finish over-mij-page first (Build and Test → PR → merge), then start the new feature `soorten-fotoshoots-page` on a fresh branch from master (recommended)
- B) Start the new feature now, branching from `feature/over-mij-page` (stack on the unmerged work)
- C) Start the new feature now from master, without the over-mij shared blocks
- D) Other
[Answer]: B
@@ -0,0 +1,94 @@
# Application Design Plan — Soorten fotoshoots Page
Depth: minimal. Business rules (contact-link derivation, structured data, PBT properties) follow in Functional Design for unit 2.
## Plan
- [x] Answer the design questions below
- [x] Generate `components.md`: new and changed components with responsibilities and interfaces
- [x] Generate `component-methods.md`: props and function signatures (incl. link derivation and SEO builders)
- [x] Generate `services.md`: composition in the route (there is no service layer in this SPA)
- [x] Generate `component-dependency.md`: dependency matrix and data flow
- [x] Generate `application-design.md`: consolidated design
- [x] Validate completeness and consistency against requirements.md
## Already decided (no question needed)
- **`MediaText` `reverse`**: optional boolean, default `false`; from `lg` the photo moves to the second column (design `.about--reverse` / `.shoot:nth-child(even)`), stacked it stays on top. Existing callers pass nothing and render exactly as before.
- **Page-specific parts** go in `components/shoots/` (e.g. `ShootBlock` for one shoot, `ShootList` for the five with the divider lines and the alternation), the same split as `components/home/` and `components/about/` (Over mij design Q4 = A). Shared building blocks get their own folder directly under `components/`.
- **Contact link**: a pure function in `lib/` derives the router link props from a shoot type (`{ to: '/', search: { pakket }, hash: 'contact' }` or without `search`). The target is never stored as a URL in the content (NFR-SF-06). Switching to `/contact?pakket=` later means changing only this function.
- **Accessible link name**: the same pattern as the price cards: visible "Stuur een berichtje" plus a `VisuallyHidden` part ("over een newbornshoot").
- **Content**: `ShootType` in `content/types.ts`, the list in `content/shootTypes.ts`, page texts (intro, closing block) in a page content object; passed in from the route. Shape agreed with portfolio-page, which uses the list for its filters and captions: `{ id: ShootTypeId; name; shootLabel; paragraphs; image; packageId? }` with `ShootTypeId = 'newborn' | 'zwangerschap' | 'gezin' | 'loveshoot' | 'portret'` (stable ids; `id` instead of the earlier working name `slug`, as in `packages.ts`). `shootLabel` ("Newbornshoot") also feeds the hidden part of the link name.
- **SEO**: `serviceArea` in `SiteContent`; `professionalService` reads it; a pure builder for the page (`ItemList` of `Service`) passed as `extra` into contact-page's `webPage()`. The route's `head()` combines `pageHead('/soorten-fotoshoots')` with one extra `application/ld+json` script.
- **Anchor**: `Pricing` passes `id="prijzen"` to its `PageSection`, which already handles `scrollMarginTop` for anchors.
---
Vul per vraag de letter in na `[Answer]:`. Past geen enkele optie, kies dan de laatste (Anders) en licht toe.
## Vraag 1: Foto zonder kader in `MediaText`
`MediaText` toont de foto nu altijd met het zandkleurige vlak erachter (`FramedImage`, design `.about__media`). In het ontwerp hebben de shootfoto's **geen** kader (`.shoot__media`: alleen de foto, staand 4:5).
- A) `MediaText` krijgt een optie `frame` (standaard aan). Met `frame={false}` toont hij dezelfde foto zonder het vlak; het laden (`DeferredImage`, of `priority` voor de eerste foto) blijft hetzelfde. `FramedImage` krijgt daarvoor dezelfde optie, zodat de fotostijl op één plek blijft. Bestaand gebruik verandert niet. (aanbevolen: volgt het ontwerp, en de layout blijft in één component)
- B) De shootfoto's krijgen ook het zandkleurige kader. Geen extra optie nodig, maar dat wijkt af van het ontwerp.
- C) `ShootBlock` bouwt zijn eigen grid met een gewone foto en gebruikt `MediaText` niet. Dan is ook de `reverse`-optie op `MediaText` niet nodig.
- X) Anders (beschrijf hieronder na de [Answer]:-tag)
[Answer]: X, in het live design heb je op deze pagina een soortgelijk kader, maar per shoot een andere kleur. Kan je het kader niet laten staan, maar dan een kleur opgeven voor het kader met als standaard de kleurdie nu wordt gebruikt? Dus houden wat er nu is, maar de kleur kunnen meegeven.
## Vraag 2: Interface van `CallToAction`
Het afsluitende blok heeft een h2, een intro met een link erin ("de pakketten") en een knop.
- A) **Layout met vaste plekken**: `CallToAction` krijgt `title`, `titleId`, `lead` (tekst of tekst met link, als `ReactNode`) en de knop als `children`. Hij regelt de sectie (achtergrond `paper.alt`, smalle gecentreerde kolom, compacte ruimte), de koptekststijl, de intro-stijl en de ruimte boven de knop. Elke pagina kiest zelf de knop (`LinkButton`) en de link in de tekst. (aanbevolen: dezelfde aanpak als `MediaText`, en een andere pagina kan hem gebruiken met een andere knop)
- B) **Alles als data**: `CallToAction` krijgt `{ title, lead, action: { label, to, hash } }` en rendert de knop zelf. Minder code per gebruik, maar een link in de intro moet dan via een apart model voor tekst met links.
- X) Anders (beschrijf hieronder na de [Answer]:-tag)
[Answer]: A
---
## Vervolgvragen
Vraag 1 is duidelijk: het vlak blijft, `FramedImage`/`MediaText` krijgen een optie voor de **kleur** van het vlak, standaard `sand` (#d9cdbc), dus homepage en Over mij blijven gelijk.
Op de live pagina heeft elk shootvlak deze kleur. Geen ervan staat nu in het thema:
| Shoot | Kleur live |
| ------------- | --------------------- |
| Newborn | #ABA699 (grijsbeige) |
| Zwangerschap | #975030 (roestbruin) |
| Loveshoot | #A18679 (taupe) |
| Portretten | #84847C (grijsgroen) |
| Gezin (nieuw) | bestaat live nog niet |
### Vervolgvraag 1: Welke kleuren krijgen de vlakken?
- A) De vier live kleuren als nieuwe theme-tokens in een eigen groep (bijv. `frame.stone`, `frame.rust`, `frame.taupe`, `frame.olive`, naast `sand` als standaard). In `shootTypes.ts` staat per shoot alleen de naam van het token, geen hexcode, zodat de kleuren op één plek in het thema blijven. Gezin krijgt het heidegroen van de site (`accent`, #7f8b76), al een themakleur die bij de rest past. (aanbevolen)
- B) Zoals A, maar Gezin krijgt `sand`, de standaardkleur
- C) Geen nieuwe kleuren: elke shoot kiest uit de bestaande themakleuren (`sand`, `paper.deep`, `accent`, `ink.muted`). Rustiger, maar wijkt af van de live site.
- X) Anders (beschrijf hieronder na de [Answer]:-tag)
[Answer]: A
### Vervolgvraag 2: Liggend of staand?
Het ontwerp snijdt de shootfoto's **staand** bij (4:5). De live foto's zijn **liggend** (3:2, bijv. 1600×1067). Een liggende foto staand bijsnijden laat bijna de helft van de breedte weg.
- A) **Liggend 3:2**, zoals de live foto's. Er valt niets weg, en het vlak achter de foto valt net zo als op de homepage. (aanbevolen: past bij de foto's die er zijn)
- B) **Staand 4:5**, zoals het ontwerp. Per foto kies ik het uitsnedepunt en laat ik je het resultaat zien voordat het vastligt; komt een foto er slecht uit, dan kiezen we samen een andere.
- C) **4:3**, zoals de foto in het blok Over mij: een tussenweg
- X) Anders (beschrijf hieronder na de [Answer]:-tag)
[Answer]: B
### Vervolgvraag 3: Link naar de portfoliofoto's per shoot
De portfoliopagina (parallelle feature) krijgt filters per shoot, en dat filter kan in de URL: `/portfolio?shoot=newborn` toont alleen de newbornfoto's; een onbekende soort of een soort zonder foto's valt terug op "Alles". Elk shootblok hier zou daarnaar kunnen linken. Dit staat niet in het ontwerp en niet in de goedgekeurde requirements.
- A) Ja: onder elk shootblok, naast "Stuur een berichtje", een tweede link **"Bekijk meer newbornfoto's"** (per shoot de juiste naam) naar `/portfolio?shoot=<id>`. Zolang portfolio nog niet gemerged is, komt de bezoeker daar op de placeholder "in de maak" uit; daarom zet ik de link pas aan als portfolio in master staat.
- B) Nee, niet in deze feature. Later één kleine aanpassing, zodra beide pagina's live zijn. (aanbevolen: deze feature hangt dan niet af van de planning van portfolio)
- X) Anders (beschrijf hieronder na de [Answer]:-tag)
[Answer]: A
@@ -0,0 +1,165 @@
# Execution Plan — Soorten fotoshoots Page
## Detailed Analysis Summary
### Transformation Scope (Brownfield)
- **Transformation Type**: Single component (`web/`), application-level only
- **Primary Changes**: replace the `/soorten-fotoshoots` placeholder with the real page (five shoot blocks, closing call to action); a new shoot-types content list; a `reverse` option on the shared `MediaText`; a new shared `CallToAction`; an anchor on the homepage pricing section; a shared service area for the structured data; page-specific SEO (indexing, description, `WebPage` + `ItemList` of `Service` JSON-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](../../../../../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 `ShootType` type with optional `packageId`; new `serviceArea` field in `SiteContent`
- **API changes**: No external API; `MediaText` gets an optional prop
- **NFR impact**: Yes. SEO (indexed, structured data, `areaServed` of 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
```mermaid
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: `areaServed` from `serviceArea`, new page JSON-LD), `siteContent`/`types.ts` (Minor, new fields)
- **Dependent Components**: homepage `AboutBlock`, Over mij `AboutIntro` (must render unchanged); every page's business JSON-LD (new `areaServed`)
- **Supporting Components**: Lighthouse CI config (Configuration-only), LAYOUT.md (documentation)
### Parallel Feature Coordination
- **contact-page** owns the generic `webPage()` helper in `seo.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.ts` go in an **assets/content-only commit** (hash to portfolio-page); `serviceArea` + `professionalService` go 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
```mermaid
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
- [x] Workspace Detection (COMPLETED)
- [x] 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)
- [x] Requirements Analysis (COMPLETED)
- [x] User Stories (SKIPPED)
- **Rationale**: one persona (the visitor), concrete FRs with exact texts and link targets; stories would restate the requirements
- [x] Execution Plan (IN PROGRESS)
- [ ] Application Design - EXECUTE (minimal depth)
- **Rationale**: a new shared component (`CallToAction`) and a new option on a shared one (`MediaText` `reverse`) need agreed props before code, plus the `ShootType` model, where the contact-link derivation lives, and how the page JSON-LD builds on `webPage()` and `serviceArea`
- [ ] 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, one `Service` per shoot in order, no e-mail, shared `areaServed`) and PBT-01 requires their properties to be identified in design. Unit 1 has nothing to design beyond Application Design
- [ ] 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 check` incl. Lighthouse for `/`, `/over-mij` and `/soorten-fotoshoots`
### 🟡 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-fotoshoots` page; `CallToAction`; `MediaText` `reverse`; `shootTypes.ts` and five resized photos; `serviceArea`; page JSON-LD with tests; a 1200×630 preview image; updated LAYOUT.md and Lighthouse config
- **Quality Gates**: `pnpm check` passes (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-fotoshoots` in the shell; links to `/?pakket=…#contact` preselect the package and land on the contact section; `/#prijzen` lands on the pricing section below the fixed header
@@ -0,0 +1,181 @@
# Verificatievragen — Soorten fotoshoots-pagina
Al vastgelegd (geen vraag nodig):
- **Route** `/soorten-fotoshoots` bestaat al als placeholder ([soorten-fotoshoots.tsx](../../../../../web/src/routes/soorten-fotoshoots.tsx)) en wordt de echte pagina. De navigatie en de footer verwijzen er al naar.
- **Layout en stijl** komen uit het ontwerp ([soorten-fotoshoots.html](../../../../../design/andreaslop-static/soorten-fotoshoots.html)). [LAYOUT.md](../../../../../LAYOUT.md) ("Types of shoots": Intro → Newborn → Pregnancy → Loveshoot → Portraits → Prices & Book) komt daar al mee overeen. Teksten en foto's komen als vaste data in `web/src/content/`, in de vorm die de API straks levert.
- **Hergebruik eerst**: `PageIntro` (h1 + intro), `PageSection`, `MediaText`, `FramedImage`, `Eyebrow`, `Reveal`, `LinkButton` (variant `accent`), de `underline`-variant van `Link` en de theme-tokens. Geen hardgecodeerde kleuren, geen CSS-bestanden en geen nieuwe dependencies.
- **Toegankelijkheid**: dezelfde lat als bij de homepage en Over mij: één h1, secties met een toegankelijke naam, contrast ≥ 4.5:1, `prefers-reduced-motion`, axe in de tests en Lighthouse accessibility 1.0.
- **Codecommentaar** in het Engels; teksten voor bezoekers in het Nederlands.
- **Afspraken met de parallelle features** (contact, portfolio, over-mij): JSON-LD via de gedeelde helper `webPage()` die de contactfeature maakt. Deze feature levert `content/shootTypes.ts`, een gedeelde `CallToAction` en een `reverse`-optie op `MediaText`. Zie `aidlc-state.md` § Parallel Work Agreements.
Wat ik op de live site (andreaslop.nl/soorten-fotoshoots) zag en wat afwijkt van het ontwerp:
| Onderdeel | Ontwerp | Live site |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Intro onder de h1 | eyebrow "Mogelijkheden" + alinea over de soorten shoots en de regio (**Huizen, Bussum, Hilversum** en omgeving, ook andere locaties) | alleen de h1 "Soorten Fotoshoots" |
| Labels boven de koppen | "Newbornshoot", "Zwangerschapsshoot", "Loveshoot", "Portretshoot" | geen |
| Newborn | "…tot 12 weken na de geboorte van je baby." en daarna meteen "Ben je op zoek naar…" | daartussen: **"De fotoshoot vindt bij jou thuis plaats. We nemen alle tijd en volgen het ritme van jullie baby. Je kunt tussendoor gewoon je baby voeden en verschonen als dat nodig is."** |
| Zwangerschap | "…die bij jullie past, **denk aan de Soesterduinen of de heide.**" | "…die bij jullie past." |
| Links | onder elke shoot "Stuur een berichtje", onderaan een blok "Benieuwd naar de prijzen?" met de knop "Boek je shoot" | geen |
| Foto's | uit `assets/img`, met alt-teksten | eigen foto's, **zonder alt-teksten** |
Op de homepage staan drie pakketten met prijzen: **Zwangerschap, Newborn en Gezin**. Een gezinsshoot staat niet op deze pagina (ontwerp en live), maar de huidige meta-beschrijving noemt hem wel.
Vul per vraag de letter in na `[Answer]:`. Past geen enkele optie, kies dan de laatste (Anders) en licht toe.
---
## Vraag 1: Bron voor de teksten
Welke teksten komen op de pagina als ontwerp en live site verschillen?
- A) De opbouw van het ontwerp (intro met de regio, de labels, de links en het afsluitende blok) met de **volledige live teksten** erin: de extra zinnen bij Newborn. "denk aan de Soesterduinen of de heide" uit het ontwerp blijft ook staan. (aanbevolen: meer concrete tekst, goed voor bezoekers en lokale SEO)
- B) Zelfde als A, maar zonder "denk aan de Soesterduinen of de heide" (de shootteksten precies zoals live)
- C) Alles precies zoals in het ontwerp
- X) Anders (beschrijf hieronder na de [Answer]:-tag)
[Answer]: A
## Vraag 2: Gezinsshoot
Het pakket "Gezin" staat op de homepage, maar niet op deze pagina.
- A) Een vijfde blok **Gezin** toevoegen (na Newborn of Zwangerschap). Ik stel een tekst voor in requirements.md die Andrea nog moet goedkeuren, en zoek er een foto bij (bijv. uit het portfolio). LAYOUT.md krijgt dan ook een extra blok.
- B) Bij de vier shoots van ontwerp en live site blijven, en de meta-beschrijving aanpassen zodat er geen gezinsshoot meer in staat (aanbevolen: geen tekst verzinnen die Andrea nog niet heeft)
- C) Bij de vier shoots blijven en de meta-beschrijving laten zoals hij is
- X) Anders (beschrijf hieronder na de [Answer]:-tag)
[Answer]: A
## Vraag 3: Waar gaan de links "Stuur een berichtje" naartoe?
`/contact` is nog een placeholder. De contactfeature (parallel) bekijkt of `/contact?onderwerp=<soort>` het onderwerp vooraf kan invullen; dat is nog niet besloten. Het werkende formulier staat op de homepage (`/#contact`) en kan met `?pakket=` al een pakket vooraf kiezen.
- A) Voorlopig naar `/#contact`. Voor Newborn en Zwangerschap, die een pakket hebben, met `?pakket=` erbij zodat het formulier dat pakket al kiest. Loveshoot en Portretten gaan naar `/#contact` zonder keuze. Zodra de contactpagina af is, zetten we alle links in één keer om naar het formaat dat daar wordt afgesproken. (aanbevolen: werkt nu al, en het blijft bij één plek in `shootTypes.ts`)
- B) Voorlopig naar `/#contact`, zonder vooraf ingevuld pakket (zoals op Over mij)
- C) Meteen naar `/contact`; die pagina wordt later echt
- X) Anders (beschrijf hieronder na de [Answer]:-tag)
[Answer]: A
## Vraag 4: Afsluitend blok "Benieuwd naar de prijzen?"
De tekst zegt "Bekijk de pakketten op de homepage of stel je vraag via het contactformulier." Het prijzenblok op de homepage heeft nog geen anker om naartoe te linken.
- A) "de pakketten" wordt een link naar het prijzenblok (`/#prijzen`; daarvoor krijgt dat blok een `id`, verder verandert er niets aan) en de knop "Boek je shoot" gaat naar dezelfde plek als in vraag 3 (aanbevolen)
- B) Alleen de knop "Boek je shoot" als link, de tekst blijft zonder link (zoals in het ontwerp)
- X) Anders (beschrijf hieronder na de [Answer]:-tag)
[Answer]: A
## Vraag 5: Koppen en labels per shoot
In het ontwerp staat boven elke kop een klein label ("Newbornshoot") en daaronder de kop ("Newborn").
- A) Het label als gewone tekst (`Eyebrow`, wordt niet als kop voorgelezen) en de kop als h2, zoals in het ontwerp. Elke shoot wordt een `article` met die h2 als naam. (aanbevolen: het label herhaalt de kop, dus als aparte kop voegt het niets toe)
- B) Het label weglaten, alleen de h2 (zoals live)
- X) Anders (beschrijf hieronder na de [Answer]:-tag)
[Answer]: B
## Vraag 6: Opbouw van de shootblokken
Ontwerp: foto (staand, 4:5) naast tekst, om en om links en rechts, met een dunne lijn tussen de blokken, en een lichte zoom op de foto als je eroverheen beweegt. Op telefoon en tablet staat alles onder elkaar, met de foto steeds boven.
- A) Precies zo. De zoom valt weg bij `prefers-reduced-motion`. (aanbevolen)
- B) Zo, maar zonder zoom-effect
- C) Alle foto's aan dezelfde kant (geen om-en-om)
- X) Anders (beschrijf hieronder na de [Answer]:-tag)
[Answer]: B
## Vraag 7: Indexeren door zoekmachines
`/soorten-fotoshoots` staat nu op `noindex` en ontbreekt in `sitemap.xml`.
- A) Bij het mergen van deze feature op **geïndexeerd** zetten: geen `noindex` meer, opnemen in de sitemap, en in Lighthouse CI meenemen als geïndexeerde pagina (aanbevolen, zoals bij Over mij)
- B) Voorlopig op `noindex` laten
- X) Anders (beschrijf hieronder na de [Answer]:-tag)
[Answer]: A
## Vraag 8: Titel en beschrijving (SEO)
Nu: titel "Soorten fotoshoots | Andrea Slop Fotografie", beschrijving "Van loveshoot tot gezins-, zwangerschaps- en newbornshoot: ontdek welke fotoshoots Andrea Slop Fotografie aanbiedt in Huizen en omgeving."
- A) Titel met zoekwoorden, bijvoorbeeld "Soorten fotoshoots – newborn, zwangerschap & loveshoot in Huizen", en een beschrijving die precies de shoots van deze pagina en de regio noemt. Ik stel ze voor in requirements.md en jij keurt ze goed. (aanbevolen)
- B) Titel laten staan, alleen de beschrijving laten aansluiten op het antwoord bij vraag 2
- X) Anders (beschrijf hieronder na de [Answer]:-tag)
[Answer]: B, want optie A omvat niet alle shoots en de shoot skunnen ook in de beschrijving.
## Vraag 9: Gestructureerde data (JSON-LD)
Zoekmachines kunnen per shoot zien wat je aanbiedt.
- A) Een `WebPage` met een lijst (`ItemList`) van `Service`-items, één per shoot: naam, korte omschrijving, foto, werkgebied (Huizen, Bussum, Hilversum) en als aanbieder het bestaande bedrijf. **Zonder prijzen**, omdat die niet op deze pagina staan; Google wil dat gestructureerde data overeenkomt met wat op de pagina zichtbaar is. (aanbevolen)
- B) Zoals A, maar met de prijzen uit de pakketten erbij (alleen Newborn en Zwangerschap)
- C) Geen extra gestructureerde data
- X) Anders (beschrijf hieronder na de [Answer]:-tag)
[Answer]: A, werkgevbied is Huizen en omgeving of Huizen en Gooi en Vechstreek, maar hoeft daar niet beperkt te blijven en zou in theorie heel Nederland kunnen zijn. Wat is handig om daarvoor te doen?
## Vraag 10: Preview-afbeelding bij delen (Open Graph)
- A) Een eigen preview voor deze pagina: een van de shootfoto's (bijv. Newborn), bijgesneden tot 1200×630 in `web/public/` (aanbevolen, zoals bij Over mij)
- B) De standaardafbeelding van de site houden
- X) Anders (beschrijf hieronder na de [Answer]:-tag)
[Answer]: A
## Vraag 11: Foto's en alt-teksten
- A) De originele foto's van andreaslop.nl downloaden, eenmalig verkleinen en comprimeren (zoals bij Over mij) en per foto een beschrijvende Nederlandse alt-tekst schrijven die Andrea later kan nalezen (aanbevolen)
- B) De foto's uit het ontwerp gebruiken (`assets/img`) met hun alt-teksten
- X) Anders (beschrijf hieronder na de [Answer]:-tag)
[Answer]: A
## Vraag 12: Herbruikbare onderdelen
- A) De soorten shoots als één lijst in `content/shootTypes.ts` (ook bruikbaar voor de contactpagina), de shootblokken op de bestaande `MediaText` met een nieuwe optie `reverse` (bestaand gebruik verandert niet), en het afsluitende blok als gedeelde component `CallToAction` (koptekst, intro en knop op een gekleurde achtergrond), te gebruiken op elke pagina. (aanbevolen, zo afgesproken met de andere features)
- B) Zelfde als A, maar het afsluitende blok alleen op deze pagina (nog geen gedeelde component, want er is nu maar één plek die hem gebruikt)
- C) Een eigen `ShootCard`-component voor deze pagina, zonder `MediaText` aan te passen
- X) Anders (beschrijf hieronder na de [Answer]:-tag)
[Answer]: A
---
## Vraag: Beveiligingsextensies
Moeten de beveiligingsregels als harde vereisten worden afgedwongen voor dit project?
- A) Ja — dwing alle BEVEILIGINGSREGELS af als blokkerende vereisten (aanbevolen voor productietoepassingen)
- B) Nee — sla alle BEVEILIGINGSREGELS over (geschikt voor PoC's, prototypes en experimentele projecten)
- X) Anders (beschrijf hieronder na de [Answer]:-tag)
[Answer]: A
## Vraag: Property-Based Testing Extensie
Moeten de property-based testing (PBT) regels worden afgedwongen voor dit project?
- A) Ja — dwing alle PBT-regels af als blokkerende vereisten (aanbevolen voor projecten met bedrijfslogica, datatransformaties, serialisatie of stateful componenten)
- B) Gedeeltelijk — dwing PBT-regels alleen af voor pure functies en serialisatie round-trips (geschikt voor projecten met beperkte algoritmische complexiteit)
- C) Nee — sla alle PBT-regels over (geschikt voor eenvoudige CRUD-applicaties, UI-only projecten of dunne integratielagen zonder significante bedrijfslogica)
- X) Anders (beschrijf hieronder na de [Answer]:-tag)
[Answer]: A
## Vraag: Operations-fase
Moet deze feature na Construction door de Operations-fase (deployment en monitoring inrichten)? Deployment naar test en productie en de monitoring (Sentry, Umami, UptimeRobot) bestaan al.
- A) Ja — na Construction de Operations-fase doorlopen (deployment + monitoring inrichten)
- B) Nee — stoppen na Build and Test (deployment en monitoring vallen buiten deze feature)
- C) Weet ik nog niet — vraag het opnieuw na de Construction-fase
- X) Anders (beschrijf hieronder na de [Answer]:-tag)
[Answer]: B
@@ -0,0 +1,232 @@
# Requirements — Soorten fotoshoots Page
## Intent Analysis
- **User Request**: build the "Soorten fotoshoots" page, again paying attention to SEO, accessibility and reuse of code elements, Chakra UI and theming, as in the previous feature (Over mij).
- **Request Type**: New Feature (replaces the `/soorten-fotoshoots` placeholder with the real page) with small, backwards-compatible extensions of shared components
- **Scope Estimate**: Multiple components within one package (`web/`), plus [LAYOUT.md](../../../../../LAYOUT.md)
- **Complexity Estimate**: Simple to moderate. One presentational page, a new content list, one new shared component, one new option on an existing shared component, SEO additions (indexing, structured data, preview image), image preparation, coordination with three parallel features
- **Requirements Depth**: Standard
## Source of Truth
- **Layout and styling**: [design/andreaslop-static/soorten-fotoshoots.html](../../../../../design/andreaslop-static/soorten-fotoshoots.html) and `assets/css/style.css` (`.page-head`, `.shoot`, `.section--alt`, `.section--tight`, `.container--narrow`, `.btn--accent`, `.link-underline`). Exceptions: no labels above the shoot headings (Q5 = B), no hover zoom (Q6 = B).
- **Texts**: the design's structure (intro with the service region, links, closing block) filled with the full live texts of https://andreaslop.nl/soorten-fotoshoots/ as of 2026-10-24, keeping the design's "denk aan de Soesterduinen of de heide". *Source: Q1 = A*
- **Decisions**: [requirement-verification-questions.md](requirement-verification-questions.md)
- **Parallel work**: [aidlc-state.md § Parallel Work Agreements](../../aidlc-state.md)
## Page Structure
Shell header → **Intro** (page head, h1) → **Newborn** → **Zwangerschap** → **Gezin** → **Loveshoot** → **Portretten** → **Prices & Book** (closing call to action) → shell footer.
```mermaid
graph TD
Intro["Intro (h1 Soorten fotoshoots)"] --> Newborn["Newborn (h2)"]
Newborn --> Pregnancy["Zwangerschap (h2)"]
Pregnancy --> Family["Gezin (h2, new)"]
Family --> Love["Loveshoot (h2)"]
Love --> Portraits["Portretten (h2)"]
Portraits --> Cta["Benieuwd naar de prijzen? (h2)"]
classDef head fill:#e76f51,stroke:#ad533d,color:#000;
classDef shoot fill:#f4a261,stroke:#b77a49,color:#000;
classDef added fill:#2a9d8f,stroke:#20766b,color:#000;
classDef cta fill:#b56576,stroke:#884c59,color:#000;
class Intro head;
class Newborn,Pregnancy,Love,Portraits shoot;
class Family added;
class Cta cta;
```
Text alternative: the page runs from the intro through five shoot blocks (Gezin is new) to the closing call to action.
## Out of Scope
- The `/contact` page itself and its subject preselection (parallel feature contact-page). This page links to the homepage contact section until that is in place.
- Prices on this page; they stay in the homepage pricing section.
- A responsive image pipeline (srcset/WebP), unchanged from earlier features.
- The Google Business Profile service area (outside the code; see SEO-SF-03 note).
- Operations phase. *Source: Operations = B*
---
## Functional Requirements
### FR-SF-01 Intro (page head)
- Eyebrow **"Mogelijkheden"**, the page's only h1 **"Soorten fotoshoots"**, and the design's intro paragraph via the existing `PageIntro`: "Hieronder vind je de verschillende soorten fotoshoots die je bij mij kunt boeken. Ik fotografeer voornamelijk in Huizen, Bussum, Hilversum en omgeving, maar ik kom ook naar andere locaties." *Source: Q1 = A*
- `PageIntro` is used as is. Changes to it are announced to the parallel features first.
### FR-SF-02 Shoot blocks
- One block per shoot type, in the order Newborn → Zwangerschap → Gezin → Loveshoot → Portretten. Each block is an `article` named by its h2 (the shoot name), with the photo next to the text column.
- Photo in portrait crop **4:5**. The live photos are landscape (3:2), so the crop point is chosen per photo and shown to the user before it is fixed; a photo that does not survive the crop is replaced in consultation. *Source: Q6 = B, Application Design follow-up 2 = B*
- Each photo keeps the **offset block behind it** (as in the About blocks), in a colour per shoot taken from the live page: Newborn `#ABA699`, Zwangerschap `#975030`, Loveshoot `#A18679`, Portretten `#84847C`, Gezin the site's heather green (`accent`, `#7f8b76`). The colours become theme tokens; the content names the token. The block is decorative. *Source: Application Design Q1 = X, follow-up 1 = A*
- The blocks alternate: photo left on the 1st, 3rd and 5th block, photo right on the 2nd and 4th, from `lg` up. On phones and tablets the photo always sits above the text. *Source: Q6 = B*
- A thin line (theme border token) between consecutive blocks, as in the design (`.shoot + .shoot`).
- **No hover zoom** on the photos. *Source: Q6 = B*
- **No label above the heading**; only the h2. *Source: Q5 = B (overrides the "labels" part of Q1 = A)*
- Below the text a link **"Stuur een berichtje"** (`underline` link variant), see FR-SF-04.
- The texts:
| Shoot | h2 | Text |
|---|---|---|
| Newborn | Newborn | "Ben je in verwachting? Boek een newbornshoot om de 'kleinste' momenten voor altijd te bewaren. De ideale periode voor een newbornshoot is tot 12 weken na de geboorte van je baby. De fotoshoot vindt bij jou thuis plaats. We nemen alle tijd en volgen het ritme van jullie baby. Je kunt tussendoor gewoon je baby voeden en verschonen als dat nodig is." / "Ben je op zoek naar een newbornfotograaf in Huizen en omgeving? Stuur gerust een berichtje voor de mogelijkheden." |
| Zwangerschap | Zwangerschap | "Met een zwangerschapsshoot leg je deze bijzondere periode vast voor altijd. De mooiste periode voor een zwangerschapsshoot is tussen de 30 en 34 weken. We kiezen samen een locatie uit die bij jullie past, denk aan de Soesterduinen of de heide." |
| Gezin | Gezin | **Draft, for Andrea to approve:** "Met een gezinsshoot leggen we vast hoe jullie nu samen zijn: spelen, knuffelen en lachen. Geen stijve poses, maar echte momenten die je later met plezier terugkijkt. We kiezen samen een plek die bij jullie past, bij jullie thuis of buiten in de natuur." |
| Loveshoot | Loveshoot | "Een loveshoot is een prachtige manier om jullie liefde vast te leggen. Zijn jullie verloofd? Dan kan je de foto's gebruiken voor de trouwkaart." |
| Portretten | Portretten | "Van portretshoots in de natuur tot zakelijke shoots voor de branding van je bedrijf." |
- *Source: Q1 = A, Q2 = A. Gezin is placed after Zwangerschap so that the existing order of the design and live page stays intact. The Gezin text is new wording; it stays marked as a draft in the content file until Andrea approves it.*
### FR-SF-03 Closing call to action ("Prices & Book")
- Section on the `paper.alt` background with a narrow, centred column: h2 **"Benieuwd naar de prijzen?"**, lead **"Bekijk de pakketten op de homepage of stel je vraag via het contactformulier."** and button **"Boek je shoot"** (`LinkButton`, variant `accent`).
- **"de pakketten"** links to the homepage pricing section **`/#prijzen`**. For that anchor the homepage `Pricing` section gets `id="prijzen"`; nothing else in `Pricing` changes. The anchor lands below the fixed header, like `/#contact`. *Source: Q4 = A; agreed with contact-page, which does not touch `Pricing.tsx`*
- "Boek je shoot" goes to the same target as the shoot links without a package: `/#contact`. *Source: Q4 = A*
### FR-SF-04 Contact links
- For now, "Stuur een berichtje" goes to the homepage contact section. Shoots with a package preselect it via the existing `?pakket=` parameter: Newborn → `/?pakket=newborn#contact`, Zwangerschap → `/?pakket=zwangerschap#contact`, Gezin → `/?pakket=gezin#contact`. Loveshoot and Portretten → `/#contact`. *Source: Q3 = A*
- The targets are derived from one place (the shoot type's optional `packageId`). contact-page has settled on **`/contact?pakket=<packageId>`** (plain `/contact` without a package). If the contact page is merged before this feature, the links switch to that format here; otherwise the switch is a one-line follow-up.
- Each link has an accessible name that says which shoot it is about (e.g. visually "Stuur een berichtje", accessible name "Stuur een berichtje over een newbornshoot"), so that five identical link texts do not confuse screen reader users.
### FR-SF-04b Portfolio links
- Below each shoot, next to "Stuur een berichtje", a second link **"Bekijk meer …foto's"** (Newborn: "newbornfoto's", Zwangerschap: "zwangerschapsfoto's", Gezin: "gezinsfoto's", Loveshoot: "loveshootfoto's", Portretten: "portretfoto's") to **`/portfolio?shoot=<id>`**, the filter agreed with portfolio-page (unknown or empty types fall back to "Alles" there).
- The links only render once the portfolio page is live, i.e. when `/portfolio` is `indexed` in `sitePages.ts` (portfolio-page sets that when it merges). Until then they are left out, so visitors never land on the placeholder. No code change is needed to switch them on.
- *Source: Application Design follow-up 3 = A (scope addition after requirements approval)*
### FR-SF-05 Scroll reveal
- Blocks fade in as on the other pages (existing `Reveal`), respecting `prefers-reduced-motion`; content is always in the DOM.
### FR-SF-06 Content and images
- The shoot types live as one API-shaped list in a new `web/src/content/shootTypes.ts` (type in `content/types.ts`): `id` (`ShootTypeId`, stable), `name`, `shootLabel`, paragraphs, `image` (`ContentImage`), optional `packageId` (an id from `packages.ts`). Shape agreed with portfolio-page, which uses the list for its filters (after approval; `slug` renamed to `id`, `shootLabel` added). Page-level texts (intro, closing block) live in the same content module or a page content object, passed into the components from the route. *Source: Q12 = A*
- `shootTypes.ts` is also used by portfolio-page (filters, captions) and possibly the contact page; they consume it and do not change it.
- Photos: the four live photos (newborn, zwangerschap, loveshoot, portret) are downloaded in their original size, resized once to at most ±1600 px wide, compressed and stored in `web/src/assets/shoots/`, the same approach as before, with no new dependency. This feature also picks and processes the Gezin photo, from the live site. All five shoot photos land in a **separate commit containing only the assets** (plus `content/shootTypes.ts` if convenient), so portfolio-page can cherry-pick it and import from `assets/shoots/` if it uses the same photos (overlap expected for newborn and portret). Portfolio-only photos are portfolio-page's (`assets/portfolio/`). *Source: Q11 = A; agreed with portfolio-page*
- Every photo gets a descriptive Dutch alt text, written after looking at the photo, for Andrea to review.
### FR-SF-07 Shared components
- **`MediaText`** gets an optional `reverse` option that puts the photo on the right from `lg` up (photo stays on top when stacked). Default unchanged: existing callers (homepage `AboutBlock`, Over mij `AboutIntro`) render exactly as before. The 4:5 crop uses the existing `aspectRatio` prop. *Source: Q12 = A*
- **`MediaText` / `FramedImage`** get an optional colour for the offset block, default `sand` (unchanged for existing callers). *Source: Application Design Q1 = X*
- **`RichParagraph`** (text with inline links, now in `components/about/`) moves to `components/` so the closing block can use it for "de pakketten"; Over mij keeps using it unchanged.
- **`CallToAction`** (new shared component): a section with heading, lead text and an action (button) on the `paper.alt` background in a narrow centred column, usable on any page. FR-SF-03 is its first use. *Source: Q12 = A*
- The shoot block itself is the page's composition of `MediaText`, `SectionHeading`-style heading and text. If it needs styling another page will need too, that goes into a shared component, text style or recipe, not inline per page.
### FR-SF-08 LAYOUT.md
- Update the "Types of shoots" diagram with the Gezin block: **Intro → Newborn → Pregnancy → Family → Loveshoot → Portraits → Prices & Book**, following [.ai/layout-conventions.md](../../../../../.ai/layout-conventions.md). *Source: Q2 = A*
---
## SEO Requirements
### SEO-SF-01 Indexing
- `/soorten-fotoshoots` becomes **indexed** when this feature merges: `indexed: true` in `sitePages.ts` (no `robots noindex`, included in `sitemap.xml`), and added to the indexed paths in `web/lighthouserc.cjs` / `.desktop.cjs` (the existing sync test must pass). Only this page's own entry is changed in these hot files. *Source: Q7 = A*
### SEO-SF-02 Title and description
- Title unchanged: **"Soorten fotoshoots"**, rendered as "Soorten fotoshoots | Andrea Slop Fotografie" (43 characters).
- Description, naming all five shoots of this page and the region: **"Newborn-, zwangerschaps-, gezins-, love- en portretshoots: ontdek welke fotoshoots Andrea Slop Fotografie aanbiedt in Huizen, het Gooi en omgeving."** (147 characters, within the ~155 guideline). *Source: Q8 = B with the user's note that all shoots can go into the description*
### SEO-SF-03 Structured data
- A `WebPage` JSON-LD built with the shared `webPage('WebPage', '/soorten-fotoshoots', extra)` helper from contact-page (no page-specific `xxxPage()` function), whose `mainEntity` is an `ItemList` of `Service` items, one per shoot type in page order: `name`, `description` (first paragraph), `image`, `serviceType`, `areaServed`, and `provider: { '@id': businessId }`. **No prices**, because they are not visible on this page. *Source: Q9 = A*
- **Service area** (the user's question with Q9): one shared value, used both by the existing `ProfessionalService` (`areaServed` is now only `Huizen`) and by every `Service`:
- `City` **Huizen** and `AdministrativeArea` **Gooi en Vechtstreek** (which covers Bussum and Hilversum from the intro text).
- **Not** "Nederland". Structured data should match what the page says ("voornamelijk in Huizen, Bussum, Hilversum en omgeving"), and a nationwide area weakens the local signal that matters for searches like "newbornfotograaf Huizen" without making the site rank elsewhere. The sentence "ik kom ook naar andere locaties" stays as visible text.
- Note: for local search results Google relies mostly on the service area of a Google Business Profile, not on `areaServed`. Setting that up is outside this feature, but worth doing.
- The service area lives as data in `siteContent` (API-shaped), not hard-coded in `seo.ts`. The change to `professionalService` is coordinated with contact-page, which is refactoring `seo.ts`.
- No e-mail address in the structured data. Escaped through the existing `jsonLdScript`. Pure functions in `seo.ts` (100% coverage threshold applies).
### SEO-SF-04 Preview image (Open Graph)
- A page-specific preview image: the Newborn photo cropped to **1200×630**, stored in `web/public/` (stable URL, outside the bundle), set as the page's `ogImage` in `sitePages.ts` with its own alt text. *Source: Q10 = A*
### SEO-SF-05 Semantic structure
- One h1; heading outline h1 Soorten fotoshoots → h2 per shoot → h2 Benieuwd naar de prijzen?; no skipped levels; descriptive link names (FR-SF-04); images with width/height.
---
## Non-Functional Requirements
### NFR-SF-01 Accessibility (WCAG 2.1 AA as guideline)
- Heading outline as in SEO-SF-05.
- Each shoot is an `article` named by its h2 (`aria-labelledby`); the closing block is a `section` named by its h2.
- Text contrast ≥ 4.5:1 (`ink.soft` running text, theme link colours); the divider line is decorative.
- Descriptive alt texts (FR-SF-06); links distinguishable and keyboard reachable with the theme focus ring; touch targets ≥ 44×44 px for the button and the links.
- `prefers-reduced-motion` respected (reveal).
- Axe checks in the component and route tests; Lighthouse accessibility 1.0 for `/soorten-fotoshoots` (mobile and desktop).
### NFR-SF-02 Styling and reuse
- Reuse before building: `PageIntro`, `PageSection`, `MediaText`, `FramedImage`/`DeferredImage`, `Reveal`, `LinkButton` (`accent`), `Link` (`underline`), `RouterLink`, and theme tokens/text styles (`paper.alt`, `contentNarrow`, `sectionY`, `gridGap`, `sectionTitle`, `pageTitle`, border tokens).
- No hard-coded colours, CSS files or Tailwind; Chakra primitives where they fit.
- Components in their own folders under `components/`, Prettier style; code comments in English; visitor-facing texts in Dutch.
- Responsive from 320 px to ultrawide, mobile-first, no horizontal scroll, works at 200% zoom.
### NFR-SF-03 Testing
- **Example-based**: page content and structure (heading outline, article names, order, alternation), link targets per shoot (with and without package), the `/#prijzen` anchor on the homepage, `MediaText` with and without `reverse` (existing callers unchanged), `CallToAction`, head tags (title, description, no `noindex`, canonical, `og:image`), axe checks.
- **Property-based** (fast-check, existing arbitraries): the contact target derived from a shoot type always is a known route, carries `?pakket=` only with an existing package id and never reflects anything else; the structured data never contains an e-mail address, has one `Service` per shoot in page order and all of them point to the business `@id`; the script output stays escaped. *Source: PBT extension = A (full)*
- `pnpm check` (lint, format, tests incl. coverage thresholds, build, audits, Lighthouse) passes.
### NFR-SF-04 Security (Security Baseline extension enabled)
- No new third parties: no external scripts, fonts, embeds or endpoints; CSP in `web/config/securityHeaders.ts` unchanged.
- No e-mail address in markup, bundle, content or structured data.
- Structured data goes through `jsonLdScript`. Query parameters on outgoing links are built from our own package ids only.
- No new runtime dependencies; image processing is a one-off local step.
### NFR-SF-05 Performance
- The first shoot photo may be above the fold on wide screens; whether it is the largest contentful paint is decided in design. If it is, it is not deferred; all other photos use `DeferredImage` with intrinsic width/height (no layout shift).
- Lighthouse performance for `/soorten-fotoshoots`: ≥ 0.9 on mobile and desktop.
- No new network requests other than the bundled images.
### NFR-SF-06 Content for the future API
- `shootTypes` and the page texts are plain data (strings, arrays, `ContentImage`, ids) so the API can deliver them 1-to-1. Link targets are derived in code from `packageId`, not stored as URLs in the content.
### NFR-SF-07 Parallel development
- This branch is stacked on `feature/over-mij-page` and is rebased onto master once over-mij-page is merged (the over-mij session reports the merge commit).
- The `webPage()` helper commit from contact-page is cherry-picked once it exists; until then the JSON-LD code is written against its agreed signature.
- In the hot files (`sitePages.ts`, `lighthouserc.cjs`, `active-features.md`, `_shared/reverse-engineering/`) only this feature's own entries are changed.
---
## Extension Compliance — Requirements Level
### Security Baseline
| Rule | Status | Rationale |
|---|---|---|
| SECURITY-01 Encryption | N/A | No data stores |
| SECURITY-02 Access logging | N/A | No intermediaries added; hosting unchanged |
| SECURITY-03 Application logging | N/A | No server-side component; client errors already go to Sentry |
| SECURITY-04 HTTP security headers | Compliant | Existing header set unchanged; no CSP loosening (NFR-SF-04) |
| SECURITY-05 Input validation | Compliant | No input on this page; the homepage keeps validating `?pakket=` with `packageFromSearch`, and this page only generates known ids |
| SECURITY-06 Least privilege | N/A | No IAM |
| SECURITY-07 Network configuration | N/A | No network infrastructure |
| SECURITY-08 Access control | N/A | Public content |
| SECURITY-09 Hardening | Compliant | No debug output; no new configuration |
| SECURITY-10 Supply chain | Compliant | No new dependencies |
| SECURITY-11 Secure design | Compliant | Structured data escaped; e-mail kept out of the page |
| SECURITY-12 Authentication | N/A | No authentication |
| SECURITY-13 Integrity | Compliant | No external CDN resources; all assets self-hosted |
| SECURITY-14 Alerting | N/A | No server-side component; existing monitoring unchanged |
| SECURITY-15 Exception handling | Compliant | Existing global error handling and error page |
### Property-Based Testing
| Rule | Status | Rationale |
|---|---|---|
| PBT-01 Property identification | Planned | Properties of the link derivation and the SEO functions identified in design |
| PBT-02 Round-trip | Planned | `jsonLdScript` output parses back to the same data (reuse existing property if present) |
| PBT-03 Invariants | Planned | Known routes only, `?pakket=` only with existing ids, no e-mail, one `Service` per shoot in order |
| PBT-04 Idempotency | N/A | No idempotent operations added |
| PBT-05 Oracle | N/A | No reference implementation |
| PBT-06 Stateful | N/A | No stateful logic added |
| PBT-07 Generators | Planned | Reuse/extend `src/test/arbitraries.ts` (shoot type arbitrary) |
| PBT-08 Shrinking/reproducibility | Compliant | Existing seed logging (`config/testSeed.ts`) |
| PBT-09 Framework | Compliant | fast-check already configured |
| PBT-10 Complementary testing | Planned | Example-based tests for the page and components alongside PBT |
---
## Summary of Key Decisions
| # | Decision |
|---|---|
| Q1 | Design structure with the full live texts, Soesterduinen sentence kept |
| Q2 | New Gezin block after Zwangerschap; draft text for Andrea to approve; LAYOUT.md updated |
| Q3 | Shoot links to `/#contact`, with `?pakket=` for Newborn, Zwangerschap and Gezin; switch to `/contact` later in one change |
| Q4 | "de pakketten" → `/#prijzen` (new id on Pricing), "Boek je shoot" → `/#contact` |
| Q5 | No labels above the shoot headings; h2 only |
| Q6 | Alternating photo/text with divider lines, no hover zoom; portrait 4:5 crop chosen per photo; offset block per shoot in the live colours (theme tokens), Gezin heather green |
| Q7 | Indexed on merge |
| Q8 | Title unchanged; description names all five shoots and the region |
| Q9 | `WebPage` + `ItemList` of `Service` without prices, via the shared `webPage()`; service area Huizen + Gooi en Vechtstreek, shared with the business |
| Q10 | Own 1200×630 preview image from the Newborn photo |
| Q11 | Original live photos, resized once, descriptive alt texts |
| Q12 | `shootTypes.ts`, `MediaText` `reverse` and frame-colour options, shared `CallToAction`, `RichParagraph` moved to shared |
| AD-F3 | "Bekijk meer …foto's" links to `/portfolio?shoot=<id>`, shown once `/portfolio` is indexed |
| Ext. | Security Baseline: Yes · PBT: Yes (full) · Operations: No |