# Card

A card groups a concise set of information and actions about one object or concept into a reusable visual container.

- Type: artifact
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-10-06
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/card/>)

## What it means

A card is a bounded content container representing a single entity, destination, or task. It commonly combines a heading, metadata, media, status, and a small number of actions. A card may be static, link to details, support selection, or contain separate controls, but those interaction models should not be mixed ambiguously.

## Why it matters

Cards create repeatable scanning units for varied content and adapt well to responsive grids or lists. Their flexibility can also produce inconsistent hierarchy and excessive containers unless teams constrain content and behavior.

## When to use it

Use cards for repeated objects whose essential attributes and actions can be understood independently, such as projects or products. Use a table for dense cross-row comparison, a plain list for simple homogeneous items, and an unboxed content layout when grouping is already obvious.

## How it works

1. Define the object or concept represented and the minimum information needed to recognize and assess it.
2. Establish a consistent hierarchy for title, supporting details, status, media, and actions.
3. Choose one interaction model: static container, single destination, selectable item, or container with separate controls.
4. Make focus order, hover, selection, loading, and error states match that model.
5. Test variable content, whole-card activation, nested controls, responsive reflow, keyboard access, and screen-reader structure.

## A practical example

A project portfolio uses cards with project name, owner, health status, next milestone, and a View project link. The card itself is not a second competing click target, while a separate overflow menu holds Rename and Archive actions with clear focus order.

## Where it breaks

Cards use more space than compact lists or tables, can hide comparison patterns, and often accumulate too many actions. A grid of visually identical cards can still be difficult to scan when titles and metadata lack hierarchy.

## Common mistakes

- Making the entire card clickable while nesting other interactive controls inside it.
- Putting unrelated information in one card because it fits visually.
- Using cards for data that users primarily need to compare by column.
- Allowing variable content to create inconsistent action placement and reading order.

## Sources

1. [Cards](<https://m3.material.io/components/cards/overview>) — Material Design · Institutional design system
2. [React Card](<https://fluent2.microsoft.design/components/web/react/core/card/usage>) — Fluent 2 Design System · Institutional design system

## Related topics

- [Visual Hierarchy](<https://wiki.soroush.uk/topic/visual-hierarchy/>)
- [Data Table](<https://wiki.soroush.uk/topic/data-table/>)
- [Responsive Design](<https://wiki.soroush.uk/topic/responsive-design/>)
