Bedrock v2

Open
#764 17 comments 34 reactions 1 assignee View on GitHub

@retlehs is already working on this.

Since Feb 20, 2025.

Assessment

This issue has not been assessed yet.

Description

enhancement

Bedrock will be getting a major version update 💥 We'll be making changes to the directory structure and configuration system to better align with modern PHP practices.

These directory changes mean we'll need to update Trellis to accommodate the new structure. It will also mean we'll need to update any other tools that interact with Bedrock sites, such as Valet/Herd drivers, deployment scripts, docs/tutorials, etc.

Directory structure
  • Rename web/ directory to public/ to better align with modern PHP practices
  • Make the app/ directory (wp-content) the public web root 🔨
Configuration

Bedrock v1:

├── composer.json
├── config/
│   ├── application.php     # Primary wp-config
│   └── environments
│       ├── development.php
│       ├── staging.php
│       └── production.php
├── vendor/                 # Composer dependencies
└── web/                    # Public document root
    ├── app/                # WordPress content dir
    │   ├── mu-plugins/
    │   ├── plugins/
    │   ├── themes/
    │   └── uploads/
    ├── index.php
    ├── wp-config.php
    └── wp/                 # WordPress core

Bedrock v2:

├── config.php              # Primary wp-config
├── composer.json
├── vendor/                 # Composer dependencies
└── public/                 # Public document root (renamed from web/)
    ├── index.php
    ├── wp-config.php       # Required wp-config.php from WordPress, loads our wp-config.php from the project root
    ├── mu-plugins/
    ├── plugins/
    ├── themes/
    ├── uploads/
    └── wp/                 # WordPress core
Dominant language
PHP
Stars
6.6k
Forks
1.2k
Avg merge
2h 15m
Merged PRs (30d)
1

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from roots/bedrock

All issues in roots/bedrock

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.