Everything in its slightly peculiar place.
Wrapped labels, longer descriptions and different values share real parent tracks. No fixed heights. No flattened markup.
Cards that agree on where the buttons go.
A small improvement
A practical addition to the plan.
An ambitious and rather elaborate expedition
A longer description keeps important context visible. Neighboring cards still line up, all the way down to their actions.
A backup kettle
The original kettle has asked for a deputy.
Labels, controls and hints share three rows.
Dossiers share body and action columns.
Research lead
A longer explanation stays aligned with the next record's action.
Operations lead
Coordinate the team.
A season cover pairs flexible copy with artwork.
Small beginnings. Great company.
The text determines the height; the image fills its own track.
- Standing
- #3 / 12
- League
- Neighborhood
Explore paper surfaces, native selects and pace buttons →
How these layouts work
Cards share four rows: heading, description, body and footer. Fields share three: label, control and hint. Stat tiles share label, value and detail rows. Each nested component inherits its parent tracks through subgrid, with container queries adapting the number of columns. Native details animates its intrinsic content size where supported.