WordPress boilerplate with modern development tools, easier configuration, and an improved folder structure
# Create a new Bedrock project
$ composer create-project roots/bedrock
# Add plugins with Composer
$ composer require wpackagist-plugin/safe-redirect-manager
$ composer require wpackagist-plugin/simple-page-ordering
$ composer require wpackagist-plugin/woocommerce
Better WordPress project structure
The organization of Bedrock is similar to putting WordPress in its own subdirectory but with some improvements, including renaming wp-content/ to app/.
├── composer.json
├── config
│ ├── application.php
│ └── environments
│ ├── development.php
│ ├── staging.php
│ └── production.php
├── vendor
└── web
├── app
│ ├── mu-plugins
│ ├── plugins
│ ├── themes
│ └── uploads
├── wp-config.php
├── index.php
└── wpDependency management with Composer
Manage your WordPress install and plugins with Composer, a PHP dependency manager. Composer will make development more reliable, help with team collaboration, and it helps maintain a better Git repository.
Easy WordPress configuration
Environment specific configuration files and environment variables with Dotenv.
Enhanced Security
Isolated web root to limit access to non-web files and more secure passwords through wp-password-bcrypt.
Built with Bedrock
What others say
Bedrock professionalizes WordPress development and should be the default starting point for any WordPress site.
Bedrock is doing a huge service to the WordPress community, and I can see it being adopted as the standard for WordPress development. Hopefully as more people adopt it, the developer community at large will view WordPress sites on similar footing as more "professional" platforms.
Why Bedrock, not a regular WordPress install?
Bedrock gives you a better structure for your WordPress installation with modern development tools. Compare Bedrock with vanilla WordPress
Colin OBrien