This document keeps track of all the work and tasks to extend thel DataForm and DataViews components (Fields). These components are used to power all/most screens in Admin Redesign (side editor first and expanded to more screens later). Users should be able to extend these screens in all sort of ways. We should able to allow field, actions registration/unregistration, custom layouts, default layouts for lists and forms and a lot more.

CPT / Entity based extensibility APIs

The extensibility APIs should be consistent, and PHP first. you should be able to do 80% of the modification using simple PHP APIs and for very specific/advanced cases be able to write React components to extend the default behavior. Most of the following APIs involve extending register_post_type/register_taxonomy function with new possibilities. But for WordPress entities that are not post types or taxonomies (users, comments...), a similar PHP API is going to be needed.

• Support defining the support layouts per entity (list, table, grid)
• Support defining the default fields and default configuration for each layout per entity.
• Support defining the default quick edit (form) fields for each entity.
• Support defining the default rendering mode for each entity (template-locked vs post only).
• Support registering additional fields per entity.
• Support registering additional actions per entity. DataViews: Bootstrap Actions Extensibility API #62052
• Support registering "default views" per entity.

More global extensibility APIs.

• Support registering custom DataViews layouts.
• Support registering custom Field Types.
• Support registering custom Field Controls.

Common

• Versioning the APIs DataViews: Preparation for making the API stable. #67274

Low priority

• Audit the action "ids" and bring some consistency there.
• Audit the action code bases and improve things like notices and error handling (most of these can be absorbed into the framework I think)