Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Sitemap Filter Footer Block for React

A sitemap footer for a documentation host: a search field that filters 36 links across six columns as you type, with a live count and a clear button.

Framework
UI library

Preview

Preview width

Installation

Part of Pro
Pro unlocks the code and one-line install of every Pro button and text effect, plus the MCP for your AI editor.
Have Pro already? Sign in to open it.Opens here as soon as you're Pro.

Overview

A sitemap footer for React with Base UI. A lean band holds the wordmark and one sentence; under it, a band with a search field and a live count; under that, a nav labelled Footer with six columns (Platform, Authoring, Integrations, Learn, Company, Trust) of six pages each. Type in the field and the links that don't match disappear, the matched letters are marked in the ones that stay, a column with no match drops out, and the count reads "24 of 36 pages". If nothing matches, a message and a Clear filter button take the place of the columns. The / key focuses the field from anywhere on the page, and Escape clears it. The page's rails and top rule come from the Guides spine. It's built from Input Group, Kbd, Search Highlight Text, Guides and your theme's tokens.

FAQ

How does the filter match?

It ignores case and accents, so "api" finds "API pages" and "resume" finds "Résumé", and it matches anywhere in the label, not only at the start. A blank field shows everything. Matching letters are marked with the catalog's Search Highlight Text, in a light tint of your foreground colour.

Is the count announced to screen readers?

Yes. The count is a status line that is polite, so a screen reader reads the new number after you pause typing, without interrupting. The field has its own name, Filter the sitemap, and the clear button is named Clear the filter. When nothing matches, the status reads "No pages match" and the message below says so too.

What does the / key do?

It moves focus to the field, as in many docs sites, unless you are already typing in a field, an editable area or a menu, and unless Ctrl, Command or Alt is held. The key is announced to assistive technology as the field's shortcut. If your page already uses / for its own search, remove the effect that listens for it and the hint beside the field.

Does the page jump while I type?

The sitemap keeps a floor height (about one screen of columns), so filtering never pulls the page up. With a very short result the columns simply sit at the top of that space.

How does it fit on a phone?

Below md the field spans the page with the count under it, and the columns sit two across; from md they sit three across and from lg all six. Nothing scrolls sideways at 320 pixels.

  • Pro

    Mega Footer

    Link grids

    A mega footer for a cloud platform: a brand band, eight link groups with icons in two ruled bands of four on one desktop screen, an accordion on phones, and a legal band.

  • Pro

    Sitemap Tree Footer

    Sitemaps and trails

    A sitemap footer drawn as three trees: nested lists with hairline connectors, a root link for each section, pages indented under it and some with their own children.

  • Pro

    Command Palette Footer

    Sitemaps and trails

    A centred footer for a notes app with a search-or-jump button and Command K shortcut that open a palette listing the footer's own links by group.

  • Pro

    The classic link-column footer for an email API: a brand column with the wordmark, one sentence and four social links, four groups of links behind a split divider, and a legal band with the copyright and the policy links.

  • Pro

    A brandless link directory: six groups of five links as cells on shared hairlines, three across by two down, with a legal band under the grid.

  • Pro

    A searchable FAQ for a notes app: a start-aligned header, a band with a full-width search field and a live count, and ten questions that filter as you type, open every match and mark the matched words.