Private Pro category · 6 compositions
Footers
Responsive closing navigation for products, docs, and editorial sites. These records are manifest-derived and source-free; an implemented status does not imply manual verification, release readiness, entitlement protection, or availability for purchase.
Manifest items
All 6 records currently carry implemented status. A dedicated detail becomes internally discoverable only after release readiness and a reviewed public preview.
Documentation close
Studio colophon
Editorial directory
Compact utility close
Multilingual close
Category contract
- Purpose
- Responsive closing navigation for products, docs, and editorial sites.
- Declared dependencies
- gummy-navigation-menu, gummy-typography, gummy-separator
- Required review
- light, dark, responsive, keyboard-reviewed, rtl-reviewed, reduced-motion
How to evaluate Footers blocks
Choose a footer by the navigation customers still need at the end of a page: product discovery, documentation, account help, company context, or legal terms. Keep the link set deliberate; a larger sitemap is not automatically a more useful footer.
Generate destinations from maintained route data where practical, use descriptive group headings, and include only monitored contact and social channels. Preserve comfortable targets and visible focus as columns collapse. Legal, privacy, licence, refund, and support links should reach canonical current pages.
Check every destination, locale label, copyright value, external-link treatment, and mobile order before release. Ensure duplicate links have the same purpose, newsletter fields are connected to real consent and delivery systems, and unsupported network logos or community counts are absent.
Maintain the footer groups as a small route contract with an owner for product, company, support, and legal destinations. Supply the breakpoint order and identify links that leave the service. A removed route should fail review rather than linger as a redirect chain, and a new provider or policy should reach the canonical disclosure from every relevant page.
Boundary
Public pages contain only approved names, purposes, dependency aliases, requirements, status, and any future reviewed image preview. Editable paid source, test paths, release locations, and entitlement details remain private.