1798dc0d5 Update theme 403fa716e Update CLI documentation (#2092) aade5a09e Correct media subtype example 53cd9dea6 netlify: Hugo 0.112.3 b78b86cb1 Add source/target warning to resources.Copy (#2091) 50c299729 netlify: Hugo 0.112.2 73197046f Change config.xxx to hugo.xxx throughout the documentation (#2090) d489d4c6f Add hugo.WorkingDir to docs (#2089) 7487df809 Fix typos (#2088) 6d0572cd6 netlify: Hugo 0.112.1 6838600b2 netlify: Hugo 0.112.0 513e7a80f Merge branch 'tempv0.112.0' 91eb44275 Some more about 0.112.0 bd3b33a27 docs: Regen docshelper fb3027daf docs: Regen CLI docs 8e7b8e987 Merge commit 'f96384a3b596f9bc0a3a035970b09b2c601f0ccb' a942ceef4 tpl/tplimpl: Add img loading attribute to figure shortcode (#10927) 0e0c7b25e tpl/urls: Return empty string when JoinPath has zero args 310ce949a tpl/urls: Add JoinPath template function ae435ca77 tpl: Add math.Abs f340139f8 Revert "Update syntax-highlighting.md (#10929)" (#10930) 917a0e24d Update syntax-highlighting.md (#10929) git-subtree-dir: docs git-subtree-split: 1798dc0d54ce048dd975863b490cd809ef14268a
2.3 KiB
title | description | categories | keywords | menu | weight | aliases | toc | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Theme Components | Hugo provides advanced theming support with Theme Components. |
|
|
|
50 |
|
true |
{{% note %}}
This section contain information that may be outdated and is in the process of being rewritten.
{{% /note %}}
Since Hugo 0.42
a project can configure a theme as a composite of as many theme components you need:
{{< code-toggle file="hugo" >}} theme = ["my-shortcodes", "base-theme", "hyde"] {{< /code-toggle >}}
You can even nest this, and have the theme component itself include theme components in its own hugo.toml
(theme inheritance).1
The theme definition example above in hugo.toml
creates a theme with 3 theme components with precedence from left to right.
For any given file, data entry, etc., Hugo will look first in the project and then in my-shortcodes
, base-theme
, and lastly hyde
.
Hugo uses two different algorithms to merge the filesystems, depending on the file type:
- For
i18n
anddata
files, Hugo merges deeply using the translation ID and data key inside the files. - For
static
,layouts
(templates), andarchetypes
files, these are merged on file level. So the left-most file will be chosen.
The name used in the theme
definition above must match a folder in /your-site/themes
, e.g. /your-site/themes/my-shortcodes
. There are plans to improve on this and get a URL scheme so this can be resolved automatically.
Also note that a component that is part of a theme can have its own configuration file, e.g. hugo.toml
. There are currently some restrictions to what a theme component can configure:
params
(global and per language)menu
(global and per language)outputformats
andmediatypes
The same rules apply here: The left-most param/menu etc. with the same ID will win. There are some hidden and experimental namespace support in the above, which we will work to improve in the future, but theme authors are encouraged to create their own namespaces to avoid naming conflicts.
-
For themes hosted on the Hugo Themes Showcase components need to be added as git submodules that point to the directory
exampleSite/themes
↩︎