DataViews component

[youknowriad]

In light of the discussions in #53233 #50430 it became clear that we need to work new powerful views, that support several features:

• Rendering table layouts to show posts, pages, templates,.. CPTs.
• Rendering grid/gallery layouts to show the same entities (or other entities, think patterns, media) in a Grid format.
• Allow a high level of customizations: Filtering, searching, pagination, grouping, sorting, hiding and showing fields/columns...
• Allow actions and bulk actions.
• Potentially allow users to create and save custom views.
• Potentially allow users to edit data/content inline.
• Potentially allow users to create new fields inline.
• Offer strong extensibility APIs for plugins to be able to customize everything: adding new layouts, adding new fields, hiding/showing fields, adding actions and bulk actions.
• Potentially have the ability to offer the same kind of views for frontend (new connected blocks with filtering/customization capabilities)

We might not get to everything right away but I'm creating this issue to track and coordinate the initial steps (non exhaustive) for this ambitious undertaking.

See also issues and PRs tagged with the [Feature] Data Views label.

DataViews component

• Support defining actions per row. #55096
• Add support for reordering fields. #63414
• Implement a new layout (or view type): Grid/Gallery.
• Iterations on the grid layout: #56643
• Implement the list layout. #56746
• List View Iterations #56983 #57116 #57578 #57523 #56602 #57649 #56746
• Keyboard navigation: potentially use arrow up/down to navigate through the list. #57895 #59637
• Iterations on search and filtering #55905 #60696 #63152
• Bulk actions #55098 #63193 #63150
• Field registration API
• Pagination #55095 #55937 #55164 #63675
• View config iterations #63195 #63872
• Implement custom views.
• Support density #60630 #66312
• Support different fields formats #60284 #60083
• Accessibility iterations #56396 #56853 #56441 #57341 #56001 #57978 #58977
• Some Bug fixes #56154 #60708 #60709
• Performance #63151

DataViews implementations

• Pages DataViews
• Templates DataViews
• Patterns and template parts DataViews

Next steps

• Unify Layouts config #67391
• Visualize page hierarchy in table/list layout (Hierarchy support for dataviews) #55957
• Next steps for search and filtering #55100

Medium priority

• General polish #60847 #59832 #65234 #63719 [DataViews: make actions column sticky in table layout so they are visible #65086)(https://github.com/DataViews: make actions column sticky in table layout so they are visible #65086)
• Persisting view configs #57860 #57669
• Implement a group by field. #57967
• Better keyboard accessibility #56330 #56328

Lower priority

• Kanban Layout #57024
• Custom field creation, maybe ? #55102
• Table summary footer #57270
• Support aspect ratio configuration #60891
• Support right click #59608
• Support column alignments #66623
• Custom views next steps (admin menu placement, visibility, persistence) #56205
• Support pinning columns #64679
• Contextual order control #65831

[oandregal]

I've updated a bit the issue description pointing to other places where we're tracking goals for WordPress 6.8 and adding a section about "theming", that groups together related issues:

[youknowriad]

Hey folks! this issue was becoming a bit hard to follow and scan. I did some triage and updated the issue. I tried to keep it contained and easy to scan and help people understand the priorities... Let me know if you think I've missed anything.

[jameskoster]

A couple to consider for low prio:

• DataViews: make actions column sticky in table layout so they are visible #65086
• Data views: allow users/consumers to pin columns in table layout  #64679
• Data Views: Contextual order control #65831

[youknowriad]

Thanks @jameskoster I added them to the list.