Skip to content

Latest commit

 

History

History
42 lines (40 loc) · 1.58 KB

folder-structure.md

File metadata and controls

42 lines (40 loc) · 1.58 KB
ID post_title author post_date post_excerpt layout permalink published docs_project publish_to_discourse
6142
Folder Structure
Ben Word
2015-09-03 10:17:56 -0700
doc
true
a:1:{i:0;s:2:"18";}
a:1:{i:0;s:1:"0";}
├── composer.json
├── config
│   ├── application.php
│   └── environments
│       ├── development.php
│       ├── staging.php
│       └── production.php
├── vendor
└── web
    ├── app
    │   ├── mu-plugins
    │   ├── plugins
    │   ├── themes
    │   └── uploads
    ├── wp-config.php
    ├── index.php
    └── wp

The organization of Bedrock is similar to putting WordPress in its own subdirectory but with some improvements.

  • In order not to expose sensitive files in the webroot, Bedrock moves what's required into a web/ directory including the vendor'd wp/ source, and the wp-content source.
  • wp-content has been named app to better reflect its contents. It contains application code and not just "static content". It also matches up with other frameworks such as Symfony and Rails.
  • wp-config.php remains in the web/ because it's required by WP, but it only acts as a loader. The actual configuration files have been moved to config/ for better separation.
  • vendor/ is where the Composer managed dependencies are installed to.
  • wp/ is where the WordPress core lives. It's also managed by Composer but can't be put under vendor due to WP limitations.