Skip to main content
A titled Zone 1 Status card containing a temperature readout, a status indicator, and a Details button

A card grouping an asset's readout, status, and action into one unit on the panel grid

Containers group other components. Use them when a panel grows beyond a simple grid — to cluster a machine’s readouts under one title or split a screen into tabs.
Like trays on a workbench. The bench grid holds the trays in place; each tray keeps one job’s tools together so they move as a unit.

Two containers are available today: card for grouping, tabs for splitting.

Card

Groups child components under a title.
A titled card with one readout inside:
A titled Zone 1 Status card containing a temperature readout

A titled card grouping a single temperature readout

Tabs

Each tab holds its own components — useful for Overview / Analytics / Settings splits on one screen.
In the current HUB build, tab headers show the inner component name rather than the ADD TAB title. The structure below matches the spec syntax; tab labelling is tracked as a known issue.
A tabbed container switching between sub-views on one panel

A tab strip switching between sub-views on one panel (current build labels tabs from their content)

Card vs. grid position?

Use grid positioning (AT COLUMN/ROW) when components are independent readouts. Use a card when components belong to the same asset and should travel together — a card moves as one unit when you rearrange the panel. See Mixing layouts with cards for a complete panel that combines both.

Next Steps

Display components

The readouts you place inside cards and tabs.

Common patterns

Full panels that combine containers with live data.
Last modified on August 28, 2026