Plans the Contact page and records unit 1 as generated

Workspace detection, a reverse engineering delta, requirements with the
approved layout mockups, the execution plan and the application design
for the Contact page, plus the code generation plan and summary of the
webPage helper. Corrects the contact payload in the shared API notes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-25 16:59:38 +01:00
co-authored by Claude Opus 5.5
parent a58bc1c1d6
commit 4c257b7ac0
23 changed files with 1766 additions and 1 deletions
@@ -0,0 +1,51 @@
# Application Design — Contact Page
Consolidates [components.md](components.md), [component-methods.md](component-methods.md), [services.md](services.md) and [component-dependency.md](component-dependency.md). Decisions: [application-design-plan.md](../plans/application-design-plan.md).
## Design decisions
| # | Decision |
|---|---|
| Q1 | `ContactPanel` = gate + form loading (`lazy` / `eager`) + shoot options + preselect + mail subject. The heading and the URL clean-up, scroll and focus stay with each page |
| Q2 | The contact card is rendered twice: one per screen width, the other `display: none`, each with its own heading id. The DOM order always matches the visual order |
| Q3 | Optional `label` per social link in the content; without a label the platform name is shown |
| Q4 | `ContactAside` (photo with an overlapping card) is a page component in `components/contact/` |
| — | `webPage()` / `WebPageType` / `contactPage()` in `seo.ts`; `aboutPage()` rebuilt with identical output |
| — | Privacy line inside `ContactForm`; reply time as `siteContent.contactForm.replyTime` |
## Units and what they touch
| Unit | New | Changed |
|---|---|---|
| 1 webPage helper | `webPage`, `WebPageType` | `aboutPage` (internals), `seo.test.ts` |
| 2 Shared contact blocks | `ContactPanel`, `ContactDetails` | `ContactForm`, `home/ContactSection`, `routes/index.tsx` (prop pass-through), `content/types.ts`, `siteContent.ts` |
| 3 Contact page | `contact/ContactAside`, `contactContent.ts`, `contactPage()`, photos | `routes/contact.tsx`, `aboutContent.ts`, `sitePages.ts`, `lighthouserc*.cjs`, LAYOUT.md |
## Page composition (`/contact`)
```mermaid
graph TD
Intro["PageIntro: eyebrow, h1 Contact, intro"]
Section["PageSection flushTop"]
Narrow["ContactDetails with portrait (narrow only)"]
FormCol["Form column: hidden h2 + ContactPanel eager"]
Aside["ContactAside: photo + ContactDetails (wide only)"]
Intro --> Section
Section --> Narrow
Section --> FormCol
Section --> Aside
classDef head fill:#e76f51,stroke:#ad533d,color:#000;
classDef block fill:#2a9d8f,stroke:#20766b,color:#000;
classDef card fill:#f4a261,stroke:#b77a49,color:#000;
class Intro head;
class Section,FormCol block;
class Narrow,Aside card;
```
Text alternative: the page has the intro and one section; inside it, in DOM order, the narrow-screen card, the form column and the wide-screen aside with photo and card.
## Coordination
- Unit 1 is a separate commit (only `seo.ts` + `seo.test.ts`); its hash goes to portfolio-page and soorten-fotoshoots-page.
- `content/types.ts` and `siteContent.ts` are also changed by soorten-fotoshoots-page (`serviceArea`); different fields, small rebase at most.
## Extension compliance (design level)
- **Security**: no new endpoints or third parties; e-mail only assembled in the browser (`ContactDetails` reuses `emailAddress`); `?pakket=` validated against package ids inside `ContactPanel` and never rendered; structured data through `jsonLdScript`. Compliant / N/A as in requirements.
- **PBT-01**: properties identified now for unit 1: `webPage()` `@id` = `url` = canonical URL of the path, `@type` preserved, `inLanguage` fixed, `extra` keys present in the output; `aboutPage()` equals the previous implementation for generated content (oracle); `jsonLdScript` round-trip. Unit 2 and 3 properties follow in their Functional Design.