Add a Playground blueprint json to the /assets/blueprints folder of Plugin Repo

[bph]

What?

Adds a blueprint.json to the assets/blueprints folder, to show a preview in the Plugins Directory for the plugin.
Fix #67739

Why?

To empower users to test and try out the latest Gutenberg plugin version.

How?

Following the Plugin Review Teams instructions.

Testing Instructions

Test via Playground (updated 12/11/24)

• Needs a second step from plugin committers on record to switch the blueprint from test to public.

[github-actions]

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 props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: bph <[email protected]>
Co-authored-by: brandonpayton <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

Warning: Type of PR label mismatch

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

• Type-related labels to choose from: [Type] Automated Testing, [Type] Breaking Change, [Type] Bug, [Type] Build Tooling, [Type] Code Quality, [Type] Copy, [Type] Developer Documentation, [Type] Enhancement, [Type] Experimental, [Type] Feature, [Type] New API, [Type] Task, [Type] Technical Prototype, [Type] Performance, [Type] Project Management, [Type] Regression, [Type] Security, [Type] WP Core Ticket, Backport from WordPress Core, Gutenberg Plugin.
• Labels found: [Type] Enhancement, Gutenberg Plugin.

Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task.

[brandonpayton]

Thanks, @bph! This tests well for me. I approved the PR but left some notes about potential improvements, depending on what you think.

[t-hamano]

@sirreal @gziolo Do you know if the assets directory is included in the files released to .org? Maybe we need to explicitly include it here:

gutenberg/bin/build-plugin-zip.sh

Lines 83 to 93 in b66f9ff

	zip --recurse-paths --no-dir-entries \
	gutenberg.zip \
	gutenberg.php \
	lib \
	packages/block-serialization-default-parser/*.php \
	post-content.php \
	build \
	build-module \
	readme.txt \
	changelog.txt \
	README.md

[bph]

Oh, good catch @t-hamano - Thank you!

[bph]

I downloaded the plugin build artifact from this PR and the assets folder didn't come with it.

[sirreal]

I'm not sure how the plugin publish flow works for Gutenberg, but the asset directory is separate from what goes into the plugin zip on the plugin repository, so it's not surprising that it wouldn't be listed as part of the plugin zip.

[bph]

I added a new issue

• add /assets folder to plugin build process #67835