## Reference images

Study these alongside the description below: hierarchy, rhythm, spacing, colour. Build for the product you are asked about, using this design language.

- Component: https://kage-design-assets.t3.tigrisfiles.io/components/domestika-org/a1bec580-5d19-4289-a277-048dcd6cb3c6-1789146412-6.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/domestika-org/a1bec580-5d19-4289-a277-048dcd6cb3c6-1789146385540-full.webp
- Component on Kage: https://kage.design/component/domestika-footer

## Before you start
Ask what the user's product, information architecture, and brand are, then apply these principles to that context.

Build a large directory footer on a very light neutral background such as `#fafafa`. Start with a brand mark, then arrange link groups into four balanced columns for categories, topics, tools, and lists. Add a horizontal divider and a second utility row with sections, company/information links, support, language selection, and mobile app badges. Finish with another divider and a bottom legal bar containing copyright, policy links, and social icons. Use small 12–14px text, strong 15–16px group headings, dark gray text, muted link color, 24–40px column gaps, and restrained borders. Make columns stack cleanly on mobile, allow long link lists to remain readable, and ensure all controls and external badges have accessible labels.

Never: copy the reference's logo, product name, exact link labels, app-store artwork, legal copy, social icons, illustrations, or imagery.