Publish Composer Packages

Open
#3 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
php
Domain
release

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.

Description

The explorations in this repo will likely yield multiple useful libraries, like:

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

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

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.

More from WordPress/php-toolkit

All issues in WordPress/php-toolkit

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.