An outline of ProcessWire’s file and directory structure, highlighting the locations where your site’s files go, where the core files live, where to place modules, and more.
ProcessWire follows a simple directory structure which aims to do the following:
Keep your site's files and assets completely separate from ProcessWire's, so that you can upgrade your site simply by replacing ProcessWire's core.
Minimizes the impact to your root installation directory, so that everything is clean and doesn't create confusion with other applications you may have installed.
ProcessWire may be installed anywhere on your web server. While it's most common to install it in your web root (/) the software will run just as well under any directory structure.
ProcessWire only creates two directories from your root. This includes /wire and /site. The /wire directory contains the ProcessWire installation and modules, while the /site directory contains everything unique to a given site, including templates, your configuration, stylesheets, scripts, cache files and other assets. This structure is outlined in more detail below.
Root installation directory (/)
|Required directives to Apache
|Bootstrap index file
|Installation script (you should delete this after installation)
Core and modules (/wire/)
|Default plugin modules
|Templates, stylesheets and scripts for the admin control panel
All files unique to a given site (/site/)
|Your site's configuration file
|All writable assets including files, images, cache files, logs and temporary files created by ProcessWire.
|Installation profile. You should delete this directory after installation.
|Any plugin modules unique to a given site (optional).
|Template files specific to your site
|CSS files specific to your site. You may locate this directory elsewhere, and/or rename it, if you prefer.