Bedrock — structured, secure and Composer-powered
Bedrock is a modern WordPress stack that simplifies configuration and customisation by integrating seamlessly with Composer. With a well-organised project structure and top-notch development tools, kick off professional WordPress projects the right way.
What is Bedrock?
Bedrock is a WordPress stack designed to streamline configuration and customisation of WordPress installations by integrating with Composer — the standard PHP dependency manager. With comprehensive development tools and a well-organised project structure, developers can kick off projects efficiently. Over 9 years of continuous maintenance has made it the most widely used Composer-based WordPress setup.
Cutting-edge WordPress boilerplate
Over 9 years of continuous maintenance. Enhanced Git integration. Seamless Composer workflow. Bedrock gives your WordPress projects a robust, well-established foundation.
Composer for WordPress
Manage WordPress Core, plugins, and themes as versioned Composer packages. Running composer install builds the entire site — no dashboard clicks, no manual FTP uploads. Reproducible builds every time.
Enhanced security
Bedrock's file structure limits access to non-public files — only the web/ directory is the public web root. Config files and credentials sit outside browser reach. Includes wp-password-bcrypt for stronger password hashing.
Environment-specific config
Uses Dotenv to set up different config values for local, staging, and production environments. Sensitive database credentials and API keys live in a .env file — never committed to your repository.
Git-friendly workflow
WordPress Core is git-ignored and managed by Composer — your repository contains only your actual code. Enables proper team collaboration, code review, and pull request workflows that traditional WordPress cannot support cleanly.
CI/CD deployment ready
Bedrock's structure is built for automated pipelines. Deploy via Git and CI/CD tools rather than FTP. In non-development environments, plugin and theme editing via the admin panel is automatically disabled for added stability.
mu-plugins autoloader
Automatically loads must-use plugins from subdirectories — enabling cleaner organisation of essential plugins that must run on every request, without manual activation or scattered plugin files.
Bedrock vs Traditional WordPress
Bedrock leverages WordPress Core functionality and is compatible with most plugins — while adding structure and tooling that traditional WordPress lacks by default.
| Feature | Bedrock | Traditional WordPress |
|---|---|---|
| WordPress coding standards 1 | — Optional add-on | ✓ Default |
| Traditional WordPress structure 2 | — Not used | ✓ Default |
| Separate configs per environment | ✓ Dotenv (.env) | — Single wp-config.php |
| Environment variables | ✓ Built-in | — Not native |
| Custom wp-content directory | ✓ web/app/ | — Fixed location |
| Composer for WordPress installation | ✓ Full control | — Manual / FTP |
| Composer for plugins & themes | ✓ Versioned packages | — Dashboard only |
| mu-plugins autoloader | ✓ Built-in | — Manual |
| Separate public web root | ✓ web/ directory | — Root exposed |
| Secure password hashing | ✓ wp-password-bcrypt | — MD5 default |
1. WordPress coding standards are not enforced by default in Bedrock, but can be added if preferred. | 2. Bedrock leverages WordPress Core functionality and is compatible with most plugins.
Three pillars of the Bedrock stack
Bedrock improves on standard WordPress across three fundamental dimensions — dependency management, security, and configuration.
Composer manages everything
WordPress Core, plugins, and themes are declared in composer.json with pinned versions. No manual updates — everything is tracked and reproducible.
File structure enforces security
Only the web/ directory is the public web root. Config files and .env credentials live above it — inaccessible from the browser by design.
Dotenv per environment
Each environment reads from its own .env file. Database credentials and API keys never touch your Git repository — separate for local, staging, and production.
The next generation of WordPress hosting
Convesio's modern container-based architecture fully supports Bedrock's workflow — including Composer deployments, web root configuration, and environment variable management. More performance, scalability, security, and peace of mind.
Bedrock questions answered
Common questions from developers and agencies evaluating a Bedrock-based WordPress workflow.
Ask our teamReady to build on a modern WordPress stack?
Start your Bedrock-powered WordPress site on Convesio — with full Composer support, container isolation, and a team that understands modern WordPress development.
Learn more at thecloudszone.com · Recommended host: Convesio static sites ↗
