When to use

The console is the application itself — the surface an operator lives in. It frames the work with an AppShell: a staging EnvStrip so nobody mistakes test data for production, a top bar with system health, and a persistent sidebar. Inside, a KPI row summarizes the state of the world, and a server-driven DataTable is the workhorse. Rows open a detail Sheet rather than navigating away, so the operator never loses their place.

Use it for every authenticated, data-dense screen. Marketing lives in the home and product patterns; this is where the product is operated.

Structure

Design the five states

A console table is never just its populated state. DataTable renders all five natively — design copy for each before you ship:

• Loading — skeleton rows via loading, so layout never jumps.
• Populated — the default; keep the summary count honest (server total, not page length).
• Empty — a purposeful emptySlot that tells the operator what to do next, not a blank grid.
• Error — an error payload with a copyable debugId and a retry.
• Selection — the selection bar with capability-gated bulk actions.

Key components

Open any component to read its full API and live examples.