Update Blueprint to follow pattern in Gutenberg#2337
Merged
westonruter merged 1 commit intotrunkfrom Jan 9, 2026
Merged
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
b1ink0
approved these changes
Jan 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is another stab to fix #2279
Even after releasing #2325 it still didn't fix the issue.
The Gutenberg plugin's directory page has the "Live Preview" button as expected, so I looked at its
blueprint.jsonand noticed some key differences in its blueprint.json`:pluginsproperty.loginproperty.featuresproperty.preferredVersionsproperty.This also works in Playground.
I'm thinking the root
pluginsproperty is what the directory is looking at to decide whether to show the Live Preview button, making it conditional based on whether the slug is among thepluginsproperty. It's confusing to me why there are these two different ways to install a plugin, however.