WordPress / WordPress/php-toolkit
Project Roadmap
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 61
- Forks
- 21
- Avg merge
- 19h 34m
- Merged PRs (30d)
- 7
Description
Blueprints library – version 0.1 for early adopters
- Feature completeness
- wp-blueprints CLI tool to prove it works natively
- Command to execute a Blueprint
- Command to turn Blueprint into a Snapshot (.zip bundle)
- Integrate into WordPress Playground to prove it works with WASM
- Figure out the development workflow
- Figure out the version update workflow
- https://github.com/WordPress/blueprints-library/issues/87
- Decide what to do when WordPress directory already exists – delete? Act on that WordPress instance?
- wp-blueprints CLI tool to prove it works natively
- Distribution
- CLI tool documentation
- The default --help message
- Web page with Quick start and usage examples
- Build flow
- Building a minified ~200kb .phar library to use in Playground
- Building a CLI tool as .phar
- Distribution
- Scripts to publish GitHub releases
- CLI tool documentation
- Superior quality from day 1
- Exception handling when running steps
- #108
- Unit Tests
- HTTP Client
- All Blueprint steps
- ZIP processing
- Parsing and compiling for all input types: JSON string, stdClass and
Blueprint - Blueprint Mapper
- Blueprint Validator
- Improve JSON Schema discriminator-related error messages
- Code formatter setup (PHPCBF)
- Contributor docs
- Setting up the project
- JSON Schema as the source of truth
- Regenerating models classes
- How to build the phar library with box ?
- Why include dependencies in the repo? (PHP 7.0 - 8.3 compat, composer constraints issues)
- Optional: static code analysis (PHPCS) for PHP 7.0 – 8.3 – PHPUnit solves a similar problem
- https://github.com/WordPress/blueprints-library/pull/86
1.0 Stable Release
- Research
- Settle on the Blueprint schema
- Explore integration with wp-env
- Explore runtime adapters
- Other
- Blueprint library consumer documentation – tutorials, examples, API reference
- @php-wasm/cli support – there's a few functions to wrap in Asyncify
- Downloads caching for both native PHP and PHP.wasm
- Scripts to publish composer packages
- Windows Compatibility
1.1 Extra features
- wp-cli plugin
- Publish Composer Packages
- WordPress plugin (Integrate with the WordPress Playground plugin? Build a new one?)
- Explore Custom Post Types handling in Blueprint
Future – Path to WordPress Core
- Refactor to WordPress Coding Standards
- Integrate into WordPress core
cc @reimic
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
Review the linked issues #87, #27, #108, and #3, along with pull request #86, to separate this roadmap into specific deliverables. Start with one unchecked area such as CLI commands, Playground integration, phar builds, documentation, or unit tests; done should be defined by a dedicated issue with a focused scope and verification steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wasm
- Domain
- build-system, cli, documentation, release, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100