Custom Blueprint
A valid assets/blueprints/blueprint.json designed around the plugin’s public build and dependencies.
WordPress.org preview enablement
Put a working proof beside the Download button.
PreviewReady designs and tests one useful evaluator journey, then hands your committer the Playground Blueprint, seeded demo, validation evidence, and SVN-ready package needed to enable an official Live Preview.
$149founding rate · first 3 accepted pilots
48 hoursafter fit + inputs are confirmed
- Public sources first
- No production login
- No repository access to assess fit
01 Public availability check
Does your plugin page have Live Preview today?
Check the official WordPress.org page. No login, scan, or email required.
Point-in-time evidence only. This checks for WordPress.org’s official control; it does not test compatibility or detect demos hosted elsewhere.
The pilot
A committer-ready package, not a generic template.
Your plugin’s primary evaluation path shapes the setup, content, landing screen, and smoke plan.
Seeded demo state
Purpose-built sample content and settings so the first screen demonstrates a real use case.
One-click preview URL
A public test link for review before your committer enables the WordPress.org control.
Validation report
Blueprint validation plus a concise Chrome and Firefox smoke plan and observed results.
SVN-ready handoff
Exact asset path, file notes, publishing steps, and a clean final package for your committer.
One revision
One focused revision to the accepted pilot scope after your team reviews the handoff.
Founding-pilot scope: one public WordPress.org plugin, one primary evaluator journey, up to two public dependencies, one seeded state, one landing screen, the latest supported WordPress/PHP configuration, documented Chrome and Firefox smoke observations, one SVN-ready handoff, and one consolidated revision. Your authorized committer publishes the asset and enables Live Preview.
See the work
Open the package before you open an inquiry.
The public sample shows the Blueprint structure, seeded demo, validation checklist, and the handoff notes a plugin committer would receive. It is an independent demonstration, not client work or an endorsement.
Review the sample packageFit gate
We check feasibility before charging.
Usually a fit
- The current plugin build is public on WordPress.org.
- A useful first-run experience can work in Playground.
- Required dependencies are public and installable.
- Your committer can review and publish the final asset.
We may decline
- The core value depends on a private service or secret key.
- The demo requires external accounts or non-public files.
- Playground cannot support a required server capability.
- The requested outcome cannot be tested responsibly.
A “not yet” is useful information. Unsuitable plugins are declined before any charge.
48-hour path
Four gates. One clean handoff.
The clock starts after written fit confirmation and receipt of the required public URLs.
- 01Fit review
We inspect the public plugin page, current package, dependencies, and likely demo path.
- 02Build the proof
We write the Blueprint and seed only the content and settings needed to show the primary use case.
- 03Validate the route
We validate the file and document the Chrome and Firefox smoke checks and any known constraints.
- 04Hand off to your committer
You receive the asset, test URL, concise SVN notes, and the included revision path.
After preview enablement
Shipping a release, not just a preview?
The PreviewReady Preflight Packet turns a public changelog, public docs, and a provided non-secret build or demo into a risk-ranked pre-release QA packet.
$199 packetSee the Preflight Packet
Start with fit
Send the public plugin page. We’ll assess the pilot.
This is an inquiry, not a checkout or automatic booking. We review suitability first and reply by email.
Founding pilot
$149
first 3 accepted, paid pilots