Out of the discussion in this issue and elsewhere it has become clear that some of the required features are quite intricate, and to capture all the details it's probably going to be best to break them down into separate issues. In those issues each feature can be explored abstractly, and contextually as required.

• Data views: View options #55094
• Data views: Pagination #55095
• Table: Quick-actions #55096
  • Data views: Expanding quick-actions for Pages #55628
  • Quick actions for templates
• Data view: Bulk actions #55098
• Data view: Search & Filtering #55100
• Data views: quick-editing #55101
• Data view: Custom field creation #55102
• Data views: Grid layout refinements #55733
• Showcase hierarchy in table/list layout #55957
• Data views: Editing default views can lead to awkward results #56204
• Exporting
• Empty states
• Loading state
• Managing custom views (edit, save, duplicate, rename)

Original issue

In https://github.com//pull/50766 a `Table` component was introduced, facilitating a consistent way to render the template and template part management views in the site editor:

As we consider the broader admin experience it could be a good time to expand this component so that it is able to entertain various capabilities and contexts:

Contexts	Capabilities
Templates #50430	Search
Patterns	Filtering
Posts / Pages / Comments	Sorting / Ordering
Users	Bulk actions
Media	Column toggling
Themes	Inline editing
Plugins	List / Grid toggle
Tools
Sites (multisite)

In this issue we can explore designs for a 'kitchen sink' application illustrating the full scope of the component, then concentrate on specific contexts in dedicated issues.

---

Figma.