# Application Design — Over mij Page Consolidated view of [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) (Q1–Q4 = A). ## Design Decisions | # | Decision | |---|---| | Q1 | `MediaText` is layout only: photo as data, text column as `children` | | Q2 | One `Eyebrow` component (`as` prop) for every accent label; with `as="h3"` it is the story headings; `SectionHeading`, `PageIntro`, `ContactFormGate` and `TestimonialSlide` switch to it | | Q3 | New small `PhotoDuo`; `IntroGallery` stays as it is | | Q4 | Page-specific components in `components/about/` (`AboutIntro`, `StorySection`, `RichParagraph`); shared blocks each in their own folder under `components/` | | — | `HomeSection` → `PageSection`, plus spacing `flushTop` | | — | Structured data builders in `seo.ts`; route head = `pageHead` + `AboutPage` script; business gets a stable `@id` | | — | Content in `content/aboutContent.ts` typed by `AboutPageContent`; images in `assets/about/`, preview image in `public/` | ## Page Composition ```mermaid graph TD Page["/over-mij"] --> Intro["PageIntro: eyebrow + h1 Over mij"] Page --> A["AboutIntro: PageSection flushTop + MediaText"] A --> AH["SectionHeading: Lifestyle fotograaf + h2 Hoi! Ik ben Andrea"] A --> AP["RichParagraph x3 with links /portfolio and /#contact"] Page --> B["StorySection tone alt: Eyebrow h3 Hoe het begon + text"] Page --> D["PhotoDuo: two 3:2 photos"] Page --> E["StorySection: Eyebrow h3 Buiten de camera om + text"] E --> Btn["LinkButton accent: Boek je shoot to /#contact"] classDef page fill:#f6e05e,stroke:#c05621,stroke-width:1px,color:#000; classDef block fill:#9ae6b4,stroke:#2f855a,stroke-width:1px,color:#000; classDef part fill:#e2e8f0,stroke:#4a5568,stroke-width:1px,color:#000; class Page page; class Intro,A,B,D,E block; class AH,AP,Btn part; ``` Text alternative: the page renders the page head with the h1, the intro block (photo next to an h2 and three paragraphs with links), the "Hoe het begon" story block on the alternate background, the photo duo, and the "Buiten de camera om" story block ending in the booking button. Heading outline: h1 Over mij → h2 Hoi! Ik ben Andrea → h3 Hoe het begon, h3 Buiten de camera om. ## Components - **New shared**: `MediaText`, `Eyebrow` (unit 1), `PhotoDuo` (unit 2) - **Changed shared**: `PageSection` (renamed + `flushTop`), `SectionHeading`, `PageIntro`, `ContactFormGate`, `TestimonialSlide` (use `Eyebrow`), `home/AboutBlock` (uses `MediaText`) — all output-preserving - **New page-specific**: `about/AboutIntro`, `about/StorySection`, `about/RichParagraph` - **Changed modules**: `routes/over-mij.tsx`, `content/types.ts`, `seo.ts`, `sitePages.ts`, `lighthouserc*.cjs` - **New modules/assets**: `content/aboutContent.ts`, `assets/about/*`, `public/og-over-mij.jpg` Interfaces: see [component-methods.md](component-methods.md). ## Composition and Data Flow Props down only, from the route; no service layer, context or fetching. The route builds the head from `seo.ts` and passes static content to presentational components (see [services.md](services.md)). ## Dependencies and Order See [component-dependency.md](component-dependency.md). Unit 1 builds `Eyebrow`, `PageSection` and `MediaText` and switches the existing users with unchanged output; unit 2 builds the page on top. ## Left to Functional Design (unit 2) - `RichText` (paragraph with inline links) and the type of link targets that may include a hash (`/#contact`) - Fields and rules of the `Person` / `AboutPage` structured data, and the properties to test (PBT-01) ## Extension Compliance — Application Design | Rule | Status | Rationale | |---|---|---| | SECURITY-04 | Compliant | No CSP change; only self-hosted assets | | SECURITY-10 | Compliant | No new dependencies | | SECURITY-11 | Compliant | Structured data via the escaping `jsonLdScript`; e-mail kept out | | SECURITY-13 | Compliant | No external resources | | Other SECURITY rules | N/A | No data stores, endpoints, auth, infrastructure or server code | | PBT-01 | Planned | Properties of the SEO builders identified in Functional Design (unit 2) | | PBT-02..10 | N/A at this stage | Applied in Functional Design and Code Generation |