Section 1
Launch Source
Choose exactly how this client test starts. Each source keeps its own inputs and consequences visible.
Start Vanilla WordPress
Create a clean temporary Playground using the selected WordPress and PHP versions.
Section 2
Save Destination
Temporary Playgrounds are lost on refresh or close until one of these destinations completes.
Section 3
Saved Playgrounds
Browser-backed entries keep their identity, action menu, and destructive delete affordance close to the project document.
Section 4
Site Manager Notebook
Settings, files, blueprint, database, and logs read like sections of the same project instead of a separate utility panel.
- /wordpress
- wp-admin
- wp-content
- wp-includes
- index.php
- wp-config.php
- wp-cron.php
- wp-settings.php
1 <?php define( 'CONCATENATE_SCRIPTS', false );
2 /** The base configuration for WordPress */
3 define( 'DB_NAME', 'database_name_here' );
4 define( 'DB_USER', 'username_here' );
5 define( 'DB_PASSWORD', 'password_here' );
6 define( 'DB_HOST', 'localhost' );
7 define( 'DB_CHARSET', 'utf8mb4' );- blueprint.json
{
"$schema": "https://playground.wordpress.net/blueprint-schema.json",
"landingPage": "/hello-from-playground/",
"login": true,
"preferredVersions": { "php": "8.3", "wp": "latest" }
}Database management is an early access feature
WordPress Playground emulates MySQL using SQLite. The database tools are available for inspection and export.
- Database driver
- MySQL emulation backed by SQLite
- SQLite database path
- /wordpress/wp-content/database/.ht.sqlite
- Size
- 452 KB
Section 5
Blueprint Catalog
A dense catalog with search, category filters, selected detail, inspect JSON, and run behavior.
Showing 43 of 43 catalog entries
Section 6
Import, Export, and Current-Site Consequences
The same document keeps irreversible actions close to the active project state.