Blueprints: Support Command Palette

[adamziel]

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

[annezazu]

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.

[ironprogrammer]

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.

[adamziel]

Related: https://github.com/WordPress/gutenberg/issues/57312

[flexseth]

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.

Deep linking use cases

• Demo various screens in the WordPress CMS to a potential new client
  • change fonts
  • color schemes
  • how this affects button styles
  • etc
• Demo at a Meetup - "Intro to the Stylebook"
• Rapidly change a website
  • Change the site title and tagline
  • Create three new posts
  • Set the home page to a pattern
  • Turn off comments

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

• Create a blueprint to make a command in the Command Palette
• Extend the command to "deep link" to an editor interface - Stylebook

added to the master list for Playground

Stellar ideas!!