Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Timeline Event Card Stats Block for React

A deployment timeline in a split: the run's facts at the start, and eight steps at the end, each with its start time, how long it took and a duration bar on one shared scale.

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 timeline card for React with Base UI. Pushrail, a release-pipeline tool, opens with the step a deploy is on. The start of the split holds the facts of the run (release, branch, commit, start time, time elapsed and expected finish); the end is a vertical timeline of eight steps. A finished step has a filled node with a check, the running step has a ringed node that pulses once, and the steps to come are numbered and outlined. Each step has a start time, how long it took and a bar on one scale. It is built from Guides, lucide's Check icon and CSS.

FAQ

How do I change the steps?

Edit STEPS at the top of the file. A step has a name, a state (done, current or next), the seconds it took or has run so far, and how long it typically takes. STARTED is when the run began, in seconds after midnight UTC. Start times, the time elapsed, the expected finish, the bar widths and the headline are all computed from these.

How are the bars drawn?

All eight bars share one scale, where the longest step (finished or expected) is the full bar. A finished step is a solid bar. The running step is solid for the time spent so far inside an outline of its usual length, and a step to come is only the outline, so the card never shows time that hasn't happened.

Does the timeline move?

Only once. The running step's ring expands one time when the page loads and is gone, and the header and timeline fade up once. With reduced motion there is no ring animation. The card is a snapshot: it does not tick, and the times shown are fixed in the data.

Is the timeline accessible?

Yes. It is an ordered list, and each step's name is a heading that starts with a hidden word for its state: "Done", "Running" or "Up next". The bars and the nodes are decorative because the time and the duration are written as text. Times are time elements, and digits stay left to right in right-to-left layouts.

How does it fit on a phone?

The facts come first, then the timeline, with a rule between them. The divider between the two columns appears from lg. Nothing scrolls sideways at 320 pixels.

  • Pro

    A sales pipeline as five chevrons as wide as the deals in each stage, in deepening weights, with the deals and their value in a cell under each and the stage worth the most picked out.

  • Pro

    A sprint burndown in a card in a card: the ideal burn as a dashed line, the actual remaining work as a solid one, the gap shaded, a tick where scope was added and a band of three figures under the chart.

  • Pro

    A background-job table where each queue's depth is a bar split into waiting, running and retrying, with the backlog total in the header.

  • Pro

    A page-speed comparison with the time before a tune, the time after it, and the seconds saved on a connecting line between two dots.

  • Pro

    A 3 by 3 grid of hosting services whose latency and twelve-bar history advance on a timer you can pause, with the one slow service marked.

  • Pro

    Progress Bar List Stats

    Goals and progress

    Six launch milestones in one hairline frame, each with its owner and due week, its count against the target, the percentage and a Progress bar, under a headline that counts the milestones done.