Command Palette Overview #66648
Labels
[Type] Comand Palette
[Type] Overview
Comprehensive, high level view of an area of focus often with multiple tracking issues
It's been more than a year since the Command Palette was first introduced in WordPress 6.3. The number of commands has grown in subsequent releases, and there are a handful of proposals to evolve the Command Palette in different ways. This issue aims to summarize all these efforts.
Palette availability
Currently the Command Palette only works inside the different block editors. There is a pair of issue and PR addressing this so that the Command Palette can be invoked everywhere in the wp-admin and the frontend:
Command organization
Right now, all command search results appear together. As the number of results grows due to adding more commands grows or having lots of content related to the searches, this makes it harder to find the right command and, in general, understand the results.
For example, if you type
a
in the Command Palette, you will get a mix of results like adding new post/pages, navigating to templates or to specific pages that contain the lettera
in their name, relying only on icons to explain the purpose of the command.There are many ways to mitigate that, from improving the context and icons of the results to grouping the commands by type.
Command context
Apart from structuring the commands better, as the available commands grow in both directions with site-wide admin commands and niche, context-specific ones, the results need to take the context more into account. There is currently an in-depth discussion of site/page/template editing contextual commands at #50407
New commands
Considering the command context a key feature of the Command Palette usability, the following command suggestions are grouped by the context in which they should appear. NOTE: This is a work in progress, and the list will grow!
Available everywhere
Available in any block editor
Available in site editor
Available when editing a post/page
Extensibility and Developer Experience
The text was updated successfully, but these errors were encountered: