Merge commit '5be51ac3db225d5df501ed1fa1499c41d97dbf65'

author: Bjørn Erik Pedersen <bjorn.erik.pedersen@gmail.com> 2025-04-10 13:04:51 +0200
committer: Bjørn Erik Pedersen <bjorn.erik.pedersen@gmail.com> 2025-04-10 13:04:51 +0200
commit: 653f1c1d462332bccf303a5040e5cd99c89a4378 (patch)
tree: c993984f169a240567526e9993261241c0cda771 /docs/content/en/getting-started
parent: 208a0de6c31354df6f9463d49e90db9dec935169 (diff)
parent: 5be51ac3db225d5df501ed1fa1499c41d97dbf65 (diff)
download: hugo-653f1c1d462332bccf303a5040e5cd99c89a4378.tar.gz
hugo-653f1c1d462332bccf303a5040e5cd99c89a4378.zip
8 files changed, 98 insertions, 1625 deletions
diff --git a/docs/content/en/getting-started/_index.md b/docs/content/en/getting-started/_index.md
index ca180d999..2e2f57127 100644
--- a/docs/content/en/getting-started/_index.md
+++ b/docs/content/en/getting-started/_index.md
@@ -1,20 +1,8 @@
 ---
 title: Getting started
-
 description: How to get started with Hugo.
 categories: []
 keywords: []
-menu:
-  docs:
-    identifier: getting-started-in-this-section
-    parent: getting-started
-    weight: 10
 weight: 10
 aliases: [/overview/introduction/]
 ---
-
-If this is your first time using Hugo and you've [already installed Hugo on your machine][installed], we recommend the [quick start]. You can also use [external learning resources] to learn Hugo.
-
-[installed]: /installation/
-[quick start]: /getting-started/quick-start/
-[external learning resources]: /getting-started/external-learning-resources/
diff --git a/docs/content/en/getting-started/configuration-build.md b/docs/content/en/getting-started/configuration-build.md
deleted file mode 100644
index 791d4bb99..000000000
--- a/docs/content/en/getting-started/configuration-build.md
+++ /dev/null
@@ -1,85 +0,0 @@
----
-title: Configure build
-description: Configure global build options.
-categories: [getting started,fundamentals]
-keywords: [build,buildStats,cache]
-menu:
-  docs:
-    parent: getting-started
-    weight: 70
-weight: 70
-slug: configuration-build
-toc: true
----
-
-The `build` configuration section contains global build-related configuration options.
-
-{{< code-toggle config=build />}}
-
-###### buildStats
-
-See [Configure buildStats](#configure-build-stats).
-
-###### cachebusters
-
-See [Configure Cache Busters](#configure-cache-busters).
-
-###### noJSConfigInAssets
-
-(`bool`) If `true`, turns off writing a `jsconfig.json` into your `assets` directory with mapping of imports from running [js.Build](/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.
-
-###### useResourceCacheWhen
-
-(`string`) When to use the resource file cache, one of `never`, `fallback`, or `always`. Applicable when transpiling Sass to CSS. Default is `fallback`.
-
-## Configure cache busters
-
-The `build.cachebusters` configuration option was added to support development using Tailwind 3.x's JIT compiler where a `build` configuration may look like this:
-
-{{< code-toggle file=hugo >}}
-[build]
-  [build.buildStats]
-    enable = true
-  [[build.cachebusters]]
-    source = "assets/watching/hugo_stats\\.json"
-    target = "styles\\.css"
-  [[build.cachebusters]]
-    source = "(postcss|tailwind)\\.config\\.js"
-    target = "css"
-  [[build.cachebusters]]
-    source = "assets/.*\\.(js|ts|jsx|tsx)"
-    target = "js"
-  [[build.cachebusters]]
-    source = "assets/.*\\.(.*)$"
-    target = "$1"
-{{< /code-toggle >}}
-
-When `buildStats` {{< new-in 0.115.1 />}} is enabled, Hugo writes a `hugo_stats.json` file on each build with HTML classes etc. that's used in the rendered output. Changes to this file will trigger a rebuild of the `styles.css` file. You also need to add `hugo_stats.json` to Hugo's server watcher. See [Hugo Starter Tailwind Basic](https://github.com/bep/hugo-starter-tailwind-basic) for a running example.
-
-source
-: A regexp matching file(s) relative to one of the virtual component directories in Hugo, typically `assets/...`.
-
-target
-: A regexp matching the keys in the resource cache that should be expired when `source` changes. You can use the matching regexp groups from `source` in the expression, e.g. `$1`.
-
-## Configure build stats 
-
-{{< code-toggle config=build.buildStats />}}
-
-{{< new-in 0.115.1 />}}
-
-If `enable` is set to `true`, creates a `hugo_stats.json` file in the root of your project. This file contains arrays of the `class` attributes, `id` attributes, and tags of every HTML element within your published site. Use this file as data source when [removing unused CSS] from your site. This process is also known as pruning, purging, or tree shaking.
-
-[removing unused CSS]: /functions/resources/postprocess/
-
-Exclude `class` attributes, `id` attributes, or tags from `hugo_stats.json` with the `disableClasses`, `disableIDs`, and `disableTags` keys.
-
-{{% note %}}
-Given that CSS purging is typically limited to production builds, place the `buildStats` object below [`config/production`].
-
-[`config/production`]: /getting-started/configuration/#configuration-directory
-
-Built for speed, there may be "false positive" detections (e.g., HTML elements that are not HTML elements) while parsing the published site. These "false positives" are infrequent and inconsequential.
-{{% /note %}}
-
-Due to the nature of partial server builds, new HTML entities are added while the server is running, but old values will not be removed until you restart the server or run a regular `hugo` build.
diff --git a/docs/content/en/getting-started/configuration-markup.md b/docs/content/en/getting-started/configuration-markup.md
deleted file mode 100644
index ef885e44b..000000000
--- a/docs/content/en/getting-started/configuration-markup.md
+++ /dev/null
@@ -1,387 +0,0 @@
----
-title: Configure markup
-description: Configure rendering of markup to HTML.
-categories: [getting started,fundamentals]
-keywords: [markup,markdown,goldmark,asciidoc,asciidoctor,highlighting]
-menu:
-  docs:
-    parent: getting-started
-    weight: 60
-weight: 60
-slug: configuration-markup
-toc: true
----
-
-## Default handler
-
-Hugo uses [Goldmark] to render Markdown to HTML.
-
-{{< code-toggle file=hugo >}}
-[markup]
-defaultMarkdownHandler = 'goldmark'
-{{< /code-toggle >}}
-
-Files with a `.md`, `.mdown`, or `.markdown` extension are processed as Markdown, provided that you have not specified a different [content format] using the `markup` field in front matter.
-
-To use a different renderer for Markdown files, specify one of `asciidocext`, `org`, `pandoc`, or `rst` in your site configuration.
-
-defaultMarkdownHandler|Description
-:--|:--
-`asciidocext`|[AsciiDoc]
-`goldmark`|[Goldmark]
-`org`|[Emacs Org Mode]
-`pandoc`|[Pandoc]
-`rst`|[reStructuredText]
-
-To use AsciiDoc, Pandoc, or reStructuredText you must install the relevant renderer and update your [security policy].
-
-{{% note %}}
-Unless you need a unique capability provided by one of the alternative Markdown handlers, we strongly recommend that you use the default setting. Goldmark is fast, well maintained, conforms to the [CommonMark] specification, and is compatible with [GitHub Flavored Markdown] (GFM).
-
-[commonmark]: https://spec.commonmark.org/0.30/
-[github flavored markdown]: https://github.github.com/gfm/
-{{% /note %}}
-
-[asciidoc]: https://asciidoc.org/
-[content format]: /content-management/formats/#formats
-[emacs org mode]: https://orgmode.org/
-[goldmark]: https://github.com/yuin/goldmark/
-[pandoc]: https://pandoc.org/
-[restructuredtext]: https://docutils.sourceforge.io/rst.html
-[security policy]: /about/security/#security-policy
-
-## Goldmark
-
-This is the default configuration for the Goldmark Markdown renderer:
-
-{{< code-toggle config=markup.goldmark />}}
-
-### Goldmark extensions
-
-The extensions below, excluding Extras and Passthrough, are enabled by default.
-
-Extension|Documentation|Enabled
-:--|:--|:-:
-cjk|[Goldmark Extensions: CJK]|:heavy_check_mark:
-definitionList|[PHP Markdown Extra: Definition lists]|:heavy_check_mark:
-extras|[Hugo Goldmark Extensions: Extras]|
-footnote|[PHP Markdown Extra: Footnotes]|:heavy_check_mark:
-linkify|[GitHub Flavored Markdown: Autolinks]|:heavy_check_mark:
-passthrough|[Hugo Goldmark Extensions: Passthrough]|
-strikethrough|[GitHub Flavored Markdown: Strikethrough]|:heavy_check_mark:
-table|[GitHub Flavored Markdown: Tables]|:heavy_check_mark:
-taskList|[GitHub Flavored Markdown: Task list items]|:heavy_check_mark:
-typographer|[Goldmark Extensions: Typographer]|:heavy_check_mark:
-
-[GitHub Flavored Markdown: Autolinks]: https://github.github.com/gfm/#autolinks-extension-
-[GitHub Flavored Markdown: Strikethrough]: https://github.github.com/gfm/#strikethrough-extension-
-[GitHub Flavored Markdown: Tables]: https://github.github.com/gfm/#tables-extension-
-[GitHub Flavored Markdown: Task list items]: https://github.github.com/gfm/#task-list-items-extension-
-[Goldmark Extensions: CJK]: https://github.com/yuin/goldmark?tab=readme-ov-file#cjk-extension
-[Goldmark Extensions: Typographer]: https://github.com/yuin/goldmark?tab=readme-ov-file#typographer-extension
-[Hugo Goldmark Extensions: Extras]: https://github.com/gohugoio/hugo-goldmark-extensions?tab=readme-ov-file#extras-extension
-[Hugo Goldmark Extensions: Passthrough]: https://github.com/gohugoio/hugo-goldmark-extensions?tab=readme-ov-file#passthrough-extension
-[PHP Markdown Extra: Definition lists]: https://michelf.ca/projects/php-markdown/extra/#def-list
-[PHP Markdown Extra: Footnotes]: https://michelf.ca/projects/php-markdown/extra/#footnotes
-
-#### Extras
-
-{{< new-in 0.126.0 />}}
-
-Enable [deleted text], [inserted text], [mark text], [subscript], and [superscript] elements in Markdown.
-
-Element|Markdown|Rendered
-:--|:--|:--
-Deleted text|`~~foo~~`|`<del>foo</del>`
-Inserted text|`++bar++`|`<ins>bar</ins>`
-Mark text|`==baz==`|`<mark>baz</mark>`
-Subscript|`H~2~O`|`H<sub>2</sub>O`
-Superscript|`1^st^`|`1<sup>st</sup>`
-
-[deleted text]: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/del
-[inserted text]: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/ins
-[mark text]: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/mark
-[subscript]: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/sub
-[superscript]: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/sup
-
-To avoid a conflict when enabling the Hugo Goldmark Extras subscript extension, if you want to render subscript and strikethrough text concurrently you must:
-
-1. Disable the Goldmark strikethrough extension
-1. Enable the Hugo Goldmark Extras delete extension
-
-For example:
-
-{{< code-toggle file=hugo >}}
-[markup.goldmark.extensions]
-strikethrough = false
-
-[markup.goldmark.extensions.extras.delete]
-enable = true
-
-[markup.goldmark.extensions.extras.subscript]
-enable = true
-{{< /code-toggle >}}
-
-#### Passthrough
-
-{{< new-in 0.122.0 />}}
-
-Enable the passthrough extension to include mathematical equations and expressions in Markdown using LaTeX markup. See [mathematics in Markdown] for details.
-
-[mathematics in Markdown]: content-management/mathematics/
-
-#### Typographer
-
-The Typographer extension replaces certain character combinations with HTML entities as specified below:
-
-Markdown|Replaced by|Description
-:--|:--|:--
-`...`|`&hellip;`|horizontal ellipsis
-`'`|`&rsquo;`|apostrophe
-`--`|`&ndash;`|en dash
-`---`|`&mdash;`|em dash
-`«`|`&laquo;`|left angle quote
-`“`|`&ldquo;`|left double quote
-`‘`|`&lsquo;`|left single quote
-`»`|`&raquo;`|right angle quote
-`”`|`&rdquo;`|right double quote
-`’`|`&rsquo;`|right single quote
-
-### Goldmark settings explained
-
-Most of the Goldmark settings above are self-explanatory, but some require explanation.
-
-###### duplicateResourceFiles
-
-{{< new-in 0.123.0 />}}
-
-(`bool`) If `true`, shared page resources on multilingual single-host sites will be duplicated for each language. See [multilingual page resources] for details. Default is `false`.
-
-[multilingual page resources]: /content-management/page-resources/#multilingual
-
-{{% note %}}
-With multilingual single-host sites, setting this parameter to `false` will enable Hugo's [embedded link render hook] and [embedded image render hook]. This is the default configuration for multilingual single-host sites.
-
-[embedded image render hook]: /render-hooks/images/#default
-[embedded link render hook]: /render-hooks/links/#default
-{{% /note %}}
-
-###### parser.wrapStandAloneImageWithinParagraph
-
-(`bool`) If `true`, image elements without adjacent content will be wrapped within a `p` element when rendered. This is the default Markdown behavior. Set to `false` when using an [image render hook] to render standalone images as `figure` elements. Default is `true`.
-
-[image render hook]: /render-hooks/images/
-
-###### parser.autoHeadingIDType
-
-(`string`) The strategy used to automatically generate heading `id` attributes, one of `github`, `github-ascii` or `blackfriday`.
-
-- `github` produces GitHub-compatible `id` attributes
-- `github-ascii` drops any non-ASCII characters after accent normalization
-- `blackfriday` produces `id` attributes compatible with the Blackfriday Markdown renderer
-
-This is also the strategy used by the [anchorize](/functions/urls/anchorize) template function. Default is `github`.
-
-###### parser.attribute.block
-
-(`bool`) If `true`, enables [Markdown attributes] for block elements. Default is `false`.
-
-[Markdown attributes]: /content-management/markdown-attributes/
-
-###### parser.attribute.title
-
-(`bool`) If `true`, enables [Markdown attributes] for headings. Default is `true`.
-
-###### renderHooks.image.enableDefault
-
-{{< new-in 0.123.0 />}}
-
-(`bool`) If `true`, enables Hugo's [embedded image render hook]. Default is `false`.
-
-[embedded image render hook]: /render-hooks/images/#default
-
-{{% note %}}
-The embedded image render hook is automatically enabled for multilingual single-host sites if [duplication of shared page resources] is disabled. This is the default configuration for multilingual single-host sites.
-
-[duplication of shared page resources]: /getting-started/configuration-markup/#duplicateresourcefiles
-{{% /note %}}
-
-###### renderHooks.link.enableDefault
-
-{{< new-in 0.123.0 />}}
-
-(`bool`) If `true`, enables Hugo's [embedded link render hook]. Default is `false`.
-
-[embedded link render hook]: /render-hooks/links/#default
-
-{{% note %}}
-The embedded link render hook is automatically enabled for multilingual single-host sites if [duplication of shared page resources] is disabled. This is the default configuration for multilingual single-host sites.
-
-[duplication of shared page resources]: /getting-started/configuration-markup/#duplicateresourcefiles
-{{% /note %}}
-
-###### renderer.hardWraps
-
-(`bool`) If `true`, Goldmark replaces newline characters within a paragraph with `br` elements. Default is `false`.
-
-###### renderer.unsafe
-
-(`bool`) If `true`, Goldmark renders raw HTML mixed within the Markdown. This is unsafe unless the content is under your control. Default is `false`.
-
-## AsciiDoc
-
-This is the default configuration for the AsciiDoc renderer:
-
-{{< code-toggle config=markup.asciidocExt />}}
-
-### AsciiDoc settings explained
-
-###### attributes
-
-(`map`) A map of key-value pairs, each a document attribute. See Asciidoctor’s [attributes].
-
-[attributes]: https://asciidoctor.org/docs/asciidoc-syntax-quick-reference/#attributes-and-substitutions
-
-###### backend
-
-(`string`) The backend output file format. Default is `html5`.
-
-###### extensions
-
-(`string array`) An array of enabled extensions, one or more of `asciidoctor-html5s`, `asciidoctor-bibtex`, `asciidoctor-diagram`, `asciidoctor-interdoc-reftext`, `asciidoctor-katex`, `asciidoctor-latex`, `asciidoctor-mathematical`, or `asciidoctor-question`.
-
-{{% note %}}
-To mitigate security risks, entries in the extension array may not contain forward slashes (`/`), backslashes (`\`), or periods. Due to this restriction, extensions must be in Ruby's `$LOAD_PATH`.
-{{% /note %}}
-
-###### failureLevel
-
-(`string`) The minimum logging level that triggers a non-zero exit code (failure). Default is `fatal`.
-
-###### noHeaderOrFooter
-
-(`bool`) If `true`, outputs an embeddable document, which excludes the header, the footer, and everything outside the body of the document. Default is `true`.
-
-###### preserveTOC
-
-(`bool`) If `true`, preserves the table of contents (TOC) rendered by Asciidoctor. By default, to make the TOC compatible with existing themes, Hugo removes the TOC rendered by Asciidoctor. To render the TOC, use the [`TableOfContents`] method on a `Page` object in your templates. Default is `false`.
-
-[`TableOfContents`]: /methods/page/tableofcontents/
-
-###### safeMode
-
-(`string`) The safe mode level, one of `unsafe`, `safe`, `server`, or `secure`. Default is `unsafe`.
-
-###### sectionNumbers
-
-(`bool`) If `true`, numbers each section title. Default is `false`.
-
-###### trace
-
-(`bool`) If `true`, include backtrace information on errors. Default is `false`.
-
-###### verbose
-
-(`bool`)If `true`, verbosely prints processing information and configuration file checks to stderr. Default is `false`.
-
-###### workingFolderCurrent
-
-(`bool`) If `true`, sets the working directory to be the same as that of the AsciiDoc file being processed, allowing [includes] to work with relative paths. Set to `true` to render diagrams with the [asciidoctor-diagram] extension. Default is `false`.
-
-[asciidoctor-diagram]: https://asciidoctor.org/docs/asciidoctor-diagram/
-[includes]: https://docs.asciidoctor.org/asciidoc/latest/syntax-quick-reference/#includes
-
-### AsciiDoc configuration example
-
-{{< code-toggle file=hugo >}}
-[markup.asciidocExt]
-    extensions = ["asciidoctor-html5s", "asciidoctor-diagram"]
-    workingFolderCurrent = true
-    [markup.asciidocExt.attributes]
-        my-base-url = "https://example.com/"
-        my-attribute-name = "my value"
-{{< /code-toggle >}}
-
-### AsciiDoc syntax highlighting
-
-Follow the steps below to enable syntax highlighting.
-
-Step 1
-: Set the `source-highlighter` attribute in your site configuration. For example:
-
-{{< code-toggle file=hugo >}}
-[markup.asciidocExt.attributes]
-source-highlighter = 'rouge'
-{{< /code-toggle >}}
-
-Step 2
-: Generate the highlighter CSS. For example:
-
-```text
-rougify style monokai.sublime > assets/css/syntax.css
-```
-
-Step 3
-: In your base template add a link to the CSS file:
-
-{{< code file=layouts/_default/baseof.html >}}
-<head>
-  ...
-  {{ with resources.Get "css/syntax.css" }}
-    <link rel="stylesheet" href="{{ .RelPermalink }}" integrity="{{ .Data.Integrity }}" crossorigin="anonymous">
-  {{ end }}
-  ...
-</head>
-{{< /code >}}
-
-Then add the code to be highlighted to your markup:
-
-```text
-[#hello,ruby]
-----
-require 'sinatra'
-
-get '/hi' do
-  "Hello World!"
-end
-----
-```
-
-### AsciiDoc troubleshooting
-
-Run `hugo --logLevel debug` to examine Hugo's call to the Asciidoctor executable:
-
-```txt
-INFO 2019/12/22 09:08:48 Rendering book-as-pdf.adoc with C:\Ruby26-x64\bin\asciidoctor.bat using asciidoc args [--no-header-footer -r asciidoctor-html5s -b html5s -r asciidoctor-diagram --base-dir D:\prototypes\hugo_asciidoc_ddd\docs -a outdir=D:\prototypes\hugo_asciidoc_ddd\build -] ...
-```
-
-## Highlight
-
-This is the default `highlight` configuration. Note that some of these settings can be set per code block, see [Syntax Highlighting](/content-management/syntax-highlighting/).
-
-{{< code-toggle config=markup.highlight />}}
-
-For `style`, see these galleries:
-
-* [Short snippets](https://xyproto.github.io/splash/docs/all.html)
-* [Long snippets](https://xyproto.github.io/splash/docs/longer/all.html)
-
-For CSS, see [Generate Syntax Highlighter CSS](/content-management/syntax-highlighting/#generate-syntax-highlighter-css).
-
-## Table of contents
-
-This is the default configuration for the table of contents, applicable to Goldmark and Asciidoctor:
-
-{{< code-toggle config=markup.tableOfContents />}}
-
-###### startLevel
-
-(`int`) Heading levels less than this value will be excluded from the table of contents. For example, to exclude `h1` elements from the table of contents, set this value to `2`. Default is `2`.
-
-###### endLevel
-
-(`int`) Heading levels greater than this value will be excluded from the table of contents. For example, to exclude `h4`, `h5`, and `h6` elements from the table of contents, set this value to `3`. Default is `3`.
-
-###### ordered
-
-(`bool`) If `true`, generates an ordered list instead of an unordered list. Default is `false`.
diff --git a/docs/content/en/getting-started/configuration.md b/docs/content/en/getting-started/configuration.md
deleted file mode 100644
index 23376f68f..000000000
--- a/docs/content/en/getting-started/configuration.md
+++ /dev/null
@@ -1,996 +0,0 @@
----
-title: Configure Hugo
-linkTitle: Configuration
-description: How to configure your Hugo site.
-categories: [getting started,fundamentals]
-keywords: [configuration,toml,yaml,json]
-menu:
-  docs:
-    parent: getting-started
-    weight: 50
-weight: 50
-toc: true
-aliases: [/overview/source-directory/,/overview/configuration/]
----
-
-## Configuration file
-
-Create a site configuration file in the root of your project directory, naming it `hugo.toml`, `hugo.yaml`, or `hugo.json`, with that order of precedence.
-
-```text
-my-project/
-└── hugo.toml
-```
-
-{{% note %}}
-With v0.109.0 and earlier the basename of the site configuration file was `config` instead of `hugo`. You can use either, but should transition to the new naming convention when practical.
-{{% /note %}}
-
-A simple example:
-
-{{< code-toggle file=hugo >}}
-baseURL = 'https://example.org/'
-languageCode = 'en-us'
-title = 'ABC Widgets, Inc.'
-[params]
-subtitle = 'The Best Widgets on Earth'
-[params.contact]
-email = 'info@example.org'
-phone = '+1 202-555-1212'
-{{< /code-toggle >}}
-
-To use a different configuration file when building your site, use the `--config` flag:
-
-```sh
-hugo --config other.toml
-```
-
-Combine two or more configuration files, with left-to-right precedence:
-
-```sh
-hugo --config a.toml,b.yaml,c.json
-```
-
-{{% note %}}
-See the specifications for each file format: [TOML], [YAML], and [JSON].
-
-[TOML]: https://toml.io/en/latest
-[YAML]: https://yaml.org/spec/
-[JSON]: https://datatracker.ietf.org/doc/html/rfc7159
-{{% /note %}}
-
-## Configuration directory
-
-Instead of a single site configuration file, split your configuration by [environment](g), root configuration key, and language. For example:
-
-```text
-my-project/
-└── config/
-    ├── _default/
-    │   ├── hugo.toml
-    │   ├── menus.en.toml
-    │   ├── menus.de.toml
-    │   └── params.toml
-    └── production/
-        └── params.toml
-```
-
-The root configuration keys are `build`, `caches`, `cascade`, `deployment`, `frontmatter`, `imaging`, `languages`, `markup`, `mediatypes`, `menus`, `minify`, `module`, `outputformats`, `outputs`, `params`, `permalinks`, `privacy`, `related`, `security`, `segments`, `server`, `services`, `sitemap`, and `taxonomies`.
-
-### Omit the root key
-
-When splitting the configuration by root key, omit the root key in the given file. For example, these are equivalent:
-
-{{< code-toggle file=hugo >}}
-[params]
-foo = 'bar'
-{{< /code-toggle >}}
-
-{{< code-toggle file=params >}}
-foo = 'bar'
-{{< /code-toggle >}}
-
-### Recursive parsing
-
-Hugo parses the `config` directory recursively, allowing you to organize the files into subdirectories. For example:
-
-```text
-my-project/
-└── config/
-    └── _default/
-        ├── navigation/
-        │   ├── menus.de.toml
-        │   └── menus.en.toml
-        └── hugo.toml
-```
-
-### Example
-
-```text
-my-project/
-└── config/
-    ├── _default/
-    │   ├── hugo.toml
-    │   ├── menus.en.toml
-    │   ├── menus.de.toml
-    │   └── params.toml
-    ├── production/
-    │   ├── hugo.toml
-    │   └── params.toml
-    └── staging/
-        ├── hugo.toml
-        └── params.toml
-```
-
-Considering the structure above, when running `hugo --environment staging`, Hugo will use every setting from `config/_default` and merge `staging`'s on top of those.
-
-Let's take an example to understand this better. Let's say you are using Google Analytics for your website. This requires you to specify a [Google tag ID] in your site configuration:
-
-[Google tag ID]: https://support.google.com/tagmanager/answer/12326985?hl=en
-
-{{< code-toggle file=hugo copy=false >}}
-[services.googleAnalytics]
-ID = 'G-XXXXXXXXX'
-{{< /code-toggle >}}
-
-Now consider the following scenario:
-
-1. You don't want to load the analytics code when running `hugo server`.
-1. You want to use different Google tag IDs for your production and staging environments. For example:
-
-    - `G-PPPPPPPPP` for production
-    - `G-SSSSSSSSS` for staging
-
-To satisfy these requirements, configure your site as follows:
-
-1. `config/_default/hugo.toml`
-
-    Exclude the `services.googleAnalytics` section. This will prevent loading of the analytics code when you run `hugo server`.
-
-    By default, Hugo sets its `environment` to `development` when running `hugo server`. In the absence of a `config/development` directory, Hugo uses the `config/_default` directory.
-
-1. `config/production/hugo.toml`
-
-    Include this section only:
-
-    {{< code-toggle file=hugo copy=false >}}
-    [services.googleAnalytics]
-    ID = 'G-PPPPPPPPP'
-    {{< /code-toggle >}}
-
-    You do not need to include other parameters in this file. Include only those parameters that are specific to your production environment. Hugo will merge these parameters with the default configuration.
-
-    By default, Hugo sets its `environment` to `production` when running `hugo`. The analytics code will use the `G-PPPPPPPPP` tag ID.
-
-1. `config/staging/hugo.toml`
-
-    Include this section only:
-
-    {{< code-toggle file=hugo copy=false >}}
-    [services.googleAnalytics]
-    ID = 'G-SSSSSSSSS'
-    {{< /code-toggle >}}
-
-    You do not need to include other parameters in this file. Include only those parameters that are specific to your staging environment. Hugo will merge these parameters with the default configuration.
-
-    To build your staging site, run `hugo --environment staging`. The analytics code will use the `G-SSSSSSSSS` tag ID.
-
-## Merge configuration from themes
-
-The configuration value for `_merge` can be one of:
-
-none
-: No merge.
-
-shallow
-: Only add values for new keys.
-
-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.
-
-{{< code-toggle file=hugo dataKey="config_helpers.mergeStrategy" skipHeader=true />}}
-
-## All configuration settings
-
-###### archetypeDir
-
-(`string`) The directory where Hugo finds archetype files (content templates). Default is `archetypes`. {{% module-mounts-note %}}
-
-###### assetDir
-
-(`string`) The directory where Hugo finds asset files used in [Hugo Pipes](/hugo-pipes/). Default is `assets`. {{% module-mounts-note %}}
-
-###### baseURL
-
-(`string`) The absolute URL (protocol, host, path, and trailing slash) of your published site (e.g., `https://www.example.org/docs/`).
-
-###### build
-
-See [Configure Build](#configure-build).
-
-###### buildDrafts
-
-(`bool`) Include drafts when building. Default is `false`.
-
-###### buildExpired
-
-(`bool`) Include content already expired. Default is `false`.
-
-###### buildFuture
-
-(`bool`) Include content with a future publication date. Default is `false`.
-
-###### caches
-
-See [Configure File Caches](#configure-file-caches).
-
-###### canonifyURLs
-
-(`bool`) See&nbsp;[details](/content-management/urls/#canonical-urls) before enabling this feature. Default is `false`.
-
-###### capitalizeListTitles
-
-{{< new-in 0.123.3 />}}
-
-(`bool`) Whether to capitalize automatic list titles. Applicable to section, taxonomy, and term pages. Default is `true`. You can change the capitalization style in your site configuration to one of `ap`, `chicago`, `go`, `firstupper`, or `none`. See&nbsp;[details].
-
-[details]: /getting-started/configuration/#configure-title-case
-
-###### cascade
-
-Pass 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#cascade).
-
-{{% note %}}
-For a website in a single language, define the `[[cascade]]` in [Front Matter](/content-management/front-matter#cascade). For a multilingual website, define the `[[cascade]]` in [Site Config](/getting-started/configuration/#cascade).
-
-To remain consistent and prevent unexpected behavior, do not mix these strategies.
-{{% /note %}}
-
-###### cleanDestinationDir
-
-(`bool`) When building, removes files from destination not found in static directories. Default is `false`.
-
-###### contentDir
-
-(`string`) The directory from where Hugo reads content files.  Default is `content`. {{% module-mounts-note %}}
-
-###### copyright
-
-(`string`) Copyright notice for your site, typically displayed in the footer.
-
-###### dataDir
-
-(`string`) The directory from where Hugo reads data files. Default is `data`. {{% module-mounts-note %}}
-
-###### defaultOutputFormat
-(`string`) The default output format for the site. If unspecified, the first available format in the defined order (by weight, then alphabetically) will be used.
-
-###### defaultContentLanguage
-
-(`string`) Content without language indicator will default to this language. Default is `en`.
-
-###### defaultContentLanguageInSubdir
-
-(`bool`) Render the default content language in subdir, e.g. `content/en/`. The site root `/` will then redirect to `/en/`. Default is `false`.
-
-###### disableAliases
-
-(`bool`) Will 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. Default is `false`.
-
-###### disableDefaultLanguageRedirect
-
-{{< new-in 0.140.0 />}}
-
-(`bool`) Disables generation of redirect to the default language when DefaultContentLanguageInSubdir is `true`. Default is `false`.
-
-###### disableHugoGeneratorInject
-
-(`bool`) Hugo 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. Default is `false`.
-
-###### disableKinds
-
-(`[]string`) Disable rendering of the specified page [kinds](g), any of `404`, `home`, `page`, `robotstxt`, `rss`, `section`, `sitemap`, `taxonomy`, or `term`.
-
-###### disableLanguages
-
-See [disable a language](/content-management/multilingual/#disable-a-language).
-
-###### disableLiveReload
-
-(`bool`) Disable automatic live reloading of browser window. Default is `false`.
-
-###### disablePathToLower
-
-(`bool`) Do not convert the url/path to lowercase. Default is `false`.
-
-###### enableEmoji
-
-(`bool`) Enable Emoji emoticons support for page content; see the [emoji shortcode quick reference guide](/quick-reference/emojis/). Default is `false`.
-
-###### enableGitInfo
-
-(`bool`) Enable `.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. Default is `false`.
-
-###### enableMissingTranslationPlaceholders
-
-(`bool`) Show a placeholder instead of the default value or an empty string if a translation is missing. Default is `false`.
-
-###### enableRobotsTXT
-
-(`bool`) Enable generation of `robots.txt` file. Default is `false`.
-
-###### environment
-
-(`string`) Build environment. Default is `production` when running `hugo` and `development` when running `hugo server`. See [Configuration directory](https://gohugo.io/getting-started/configuration/#configuration-directory).
-###### frontmatter
-
-See [Front matter Configuration](#configure-front-matter).
-
-###### hasCJKLanguage
-
-(`bool`) If true, auto-detect Chinese/Japanese/Korean Languages in the content. This will make `.Summary` and `.WordCount` behave correctly for CJK languages. Default is `false`.
-
-###### ignoreCache
-
-(`bool`) Ignore the cache directory. Default is `false`.
-
-###### ignoreLogs
-(`[]string`) A slice of message identifiers corresponding to warnings and errors you wish to suppress. See [`erroridf`] and [`warnidf`].
-
-[`erroridf`]: /functions/fmt/erroridf/
-[`warnidf`]: /functions/fmt/warnidf/
-
-###### ignoreVendorPaths
-
-(`string`) Ignore vendored modules that match the given [Glob] pattern within the `_vendor` directory.
-
-[Glob]: https://github.com/gobwas/glob?tab=readme-ov-file#example]
-
-###### imaging
-
-See [image processing configuration](/content-management/image-processing/#imaging-configuration).
-
-###### languageCode
-
-(`string`) A language tag as defined by [RFC 5646](https://datatracker.ietf.org/doc/html/rfc5646). This value is used to populate:
-
-- The `<language>` element in the embedded [RSS template]({{% eturl rss %}})
-- The `lang` attribute of the `<html>` element in the embedded [alias template]({{% eturl alias %}})
-- The `og:locale` `meta` element in the embedded [Open Graph template]({{% eturl opengraph %}})
-
-When present in the root of the configuration, this value is ignored if one or more language keys exists. Please specify this value independently for each language key.
-
-###### languages
-
-See [Configure Languages](/content-management/multilingual/#configure-languages).
-
-###### layoutDir
-
-(`string`) The directory that contains templates. Default is `layouts`.
-
-###### markup
-
-See [Configure Markup](/getting-started/configuration-markup).
-
-###### mediaTypes
-
-See [Configure Media Types](/templates/output-formats/#media-types).
-
-###### menus
-
-See [Menus](/content-management/menus/#define-in-site-configuration).
-
-###### minify
-
-See [Configure Minify](#configure-minify).
-
-###### module
-
-Module configuration see [module configuration](/hugo-modules/configuration/).
-
-###### newContentEditor
-
-(`string`) The editor to use when creating new content.
-
-###### noBuildLock
-
-(`bool`) Don't create `.hugo_build.lock` file. Default is `false`.
-
-###### noChmod
-
-(`bool`) Don't sync permission mode of files. Default is `false`.
-
-###### noTimes
-
-(`bool`) Don't sync modification time of files. Default is `false`.
-
-###### outputFormats
-
-See [custom output formats].
-
-###### page
-
-See [configure page](#configure-page).
-
-###### pagination
-
-See [configure pagination](/templates/pagination/#configuration).
-
-###### panicOnWarning
-
-(`bool`) Whether to panic on first WARNING. Default is `false`.
-
-###### permalinks
-
-See [Content Management](/content-management/urls/#permalinks).
-
-###### pluralizeListTitles
-
-(`bool`) Whether to pluralize automatic list titles. Applicable to section pages. Default is `true`.
-
-###### printI18nWarnings
-
-(`bool`) Whether to log WARNINGs for each missing translation. Default is `false`.
-
-###### printPathWarnings
-
-(`bool`) Whether to log WARNINGs when Hugo publishes two or more files to the same path. Default is `false`.
-
-###### printUnusedTemplates
-
-(`bool`) Whether to log WARNINGs for each unused template. Default is `false`.
-
-###### publishDir
-
-(`string`) The directory where Hugo will write the final static site (the HTML files etc.). Default is `public`.
-
-###### refLinksErrorLevel
-
-(`string`) When using `ref` or `relref` to resolve page links and a link cannot be resolved, it will be logged with this log level. Valid values are `ERROR` (default) or `WARNING`. Any `ERROR` will fail the build (`exit -1`).  Default is `ERROR`.
-
-###### refLinksNotFoundURL
-
-(`string`) URL to be used as a placeholder when a page reference cannot be found in `ref` or `relref`. Is used as-is.
-
-###### related
-
-See [Related Content](/content-management/related/#configure-related-content).
-
-###### relativeURLs
-
-(`bool`) See&nbsp;[details](/content-management/urls/#relative-urls) before enabling this feature. Default is `false`.
-
-###### removePathAccents
-
-(`bool`) Removes [non-spacing marks](https://www.compart.com/en/unicode/category/Mn) from [composite characters](https://en.wikipedia.org/wiki/Precomposed_character) in content paths. Default is `false`.
-
-```text
-content/post/hügó.md → https://example.org/post/hugo/
-```
-
-###### renderSegments
-
-{{< new-in 0.124.0 />}}
-
-(`[]string`) A list of segments to render. If not set, everything will be rendered. This is more commonly set in a CLI flag, e.g. `hugo --renderSegments segment1,segment2`. The segment names must match the names in the [segments](#configure-segments) configuration.
-
-###### sectionPagesMenu
-
-See [Menus](/content-management/menus/#define-automatically).
-
-###### security
-
-See [Security Policy](/about/security/#security-policy).
-
-###### segments
-
-See [Segments](#configure-segments).
-
-###### sitemap
-
-Default [sitemap configuration](/templates/sitemap/#configuration).
-
-###### summaryLength
-
-(`int`) Applicable to [automatic summaries], the minimum number of words to render when calling the [`Summary`] method on a `Page` object. In this case the `Summary` method returns the content, truncated to the paragraph closest to the `summaryLength`.
-
-[automatic summaries]: /content-management/summaries/#automatic-summary
-[`Summary`]: /methods/page/summary/
-
-###### taxonomies
-
-See [Configure Taxonomies](/content-management/taxonomies#configure-taxonomies).
-
-###### templateMetrics
-
-(`bool`) Whether to print template execution metrics to the console. Default is `false`. See [Template metrics](/troubleshooting/performance/#template-metrics).
-
-###### templateMetricsHints
-
-(`bool`) Whether to print template execution improvement hints to the console. Applicable when `templateMetrics` is `true`. Default is `false`. See [Template metrics](/troubleshooting/performance/#template-metrics).
-
-###### theme
-
-See [module configuration](/hugo-modules/configuration/#module-configuration-imports) for how to import a theme.
-
-###### themesDir
-
-(`string`) The directory where Hugo reads the themes from. Default is `themes`.
-
-###### timeout
-
-(`string`) Timeout for generating page contents, specified as a [duration](https://pkg.go.dev/time#Duration) or in seconds. *Note:*&nbsp;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). Default is `30s`.
-
-###### timeZone
-
-(`string`) The time zone used to parse dates without time zone offsets, including front matter date fields and values passed to the [`time.AsTime`] and [`time.Format`] template functions. The list of valid values may be system dependent, but should include `UTC`, `Local`, and any location in the [IANA Time Zone Database]. For example, `America/Los_Angeles` and `Europe/Oslo` are valid time zones.
-
-[`time.AsTime`]: /functions/time/astime/
-[`time.Format`]: /functions/time/format/
-[IANA Time Zone Database]: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
-
-###### title
-
-(`string`) Site title.
-
-###### titleCaseStyle
-
-(`string`) Default is `ap`. See [Configure Title Case](#configure-title-case).
-
-###### uglyURLs
-
-(`bool` or `map`) Whether to generate uglyURLs. Default is `false`. See&nbsp;[details](/content-management/urls/#appearance).
-
-###### watch
-
-(`bool`) Watch filesystem for changes and recreate as needed. Default is `false`.
-
-{{% note %}}
-If you are developing your site on a \*nix machine, here is a handy shortcut for finding a configuration option from the command line:
-```txt
-cd ~/sites/yourhugosite
-hugo config | grep emoji
-```
-
-which shows output like
-
-```txt
-enableemoji: true
-```
-{{% /note %}}
-
-## Configure page
-
-{{< new-in 0.133.0 />}}
-
-These methods on a `Page` object navigate to the next or previous page within a page collection, relative to the current page:
-
-- [Next](/methods/page/next/)
-- [NextInSection](/methods/page/nextinsection/)
-- [Prev](/methods/page/prev/)
-- [PrevInSection](/methods/page/previnsection/)
-
-Hugo determines the _next_ and _previous_ page by sorting a page collection according to this sorting hierarchy:
-
-Field|Precedence|Sort direction
-:--|:--|:--
-[`weight`]|1|descending
-[`date`]|2|descending
-[`linkTitle`]|3|descending
-[`path`]|4|descending
-
-[`date`]: /methods/page/date/
-[`weight`]: /methods/page/weight/
-[`linkTitle`]: /methods/page/linktitle/
-[`path`]: /methods/page/path/
-
-The sort direction in the table above corresponds to these default site configuration values:
-
-{{< code-toggle config=page />}}
-
-To sort all fields in ascending order:
-
-{{< code-toggle file=hugo >}}
-[page]
-  nextPrevInSectionSortOrder = 'asc'
-  nextPrevSortOrder = 'asc'
-{{< /code-toggle >}}
-
-{{% note %}}
-These settings do not apply to the [`Next`] or [`Prev`] methods on a `Pages` object.
-
-[`Next`]: /methods/pages/next
-[`Prev`]: /methods/pages/next
-{{% /note %}}
-
-## Configure build
-
-See [Configure Build](/getting-started/configuration-build/).
-
-## Configure server
-
-This 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):
-
-{{< code-toggle file=hugo >}}
-[server]
-[[server.headers]]
-for = "/**"
-
-[server.headers.values]
-X-Frame-Options = "DENY"
-X-XSS-Protection = "1; mode=block"
-X-Content-Type-Options = "nosniff"
-Referrer-Policy = "strict-origin-when-cross-origin"
-Content-Security-Policy = "script-src localhost:1313"
-{{< /code-toggle >}}
-
-Since this is "development only", it may make sense to put it below the `development` environment:
-
-{{< code-toggle file=config/development/server >}}
-[[headers]]
-for = "/**"
-
-[headers.values]
-X-Frame-Options = "DENY"
-X-XSS-Protection = "1; mode=block"
-X-Content-Type-Options = "nosniff"
-Referrer-Policy = "strict-origin-when-cross-origin"
-Content-Security-Policy = "script-src localhost:1313"
-{{< /code-toggle >}}
-
-You can also specify simple redirects rules for the server. The syntax is again similar to Netlify's.
-
-Note 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:
-
-{{< code-toggle file=config/development/server >}}
-[[redirects]]
-from = "/myspa/**"
-to = "/myspa/"
-status = 200
-force = false
-{{< /code-toggle >}}
-
-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 behavior, but this is inline with how Netlify does it.
-
-## 404 server error page {#_404-server-error-page}
-
-Hugo will, by default, render all 404 errors when running `hugo server` with the `404.html` template. Note that if you have already added one or more redirects to your [server configuration](#configure-server), you need to add the 404 redirect explicitly, e.g:
-
-{{< code-toggle file=config/development/server >}}
-[[redirects]]
-from   = "/**"
-to     = "/404.html"
-status = 404
-{{< /code-toggle >}}
-
-With a multilingual site, define the redirect for the default content language last:
-
-{{< code-toggle file=config/development/server >}}
-defaultContentLanguage = 'en'
-defaultContentLanguageInSubdir = false
-[[redirects]]
-from = '/fr/**'
-to = '/fr/404.html'
-status = 404
-
-[[redirects]] # Default language must be last.
-from = '/**'
-to = '/404.html'
-status = 404
-{{< /code-toggle >}}
-
-If you are serving the default content language from a subdirectory:
-
-{{< code-toggle file=config/development/server >}}
-defaultContentLanguage = 'en'
-defaultContentLanguageInSubdir = true
-[[redirects]]
-from = '/fr/**'
-to = '/fr/404.html'
-status = 404
-
-[[redirects]] # Default language must be last.
-from = '/**'
-to = '/en/404.html'
-status = 404
-{{< /code-toggle >}}
-
-## Configure title case
-
-By default, Hugo follows the capitalization rules published in the [Associated Press Stylebook] when creating automatic section titles, and when transforming strings with the [`strings.Title`] function.
-
-Change this behavior by setting `titleCaseStyle` in your site configuration to any of the values below:
-
-ap
-: Use the capitalization rules published in the [Associated Press Stylebook].
-
-chicago
-: Use the capitalization rules published in the [Chicago Manual of Style].
-
-go
-: Capitalize the first letter of every word.
-
-firstupper
-: Capitalize the first letter of the first word.
-
-none
-: Disable transformation of automatic section titles, and disable the transformation performed by the `strings.Title` function. This is useful if you would prefer to manually capitalize section titles as needed, and to bypass opinionated theme usage of the `strings.Title` function.
-
-[`strings.Title`]: /functions/strings/title/
-[Associated Press Stylebook]: https://www.apstylebook.com/
-[Chicago Manual of Style]: https://www.chicagomanualofstyle.org/home.html
-[site configuration]: /getting-started/configuration/#configure-title-case
-
-## Configuration environment variables
-
-DART_SASS_BINARY
-: (`string`) The absolute path to the Dart Sass executable. By default, Hugo searches for the executable in each of the paths in the `PATH` environment variable.
-
-HUGO_ENVIRONMENT
-: (`string`) Overrides the default [environment](g), typically one of `development`, `staging`, or `production`.
-
-HUGO_FILE_LOG_FORMAT
-: (`string`) A format string for the file path, line number, and column number displayed when reporting errors, or when calling the `Position` method from a shortcode or Markdown render hook. Valid tokens are `:file`, `:line`, and `:col`. Default is `:file::line::col`.
-
-{{< new-in 0.123.0 />}}
-
-HUGO_MEMORYLIMIT
-: (`int`) The maximum amount of system memory, in gigabytes, that Hugo can use while rendering your site. Default is 25% of total system memory.
-
-HUGO_NUMWORKERMULTIPLIER
-: (`int`) The number of workers used in parallel processing. Default is the number of logical CPUs.
-
-## Configure with environment variables
-
-Configuration key-values can be defined through operating system environment variables.
-
-For example, the following command will effectively set a website's title on Unix-like systems:
-
-```txt
-$ env HUGO_TITLE="Some Title" hugo
-```
-
-This 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.
-
-{{% note %}}
-Names must be prefixed with `HUGO_` and the configuration key must be set in uppercase when setting operating system environment variables.
-
-To set configuration parameters, prefix the name with `HUGO_PARAMS_`
-{{% /note %}}
-
-If you are using snake_cased variable names, the above will not work. 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.
-
-## Ignore content and data files when rendering
-
-{{% note %}}
-This works, but we recommend you use the newer and more powerful [includeFiles and excludeFiles](/hugo-modules/configuration/#module-configuration-mounts) mount options.
-{{% /note %}}
-
-To exclude specific files from the `content`, `data`, and `i18n` directories when rendering your site, set `ignoreFiles` to one or more regular expressions to match against the absolute file path.
-
-To ignore files ending with `.foo` or `.boo`:
-
-{{< code-toggle file=hugo >}}
-ignoreFiles = ['\.foo$', '\.boo$']
-{{< /code-toggle >}}
-
-To ignore a file using the absolute file path:
-
-{{< code-toggle file=hugo >}}
-ignoreFiles = ['^/home/user/project/content/test\.md$']
-{{< /code-toggle >}}
-
-## Configure front matter
-
-### Configure dates
-
-Dates 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 `hugo.toml`.
-
-The default configuration is:
-
-{{< code-toggle config=frontmatter />}}
-
-If you, as an example, have a non-standard date parameter in some of your content, you can override the setting for `date`:
-
-{{< code-toggle file=hugo >}}
-[frontmatter]
-date = ["myDate", ":default"]
-{{< /code-toggle >}}
-
-The `: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.
-
-In 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`.
-
-The special date handlers are:
-
-`:fileModTime`
-: Fetches the date from the content file's last modification timestamp.
-
-An example:
-
-{{< code-toggle file=hugo >}}
-[frontmatter]
-lastmod = ["lastmod", ":fileModTime", ":default"]
-{{< /code-toggle >}}
-
-The 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`.
-
-`:filename`
-: Fetches the date from the content file's file name. 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`.
-
-An example:
-
-{{< code-toggle file=hugo >}}
-[frontmatter]
-date  = [":filename", ":default"]
-{{< /code-toggle >}}
-
-The above will try first to extract the value for `.Date` from the file name, then it will look in front matter parameters `date`, `publishDate` and lastly `lastmod`.
-
-`:git`
-: 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 configuration.
-
-## Configure minify
-
-See the [tdewolff/minify] project page for details.
-
-[tdewolff/minify]: https://github.com/tdewolff/minify
-
-Default configuration:
-
-{{< code-toggle config=minify />}}
-
-## Configure file caches
-
-Since Hugo 0.52 you can configure more than just the `cacheDir`. This is the default configuration:
-
-{{< code-toggle config=caches />}}
-
-You can override any of these cache settings in your own `hugo.toml`.
-
-### The keywords explained
-
-cacheDir
-: (`string`) See [Configure cacheDir](#configure-cachedir).
-
-project
-: (`string`) 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.
-
-resourceDir
-: (`string`) This is the value of the `resourceDir` configuration option.
-
-maxAge
-: (`string`) 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).
-
-dir
-: (`string`) The absolute path to where the files for this cache will be stored. Allowed starting placeholders are `:cacheDir` and `:resourceDir` (see above).
-
-## Configure cacheDir
-
-This is the directory where Hugo by default will store its file caches. See [Configure File Caches](#configure-file-caches).
-
-This can be set using the `cacheDir` config option or via the OS environment variable `HUGO_CACHEDIR`.
-
-If this is not set, Hugo will use, in order of preference:
-
-1. If running on Netlify: `/opt/build/cache/hugo_cache/`. 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).
-1. In a `hugo_cache` directory below the OS user cache directory as defined by Go's [os.UserCacheDir](https://pkg.go.dev/os#UserCacheDir). On Unix systems, this is `$XDG_CACHE_HOME` as specified by [basedir-spec-latest](https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html) if non-empty, else `$HOME/.cache`. On MacOS, this is `$HOME/Library/Caches`. On Windows, this is`%LocalAppData%`. On Plan 9, this is `$home/lib/cache`. {{< new-in 0.116.0 />}}
-1. In a  `hugo_cache_$USER` directory below the OS temp dir.
-
-If you want to know the current value of `cacheDir`, you can run `hugo config`, e.g: `hugo config | grep cachedir`.
-
-[`.Site.Params`]: /method/site/params/
-[directory structure]: /getting-started/directory-structure/
-[lookup order]: /templates/lookup-order/
-[custom output formats]: /templates/output-formats/
-[templates]: /templates/
-[static-files]: /content-management/static-files/
-
-## Configure HTTP cache
-
-{{< new-in 0.127.0 />}}
-
-Note that this configuration is currently only relevant when using the [resources.GetRemote] function.
-
-The caching in Hugo is layered:
-
-```goat {.w-40}
- .-----------.
-|  dynacache  |
- '-----+-----'
-       |
-       v
- .----------.
-| HTTP cache |
- '-----+----'
-       |
-       v
- .----------.
-| file cache |
- '-----+----'
-```
-
-Dynacache
-: A in memory LRU cache that gets evicted on changes, [Cache Buster](/getting-started/configuration-build/#configure-cache-busters) matches and in low memory situations.
-
-HTTP Cache
-: Enables HTTP cache behavior (RFC 9111) for remote resources. This works best for resources with properly set up HTTP cache headers. The HTTP cache uses the [file cache] to store and serve cached resources.
-
-File Cache
-: See [file cache].
-
-The default HTTP cache disables everything:
-
-{{< code-toggle config=HTTPCache />}}
-
-caching
-: Enabled RFC 9111 cache behavior _for_ a configured set of resources. Stale resources will be refreshed from the [file cache] even if their configured TTL isn't reached.
-
-polling
-: Enables polling _for_ a set of resources. Note that you can enable polling for resources even if HTTP caching is disabled. This setting is only used when in watch mode (e.g. `hugo server`). When a changed resource is detected, that change triggers a rebuild of pages using that resource.
-
-[resources.GetRemote]: /functions/resources/getremote/
-[file cache]: #configure-file-caches
-
-## Configure segments
-
-{{< new-in 0.124.0 />}}
-
-{{% note %}}
-The `segments` configuration is currently only used to configure partitioned rendering.
-This feature is only about what gets rendered when, Hugo's entire object graph (sites and pages) is
-always available.
-{{% /note %}}
-
-* Each segment consists of zero or more `exclude` filters and zero or more `include` filters.
-* Each filter consists of one or more field Glob matchers.
-* Each filter in a section (`exclude` or `include`) is ORed together, each matcher in a filter is ANDed together.
-
-The fields that can be used in the filters are:
-
-path
-: The logical page [path].
-
-lang
-: The [page language].
-
-kind
-: The [kind](g) of the page.
-
-output
-: The [output format](g) of the page.
-
-It is recommended to put coarse grained filters (e.g. for language and output format) in the excludes section, e.g.:
-
-{{< code-toggle file=hugo >}}
-[segments.segment1]
-  [[segments.segment1.excludes]]
-    lang = "n*"
-  [[segments.segment1.excludes]]
-    lang   = "en"
-    output = "rss"
-  [[segments.segment1.includes]]
-    kind = "{home,term,taxonomy}"
-  [[segments.segment1.includes]]
-    path = "{/docs,/docs/**}"
-{{< /code-toggle >}}
-
-With the above you can render only the pages in `segment1` by configuring the [renderSegments](#rendersegments) or setting the `--renderSegments` flag:
-
-```bash
-hugo --renderSegments segment1
-```
-
-Multiple segments can be configured, and the `--renderSegments` flag can take a comma separated list of segments.
-
-Some use cases for this feature:
-
-* Splitting builds of big sites.
-* Enable faster builds during development by only rendering a subset of the site.
-* Partial rebuilds, e.g. render the home page and the "news section" every hour, render the entire site once a week.
-* Render only e.g. the JSON output format to push to e.g. a search index.
-  
-[path]: /methods/page/path/
-[page language]: /methods/page/language/
diff --git a/docs/content/en/getting-started/directory-structure.md b/docs/content/en/getting-started/directory-structure.md
index ce1df600f..3feecd135 100644
--- a/docs/content/en/getting-started/directory-structure.md
+++ b/docs/content/en/getting-started/directory-structure.md
@@ -1,17 +1,14 @@
 ---
 title: Directory structure
-description: Each Hugo project is a directory, with subdirectories that contribute to the content, structure, behavior, and presentation of your site.
-categories: [getting started,fundamentals]
-keywords: [source, organization, directories]
-menu:
-  docs:
-    parent: getting-started
-    weight: 40
-weight: 40
-toc: true
+description: An overview of Hugo's directory structure.
+categories: []
+keywords: []
+weight: 30
 aliases: [/overview/source-directory/]
 ---
 
+Each Hugo project is a directory, with subdirectories that contribute to the content, structure, behavior, and presentation of your site.
+
 ## Site skeleton
 
 Hugo generates a project skeleton when you create a new site. For example, this command:
@@ -78,49 +75,38 @@ my-site/
 
 Each of the subdirectories contributes to the content, structure, behavior, or presentation of your site.
 
-###### archetypes
-
-The `archetypes` directory contains templates for new content. See&nbsp;[details](/content-management/archetypes/).
-
-###### assets
-
-The `assets` directory contains global resources typically passed through an asset pipeline. This includes resources such as images, CSS, Sass, JavaScript, and TypeScript. See&nbsp;[details](/hugo-pipes/introduction/).
-
-###### config
-
-The `config` directory contains your site configuration, possibly split into multiple subdirectories and files. For projects with minimal configuration or projects that do not need to behave differently in different environments, a single configuration file named `hugo.toml` in the root of the project is sufficient. See&nbsp;[details](/getting-started/configuration/#configuration-directory).
-
-###### content
+archetypes
+: The `archetypes` directory contains templates for new content. See&nbsp;[details](/content-management/archetypes/).
 
-The `content` directory contains the markup files (typically Markdown) and page resources that comprise the content of your site. See&nbsp;[details](/content-management/organization/).
+assets
+: The `assets` directory contains global resources typically passed through an asset pipeline. This includes resources such as images, CSS, Sass, JavaScript, and TypeScript. See&nbsp;[details](/hugo-pipes/introduction/).
 
-###### data
+config
+: The `config` directory contains your site configuration, possibly split into multiple subdirectories and files. For projects with minimal configuration or projects that do not need to behave differently in different environments, a single configuration file named `hugo.toml` in the root of the project is sufficient. See&nbsp;[details](/configuration/introduction/#configuration-directory).
 
-The `data` directory contains data files (JSON, TOML, YAML, or XML) that augment content, configuration, localization, and navigation. See&nbsp;[details](/content-management/data-sources/).
+content
+: The `content` directory contains the markup files (typically Markdown) and page resources that comprise the content of your site. See&nbsp;[details](/content-management/organization/).
 
-###### i18n
+data
+: The `data` directory contains data files (JSON, TOML, YAML, or XML) that augment content, configuration, localization, and navigation. See&nbsp;[details](/content-management/data-sources/).
 
-The `i18n` directory contains translation tables for multilingual sites. See&nbsp;[details](/content-management/multilingual/).
+i18n
+: The `i18n` directory contains translation tables for multilingual sites. See&nbsp;[details](/content-management/multilingual/).
 
-###### layouts
+layouts
+: The `layouts` directory contains templates to transform content, data, and resources into a complete website. See&nbsp;[details](/templates/).
 
-The `layouts` directory contains templates to transform content, data, and resources into a complete website. See&nbsp;[details](/templates/).
+public
+: The `public` directory contains the published website, generated when you run the `hugo` or `hugo server` commands. Hugo recreates this directory and its content as needed. See&nbsp;[details](/getting-started/usage/#build-your-site).
 
-###### public
+resources
+: The `resources` directory contains cached output from Hugo's asset pipelines, generated when you run the `hugo` or `hugo server` commands. By default this cache directory includes CSS and images. Hugo recreates this directory and its content as needed.
 
-The `public` directory contains the published website, generated when you run the `hugo` or `hugo server` commands. Hugo recreates this directory and its content as needed. See&nbsp;[details](/getting-started/usage/#build-your-site).
+static
+: The `static` directory contains files that will be copied to the `public` directory when you build your site. For example: `favicon.ico`, `robots.txt`, and files that verify site ownership. Before the introduction of [page bundles](g) and [asset pipelines](/hugo-pipes/introduction/), the `static` directory was also used for images, CSS, and JavaScript.
 
-###### resources
-
-The `resources` directory contains cached output from Hugo's asset pipelines, generated when you run the `hugo` or `hugo server` commands. By default this cache directory includes CSS and images. Hugo recreates this directory and its content as needed.
-
-###### static
-
-The `static` directory contains files that will be copied to the `public` directory when you build your site. For example: `favicon.ico`, `robots.txt`, and files that verify site ownership. Before the introduction of [page bundles](g) and [asset pipelines](/hugo-pipes/introduction/), the `static` directory was also used for images, CSS, and JavaScript.
-
-###### themes
-
-The `themes` directory contains one or more [themes](g), each in its own subdirectory.
+themes
+: The `themes` directory contains one or more [themes](g), each in its own subdirectory.
 
 ## Union file system
 
@@ -158,11 +144,10 @@ source = '/home/user/shared-content'
 target = 'content'
 {{< /code-toggle >}}
 
-{{% note %}}
-When you overlay one directory on top of another, you must mount both directories.
-
-Hugo does not follow symbolic links. If you need the functionality provided by symbolic links, use Hugo's union file system instead.
-{{% /note %}}
+> [!note]
+> When you overlay one directory on top of another, you must mount both directories.
+>
+> Hugo does not follow symbolic links. If you need the functionality provided by symbolic links, use Hugo's union file system instead.
 
 After mounting, the union file system has this structure:
 
@@ -185,11 +170,10 @@ home/
         └── hugo.toml
 ```
 
-{{% note %}}
-When two or more files have the same path, the order of precedence follows the order of the mounts. For example, if the shared content directory contains `books/book-1.md`, it will be ignored because the project's `content` directory was mounted first.
-{{% /note %}}
+> [!note]
+> When two or more files have the same path, the order of precedence follows the order of the mounts. For example, if the shared content directory contains `books/book-1.md`, it will be ignored because the project's `content` directory was mounted first.
 
-You can mount directories to `archetypes`, `assets`, `content`, `data`, `i18n`, `layouts`, and `static`. See&nbsp;[details](/hugo-modules/configuration/#module-configuration-mounts).
+You can mount directories to `archetypes`, `assets`, `content`, `data`, `i18n`, `layouts`, and `static`. See&nbsp;[details](/configuration/module/#mounts).
 
 You can also mount directories from Git repositories using Hugo Modules. See&nbsp;[details](/hugo-modules/).
 
diff --git a/docs/content/en/getting-started/external-learning-resources/index.md b/docs/content/en/getting-started/external-learning-resources/index.md
index 80805d4a6..7838b6810 100644
--- a/docs/content/en/getting-started/external-learning-resources/index.md
+++ b/docs/content/en/getting-started/external-learning-resources/index.md
@@ -2,19 +2,14 @@
 title: External learning resources
 linkTitle: External resources
 description: Use these third-party resources to learn Hugo.
-categories: [getting started]
-keywords: [books, tutorials, learning, usage]
-menu:
-  docs:
-    parent: getting-started
-    weight: 90
-weight: 90
-toc: true
+categories: []
+keywords: []
+weight: 40
 ---
 
 ## Books
 
-### Hugo In Action
+### Hugo in Action
 
 Hugo in Action is a step-by-step guide to using Hugo to create static websites. Working with a complete example website and source code samples, you'll learn how to build and host a low-maintenance, high-performance site that will wow your users and stay stable without relying on a third-party server.
 
@@ -28,7 +23,7 @@ ISBN: 9781617297007
 
 ### Build Websites with Hugo
 
-In this book, you'll use Hugo to build a personal portfolio site that you can use to showcase your skills and thoughts to the world. You'll build the basic skeleton, develop a custom theme, and use content templates to generate new pages quickly. You'll use internal and external data sources to embed content into your site, and render some of your content in JSON and RSS. You'll add a blog section with posts and integrate Disqus with your site, and then make your site searchable.
+In this book, you'll use Hugo to build a personal portfolio site that you can use to showcase your skills and thoughts to the world. You'll build the basic skeleton, develop a custom theme, and use content templates to generate new pages quickly. You'll use internal and external data sources to embed content into your site and render some of your content in JSON and RSS. You'll add a blog section with posts and integrate Disqus with your site, and then make your site searchable.
 
 [{{< img src="build-websites-with-hugo.png" alt="Book cover: Build Websites with Hugo" filter="process" filterArgs="resize x350 webp">}}](https://pragprog.com/titles/bhhugo/build-websites-with-hugo/)
 
@@ -42,7 +37,7 @@ ISBN: 9781680507263
 
 ### Hugo Beginner Tutorial Series
 
-Welcome to this introduction to Hugo tutorial. The goal of this series is to take you from a lion cub with basic web design knowledge to creating your first Hugo website. In this series you’ll learn how to set up a Hugo site, the basics of usingHugo layouts, partials, and templating, set up a blog, and finally use data files. By the end of this series you’ll have the foundational knowledge to build your own Hugo sites.
+Welcome to this introduction to Hugo tutorial. This series aims to take you from a lion cub with basic web design knowledge to creating your first Hugo website. In this series, you'll learn how to set up a Hugo site, the basics of using Hugo layouts, partials, and templating, set up a blog, and finally, use data files. By the end of this series, you'll have the foundational knowledge to build your own Hugo sites.
 
 1. [Getting set up in Hugo](https://cloudcannon.com/tutorials/hugo-beginner-tutorial/)
 1. [Layouts in Hugo](https://cloudcannon.com/tutorials/hugo-beginner-tutorial/layouts-in-hugo/)
@@ -55,9 +50,9 @@ Creator: Mike Neumegen\
 Affiliation: [CloudCannon](https://cloudcannon.com/)\
 Creation date: April 2022
 
-#### Hugo Static Site Generator
+### Hugo Static Site Generator
 
-This course covers the basics of using the Hugo static site generator. Work your way through the articles and we'll teach you everything you need to know to create a professional and scalable website or blog!
+This course covers the basics of using the Hugo static site generator. Work your way through the articles, and we'll teach you everything you need to know to create a professional and scalable website or blog!
 
 1. [Introduction](https://www.giraffeacademy.com/static-site-generators/hugo/)
 1. [Windows Installation](https://www.giraffeacademy.com/static-site-generators/hugo/installing-hugo-on-windows/)
diff --git a/docs/content/en/getting-started/quick-start.md b/docs/content/en/getting-started/quick-start.md
index cb22e0121..dfb78f42e 100644
--- a/docs/content/en/getting-started/quick-start.md
+++ b/docs/content/en/getting-started/quick-start.md
@@ -1,16 +1,12 @@
 ---
 title: Quick start
-description: Learn to create a Hugo site in minutes.
-categories: [getting started]
-keywords: [quick start,usage]
-menu:
-  docs:
-    parent: getting-started
-    weight: 20
-weight: 20
-toc: true
+description: Create a Hugo site in minutes.
+categories: []
+keywords: []
+params:
+  minVersion: v0.128.0
+weight: 10
 aliases: [/quickstart/,/overview/quickstart/]
-minVersion: v0.128.0
 ---
 
 In this tutorial you will:
@@ -33,18 +29,14 @@ You must also be comfortable working from the command line.
 
 ### Commands
 
-{{% note %}}
-**If you are a Windows user:**
-
-- Do not use the Command Prompt
-- Do not use Windows PowerShell
-- Run these commands from [PowerShell] or a Linux terminal such as WSL or Git Bash
-
-PowerShell and Windows PowerShell [are different applications].
-
-[PowerShell]: https://learn.microsoft.com/en-us/powershell/scripting/install/installing-powershell-on-windows
-[are different applications]: https://learn.microsoft.com/en-us/powershell/scripting/whats-new/differences-from-windows-powershell?view=powershell-7.3
-{{% /note %}}
+> [!note]
+> **If you are a Windows user:**
+>
+> - Do not use the Command Prompt
+> - Do not use Windows PowerShell
+> - Run these commands from [PowerShell] or a Linux terminal such as WSL or Git > Bash
+>
+> PowerShell and Windows PowerShell [are different applications].
 
 Verify that you have installed Hugo {{% param "minVersion" %}} or later.
 
@@ -127,8 +119,6 @@ Notice the `draft` value in the [front matter] is `true`. By default, Hugo does
 
 Add some [Markdown] to the body of the post, but do not change the `draft` value.
 
-[markdown]: https://commonmark.org/help/
-
 ```text
 +++
 title = 'My First Post'
@@ -142,7 +132,7 @@ This is **bold** text, and this is *emphasized* text.
 Visit the [Hugo](https://gohugo.io) website!
 ```
 
-Save the file, then start Hugo’s development server to view the site. You can run either of the following commands to include draft content.
+Save the file, then start Hugo's development server to view the site. You can run either of the following commands to include draft content.
 
 ```text
 hugo server --buildDrafts
@@ -153,12 +143,8 @@ View your site at the URL displayed in your terminal. Keep the development serve
 
 When satisfied with your new content, set the front matter `draft` parameter to `false`.
 
-{{% note %}}
-Hugo's rendering engine conforms to the CommonMark [specification] for Markdown. The CommonMark organization provides a useful [live testing tool] powered by the reference implementation.
-
-[live testing tool]: https://spec.commonmark.org/dingus/
-[specification]: https://spec.commonmark.org/
-{{% /note %}}
+> [!note]
+> Hugo's rendering engine conforms to the CommonMark [specification] for Markdown. The CommonMark organization provides a useful [live testing tool] powered by the reference implementation.
 
 ## Configure the site
 
@@ -183,15 +169,10 @@ Start Hugo's development server to see your changes, remembering to include draf
 hugo server -D
 ```
 
-{{% note %}}
-Most theme authors provide configuration guidelines and options. Make sure to visit your theme's repository or documentation site for details.
-
-[The New Dynamic], authors of the Ananke theme, provide [documentation] for configuration and usage. They also provide a [demonstration site].
-
-[demonstration site]: https://gohugo-ananke-theme-demo.netlify.app/
-[documentation]: https://github.com/theNewDynamic/gohugo-theme-ananke#readme
-[The New Dynamic]: https://www.thenewdynamic.com/
-{{% /note %}}
+> [!note]
+> Most theme authors provide configuration guidelines and options. Make sure to visit your theme's repository or documentation site for details.
+>
+> [The New Dynamic], authors of the Ananke theme, provide [documentation] for configuration and usage. They also provide a [demonstration site].
 
 ## Publish the site
 
@@ -205,7 +186,7 @@ When you publish your site, you typically do _not_ want to include [draft, futur
 hugo
 ```
 
-To learn how to _deploy_ your site, see the [hosting and deployment] section.
+To learn how to _deploy_ your site, see the [host and deploy] section.
 
 ## Ask for help
 
@@ -216,17 +197,22 @@ Hugo's [forum] is an active community of users and developers who answer questio
 For other resources to help you learn Hugo, including books and video tutorials, see the [external learning resources](/getting-started/external-learning-resources/) page.
 
 [Ananke]: https://github.com/theNewDynamic/gohugo-theme-ananke
+[are different applications]: https://learn.microsoft.com/en-us/powershell/scripting/whats-new/differences-from-windows-powershell?view=powershell-7.3
+[demonstration site]: https://gohugo-ananke-theme-demo.netlify.app/
 [directory structure]: /getting-started/directory-structure/
+[documentation]: https://github.com/theNewDynamic/gohugo-theme-ananke#readme
 [draft, future, and expired content]: /getting-started/usage/#draft-future-and-expired-content
 [draft, future, or expired content]: /getting-started/usage/#draft-future-and-expired-content
-[external learning resources]:/getting-started/external-learning-resources/
-[forum]: https://discourse.gohugo.io/
 [forum]: https://discourse.gohugo.io/
 [front matter]: /content-management/front-matter/
 [Git submodule]: https://git-scm.com/book/en/v2/Git-Tools-Submodules
-[hosting and deployment]: /hosting-and-deployment/
+[host and deploy]: /host-and-deploy/
 [Install Git]: https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
 [Install Hugo]: /installation/
-[Requesting Help]: https://discourse.gohugo.io/t/requesting-help/9132
-[Requesting Help]: https://discourse.gohugo.io/t/requesting-help/9132
-[site configuration]: /getting-started/configuration/
+[live testing tool]: https://spec.commonmark.org/dingus/
+[Markdown]: https://daringfireball.net/projects/markdown
+[PowerShell]: https://learn.microsoft.com/en-us/powershell/scripting/install/installing-powershell-on-windows
+[requesting help]: https://discourse.gohugo.io/t/requesting-help/9132
+[site configuration]: /configuration/
+[specification]: https://spec.commonmark.org/
+[The New Dynamic]: https://www.thenewdynamic.com/
diff --git a/docs/content/en/getting-started/usage.md b/docs/content/en/getting-started/usage.md
index 3380b0ff2..d6bc42550 100644
--- a/docs/content/en/getting-started/usage.md
+++ b/docs/content/en/getting-started/usage.md
@@ -1,14 +1,9 @@
 ---
 title: Basic usage
-description: Hugo's command line interface (CLI) is fully featured but simple to use, even for those with limited experience working from the command line.
-categories: [getting started]
-keywords: [usage,livereload,command,flags]
-menu:
-  docs:
-    parent: getting-started
-    weight: 30
-weight: 30
-toc: true
+description: Use the command-line interface (CLI) to perform basic tasks.
+categories: []
+keywords: []
+weight: 20
 aliases: [/overview/usage/,/extras/livereload/,/doc/usage/,/usage/]
 ---
 
@@ -50,11 +45,10 @@ hugo
 
 The [`hugo`] command builds your site, publishing the files to the `public` directory. To publish your site to a different directory, use the [`--destination`] flag or set [`publishDir`] in your site configuration.
 
-{{% note %}}
-Hugo does not clear the `public` directory before building your site. Existing files are overwritten, but not deleted. This behavior is intentional to prevent the inadvertent removal of files that you may have added to the `public` directory after the build.
-
-Depending on your needs, you may wish to manually clear the contents of the `public` directory before every build.
-{{% /note %}}
+> [!note]
+> Hugo does not clear the `public` directory before building your site. Existing files are overwritten, but not deleted. This behavior is intentional to prevent the inadvertent removal of files that you may have added to the `public` directory after the build.
+>
+> Depending on your needs, you may wish to manually clear the contents of the `public` directory before every build.
 
 ## Draft, future, and expired content
 
@@ -67,12 +61,8 @@ Hugo allows you to set `draft`, `date`, `publishDate`, and `expiryDate` in the [
 
 {{< new-in 0.123.0 />}}
 
-{{% note %}}
-Hugo publishes descendants of draft, future, and expired [node](g) pages. To prevent publication of these descendants, use the [`cascade`] front matter field to cascade [build options] to the descendant pages.
-
-[build options]: /content-management/build-options/
-[`cascade`]: /content-management/front-matter/#cascade-field
-{{% /note %}}
+> [!note]
+> Hugo publishes descendants of draft, future, and expired [node](g) pages. To prevent publication of these descendants, use the [`cascade`] front matter field to cascade [build options] to the descendant pages.
 
 You can override the default behavior when running `hugo` or `hugo server` with command line flags:
 
@@ -84,11 +74,10 @@ hugo --buildFuture    # or -F
 
 Although you can also set these values in your site configuration, it can lead to unwanted results unless all content authors are aware of, and understand, the settings.
 
-{{% note %}}
-As noted above, Hugo does not clear the `public` directory before building your site. Depending on the _current_ evaluation of the four conditions above, after the build your `public` directory may contain extraneous files from a previous build.
-
-A common practice is to manually clear the contents of the `public` directory before each build to remove draft, expired, and future content.
-{{% /note %}}
+> [!note]
+> As noted above, Hugo does not clear the `public` directory before building your site. Depending on the _current_ evaluation of the four conditions above, after the build your `public` directory may contain extraneous files from a previous build.
+>
+> A common practice is to manually clear the contents of the `public` directory before each build to remove draft, expired, and future content.
 
 ## Develop and test your site
 
@@ -122,9 +111,8 @@ hugo server --navigateToChanged
 
 ## Deploy your site
 
-{{% note %}}
-As noted above, Hugo does not clear the `public` directory before building your site. Manually clear the contents of the `public` directory before each build to remove draft, expired, and future content.
-{{% /note %}}
+> [!note]
+> As noted above, Hugo does not clear the `public` directory before building your site. Manually clear the contents of the `public` directory before each build to remove draft, expired, and future content.
 
 When you are ready to deploy your site, run:
 
@@ -154,25 +142,25 @@ public/
 
 In a simple hosting environment, where you typically `ftp`, `rsync`, or `scp` your files to the root of a virtual host, the contents of the `public` directory are all that you need.
 
-Most of our users deploy their sites using a CI/CD workflow, where a push[^1] to their GitHub or GitLab repository triggers a build and deployment. Popular providers include [AWS Amplify], [CloudCannon], [Cloudflare Pages], [GitHub Pages], [GitLab Pages], and [Netlify].
+Most of our users deploy their sites using a [CI/CD](g) workflow, where a push[^1] to their GitHub or GitLab repository triggers a build and deployment. Popular providers include [AWS Amplify], [CloudCannon], [Cloudflare Pages], [GitHub Pages], [GitLab Pages], and [Netlify].
 
-Learn more in the [hosting and deployment] section.
+Learn more in the [host and deploy] section.
 
 [^1]: The Git repository contains the entire project directory, typically excluding the `public` directory because the site is built _after_ the push.
 
 [`--destination`]: /commands/hugo/#options
+[`cascade`]: /content-management/front-matter/#cascade
 [`hugo server`]: /commands/hugo_server/
 [`hugo`]: /commands/hugo/
-[`publishDir`]: /getting-started/configuration/#publishdir
+[`publishDir`]: /configuration/all/#publishdir
 [AWS Amplify]: https://aws.amazon.com/amplify/
+[build options]: /content-management/build-options/
 [CloudCannon]: https://cloudcannon.com/
 [Cloudflare Pages]: https://pages.cloudflare.com/
-[commands]: /commands/
 [front matter]: /content-management/front-matter/
 [GitHub Pages]: https://pages.github.com/
 [GitLab Pages]: https://docs.gitlab.com/ee/user/project/pages/
-[hosting and deployment]: /hosting-and-deployment/
-[hosting]: /hosting-and-deployment/
+[host and deploy]: /host-and-deploy/
 [installing]: /installation/
 [LiveReload]: https://github.com/livereload/livereload-js
 [Netlify]: https://www.netlify.com/
author	Bjørn Erik Pedersen <bjorn.erik.pedersen@gmail.com>	2025-04-10 13:04:51 +0200
committer	Bjørn Erik Pedersen <bjorn.erik.pedersen@gmail.com>	2025-04-10 13:04:51 +0200
commit	653f1c1d462332bccf303a5040e5cd99c89a4378 (patch)
tree	c993984f169a240567526e9993261241c0cda771 /docs/content/en/getting-started
parent	208a0de6c31354df6f9463d49e90db9dec935169 (diff)
parent	5be51ac3db225d5df501ed1fa1499c41d97dbf65 (diff)
download	hugo-653f1c1d462332bccf303a5040e5cd99c89a4378.tar.gz hugo-653f1c1d462332bccf303a5040e5cd99c89a4378.zip