Skip to content

Building Blocks

css/modules/bricks/

Screens in this system are assembled from a deliberately small set of semantic building blocks. Three carry the weight:

<section>
The semantic grouping block. It thematically unites primarily textual content and sets the vertical rhythm between page parts.
.card
A narrative surface — authorial, human, story-like content that wants to stand slightly apart from the page. See Cards.
.panel
The data surface — the stricter sibling for system-facing, structured, metric-heavy content. See Panels; its companion, the Legend, keys colour-coded data, and Stats set its KPI figures.

The important idea is what is not here. There is no grid component, no deck component, no positioning component. Those jobs belong to the utility layers — layout & grid, alignment, spacing, and positioning. A handful of surfaces plus the utilities compose any screen, so reaching for a brand-new class should be rare and deliberate.

Card vs Panel

Both are surfaces, but they answer different questions, and keeping them separate keeps the intent of a screen legible.

.card — narrative

Authorial, human, story-like. An article preview, a person, a project, a pricing block, a visual fragment.

.panel — data

System-facing, structured, scannable. A KPI, a status block, settings, a log, a metrics readout.

The rule: If a human authored it and it reads as content, it is a .card. If a system produced it and it reads as data, it is a .panel. When unsure, ask whether the block would feel at home in an article (card) or on a dashboard (panel). A chart is data: its frame is a panel, and the prose that explains it stays text around it.
.card .panel
Background Paints its own: --surface-current, light gray; .card-inverted is dark None: the surface behind shows through, so it works on any page or card
Padding None — add a utility (.padding-lg) Built in: 16px; in a caption-width box each side that hangs takes the outdent (32px); .panel--flush removes it
Border None — add .bordered None — add .panel--bordered
Structure Free; a header is a block with .border-bottom __header / __body / __footer, divided by thin rules
Layout Flex column: children stack Block; with parts, a flex column whose body takes the free height
Many of them .card-grid, .feature-row .panel-grid: footers line up across a row

Section

css/modules/bricks/_sections.scss

The section is the basic semantic block, thematically uniting primarily text elements. Think of it as the foundation piece in your construction set. It is visually separated with margin-bottom: var(--space-lg):

Section

Wide Background

Sometimes a section needs more canvas than the normal reading column allows: a full-bleed image, a contextual band, or a wide visual insert. .wide-background breaks the outer section to the viewport edge, while .wide-background-text-content-wrapper brings inner prose back to the normal line.

A full-bleed band with a disciplined inner text line

The outer surface can carry color, imagery, or other wide media. The inner wrapper returns content to the same reading track the rest of the page uses, so a dramatic section does not force the prose to become chaotic.

Feature Row

When a set of features, offerings, or highlights reads better as a scannable horizontal strip than as a wrapping grid, .feature-row lays its .feature-row__item children out in a single row that scrolls sideways instead of squashing. Each item is a flex column — media on top, copy below — pinned to a fixed responsive width (clamp(280px, 30vw, 420px)), so the cards keep a comfortable size and the row simply runs past the edge when there are more than fit.

Read the table

Surface the one number that changes the next move — not the whole hand.

Stay flexible

Match it to your brand without bending the underlying presentation logic.

Cut the noise

Every tile earns its place, or it doesn’t get one.

Use it for a small, deliberate set of features — not as a generic carousel. If the items want a uniform, wrapping arrangement instead of a horizontal scroll, reach for .card-grid instead.