Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Sticky Headline Six Point Features Block for React

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.

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 six-point feature section for React with Base UI. A start column with the headline, one sentence and a tally ("6 of 6 checks passing", counted from the six checks, with a badge for the time of the last run from sm) stays in view from lg beside a two-by-three of principle cells. Each cell is drawn with lines that overshoot its corners and sits apart from its neighbours, and holds a principle, a sentence and a check line: the check's name in code, its status and when it last ran. It's built from Guides, Sliding Number, Status and Badge, with CSS for the entrance and your theme's tokens for every colour. For engineering handbooks, platform and security teams and any set of rules that a tool can actually enforce.

FAQ

How do I change the principles?

Edit PRINCIPLES at the top of the file: each has a title, a description, a check (the name shown in code), the minutes since it ran and an id. The tally counts the entries, so adding a principle changes "of 6" without another edit.

Does the number count up?

The figure is a Sliding Number: it renders its real value on the server and the first paint, and rolls its digits only when the value changes. It never starts from zero, so a page without scripts still says "6".

What does the status dot mean?

It is a small dot in the foreground colour beside the word "passing", so the state is in text and the dot is only decoration. Use a status colour only for a check that fails, which is the one time colour carries meaning here.

Is the header really pinned?

From lg the header's content is sticky below the top of the viewport. The cells are taller than the header, so it waits in place while you scroll past the last row. Below lg the header simply comes first.

How does it fit on a phone?

The header comes first, then the six cells one per row, then from md two across. The lines that overshoot the cells have room because the grid is inset from the rails. Nothing scrolls sideways at 320 pixels.

Does it follow my theme?

Yes. The cells use card and foreground tokens, with no fixed colours and no dark scope. The block has no button, so it has no 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

    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.

  • 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

    Six control cards for a privacy-operations tool, each with a coverage ring counted from the data, a sentence of counts and a Passing or open-items badge.

  • Pro

    A centred manifesto feature section for a deploy tool: a statement over a full-width two-by-two of numbered principles, each written as what you give up against what you get, crossing at one plus mark.

  • Pro

    Six pillars for an infrastructure kit as a grid of cards with large outlined numerals stamped behind the title, each with its owner and its check in a description list.