Blueprints Naming: Call for Feedback

[sfougnier]

Thanks to everyone who contributed to the original issue to provide new name suggestions for Blueprints! We’ve spent some time compiling the full list of names into a single location to help us filter the options.

We used the following criteria to assess what names stay in the running:

1. The name should fit within the WordPress mental model. While Blueprints are currently closely associated with Playground, they won’t always be. Therefore, whatever name we use for them should make sense within the larger WordPress ecosystem.
2. Bonus points if the name fits the above and works when paired with the term “Playground.”
3. The name should be ownable. It should be free of connotations or associations that make it hard to tie to WordPress.
4. The name should be flexible enough to accommodate upcoming use cases:

• First class support for running Blueprints in WordPress core – either via the command palette or as an API for plugin authors
• Collections, like the Blueprints directory, but personal or shared with your team or the public.
• Single-click sites based on Blueprints from these collections
• Building a Playground from many Blueprints, applying a Blueprint to an existing Playground
• A directory of custom Blueprint steps for the community to share
• A Block-based UI for building Blueprints in the block editor

Here’s a look at our filtered list, with our selects highlighted at the top:

Here’s where you come in. We want your help deciding which name out of our filtered list makes the most sense. Please make a selection from the following:

[adamsilverstein]

Still like recipes

[sfougnier]

Closing this request for feedback, thank you to all who voted!

The consensus is to keep the name Blueprints, followed by a close second of changing to Playbooks.