playground(s)

[carstingaxion]

Is your enhancement related to a problem? Please describe.

We could use some different instances of WordPress playground for multiple purposes:

• 664 for the new Plugin Preview feature on wp.org/plugins

• 666 or #668 to preview pull requests

• 649 for creating, managing and persisting demo-data

• for the experiments around blocks

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[carstingaxion]

Enabling Plugin Previews

There are two things required for a plugin preview button to appear to all users:

• A valid blueprint.json file must be provided in a blueprints sub-directory of the plugin’s assets folder.
• The plugin preview must be set to “public” from the plugin’s Advanced view by a committer.

[carstingaxion]

When GatherPress is available via wp.org we can replace the current implementation with:

{
    "step": "installPlugin",
    "pluginZipFile": {
        "resource": "wordpress.org\/plugins",
        "slug": "gatherpress"
    },
    "options": {
        "activate": true
    }
},