Themes

Use a theme, override its templates and assets, and how a theme's configuration merges with yours.

A theme is a project whose layouts, assets, content, data and i18n files are used under yours.

theme = "my-theme"

theme: my-theme

{
   "theme": "my-theme"
}

fugo looks for themes/my-theme (or themesDir). theme may be a list: the first wins where themes provide the same file. A theme can import other themes with [[module.imports]].

Themes for fugo are written in Tera, with the current layout names; a theme written in Go templates must be converted first (see Migrating from Go templates).

Overriding a theme#

Any file of yours with the same path wins: layouts/_partials/footer.html replaces the theme’s footer, assets/css/theme.css its stylesheet, i18n/en.toml keys add to or replace its strings. A theme’s more specific template still beats your general one: the theme’s layouts/posts/single.html wins over your layouts/single.html for posts.

Configuration#

A theme’s configuration file (one config.toml, as in a project) is merged below yours: your values always win, and the theme adds what you do not set. The theme’s [environments.<name>] table of the build’s environment is merged over its own settings first.

Root values (title, baseURL) never come from a theme. Write _merge = "deep", "shallow" or "none" in a table to change what it takes; _merge = "none" at the root ignores theme configuration altogether.