roots/bedrock

WordPress boilerplate with Composer and Git, easier configuration, and an improved folder structure

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 19 minutes ago
Added to GitGenius on September 10th, 2026
Created on November 2nd, 2013
Open Issues & Pull Requests: 6 (+0)
GitHub issues: Enabled
Number of forks: 1,167
Total Stargazers: 6,571 (+0)
Total Subscribers: 227 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Bedrock is a WordPress boilerplate that uses Composer for dependency management and Git for version control, offering easier configuration and an improved folder structure.

Bedrock solves the problem of managing WordPress projects with modern development practices. Traditional WordPress installations mix core files, plugins, and themes in a flat structure that makes version control and dependency management difficult. Bedrock reorganizes the project layout to separate concerns, allowing developers to manage WordPress core and plugins through Composer rather than manual downloads. This approach treats WordPress as a dependency like any other package, enabling reproducible builds and cleaner Git histories by excluding vendor directories.

Bedrock suits teams and developers who want to apply software engineering best practices to WordPress projects. It works well for projects where multiple developers collaborate, where deployment automation matters, or where you need consistent environments across development, staging, and production. The boilerplate is particularly valuable if your team already uses Composer and Git workflows in other projects, as it brings WordPress into that same ecosystem. The project draws inspiration from the Twelve-Factor App methodology, which emphasizes stateless processes and environment-based configuration, making it especially suitable for cloud deployments and containerized environments.

The project maintains active continuous integration testing. Development activity shows consistent engagement with the codebase through regular updates and maintenance of the build pipeline.