2.8 KiB
2.8 KiB
Functional Design Plan - Unit 2: Display fallbacks
Feature: prerendering. Unit: 2 "display-fallbacks" (fade-in, no JavaScript, first photo; see execution-plan.md § Units of Work). Builds on unit 1 (start-migration functional design and code summary). Artifacts: functional-design/.
No questions were needed. The choices that belonged to the owner (O1 to O5) were decided on 2026-10-31 and are final in business-rules.md section 5; step 15 applies them.
Steps
- Step 1: Analyse unit context (FR-PR-09 to 13, 21, 22; D6 to D9; components.md; unit 1 business rules section 3, BR-HYD, BR-MAIL-09, BR-LZY; code summary, verification log, measurement gate)
- Step 2: Verify
Reveal,useReveal,useInView, all 21 call sites, their tests anddata-revealconsumers inweb/src - Step 3: Verify every image path (
DeferredImage,Image,Hero,IntroGallery,PortfolioGrid,InstagramGrid,PhotoMosaic,PhotoDuo,FramedImage,MediaText,Pricing,ContactAside,ContactDetails, logos) and what each does without JavaScript - Step 4: Verify in
react-dom19.3 hownoscriptchildren and image preloads are rendered on the server and in the browser - Step 5: Verify the menu without JavaScript in Chrome (
:targeton the fixed panel, Emotion specificity, scroll, Tab order, desktop submenu) against the builtdist/client - Step 6: Read the Lighthouse reports (
afterandrevealvisible, mobile and desktop, master baseline) and measure the largest paint per page and width in Chrome; explain the LCP differences - Step 7: Verify the other fallbacks (hero controls, testimonials, contact form, lightbox triggers, filter, footer Contact title) against the code and the unit 1 browser tests
- Step 8: Create this plan
- Step 9:
business-logic-model.md(Reveal lifetime, images, menu, per-page view without JavaScript, first photo, LCP evidence, testable properties) - Step 10:
business-rules.md(BR-RVL, BR-IMG, BR-NAV, BR-NJS, BR-PRE, BR-DMS, BR-DTS; to verify in code generation; owner decisions) - Step 11:
domain-entities.md(reveal phase, markers, fragment targets, preload link, per-page image profile) - Step 12:
frontend-components.md(hierarchy, new and changed components, first-render contract, call sites, tests, accessibility) - Step 13: Check diagrams against the Mermaid standards and the content validation rules
- Step 14: Report to the orchestrator
- Step 15: Apply the owner decisions O1 to O5: remove "provisional", specify the portfolio first row (columns, tiles, preloads, filter, lightbox), rewrite BR-PRE-08, add the portfolio measurement (BR-DMS-05), update properties, verification points and components