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

Snapshots Support

Open
#9 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

No file, test, or entry point is named. Start by reading the Blueprint and Snapshot examples in the issue and the repository context, then clarify how their contents should relate across the described spectrum. Done means an agreed relationship and an actionable implementation scope.

Written by the indexing model from the issue text.

Description

Architecture Snapshots

Let's define the relationship between Snapshots and Blueprints.

  • When writing Blueprints, it's useful to include some files, e.g. private plugins. If Blueprints required shipping them in wp-content/plugins, that starts resembling a Snapshot.
  • A Snapshot exported from WordPress could include a Blueprint like {"theme": "twentytwentythree"} instead of shipping the actual files. That's a smaller archive and an up-to-date theme import.

Blueprints and Snapshots are a spectrum, not distinct ideas

The smallest WordPress setup description is an empty Blueprint {}.

The most extensive description is a full Snapshot + Playground binary bundled as a double click executable – click, and that exact site runs on your computer.

There's so much in between, though:

  • A Blueprint file with some plugins, themes, and site options
  • A Blueprint file + a wp-config.php
  • A Blueprint file with a few plugins + wp-content with more plugins and themes
  • A full snapshot with a Blueprint to update the WordPress version
Dominant language
PHP
Stars
61
Forks
22
Avg merge
19h 34m
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.