WordPress / WordPress/php-toolkit

[Blueprints v2] Constraint the Blueprint bundle format

Open
#132 4 comments 0 reactions 1 assignee View on GitHub

@JanJakes is already working on this.

Since Jul 28, 2025.

Blueprints enhancement
Dominant language
PHP
Stars
61
Forks
21
Avg merge
19h 34m
Merged PRs (30d)
7

Description

The Blueprints v2 spec defines a required bundle directory structure. Let's make sure any bundle not following this structure is rejected by the PHP runner. cc @janjakes

blueprint.json
wp-content/
└─── plugins/
|    └─── akismet.zip
|    └─── custom-meta-box.php
|    └─── hello-dolly/
|         └─── hello-dolly.php
└─── mu-plugins/
|    └─── 0-check-integrity.zip
└─── themes/
|    └─── twentytwentythree/
|         └─── style.css
|         └─── functions.php
|         └─── screenshot.jpg
└─── languages/
|    └─── plugins/
|         └─── akismet/
|              └─── akismet-en_US.po
|              └─── akismet-en_US.mo
|              └─── akismet-de_DE.po
|              └─── akismet-de_DE.mo
|    └─── themes/
|         └─── twentytwentythree/
|              └─── twentytwentythree-en_US.po
|              └─── twentytwentythree-en_US.mo
|    └─── en_US.po
|    └─── en_US.mo
|    └─── de_DE.po
|    └─── de_DE.mo
└─── uploads/
|    └─── fonts/
|         └─── open-sans.woff2
|         └─── roboto.woff2
|         └─── ...
|    └─── 2024/
|         └─── 01/
|              └─── image.jpg
|              └─── video.mp4
|              └─── audio.mp3
|              └─── document.pdf
|              └─── other.txt
└─── content/
     └─── dump-1.sql
     └─── dump-2.sql
     └─── dump-3.sql
     └─── bike-repair-shop.wxr
     └─── posts/
           └─── posts/
				└─── 2025-01-01-my-first-post.html
           └─── pages/
                └─── books/
                     └─── post-type.json
                     └─── the-old-man-and-the-sea.html
                     └─── harry-potter.md

Contributor guide

No contributing guide indexed for this repository

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.