Switch WordPress Composer guides from WPackagist to WP Packages and roots/wordpress

[retlehs]

This PR updates Platform.sh's WordPress Composer guides to use WP Packages (instead of WPackagist) and roots/wordpress (instead of johnpbloch/wordpress-core).

Disclosure: I maintain WP Packages and Bedrock. The tables below try to be even-handed — flag anything that reads as biased and I'll fix it.

WPackagist vs WP Packages

	WPackagist	WP Packages
Launched	2012	2025
Operator	WP Engine (acquired March 2026, previously Outlandish)	Roots / community-funded via GitHub Sponsors
Track record	12+ years	New, less battle-tested
Composer v2 metadata-url	No	Yes
Update frequency	~1.5 hours	5 minutes
Cold Composer resolve	baseline	~17× faster (benchmarks)
Source publication	Application code only	Application + infrastructure + deployment
Untagged plugin installs	Mutable trunk zips	Pinned SVN revisions
Closed plugins	Continues serving	Removed in lockstep with wp.org

johnpbloch/wordpress-core vs roots/wordpress

	johnpbloch/wordpress-core	roots/wordpress
Started	2013	2014
Maintainer	John P Bloch	Roots org
Track record	10+ years	10+ years
Build flavors	Single package	Meta-package family: roots/wordpress, -full, -no-content
Beta/RC releases	No	Yes (via roots/wordpress-full)
Companion installer	Required as separate dep (johnpbloch/wordpress-core-installer ^2.0)	Pulled in transitively by roots/wordpress (no separate require needed)
Ecosystem	Standalone	Pairs with Bedrock, Sage, Trellis

Files intentionally left alone

These reference Platform.sh's platformsh-templates/wordpress-composer template (and upsun/snippets/wordpress-composer), which use johnpbloch internally. I left them as-is to avoid documenting one stack while pointing readers at a different one — but worth flagging that platformsh-templates/wordpress-composer is now marked "no longer maintained" (same as wordpress-bedrock). If those templates are being sunset, these guides may want their own pass to either point at maintained alternatives or use upstream Bedrock directly (the approach the Upsun bedrock guide already takes):

• sites/platform/src/guides/wordpress/deploy/_index.md — heavily template-bound; explicitly documents the wordpress-composer template's structure
• shared/data/templates.yaml L602 — template metadata
• sites/upsun/src/get-started/stacks/wordpress/composer.md — references the upsun snippets WordPress Composer example

Bedrock-flavored guides already in sync

The Upsun bedrock guide (sites/upsun/src/get-started/stacks/wordpress/bedrock.md) delegates to upstream Bedrock via composer create-project roots/bedrock, which already uses WP Packages and dropped roots/wp-password-bcrypt (current Bedrock removed it after WP 6.8 shipped native bcrypt). No changes needed there — flagging for completeness.

Companion PRs

Even though the two template repos are marked "no longer maintained," I've also opened community-contribution PRs to refresh them — in case those templates aren't fully sunset and/or for the benefit of anyone forking them:

• platformsh-templates/wordpress-composer#470 — switches the template from johnpbloch/wordpress-core to roots/wordpress and from WPackagist to WP Packages
• platformsh-templates/wordpress-bedrock#1010 — syncs the template with current upstream Bedrock (drops wp-password-bcrypt, adopts WP Packages, modernizes config/application.php)

Open to feedback on framing. Happy to close if it's not the direction you want.