Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Architecture Flow Diagram Features Block for React

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.

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 request-path features section for React with Base UI. Five hops (Client, Edge, Auth, Service, Store) sit in cells that share their hairlines, each a node on one wire with a chevron where it hands over to the next; a single dot hops from node to node along the wire. Under every node, a tile gives the time the request spends there and its share of the budget; across the foot, a stacked bar sets the five times side by side so the largest, Service, stands out in the text colour. On a phone the cells become a column of rows on a vertical wire and the bar drops its labels. It's built from Guides and Badge, with inline SVG and CSS for everything else, and it follows your theme's tokens. For infrastructure products, gateways, CDNs and any product whose pitch is a path that is fast at every step.

FAQ

How do I change the hops and their times?

Edit HOPS at the top of the file: each hop has a name, a caption, an icon and ms, its time at the median. The total, each hop's share of the budget, the bar's segment widths and the sentence under the bar are all worked out from that list, so they always agree. The layout is built for five hops across.

How does the dot move, and can I stop it?

The dot is drawn with SMIL animation inside each cell's SVG: each cell's dot starts 0.7 seconds after the one before and rests for the rest of a 3.5-second loop, so one dot seems to travel the whole path. It's hidden when the visitor prefers reduced motion, and the diagram reads the same without it. Delete the circle in Wire to remove it.

How does a screen reader get the diagram?

The diagram is an ordered list named "The request path". Each hop is a list item with a heading and a caption, and its time and share are a term and its value, announced as "Time spent at Edge, 6 ms". The wire, the chevrons and the bar are hidden from assistive technology, because the list says everything they draw.

How does it fit on a phone?

Below md the five cells stack as rows: the icon and name at the start, the time at the end, on a vertical wire through the icons. The bar keeps its proportions without the names inside the segments, and the sentence under it names the largest hop. Nothing scrolls sideways at 320 pixels.

Does it mirror in right-to-left languages?

No, on purpose: a request path is a picture of order in space, so the diagram keeps its direction (dir="ltr") and reads Client to Store whichever way the page runs. Values such as "6 ms" and "15% of the budget" are wrapped in bdi so they keep their order.

Why is there no button?

The diagram is the feature, so the block has no call to action. Add a Shine Button to the header row if your page wants one there.

  • 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 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.

  • Pro

    A 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

    A 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

    A bento of five features for an issue tracker, each cell drawn as the product at work: a live board with teammates' cursors, a pull request, a burndown, a triage rule and a typed SDK, in cells that share their hairlines.

  • Pro

    A 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.