WordPress / WordPress/php-toolkit
Blueprints: Merging Blueprints
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- PHP
- Stars
- 61
- Forks
- 21
- Avg merge
- 19h 34m
- Merged PRs (30d)
- 7
Description
I want to be able to merge these two Blueprints:
{
"landingPage": "/wp-admin/",
"steps": [
// .. Set up a blog ...
]
}
{
"steps": [
// .. Set up a woo store ...
]
}
And get a single Blueprint which sets up a site that's both a blog and a store
Known plugins with a Blueprint.json file
Let's use these Blueprints to explore the merging process
- https://github.com/jdevalk/fewer-tags/blob/main/.wordpress.org/blueprints/blueprint.json
- https://wordpress.org/plugins/interactive-code-block
Related
- https://github.com/WordPress/wordpress-playground/issues/201
- WordPress/blueprints#33
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the two example blueprint.json files linked in the issue and read the related WordPress/wordpress-playground#201 and WordPress/blueprints#33 discussions. Define how their fields and steps should combine, then verify that the result produces one Blueprint capable of setting up both a blog and a store.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100