Vanilla WordPress
Start a clean Playground using the selected runtime.
A usable WordPress site stays central. The Settings rail is open, but the preview can take the entire window at any time.
Downloading WordPress, mounting SQLite, applying blueprint steps.
The launcher uses native grouped rows, but every non-vanilla route exposes its required input before it boots.
Start a clean Playground using the selected runtime.
Boot from a core pull request.
Test a Gutenberg pull request or branch.
Load a theme or plugin from a repository.
Paste a blueprint JSON URL.
Upload a previously exported Playground bundle.
One canonical runtime page. The toolbar gear lands here, and Apply & Reset always opens the same destructive sheet.
Site Manager file browser with New File, New Folder, tree navigation, and an editor pane.
Author blueprint JSON and bundle files, then copy, download, or run it against the current Playground.
Database and debugging have a named home instead of disappearing into a generic More bucket.
| Table | Rows | Recent record | Status |
|---|---|---|---|
| wp_posts | 18 | Hello from WordPress Playground! | ready |
| wp_options | 142 | siteurl = http://playground.local | ready |
| wp_users | 1 | admin | ready |
| wp_terms | 6 | Uncategorized | ready |
Site Manager header actions and the additional actions menu are grouped without hiding common WP Admin and Homepage jumps.