# Folder Structure
# Overview
(theme root)
├─ acf-json
├─ dist
├─ functions
│ ├─ cpt
│ └─ lib
├─ languages
├─ node_modules
├─ src
│ ├─ fonts
│ ├─ img
│ ├─ js
│ └─ sass
├─ templates
└─ vendor
# Folder Details
# acf-json
Support for Advanced Custom Fields local JSON (opens new window). You can delete this directory if you don't use this feature (more details on ACF page).
# dist
Compiled resources coming from src
and built by Gulp, directly loaded into the theme.
WARNING
The contents of this folder are automatically updated and overwritten by compiling tasks. You should not manually edit anything here.
# functions
Modularization of functions.php
WordPress file (more details on Functions page).
# functions/cpt
Custom Post Types (opens new window) and Custom Taxonomies (opens new window) definitions.
Two *.php.sample
files are already present. You can rename them to *.php
and start customizing them to your needs (Any *.php
file present in this folder will be automatically loaded in to the theme)
# functions/lib
Third-party php resources. WP Bootstrap Navwalker (opens new window) is already present, you can add here more php libraries you might need to include.
# node_modules
NPM dependencies. Automatically created during installation, it should not be modified manually.
# languages
Translations support. The source template.pot
template file is located here, you should put here also actual *.po
and *.mo
translation files (more details on Localization page).
# src
Uncompiled resource files, ready to be edited and customized. They will be compiled to dist
by Gulp.
# src/fonts
Source custom font files (otf/ttf fonts will be converted into woff2 web format, while woff/woff2 fonts will be simply copied).
# src/img
Source images (will be optimized with imagemin).
# src/js
Source JavaScript files (will be bundled by Rollup).
# src/sass
Source Sass files (will be optimized by PurgeCSS and Autoprefixer).
# templates
Template files partials, to be called with get_template_part()
. Bricks templates are modularized and split into partial files, in order to keep an ordered structure and provide a component-like development experience.
TIP
You are encouraged to take advantage of get_template_part() (opens new window) and modularize your own custom templates as well, to keep your code clean, simple and easily maintainable.
# vendor
Composer dependencies. Automatically created during installation, it should not be modified manually.