WordPress Quickstart Format

Snapshots and Blueprints go hand in hand. Let's find a convenient way for a developer to type in a single command, like wp up, and get a WordPress site built / served based on the current directory contents.

For example, I could have just some themes, plugins, etc:

    ./wp-config.php
    ./wp-content
    ./wp-content/database
    ./wp-content/themes/twentytwentythree
    ./wp-content/plugins/gutenberg
    ./wp-content/plugins/woocommerce
    ./wp-content/mu-plugins
    … etc …

Or, I could have just a Blueprint:

    ./blueprint.json

Or I could have both:

    ./blueprint.json
    ./wp-content/plugins/gutenberg

This is, more or less, what wp-env and wp-now do today. They could converge into a single tool.

Open questions

• Should the WordPress directory structure be required?
• Should the local directory change as a result of wp up? E.g. should the downloaded themes be unzipped in wp-content/themes? And should there be a wp reset command to restore the original site? And how it would work under the hood?
• Should wp up create a new, ephemeral site? Or always the same site running from that local directory? Or should that be a matter of the runtime adapter used? Or a CLI switch? Like --temporary or --permanent?

cc @danielbachhuber @noahtallen @sejas @dmsnell @youknowriad @mtias

Start by comparing the current behavior of wp-env and wp-now, then read the linked Blueprints issues 9 and 1. The issue leaves directory requirements, persistence, reset behavior, and runtime-adapter responsibilities open. Done would require an agreed design for a single command and its site lifecycle.