# Reproducible Environments Encode Repeated Setup as Config ## Claim Treating a repeated local-dev setup as a declarative file makes the environment reproducible, shareable, and reviewable, instead of trapped as one-off manual clicks on one machine. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds when the setup is genuinely repeated and stable across projects (same plugins, theme, settings). - Breaks when each project needs a meaningfully different stack — writing and maintaining a template then costs more than it saves. - The claim is about local-dev tooling specifically here (WordPress Studio Blueprints); the underlying principle is the general infrastructure-as-code argument, not a WordPress-specific one. ## Evidence WordPress Studio's Blueprints are described plainly as configuration, not app state: "Blueprints are just a JSON file that describe how a site is built in WordPress Studio." The trigger for adopting one is explicit and behavioral: "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" — repetition detected, then encoded once. ## Links - [[DevRel MOC]] — turning repeated setup pain into something shareable and reviewable - [[3. Resources/Permanent Notes/Pick a Local WordPress Environment by Use Case Not Vendor Label]] — because applies-in; Blueprints is one of the features that stays valuable even where Studio's other gaps (DB access, live-site import) rule it out for certain work. - [[3. Resources/MOCs/WordPress Hosting Security Stack MOC]] — because applies-in; declarative, version-controllable environment config is a hosting/dev-stack hygiene practice broader than this one tool. ## Tests / falsifiers - Find a case where blueprint maintenance overhead (keeping the JSON in sync with an evolving real setup) exceeded the time saved vs. manual setup — would bound the "breaks when" condition more precisely. - Compare setup-time and error-rate for blueprint-driven site creation vs. manual click-through setup across a handful of real projects. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Literature Notes/How to use Blueprints in WordPress Studio]] — defines the blueprint format and states the repetition-to-config trigger directly.