shadcn.io is not affiliated with official shadcn/ui
Pipeline Step Diagram Features Block for React
A CI pipeline drawn as five stages joined by chevrons, each with its time and status, over a band that measures the pipeline's impact with rolling numbers.
Installation
Overview
A pipeline features section for React with Base UI. Five stages (Commit, Build, Test, Preview, Release) sit in one ordered list as cells that share their hairlines, each joined to the next by a chevron that mirrors in right-to-left layouts. A stage says what it does, shows a passed status and the time it takes, and draws a thin bar of its share of the eight-minute run; the slowest carries a badge. A closing band measures the whole pipeline: cycle time, rollback rate and releases a day, each rolling to its new value beside the old one. Below md the stages stack and the chevrons point down. It's built from Guides, Badge, Status and Sliding Number, and it follows your theme. For CI and deployment products, build tools and any feature that is a sequence with something to prove at the end.
FAQ
How do I change the stages and their times?
Edit STAGES at the top of the file: each has a name, a sentence, an icon and its time in seconds. The run's total, each stage's share, the "Slowest" badge and the labels like "2 min 10 s" are all derived from those numbers by small functions, so they always agree. The grid is five columns from md; if you add or remove a stage, change md:grid-cols-5.
How do the rolling numbers work?
Each figure in the closing band is a Sliding Number: its digits roll like an odometer to the value when the band scrolls into view. The old value sits beside it as plain text, so the comparison reads without the animation. Edit IMPACTS for the figures, their units and how many decimals to show.
How does a screen reader get the pipeline?
The stages are an ordered list named "The pipeline, in order", each with a heading, its sentence, its status and its time ("Takes 2 min 10 s"). The chevrons and the share bars are decorative and hidden. Each rolling number carries its final value as hidden text, so it is read once, whole.
What happens in right-to-left languages?
The stages run from the right, the chevrons flip to point the way the pipeline goes, and times and percentages are isolated so their units stay in order. The shares and bars follow the same direction.
Related
- Pro
Architecture Flow Diagram Features
Diagrams and mapsA request path for an edge-routing layer: five hops on one wire with a dot travelling along it, the time each hop spends under it, and a latency-budget bar that sums them.
- Pro
Sankey Flow Diagram Features
Diagrams and mapsA Sankey of an event router's flows: three sources, four destinations and curved bands whose width is the events they carry, with nodes you hover, focus or press to follow a stream.
- Pro
Metro Line Journey Diagram Features
Diagrams and mapsA 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
Metric Hero Strip Features
Metrics and chartsFour metric-over-feature columns for a data-pipeline tool: a giant tabular figure and label, then the feature that makes it true, in one divided band under a centred header.
- Pro
Split Architecture Diagram Hero
Diagrams and mapsA reverse split hero for an infrastructure platform: a service topology on a tinted canvas flush with the start rail, six icon nodes, a travelling request and an inspector, beside a headline, a Shine Button and three ticks.
- Pro
Circular Orbit Layout Features
Diagrams and mapsA hub and six connections around a solid ring for an integration hub: hovering, focusing or tapping a node writes its title and sentence into the hub.