-
Notifications
You must be signed in to change notification settings - Fork 274
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blueprints: Support Command Palette #934
Comments
That would be neat! With how the command palette works today, I'm not sure how useful it might be though as we're not currently able to see previous commands run or have them listed out in order. In my mind, I'm imagining a quick way to use the command palette to enable different experiments in GB, install/activate a specific theme, install/activate GB plugin, etc. I'd want to see what I'd already done though to ensure it's doing what I wanted. |
Some examples that previously came up where this could tie in was deep linking into editor screens, eg displaying the Style Book, or showing the Font Library modal after launching a Playground. |
Related: WordPress/gutenberg#57312 |
Deep linking use cases
With competing CMS's trying to take market share, usability is a major driving force to adoption. Following the conversation, this is something I'd like to take a try at in the Playground Action steps
added to the master list for Playground Stellar ideas!! |
It would be useful to be able to run command palette tasks as a part of preparing the WordPress instance. I'm interested in use-cases and what kind of setups would that unlock – what do you think @annezazu @ironprogrammer @juanmaguitar
The text was updated successfully, but these errors were encountered: