Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Layered Diagram Architecture About Block for React

A layered architecture diagram for a CI platform: four bands from the edge down to the data, joined by arrows, with a numbered request path down the start side and a note that opens on each layer.

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 layered architecture diagram for React with Base UI, written for Rungwell, a fictional CI platform. At the start, a compact header and three figures; at the end, behind a split divider, a framed figure of four bands stacked from the edge down to the data (Edge, API, Services, Data). Arrows between the bands show the call going in and the result coming back, and a hairline through numbered nodes down the start side is the request's path. Each band lists the technologies it uses as badges, named for what they are, and opens a note on what the layer does and how long it may take. The diagram is greyscale: the layers differ by number, label and icon, never by colour, so it reads the same in any theme. The time budget in the figures is the sum of the four bands' budgets. It's built from Collapsible, Badge and Guides, with CSS transitions for the entrance and your theme's tokens for every colour. For technical about pages, security reviews and any page that has to show how the product is put together. The figures and budgets are example data.

FAQ

How do I change the layers, the badges and the notes?

Edit LAYERS at the top of the file: each layer has a name, a role, a note, its tech badges and a budget in milliseconds, plus the icon drawn beside its name. The numbers, the arrows and the path follow the list, and the "time budget" figure is computed from the budgets, so it always matches the bands. Four layers fit the frame; more will need a taller figure.

How does a layer open, and what does it do for a keyboard?

Each band is a Collapsible: its header is a button inside an h3, so a screen reader lists the four layers as headings and Tab, Enter and Space open and close them. The first layer starts open, and each one opens on its own, so you can compare two notes side by side. The technology badges stay visible when a layer is closed. A closed note stays in the HTML, so it can be found with the browser's search and read by crawlers.

Why are the layers not colour-coded?

A layer's colour would only be a second way of saying its number, and in a theme where the accent is light it fades. Here the numbered node, the label and the icon say which layer it is, so nothing depends on telling two greys apart. The only filled shapes are the numbered nodes on the path.

Why are the technologies generic names?

The badges say what each part is (a request cache, a job queue, an object store) rather than naming a product, so the block never advertises a vendor and stays true if you swap one. Replace them with your own stack's names if you want to show it.

How does it fit on a phone?

The header comes first and the diagram follows in a single column, each band full width with its number at the start. The three figures are left out on a phone, because the budgets are in the notes. Nothing scrolls sideways at 320 pixels, and in a right-to-left layout the path moves to the right while the arrows still point down and up.

What moves, and what happens with reduced motion?

The header and the diagram fade up once on load, and a note opens with a short height transition and its chevron turns. With reduced motion the entrance is off and a note opens at once.

  • Pro

    Spec Sheet Infrastructure About

    Security and platform

    A layer spec sheet for a managed-hosting company: a list of four infrastructure layers as single-choice toggles, and a framed sheet of specs for the chosen layer.

  • Pro

    A bill of materials for a build tool: a filter field and a framed, scrolling table of 24 technologies grouped by layer, each with a monospace version and what it is used for, with an empty state.

  • Pro

    Region Rows Data Centers About

    Security and platform

    Region rows for a bare-metal host: six regions in an accordion with a status dot and a capacity bar, each opening to its hardware, round trips to its nearest regions and audits.

  • Pro

    A flat stack ladder for an app platform: five bars from interface to infrastructure, each a step wider, linked by hover and focus to a list of what sits in every layer.

  • Pro

    A 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

    An API's reliability record: a 30-day status grid with one flagged day, the computed uptime beside it, and a framed table of endpoints with volume, p95 latency and success rate.