Blocks

Blocks you can drop into a real product.

Start from a complete interaction, then strip it back to the pieces your product actually needs. Every block below is running: real components, real state, nothing screenshotted. They're filed by the job they do rather than by which components they happen to use, because that's how you'll be looking for them.

118 blocks 6 surfaces 29 use cases

Operations

Interactive shells and control surfaces for running services, reviewing work, and making changes with context intact. All workspace data is illustrative.

Sidebar operations console

An illustrative service console with live navigation, operational metrics, deployments, logs, and account tools.

Overview

p95 latency
127ms
-0.5%
requests
4.77M/day
-0.5%
error rate
0.21%
-0.5%
Requests / month
SeriesXY
Area042
Area158
Area251
Area374
Area488
Area579
Area696
Area7111
Area8103
Area9121
Area10134
Area11128

Split inbox workspace

An illustrative team inbox with folders, read state, starring, archiving, and an inline reply surface.

Parity gate is red on the Svelte adapterGHGrace Hopper · 09:14

The keyboard layer diverged after the focus-trap change landed on Tuesday. Svelte is returning focus to the trigger one tick later than the other four, so the assertion on the restored activeElement fails.

It's a real divergence rather than a flaky test. I can reproduce it by hand. I would rather we hold the release than record it as an intentional difference.

Top-nav service workspace

An illustrative service directory that filters rows, exposes activity and usage, and protects deployment confirmation.

Acme Platformproduction
Data table
State
edge-cachestagingplatform19mspaused
docsprodplatform64mslive
webprodgrowth88mslive
ledger-apiprodpayments142mslive
searchstaginggrowth204mslive
workerprodpayments311msrolling
6 of 6

Service settings workspace

An illustrative settings shell with dirty-state feedback, revert and save actions, access roles, and empty history.

General
Lowercase, hyphen-separated.
0 / 140

Deployment control panel

A rollout review surface that joins service readiness, blast radius, and pause policy before any action is allowed.

Review a production rollout

Compare service readiness, choose blast radius, and record the safety posture before any deployment begins.

Illustrative dataScenario only; the controls never deploy.
First cohort2 of 20 replicas
Readiness evidencesample workspace
Data table
Readiness
web1c09aagrowth88msready
ledger-api8f21c4payments142msready
searchc72d18growth204msblocked
worker4b7e02platform311mswatch

Why these aren't registry items

A component is the stable bit: one contract, checked across five adapters. A block is one particular arrangement of those components, and it carries state and data that really belong to whatever product is using it. Those choices won't survive contact with your app, so shipping them as registry items would only promise a stability they don't have.

Install the primitives, adapt the pattern

Blocks are patterns, not packages: copy the layout and state from here, then install the primitives each one leans on.

pnpm dlx grassroot add ui/select