Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Spec Sheet Infrastructure About Block for React

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.

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 layer spec sheet for React with Base UI, written for Moorwell, a fictional managed-hosting company. Under a compact header band, the four layers a site runs on (Compute, Network, Storage, Backups) are a list of single-choice toggles at the start; at the end, behind a split divider, a framed sheet shows the chosen layer: a title, one sentence and a description list of four specs (what kind of provider runs it, where it lives, how it is copied, and its uptime over the last twelve months). The downtime a year is worked out from the uptime, so the two never disagree. Every layer's sheet is stacked, unseen, under the open one, so choosing a layer never moves the page. On a phone the list becomes a row of chips above the sheet. It's built from Toggle Group and Guides, with CSS transitions for the entrance and your theme's tokens for every colour. For hosting, platform and infrastructure companies that want a buyer to check the facts layer by layer. The specs are example data.

FAQ

How do I change the layers and their specs?

Edit LAYERS at the top of the file: each layer has a label and a summary for the list, a title and a sentence for the sheet, and four specs (provider, regions, redundancy and uptime, a number in percent). The sheet's downtime line is computed from uptime by downtimeOf, in minutes under two hours and in hours above. Add a layer and it appears in the list and in the unseen stack that holds the height.

How is the list chosen with a keyboard or a screen reader?

The layers are a Toggle Group with one layer always chosen: pressing the chosen one keeps it, pressing another moves the choice, and the sheet is announced politely when it changes. Tab moves into the list and the arrow keys move between layers (Up and Down, as the list is vertical on a wide screen), and Enter or Space chooses one. Each toggle reads as a name and its summary; the specs are a real description list, so a screen reader hears "Uptime, last 12 months" followed by the figure.

Why does the page never move when I choose a layer?

Every layer's sheet is rendered in the same grid cell, and all but the open one are invisible, inert and hidden from assistive technology. The cell is as tall as the tallest sheet, so choosing a layer only swaps what is visible. The open sheet fades in again each time it changes, and not at all with reduced motion.

Why does the sheet name a kind of provider and not a provider?

Saying "Two independent carriers at every site" tells a buyer what they need to judge redundancy, and stays true when a contract changes. Put a company's real names there if your page should name them.

How does it fit on a phone?

The header comes first, then the four layers as a wrapping row of chips (the one-line summaries are left out), then the sheet with a rule above it. The specs drop their two-column layout and show each label above its value. Nothing scrolls sideways at 320 pixels, and in a right-to-left layout the list and the divider move to the other side.

What moves, and what happens with reduced motion?

The header and the sheet fade up once on load, and the sheet fades in again when the layer changes. With reduced motion every transition is off and the sheet changes at once.

  • Pro

    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.

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

    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.

  • Pro

    Response Times Matrix About

    Support and contact

    Support promises as a framed matrix of channels by plan, each cell giving the promised first response and last quarter's median, with the Enterprise column ringed and a status dot per channel.

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