Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Sticky Headline Scroll List Features Block for React

A feature list for a developer platform: a narrow headline column that stays in view beside eight numbered rows, each ending in a compact mockup of the feature.

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 sticky-headline feature list for React with Base UI. A narrow start column holds the headline, one sentence, a Shine Button, a ghost link and three counts, and stays in view from lg while eight numbered rows scroll beside it. The rows are bands ruled by Guides, behind a split divider with + marks where each rule meets it. Each row ends in a compact greyscale mockup of its feature: a command chip, a table of services, a preview address, latency bars, a pair of switches, a masked secret, a cost meter and on-call avatars. It's built from Guides, Shine Button, Button and Avatar, with CSS for the entrance and your theme's tokens for every colour. For developer platforms, internal tools and any product whose pitch is a long list that reads better with a headline that waits.

FAQ

How do I change the rows?

Edit the eight feature objects at the top of the file: each has a title and a description. Each row takes its mockup as its child, so swap a mockup by replacing the component inside its Row. The numbers come from each row's place in the list. Keep the rows short: eight at this size already run past one screen, which is what lets the header wait.

Is the header really pinned?

From lg the header's content is sticky below the top of the viewport, so it stays in view while the longer list scrolls past. Below lg it simply comes first, and the rows follow.

Are the counts a list?

Yes: they are a description list, with each label under its figure but the figure first in the markup's reading order, so a screen reader hears "8, paved roads". Figures with a unit are wrapped so a right-to-left layout keeps "11 min" and "300+" together.

How does it fit on a phone?

The header comes first, then the rows. On a phone each row is its number and text, with the mockup under the text; from md the mockup moves to the end of the row. Nothing scrolls sideways at 320 pixels.

Does it follow my theme?

Yes. Mockups use card, muted and foreground tokens, and the toggles and chips are in foreground, never primary. There's no dark scope, so the block is light on a light page and dark on a dark one. Only the Shine Button carries the primary colour.

  • Pro

    A feature section for a developer portal with a display headline pinned to the start side and a two-by-two grid of features in shared hairlines, each cell leading with a small greyscale drawing.

  • Pro

    Six engineering principles as automated checks: a sticky header with a live tally of passing checks beside a two-by-three of cells, each with its check line.

  • Pro

    A numbered two-by-two for fleet operations with the headline pinned to the end side: four cells in shared hairlines, each with a command line and what it did.

  • Pro

    A feature section for an onboarding tool with a large headline on the start side and a card-in-card setup checklist beside it, whose real checkboxes drive a progress meter and a spoken count.

  • Pro

    Changelog Features

    Timelines and steps

    A release feed for a changelog tool that presents its features as release entries: a New, Improved and Fixed filter with counts, a version rail, and a collapsible What changed list on each.

  • Pro

    A features section for a knowledge base as a working tree: a rail of three categories and six features beside a detail panel with the selected feature's sentence, three ticks and a small drawing.