shadcn.io is not affiliated with official shadcn/ui
Alternating Stripe Sections Features Block for React
Three tinted stripes for a CI platform: pipeline runs beside their copy, an environments table beside its copy, then a centred statement over a three-cell grid of build figures.
Installation
Overview
A features section for React with Base UI made of full-width stripes. Three bands run between the page's rails, each with its rule and + marks drawn by Guides: the first and third are tinted a step darker, the middle one plain. The first stripe puts its copy beside a list of pipeline runs, each with a dot, a commit message, a state written in words and a time. The second mirrors it, with an environments table (name, version, deploy time, health). The third is a centred statement over a three-cell grid of build figures. The drawings are built from the Status dot, Badge and theme tokens, with a destructive dot only on the one failed run. For CI, deploy and developer-platform products that want a long, calm page with a rhythm of bands.
FAQ
How do I change the runs, environments and figures?
Edit RUNS, ENVIRONMENTS and FIGURES at the top of the file. A run's state is one of passed, running, queued or failed and picks its dot and its label; an environment's ok flag picks a filled dot or a ring. The figures are plain strings, written in a bdi element so units keep their order in right-to-left layouts.
Why is only one run red?
State is carried by words and by the shape of the dot (filled, ring, destructive), never by colour alone, and the status colours stay rare so a failure is easy to spot. Passed runs use the foreground dot, queued and running runs a ring, and the one failed run uses the destructive status token.
How are the stripes tinted?
The tint is on each stripe, inside the page column, and the column itself has no background, so the rails and the top rule stay clean. Each stripe's rule comes from Guides rather than a border, so the + marks land on the line. Pass tinted to a stripe to tint it.
Are the drawings interactive?
No. The runs list and the environments table are pictures of the product, hidden from assistive technology and inert, so nothing in them takes focus. The heading and sentence beside each say what it shows, and the link under it is the only control.
Related
- Pro
Alternating Rows Features
Alternating rowsTwo plain alternating rows for a design-system kit in one box of shared hairlines: a permissions card with three toggles, and a notification card over a stack of avatars.
- Pro
Alternating Mockup Rows Features
Alternating rowsThree alternating bands for a support back office, each pairing a sentence with a browser window that holds a different admin screen: a filtered ticket table, a settings form with toggles and a weekly chart with its legend.
- Pro
Alternating Code Block Rows Features
Alternating rowsThree alternating bands for a typed event-stream client, each pairing a sentence with a code window that draws a different artifact: a call with its autocomplete popover, a config file with one line marked, and a command's output.
- Pro
Alternating Device Frame Rows Features
Alternating rowsTwo alternating rows for a transit app, each pairing a sentence with a phone drawn as a ring on a hairline floor: the trip planner with line chips and the live arrivals with countdowns.
- Pro
Zigzag Screenshot Rows Features
Alternating rowsFour alternating feature rows for a team workspace, each with a badge, a title, three ticks and a framed drawing: a graph of linked docs, a rule builder, a global search and a live document.
- Pro
Split Mockup Icon Checklist Features
Split with mockupA reverse split features section for a planning canvas: a square canvas in a card in card with linked cards and two named cursors, beside four icon rows and two buttons.