An Introduction to WordPress Studio  🔗 **Source:** [An Introduction to WordPress Studio](https://www.youtube.com/watch?v=2MV17Qzj_T0) > [!note]+ Document Notes > tags: [wordpress-development, local-development, developer-tools, wordpress-com, webassembly, ai-assistant] > author: Nick (host, uncredited surname) > source: WordPress.com > reference: https://www.youtube.com/watch?v=2MV17Qzj_T0 > date created: {{date:YYYY-MM-DD}} {{time:HH:mm}} > > # 🏷️ Title: An introduction to WordPress Studio > <!-- deep-read:sections start --> ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [Studio download page](https://developer.WordPress.com/Studio) - [Studio GitHub repository](https://github.com/Automattic/studio) ## 📝 Summary - A WordPress.com host named Nick walks through Studio, a free, open source desktop app for local WordPress development on macOS and Windows. - It matters because Studio removes the usual local-dev friction — no Docker, no manual server config — and ships with WebAssembly under the hood, so you spin up a working site in seconds. - Key stakeholders: WordPress.com (vendor), Pressable customers, plugin and theme developers, agencies sharing work with clients, and the broader open source WordPress community. - Risks and tradeoffs: the most valuable features (Sync, live previews, AI assistant) lean on a WordPress.com account, and Sync to production is gated to business/commerce plans. The video is vendor marketing, so it frames everything positively and skips limitations. - Bottom line: Studio is a genuinely useful, free local-dev tool whose core works account-free, but its standout workflow features pull you toward the WordPress.com/Pressable ecosystem. ## 📖 Main Content - Studio is positioned as a fast, lightweight local WordPress environment "built with cutting edge web assembly technology" and aimed at "modern development workflows." WebAssembly (WASM) is what lets it run WordPress without Docker or a manually configured PHP/MySQL stack. - Core, account-free features: create local sites from a fresh install or a backup import; pick PHP version, WordPress version (including nightlies and betas), custom local path, custom domain, and optional HTTPS; start/stop sites; jump straight to wp-admin, the site editor, the site folder, your code editor, or a terminal. - Preferences let you set language, preferred code editor (the host uses Cursor), and terminal app. Studio detects which supported apps are installed. - Account-gated features (free WordPress.com account): live preview links to share work, Studio Sync with WordPress.com/Pressable staging or production, and a built-in AI assistant. - Studio Sync pulls a live site down to overwrite your local copy, or pushes a local build up — even launching a local site as a brand new WordPress.com site. Caveat stated in-video: Sync only works on WordPress.com business or commerce plans; lower tiers see an upgrade prompt. Pressable sites need Jetpack activated and connected with the same account. - Live previews: up to 10 free preview sites at once, each with a unique URL based on your WordPress.com username, expiring seven days after the last update, powered by WordPress.com. They're separate from production/staging and meant for showing colleagues or clients. - AI assistant: every WordPress.com account gets 200 free prompts per month. It's framed as a complement, not a replacement, for tools like Cursor — it makes changes directly to the Studio site, often returning WP-CLI commands you run with a click (demo installs WooCommerce). - Contested/uncertain (as vendor content): "fast," "lightweight," and "saves a lot of time" are unquantified claims. No benchmarks, no comparison to competing tools (Local, LocalWP, wp-env, DevKinsta), and no mention of WASM limitations or current AI-assistant constraints beyond the prompt cap. ### 🗒️ Notes #### ⏱️ [00:00:00](https://www.youtube.com/watch?v=2MV17Qzj_T0?t=0) Intro and feature roadmap - Host Nick introduces Studio as a free, open source local WordPress dev app for plugins, themes, or full sites. - Pitched as fast, lightweight, WebAssembly-based, for modern workflows. - Promised agenda: create a local site, configure preferences, sync WordPress.com/Pressable sites, create shareable preview copies, use the AI assistant. #### ⏱️ [00:01:00](https://www.youtube.com/watch?v=2MV17Qzj_T0?t=60) Dashboard and creating a site - macOS and Windows supported; download at developer.WordPress.com/Studio. - Familiar two-pane layout: site list on the left, overview on the right (selected site named "Encore"). - "Add site" → name it ("push to prod"), start fresh or import a backup. #### ⏱️ [00:02:30](https://www.youtube.com/watch?v=2MV17Qzj_T0?t=150) Advanced options and no-Docker setup - Advanced toggle: custom local path, PHP version, WordPress version (nightlies/betas), custom domain, optional HTTPS (handy for Jetpack). - Studio configures everything behind the scenes — "no extra tooling like Docker." - Start/stop sites from overview or sidebar; defaults give a Twenty Twenty-Five install on localhost. #### ⏱️ [00:05:00](https://www.youtube.com/watch?v=2MV17Qzj_T0?t=300) Settings, overview buttons, preferences - Edit site settings anytime (custom domain, WordPress version) via a modal like the create flow. - Overview buttons jump to site editor, open the site folder in Finder, or launch your code editor/terminal — "the less mouse clicks, the better." - Preferences (via WordPress.com login link): language, preferred editor (Cursor), terminal app; Studio remembers selections. #### ⏱️ [00:07:30](https://www.youtube.com/watch?v=2MV17Qzj_T0?t=450) Open source + account-gated features - Core features work with a fresh install, no account needed; full code base on GitHub. - A free WordPress.com account unlocks shareable live previews, Sync with WordPress.com/Pressable, and the AI assistant. #### ⏱️ [00:08:30](https://www.youtube.com/watch?v=2MV17Qzj_T0?t=510) Studio Sync - Sign in, see WordPress.com sites and Jetpack-enabled Pressable sites; link them to local sites, or push a local site up as a new WordPress.com site. - Caveat: Sync needs a business or commerce plan; lower tiers show an upgrade prompt. Pressable needs Jetpack on the same account. - Demo: connect production "push to prod," click Pull to overwrite the local fresh install with the real site. #### ⏱️ [00:10:30](https://www.youtube.com/watch?v=2MV17Qzj_T0?t=630) Live site previews - Previews tab needs only a free WordPress.com account; up to 10 at once, expire 7 days after last update, powered by WordPress.com. - Each gets a unique URL based on your username (host's is "ndiego"); log in with credentials on the Settings tab. - Update locally then push the preview so collaborators see changes immediately. #### ⏱️ [00:12:30](https://www.youtube.com/watch?v=2MV17Qzj_T0?t=750) AI assistant and wrap-up - Assistant gives 200 free prompts/month per account; complements rather than replaces Cursor, making changes directly to the Studio site. - Demo: "install WooCommerce" returns a WP-CLI command you click Run; opens the WooCommerce setup wizard. - Closing pitch: fast, flexible, free, open source; download at developer.WordPress.com/Studio; like and subscribe. ## 📚 References - [Studio download](https://developer.WordPress.com/Studio) - [Studio on GitHub (Automattic/studio)](https://github.com/Automattic/studio) - [WordPress.com](https://wordpress.com/) - [Pressable](https://pressable.com/) - [WP-CLI](https://wp-cli.org/) - [WooCommerce](https://woocommerce.com/) ## 🗣️ Paraphrase - Studio is a free, open source desktop app from WordPress.com that gives you a local WordPress site in seconds. Because it runs on WebAssembly, you skip Docker and manual server setup entirely, and you can pin PHP and WordPress versions, set custom domains and HTTPS, and jump straight into your editor, terminal, or wp-admin. - The core works without any account, but signing in with a free WordPress.com account adds the headline workflow tools: shareable live previews (up to 10, expiring after a week), two-way Sync with WordPress.com or Pressable, and a built-in AI assistant with 200 monthly prompts that mostly hands you click-to-run WP-CLI commands. Sync to production is reserved for business and commerce plans. ## 📰 Newsletter - Local WordPress dev without the Docker headache? WordPress.com's Studio app is worth a look — it's free, open source, and spins up a fresh site (PHP version, WP nightlies, custom domain, HTTPS and all) before your coffee cools, thanks to WebAssembly. - Hook in a free WordPress.com account and you get bonus toys: share a live preview link with a client (10 at a time, gone after 7 idle days), Sync local work to and from WordPress.com or Pressable, and lean on a built-in AI assistant that mostly speaks fluent WP-CLI — "install WooCommerce" becomes one click. - Fair warning: Sync to production wants a business or commerce plan, and this is a vendor walkthrough, so pack your own benchmarks. Grab it at developer.WordPress.com/Studio or read the source on [GitHub](https://github.com/Automattic/studio). ## ✅ Action Items #### DevRel - Developer advocacy: produce a vendor-neutral "Studio vs Local vs wp-env" comparison talk or post that quantifies the "fast/lightweight" claims with real cold-start and sync benchmarks. - Education: build a hands-on workshop — create a site, pin a WP beta, sync from staging, ship a preview link — with a reproducible checklist. - Developer experience: write a quickstart that documents the account-free path explicitly so newcomers know what works without a WordPress.com login. - Developer marketing: a short clip series on each gated feature (Sync, previews, AI assistant) with honest plan-gating callouts. - Community management: open a feedback thread on what WP-CLI prompts the AI assistant handles well vs poorly. - Internal/external/cross-project: feed AI-assistant prompt-cap and WASM-limitation questions back to the Studio team. #### OSPO - Policy & Governance: confirm the open source license and contribution policy on Automattic/studio before recommending it internally. - License Compliance: scan Studio's bundled dependencies (WASM PHP build) for license obligations. - Security Management: review how preview-site credentials (admin user + password shown in Settings) are generated and exposed. - Software Inventory: add Studio to your tooling SBOM if teams adopt it. - Developer Support: draft guardrails for using the AI assistant against synced production data. - Community Engagement: track upstream issues/PRs relevant to your stack. - Strategic Alignment: assess vendor lock-in risk from Sync/preview dependence on WordPress.com. #### Community - Maintainers: trial Studio's WP nightly/beta selector for testing plugin/theme compatibility against upcoming releases. - Contributors: use account-free Studio as a low-friction onboarding environment for first-time contributors. - Sponsors: n/a. - Ecosystem: coordinate a shared "Studio for core/plugin testing" guide across projects. #### WordPress - Core: use Studio's nightly/beta install option for early Core regression testing. - Core Performance: benchmark Studio's WASM runtime against native local stacks for realistic profiling fidelity. - Playground: clarify the relationship between Studio's WASM approach and WordPress Playground for education modules. - Training: turn the walkthrough into a Learn WordPress lesson on local development. - Documentation: examples-first docs for the import-backup and Sync flows the video skips. - CLI: document which WP-CLI commands the AI assistant emits and verify they're current. - Hosting: cross-host guidance on syncing Studio with non-WordPress.com/Pressable environments (gap). - Accessibility: audit the Studio Electron UI against WCAG; the video shows none. #### The WPCC - Programs: n/a to this source. - Projects: n/a to this source. - Funding experiments: n/a to this source. ### FAIR - Technical independence: note that Sync and previews route through WordPress.com infrastructure — evaluate provenance and portability for FAIR-aligned workflows. - Policies and covenants: n/a to this source. - Productized governance artifacts: n/a to this source. ## 🧪 Hypotheses - Studio's WebAssembly runtime spins up a working local site faster than Docker-based tools like DevKinsta on the same hardware. - The account-free core is sufficient for most plugin/theme development, so most adoption value doesn't require a WordPress.com account. - Gating Sync behind business/commerce plans measurably steers users toward higher-tier WordPress.com hosting. - The AI assistant's WP-CLI-first responses raise task-completion rates for developers unfamiliar with WP-CLI. - WASM-based local environments diverge from native PHP/MySQL behavior in edge cases (e.g., certain extensions), causing some production bugs to not reproduce locally. ## 📊 Methodology - Benchmark cold-start and site-creation time for Studio vs Local, wp-env, and DevKinsta across identical macOS/Windows hardware. - Instrument a cohort of new users; segment by account vs no-account; measure feature usage and conversion to paid WordPress.com plans. - A/B a WP-CLI-novice group with vs without the AI assistant; measure task success and time. - Run a compatibility matrix of plugins/extensions on Studio's WASM PHP vs native PHP to surface divergence. ### ❓ Questions - What exactly does the WASM runtime not support that a native local stack does? - Can Sync target arbitrary hosts via SSH/SFTP, or only WordPress.com and Pressable? - Where is preview-site data stored, and who can access expired previews before deletion? - What model powers the AI assistant, and does synced production content leave your machine? - How does Studio relate to and differ from WordPress Playground? ### 🔮 Future Research - Independent performance and fidelity comparison of WASM local environments vs native stacks. - Security review of preview-site credential handling and data residency. - Longitudinal study of free-tool-to-paid-host conversion driven by Sync gating. ### 💡 Implications - Practice: lowers the barrier to local WordPress dev, especially for newcomers intimidated by Docker. - Policy: organizations should set guidance on using the AI assistant against synced production data. - Security: preview credentials and synced data introduce review surface area. - Education: a strong teaching tool for local-dev and WP-CLI fundamentals. - Funding models: free tooling that nudges toward business/commerce plans is a classic ecosystem-funding lever. ### 🧠 Learning Styles Assessment - Reading level estimate: Flesch-Kincaid Grade ~8–9 (conversational narration, short clauses, light jargon like WASM and WP-CLI). Flesch Reading Ease roughly 60–70. #### 👀 Visual learners - Present: live screen-recording demo of every feature, UI walkthrough. - Improve: add an architecture diagram of the WASM runtime and a before/after of the Sync pull. #### 🔊 Aural learners - Present: clear spoken narration throughout. - Improve: offer a 2–5 minute audio-only recap and downloadable transcript. #### 🗣️ Verbal learners - Present: terms named in context (WebAssembly, WP-CLI, Jetpack, nightlies). - Improve: a short glossary callout for WASM, WP-CLI, and "business/commerce plan." #### 🧩 Kinesthetic learners - Present: step-by-step "follow along" framing with a download link. - Improve: a companion checklist and a sample repo to reproduce the demo. #### 🧠 Logical learners - Present: linear feature-by-feature structure (core → Sync → previews → AI). - Improve: a decision tree for "account-free vs account-gated" and a plan-gating table. #### 🧑‍🤝‍🧑 Social learners - Present: invitation to ask questions in comments. - Improve: link a community forum or Discord and host office hours. #### 🧘‍♀️ Solitary learners - Present: self-paced video format. - Improve: add reflection prompts and a self-check quiz on the features. #### 🌿 Naturalistic learners - Present: none. - Improve: tie to sustainability — local-first dev and lightweight WASM reduce cloud resource use. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: spoken narration conveys most on-screen actions. - Improve: ensure the YouTube description repeats key links as text; the Studio Electron UI needs its own ARIA/landmark audit (not shown). #### Keyboard navigation - Present: not demonstrated. - Improve: verify Studio app is fully keyboard-navigable with visible focus. #### Contrast and readability - Present: standard Studio UI shown. - Improve: confirm UI meets 4.5:1 text contrast. #### Text resizing and reflow - Present: not addressed. - Improve: confirm the app scales without clipping; respect prefers-reduced-motion. #### Media and captions - Present: YouTube auto-captions likely available. - Improve: ship a human-verified transcript and caption track; avoid relying on auto-captions for jargon like WP-CLI. #### Forms and interactions - Present: site-creation modal shown with labeled fields. - Improve: confirm form labels, inline validation, and target sizes in the actual app. #### Standards reference - Map gaps to WCAG 2.2 AA: 1.2.2 (captions), 2.1.1 (keyboard), 1.4.3 (contrast), 1.4.10 (reflow). ### 🌍 DEIB Assessment #### Cultural breadth - Present: a language preference setting is shown. - Improve: note localization coverage and provide multilingual captions. #### Inclusive language - Present: neutral, plain language; jargon mostly defined in context. - Improve: expand a glossary so non-native speakers and beginners aren't gated by WASM/WP-CLI terms. #### Neurodiversity support - Present: consistent, chunked, predictable feature-by-feature pacing. - Improve: add on-screen section headings and a chaptered timeline. #### Representation - Present: single host (Nick); no team or community voices. - Improve: feature varied developers and use cases (agency, solo, contributor). #### Psychological safety - Present: encouraging, low-pressure "highly encourage you to try it" tone. - Improve: set expectations honestly about plan gating and AI-assistant limits to avoid surprise. ### ✅ Logical Validity #### Strong reasoning - Causal (no-Docker → less friction): "there's no complex manual configuration, no extra tooling like Docker" supports the "fast/lightweight" claim with a concrete mechanism. Clarify further with timing benchmarks. - Conditional reasoning on gating: the host correctly conditions Sync on plan tier ("Studio Sync only works with WordPress.com sites on a business or commerce plan"), an honest, valid qualifier rather than an overclaim. - Analogical framing: "if you've used other local development tools before, this layout should feel pretty familiar" reasonably transfers prior knowledge to lower the learning curve. #### Fallacies - Unsupported superlative / vagueness: "one of my favorite tools" and "fast, lightweight" assert quality without evidence. Fix: cite benchmarks or specific comparisons. - Appeal to novelty: "built with cutting edge web assembly technology" implies value from newness alone. Fix: state what WASM concretely enables (no Docker, instant spin-up) — which the video partly does. - Promissory hand-wave: "with AI tools expected to get better and more capable over time" defers current limitations to the future. Fix: state today's concrete capabilities and limits. #### Tone of voice - Friendly, enthusiastic, promotional, instructional. Examples: "so let's dive in," "one of my favorite features," "I highly encourage you to head on over." Consistent vendor-advocacy register. ### 🛡️ DARVO Analysis - Not applicable to this source. This is a vendor product walkthrough, not a dispute or accusation; there's no accuser, denial, counter-attack, or victim/offender reversal to analyze. The only adversarial-adjacent move is mild upsell framing (plan gating presented as an "upgrade prompt"), which is promotional, not DARVO. ## 🎯 Conclusion - Bottom line: Studio is a legitimately useful, free, open source local WordPress dev tool whose account-free core (no-Docker, WASM-powered site creation with PHP/WP version control) stands on its own, while its best workflow features — Sync, live previews, and the AI assistant — tie you into the WordPress.com/Pressable ecosystem and, for production Sync, a paid plan. - Practical next steps: download from developer.WordPress.com/Studio, try the account-free flow first, then test a free-account preview link; if you rely on the claims, run your own speed and compatibility checks against your current local stack before switching. ## 🔄 Refactor Appendix — An introduction to WordPress Studio > Density: 2–5 Literature atoms (H3), 0–3 Permanent candidates (H4). > Defaults: 3 Literature, 1 Permanent. Resonance filter: if you can't > articulate in one line why a claim matters, drop it. > > Konik claim-header rules: present tense, declarative, ≤10 words when > possible, searchable, unique, mirrors annotation focus if present. > > Atomicity: one declarative sentence per atom. "and"/"also" → split. > > Tag pool: #bmf · #addendum · #xref · #articleseed · #storystem · #share · #aphorisms ### 📚 Literature Atoms (H3) #### Studio runs WordPress locally on WebAssembly > [!quote] ID:rw_2MV17Qzj_T0_a1 > built with cutting edge web assembly technology and is designed specifically for modern development workflows **Context & use**: - Intro, ~[00:00:20](https://www.youtube.com/watch?v=2MV17Qzj_T0?t=20). - WASM is the mechanism behind the "no Docker" claim — the load-bearing technical differentiator versus native local stacks. **Tags**: #xref **Highlight**: [view highlight](https://www.youtube.com/watch?v=2MV17Qzj_T0?t=20) <!-- atomicity: 1 idea ✓ --> #### Studio needs no Docker or manual config > [!quote] ID:rw_2MV17Qzj_T0_a2 > there's no complex manual configuration, no extra tooling like Docker **Context & use**: - Site-creation segment, ~[00:04:30](https://www.youtube.com/watch?v=2MV17Qzj_T0?t=270). - The friction-removal promise that defines Studio's pitch to newcomers; testable against competing tools. **Tags**: #xref **Highlight**: [view highlight](https://www.youtube.com/watch?v=2MV17Qzj_T0?t=270) <!-- atomicity: 1 idea ✓ --> #### Studio Sync requires business or commerce plans > [!quote] ID:rw_2MV17Qzj_T0_a3 > Studio Sync only works with WordPress.com sites on a business or commerce plan **Context & use**: - Sync segment, ~[00:09:30](https://www.youtube.com/watch?v=2MV17Qzj_T0?t=570). - The key plan-gating constraint — the lock-in/upsell boundary between free tooling and paid hosting. **Tags**: #xref #share **Highlight**: [view highlight](https://www.youtube.com/watch?v=2MV17Qzj_T0?t=570) <!-- atomicity: 1 idea ✓ --> ### 🧠 Permanent Candidates (H4) #### Free local tools funnel toward paid hosting tiers **Claim** (one sentence, Courtney's voice): Free, open source developer tools acquire users at low friction while reserving their highest-leverage workflows for paid hosting tiers, making the tool itself a funnel into the vendor's ecosystem. **Evidence pointer**: [[#Studio Sync requires business or commerce plans]] **Scope & conditions**: Holds when a free tool's standout features depend on vendor-hosted infrastructure (Sync, previews); breaks when the tool is fully self-hostable with no gated remote services. **Links**: - [[Open source as developer acquisition]] — because extends - [[Vendor lock-in vs technical independence]] — because contrasts on portability <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Benchmark Studio WASM cold-start vs Local/wp-env/DevKinsta — needs own hardware test #fleeting #inbox - [F2] Clarify Studio vs WordPress Playground relationship for Learn WordPress — open question #fleeting #inbox ### → Things 3 (max 2 actions) - [ ] Draft a vendor-neutral local-WordPress-dev comparison post with real benchmarks — DevRel #things - [ ] Open a feedback thread on Studio AI-assistant WP-CLI prompt quality — community #things <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/An Introduction to WordPress Studio.md|An Introduction to WordPress Studio by WordPress.com]] ## Highlights - Hey there, my name is Nick, and in this video we're going to be taking a look at one of my favorite tools Studio by the WordPress.com team. It's a free open source application for local WordPress development, and it's great for building plugins, themes, or even entire WordPress websites. It's also fast, lightweight, and built with cutting edge web assembly technology and is designed specifically for modern development workflows. In the next few minutes, you're going to learn how to create a local WordPress site using Studio, configure Studio based on your own development preferences. ([View Highlight](https://read.readwise.io/read/01kw2mx3fryghxx3hsht1p9k16)) - Note: WASM is the load-bearing differentiator behind the "no Docker" claim. - Tags: webassembly, atom/literature/h1 - If you go with a custom domain, you'll have the option to enable HTTPS as well, which can come in handy when working with plugins like Jetpack that sometimes require a secure connection. For this walkthrough, I'm going to stick with the defaults and just click Add site, and just like that, the new site is up and running. Studio sets up everything for me. Behind the scenes, there's no complex manual configuration, no extra tooling like Docker. ([View Highlight](https://read.readwise.io/read/01kw2mx6nze58skj2y2wgc75ew)) - Note: The friction-removal promise central to the pitch: no manual config, no Docker. - Tags: local-development, atom/literature/h2 - Now it's important to note that Studio Sync only works with WordPress.com sites on a business or commerce plan. If your site is on a lower tiered plan, you'll see an upgrade prompt like you do here with some of these other test sites. For Pressable sites, you will need to ensure that you have Jet Pack activated and connected using the same WordPress.com account that you're using here in Studio. Links to WordPress.com and Pressable documentation that talk more about this are available in the video description. ([View Highlight](https://read.readwise.io/read/01kw2mx9fcg9ns2ycd8zsza8w7)) - Note: Same plan-gating/upsell boundary restated — Sync requires a paid WordPress.com plan. - Tags: wordpress-com, atom/literature/h3 ## Links - [[3. Resources/Permanent Notes/Emulated Local Dev Trades Production Fidelity for Zero-Setup Speed]] — evidence-for: WebAssembly removes Docker and manual configuration while creating the fidelity tradeoff this Permanent names. - [[3. Resources/Permanent Notes/General WordPress-to-WordPress Sync Is Unsolvable Because Environment Is Part of the Site]] — applies-in: Studio Sync's plan and platform constraints show that environment remains part of transferability.