Skip to Content

Footer Section

Compose semantic, responsive site footers with navigation groups, social links, newsletter content, and legal links.

FooterSection renders the site-wide semantic <footer> landmark and caller-provided navigation and content. Routing, newsletter delivery, and legal destinations remain application-owned.

Basic usage

Group links by destination. Give each group and link a stable ID; labels and URLs are plain caller data.

multi-column - Group key site destinations.

390 × 844

minimal - End a small site with a short legal line.

390 × 844

centered - Center a simple brand sign-off.

390 × 844

large - Give the brand statement more space.

390 × 844

newsletter - Pair navigation with a newsletter slot.

390 × 844

social - Make social destinations easy to find.

390 × 844

mega - Show a broad set of multi-level destinations.

390 × 844

editorial - Use a restrained magazine-style ending.

390 × 844

dark - Create a contrasting visual footer.

390 × 844

split - Separate brand information from navigation.

390 × 844

cta - Give a final call to action a clear place.

390 × 844

portfolio - Support a studio or agency portfolio.

390 × 844

ecommerce - Organize shop, support, and policy links.

390 × 844

legal - Emphasize copyright and legal destinations.

390 × 844

Variants

Each variant changes column layout and emphasis without changing the navigation semantics.

VariantUse case
multi-columnStandard site navigation groups.
minimalShort legal or brand sign-off.
centeredCentered identity and links.
largeLarger brand description area.
newsletterPair links with a signup slot.
socialEmphasize social destinations.
megaBroad navigation collections.
editorialRestrained editorial footer.
darkInverse surface presentation using theme roles.
splitSeparate identity from navigation.
ctaReserve space for a final action.
portfolioStudio or agency portfolio navigation.
ecommerceShop, support, and policy links.
legalFocus on copyright and legal destinations.
390 × 844

Accessibility and responsive behavior

  • The root is a native footer/contentinfo landmark.
  • Navigation, social, and legal links use separately labelled <nav> landmarks.
  • Social links with icon-only content use the link label as their accessible name; visible labels are also rendered.
  • Links retain visible :focus-visible styles and native keyboard/touch behavior.
  • Phone layouts stack footer sections, navigation groups, social/legal links, and newsletter controls vertically with token-based spacing. Tablet layouts use two columns; wider desktop layouts expand to four columns where appropriate.
  • The dark variant uses semantic text/background roles and adapts to the active theme.

API

PropTypeRequiredDefaultDescription
variantFooterSectionVariantNomulti-columnLayout variant.
logoReactNodeNo—Brand mark or name.
descriptionReactNodeNo—Supporting brand description.
navigationGroupsreadonly FooterNavigationGroup[]No[]Primary navigation groups.
socialLinksreadonly FooterSocialLink[]No[]Social destinations with optional icons.
legalLinksreadonly FooterLink[]No[]Privacy, terms, and related links.
newsletterReactNodeNo—Caller-owned signup form.
copyrightReactNodeNo—Copyright line.
childrenReactNodeNo—Additional content.
navigationLabel, socialLabel, legalLabelstringNo"Footer navigation", "Social media", "Legal"Accessible names for navigation landmarks.
classNamestringNo—Additional footer class.

FooterLink contains id, label, and href; FooterSocialLink adds optional icon. Each FooterNavigationGroup contains id, label, and a readonly links array.

Customization

Use the component's className and documented slots to adapt the composition. Prefer a caller-provided ReactNode for media, actions, or controls rather than adding domain behavior to the section.

import type { ComponentProps } from "react";
import { FooterSection } from "@puzzle-ui/pieces";

type FooterSectionProps = ComponentProps<typeof FooterSection>;

export function CustomizedSection(props: FooterSectionProps) {
  return (
    <FooterSection
      {...props}
      className={[props.className, "brand-section"].filter(Boolean).join(" ")}
    />
  );
}

Theme support

The section consumes semantic variables from @puzzle-ui/theme and inherits active or scoped themes. Wrap the application with Theme, and use semantic roles such as text, surface, border, and primary for local overrides. Avoid hard-coded colors, spacing, radii, and shadows.

.brand-section {
  color: var(--puzzle-color-text);
  background: var(--puzzle-color-surface);
  border-color: var(--puzzle-color-border);
}

Composition

Compose this section with the UI primitives named in its API and use the documented slots for consumer-owned controls or media. Keep data fetching, routing, validation, permissions, and persistence in the application. The children slot is intended for additional content that belongs with this section, not as a substitute for its typed data model.

TypeScript example

The package exports this component from its root. Derive a wrapper's exact prop type from the public component rather than widening it:

import type { ComponentProps } from "react";
import { FooterSection } from "@puzzle-ui/pieces";

type FooterSectionProps = ComponentProps<typeof FooterSection>;

export function SectionWrapper(props: FooterSectionProps) {
  return <FooterSection {...props} />;
}

Framework compatibility

The section is router-independent. Static compositions can be server-rendered; place callback-driven interactions in the framework's client boundary. See Next.js and TanStack Start integration for runnable framework examples and SSR guidance.