Bedrock vs Regular WordPress Installs
A better structure for your WordPress installation.
.@rootswp https://t.co/6xT02jiH64 professionalizes WordPress development and should be the default starting point for any WordPress site.
— Robbert vt Westende (@piepkrak) May 12, 2015
Been using the Bedrock stack (https://t.co/I2dj7LwAFv) for all my WP dev over the last four months. Can't recommend it enough.
— Chris Waters (@christhesoul) August 5, 2014
| Bedrock | Standard WordPress |
WordPlate | WP-Stack | |
|---|---|---|---|---|
| Separate configs per environment | ✅ | ❌ | ❌ | ✅ |
| Environment variables | ✅ | ❌ | ✅ | ❌ |
| Enhanced security | ✅ | ❌ | ✅ | ❌ |
| Custom wp-content directory | ✅ | ❌ | ❌ | ✅ |
| Composer for managing WordPress installation | ✅ | ❌ | ✅ | ❌ |
| Composer for managing WordPress plugins and themes | ✅ | ❌ | ✅ | ❌ |
| PSR-2 coding standards | ✅ | ❌ | ✅ | ❌ |
| mu-plugins autoloader | ✅ | ❌ | ❌ | ❌ |
Bedrock’s structure
site/
├── config/
│ ├── environments/
│ │ ├── development.php
│ │ ├── staging.php
│ │ └── production.php
│ └── application.php # Primary wp-config.php
├── vendor/ # Composer dependencies
└── web/ # Virtual host document root
├── app/ # WordPress content directory
│ ├── mu-plugins/
│ ├── plugins/
│ ├── themes/
│ └── uploads/
└── wp/ # WordPress core
Standard WordPress structure
site/
├── index.php
├── license.txt
├── readme.html
├── wp-activate.php
├── wp-admin/
├── wp-blog-header.php
├── wp-comments-post.php
├── wp-config-sample.php
├── wp-content/
│ ├── index.php
│ ├── plugins/
│ └── themes/
├── wp-cron.php
├── wp-includes/
├── wp-links-opml.php
├── wp-load.php
├── wp-login.php
├── wp-mail.php
├── wp-settings.php
├── wp-signup.php
├── wp-trackback.php
└── xmlrpc.php
Better security
Bedrock’s web root is isolated to limit access to non-web files. Bedrock also has more secure passwords through the wp-password-bcrypt plugin.
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.
I don’t mean to sound overly dramatic, but coming across Bedrock and Sage has completely changed the way that I code (and much for the better).
I swore to never touch WordPress again until I found Bedrock :) Composer and git all the things!
If I absolutely need to develop a WordPress site, I use the Roots stack. Trellis, Bedrock, Sage are the best thing to ever happen to any developer working with WordPress.
Working with WordPress on two projects over the next few months, the folks at Roots really have some amazing resources!
Digging back into learning in my favorite stack to developing WordPress sites, Roots. The people who’ve worked hard on this project have really made a wonderful tool for getting a development environment with parity setup super quick!
The first step is building your WordPress site correctly, and for me, that starts with using Trellis and Bedrock.
Roots stack will either teach you a lot, or make you feel right at home depending on your background. Either way. It’s a no brainer for WP development at a professional level.
Sage, Bedrock, and Trellis by Roots have challenged me to become a better WordPress developer over the years & modernize my toolset.
Bedrock professionalizes WordPress development and should be the default starting point for any WordPress site.
Been using the Bedrock stack for all my WordPress development over the last four months. Can’t recommend it enough.
Colin OBrien