Start a clean WordPress site immediately with the selected runtime.
Step 1
Choose how this lesson starts
Each route keeps its real input shape so a learner can tell what will happen before it touches the current site.
Builds WordPress from the referenced core pull request.
Loads the Gutenberg plugin from a branch or pull request.
Imports plugins, themes, or wp-content. Token is not stored after refresh.
Runs the remote Blueprint against a new Playground.
Importing over the current site replaces the current files and database.
Preparing WordPress... 68% -> Ready at /hello-from-playground/ as admin.
Step 2
Pick a real save destination
The two current destinations are shown as separate choices, with progress and resulting state beside them.
Copying WordPress files, uploads, database, and blueprint metadata into browser storage.
Research Browser Playground is now listed as a saved browser-backed Playground and keeps its own addressable slug.
Folder selected: ~/Playgrounds/research-browser. Save & Reload appears after runtime settings change.
Step 3
Manage saved and temporary Playgrounds inline
The list keeps unsaved state, saved browser state, rename, and delete in one surface.
Not saved to browser storage. Refreshing or closing loses changes.
Created May 21, 2026. Saved in this browser.
Created May 20, 2026. Local directory save.
Rename saved Playground
Delete saved copy
This removes the selected browser copy from Saved Playgrounds. It does not preserve unsaved tab changes.
Step 4
Site Manager as a learning bench
The current tabs become inline benches so a first-time learner can see what each tool affects.
- /wordpress
- wp-admin
- wp-content
- wp-includes
- wp-config.php
- wp-settings.php
1 <?php define( 'CONCATENATE_SCRIPTS', false );
2 define( 'DB_NAME', 'database_name_here' );
3 define( 'DB_USER', 'username_here' );
4 define( 'DB_HOST', 'localhost' );
5 $table_prefix = 'wp_';
6 define( 'WP_DEBUG', false );
{
"$schema": "https://playground.wordpress.net/blueprint-schema.json",
"login": true,
"landingPage": "/hello-from-playground/",
"preferredVersions": { "php": "8.3", "wp": "latest" }
}
WordPress Playground emulates MySQL using SQLite.
- Driver
- MySQL emulation backed by SQLite
- Path
- /wordpress/wp-content/database/.ht.sqlite
- Size
- 452 KB
No errors captured.
No PHP notices.
Runtime log is empty.
Step 5
Blueprint gallery with dense catalog behavior
Categories, search, selected detail, inspect, and run actions remain visible while browsing the full captured catalog.
Step 6
Move work in or out with consequences exposed
Additional actions, export, download, and import-over-current warnings are presented inline.
Starts the current Playground export flow after GitHub authentication.
Downloads files, database, and blueprint bundle for the current Playground.
The imported archive replaces the current files and database. Save first if you need the current state.
Step 7
Active WordPress result
The preview remains reachable from the learning path with homepage, WP Admin, refresh, and path navigation.
Hello from WordPress Playground!
This is Playground, a WordPress that runs client-side in your browser. It is perfect for training, demonstrating plugins and themes, and testing purposes.
Note that you are logged-in as admin!