WordPress / WordPress/php-toolkit
Publish Composer Packages
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 61
- Forks
- 21
- Avg merge
- 19h 34m
- Merged PRs (30d)
- 7
Description
The explorations in this repo will likely yield multiple useful libraries, like:
- Blueprints
- Stream processing
- Zip Decoder/Encoder
- Runtime compatibility layer
They could be packaged and published as Composer packages on https://packagist.org/. Brownie points for doing the same with the recent addition to WordPress core that is WP_HTML_Tag_Processor.
cc @dmsnell
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 listed library areas—Blueprints, stream processing, ZIP encoding/decoding, the runtime compatibility layer, and WP_HTML_Tag_Processor—and determine which are independently packageable. Check Packagist’s Composer package requirements and define the package boundaries, metadata, and publishing process before implementation; done means the selected libraries are published as usable packages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100