Getting Started with WordPress Studio - CourtneyR.dev's 2nd Brain

# Getting Started with WordPress Studio > [!question] Lingering Questions > - What exactly happens to a preview site at day seven — hard delete, or a grace period, and is there a warning before it's gone? > - Can Studio Sync target self-hosted WordPress at all, or is it strictly WordPress.com/Pressable? > - Does the open source core include the preview/sync backend, or only the client app? The GitHub claim is real but the video doesn't say where the line falls. > [!tip] Article Ideas > - A companion demo comparing Studio against other local stacks (Local, DevKinsta, wp-env) with a real plugin/theme dev loop, since this video (like the sibling walkthrough already in the vault) supplies zero comparative benchmarks. #articleseed > [!link] Cross Reference > - [[3. Resources/Permanent Notes/Free Local Tools Funnel Toward Paid Hosting Tiers]] — already exists, sourced from a sibling Studio walkthrough ([[3. Resources/Literature Notes/An introduction to WordPress Studio]]); this doc's own Sync-gating claim is the same pattern, not a new claim > - [[3. Resources/Literature Notes/An introduction to WordPress Studio]] — a near-duplicate vendor walkthrough of the same tool, same host, same feature set (Sync/Preview/Assistant) — treat the two as complementary evidence for the same underlying claims rather than independent sources > - [[3. Resources/Literature Notes/WordPress Studio Review]] — an independent (non-vendor) review that surfaces gaps this walkthrough skips > - [[3. Resources/MOCs/Product & Startup Instincts MOC]] > [!quote] Vocabulary > - *Blueprint* — a Studio "recipe" for scaffolding a new site's starting configuration; described in the video as "like a recipe" ## Bib capsule Nick Diego, "Getting Started with WordPress Studio," WordPress.com, 2026. ## Author's thesis WordPress Studio is a free, open source, WebAssembly-powered local WordPress app that removes manual server/PHP/database setup, and its account-free core (site creation, version pinning, custom domains) is genuinely functional without any login. The standout workflow features — Sync to staging/production, shareable live previews, and an AI Studio Assistant — all require at least a free WordPress.com account, and the single most valuable one (Sync) is further gated behind a paid Business or Commerce plan. ## Key arguments 1. Studio runs on WebAssembly (the same foundation as WordPress Playground), which is the mechanism behind its no-manual-config, fast-start pitch. 2. The account-free core is fully real and useful on its own — blank site creation, Blueprints, PHP/WordPress version selection — but every workflow feature that makes Studio distinctive from a plain local server sits behind a WordPress.com account. 3. Studio Sync, the highest-leverage feature (pulling and pushing between local and production), is explicitly restricted to Business or Commerce plan sites; lower tiers see an upgrade prompt instead. ## Claim atoms ### Studio is free, open source local WordPress development > [!quote] ID:rw_h1 > a free and open source application for local WordPress development **Context & use**: 00:00:00 intro. Anchors Studio's positioning; the open source claim is real (GitHub) but headline features depend on WordPress.com hosting. **Tags**: #xref  ### Studio runs on WebAssembly for fast local sites > [!quote] ID:rw_h2 > built on cutting edge Web Assembly technology, and design specifically for modern development workflows **Context & use**: 00:00:30 intro. Same WebAssembly foundation as WordPress Playground; explains the no-stack-setup speed claim, though unquantified. **Tags**: #xref  ### Studio Sync requires a Business or Commerce plan > [!quote] ID:rw_h3 > Studio Sync only works with WordPress.com sites on a Business or Commerce plan **Context & use**: 00:08:00 sync section. The free/paid boundary and the core funnel mechanic — the most valuable workflow is gated. Same claim already captured in the vault's existing Permanent note on this pattern. **Tags**: #xref #addendum  ### Preview sites are free but expire after seven days > [!quote] ID:rw_h4 > you can have up to 10 free preview sites at any one time **Context & use**: 00:10:30 previews section. Defines the sharing workflow's limits; previews need only a free account, unlike sync. **Tags**: #xref  ## Permanent candidates - [[3. Resources/Permanent Notes/Free Local Tools Funnel Toward Paid Hosting Tiers]] — already exists (created from the sibling "An introduction to WordPress Studio" walkthrough), capturing atom 3's exact claim; linked rather than duplicated. - No further Permanent candidate from this source — atoms 1, 2, and 4 are descriptive/product-detail claims specific to this tool, not independently reusable outside a WordPress-Studio-specific context. ## Processing checklist - [x] Verbatim quotes preserved from the source deep-read - [x] Atomicity markers present on all four atoms - [x] Checked for existing Permanent notes before drafting — found an exact match from a sibling source; linked instead of duplicating - [x] Connect into the relevant MOC(s) ## Links - [[3. Resources/MOCs/Product & Startup Instincts MOC]] — free-tool-to-paid-hosting funnel as a product strategy pattern - Source doc: [[3. Resources/Readwise/Articles/Getting Started with WordPress Studio]] - [[3. Resources/Permanent Notes/Free Local Tools Funnel Toward Paid Hosting Tiers]] — the Permanent note this walkthrough's Sync-gating atom restates; Sync requires a Business or Commerce plan - [[3. Resources/Literature Notes/An introduction to WordPress Studio]] — sibling vendor walkthrough of the same tool and features; treat the two as complementary evidence, not independent sources - [[3. Resources/Permanent Notes/Pick a Local WordPress Environment by Use Case Not Vendor Label]] — the decision rule for where Studio fits: Playground-based speed suits experiments, while client work needs a real pull-live-site workflow