-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Classic themes and appearance-tools issues and blockers #56131
Copy link
Copy link
Closed
Labels
[Feature] Design ToolsTools that impact the appearance of blocks both to expand the number of tools and improve the experiTools that impact the appearance of blocks both to expand the number of tools and improve the experi[Type] Tracking IssueTactical breakdown of efforts across the codebase and/or tied to Overview issues.Tactical breakdown of efforts across the codebase and/or tied to Overview issues.has dev notewhen dev note is done (for upcoming WordPress release)when dev note is done (for upcoming WordPress release)
Metadata
Metadata
Assignees
Labels
[Feature] Design ToolsTools that impact the appearance of blocks both to expand the number of tools and improve the experiTools that impact the appearance of blocks both to expand the number of tools and improve the experi[Type] Tracking IssueTactical breakdown of efforts across the codebase and/or tied to Overview issues.Tactical breakdown of efforts across the codebase and/or tied to Overview issues.has dev notewhen dev note is done (for upcoming WordPress release)when dev note is done (for upcoming WordPress release)
Type
Fields
Give feedbackNo fields configured for issues without a type.
There have been a few efforts to enable
appearance-toolsin Classic themes, with work more recently explored in #47451 and #56130 to unblock this feature. This issue is to gather together to-do list items for points of friction, things to test, or things to resolve in order for the feature to feel stable and useful to use (and to be able to be made available in core). If there is already an issue that's tracking this, we can close this one out.Tasks / points of friction
To test, add
add_theme_support( 'appearance-tools' );to a Classic theme.Deprioritised issues (things noticed during testing but that aren't blockers)
PRs / WIPs