# Build process
When you run `maizzle build`, your Templates go through a series of events that compile them to plain HTML and apply various, email-specific transformations.
To get a better understanding of how Maizzle builds your emails, here's a step-by-step guide of what's going on under the hood.
## Environment config
First, a global configuration object is computed by merging your Environment config on top of the base `config.js`.
For example, running `maizzle build production` will tell Maizzle to look for the `config.production.js` file at your current location, and merge it on top of `config.js`.
When running `maizzle build` or `maizzle serve`, only the base `config.js` will be used.
## beforeCreate()
The [beforeCreate](/docs/events#beforecreate) event (CLI-only) is triggered, giving you access to the config before Maizzle loops over your Templates to compile them.
## Clean destination
The destination directories that you have defined under `build.output.path` in your environment config are deleted.
Be careful when customizing this path, so you don't end up deleting important directories and files on your machine.
## Compile templates
Each Template file is parsed and compiled:
1. Maizzle reads the Template file
2. It extracts its Front Matter
3. A unique Template `config` is computed by merging the Template's Front Matter keys with the Environment `config`
4. [beforeRender()](/docs/events#beforerender) event is triggered
5. The HTML is rendered with PostHTML
Your Environment name and all `config` options (including any you defined in Front Matter) are exposed under the `page` object, which you can access through [expressions](/docs/expressions).
PostHTML plugins that are used as part of the rendering process:
- envTags - core plugin that enables [``](/docs/tags#env) tags
- envAttributes - core plugin that enables attributes like `src-{env}`
- expandLinkTags - core plugin that expands local [`` tags](/docs/layouts#link-tag) into `