--- name: footer-usage description: > Use after component-usage-ux when an app needs @techsio/ui-kit Footer for site footer composition with container, section, title, list, link, text, divider, bottom area, size, layout, direction, section flow, and framework link adapters. metadata: component_version: "1.2.0" type: "core" library: "@techsio/ui-kit" library_version: "0.3.2" requires: "component-usage-ux framework-consumer-integration app-token-overrides ux-guidelines" resources: "references/ux.md ../../references/component-contracts.md ../../references/consumer_app_usage_rules.md" sources: "" contributor_sources: "libs/ui/src/organisms/footer.tsx libs/ui/src/tokens/components/organisms/_footer.css libs/ui/stories/organisms/footer.stories.tsx" audience: "consumer" --- > Portable scope: Use the installed package's exported types and bundled sibling skills. Repository source paths are optional contributor evidence, not consumer prerequisites; use the consuming app's own checks. Resolve ../../references/ paths from this skill's folder, not the app working directory. # @techsio/ui-kit Footer Usage Use Footer for global footer layout. Do not build app footers from raw divs and anchors when this organism fits. ## UX/UI guidelines House rules come from the `ux-guidelines` skill (writing, formatting, states, where actions and feedback live). This section applies them to `Footer`. **Use it when** - The global site footer: secondary navigation, legal links, contact, newsletter, payment/shipping marks. **Use something else when** | Need | Use instead | | --- | --- | | Primary navigation | Header | | Actions for the current page | page content / page header | **Do** - Group links under short headings; keep the same footer on every storefront page. - Include legal links (terms, privacy, cookies) and contact details users look for. - Stack groups into accordions or a single column on mobile without hiding legal links. **Don't** - Put important actions only in the footer. - Duplicate the whole header navigation. **Copy and states** - Headings are nouns (`Customer care`, `Company`); `© 2026 Company name` generated from the current year. **Behaviour (from the UX spec)** - `Footer.Title` is a heading, not a link; give each `Footer.Section` `aria-labelledby` pointing at its title. - Render `Footer.Divider` only between groups that are present; an empty group leaves no heading or lone line. - Contact, legal and version data come from the product owner; never ship sample values. **Figma → code** | Figma | Code | | --- | --- | | `size=sm…lg` | same prop | | — | `direction`, `layout`, `sectionFlow` (not in Figma) | | FooterTitle / FooterLink / FooterText / FooterDivider | `Footer.Title` / `Footer.Link` / `Footer.Text` / `Footer.Divider` | | — | `Footer.Container`, `Footer.Section`, `Footer.List`, `Footer.Bottom` (no Figma part) | Full UX page (anatomy, states, behaviour, edge cases): [references/ux.md](references/ux.md). The same page renders in Storybook as *Organisms/Footer → UX guidelines*. ## Setup ```tsx import NextLink from "next/link" import { Footer } from "@techsio/ui-kit/organisms/footer" ``` Supported props: ```text Footer size: sm | md | lg direction: vertical | horizontal layout: col | row sectionFlow: col | row Link: href/external/as framework adapter parts: Container, Section, Title, List, Link, Text, Divider, Bottom ``` ## Core Patterns ### Use Footer.Link for footer navigation It wraps the UI-kit Link atom and supports framework adapters. ### Use sections for groups Group footer columns with `Footer.Section`, `Footer.Title`, and `Footer.List`. `Footer.List` is a `