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>
11 lines
1.1 KiB
Markdown
11 lines
1.1 KiB
Markdown
# Functional Design Plan — Unit 2: Over mij page
|
|
|
|
Depth: minimal. Scope from the execution plan: the content model with inline links, and the rules and testable properties of the structured data (PBT-01). Questions: [over-mij-page-fd-questions.md](over-mij-page-fd-questions.md).
|
|
|
|
- [x] Collect and analyse the answers in `over-mij-page-fd-questions.md`
|
|
- [x] `domain-entities.md` — `AboutPageContent`, `RichText` and its segments, link target, `ContentImage` reuse; structured data entities (`AboutPage`, `Person`, `ProfessionalService` `@id`)
|
|
- [x] `business-rules.md` — content rules (texts, link targets, alt texts), structured data rules (fields, sources, exclusions, linking), SEO registry rules (indexed, title/description limits, preview image)
|
|
- [x] `business-logic-model.md` — how the route turns content and site data into head tags, JSON-LD and the rendered page; pure functions and their properties for PBT (PBT-01)
|
|
- [x] `frontend-components.md` — component hierarchy, props, heading ids, interactions (links, hash navigation to `/#contact`, reveal), test ids
|
|
- [x] Validate against requirements.md, application-design.md and the extension rules
|