Files
AndreaSlopFotografie/aidlc-docs/features/contact-page/construction/contact-page/functional-design/business-rules.md
T
SluijsensandClaude Opus 5.5 65c007f8c2
Continuous Integration / check (pull_request) Successful in 12m4s
Continuous Integration / deploy-test (pull_request) Skipped
Continuous Integration / lighthouse (pull_request) Successful in 13m38s
Continuous Integration / deploy-production (pull_request) Skipped
Records Build and Test of the Contact page
Build, unit, integration and performance test instructions and the
summary, the corrected scroll rule and the review on test.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-25 20:14:28 +01:00

4.1 KiB

Business Rules — Unit 3: Contact page

Answers: contact-page-fd-questions.md (Q1 A, Q2 A).

Layout

Id Rule
BR-CP-01 From 1024 px (lg): two columns, the form column (≈ 3/5) left and ContactAside (≈ 2/5) right, aligned at the top. Q1 = A
BR-CP-02 Below 1024 px: one column — the narrow card (with the round portrait) above the form, both full width; ContactAside is not shown.
BR-CP-03 DOM order = visual order on every width: narrow card, form column, aside. The narrow card is hidden from 1024 px, the aside below it (display: none, so also hidden from assistive technology).
BR-CP-04 The section sits directly under the page head (PageSection spacing="flushTop"), as in the design. Both columns fade in with Reveal.
graph TD
    W{"Viewport at least 1024 px?"}
    W -->|"yes"| Wide["Form left; photo with card right; narrow card hidden"]
    W -->|"no"| Narrow["Card with portrait, then form; aside hidden and photo not fetched"]
    classDef decision fill:#FFF59D,stroke:#F57F17,stroke-width:1px,color:#000;
    classDef result fill:#9ae6b4,stroke:#2f855a,stroke-width:1px,color:#000;
    class W decision;
    class Wide,Narrow result;

Text alternative: from 1024 px the page shows the form with the photo and card beside it; below that it shows the card with the portrait above the form and does not fetch the large photo.

Photo

Id Rule
BR-CP-06 The large photo is a <picture> whose source only applies from 1024 px; below that the img falls back to a tiny inline transparent image, so phones and portrait tablets never download the photo. (data: is already allowed by the CSP.)
BR-CP-07 On wide screens the photo is the largest paint: no deferral, fetchpriority="high", intrinsic width and height to reserve space.
BR-CP-08 The portrait is a separate small crop, decorative (alt=""), only in the narrow card.
BR-CP-09 The card overlaps the bottom edge of the photo (as in mockup 1a); the aside reserves room below the photo so the card never covers the next content.

?pakket= on this page

Id Rule
BR-CP-10 The route keeps pakket from the search only when it is text (same validateSearch as the homepage).
BR-CP-11 ContactPanel load="eager" receives it and applies the preselect per BR-CPN-02 (unit 2).
BR-CP-12 After it was applied, the route replaces the URL with /contact without search, no history entry, no focus move; the page starts at the top. An invalid value is removed the same way. Corrected at Build and Test: 'no scroll' left a visitor coming from a scrolled page mid-page.

Texts and headings

Id Rule
BR-CP-05 The intro is head.intro with {reactietermijn} replaced by the reply time; without the placeholder the text is used as is.
BR-CP-13 One h1 "Contact" (PageIntro); h2 "Stuur me een bericht" visually hidden, labelling the form section; h2 "Direct contact" in each card with its own id (contact-details-narrow, contact-details-wide).
BR-CP-14 The contact section is a landmark named by the form heading.

SEO and checks

Id Rule
BR-CP-15 sitePages['/contact'] gets the approved title and description, indexed: true and the preview image; head tags via pageHead('/contact').
BR-CP-16 The route adds the ContactPage JSON-LD via structuredDataScript(contactPage('/contact')).
BR-CP-17 /contact becomes an indexed path in Lighthouse CI with the standard mobile budget 0.9 (not a photo page). If it does not reach 0.9, report the measurement and cause to the owner before changing any budget. Q2 = A
BR-CP-18 The sitemap test expects /contact.

Other pages

Id Rule
BR-CP-19 Over mij: "neem contact op" and "Boek je shoot" link to /contact (no hash). The homepage "Boek …" links stay on the homepage form.
BR-CP-20 LAYOUT.md "Contact": Intro over the full width, then Contact form beside Photo with contact details, per .ai/layout-conventions.md.