mirror of
https://github.com/gohugoio/hugo.git
synced 2025-08-21 21:35:28 +02:00
Merge commit 'd3927310d5b2404c3238f9b899db3329ea516490'
This commit is contained in:
@@ -29,7 +29,7 @@ example/
|
||||
├── public/
|
||||
├── static/
|
||||
├── themes/
|
||||
└── config.toml
|
||||
└── hugo.toml
|
||||
```
|
||||
|
||||
## Directory Structure Explained
|
||||
@@ -46,7 +46,7 @@ By default, Hugo will create new content files with at least `date`, `title` (in
|
||||
[`config`](/getting-started/configuration/)
|
||||
: 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.
|
||||
Projects with minimal settings and no need for environment awareness can use a single `hugo.toml` file at its root.
|
||||
|
||||
Many sites may need little to no configuration, but Hugo ships with a large number of [configuration directives] for more granular directions on how you want Hugo to build your website. Note: config directory is not created by default.
|
||||
|
||||
|
Reference in New Issue
Block a user