# 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=`, 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).