ref: https://developer.wordpress.org/plugins/wordpress-org/previews-and-blueprints/
If you haven’t noticed it yet, the WordPress Playground is an amazing feature that lets anyone safely run a temporary WordPress install within their browser. It uses WASM to run a complete WordPress install – PHP, database, and all – entirely from within your web browser. No server needed, nothing to install.
For a while now Playground has supported loading any plugin or theme from the plugin directory; here’s how.
The Plugin Preview feature adds a convenient button to plugins in the plugin directory, when enabled by a plugin’s developers. The button takes the user to Playground with that plugin installed. It’s right beside the Download button.
The Preview button is not shown by default; it must be explicitly enabled. Developers can use blueprint files in order to configure the preview environment and install dependencies (such as other plugins and themes).
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.
If a valid blueprint.json file is present, then the Preview button will be present for plugin committers only. In which case it will look like this:
The Test Preview button allows plugin authors to showcase what their plugin does with one click.
It’s called Test Preview because that’s why it’s there: to allow plugin committers to test their plugin in the Playground environment and decide whether or not to make it easily available to the public.
ref: https://developer.wordpress.org/plugins/wordpress-org/previews-and-blueprints/ If you haven’t noticed it yet, the WordPress Playground is an amazing feature that lets anyone safely run a temporary WordPress install within their browser. It uses WASM to run a complete WordPress install – PHP, database, and all – entirely from within your web browser. No server needed, nothing to install.
For a while now Playground has supported loading any plugin or theme from the plugin directory; here’s how.
The Plugin Preview feature adds a convenient button to plugins in the plugin directory, when enabled by a plugin’s developers. The button takes the user to Playground with that plugin installed. It’s right beside the Download button.
The Preview button is not shown by default; it must be explicitly enabled. Developers can use blueprint files in order to configure the preview environment and install dependencies (such as other plugins and themes).
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. If a valid blueprint.json file is present, then the Preview button will be present for plugin committers only. In which case it will look like this:
The Test Preview button allows plugin authors to showcase what their plugin does with one click. It’s called Test Preview because that’s why it’s there: to allow plugin committers to test their plugin in the Playground environment and decide whether or not to make it easily available to the public.