A Composer-based WordPress boilerplate with environment-file config, WP Packages plugin management, Vite and Tailwind CSS.
roots/bedrock
A WordPress boilerplate that uses Composer and Git to manage core, plugins and themes, with environment-based configuration and a cleaner folder layout.
- Stars
- 6,585
- Forks
- 1,172
- Open issues
- 6
- Last commit
- 5 days ago
What is it?
Bedrock is a WordPress project boilerplate for developers who want to manage a site the way they manage other applications: with Git for version control and Composer for dependencies. WordPress core is installed as a Composer package (roots/wordpress), and plugins and themes can be pulled from the WP Packages repository, so the codebase no longer needs to commit WordPress files directly.
The project reorganizes the usual WordPress layout into a clearer structure, moving the web root into a dedicated directory and separating application code from core. Configuration is handled through environment-specific files and environment variables loaded with Dotenv, so secrets and per-environment settings stay out of the repository. It also includes an autoloader for mu-plugins, letting regular plugins be loaded as must-use plugins.
The design follows the Twelve-Factor App methodology adapted for WordPress.
Key features
- 01Installs WordPress core via Composer using the roots/wordpress package
- 02Pulls plugins and themes from the WP Packages repository
- 03Environment-specific configuration files and Dotenv-based environment variables
- 04Reorganized folder structure that separates the web root from application code
- 05Autoloader for loading regular plugins as mu-plugins
Use cases
- Starting a new WordPress site that should be version-controlled and deployed through Git
- Managing WordPress plugins and themes as Composer dependencies across several environments
- Keeping database credentials and API keys out of the codebase
Quick start
- 1
Read the Bedrock installation documentation linked in the README
Topics
FAQ
- What is bedrock?
- A WordPress boilerplate that uses Composer and Git to manage core, plugins and themes, with environment-based configuration and a cleaner folder layout. Bedrock is a WordPress project boilerplate for developers who want to manage a site the way they manage other applications: with Git for version control and Composer for dependencies. WordPress core is installed as a Composer package (roots/wordpress), and plugins and themes can be pulled from the WP Packages repository, so the codebase no longer needs to commit WordPress files directly.
- Is bedrock free to use? What license does it have?
- bedrock is open source under the MIT license. Check the license terms before using it in commercial products.
- Is bedrock still maintained?
- Actively maintained. The last commit to bedrock was on Nov 1, 2026.
- What can I use bedrock for?
- Starting a new WordPress site that should be version-controlled and deployed through Git Managing WordPress plugins and themes as Composer dependencies across several environments Keeping database credentials and API keys out of the codebase
- How do I install bedrock?
- Read the Bedrock installation documentation linked in the README
- Where can I get bedrock?
- The source code and installation instructions are on GitHub: https://github.com/roots/bedrock
Summary generated by AI from the project's README. GitHub stats refresh daily.
Related projects
A GraphQL API plugin for WordPress that exposes posts, pages, users, taxonomies and custom content types as a queryable schema.
A Git mirror of WordPress core's Subversion repository, with branches and tags, for contributing patches and running the local dev environment.
A community-maintained WordPress plugin that adds multilingual content to posts and pages, stored together in a single post.
A PHP library that lets WordPress themes be built with the Twig template engine, separating PHP logic from HTML markup.
The official WordPress client for Android, letting users manage self-hosted WordPress sites and WordPress.com accounts from a phone.