Files
SluijsensandClaude Opus 5.5 166e5d32bb 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>
2026-10-25 08:26:06 +01:00

22 KiB
Raw Permalink Blame History

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
  • 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

Page Structure

Shell header → Intro (page head, h1) → Newborn → Zwangerschap → Gezin → Loveshoot → Portretten → Prices & Book (closing call to action) → shell footer.

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
  • 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.
  • 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. 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