Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

WordPress Quickstart Format

Open
  • Is something wrong?
#11 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
php, wordpress
Domain
cli

Research direction

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.

Written by the indexing model from the issue text.

Description

Architecture

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

Dominant language
PHP
Stars
61
Forks
23
Avg merge
20h 9m
Merged PRs (30d)
7

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from WordPress/php-toolkit

All issues in WordPress/php-toolkit

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.