After installing Aztlan, you now have a skeleton to work from for your specific theme.
As shown after you installed Aztlan, the install script created a directory structure similar to:
. ├── assets │ ├── fonts │ ├── js │ ├── stylus ├── cli ├── deploy ├── environment │ ├── bin │ ├── docker │ ├── env │ ├── extra │ │ └── uploads │ ├── initdb ├── inc │ ├── languages │ └── src ├── phpqa ├── public │ ├── wp │ ├── packages ├── themes │ └── env-theme └── wp-packages ├── languages │ ├── plugins │ └── themes ├── mu-plugins └── private ├── plugins └── themes
All the assets are bundle by Webpack.
fonts: the directory contains the web fonts;
js: the directory contains ES6 modules, transpilled by Babel;
stylus: the directory contains Stylus files, all modules must be included on
cli directory contains classes to extends WP CLI commands.
deploy directory contains all necessary files to Deployer.
environment directory contains all necessary files to build up the Docker containers.
bin: the directory contains environment routine scripts;
docker: the directory contains all Dockerfiles;
env: the directory contains all environment variables;
extra/uploads: the directory contains all required uploads files for the theme to work;
initdb: the directory can contain a MySQL dump to be use as initial database;
inc directory contains all theme classes.
src: the directory contains all theme classes;
languages: the directory contains translations for classes;
Tools to analyze PHP code.
public directory contains the WordPress installation.
wp: the WordPress core.
themes directory contains all availables themes.
wp-packages directory contains all themes and plugins installed via WordPress Packagist.
languages: the directory contains translations for 3rd party themes and plugins;
mu-plugins: the directory contains must-use plugins;
private: the directory contains the plugins and themes ZIP files, they are activated on installation.