Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve config merge section #2186

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions content/en/getting-started/configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -97,9 +97,9 @@ This is how you need to configure your `hugo.toml` files considering the above s
Default environments are __development__ with `hugo server` and __production__ with `hugo`.
{{%/ note %}}

## Merge configuration from themes
## Configuration merge strategy

The configuration value for `_merge` can be one of:
Configuration from [themes](/hugo-modules/theme-components/) as well as [language-specific configuration](/content-management/multilingual/#configure-languages) is merged with the main [site configuration](#configuration-file) according to the respective `_merge` strategy, which can be one of:

none
: No merge.
Expand All @@ -110,7 +110,7 @@ shallow
deep
: Add values for new keys, merge existing.

Note that you don't need to be so verbose as in the default setup below; a `_merge` value higher up will be inherited if not set.
The default values of `_merge` for the different configuration objects are as follows. Note that you don't need to be so verbose, a `_merge` value higher up will be inherited if not set.

{{< code-toggle file="hugo" dataKey="config_helpers.mergeStrategy" skipHeader=true />}}

Expand Down