Files
AndreaSlopFotografie/aidlc-docs/features/over-mij-page/construction/over-mij-page/functional-design/business-rules.md
T
SluijsensandClaude Opus 5.5 93993718c7 Designs the content model and structured data of the Over mij page
A paragraph with links is stored as text pieces and typed route links, so
the API can deliver it without HTML. On the about page, Andrea becomes a
Person with her specialisations, linked both ways to the business that
every page already describes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 01:17:33 +02:00

4.4 KiB
Raw Blame History

Business Rules — Unit 2: Over mij page

Content

ID Rule
BR-OM-01 Texts are the live texts in the design's structure (FR-OM-02..05); no "(vaak met een kat naast me)".
BR-OM-02 Link targets are a RoutePath plus optional hash; "mijn portfolio" → /portfolio, "neem contact op" and "Boek je shoot" → / + contact (the homepage contact section, until /contact exists).
BR-OM-03 A RichText paragraph renders its pieces in order: text as text, an InlineLink as an underlined router link with its text as the link name. Link names are descriptive on their own ("mijn portfolio", "neem contact op").
BR-OM-04 Every photo is informative and has a Dutch alt text that says what is in it; no "Werk van Andrea Slop"-style alt texts.
BR-OM-05 Images carry their intrinsic width/height (space reserved, no layout shift).

Structure and Accessibility

ID Rule
BR-OM-10 Heading outline: h1 "Over mij" (PageIntro) → h2 "Hoi! Ik ben Andrea" → h3 "Hoe het begon", h3 "Buiten de camera om". The h3s look like eyebrow labels (Eyebrow as="h3").
BR-OM-11 The intro, background and personal blocks are sections named by their heading. The photo block has no heading in the design, so it is not a named region; its photo list has the accessible name "Foto's". PageSection.labelledBy becomes optional for this case.
BR-OM-12 Reveal and the photo hover zoom respect prefers-reduced-motion.

Structured Data

graph TD
    Start["Build head for a page"] --> Root["Root route adds ProfessionalService"]
    Root --> Ids["ProfessionalService gets @id businessId and founder @id personId"]
    Start --> IsAbout{"Is the path /over-mij?"}
    IsAbout -->|"no"| Done["Only page meta and site data"]
    IsAbout -->|"yes"| Person["Build Person from content and site data"]
    Person --> Socials{"Any valid https social links?"}
    Socials -->|"yes"| WithSame["sameAs = their hrefs, same order"]
    Socials -->|"no"| NoSame["leave sameAs out"]
    WithSame --> Skills{"Any non-empty knowsAbout entries?"}
    NoSame --> Skills
    Skills -->|"yes"| WithSkills["knowsAbout = trimmed, non-empty, unique"]
    Skills -->|"no"| NoSkills["leave knowsAbout out"]
    WithSkills --> About["AboutPage with mainEntity Person"]
    NoSkills --> About
    About --> Script["Serialise with jsonLdScript"]
    classDef step fill:#2196F3,stroke:#0d47a1,color:#000;
    classDef decision fill:#FF9800,stroke:#e65100,color:#000;
    classDef result fill:#4CAF50,stroke:#2e7d32,color:#000;
    class Start,Root,Ids,Person,About step;
    class IsAbout,Socials,Skills decision;
    class Done,WithSame,NoSame,WithSkills,NoSkills,Script result;

Text alternative: every page gets the business with its id and founder reference; only the about page also builds a Person (sameAs only with valid https socials, knowsAbout only with non-empty entries) inside an AboutPage, serialised through jsonLdScript.

ID Rule
BR-SD-01 No e-mail address anywhere in the structured data, on any page.
BR-SD-02 sameAs contains exactly the hrefs of visibleSocials(socials), in that order; omitted when that list is empty.
BR-SD-03 Stable identifiers: businessId and personId are constants. ProfessionalService.founder['@id'] === personId and Person.worksFor['@id'] === businessId (two-way link, Q4 B). The business keeps all its current fields.
BR-SD-04 Person.image is the absolute URL of /over-mij's ogImage (stable path in public/).
BR-SD-05 knowsAbout: entries trimmed, empty ones dropped, duplicates removed (first one kept); the field is omitted when nothing is left.
BR-SD-06 AboutPage.name/description equal the page's registry title and description; @id/url equal its canonical URL.
BR-SD-07 All structured data is serialised by jsonLdScript (escapes <, >, &), in one application/ld+json script per object (site script from the root route, about script from the page).

SEO Registry

ID Rule
BR-SEO-OM-01 /over-mij is indexed: true: no robots noindex, listed in sitemap.xml, checked as an indexed page by Lighthouse CI (indexedPaths).
BR-SEO-OM-02 Rendered title ≤ 60 characters, description ≤ 155 characters (registry guideline).
BR-SEO-OM-03 ogImage is a 1200×630 JPEG at web/public/og-over-mij.jpg with an alt text that describes the crop.