# Component Dependencies — Contact Page ## Dependency graph ```mermaid graph TD ContactRoute["routes/contact.tsx"] --> PageIntro["PageIntro"] ContactRoute --> PageSection["PageSection"] ContactRoute --> Panel["ContactPanel"] ContactRoute --> Details["ContactDetails"] ContactRoute --> Aside["contact/ContactAside"] ContactRoute --> ContactContent["contactContent"] ContactRoute --> Seo["seo.ts: contactPage, webPage"] HomeSection["home/ContactSection"] --> Panel Panel --> Gate["ContactFormGate"] Panel --> Form["ContactForm"] Panel --> Lib["lib: shootOptions, packageFromSearch, visiblePackages, mailSubject"] Details --> Platforms["socialPlatforms"] Details --> Lib2["lib: emailAddress, visibleSocials, mailtoLink"] Aside --> Img["DeferredImage or eager image"] Form --> Router["RouterLink to privacyverklaring"] ContactRoute --> SiteContent["siteContent: email, socials, contactForm"] AboutRoute["routes/over-mij.tsx"] --> Seo classDef newpart fill:#FFA726,stroke:#E65100,stroke-width:1px,color:#000; classDef changed fill:#63b3ed,stroke:#2b6cb0,stroke-width:1px,color:#000; classDef existing fill:#e2e8f0,stroke:#4a5568,stroke-width:1px,color:#000; class ContactRoute,Panel,Details,Aside,ContactContent newpart; class HomeSection,Form,Seo,SiteContent,AboutRoute changed; class PageIntro,PageSection,Gate,Lib,Lib2,Platforms,Img,Router existing; ``` Text alternative: the contact route uses PageIntro, PageSection, the new ContactPanel, ContactDetails and ContactAside, new content and the SEO helpers; the homepage contact section also uses ContactPanel; ContactPanel wraps the gate and the form and uses the existing package helpers; ContactDetails uses the platform registry and the e-mail and social helpers; the form links to the privacy page; the about route uses the rebuilt SEO helper. ## Dependency matrix | Component | Depends on | Used by | |---|---|---| | `webPage()` | `sitePages`, `canonicalUrl` | `aboutPage`, `contactPage`, portfolio-page, soorten-fotoshoots-page | | `ContactPanel` | `ContactFormGate`, `ContactForm` (lazy or eager), `shootOptions`, `packageFromSearch`, `visiblePackages`, `mailSubject`, `useInView` | `home/ContactSection`, `routes/contact.tsx` | | `ContactForm` | reducer and validation helpers, `RouterLink` (privacy) | `ContactPanel` | | `ContactDetails` | `emailAddress`, `mailtoLink`, `mailSubject`, `visibleSocials`, `socialPlatforms`, `Eyebrow` | `routes/contact.tsx` (twice) | | `ContactAside` | image component | `routes/contact.tsx` | | `contactContent` | `ContactPageContent`, assets | `routes/contact.tsx` | ## Communication patterns - Props down only; no context, store or events beyond what exists (the form's reducer stays internal). - The URL is the only input from outside the content: `?pakket=` read by the route, validated in `ContactPanel`, removed by the route. - No new cycles: `ContactPanel` does not import routes; `ContactDetails` does not know the page. ## Data flow `siteContent` + `packages` + `contactContent` → route → components. Nothing flows back except the form submit, which goes to `submitContactForm` (unchanged, gated).