Variant 01
Table structure
The low-level parts preserve native table semantics.
View content
| Project | Owner |
|---|---|
| Research workspace | Mika Lee |
Components
Components / organisms
A table shows many similar records in rows and columns, with sorting, filtering and selection.
Usage
Use a table when people need to compare values across similar records. Keep filters and actions next to the table. On small screens, let the table scroll sideways so its rows and columns stay intact.
02 / examples
Variant 01
The low-level parts preserve native table semantics.
View content
| Project | Owner |
|---|---|
| Research workspace | Mika Lee |
Variant 02
One cell, in the shapes a product actually needs.
View content
| Research workspace |
| Research workspaceUpdated today |
| Research workspace |
| Research workspace |
| Research workspaceUpdated today |
Variant 03
A higher-level table with filtering, sorting, and row selection.
View content
8 of 8 items
| Select | Project | Owner | Status | Due | Actions | |
|---|---|---|---|---|---|---|
| Approval flowDS-107 | Customer portal | Aino Salmi | 15 Sep | |||
| Audit logDS-101 | Reporting | Sofia Heikkinen | 2 Sep | |||
| Billing exportDS-104 | Finance tools | Sofia Heikkinen | 16 Sep | |||
| Data importDS-106 | Reporting | Oskar Niemi | 12 Sep | |||
| Notification settingsDS-103 | Mobile app | Aino Salmi | 30 Sep | |||
| Onboarding checklistDS-102 | Mobile app | Oskar Niemi | 19 Sep | |||
| Permission modelDS-105 | Customer portal | Mika Lee | 22 Sep | |||
| Research workspaceDS-108 | Customer portal | Mika Lee | 18 Sep |
Showing 1–8 of 24 items
Variant 04
The same data pattern inside a narrower product surface.
View content
8 of 8 items
| Select | Owner | Status | Actions | |
|---|---|---|---|---|
| Approval flowDS-107 | Aino Salmi | |||
| Audit logDS-101 | Sofia Heikkinen | |||
| Billing exportDS-104 | Sofia Heikkinen | |||
| Data importDS-106 | Oskar Niemi | |||
| Notification settingsDS-103 | Aino Salmi | |||
| Onboarding checklistDS-102 | Oskar Niemi | |||
| Permission modelDS-105 | Mika Lee | |||
| Research workspaceDS-108 | Mika Lee |
Showing 1–8 of 24 items
03 / contract
A table shows many similar records in rows and columns, so people can compare values. It is built from the real table elements, and the Table, row, header and cell parts can be used on their own when the markup needs to be customised. The data table builds on them with sorting, filtering and row selection, and it covers empty and loading states.
A cell can carry a decorative icon, a line of supporting text or a form control, and a form control inside a cell always comes from the form controls so that it looks and works the same everywhere.
04 / accessibility
Tables use scoped column and row headers and a caption, which can be visually hidden, so that screen readers can describe where a value sits. Every selection control has a label that names its row, such as select the project named in that row.
Genuinely tabular data stays in a table instead of being rebuilt with a grid layout, so the structure is not lost for people who do not see the layout. On small screens the table scrolls sideways so that rows and columns remain intact.