This is Pantheon's recommended starting point for forking new WordPress upstreams that work with the Platform's Integrated Composer build process. It is also is intended to be the Platform's standard WordPress with Composer upstream.
Unlike with other Pantheon upstreams, the WordPress core install, which you are unlikely to adjust while building sites, is not in the main branch of the repository. Instead, it is referenced as dependencies within Roots/Bedrock that are installed by Composer.
This tool is an early stage, proof-of-concept and is not recommended for use on production sites.
While the architecture and directory structure of this upstream is unlikely to change, some notable things need to happen before this upstream is fully ready for prime time.
/packages/*should be in their own repositories - Right now, thepantheon-wp-config,pantheon-wp-loader,pantheon-wp-mupluginandwordpress-integrationspackages are being loaded in as path repositories. Each of these should live in their own repositories, published on Packagist and pulled in via Composer.- Development script - In the future, it would be beneficial to have a script that set up the
/packages/folder for local development on those individual repositories, so that you could do all development within a single environment. This script would clone those repositories into/packages/so they would be used in place of the Packagist versions.
Contributions are welcome in the form of GitHub issues and pull requests. If you would like to propose a change, please fork pantheon-systems/wordpress-bedrock-recommended and submit a PR to that repository.
The /packages/ directory can be used as a local path repository if you want to do development on any of the pantheon-systems packages included in this project. Simply git clone any dependency package into /packages/ and then composer update will use your local versions rather than the public ones managed by Packagist.