Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Sequential Milestone Checklist Features Block for React

A features section for a launch-readiness tool: five milestones in an accordion, each a grouped checklist of real checkboxes, with every milestone locked until the one before it is complete.

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 features section for React with Base UI, built around gated milestones. A side header that stays in view as you scroll holds the headline, a progress ring of the requirements ticked so far and "2 of 5 milestones complete" in rolling digits. Beside it, behind a divider that meets the page's top rule with a plus mark, an accordion of five milestones on ruled rows opens one at a time; each opens to its requirements as real checkboxes in three groups (Legal, Security and Support), and ticking them updates the milestone's chip, the ring and the count. A milestone stays locked until the one before it is complete, so the order can't be skipped. It's built from Accordion, Checkbox, Circular Progress, Sliding Number, Badge and the Guides line kit, with your theme's tokens for every colour and no button. For launch plans, compliance checklists, onboarding programmes and any process with gates.

FAQ

How do I change the milestones and their requirements?

Edit the five milestone objects at the top of the file. Each has a name, a sentence and six requirements, each with a group (Legal, Security or Support), an id and a label. The counts, the percentage in the ring, "of 5 milestones complete" and each chip are all worked out from what is ticked, so they can't drift. START lists what is ticked when the page loads; clear it to start from nothing.

How does the locking work?

A milestone is open to work on while every milestone before it is complete. A locked row still sits in the list and can be reached from the keyboard, but it won't open, and its text says what it waits for ("Locked until Private beta is complete"). If you untick a box in an earlier milestone, every milestone after it locks again, and an open one gives way to the first milestone still to do. Ticking the last box of a milestone doesn't open the next one on its own; you choose when.

What does a screen reader hear?

Each row is a heading with its name, how many requirements are ticked (or what it waits for) and its state. Each checkbox is named by its requirement, and the three groups are fieldsets with legends. A polite status says when a milestone completes and which one unlocks, or when one stops being complete.

How does it work from the keyboard?

Tab moves through the rows and into the open milestone's checkboxes; Space ticks a box, and Enter or Space on a row opens it. The arrow keys, Home and End also move between rows on most versions; the Base UI and React Aria versions use Tab between rows instead.

How does it fit on a phone?

The header sits above the list, the state chip drops away (each row keeps its count or lock line), and the three groups stack in one column. Nothing scrolls the page sideways at 320 pixels.

What moves, and what happens with reduced motion?

The header and the list fade up once on load, the ring sweeps to its new value, the count rolls and a panel opens with a short height change. With reduced motion those are off and everything changes at once.

  • 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

    A features section that tells five years of an edge runtime as year tabs on one rail: what shipped, a cold start before and after in rolling digits, and a five-bar history of regions.

  • Pro

    A two-line transit map for a customer-journey tool: six stations, one interchange where the Setup and Team lines meet, and a popover on every station.

  • Pro

    Chapter Outline Features

    Documents and objects

    A course outline laid out like a book's contents: eight numbered chapters in two ruled columns, each a collapsible row that opens to three sections, with read times and the reader's place.

  • Pro

    Accordion FAQ Features

    Tabs and accordions

    A features section for an API gateway told as six capability questions in an accordion beside a sticky side header, each answer a sentence and a small drawing of the capability at work.

  • Pro

    A day view for a team planner: three features as a numbered list beside a framed 9 to 5 day with events placed by time and a Now line with a pulsing dot.