mirror/gohugoio-hugo
1
0
Fork 0
mirror of https://github.com/gohugoio/hugo.git synced 2024-05-11 05:54:58 +00:00
Code Issues Releases Activity

Merge commit '3902f9a4767fe6e62ac5146728d8311b8cd227e0'

Browse Source
This commit is contained in:
Bjørn Erik Pedersen
2022-04-28 11:52:15 +02:00
parent fa80fe3c8a 3902f9a476
commit 4852a37653
33 changed files with 98 additions and 245 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/content/en/getting-started/directory-structure.md
View File

@@ -48,7 +48,7 @@ By default, Hugo will create new content files with at least `date`, `title` (in
: Stores all the files which need be processed by [Hugo Pipes]({{< ref "/hugo-pipes" >}}). Only the files whose `.Permalink` or `.RelPermalink` are used will be published to the `public` directory. Note: assets directory is not created by default.
[`config`](/getting-started/configuration/)
: Hugo ships with a large number of [configuration directives](https://gohugo.io/getting-started/configuration/#all-variables-yaml).
: Hugo ships with a large number of [configuration directives][].
The [config directory](/getting-started/configuration/#configuration-directory) is where those directives are stored as JSON, YAML, or TOML files. Every root setting object can stand as its own file and structured by environments.
Projects with minimal settings and no need for environment awareness can use a single `config.toml` file at its root.
@@ -76,7 +76,7 @@ resources
[archetypes]: /content-management/archetypes/
[configuration directives]: /getting-started/configuration/#all-variables-yaml
[configuration directives]: /getting-started/configuration/#all-configuration-settings
[`content`]: /content-management/organization/
[content section]: /content-management/sections/
[content types]: /content-management/types/