1--- 2title: Configure Hugo 3linktitle: Configuration 4description: How to configure your Hugo site. 5date: 2013-07-01 6publishdate: 2017-01-02 7lastmod: 2017-03-05 8categories: [getting started,fundamentals] 9keywords: [configuration,toml,yaml,json] 10menu: 11 docs: 12 parent: "getting-started" 13 weight: 60 14weight: 60 15sections_weight: 60 16draft: false 17aliases: [/overview/source-directory/,/overview/configuration/] 18toc: true 19--- 20 21 22## Configuration File 23 24Hugo uses the `config.toml`, `config.yaml`, or `config.json` (if found in the 25site root) as the default site config file. 26 27The user can choose to override that default with one or more site config files 28using the command line `--config` switch. 29 30Examples: 31 32``` 33hugo --config debugconfig.toml 34hugo --config a.toml,b.toml,c.toml 35``` 36 37{{% note %}} 38Multiple site config files can be specified as a comma-separated string to the `--config` switch. 39{{% /note %}} 40 41{{< todo >}}TODO: distinct config.toml and others (the root object files){{< /todo >}} 42 43## Configuration Directory 44 45In addition to using a single site config file, one can use the `configDir` directory (default to `config/`) to maintain easier organization and environment specific settings. 46 47- Each file represents a configuration root object, such as `params.toml` for `[Params]`, `menu(s).toml` for `[Menu]`, `languages.toml` for `[Languages]` etc... 48- Each file's content must be top-level, for example: 49 50{{< code-toggle file="config" >}} 51[Params] 52 foo = "bar" 53{{< /code-toggle >}} 54 55{{< code-toggle file="params" >}} 56foo = "bar" 57{{< /code-toggle >}} 58 59- Each directory holds a group of files containing settings unique to an environment. 60- Files can be localized to become language specific. 61 62 63``` 64├── config 65│ ├── _default 66│ │ ├── config.toml 67│ │ ├── languages.toml 68│ │ ├── menus.en.toml 69│ │ ├── menus.zh.toml 70│ │ └── params.toml 71│ ├── production 72│ │ ├── config.toml 73│ │ └── params.toml 74│ └── staging 75│ ├── config.toml 76│ └── params.toml 77``` 78 79Considering the structure above, when running `hugo --environment staging`, Hugo will use every settings from `config/_default` and merge `staging`'s on top of those. 80{{% note %}} 81Default environments are __development__ with `hugo server` and __production__ with `hugo`. 82{{%/ note %}} 83 84## Merge Configuration from Themes 85 86{{< new-in "0.84.0" >}} The configuration merge described below was improved in Hugo 0.84.0 and made fully configurable. The big change/improvement was that we now, by default, do deep merging of `params` maps from themes. 87 88The configuration value for `_merge` can be one of: 89 90none 91: No merge. 92 93shallow 94: Only add values for new keys. 95 96deep 97: Add values for new keys, merge existing. 98 99Note 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. 100 101{{< code-toggle config="mergeStrategy" skipHeader=true />}} 102 103## All Configuration Settings 104 105The following is the full list of Hugo-defined variables with their default 106value in parentheses. Users may choose to override those values in their site 107config file(s). 108 109### archetypeDir 110 111**Default value:** "archetypes" 112 113The directory where Hugo finds archetype files (content templates). {{% module-mounts-note %}} 114 115### assetDir 116 117**Default value:** "assets" 118 119The directory where Hugo finds asset files used in [Hugo Pipes](/hugo-pipes/). {{% module-mounts-note %}} 120 121### baseURL 122Hostname (and path) to the root, e.g. https://bep.is/ 123 124### blackfriday 125See [Configure Blackfriday](/getting-started/configuration-markup#blackfriday) 126 127### build 128See [Configure Build](#configure-build) 129 130### buildDrafts (false) 131 132**Default value:** false 133 134Include drafts when building. 135 136### buildExpired 137 138**Default value:** false 139 140Include content already expired. 141 142### buildFuture 143 144**Default value:** false 145 146Include content with publishdate in the future. 147 148### caches 149See [Configure File Caches](#configure-file-caches) 150 151### cascade 152 153{{< new-in "0.86.0" >}} 154 155Pass down down default configuration values (front matter) to pages in the content tree. The options in site config is the same as in page front matter, see [Front Matter Cascade](/content-management/front-matter#front-matter-cascade). 156 157### canonifyURLs 158 159**Default value:** false 160 161Enable to turn relative URLs into absolute. 162 163### contentDir 164 165**Default value:** "content" 166 167The directory from where Hugo reads content files. {{% module-mounts-note %}} 168 169### copyright 170 171**Default value:** "" 172 173Copyright notice for your site, typically displayed in the footer. 174 175### dataDir 176 177**Default value:** "data" 178 179The directory from where Hugo reads data files. {{% module-mounts-note %}} 180 181### defaultContentLanguage 182 183**Default value:** "en" 184 185Content without language indicator will default to this language. 186 187### defaultContentLanguageInSubdir 188 189**Default value:** false 190 191Render the default content language in subdir, e.g. `content/en/`. The site root `/` will then redirect to `/en/`. 192 193### disableAliases 194 195**Default value:** false 196 197Will disable generation of alias redirects. Note that even if `disableAliases` is set, the aliases themselves are preserved on the page. The motivation with this is to be able to generate 301 redirects in an `.htaccess`, a Netlify `_redirects` file or similar using a custom output format. 198 199### disableHugoGeneratorInject 200 201**Default value:** false 202 203Hugo will, by default, inject a generator meta tag in the HTML head on the _home page only_. You can turn it off, but we would really appreciate if you don't, as this is a good way to watch Hugo's popularity on the rise. 204 205### disableKinds 206 207**Default value:** [] 208 209Enable disabling of all pages of the specified *Kinds*. Allowed values in this list: `"page"`, `"home"`, `"section"`, `"taxonomy"`, `"term"`, `"RSS"`, `"sitemap"`, `"robotsTXT"`, `"404"`. 210 211### disableLiveReload 212 213**Default value:** false 214 215Disable automatic live reloading of browser window. 216 217### disablePathToLower 218 219**Default value:** false 220 221: Do not convert the url/path to lowercase. 222 223### enableEmoji 224 225**Default value:** false 226 227Enable Emoji emoticons support for page content; see the [Emoji Cheat Sheet](https://www.webpagefx.com/tools/emoji-cheat-sheet/). 228 229### enableGitInfo 230 231**Default value:** false 232 233Enable `.GitInfo` object for each page (if the Hugo site is versioned by Git). This will then update the `Lastmod` parameter for each page using the last git commit date for that content file. 234 235### enableInlineShortcodes 236 237**Default value:** false 238 239Enable inline shortcode support. See [Inline Shortcodes](/templates/shortcode-templates/#inline-shortcodes). 240 241### enableMissingTranslationPlaceholders 242 243**Default value:** false 244 245Show a placeholder instead of the default value or an empty string if a translation is missing. 246 247### enableRobotsTXT 248 249**Default value:** false 250 251Enable generation of `robots.txt` file. 252 253### frontmatter 254 255See [Front matter Configuration](#configure-front-matter). 256 257### footnoteAnchorPrefix 258 259**Default value:** "" 260 261Prefix for footnote anchors. 262 263### footnoteReturnLinkContents 264 265**Default value:** "" 266 267Text to display for footnote return links. 268 269### googleAnalytics 270 271**Default value:** "" 272 273Google Analytics tracking ID. 274 275### hasCJKLanguage 276 277**Default value:** false 278 279If true, auto-detect Chinese/Japanese/Korean Languages in the content. This will make `.Summary` and `.WordCount` behave correctly for CJK languages. 280 281### imaging 282See [Image Processing Config](/content-management/image-processing/#image-processing-config). 283 284### languageCode 285 286**Default value:** "" 287 288A language tag as defined by [RFC 5646](https://datatracker.ietf.org/doc/html/rfc5646). The internal [RSS template](https://github.com/gohugoio/hugo/blob/master/tpl/tplimpl/embedded/templates/_default/rss.xml) populates its `<language>` element with this value. The value is not used elsewhere. 289 290### languages 291See [Configure Languages](/content-management/multilingual/#configure-languages). 292 293### disableLanguages 294 295See [Disable a Language](/content-management/multilingual/#disable-a-language) 296 297### markup 298See [Configure Markup](/getting-started/configuration-markup).{{< new-in "0.60.0" >}} 299 300### mediaTypes 301See [Configure Media Types](/templates/output-formats/#media-types). 302 303### menus 304See [Add Non-content Entries to a Menu](/content-management/menus/#add-non-content-entries-to-a-menu). 305 306### minify 307See [Configure Minify](#configure-minify) 308 309### module 310Module config see [Module Config](/hugo-modules/configuration/).{{< new-in "0.56.0" >}} 311 312### newContentEditor 313The editor to use when creating new content. 314 315### noChmod 316Don't sync permission mode of files. 317 318### noTimes 319Don't sync modification time of files. 320 321### outputFormats 322See [Configure Output Formats](#configure-additional-output-formats). 323 324### paginate 325 326**Default value:** 10 327 328Default number of elements per page in [pagination](/templates/pagination/). 329 330### paginatePath 331 332**Default value:** "page" 333 334The path element used during pagination (`https://example.com/page/2`). 335 336### permalinks 337See [Content Management](/content-management/urls/#permalinks). 338 339### pluralizeListTitles 340 341**Default value:** true 342 343Pluralize titles in lists. 344 345### publishDir 346 347**Default value:** "public" 348 349The directory to where Hugo will write the final static site (the HTML files etc.). 350 351### related 352: See [Related Content](/content-management/related/#configure-related-content).{{< new-in "0.27" >}} 353 354### relativeURLs 355Enable this to make all relative URLs relative to content root. Note that this does not affect absolute URLs. 356 357### refLinksErrorLevel 358 359**Default value:** "ERROR" 360 361When using `ref` or `relref` to resolve page links and a link cannot resolved, it will be logged with this log level. Valid values are `ERROR` (default) or `WARNING`. Any `ERROR` will fail the build (`exit -1`). 362 363### refLinksNotFoundURL 364URL to be used as a placeholder when a page reference cannot be found in `ref` or `relref`. Is used as-is. 365 366### removePathAccents 367 368**Default value:** false 369 370Removes [non-spacing marks](https://www.compart.com/en/unicode/category/Mn) from [composite characters](https://en.wikipedia.org/wiki/Precomposed_character) in content paths. 371 372```text 373content/post/hügó.md --> https://example.org/post/hugo/ 374``` 375 376 377### rssLimit 378 379Maximum number of items in the RSS feed. 380 381### sectionPagesMenu 382See ["Section Menu for Lazy Bloggers"](/templates/menu-templates/#section-menu-for-lazy-bloggers). 383 384### security 385 386See [Security Policy](/about/security-model/#security-policy) 387 388### sitemap 389Default [sitemap configuration](/templates/sitemap-template/#configure-sitemapxml). 390 391### summaryLength 392 393**Default value:** 70 394 395The length of text in words to show in a [`.Summary`](/content-management/summaries/#hugo-defined-automatic-summary-splitting). 396 397### taxonomies 398See [Configure Taxonomies](/content-management/taxonomies#configure-taxonomies). 399 400### theme 401: See [Module Config](/hugo-modules/configuration/#module-config-imports) for how to import a theme. 402 403### themesDir 404 405**Default value:** "themes" 406 407The directory where Hugo reads the themes from. 408 409### timeout 410 411**Default value:** "30s" 412 413Timeout for generating page contents, specified as a [duration](https://pkg.go.dev/time#Duration) or in milliseconds. *Note:* this is used to bail out of recursive content generation. You might need to raise this limit if your pages are slow to generate (e.g., because they require large image processing or depend on remote contents). 414 415### timeZone 416 417{{< new-in "0.87.0" >}} 418 419The time zone (or location), e.g. `Europe/Oslo`, used to parse front matter dates without such information and in the [`time` function](/functions/time/). The list of valid values may be system dependent, but should include `UTC`, `Local`, and any location in the [IANA Time Zone database](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). 420 421### title 422Site title. 423 424### titleCaseStyle 425 426**Default value:** "AP" 427 428See [Configure Title Case](#configure-title-case) 429 430### uglyURLs 431When enabled, creates URL of the form `/filename.html` instead of `/filename/`. 432 433### watch 434 435Watch filesystem for changes and recreate as needed. 436 437{{% note %}} 438If you are developing your site on a \*nix machine, here is a handy shortcut for finding a configuration option from the command line: 439``` 440cd ~/sites/yourhugosite 441hugo config | grep emoji 442``` 443 444which shows output like 445 446``` 447enableemoji: true 448``` 449{{% /note %}} 450 451## Configure Build 452 453{{< new-in "0.66.0" >}} 454 455The `build` configuration section contains global build-related configuration options. 456 457{{< code-toggle file="config">}} 458[build] 459useResourceCacheWhen="fallback" 460writeStats = false 461noJSConfigInAssets = false 462{{< /code-toggle >}} 463 464 465useResourceCacheWhen 466: When to use the cached resources in `/resources/_gen` for PostCSS and ToCSS. Valid values are `never`, `always` and `fallback`. The last value means that the cache will be tried if PostCSS/extended version is not available. 467 468writeStats {{< new-in "0.69.0" >}} 469: When enabled, a file named `hugo_stats.json` will be written to your project root with some aggregated data about the build, e.g. list of HTML entities published to be used to do [CSS pruning](/hugo-pipes/postprocess/#css-purging-with-postcss). If you're only using this for the production build, you should consider placing it below [config/production](/getting-started/configuration/#configuration-directory). It's also worth mentioning that, due to the nature of the partial server builds, new HTML entities will be added when you add or change them while the server is running, but the old values will not be removed until you restart the server or run a regular `hugo` build. 470 471**Note** that the prime use case for this is purging of unused CSS; it is build for speed and there may be false positives (e.g. elements that isn't really a HTML element). 472 473noJSConfigInAssets {{< new-in "0.78.0" >}} 474: Turn off writing a `jsconfig.json` into your `/assets` folder with mapping of imports from running [js.Build](https://gohugo.io/hugo-pipes/js). This file is intended to help with intellisense/navigation inside code editors such as [VS Code](https://code.visualstudio.com/). Note that if you do not use `js.Build`, no file will be written. 475 476## Configure Server 477 478{{< new-in "0.67.0" >}} 479 480This is only relevant when running `hugo server`, and it allows to set HTTP headers during development, which allows you to test out your Content Security Policy and similar. The configuration format matches [Netlify's](https://docs.netlify.com/routing/headers/#syntax-for-the-netlify-configuration-file) with slightly more powerful [Glob matching](https://github.com/gobwas/glob): 481 482 483{{< code-toggle file="config">}} 484[server] 485[[server.headers]] 486for = "/**" 487 488[server.headers.values] 489X-Frame-Options = "DENY" 490X-XSS-Protection = "1; mode=block" 491X-Content-Type-Options = "nosniff" 492Referrer-Policy = "strict-origin-when-cross-origin" 493Content-Security-Policy = "script-src localhost:1313" 494{{< /code-toggle >}} 495 496Since this is is "development only", it may make sense to put it below the `development` environment: 497 498 499{{< code-toggle file="config/development/server">}} 500[[headers]] 501for = "/**" 502 503[headers.values] 504X-Frame-Options = "DENY" 505X-XSS-Protection = "1; mode=block" 506X-Content-Type-Options = "nosniff" 507Referrer-Policy = "strict-origin-when-cross-origin" 508Content-Security-Policy = "script-src localhost:1313" 509{{< /code-toggle >}} 510 511 512{{< new-in "0.72.0" >}} 513 514You can also specify simple redirects rules for the server. The syntax is again similar to Netlify's. 515 516Note that a `status` code of 200 will trigger a [URL rewrite](https://docs.netlify.com/routing/redirects/rewrites-proxies/), which is what you want in SPA situations, e.g: 517 518{{< code-toggle file="config/development/server">}} 519[[redirects]] 520from = "/myspa/**" 521to = "/myspa/" 522status = 200 523force = false 524{{< /code-toggle >}} 525 526{{< new-in "0.76.0" >}} Setting `force=true` will make a redirect even if there is existing content in the path. Note that before Hugo 0.76 `force` was the default behaviour, but this is inline with how Netlify does it. 527 528## Configure Title Case 529 530Set `titleCaseStyle` to specify the title style used by the [title](/functions/title/) template function and the automatic section titles in Hugo. It defaults to [AP Stylebook](https://www.apstylebook.com/) for title casing, but you can also set it to `Chicago` or `Go` (every word starts with a capital letter). 531 532## Configuration Environment Variables 533 534HUGO_NUMWORKERMULTIPLIER 535: Can be set to increase or reduce the number of workers used in parallel processing in Hugo. If not set, the number of logical CPUs will be used. 536 537## Configuration Lookup Order 538 539Similar to the template [lookup order][], Hugo has a default set of rules for searching for a configuration file in the root of your website's source directory as a default behavior: 540 5411. `./config.toml` 5422. `./config.yaml` 5433. `./config.json` 544 545In your `config` file, you can direct Hugo as to how you want your website rendered, control your website's menus, and arbitrarily define site-wide parameters specific to your project. 546 547 548## Example Configuration 549 550The following is a typical example of a configuration file. The values nested under `params:` will populate the [`.Site.Params`][] variable for use in [templates][]: 551 552{{< code-toggle file="config">}} 553baseURL: "https://yoursite.example.com/" 554title: "My Hugo Site" 555footnoteReturnLinkContents: "↩" 556permalinks: 557 posts: /:year/:month/:title/ 558params: 559 Subtitle: "Hugo is Absurdly Fast!" 560 AuthorName: "Jon Doe" 561 GitHubUser: "spf13" 562 ListOfFoo: 563 - "foo1" 564 - "foo2" 565 SidebarRecentLimit: 5 566{{< /code-toggle >}} 567 568## Configure with Environment Variables 569 570In addition to the 3 config options already mentioned, configuration key-values can be defined through operating system environment variables. 571 572For example, the following command will effectively set a website's title on Unix-like systems: 573 574``` 575$ env HUGO_TITLE="Some Title" hugo 576``` 577 578This is really useful if you use a service such as Netlify to deploy your site. Look at the Hugo docs [Netlify configuration file](https://github.com/gohugoio/hugoDocs/blob/master/netlify.toml) for an example. 579 580{{% note "Setting Environment Variables" %}} 581Names must be prefixed with `HUGO_` and the configuration key must be set in uppercase when setting operating system environment variables. 582 583To set config params, prefix the name with `HUGO_PARAMS_` 584{{% /note %}} 585 586{{< new-in "0.79.0" >}} If you are using snake_cased variable names, the above will not work, so since Hugo 0.79.0 Hugo determines the delimiter to use by the first character after `HUGO`. This allows you to define environment variables on the form `HUGOxPARAMSxAPI_KEY=abcdefgh`, using any [allowed](https://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names#:~:text=So%20names%20may%20contain%20any,not%20begin%20with%20a%20digit.) delimiter. 587 588{{< todo >}} 589Test and document setting params via JSON env var. 590{{< /todo >}} 591 592## Ignore Content and Data Files when Rendering 593 594To exclude specific files from the `content` and `data` directories when rendering your site, set `ignoreFiles` to one or more regular expressions to match against the absolute file path. 595 596To ignore files ending with `.foo` or `.boo`: 597 598{{< code-toggle copy="false" >}} 599ignoreFiles = ['\.foo$', '\.boo$'] 600{{< /code-toggle >}} 601 602To ignore a file using the absolute file path: 603 604{{< code-toggle copy="false" >}} 605ignoreFiles = ['^/home/user/project/content/test\.md$'] 606{{< /code-toggle >}} 607 608## Configure Front Matter 609 610### Configure Dates 611 612Dates are important in Hugo, and you can configure how Hugo assigns dates to your content pages. You do this by adding a `frontmatter` section to your `config.toml`. 613 614 615The default configuration is: 616 617{{< code-toggle file="config" >}} 618[frontmatter] 619date = ["date", "publishDate", "lastmod"] 620lastmod = [":git", "lastmod", "date", "publishDate"] 621publishDate = ["publishDate", "date"] 622expiryDate = ["expiryDate"] 623{{< /code-toggle >}} 624 625If you, as an example, have a non-standard date parameter in some of your content, you can override the setting for `date`: 626 627{{< code-toggle file="config" >}} 628[frontmatter] 629date = ["myDate", ":default"] 630{{< /code-toggle >}} 631 632The `:default` is a shortcut to the default settings. The above will set `.Date` to the date value in `myDate` if present, if not we will look in `date`,`publishDate`, `lastmod` and pick the first valid date. 633 634In the list to the right, values starting with ":" are date handlers with a special meaning (see below). The others are just names of date parameters (case insensitive) in your front matter configuration. Also note that Hugo have some built-in aliases to the above: `lastmod` => `modified`, `publishDate` => `pubdate`, `published` and `expiryDate` => `unpublishdate`. With that, as an example, using `pubDate` as a date in front matter, will, by default, be assigned to `.PublishDate`. 635 636The special date handlers are: 637 638 639`:fileModTime` 640: Fetches the date from the content file's last modification timestamp. 641 642An example: 643 644{{< code-toggle file="config" >}} 645[frontmatter] 646lastmod = ["lastmod", ":fileModTime", ":default"] 647{{< /code-toggle >}} 648 649 650The above will try first to extract the value for `.Lastmod` starting with the `lastmod` front matter parameter, then the content file's modification timestamp. The last, `:default` should not be needed here, but Hugo will finally look for a valid date in `:git`, `date` and then `publishDate`. 651 652 653`:filename` 654: Fetches the date from the content file's filename. For example, `2018-02-22-mypage.md` will extract the date `2018-02-22`. Also, if `slug` is not set, `mypage` will be used as the value for `.Slug`. 655 656An example: 657 658{{< code-toggle file="config" >}} 659[frontmatter] 660date = [":filename", ":default"] 661{{< /code-toggle >}} 662 663The above will try first to extract the value for `.Date` from the filename, then it will look in front matter parameters `date`, `publishDate` and lastly `lastmod`. 664 665 666`:git` 667: This is the Git author date for the last revision of this content file. This will only be set if `--enableGitInfo` is set or `enableGitInfo = true` is set in site config. 668 669## Configure Additional Output Formats 670 671Hugo v0.20 introduced the ability to render your content to multiple output formats (e.g., to JSON, AMP html, or CSV). See [Output Formats][] for information on how to add these values to your Hugo project's configuration file. 672 673## Configure Minify 674 675{{< new-in "0.68.0" >}} 676 677Default configuration: 678 679{{< code-toggle config="minify" />}} 680 681## Configure File Caches 682 683Since Hugo 0.52 you can configure more than just the `cacheDir`. This is the default configuration: 684 685{{< code-toggle >}} 686[caches] 687[caches.getjson] 688dir = ":cacheDir/:project" 689maxAge = -1 690[caches.getcsv] 691dir = ":cacheDir/:project" 692maxAge = -1 693[caches.getresource] 694dir = ":cacheDir/:project" 695maxAge = -1 696[caches.images] 697dir = ":resourceDir/_gen" 698maxAge = -1 699[caches.assets] 700dir = ":resourceDir/_gen" 701maxAge = -1 702[caches.modules] 703dir = ":cacheDir/modules" 704maxAge = -1 705{{< /code-toggle >}} 706 707You can override any of these cache settings in your own `config.toml`. 708 709### The keywords explained 710 711`:cacheDir` 712: This is the value of the `cacheDir` config option if set (can also be set via OS env variable `HUGO_CACHEDIR`). It will fall back to `/opt/build/cache/hugo_cache/` on Netlify, or a `hugo_cache` directory below the OS temp dir for the others. This means that if you run your builds on Netlify, all caches configured with `:cacheDir` will be saved and restored on the next build. For other CI vendors, please read their documentation. For an CircleCI example, see [this configuration](https://github.com/bep/hugo-sass-test/blob/6c3960a8f4b90e8938228688bc49bdcdd6b2d99e/.circleci/config.yml). 713 714`:project` 715: The base directory name of the current Hugo project. This means that, in its default setting, every project will have separated file caches, which means that when you do `hugo --gc` you will not touch files related to other Hugo projects running on the same PC. 716 717`:resourceDir` 718: This is the value of the `resourceDir` config option. 719 720maxAge 721: This is the duration before a cache entry will be evicted, -1 means forever and 0 effectively turns that particular cache off. Uses Go's `time.Duration`, so valid values are `"10s"` (10 seconds), `"10m"` (10 minutes) and `"10h"` (10 hours). 722 723dir 724: The absolute path to where the files for this cache will be stored. Allowed starting placeholders are `:cacheDir` and `:resourceDir` (see above). 725 726## Configuration Format Specs 727 728* [TOML Spec][toml] 729* [YAML Spec][yaml] 730* [JSON Spec][json] 731 732[`.Site.Params`]: /variables/site/ 733[directory structure]: /getting-started/directory-structure 734[json]: https://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf "Specification for JSON, JavaScript Object Notation" 735[lookup order]: /templates/lookup-order/ 736[Output Formats]: /templates/output-formats/ 737[templates]: /templates/ 738[toml]: https://github.com/toml-lang/toml 739[yaml]: https://yaml.org/spec/ 740[static-files]: /content-management/static-files/ 741