# Workspace pages

Workspace pages use an editorial hierarchy: clear page identity on the canvas, then calm panels containing the task. The surrounding shell provides global location, so content should not repeat information already visible in navigation or detail cards.

## Page header

1. Show a concise title and one useful sentence describing the user's task or the collection's scope.
2. Keep primary page actions aligned opposite the title on wide screens and below it on narrow screens.
3. Do not repeat a record type as a subtitle when the same type is already present in the adjacent detail card.
4. A record summary may use a few lines when it adds meaning. Do not truncate useful explanatory copy merely to force a single-line header.
5. Keep status with the record summary or workflow card when that is where the state is interpreted; avoid an isolated badge between the title and metadata.

## Registry card

- Use one panel containing search, filters, table, empty state, and pagination.
- Place search at the leading edge and Filters at the trailing edge. Stack them only when width requires it.
- Keep header labels aligned with their data columns. A date value must have a date header; do not let a multiline header drift into the adjacent column.
- Use 48px minimum rows, restrained separators, no decorative zebra striping, and one clear primary destination per row.
- Keep the result range and pagination in a stable footer. Do not leave a large empty footer when only the range is present.

## Filter dialog

- Use a modal when several structured filters need labels, descriptions, or enough space to compare values.
- The title describes the operation, followed by one short explanatory sentence.
- Each control keeps a persistent label. Compact labelled selects may place the label and value in one control only when their visual and accessible separation remains clear.
- Footer actions are Reset, Cancel, then Apply filters. Apply is primary; Reset is visually quiet and must not close the dialog unless the product explicitly says so.
- Preserve draft filter choices until Apply. Cancel restores the last applied state.

## Forms

- Add a subtitle beneath the page title when it clarifies the outcome or retained record.
- Keep the form in one panel and constrain the field column rather than stretching controls across the viewport.
- Group related fields in rows only when labels, help, and errors remain readable. Stack on smaller screens.
- Place the submit action first and Cancel or Back second after a subtle section divider.

## Empty collections

Center the empty-state message vertically and horizontally within a panel with a useful minimum height. Preserve equal visual space above and below the message. Follow [empty and loading state guidance](./empty-loading-states.md) for first-use versus filtered states.

## Responsive behavior

Panels become full-width before labels become cramped. Tables may scroll horizontally; cards and filter controls stack. Reading order and action priority remain unchanged.