Public-source demonstration

A handoff you can inspect before you inquire.

This neutral demo shows the shape of a PreviewReady pilot using only publicly available WordPress.org resources. It was not commissioned, reviewed, or endorsed by the plugin developer or WordPress.org.

Run the demo in Playground View Blueprint JSON

SAMPLE / HANDOFFv1.0

Source: Public WordPress.org package
Data: Fictional seeded content
Secrets: None
Environment: Temporary browser sandbox

01 Blueprint

One file defines the repeatable preview.

The sample pins the environment choices, installs the public plugin package, activates it, creates only fictional demonstration content, and lands the evaluator at the intended first screen.

{
  "$schema": "https://playground.wordpress.net/blueprint-schema.json",
  "login": true,
  "steps": [
    { "step": "installPlugin", "pluginData": { "resource": "wordpress.org/plugins", "slug": "…" } },
    { "step": "runPHP", "code": "<?php /* seed the demo state */" }
  ]
}

Excerpt only. Open the complete sample file for the exact runnable configuration.

02 Seeded demo state

The evaluator should not arrive at an empty dashboard.

Purpose

Give a first-time evaluator one clear scenario to inspect.

Content

Use fictional, non-sensitive copy and assets created for the sandbox.

Landing

Open at the product surface that makes the plugin’s value easiest to understand.

03 Validation

Machine-readable first, human-readable second.

✓
JSON parses cleanly
No comments, trailing commas, or malformed strings.
✓
Blueprint schema reference is present
The file points to the current official Playground schema.
✓
Only intended public resources are referenced
No credentials, private archives, or temporary authenticated URLs.
✓
Handoff path is correct
The final asset is prepared for assets/blueprints/blueprint.json.

These are sample checklist items, not a claim that every plugin will pass. Actual results are recorded for the accepted plugin and version.

04 Browser smoke plan

A short route through the behavior that matters.

CheckChromeFirefox

Playground boots and installs the packageObserveObserve

Seeded content is presentObserveObserve

Intended landing screen opensObserveObserve

Primary demo action completesObserveObserve

“Observe” marks the sample plan, not a fabricated test result. A paid handoff records dated pass, fail, or constrained results.

05 SVN handoff

The plugin committer keeps the final controls.

1
Review the Blueprint and one-click test URL against the accepted demo path.
2
Commit the approved file at assets/blueprints/blueprint.json in the plugin’s WordPress.org SVN assets folder.
3
Use the plugin’s Advanced view on WordPress.org to make the preview public.
4
Verify the public Live Preview control and rerun the short smoke route.

WordPress.org requires a valid Blueprint in the assets path and a committer to enable public preview. PreviewReady does not publish or change plugin settings for the team.