# Unit Dependencies — homepage-sections ## Dependency matrix Rows depend on columns (✓ = needs something that unit introduces). | Unit | 1 Lifestyle | 2 Over mij | 3 Prijzen | 4 Lieve woorden | 5 Contact | 6 Instagram | |---|---|---|---|---|---|---| | 1 Lifestyle fotografie | — | | | | | | | 2 Over mij | ✓ HomeSection, SectionHeading, Reveal, ContentImage | — | | | | | | 3 Prijzen | ✓ | | — | | | | | 4 Lieve woorden | ✓ | ✓ FramedImage | | — | | | | 5 Contact | ✓ | | ✓ packages, packageFromSearch, `pakket` search | | — | | | 6 Instagram | ✓ | | | | | — | ## Order ```mermaid graph LR U1["1 Lifestyle fotografie (shared blocks)"] --> U2["2 Over mij (FramedImage)"] U2 --> U3["3 Prijzen (packages)"] U3 --> U4["4 Lieve woorden"] U4 --> U5["5 Contact"] U5 --> U6["6 Instagram"] U6 --> BT["Build and Test + one PR"] U1 -.-> U3 U1 -.-> U6 U2 -.-> U4 U3 -.-> U5 classDef unit fill:#9ae6b4,stroke:#2f855a,stroke-width:1px,color:#000; classDef shared fill:#63b3ed,stroke:#2b6cb0,stroke-width:1px,color:#000; classDef final fill:#f6e05e,stroke:#c05621,stroke-width:1px,color:#000; class U2,U4,U5,U6 unit; class U1,U3 shared; class BT final; ``` Text alternative: the units run in page order 1 to 6, then Build and Test; dashed arrows show the real dependencies — unit 1's shared blocks are used by all, unit 2's FramedImage by unit 4, and unit 3's packages by unit 5. ## Notes - The build order equals the page order, so the homepage is always correct up to the last finished unit. - Units 4 and 6 could be swapped without impact; unit 5 must come after unit 3. - Integration points checked at Build and Test: section order in `routes/index.tsx`, background alternation, Prijzen → Contact preselection, full-page Lighthouse. - One branch, commits per unit, one PR at the end; no unit is merged to `master` on its own.