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>
2.1 KiB
2.1 KiB
Services — Over mij Page
This is a static single-page app without a back-end: there is no service layer. "Orchestration" is composition in the route, as on the homepage.
Route composition (routes/over-mij.tsx)
- Responsibility: load the static content, build the head, compose the page.
- Head:
pageHead('/over-mij')(title, description, canonical, Open Graph incl. the page's ownogImage, nonoindex) plus oneapplication/ld+jsonscript with theAboutPage(built byseo.ts). The site-wideProfessionalServicescript still comes from the root route. - Body: content objects are passed as props to presentational components; components never import content themselves. This keeps the API swap a change in the route only.
Content source (content/aboutContent.ts)
- Responsibility: the page's static data until the CMS API exists; same role as
homeContent.ts. Images are imported fromassets/about/so Vite fingerprints them.
SEO module (seo.ts, sitePages.ts)
- Responsibility: one registry for titles, descriptions, indexing and preview images (
sitePages.ts), and pure builders for head tags and structured data (seo.ts). The sitemap (config/sitemapPlugin.ts) and Lighthouse CI config follow the registry.
Interaction
sequenceDiagram
box rgba(99,179,237,0.4) Router
participant R as Root route
participant P as over-mij route
end
box rgba(154,230,180,0.4) Modules
participant S as seo.ts and sitePages.ts
participant C as aboutContent.ts
end
box rgba(246,224,94,0.4) Components
participant V as Page components
end
R->>S: siteHead (ProfessionalService with id)
P->>S: pageHead and aboutPage
S-->>P: meta, links, JSON-LD script
P->>C: read static content
P->>V: render PageIntro, AboutIntro, StorySection, PhotoDuo with props
Text alternative: the root route adds the site-wide business data; the Over mij route asks the SEO module for its head tags and AboutPage data, reads its static content and passes it as props to the page components.