Configuration
Here’s how a Thulite project configuration is organized, and the configuration files you will find in your new project.
Example Project Configuration Tree
A common Thulite project configuration directory might look like this:
Directoryconfig
Directory_default
- hugo.toml
- markup.toml
- menus.toml
- module.toml
- params.toml
Directorynext
- hugo.toml
- params.toml
Directoryproduction
- hugo.toml
- params.toml
- babel.config.js
- postcss.config.js
config/_default/hugo.toml
The hugo.toml file includes Hugo configuration options for your Thulite project. Here you can specify taxonomies to use, build options, server options, and more.
config/_default/markup.toml
The markup.toml file is where you configure rendering of markup to HTML.
config/_default/menus.toml
The menus.toml file is where you define menu entries.
config/_default/module.toml
The module.toml file specifies the Hugo mounts, logically linking node_modules directories to component folders (ex: assets, layouts) — making Thulite Integrations available in your Thulite project.
config/_default/params.toml
The params.toml file is where you set Thulite configuration options like e.g. options for themes and integrations.
config/next/
Overrides for your next environment.
config/production/
Overrides for your production environment.
babel.config.js
The babel.config.js file is where you configure Babel. Thulite supports processing JavaScript files with Babel.
postcss.config.js
The postcss.config.js file is where you configure PostCSS. Thulite uses PostCSS to add vendor prefixes to CSS rules using Autoprefixer and to remove unused CSS from your project using PurgeCSS.
Hugo documentation
Thulite leverages Hugo’s configuration. Here are some relevant topics: