Design Principle
Admin work often moves from filtered lists into detail handling, and both views must share state and action semantics.
Principle
Admin work often moves from filtered lists into detail handling, and both views must share state and action semantics.
Design action
Lists handle filtering, sorting, bulk action, and status overview; details handle identity, history, key fields, related objects, and contextual actions.
Examples
Positive example: CRM, orders, users, moderation, tickets, and knowledge item management. Counterexample: The detail page has no path back to filtered results.
Apply when
CRM, orders, users, moderation, tickets, and knowledge item management. Users need to judge state, scope, risk, or next action quickly.
Source notes
Source note: Synthesized from GOV.UK, Carbon, Polaris, Atlassian, Design.Systems, Design Systems Repo, and product-pattern libraries.
Agent Directive
Lists handle filtering, sorting, bulk action, and status overview; details handle identity, history, key fields, related objects, and contextual actions.