Skip to content

Switch Composer docs from WPackagist to WP Packages#10063

Open
retlehs wants to merge 2 commits into
pantheon-systems:mainfrom
retlehs:main
Open

Switch Composer docs from WPackagist to WP Packages#10063
retlehs wants to merge 2 commits into
pantheon-systems:mainfrom
retlehs:main

Conversation

@retlehs

@retlehs retlehs commented May 4, 2026

Copy link
Copy Markdown

This PR updates references in the docs from WPackagist to WP Packages. WP Packages is a faster, independent, fully open-source alternative to WPackagist with the same purpose (mirrors WordPress.org plugins/themes as Composer packages):

One factual fix worth calling out: guides/integrated-composer/03-dependencies.md previously stated that WPackagist "is included with Bedrock out of the box" — Bedrock migrated from WPackagist to WP Packages, so that line is now outdated. This PR brings it back in sync with current Bedrock.

Change pattern

  • https://wpackagist.orghttps://repo.wp-packages.org (Composer endpoint) or https://wp-packages.org (prose links)
  • wpackagist-plugin/foowp-plugin/foo
  • wpackagist-theme/foowp-theme/foo
  • "WPackagist" / "WordPress Packagist" → "WP Packages" in prose

Happy to adjust anything.

Disclosure: I maintain WP Packages and Bedrock.

@retlehs retlehs requested review from a team as code owners May 4, 2026 00:44
@pantheon-site-integration pantheon-site-integration Bot temporarily deployed to pr-10063 May 4, 2026 00:45 Inactive
@pantheon-site-integration

Copy link
Copy Markdown

Successfully created multidev environment: pr-10063

@jazzsequence

Copy link
Copy Markdown
Contributor

Hey @retlehs 👋
Thanks for this! If we're making this change, I'm fine with defaulting to WP Packages but I don't want to be exclusivist about what repository to use. I'm going to tweak this PR a bit to include references to both WP Packages and WPackagist so users can choose which one they want to use.

@jazzsequence jazzsequence self-assigned this May 11, 2026
@jazzsequence jazzsequence added Type: Fix Content Issue or PR to resolve incorrect information in the docs Topic: WordPress WordPress-specific labels May 11, 2026
jazzsequence
jazzsequence previously approved these changes May 11, 2026

@jazzsequence jazzsequence left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated docs to include both WPackagist and WP Packages as examples.

Comment thread src/source/content/guides/build-tools/09-update.md Outdated
Comment thread src/source/content/guides/integrated-composer/01-introduction.md Outdated
Comment thread src/source/content/guides/integrated-composer/03-dependencies.md
Comment thread src/source/content/guides/integrated-composer/03-dependencies.md Outdated
Comment thread src/source/content/guides/integrated-composer/03-dependencies.md Outdated
Comment thread src/source/content/guides/integrated-composer/03-dependencies.md Outdated
Comment thread src/source/content/guides/integrated-composer/03-dependencies.md Outdated
Co-authored-by: Chris Reynolds <chris@jazzsequence.com>
@pantheon-site-integration

Copy link
Copy Markdown

Successfully created multidev environment: pr-10063

[WP Packages](https://wp-packages.org) is a Packagist-like mirror of the WordPress.org [plugin](https://wordpress.org/plugins) and [theme](https://wordpress.org/themes) repositories and is included with Bedrock out of the box.

You can install packages from Packagist or WPackagist without any additional configuration using `composer require`.
[WPackagist](https://wpackagist.org) is another longstanding Composer mirror for WordPress plugins and themes maintained by [WPEngine in 2026](https://wpengine.com/blog/wp-engine-acquires-wpackagist/).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
[WPackagist](https://wpackagist.org) is another longstanding Composer mirror for WordPress plugins and themes maintained by [WPEngine in 2026](https://wpengine.com/blog/wp-engine-acquires-wpackagist/).
[WPackagist](https://wpackagist.org) is another longstanding Composer mirror for WordPress plugins and themes acquired by [WPEngine in 2026](https://wpengine.com/blog/wp-engine-acquires-wpackagist/).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@stevector I felt like documenting acquisitions was putting our thumb on the needle a little more than I'd like, but I recognize that "maintained by __ in ___" sounds off. what about:

Suggested change
[WPackagist](https://wpackagist.org) is another longstanding Composer mirror for WordPress plugins and themes maintained by [WPEngine in 2026](https://wpengine.com/blog/wp-engine-acquires-wpackagist/).
[WPackagist](https://wpackagist.org) is another longstanding Composer mirror for WordPress plugins and themes maintained by [WPEngine since April 2026](https://wpengine.com/blog/wp-engine-acquires-wpackagist/).

?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Topic: WordPress WordPress-specific Type: Fix Content Issue or PR to resolve incorrect information in the docs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants