Statiq is highly configurable and everything from pipelines and modules to metadata (known as settings when used globally) can be easily customized to your needs.
The bootstrapper is the easiest way to configure an engine, add pipelines and modules to it, and process command-line arguments.
Most modules that require configuration use a special
Config<TValue> delegate. This type allows you to specify lazy logic that's evaluated at execution time and optionally uses the document and/or execution context, is async or not, or just converts from a simple value.
Statiq has a few different options for how files in the output path are deleted on each engine execution.
Settings let you define global metadata that can be accessed from the execution context or documents.
Sometimes it's desirable to have more control over the current date/time and to use an alternate date/time for the execution (for example, if you want to see what will happen during generation on a future date).
Web Settings W D
In addition to the settings available from Statiq Framework, Statiq Web also has a number of settings that can be used to control behavior. Global settings that apply to the generation process and all documents are generally defined in a configuration file. Most settings are also appropriate to define at the directory level or per-document if you only want them to apply to specific files.