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:
+94
@@ -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
|
||||
Reference in New Issue
Block a user