# Functional Design Plan — frontend-shell Unit: **frontend-shell** (single unit; Units Generation skipped). Builds on the approved Application Design in `inception/application-design/`. Questions for this stage are in [frontend-shell-fd-questions.md](frontend-shell-fd-questions.md). ## Plan - [x] 1. Answer the functional design questions - [x] 2. Analyze answers for ambiguities (follow-up questions if needed) - [x] 3. Generate `domain-entities.md` — content and navigation data model (`SiteContent`, `SocialLink`, `SocialPlatform`, `NavItem`, `HeroContent`) with relationships and field rules - [x] 4. Generate `business-rules.md` — behaviour rules and decision logic: - back-to-top visibility, scroll and focus rules - social link filtering/validation and empty-content rules - copyright line, nav invariants - 404 head (title + `noindex`) mechanism - error page behaviour and logging - [x] 5. Generate `business-logic-model.md` — flows: page navigation and scroll restoration, not-found and error rendering inside/outside the shell, back-to-top interaction, content provisioning - [x] 6. Generate `frontend-components.md` — component hierarchy, props/state per component, interaction flows, final Dutch copy for placeholders, 404 and error page - [x] 7. Add the "Testable Properties" section (PBT-01) covering `backToTopThreshold`, `visibleSocials`, `copyrightLine`, `mainNav`/`footerNav`, and explicitly mark components without properties - [x] 8. Validate against FR-01…FR-11, NFR-01…NFR-05, Security Baseline and PBT-01; validate Mermaid diagrams