A modern WordPress stack
- Dependency management with Composer
- Better folder structure
- Easy WordPress configuration with environment specific files
- Environment variables with Dotenv
- Whoops is a nice little library that helps you deal with errors and exceptions in a less painful way.
- Autoloader for mu-plugins (use regular plugins as mu-plugins)
- Debug Bar Adds a debug menu to the admin bar that shows query, cache, and other helpful debugging information.
- Developer A plugin, which helps WordPress developers develop.
- [Stage Switcher] Detects all the enviroments in WordPress.
- MultisiteDirectoryResolver Adds filters that correct directory paths in a Wordpress multisite install with the WordPress installation in a custom subfolder.
- Koodimonni composer lang support
We are using WordPress Packagist for plugins. To add a plugin from the WordPress Plugin Directory add the to the required array in the composer.json file. Specify them with
wpackagist-plugin following by the plugin slug name. Example below.
Please note that this also works with themes and WordPress multi-site plugins.
- PHP >= 5.4
Install Bedrock Multisite by issuing the Composer
create-project command in your terminal:
composer create-project gwa/bedrock-multisite-skeleton
.envand update environment variables:
DB_NAME- Database name
DB_USER- Database user
DB_PASSWORD- Database password
DB_HOST- Database host
WP_ENV- Set to environment (
WP_HOME- Full URL to WordPress home (http://example.com)
WP_SITEURL- Full URL to WordPress including subdirectory (http://example.com/wp)
- Access WP admin at
Read more about setting up
Bedrock Multisite on our installation documentation page.
Any other deployment method can be used as well with one requirement:
composer install must be run as part of the deploy process.
Contributions are welcome from everyone. We have contributing guidelines to help you get started.
Keep track of development and community news.