Configuration
Configure a fugo site — the configuration file and directory, environments, the .env file, and every section of settings.
A site’s settings live in config.toml (or config.yaml, config.yml, config.json) at the project root, or in a config/ directory. Its keys are those of Go-template sites, whose settings mostly carry over; see Introduction for how they are loaded.
| Settings | Where they are described |
|---|---|
baseURL, title, params, directories, URLs, kinds | Site settings |
[languages] | Multilingual sites |
[taxonomies] | Taxonomies |
[menus] | Menus |
[permalinks] | URLs |
[markup] | Markdown, Syntax highlighting, Table of contents |
[outputs], [outputFormats], [mediaTypes] | Output formats |
[pagination] | Pagination |
[sitemap] | Sitemaps |
[related] | Related content |
[frontmatter], [cascade] | Front matter |
[imaging] | Imaging |
[caches] | Caching |
[module], theme | Modules and mounts, Themes |
[privacy], [services] | Privacy and services |
[security] | Security |
[build], [minify] | Build and minify |
[cms] | CMS editor, Editing in the browser |
[fonts] | Font subsetting |
[server] | Development server |
fugo config prints the configuration as fugo resolved it, defaults included.
- Introduction How fugo reads its configuration — one file, its environments and command-line flags — and the .env file for secrets.
- Site settings The root settings of a fugo site — base URL, title, parameters, directories, URLs, page kinds, titles, summaries and the table of contents.
- Front matter Configure where page dates come from, and set front matter for many pages at once with cascade.
- Imaging Default quality, resampling filter, anchor, background colour and EXIF handling for image processing, and the metadata of published images.
- Caching The file caches fugo keeps between builds — processed images, assets and remote resources — and how to configure or clear them.
- Modules and mounts Mount directories into fugo's file system, share content, layouts and assets between projects, and import themes as modules.
- Themes Use a theme, override its templates and assets, and how a theme's configuration merges with yours.
- Privacy and services Configure the embedded shortcodes and partials that talk to Google Analytics, YouTube, Vimeo, Instagram and X, for privacy.
- Security Control which programs fugo runs, which environment variables templates may read and which URLs get_remote may fetch.
- CMS editor The settings of the browser editor (`[cms]`) — its path and workflow, the git repository, the sign-in, roles, field hints — and the Worker's secrets.
- Build and minify The build table, and HTML, CSS and JavaScript minification.
- Development server The settings of fugo server — proxies that send the requests of a path, such as your site's API, to another server while you develop, on this computer or published.