Feature to help plugin developers create blueprints for previews

[tellyworth]

We should encourage plugin developers to create blueprint files for their plugins, so as to enable the Live Preview button (see #7251 ).

A simple starting point for this would be to create a tool that will automatically generate a blueprint.json file. The plugin developer can then download the json file, make any necessary changes, and commit it to the assets folder (as described in ​ https://make.wordpress.org/meta/2023/11/22/plugin-directory-preview-button-revisited/ ).

Further improvements on this are easy to imagine, but I would propose starting simply and then iterating.

[tellyworth]

Initial draft patch for discussion and review

[tellyworth]

Screenshot showing the Test In Playground and Download Blueprint buttons added by the draft patch. These are only visible for a plugin's authors, and only when the plugin does not already have a published blueprint.json for previews.

[tellyworth]

Use a developer notice with explicit instructions, rather than a simple button.

[tellyworth]

The new patch uses a different UX. Instead of a simple button, a notification is displayed to plugin authors/committers with explicit instructions to test the sample blueprint and download a copy to commit to their assets folder.

[tellyworth]

Adds a dismiss button, and minor markup changes to the notice.

[tellyworth]

Screenshot showing the .3.diff version. This has a dismiss button, and improved styling of the notice.

[tellyworth]

Minor tweaks in the .4.diff patch:

• Capitalize the Dismiss button
• Make dismissal permanent
• Use pretty printing when generating the blueprint

Note that the permanent Dismiss button will need some further revision, since there should be some way to undo that or remind the developer again in future.

[tellyworth]

In thirteen thousand three hundred and thirty-five :

Plugin directory: prompt plugin developers to create a blueprint for previews

This adds a notice, visible only to a plugin's developers, prompting them to test and create a blueprint.json file so users can run a Live Preview of their plugin in the WordPress Playground. The notice can be dismissed.

See #7487 .

[dd32]

In thirteen thousand three hundred and sixty-five :

Plugin Directory: Blueprint import: Normalize installPlugin/installTheme by url to install-by-slug for WordPress.org items.

This avoids cases of the blueprint referencing an outdated version of the plugin, and attempting to install the plugin twice.

See #7487 .

[zieladam]

Surfacing this Blueprints v2 spec conversation here: ​ https://github.com/WordPress/blueprints/issues/6

It won't come together for a few more weeks or months and even then v1 will continue to work. I just wanted to make sure everyone here is aware.

[zieladam]

This issue was reported about the new page: ​ https://github.com/WordPress/wordpress-playground/issues/1110