Functional design, code generation plan and summary of the shared contact blocks, plus the coordination with the parallel features. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.1 KiB
1.1 KiB
Functional Design Plan — Unit 2: Shared contact blocks
Depth: minimal. Scope from the execution plan: which homepage behaviour ContactPanel must keep, which channels ContactDetails shows and how, the privacy line and the shared reply time, and the PBT properties of new pure logic (PBT-01). Questions: shared-contact-blocks-fd-questions.md.
- Collect and analyse the answers in
shared-contact-blocks-fd-questions.md domain-entities.md—SocialLink.label,SiteContent.contactForm.replyTime, the contact channel as derived data,ContactPanelinputsbusiness-rules.md— channel selection and order, labels, link behaviour (mailto subject, new tab), privacy line, reply time, behaviourContactPanelmust preserve fromContactSectionbusiness-logic-model.md— from site content to the list of channels (pure function), the panel's loading and preselect flow, properties for PBTfrontend-components.md— component hierarchy, props, ids and test ids, accessibility per element- Validate against requirements.md, application-design.md and the extension rules