docs: Prepare for new sub tree

See #11925

9 files changed, 0 insertions, 2065 deletions

diff --git a/docs/content/en/getting-started/_index.md b/docs/content/en/getting-started/_index.md
deleted file mode 100644
index 780b96a62..000000000
--- a/docs/content/en/getting-started/_index.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: Getting started
-linkTitle: Overview
-description: Quick start and guides for installing Hugo on your preferred operating system.
-categories: []
-keywords: []
-menu:
-  docs:
-    identifier: getting-started-overview
-    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-markup.md b/docs/content/en/getting-started/configuration-markup.md
deleted file mode 100644
index 607301d3a..000000000
--- a/docs/content/en/getting-started/configuration-markup.md
+++ /dev/null
@@ -1,218 +0,0 @@
----
-title: Configure markup
-description: Configure rendering of markup to HTML.
-categories: [getting started,fundamentals]
-keywords: [configuration,highlighting]
-menu:
-  docs:
-    parent: getting-started
-    weight: 50
-weight: 50
-slug: configuration-markup
-toc: true
----
-
-## Default handler
-
-By default, Hugo uses [Goldmark] to render markdown to HTML.
-
-{{< code-toggle file=hugo >}}
-[markup]
-defaultMarkdownHandler = 'goldmark'
-{{< /code-toggle >}}
-
-Files with the `.md` 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 alternate 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/#list-of-content-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-model/#security-policy
-
-## Goldmark
-
-This is the default configuration for the Goldmark markdown renderer:
-
-{{< code-toggle config=markup.goldmark />}}
-
-For details on the extensions, refer to the [Goldmark documentation](https://github.com/yuin/goldmark/#built-in-extensions).
-
-Some settings explained:
-
-hardWraps
-: By default, Goldmark ignores newlines within a paragraph. Set to `true` to render newlines as `<br>` elements.
-
-unsafe
-: By default, Goldmark does not render raw HTML and potentially dangerous links. If you have lots of inline HTML and/or JavaScript, you may need to turn this on.
-
-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
-
-attribute
-: Enable custom attribute support for titles and blocks by adding attribute lists inside single curly brackets (`{.myclass class="class1 class2" }`) and placing it _after the Markdown element it decorates_, on the same line for titles and on a new line directly below for blocks.
-
-Hugo supports adding attributes (e.g. CSS classes) to Markdown blocks, e.g. tables, lists, paragraphs etc.
-
-A blockquote with a CSS class:
-
-```md
-> foo
-> bar
-{.myclass}
-```
-
-There are some current limitations: For tables you can currently only apply it to the full table, and for lists the `ul`/`ol`-nodes only, e.g.:
-
-```md
-* Fruit
-  * Apple
-  * Orange
-  * Banana
-  {.fruits}
-* Dairy
-  * Milk
-  * Cheese
-  {.dairies}
-{.list}
-```
-
-Note that attributes in [code fences](/content-management/syntax-highlighting/#highlighting-in-code-fences) must come after the opening tag, with any other highlighting processing instruction, e.g.:
-
-````txt
-```go {.myclass linenos=table,hl_lines=[8,"15-17"],linenostart=199}
-// ... code
-```
-````
-
-autoHeadingIDType ("github")
-: The strategy used for creating auto IDs (anchor names). Available types are `github`, `github-ascii` and `blackfriday`. `github` produces GitHub-compatible IDs, `github-ascii` will drop any non-ASCII characters after accent normalization, and `blackfriday` will make the IDs compatible with Blackfriday, the default Markdown engine before Hugo 0.60. Note that if Goldmark is your default Markdown engine, this is also the strategy used in the [anchorize](/functions/urls/anchorize) template func.
-
-## Asciidoc
-
-This is the default configuration for the AsciiDoc markdown renderer:
-
-{{< code-toggle config=markup.asciidocExt />}}
-
-attributes
-: (`map`) Variables to be referenced in your AsciiDoc file. This is a list of variable name/value maps. See Asciidoctor’s [attributes].
-
-[attributes]: https://asciidoctor.org/docs/asciidoc-syntax-quick-reference/#attributes-and-substitutions
-
-backend:
-: (`string`) Don’t change this unless you know what you are doing.
-
-extensions
-: (`[]string`) Possible extensions are `asciidoctor-html5s`, `asciidoctor-bibtex`, `asciidoctor-diagram`, `asciidoctor-interdoc-reftext`, `asciidoctor-katex`, `asciidoctor-latex`, `asciidoctor-mathematical`, and `asciidoctor-question`.
-
-failureLevel
-: (`string`) The minimum logging level that triggers a non-zero exit code (failure).
-
-noHeaderOrFooter
-: (`bool`) Output an embeddable document, which excludes the header, the footer, and everything outside the body of the document. Don’t change this unless you know what you are doing.
-
-preserveTOC
-: (`bool`) By default, Hugo removes the table of contents generated by Asciidoctor and provides it through the built-in variable `.TableOfContents` to enable further customization and better integration with the various Hugo themes. This option can be set to true to preserve Asciidoctor’s TOC in the generated page.
-
-safeMode
-: (`string`) Safe mode level `unsafe`, `safe`, `server`, or `secure`. Don’t change this unless you know what you are doing.
-
-sectionNumbers
-: (`bool`) Auto-number section titles.
-
-trace
-: (`bool`) Include backtrace information on errors.
-
-verbose
-: (`bool`) Verbosely print processing information and configuration file checks to stderr.
-
-workingFolderCurrent
-: (`bool`) Sets the working directory to be the same as that of the AsciiDoc file being processed, so that [include] will work with relative paths. This setting uses the asciidoctor cli parameter --base-dir and attribute outdir=. For rendering diagrams with [asciidoctor-diagram], `workingFolderCurrent` must be set to `true`.
-
-[asciidoctor-diagram]: https://asciidoctor.org/docs/asciidoctor-diagram/
-[include]: https://asciidoctor.org/docs/asciidoc-syntax-quick-reference/#include-files
-
-Notice that for security concerns only extensions that do not have path separators (either `\`, `/` or `.`) are allowed. That means that extensions can only be invoked if they are in the Ruby's `$LOAD_PATH` (ie. most likely, the extension has been installed by the user). Any extension declared relative to the website's path will not be accepted.
-
-Example of how to set extensions and attributes:
-
-```yml
-[markup.asciidocExt]
-    extensions = ["asciidoctor-html5s", "asciidoctor-diagram"]
-    workingFolderCurrent = true
-    [markup.asciidocExt.attributes]
-        my-base-url = "https://example.com/"
-        my-attribute-name = "my value"
-```
-
-In a complex Asciidoctor environment it is sometimes helpful to debug the exact call to your external helper with all
-parameters. Run Hugo with `-v`. You will get an output like
-
-```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
-
-{{< code-toggle config=markup.tableOfContents />}}
-
-These settings only works for the Goldmark renderer:
-
-startLevel
-: The heading level, values starting at 1 (`h1`), to start render the table of contents.
-
-endLevel
-: The heading level, inclusive, to stop render the table of contents.
-
-ordered
-: If `true`, generates an ordered list instead of an unordered list.
-
-## Render hooks
-
-See [Markdown Render Hooks](/templates/render-hooks/).
diff --git a/docs/content/en/getting-started/configuration.md b/docs/content/en/getting-started/configuration.md
deleted file mode 100644
index 3ce0077ba..000000000
--- a/docs/content/en/getting-started/configuration.md
+++ /dev/null
@@ -1,788 +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: 40
-weight: 40
-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], root configuration key, and language. For example:
-
-[environment]: /getting-started/glossary/#environment
-
-```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
-```
-
-The root configuration keys are `build`, `caches`, `cascade`, `deployment`, `frontmatter`, `imaging`, `languages`, `markup`, `mediatypes`, `menus`, `minify`, `module`, `outputformats`, `outputs`, `params`, `permalinks`, `privacy`, `related`, `security`, `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`.
-2. 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.
-
-2. `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.
-
-3. `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 publishdate in the future. Default is `false`.
-
-###### caches
-
-See [Configure File Caches](#configure-file-caches).
-
-###### cascade
-
-Pass 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).
-
-{{% note %}}
-For a website in a single language, define the `[[cascade]]` in [Front Matter](/content-management/front-matter#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 %}}
-
-###### canonifyURLs
-
-(`bool`) Enable to turn relative URLs into absolute.  Default is `false`. See&nbsp;[details](/content-management/urls/#canonical-urls).
-
-###### 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 %}}
-
-###### 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`.
-
-###### 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 slice`) Disable rendering of the specified page [kinds], any of `404`, `home`, `page`, `robotstxt`, `rss`, `section`, `sitemap`, `taxonomy`, or `term`.
-
-[kinds]: /getting-started/glossary/#page-kind
-
-###### 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`.
-
-###### 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`.
-
-###### 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 internal [RSS template](https://github.com/gohugoio/hugo/blob/master/tpl/tplimpl/embedded/templates/_default/rss.xml)
-- The `lang` attribute of the `<html>` element in the internal [alias template](https://github.com/gohugoio/hugo/blob/master/tpl/tplimpl/embedded/templates/alias.html)
-
-###### languages
-
-See [Configure Languages](/content-management/multilingual/#configure-languages).
-
-###### disableLanguages
-
-See [Disable a Language](/content-management/multilingual/#disable-a-language)
-
-###### 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.
-
-###### 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 [Configure Output Formats](#configure-additional-output-formats).
-
-###### paginate
-
-(`int`) Default number of elements per page in [pagination](/templates/pagination/). Default is `10`.
-
-###### paginatePath
-
-(`string`) The path element used during pagination (`https://example.org/page/2`). Default is `page`.
-
-###### permalinks
-
-See [Content Management](/content-management/urls/#permalinks).
-
-###### pluralizeListTitles
-
-(`bool`) Pluralize titles in lists. Default is `true`.
-
-###### publishDir
-
-(`string`) The directory to where Hugo will write the final static site (the HTML files etc.). Default is `public`.
-
-###### related
-
-See [Related Content](/content-management/related/#configure-related-content).
-
-###### relativeURLs
-
-(`bool`) Enable this to make all relative URLs relative to content root. Note that this does not affect absolute URLs.  Default is `false`. See&nbsp;[details](/content-management/urls/#relative-urls).
-
-###### 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.
-
-###### 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/
-```
-
-###### sectionPagesMenu
-
-See [Menus](/content-management/menus/#define-automatically).
-
-###### security
-
-See [Security Policy](/about/security-model/#security-policy).
-
-###### sitemap
-
-Default [sitemap configuration](/templates/sitemap-template/#configuration).
-
-###### summaryLength
-
-(`int`) The length of text in words to show in a [`.Summary`](/content-management/summaries/#automatic-summary-splitting). Default is `70`.
-
-###### taxonomies
-
-See [Configure Taxonomies](/content-management/taxonomies#configure-taxonomies).
-
-###### 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 (or location), e.g. `Europe/Oslo`, used to parse front matter dates without such information and in the [`time`] function. 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).
-
-###### title
-
-(`string`) Site title.
-
-###### titleCaseStyle
-
-(`string`) Default is `ap`. See [Configure Title Case](#configure-title-case).
-
-###### uglyURLs
-
-(`bool`) When enabled, creates URL of the form `/filename.html` instead of `/filename/`. Default is `false`.
-
-###### 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 build
-
-The `build` configuration section contains global build-related configuration options.
-
-{{< code-toggle config=build />}}
-
-buildStats {{< new-in 0.115.1 >}}
-: When enabled, 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]: /hugo-pipes/postprocess/#css-purging-with-postcss
-
-Exclude `class` attributes, `id` attributes, or tags from `hugo_stats.json` with the `disableClasses`, `disableIDs`, and `disableTags` keys.
-
-{{% note %}}
-With v0.115.0 and earlier this feature was enabled by setting `writeStats` to `true`. Although still functional, the `writeStats` key will be deprecated in a future release.
-
-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.
-
-cachebusters
-: See [Configure Cache Busters](#configure-cache-busters)
-
-noJSConfigInAssets
-: Turn off writing a `jsconfig.json` into your `/assets` folder 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.c