Files
SluijsensandClaude Opus 5.5 26106f280f Plans the Over mij page
Refreshes the reverse engineering docs after the homepage sections and
records the requirements, execution plan and application design for the
Over mij page: live texts in the design's structure, an indexed page with
its own structured data and preview image, and shared building blocks
(PageSection, MediaText, Eyebrow) reused by the homepage.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-22 23:35:21 +02:00

15 KiB
Raw Permalink Blame History

Requirements — Over mij Page

Intent Analysis

  • User Request: add the "Over mij" page to the front end with AI-DLC, paying attention to SEO, accessibility and reuse of code and styling (Chakra UI, theme).
  • Request Type: New Feature (replaces the /over-mij placeholder with the real page) with a small supporting refactor (shared section frame and media+text block)
  • Scope Estimate: Multiple components within one package (web/), plus LAYOUT.md
  • Complexity Estimate: Simple to moderate — one presentational page, two refactors of existing shared components, SEO additions (indexing, page-specific structured data and preview image), image preparation
  • Requirements Depth: Standard

Source of Truth

Page Structure

Shell header → Intro (page head, h1) → About me → Background → Photos → Personal (with booking button) → shell footer.

Out of Scope

  • The /portfolio and /contact pages (stay placeholders; linked from this page).
  • A responsive image pipeline (srcset/WebP) — unchanged from homepage-sections.
  • Rewriting existing Dutch code comments.
  • Operations phase. Source: Operations = B

Functional Requirements

FR-OM-01 Intro (page head)

  • Eyebrow "Andrea Slop Fotografie" and the page's only h1 "Over mij", via the existing PageIntro without intro text (design .page-head).

FR-OM-02 About me

  • Portrait of Andrea (live photo WhatsApp-Image-2024-10-27-at-14.31.41.jpeg, design andrea-portret.jpg) in the sand-coloured frame, next to the text column; stacked on phones and tablets (design .about, same breakpoint as the homepage block).
  • Eyebrow "Lifestyle fotograaf", heading "Hoi! Ik ben Andrea" (h2, sectionTitle style), and the live paragraphs:
    1. "Hoi! Ik ben Andrea, een fotograaf met liefde voor het vastleggen van momenten. Momenten die je voor altijd bewaart."
    2. "Mijn stijl is te omschrijven als warm en spontaan. Ik houd van natuurlijke, ongedwongen foto's die een verhaal vertellen."
    3. "Nieuwsgierig naar mijn werk? Bekijk mijn portfolio of neem contact op voor een fotoshoot!"
  • "mijn portfolio" links to /portfolio; "neem contact op" links to /#contact (the homepage contact section) for now, to become /contact once that page exists. Both use the underline link variant. Source: Q3 = B
  • Background paper with the section directly below the page head (design .section--flush-top).

FR-OM-03 Background ("Hoe het begon")

  • h3 "Hoe het begon" styled as the design's eyebrow label. Source: Q2 = X, clarification answer — the two story sections continue Andrea's story under "Hoi! Ik ben Andrea", and the smaller style matches the lower level
  • The live text, in the narrow content column on the paper.alt background: "Tijdens de studie Communicatie & Media Design … Ik was helemaal in mijn element. Het was even een zoektocht maar uiteindelijk heb ik mijn specialisatie gevonden. Je kunt bij mij terecht voor newbornshoots, zwangerschapsshoots en gezinsshoots." Source: Q1 = B

FR-OM-04 Photos

  • Two photos side by side at a 3:2 crop (design .intro-gallery--duo), one below the other on phones; live photos slide-1.jpg and IMG_1718.jpg.
  • Decorative or informative is decided per photo when the alt texts are written (FR-OM-07); both are expected to be informative.

FR-OM-05 Personal ("Buiten de camera om")

  • h3 "Buiten de camera om" styled as the eyebrow label (same rule as FR-OM-03).
  • The live text, without the design's "(vaak met een kat naast me)": "Mijn camera gaat altijd mee op reis. Het liefst ga ik naar een plek met een mooie zee maar ik ga ook graag op pad om de natuur vast te leggen met mijn camera." / "Wanneer ik niet achter de camera sta ben ik bezig met tekenen, schilderen of lezen." Source: Q1 = B
  • Button "Boek je shoot" (LinkButton, variant accent) to the same target as "neem contact op": /#contact. Source: Q4 = A
  • Navigating to /#contact from this page lands on the homepage contact section below the fixed header, as the price card links already do.

FR-OM-06 Scroll reveal

  • Blocks fade in as on the homepage (existing Reveal), respecting prefers-reduced-motion; content is always in the DOM.

FR-OM-07 Content and images

  • All page content lives as API-shaped static data in web/src/content/ (a new aboutContent.ts with an AboutPageContent interface in content/types.ts), passed into the components from the route.
  • Photos are downloaded from andreaslop.nl in their original size, resized once to at most ±1600 px wide, compressed and stored in web/src/assets/ — same approach as homepage-sections, no new dependency. Source: Q11 = A
  • Every photo gets a descriptive Dutch alt text, written after looking at the photo, for Andrea to review.

FR-OM-08 LAYOUT.md

  • Update the "About me" diagram to the page structure above — Intro → About Me → Background → Photos → Personal — following .ai/layout-conventions.md. "Intro" is added for consistency with the other page diagrams (Types of shoots, Contact), which start with their page head. Source: Q12 = A

FR-OM-09 Shared section frame: HomeSection → PageSection

  • Rename HomeSection to PageSection (folder, component, test, every import on the homepage) without changing its behaviour, and use it on this page. Source: Q9 = A

FR-OM-10 Shared media+text block

  • Extract the photo-in-frame next to a text column (design .about) into one shared component (working name MediaText), used by both the homepage AboutBlock and FR-OM-02. The homepage must look and behave exactly as before. Source: Q10 = A

SEO Requirements

SEO-OM-01 Indexing

  • /over-mij becomes indexed when this feature merges: indexed: true in sitePages.ts (no robots noindex, included in sitemap.xml), and moved to the indexed paths in web/lighthouserc.cjs / .desktop.cjs (the existing sync test must pass). Source: Q5 = A

SEO-OM-02 Title and description

  • Title: "Over mij – fotograaf in Huizen" → rendered as "Over mij – fotograaf in Huizen | Andrea Slop Fotografie" (55 characters, within the ~60 guideline).
  • Description: "Hoi! Ik ben Andrea, lifestyle fotograaf uit Huizen. Ik maak warme, spontane foto's die een verhaal vertellen: newborn-, zwangerschaps- en gezinsshoots." (151 characters, within the ~155 guideline).
  • Source: Q6 = A; description wording changed by the user at Requirements review (the second sentence now has a subject)

SEO-OM-03 Structured data

  • On this page, add an AboutPage JSON-LD whose mainEntity is a Person (Andrea Slop; job title lifestyle fotograaf; locality Huizen, NL; sameAs the visible social links; image the page preview image), linked to the existing ProfessionalService by @id (the business gets a stable @id, e.g. https://andreaslop.nl/#business).
  • No e-mail address in the structured data (same rule as today). Escaped through the existing jsonLdScript.
  • Built by pure functions in seo.ts (100% coverage threshold applies). Source: Q7 = A

SEO-OM-04 Preview image (Open Graph)

  • A page-specific preview image: the portrait 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: Q8 = A

SEO-OM-05 Semantic structure

  • One h1; section landmarks named by their heading; a heading outline that matches the content (h1 Over mij → h2 Hoi! Ik ben Andrea → h3 Hoe het begon, h3 Buiten de camera om); descriptive link texts; images with width/height.

Non-Functional Requirements

NFR-OM-01 Accessibility (WCAG 2.1 AA as guideline)

  • Heading outline as in SEO-OM-05; no skipped levels.
  • Each content block is a section with an accessible name (aria-labelledby its h2/h3). The photos block is not a landmark of its own unless it has a name (it has no heading in the design).
  • Text contrast ≥ 4.5:1: accent.deep for eyebrow-styled text (incl. the h3 labels), ink.soft for running text.
  • Descriptive alt texts (FR-OM-07); links distinguishable and keyboard reachable with the theme focus ring; touch targets ≥ 44×44 px for the button.
  • prefers-reduced-motion respected (reveal).
  • Axe checks in the component and route tests; Lighthouse accessibility 1.0 for /over-mij (mobile and desktop).

NFR-OM-02 Styling and reuse

  • Reuse before building: PageIntro, PageSection (renamed), SectionHeading, FramedImage, DeferredImage, Reveal, LinkButton (accent), Link (underline), RouterLink, and theme tokens/text styles (paper.alt, contentNarrow, sectionY, gridGap, eyebrow, sectionTitle, pageTitle).
  • If the h3 eyebrow heading or the photo duo needs styling that another page will need too, it goes into a shared component, text style or recipe, not inline per page.
  • 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 in new code (including new comments in existing files); visitor-facing texts in Dutch.
  • Responsive from 320 px to ultrawide, mobile-first, no horizontal scroll, works at 200% zoom.

NFR-OM-03 Testing

  • Example-based: page content and structure (heading outline, section names, links and their targets, button target), the renamed PageSection, the shared media+text block, the homepage AboutBlock unchanged in output, head tags (title, description, no noindex, canonical, og:image), axe checks.
  • Property-based (fast-check, existing arbitraries) for the new pure SEO functions, e.g. the structured data never contains an e-mail address, sameAs only contains valid https social links, the script output always stays escaped. Source: PBT extension = A (full)
  • pnpm check (lint, format, tests incl. coverage thresholds, build, audits, Lighthouse) passes.

NFR-OM-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 (escapes <, >, &).
  • No new runtime dependencies; image processing is a one-off local step, not a build dependency.

NFR-OM-05 Performance

  • All page photos except possibly the portrait are below the fold and use DeferredImage with intrinsic width/height (no layout shift). Whether the portrait is above the fold at common viewport sizes is decided in design; if it is the largest contentful paint it must not be deferred.
  • Lighthouse performance for /over-mij: ≥ 0.9 on mobile and desktop (the default budget for pages other than the homepage).
  • No new network requests other than the bundled images.

NFR-OM-06 Content for the future API

  • AboutPageContent is plain data (strings, arrays, ContentImage, link targets typed as routes or route-plus-hash) so the API can deliver it 1-to-1; rich text with links is modelled without HTML strings.

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-OM-04)
SECURITY-05 Input validation N/A No input or API endpoint on this page
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 new SEO functions identified in design
PBT-02 Round-trip Planned jsonLdScript output parses back to the same data (if not already covered)
PBT-03 Invariants Planned No e-mail in structured data; sameAs ⊆ valid https socials
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
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 exact live texts (no cat remark)
Q2 "Hoe het begon" and "Buiten de camera om" are h3, styled as eyebrow labels, under h2 "Hoi! Ik ben Andrea"
Q3 "mijn portfolio" → /portfolio; "neem contact op" → /#contact for now
Q4 "Boek je shoot" → same target as "neem contact op" (/#contact)
Q5 Indexed on merge (sitemap, no noindex, Lighthouse indexed list)
Q6 New title and description (proposed above)
Q7 AboutPage + Person JSON-LD linked to the business
Q8 Own 1200×630 preview image from the portrait
Q9 HomeSection renamed to PageSection
Q10 Shared media+text block for this page and the homepage AboutBlock
Q11 Original live photos, resized once, descriptive alt texts
Q12 LAYOUT.md updated (Intro → About Me → Background → Photos → Personal)
Ext. Security Baseline: Yes · PBT: Yes (full) · Operations: No