Card
A container that groups content about one object, and the most over-applied component in modern UI.
Definition
A card groups related content about a single entity into a bounded region. It works through common region, which makes it a strong grouping signal and a heavy visual element.
Craft convention. True because the industry converged on it. Breaking it costs familiarity, not correctness.
On this plate
Reach for this when
- Grouping content about independent objects.
- Grids of comparable items with mixed content types.
Common mistakes
- Cards used for everything.
- Nested interactive elements.
- Inconsistent padding or content order.
When a card is the wrong choice
- For a list of similar rows, where dividers are lighter and allow more density.
- For a single item, where the boundary adds nothing.
- For content that needs to be compared, where a table aligns attributes better.
- When every element on the page is already a card, at which point the grouping signal is exhausted.
Consistency requirements
- Identical internal padding across a set, or the grid stops reading as a grid.
- The same content in the same position in every card, so scanning is a single sweep.
- A defined behaviour for missing optional content, so cards do not collapse unevenly.
- Equal heights within a row, with a defined truncation rule for long text.
Deciding how a card behaves
| Card holds | Behaviour | Requirement |
|---|---|---|
| One destination | The whole card is a link | One anchor, with the title as its text |
| A destination and secondary actions | Title links, actions sit above it | The actions need their own accessible names |
| No destination at all | Not interactive | Then it must not look pressable |
| A selection | The card is a label for a control | A real checkbox or radio underneath |
In practice
- i.
The card with four links inside it
Nested interactive elementsA whole-card link containing a tag link, an author link and a bookmark button produces overlapping targets, unpredictable middle-click behaviour and four confusing stops for a keyboard user. One primary link, with the rest layered above it, is the pattern that works.
- ii.
Cards as the default container
When they cost more than they giveA page of eleven cards, each with a border and a shadow, groups nothing because everything is grouped. Cards are a strong grouping signal, and their strength depends on being used sparingly.
Local chart
CMP·022 · Region III · Grid E2
This entry and the entries it is stated to connect with. Each line is labelled with what the connection means.
Continue from here
Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.
Applies when you are designing
Principles behind this
The reasoning this solution is an application of.
- Common RegionFND·006 · UI foundation
- ContainersFND·041 · UI foundation
- DensityFND·016 · UI foundation
- ElevationFND·048 · UI foundation
- GridsFND·039 · UI foundation
- ShadowsFND·049 · UI foundation
- ShapeFND·046 · UI foundation
- SimilarityFND·005 · UI foundation
Often used with
These usually appear in the same screen or the same decision.
Alternative approach
A different answer to the same problem, with a different cost.
- Data TableCMP·025 · Component
Tables compare across records. Cards suit one record at a time on small screens.