How to Use Blueprints in WordPress Studio  🔗 **Source:** [How to Use Blueprints in WordPress Studio](https://www.youtube.com/watch?v=YKLHP_ADj6o) > [!note]+ Document Notes > tags: [wordpress-studio, blueprints, local-development, woocommerce, developer-tools] > author: [MISSING] > source: WordPress.com > reference: https://www.youtube.com/watch?v=YKLHP_ADj6o > date created: {{date:YYYY-MM-DD}} {{time:HH:mm}} > > # 🏷️ Title: How to use Blueprints in 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 - [WordPress Studio](https://wordpress.studio) - [Create Block Theme plugin](https://wordpress.org/plugins/create-block-theme/) - [Plugin Check](https://wordpress.org/plugins/plugin-check/) - [WooCommerce](https://wordpress.org/plugins/woocommerce/) ## 📝 Summary - WordPress Studio now ships Blueprints, which create local sites from repeatable JSON recipes covering WordPress version, plugins, theme, content, and settings. - It matters because developers and site builders who spin up the same local environment repeatedly can codify that setup once and reuse it. - Key stakeholders: WordPress theme and plugin developers, WooCommerce store builders, and anyone using Studio for local development on Mac or Windows. - Risks and tradeoffs: creating a site from a blueprint takes longer because Studio downloads plugins, the theme, and applies settings; authoring custom blueprints needs familiarity with the JSON schema and documentation. - Bottom line: blueprints turn manual, repeated local-site setup into a one-click reproducible flow, and existing Studio users get it by updating to the latest version. ## 📖 Main Content - A blueprint is a JSON file describing how a site is built in Studio: preferred WordPress and PHP versions, which plugins and themes to install, plus content and settings. It can also run PHP and WP-CLI commands. - Studio ships three featured blueprints. Quick Start gives a WordPress.com-like environment with a collection of plugins. Development targets theme and plugin developers and bundles utility plugins like Create Block Theme and Plugin Check. Commerce is for online stores and pre-installs WooCommerce companion plugins. - The flow: click Add Site (bottom left), choose Start from a Blueprint, then pick a featured blueprint or supply your own. After Continue, you enter the normal add-site flow to name the site and set advanced settings. - Custom blueprints are pitched as the standout feature. If you keep building local sites with the same plugins, theme, and settings, you turn that into a blueprint. Plugins and themes install from the WordPress.org repository or other sources like GitHub. - The sample blueprint shown sets preferred WordPress and PHP versions, installs WooCommerce, installs the Pendant theme from WordPress.org, and sets user meta — specifically the default admin color scheme to "modern." - Uncertainties: the video calls the sample "basic" and points to the documentation for additional blueprint steps rather than enumerating the full schema. The theme name is spoken as both "Pendant" and "Pentant" — likely a single theme, transcript-level ambiguity. ### 🗒️ Notes #### ⏱️ [00:00:00](https://www.youtube.com/watch?v=YKLHP_ADj6o?t=0) What blueprints are - Blueprints let you create local sites from repeatable recipes. - Can include WordPress version, plugins, theme; can run PHP and WP-CLI commands. - Studio ships featured blueprints, or you supply your own custom blueprints. #### ⏱️ [00:00:40](https://www.youtube.com/watch?v=YKLHP_ADj6o?t=40) Starting the flow - One site already running, called Portfolio. - Add Site (bottom left) → three options: Create a site, Start from a Blueprint, Import from a backup. - Choose Start from a Blueprint. #### ⏱️ [00:01:10](https://www.youtube.com/watch?v=YKLHP_ADj6o?t=70) Featured blueprints, three options - "Blueprints are just a JSON file that describe how a site is built." - Quick Start: WordPress.com-like environment with a collection of plugins. - Development (presenter's favorite): for theme/plugin devs; includes Create Block Theme and Plugin Check. - Commerce: WooCommerce plus companion plugins pre-installed. #### ⏱️ [00:02:20](https://www.youtube.com/watch?v=YKLHP_ADj6o?t=140) Custom blueprints - "Blueprints are all about improving your workflows." - If you build the same local sites repeatedly, turn it into a blueprint. - Sample sets WP/PHP versions, installs WooCommerce, installs the Pendant theme. - Install from WordPress.org repo or elsewhere like GitHub. - Sets user meta: default admin color scheme to "modern." #### ⏱️ [00:03:40](https://www.youtube.com/watch?v=YKLHP_ADj6o?t=220) Using a blueprint file - Click Choose Blueprint file, select sample-blueprint.json, Continue. - Same Add a Site flow: name it, click Add Site. - Creation takes longer — Studio downloads plugins and theme, applies settings. #### ⏱️ [00:04:30](https://www.youtube.com/watch?v=YKLHP_ADj6o?t=270) Result and call to action - Site completes; WordPress admin shows WooCommerce installed and the theme present. - Existing users: update to the latest version when prompted. - New users: download from WordPress.Studio for Mac or Windows; like and subscribe. ## 📚 References - [WordPress Studio](https://wordpress.studio) - [WooCommerce](https://wordpress.org/plugins/woocommerce/) - [Create Block Theme](https://wordpress.org/plugins/create-block-theme/) - [Plugin Check](https://wordpress.org/plugins/plugin-check/) - [WordPress.org plugin and theme repository](https://wordpress.org/plugins/) ## 🗣️ Paraphrase - Studio added blueprints, reusable JSON recipes that build a local site from your chosen WordPress version, plugins, theme, content, and settings, and can even run PHP and WP-CLI. - Three featured blueprints cover common needs: a WordPress.com-like Quick Start, a developer-focused Development set, and a WooCommerce-ready Commerce set. - The real value is authoring your own blueprint once you find yourself rebuilding the same site repeatedly, pulling plugins and themes from WordPress.org or GitHub and pre-setting things like the admin color scheme. - Building from a blueprint takes a bit longer because Studio downloads everything and applies the settings, but the result is a ready-to-use site; existing users just update, new users download from WordPress.Studio. ## 📰 Newsletter - WordPress Studio just made "set up my usual local site" a one-click move. The new Blueprints feature reads a JSON recipe and builds a site with your preferred WordPress and PHP versions, plugins, theme, and settings — and yes, it can run PHP and WP-CLI too. - Three featured blueprints are ready out of the box: Quick Start (a WordPress.com-like environment), Development (utility plugins like Create Block Theme and Plugin Check), and Commerce (WooCommerce with companions). The crowd-pleaser, though, is rolling your own — install from WordPress.org or GitHub and bake in the small settings you always tweak, like the modern admin color scheme. - If you already use Studio, just update when prompted. New to it? Grab it for Mac or Windows at [WordPress.Studio](https://wordpress.studio). ## ✅ Action Items #### DevRel - Developer advocacy: demo a custom blueprint that mirrors your team's standard local stack and publish the JSON. - Education: write a short "author your first blueprint" walkthrough covering plugins, themes, and user meta. - Developer experience: provide starter blueprint templates (WooCommerce, block-theme dev) in a shared repo. - Developer marketing: position blueprints against manual local setup time saved. - Community management: collect community-submitted blueprints and curate a gallery. - Internal/external/cross-project: align blueprint schema docs with the Studio team's release notes. #### OSPO - Policy & Governance: define a review policy for shared blueprints that install from GitHub. - License Compliance: scan plugins/themes referenced in published blueprints for license clarity. - Security Management: vet third-party (non-WordPress.org) install sources cited in blueprints. - Software Inventory: track which plugins/themes appear across official blueprints for SBOM purposes. - Developer Support: offer office hours on blueprint authoring and WP-CLI steps. - Community Engagement: coordinate with WooCommerce maintainers on the Commerce blueprint contents. - Strategic Alignment: report adoption metrics for blueprint-based site creation. #### Community - Maintainers: publish a maintained "dev environment" blueprint for your project's contributors. - Contributors: use a shared blueprint to standardize onboarding local setups. - Sponsors: N/A — no sponsorship content in source. - Ecosystem: cross-project blueprint sharing for common stacks. #### WordPress - Core: N/A — source is a product tutorial, not core development. - Playground: connect blueprint format learnings to WordPress Playground's blueprint concept. - Documentation: link Studio blueprint docs prominently; the video repeatedly defers to "the documentation." - Training: build a Learn WordPress lesson on Studio blueprints. - CLI: document the WP-CLI step capability with examples. - Hosting: N/A — local-only tool. - Themes: highlight installing themes from WordPress.org and GitHub via blueprints. - Plugins: highlight Plugin Check inclusion in the Development blueprint. #### The WPCC - Programs: N/A — no funding/program content in source. - Projects: N/A — no governance content in source. - Funding experiments: N/A — no funding content in source. ### FAIR - Technical independence: N/A — source does not discuss federation or provenance. - Policies and covenants: N/A — not in scope of source. - Productized governance artifacts: N/A — not in scope of source. ## 🧪 Hypotheses - Teams that adopt a shared custom blueprint reduce average local-site setup time measurably versus manual setup. - The Development blueprint increases use of Create Block Theme and Plugin Check among Studio users who pick it. - Most custom blueprints will install primarily from the WordPress.org repository rather than GitHub. - Blueprint-based site creation has a higher abandonment rate during the longer download/apply step than blank-site creation. ### 📊 Methodology - Instrument Studio telemetry to compare time-to-ready for blueprint vs. blank sites. - Survey Studio users on whether they author custom blueprints and from which sources they install. - A/B the featured-blueprint screen to measure selection rates across Quick Start / Development / Commerce. - Track plugin activation rates downstream of each featured blueprint. ### ❓ Questions - What does the full blueprint JSON schema support beyond the demoed steps? - How are secrets or credentials handled if a blueprint runs WP-CLI or installs from private GitHub repos? - Can blueprints be versioned and shared via a registry, or only as local files? - Does Studio validate a blueprint before running it, or fail mid-build? ### 🔮 Future Research - Comparison of Studio blueprints with WordPress Playground blueprints — schema overlap and portability. - Patterns in community-authored blueprints once a sharing mechanism exists. - Failure modes of long-running blueprint builds and recovery behavior. ### 💡 Implications - Practice: codifying local environments lowers setup friction and onboarding cost for dev teams. - Policy: organizations may want review gates for blueprints that install from outside WordPress.org. - Security: WP-CLI and arbitrary install sources widen the trust surface of a shared blueprint. - Education: a clear, example-driven schema doc becomes the main lever for adoption. - Funding models: N/A — source does not address funding. ### 🧠 Learning Styles Assessment - Reading level estimate: Flesch-Kincaid Grade ~8 — conversational tutorial narration, short clauses, common vocabulary. #### 👀 Visual learners - Present: screen-recorded UI walkthrough showing buttons, screens, and the sample JSON. - Improve: add an architecture diagram of blueprint → site, and captioned before/after of the admin. #### 🔊 Aural learners - Present: narrated video audio. - Improve: offer a 2-minute audio recap and downloadable speaker notes. #### 🗣️ Verbal learners - Present: the "recipe" analogy for blueprints; plain-language definitions. - Improve: add a glossary entry for WP-CLI, user meta, and PHP version pinning. #### 🧩 Kinesthetic learners - Present: step-by-step click-through the viewer can follow live in Studio. - Improve: provide a downloadable sample-blueprint.json and a checklist to author one. #### 🧠 Logical learners - Present: implicit decision among three featured blueprints by use case. - Improve: a decision table mapping use case → recommended blueprint and a schema field reference. #### 🧑‍🤝‍🧑 Social learners - Present: like/subscribe call to action. - Improve: link a community space to share blueprints and ask questions. #### 🧘‍♀️ Solitary learners - Present: self-paced video the viewer follows alone. - Improve: a self-check ("does your blueprint install, theme, and set settings?") worksheet. #### 🧠 Logical learners - N/A — covered above; duplicate subtype, no additional content. #### 🌿 Naturalistic learners - Present: none. - Improve: frame reproducible environments as reducing wasted rebuild effort (lifecycle thinking). ### 📊 Accessibility Assessment #### Screen reader semantics - Present: N/A — source is a video transcript; no document headings or alt text to assess. - Improve: publish a structured text companion with headings for the steps. #### Keyboard navigation - Present: N/A — not assessable from a transcript. - Improve: confirm Studio's blueprint flow is fully keyboard reachable. #### Contrast and readability - Present: N/A — not assessable from a transcript. - Improve: verify the featured-blueprint cards meet 4.5:1 contrast. #### Text resizing and reflow - Present: N/A — not assessable from a transcript. - Improve: confirm Studio UI reflows at 200% zoom. #### Media and captions - Present: a transcript exists (this source). - Improve: ship human-verified captions and a downloadable transcript; avoid autoplay. #### Forms and interactions - Present: the add-site flow includes a site-name field and file picker. - Improve: ensure the Choose Blueprint file picker and name field have clear labels and inline validation. #### Standards reference - Map gaps to WCAG 2.2 AA: 1.2.2 Captions, 1.4.3 Contrast, 1.4.10 Reflow, 2.1.1 Keyboard, 3.3.2 Labels. ### 🌍 DEIB Assessment #### Cultural breadth - Present: none — single-presenter product demo, no regional examples. - Improve: localized walkthroughs and multilingual captions. #### Inclusive language - Present: neutral, jargon-light narration; technical terms mostly explained. - Improve: define WP-CLI and user meta inline for newcomers. #### Neurodiversity support - Present: short, consistent step structure; predictable flow. - Improve: on-screen step numbers and icon+text labels for each action. #### Representation - Present: N/A — no people or identities depicted beyond the narrator. - Improve: feature varied community contributors in follow-up content. #### Psychological safety - Present: encouraging, low-pressure "I encourage you to check the docs" framing. - Improve: add a "common mistakes / how to recover" note for failed builds. ### ✅ Logical Validity #### Strong reasoning - Inductive, ~02:20: "if you find yourself creating the same local sites ... consider turning that into a blueprint" — generalizes from a real repeated-work pattern to a reuse recommendation. Strong because the premise (repeated identical setup) reliably supports the conclusion (codify it). Clarify by quantifying the time saved. - Analogical, ~01:10: blueprint-as-recipe — apt analogy; a recipe lists ingredients and steps just as a blueprint lists plugins, theme, and settings. Clarify by noting where the analogy breaks (recipes don't run WP-CLI). #### Fallacies - Mild appeal to authority / popularity, ~04:50: "consider liking and subscribing" — standard CTA, not an argument flaw, but it's persuasion unrelated to the claim's merits. Fix: keep CTA separate from technical claims (already is). - No substantive logical fallacies; this is a procedural product demo, not an argument. #### Tone of voice - Friendly, instructional, lightly enthusiastic. Examples: "the Development option, which is my favorite," "that's how easy it is." ### 🛡️ DARVO Analysis - Deny: N/A — no accusation or wrongdoing context; nothing denied. - Attack: N/A — no accusers or critics addressed. - Reverse victim/offender: N/A — no victim/offender framing present. - This is a neutral product tutorial; DARVO patterns do not apply. ## 🎯 Conclusion - Bottom line: Studio blueprints turn repeated local-site setup into a reusable JSON recipe, with three featured options and the option to author your own. - Next steps for readers: update Studio (or download it for Mac/Windows), try the Development or Commerce blueprint, then author a custom blueprint from your usual stack and consult the documentation for advanced steps like WP-CLI. ## 🔄 Refactor Appendix — How to use Blueprints in 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. ### 📚 Literature Atoms (H3) #### [H1] Blueprints are JSON recipes that build local sites > [!quote] ID:rw_transcript > Blueprints are just a JSON file that describe how a site is built in WordPress Studio. **Context & use**: - ~01:10 in the video, defining blueprints under the featured-blueprint screen. - Matters because it frames blueprints as portable, version-controllable config, not opaque app state. **Tags**: #xref **Highlight**: [view highlight](readwise://) <!-- atomicity: 1 idea ✓ --> #### [H2] Codify repeated local-site setups into a blueprint > [!quote] ID:rw_transcript > if you find yourself creating the same local sites with the same plugins, same theme, same site settings over and over again, consider turning that into a blueprint **Context & use**: - ~02:20, the pitch for authoring custom blueprints. - Matters because it states the core workflow trigger: detect repetition, then automate it. **Tags**: #xref #aphorisms **Highlight**: [view highlight](readwise://) <!-- atomicity: 1 idea ✓ --> ### 🧠 Permanent Candidates (H4) #### [P1] Reproducible environments encode repeated setup as config **Claim** (one sentence, Courtney's voice): Treating a repeated local-dev setup as a declarative file makes the environment reproducible, shareable, and reviewable. **Evidence pointer**: [[#H2]] **Scope & conditions**: Holds when setup is genuinely repeated and stable; breaks when each project needs a meaningfully different stack, where a template adds overhead without reuse. **Links**: - [[Infrastructure as code]] — because extends - [[WordPress Playground blueprints]] — because contrasts on runtime target <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Compare Studio blueprint schema vs. WordPress Playground blueprint schema — https://www.youtube.com/watch?v=YKLHP_ADj6o #fleeting #inbox - [F2] Find the official Studio blueprints documentation for the full step list. #fleeting #inbox ### → Things 3 (max 2 actions) - [ ] Author a sample Studio blueprint mirroring my usual local stack — local dev #things - [ ] Read the Studio blueprints docs for advanced WP-CLI steps — research #things <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/How to Use Blueprints in WordPress Studio.md|How to Use Blueprints in WordPress Studio by WordPress.com]] ## Highlights - Blueprints are just a JSON file that describe how a site is built in WordPress Studio. This could include the preferred WordPress and PHP versions, which plugins and themes to install, as well as what content and settings to apply. The Quick Start option gives you a WordPress.com-like environment with a collection of plugins. And the Development option, which is my favorite, is geared towards WordPress theme and plugin developers and includes utility plugins such as the Create Block Theme plugin, and others like Plugin Check. ([View Highlight](https://read.readwise.io/read/01kw2mz7fkccmgcha0dsrzjzay)) - Note: Blueprints = portable JSON describing how Studio builds a site (WP/PHP versions, plugins, themes, content, settings). - Tags: blueprints, atom/literature/h1 - Blueprints are all about improving your workflows. So if you find yourself creating the same local sites with the same plugins, same theme, same site settings over and over again, consider turning that into a blueprint. Let's take a quick look at an example here. I have a sample blueprint, and this one's pretty basic, but if we take a look, we can see that it's doing a bunch of things. ([View Highlight](https://read.readwise.io/read/01kw2mza81q36h2eh53a3749q0)) - Note: The custom-blueprint pitch: codify repeated local-site setups (same plugins/theme/settings) into one reusable config. - Tags: blueprints, atom/literature/h2 ## Links - [[3. Resources/Permanent Notes/Data-Model-First Releases Reduce Decision Coupling]] — evidence-for: a portable JSON environment specification separates repeatable setup decisions from one-off execution. - [[3. Resources/Permanent Notes/Emulated Local Dev Trades Production Fidelity for Zero-Setup Speed]] — applies-in: Blueprints make the emulated environment repeatable without eliminating its production-fidelity limits.