Requirements, execution plan, functional design, code summaries, build and test results and the audit log; the reverse-engineering notes and the feature registry are updated. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
1.5 KiB
1.5 KiB
Functional Design Plan: testimonials (unit 2)
Only the checklist. The questions are in testimonials-fd-questions.md.
- Step 1: Analyse unit context. Requirements FR-TR-01..04 and 06..14, NFR-TR-01..06, the approved canvas, and the existing design of the section (
homepage-sections/construction/lieve-woorden/functional-design, BR-REV-01..11, BR-LZY-02). - Step 2: Questions. Four layout and behaviour questions the canvas does not settle (tablet layout, card height, sand block, out-of-range crop values).
- Step 3: Collect and check the answers.
- Step 4: Domain entities.
Testimonialwith the optionalimagePosition; the normalised position; the counter text; invariants. File:domain-entities.md. - Step 5: Business rules. Updated rule table (what replaces BR-REV-04, 06, 09, 11; new rules for the counter, the crop and the card) and decision flowcharts. File:
business-rules.md. - Step 6: Business logic model. Navigation (button, key, swipe, loop), announcement, placeholder swap, and the two pure helpers with their testable properties (PBT-01). File:
business-logic-model.md. - Step 7: Frontend components. Component hierarchy, layout geometry for desktop, tablet and phone, props, equal height, slide animation on Chakra's carousel, placeholder height, accessibility, test ids. File:
frontend-components.md. - Step 8: Extension compliance for this stage (Security Baseline, PBT-01).
- Step 9: Completion message and approval. (message presented; awaiting approval)