enableInlineShortcodes = false
- [exec]
- allow = ['^go$']
- osEnv = ['^PATH$']
-
[funcs]
getenv = ['^HUGO_', '^REPOSITORY_URL$', '^BRANCH$']
-D, --buildDrafts include content marked as draft
-E, --buildExpired include expired content
-F, --buildFuture include content with publishdate in the future
- --cacheDir string filesystem path to cache directory. Defaults: $TMPDIR/hugo_cache_$USER/
+ --cacheDir string filesystem path to cache directory
--cleanDestinationDir remove files from destination not found in static directories
--clock string set the clock used by Hugo, e.g. --clock 2021-11-06T22:30:00.00+09:00
--config string config file (default is hugo.yaml|json|toml)
### SEE ALSO
* [hugo completion](/commands/hugo_completion/) - Generate the autocompletion script for the specified shell
+
```
-b, --baseURL string hostname (and path) to the root, e.g. https://spf13.com/
- --cacheDir string filesystem path to cache directory. Defaults: $TMPDIR/hugo_cache_$USER/
+ --cacheDir string filesystem path to cache directory
-c, --contentDir string filesystem path to content directory
--format string preferred file format (toml, yaml or json) (default "toml")
-h, --help help for config
```
-b, --baseURL string hostname (and path) to the root, e.g. https://spf13.com/
- --cacheDir string filesystem path to cache directory. Defaults: $TMPDIR/hugo_cache_$USER/
+ --cacheDir string filesystem path to cache directory
-c, --contentDir string filesystem path to content directory
-h, --help help for mounts
-t, --theme strings themes to use (located in /themes/THEMENAME/)
```
--all clean entire module cache
-b, --baseURL string hostname (and path) to the root, e.g. https://spf13.com/
- --cacheDir string filesystem path to cache directory. Defaults: $TMPDIR/hugo_cache_$USER/
+ --cacheDir string filesystem path to cache directory
-c, --contentDir string filesystem path to content directory
-h, --help help for clean
--pattern string pattern matching module paths to clean (all if not set), e.g. "**hugo*"
```
-b, --baseURL string hostname (and path) to the root, e.g. https://spf13.com/
- --cacheDir string filesystem path to cache directory. Defaults: $TMPDIR/hugo_cache_$USER/
+ --cacheDir string filesystem path to cache directory
--clean delete module cache for dependencies that fail verification
-c, --contentDir string filesystem path to content directory
-h, --help help for graph
```
-b, --baseURL string hostname (and path) to the root, e.g. https://spf13.com/
- --cacheDir string filesystem path to cache directory. Defaults: $TMPDIR/hugo_cache_$USER/
+ --cacheDir string filesystem path to cache directory
-c, --contentDir string filesystem path to content directory
-h, --help help for init
-t, --theme strings themes to use (located in /themes/THEMENAME/)
```
-b, --baseURL string hostname (and path) to the root, e.g. https://spf13.com/
- --cacheDir string filesystem path to cache directory. Defaults: $TMPDIR/hugo_cache_$USER/
+ --cacheDir string filesystem path to cache directory
-c, --contentDir string filesystem path to content directory
-h, --help help for pack
-t, --theme strings themes to use (located in /themes/THEMENAME/)
```
-b, --baseURL string hostname (and path) to the root, e.g. https://spf13.com/
- --cacheDir string filesystem path to cache directory. Defaults: $TMPDIR/hugo_cache_$USER/
+ --cacheDir string filesystem path to cache directory
-c, --contentDir string filesystem path to content directory
-h, --help help for tidy
-t, --theme strings themes to use (located in /themes/THEMENAME/)
```
-b, --baseURL string hostname (and path) to the root, e.g. https://spf13.com/
- --cacheDir string filesystem path to cache directory. Defaults: $TMPDIR/hugo_cache_$USER/
+ --cacheDir string filesystem path to cache directory
-c, --contentDir string filesystem path to content directory
-h, --help help for vendor
-t, --theme strings themes to use (located in /themes/THEMENAME/)
```
-b, --baseURL string hostname (and path) to the root, e.g. https://spf13.com/
- --cacheDir string filesystem path to cache directory. Defaults: $TMPDIR/hugo_cache_$USER/
+ --cacheDir string filesystem path to cache directory
--clean delete module cache for dependencies that fail verification
-c, --contentDir string filesystem path to content directory
-h, --help help for verify
```
-b, --baseURL string hostname (and path) to the root, e.g. https://spf13.com/
- --cacheDir string filesystem path to cache directory. Defaults: $TMPDIR/hugo_cache_$USER/
+ --cacheDir string filesystem path to cache directory
-c, --contentDir string filesystem path to content directory
--editor string edit new content with this editor, if provided
-f, --force overwrite file if it already exists
-D, --buildDrafts include content marked as draft
-E, --buildExpired include expired content
-F, --buildFuture include content with publishdate in the future
- --cacheDir string filesystem path to cache directory. Defaults: $TMPDIR/hugo_cache_$USER/
+ --cacheDir string filesystem path to cache directory
--cleanDestinationDir remove files from destination not found in static directories
-c, --contentDir string filesystem path to content directory
--disableBrowserError do not show build errors in the browser
With this template code:
```go-html-template
-{{ 512.5032 | lang.FormatPercent 2 }} ---> 512.50%
+{{ 512.5032 | lang.FormatPercent 2 }} → 512.50%
```
The rendered page displays:
{{< code file="page-list-with-summaries.html" >}}
{{ range first 10 .Pages }}
-
<!-- this <div> includes the title summary -->
-
<h2><a href="{{ .RelPermalink }}">{{ .Title }}</a></h2>
- {{ .Summary }}
- </div>
- {{ if .Truncated }}
+ <article>
+ <!-- this <div> includes the title summary -->
+ <div>
+ <h2><a href="{{ .RelPermalink }}">{{ .Title }}</a></h2>
+ {{ .Summary }}
+ </div>
+ {{ if .Truncated }}
<!-- This <div> includes a read more link, but only if the summary is truncated... -->
<div>
<a href="{{ .RelPermalink }}">Read More…</a>
</div>
- {{ end }}
- </article>
+ {{ end }}
+ </article>
{{ end }}
{{< /code >}}
{{< code file="layout/_default/single.html" >}}
{{ define "main" }}
-<main>
+ <main>
<article>
- <header>
+ <header>
<h1>{{ .Title }}</h1>
- </header>
- {{ .Content }}
+ </header>
+ {{ .Content }}
</article>
<aside>
- {{ .TableOfContents }}
+ {{ .TableOfContents }}
</aside>
-</main>
+ </main>
{{ end }}
{{< /code >}}
```go-html-template
{{ $d := "2022-01-01" | time.AsTime }}
-{{ $d.AddDate 0 0 1 | time.Format "2006-01-02" }} --> 2022-01-02
-{{ $d.AddDate 0 1 1 | time.Format "2006-01-02" }} --> 2022-02-02
-{{ $d.AddDate 1 1 1 | time.Format "2006-01-02" }} --> 2023-02-02
+{{ $d.AddDate 0 0 1 | time.Format "2006-01-02" }} → 2022-01-02
+{{ $d.AddDate 0 1 1 | time.Format "2006-01-02" }} → 2022-02-02
+{{ $d.AddDate 1 1 1 | time.Format "2006-01-02" }} → 2023-02-02
-{{ $d.AddDate -1 -1 -1 | time.Format "2006-01-02" }} --> 2020-11-30
+{{ $d.AddDate -1 -1 -1 | time.Format "2006-01-02" }} → 2020-11-30
```
{{% note %}}
```go-html-template
{{ $d := "2023-01-31" | time.AsTime }}
-{{ $d.AddDate 0 1 0 | time.Format "2006-01-02" }} --> 2023-03-03
+{{ $d.AddDate 0 1 0 | time.Format "2006-01-02" }} → 2023-03-03
{{ $d := "2024-01-31" | time.AsTime }}
-{{ $d.AddDate 0 1 0 | time.Format "2006-01-02" }} --> 2024-03-02
+{{ $d.AddDate 0 1 0 | time.Format "2006-01-02" }} → 2024-03-02
{{ $d := "2024-02-29" | time.AsTime }}
-{{ $d.AddDate 1 0 0 | time.Format "2006-01-02" }} --> 2025-03-01
+{{ $d.AddDate 1 0 0 | time.Format "2006-01-02" }} → 2025-03-01
```
<h2>Featured Article</h2>
{{ range first 1 .Pages.ByPublishDate.Reverse }}
<header>
- <h3><a href="{{ . Permalink }}">{{ .Title }}</a></h3>
+ <h3><a href="{{ .Permalink }}">{{ .Title }}</a></h3>
</header>
<p>{{ .Description }}</p>
{{ end }}
Since the `defaultMarkdownHandler` and this template function use the same sanitizing logic, you can use the latter to determine the ID of a header for linking with anchor tags.
```go-html-template
-{{ anchorize "This is a header" }} --> "this-is-a-header"
-{{ anchorize "This is also a header" }} --> "this-is-also----a-header"
-{{ anchorize "main.go" }} --> "maingo"
-{{ anchorize "Article 123" }} --> "article-123"
-{{ anchorize "<- Let's try this, shall we?" }} --> "--lets-try-this-shall-we"
-{{ anchorize "Hello, 世界" }} --> "hello-世界"
+{{ anchorize "This is a header" }} → "this-is-a-header"
+{{ anchorize "This is also a header" }} → "this-is-also----a-header"
+{{ anchorize "main.go" }} → "maingo"
+{{ anchorize "Article 123" }} → "article-123"
+{{ anchorize "<- Let's try this, shall we?" }} → "--lets-try-this-shall-we"
+{{ anchorize "Hello, 世界" }} → "hello-世界"
```
{{ $s = $s | append (slice "d" "e") }}
```
+If a slice contains other slices, further slices will be appended as values:
+
+```go-html-template
+{{ $s := slice (slice "a" "b") (slice "c" "d") }}
+{{ $s = $s | append (slice "e" "f") (slice "g" "h") }}
+{{/* $s now contains a [][]string containing four slices: ["a" "b"], ["c" "d"], ["e" "f"], and ["g" "h"] */}}
+```
+
The `append` function works for all types, including `Pages`.
--- /dev/null
++++
+headless = true
++++
--- /dev/null
+When specifying the regular expression, use a raw [string literal] (backticks) instead of an interpreted string literal (double quotes) to simplify the syntax. With an interpreted string literal you must escape backslashes.
+
+Go's regular expression package implements the [RE2 syntax]. The RE2 syntax is a subset of that accepted by [PCRE], roughly speaking, and with various [caveats]. Note that the RE2 `\C` escape sequence is not supported.
+
+[caveats]: https://swtch.com/~rsc/regexp/regexp3.html#caveats
+[PCRE]: https://www.pcre.org/
+[RE2 syntax]: https://github.com/google/re2/wiki/Syntax/
+[string literal]: https://go.dev/ref/spec#String_literals
The function returns these values:
```go-html-template
-{{ os.FileExists "content" }} --> true
-{{ os.FileExists "content/news" }} --> true
-{{ os.FileExists "content/news/article-1" }} --> false
-{{ os.FileExists "content/news/article-1.md" }} --> true
-{{ os.FileExists "news" }} --> true
-{{ os.FileExists "news/article-1" }} --> false
-{{ os.FileExists "news/article-1.md" }} --> true
+{{ os.FileExists "content" }} → true
+{{ os.FileExists "content/news" }} → true
+{{ os.FileExists "content/news/article-1" }} → false
+{{ os.FileExists "content/news/article-1.md" }} → true
+{{ os.FileExists "news" }} → true
+{{ os.FileExists "news/article-1" }} → false
+{{ os.FileExists "news/article-1.md" }} → true
```
---
By default, `findRE` finds all matches. You can limit the number of matches with an optional LIMIT parameter.
-When specifying the regular expression, use a raw [string literal] (backticks) instead of an interpreted string literal (double quotes) to simplify the syntax. With an interpreted string literal you must escape backslashes.
-
-[string literal]: https://go.dev/ref/spec#String_literals
-
-This function uses the [RE2] regular expression library. See the [RE2 syntax documentation] for details. Note that the RE2 `\C` escape sequence is not supported.
-
-[RE2]: https://github.com/google/re2/
-[RE2 syntax documentation]: https://github.com/google/re2/wiki/Syntax/
-
-{{% note %}}
-The RE2 syntax is a subset of that accepted by [PCRE], roughly speaking, and with various [caveats].
-
-[caveats]: https://swtch.com/~rsc/regexp/regexp3.html#caveats
-[PCRE]: https://www.pcre.org/
-{{% /note %}}
+{{% readfile file="/functions/common/regular-expressions.md" %}}
This example returns a slice of all second level headings (`h2` elements) within the rendered `.Content`:
By default, `findRESubmatch` finds all matches. You can limit the number of matches with an optional LIMIT parameter. A return value of nil indicates no match.
-When specifying the regular expression, use a raw [string literal] (backticks) instead of an interpreted string literal (double quotes) to simplify the syntax. With an interpreted string literal you must escape backslashes.
-
-[string literal]: https://go.dev/ref/spec#String_literals
-
-This function uses the [RE2] regular expression library. See the [RE2 syntax documentation] for details. Note that the RE2 `\C` escape sequence is not supported.
-
-[RE2]: https://github.com/google/re2/
-[RE2 syntax documentation]: https://github.com/google/re2/wiki/Syntax/
-
-{{% note %}}
-The RE2 syntax is a subset of that accepted by [PCRE], roughly speaking, and with various [caveats].
-
-[caveats]: https://swtch.com/~rsc/regexp/regexp3.html#caveats
-[PCRE]: https://www.pcre.org/
-{{% /note %}}
+{{% readfile file="/functions/common/regular-expressions.md" %}}
## Demonstrative examples
Examples:
```go-html-template
-{{ os.Getenv "HOME" }} --> /home/victor
-{{ os.Getenv "USER" }} --> victor
+{{ os.Getenv "HOME" }} → /home/victor
+{{ os.Getenv "USER" }} → victor
```
You can pass values when building your site:
And then retrieve the values within a template:
```go-html-template
-{{ os.Getenv "MY_VAR1" }} --> foo
-{{ os.Getenv "MY_VAR2" }} --> bar
+{{ os.Getenv "MY_VAR1" }} → foo
+{{ os.Getenv "MY_VAR2" }} → bar
```
With Hugo v0.91.0 and later, you must explicitly allow access to environment variables. For details, review [Hugo's Security Policy](/about/security-model/#security-policy). By default, environment variables beginning with `HUGO_` are allowed when using the `os.Getenv` function.
+++ /dev/null
----
-title: hasprefix
-description: Tests whether a string begins with prefix.
-date: 2017-02-01
-publishdate: 2017-02-01
-lastmod: 2017-02-01
-categories: [functions]
-menu:
- docs:
- parent: "functions"
-keywords: [strings]
-signature: ["hasPrefix STRING PREFIX"]
-workson: []
-hugoversion:
-relatedfuncs: [hasSuffix]
-deprecated: false
-aliases: []
----
-
-* `{{ hasPrefix "Hugo" "Hu" }}` → true
+++ /dev/null
----
-title: hassuffix
-linkTitle: hasSuffix
-description: Tests whether a string ends with suffix.
-date: 2023-03-01
-publishdate: 2023-03-01
-lastmod: 2023-03-01
-categories: [functions]
-menu:
-docs:
-parent: "functions"
-keywords: [strings]
-signature: ["hasSuffix STRING SUFFIX"]
-workson: []
-hugoversion:
-relatedfuncs: [hasPrefix]
-deprecated: false
-aliases: []
----
-
-* `{{ hasSuffix "Hugo" "go" }}` → true
```go-html-template
{{ $merged := merge $m1 $m2 $m3 }}
-{{ $merged.x }} --> baz
-{{ $merged.y }} --> wobble
-{{ $merged.z.a }} --> huey
+{{ $merged.x }} → baz
+{{ $merged.y }} → wobble
+{{ $merged.z.a }} → huey
```
Example 2
```go-html-template
{{ $merged := merge $m3 $m2 $m1 }}
-{{ $merged.x }} --> foo
-{{ $merged.y }} --> wibble
-{{ $merged.z.a }} --> huey
+{{ $merged.x }} → foo
+{{ $merged.y }} → wibble
+{{ $merged.z.a }} → huey
```
Example 3
```go-html-template
{{ $merged := merge $m2 $m3 $m1 }}
-{{ $merged.x }} --> foo
-{{ $merged.y }} --> wobble
-{{ $merged.z.a }} --> huey
+{{ $merged.x }} → foo
+{{ $merged.y }} → wobble
+{{ $merged.z.a }} → huey
```
Example 4
```go-html-template
{{ $merged := merge $m1 $m3 $m2 }}
-{{ $merged.x }} --> bar
-{{ $merged.y }} --> wibble
-{{ $merged.z.a }} --> huey
+{{ $merged.x }} → bar
+{{ $merged.y }} → wibble
+{{ $merged.z.a }} → huey
```
{{% note %}}
```go-html-template
{{ $f := os.Stat "README.md" }}
-{{ $f.IsDir }} --> false (bool)
-{{ $f.ModTime }} --> 2021-11-25 10:06:49.315429236 -0800 PST (time.Time)
-{{ $f.Name }} --> README.md (string)
-{{ $f.Size }} --> 241 (int64)
+{{ $f.IsDir }} → false (bool)
+{{ $f.ModTime }} → 2021-11-25 10:06:49.315429236 -0800 PST (time.Time)
+{{ $f.Name }} → README.md (string)
+{{ $f.Size }} → 241 (int64)
{{ $d := os.Stat "content" }}
-{{ $d.IsDir }} --> true (bool)
+{{ $d.IsDir }} → true (bool)
```
Details of the `FileInfo` structure are available in the [Go documentation](https://pkg.go.dev/io/fs#FileInfo).
```go-html-template
{{ range os.ReadDir "content" }}
- {{ .Name }} --> {{ .IsDir }}
+ {{ .Name }} → {{ .IsDir }}
{{ end }}
```
---
By default, `replaceRE` replaces all matches. You can limit the number of matches with an optional LIMIT parameter.
-When specifying the regular expression, use a raw [string literal] (backticks) instead of an interpreted string literal (double quotes) to simplify the syntax. With an interpreted string literal you must escape backslashes.
-
-[string literal]: https://go.dev/ref/spec#String_literals
-
-This function uses the [RE2] regular expression library. See the [RE2 syntax documentation] for details. Note that the RE2 `\C` escape sequence is not supported.
-
-[RE2]: https://github.com/google/re2/
-[RE2 syntax documentation]: https://github.com/google/re2/wiki/Syntax/
-
-{{% note %}}
-The RE2 syntax is a subset of that accepted by [PCRE], roughly speaking, and with various [caveats].
-
-[caveats]: https://swtch.com/~rsc/regexp/regexp3.html#caveats
-[PCRE]: https://www.pcre.org/
-{{% /note %}}
+{{% readfile file="/functions/common/regular-expressions.md" %}}
This example replaces two or more consecutive hyphens with a single hyphen:
Add a given value to existing value(s) of the given key.
-For single values, `Add` accepts values that support Go's `+` operator. If the first `Add` for a key is an array or slice, the following adds will be appended to that list.
+For single values, `Add` accepts values that support Go's `+` operator. If the first `Add` for a key is an array or slice, the following adds will be [appended](/functions/append/) to that list.
```go-html-template
{{ $scratch.Add "greetings" "Hello" }}
--- /dev/null
+---
+title: strings.ContainsNonSpace
+description: Reports whether a string contains any non-space characters as defined by Unicode’s White Space property.
+categories: [functions]
+menu:
+ docs:
+ parent: functions
+keywords: [whitespace space]
+signature: ["strings.ContainsNonSpace STRING"]
+relatedfuncs: ["strings.Contains","strings.ContainsAny"]
+---
+
+```go-html-template
+{{ strings.ContainsNonSpace "\n" }} → false
+{{ strings.ContainsNonSpace " " }} → false
+{{ strings.ContainsNonSpace "\n abc" }} → true
+```
+
+Common white space characters include:
+
+```text
+'\t', '\n', '\v', '\f', '\r', ' '
+```
+
+See the [Unicode Character Database] for a complete list.
+
+[Unicode Character Database]: https://www.unicode.org/Public/UCD/latest/ucd/PropList.txt
```go-html-template
{{ with resources.GetRemote "https://example.com/rss.xml" | transform.Unmarshal }}
- {{ range .channel.item }}
- <strong>{{ .title | plainify | htmlUnescape }}</strong><br />
-
<p>{{ .description | plainify | htmlUnescape }}</p>
- {{ $link := .link | plainify | htmlUnescape }}
- <a href="{{ $link }}">{{ $link }}</a><br />
- <hr>
- {{ end }}
+ {{ range .channel.item }}
+ <strong>{{ .title | plainify | htmlUnescape }}</strong><br>
+ <p>{{ .description | plainify | htmlUnescape }}</p>
+ {{ $link := .link | plainify | htmlUnescape }}
+ <a href="{{ $link }}">{{ $link }}</a><br>
+ <hr>
+ {{ end }}
{{ end }}
```
```go-html-template
-{{ slice 1 3 2 1 | uniq }} --> [1 3 2]
+{{ slice 1 3 2 1 | uniq }} → [1 3 2]
```
{{< code file="layouts/partials/content-header.html" >}}
<header>
- <h1>{{ .Title }}</h1>
- {{ with .Params.location }}
-
<div><a href="/locations/{{ . | urlize }}">{{ . }}</a></div>
- {{ end }}
- <!-- Creates a list of tags for the content and links to each of their pages -->
- {{ with .Params.tags }}
+ <h1>{{ .Title }}</h1>
+ {{ with .Params.location }}
+ <div><a href="/locations/{{ . | urlize }}">{{ . }}</a></div>
+ {{ end }}
+ <!-- Creates a list of tags for the content and links to each of their pages -->
+ {{ with .Params.tags }}
<ul>
- {{ range .}}
- <li>
-
<a href="/tags/{{ . | urlize }}">{{ . }}</a>
- </li>
- {{ end }}
+ {{ range .}}
+ <li>
+ <a href="/tags/{{ . | urlize }}">{{ . }}</a>
+ </li>
+ {{ end }}
</ul>
- {{ end }}
+ {{ end }}
</header>
{{< /code >}}
`intersect`
: `true` if a given field value that is a slice/array of strings or integers contains elements in common with the matching value; it follows the same rules as the [`intersect` function][intersect].
+`like`
+: `true` if a given field value matches a regular expression. Use the `like` operator to compare `string` values. Returns `false` when comparing other data types to the regular expression.
+
## Use `where` with boolean values
When using booleans you should not put quotation marks.
```go-html-template
<p>{{ .Title }}</p>
{{ end }}
```
-
## Use `where` with `intersect`
{{ end }}
{{< /code >}}
+## Use `where` with `like`
+
+This example matches pages where the "foo" parameter begins with "ab":
+
+```go-html-template
+{{ range where site.RegularPages "Params.foo" "like" `^ab` }}
+ <h2><a href="{{ .RelPermalink }}">{{ .LinkTitle }}</a></h2>
+{{ end }}
+```
+
+{{% readfile file="/functions/common/regular-expressions.md" %}}
+
## Use `where` with `first`
Using `first` and `where` together can be very
**Default value:** false
-Enable to turn relative URLs into absolute.
+Enable to turn relative URLs into absolute. See [details](/content-management/urls/#canonical-urls).
### cleanDestinationDir
**Default value:** false
-Enable this to make all relative URLs relative to content root. Note that this does not affect absolute URLs.
+Enable this to make all relative URLs relative to content root. Note that this does not affect absolute URLs. See [details](/content-management/urls/#relative-urls).
### refLinksErrorLevel
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]: http://localhost:1313/hugo-pipes/postprocess/#css-purging-with-postcss
+[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.
### The keywords explained
`:cacheDir`
-: This is the value of the `cacheDir` configuration option if set (can also be set via OS env variable `HUGO_CACHEDIR`). It will fall back to `/opt/build/cache/hugo_cache/` on Netlify, or a `hugo_cache_$USER` directory below the OS temp dir for the others. This means that if you run your builds on Netlify, all caches configured with `:cacheDir` will be saved and restored on the next build. For other CI vendors, please read their documentation. For an CircleCI example, see [this configuration](https://github.com/bep/hugo-sass-test/blob/6c3960a8f4b90e8938228688bc49bdcdd6b2d99e/.circleci/config.yml).
+: See [Configure cacheDir](#configure-cachedir).
`:project`
: 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.
[toml]: https://github.com/toml-lang/toml
[yaml]: https://yaml.org/spec/
[static-files]: /content-management/static-files/
+
+
+# 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 env 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`.
build:
runs-on: ubuntu-latest
env:
- HUGO_VERSION: 0.115.1
+ HUGO_VERSION: 0.115.4
steps:
- name: Install Hugo CLI
run: |
{{< code file=".gitlab-ci.yml" >}}
variables:
- DART_SASS_VERSION: 1.63.6
- HUGO_VERSION: 0.115.3
+ DART_SASS_VERSION: 1.64.1
+ HUGO_VERSION: 0.115.4
NODE_VERSION: 20.x
GIT_DEPTH: 0
GIT_STRATEGY: clone
# Install Dart Sass
- curl -LJO https://github.com/sass/dart-sass/releases/download/${DART_SASS_VERSION}/dart-sass-${DART_SASS_VERSION}-linux-x64.tar.gz
- tar -xf dart-sass-${DART_SASS_VERSION}-linux-x64.tar.gz
- - cp -r dart-sass/* /usr/local/bin
+ - cp -r dart-sass/ /usr/local/bin
- rm -rf dart-sass*
+ - export PATH=/usr/local/bin/dart-sass:$PATH
# Install Hugo
- curl -LJO https://github.com/gohugoio/hugo/releases/download/v${HUGO_VERSION}/hugo_extended_${HUGO_VERSION}_linux-amd64.deb
- apt-get install -y ./hugo_extended_${HUGO_VERSION}_linux-amd64.deb
{{< code file="netlify.toml" >}}
[context.production.environment]
- HUGO_VERSION = "0.99.1"
+ HUGO_VERSION = "0.115.4"
{{< /code >}}
For testing:
{{< code file="netlify.toml" >}}
[context.deploy-preview.environment]
- HUGO_VERSION = "0.99.1"
+ HUGO_VERSION = "0.115.4"
{{< /code >}}
The Netlify configuration file can be a little hard to understand and get right for the different environment, and you may get some inspiration and tips from this site's `netlify.toml`:
## Build from source
-To build Hugo from source you must:
+To build the extended edition of Hugo from source you must:
1. Install [Git]
1. Install [Go] version 1.19 or later
-1. Update your PATH environment variable as described in the [Go documentation]
+1. Install a C compiler, either [GCC] or [Clang]
+1. Update your `PATH` environment variable as described in the [Go documentation]
-> The install directory is controlled by the GOPATH and GOBIN environment variables. If GOBIN is set, binaries are installed to that directory. If GOPATH is set, binaries are installed to the bin subdirectory of the first directory in the GOPATH list. Otherwise, binaries are installed to the bin subdirectory of the default GOPATH ($HOME/go or %USERPROFILE%\go).
+> The install directory is controlled by the `GOPATH` and `GOBIN` environment variables. If `GOBIN` is set, binaries are installed to that directory. If `GOPATH` is set, binaries are installed to the bin subdirectory of the first directory in the `GOPATH` list. Otherwise, binaries are installed to the bin subdirectory of the default `GOPATH` (`$HOME/go` or `%USERPROFILE%\go`).
Then build and test:
```sh
-go install -tags extended github.com/gohugoio/hugo@latest
+CGO_ENABLED=1 go install -tags extended github.com/gohugoio/hugo@latest
hugo version
```
+[Clang]: https://clang.llvm.org/
+[GCC]: https://gcc.gnu.org/
[Git]: https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
-[Go]: https://go.dev/doc/install
[Go documentation]: https://go.dev/doc/code#Command
+[Go]: https://go.dev/doc/install
sudo snap install hugo
```
-To enable access to removable media:
+To enable or revoke access to removable media:
```sh
sudo snap connect hugo:removable-media
+sudo snap disconnect hugo:removable-media
```
-To revoke access to removable media:
+To enable or revoke access to SSH keys:
```sh
-sudo snap disconnect hugo:removable-media
+sudo snap connect hugo:ssh-keys
+sudo snap disconnect hugo:ssh-keys
```
[most distributions]: https://snapcraft.io/docs/installing-snapd
{{% readfile file="/installation/common/05-build-from-source.md" %}}
{{% note %}}
-When building the extended edition of Hugo from source on Windows, you will also need to install the [GCC compiler]. See these [detailed instructions].
-
-[detailed instructions]: https://discourse.gohugo.io/t/41370
-[GCC compiler]: https://gcc.gnu.org/
+See these [detailed instructions](https://discourse.gohugo.io/t/41370) to install GCC on Windows.
{{% /note %}}
## Comparison
Hugo `0.25` is the **Kinder Surprise**: It automatically opens the page you're working on in the browser, it adds full `AND` and `OR` support in page queries, and you can now have templates per language.
-
-
If you start with `hugo server --navigateToChanged`, Hugo will navigate to the relevant page on save (see animated GIF). This is extremely useful for site-wide edits. Another very useful feature in this version is the added support for `AND` (`intersect`) and `OR` (`union`) filters when combined with `where`.
Example:
<header class="homepage-header">
<h1>{{ .Title }}</h1>
{{ with .Params.subtitle }}
- <span class="subtitle">{{ . }}</span>
+ <span class="subtitle">{{ . }}</span>
{{ end }}
</header>
<div class="homepage-content">
</div>
<div>
{{ range first 10 .Site.RegularPages }}
- {{ .Render "summary" }}
+ {{ .Render "summary" }}
{{ end }}
</div>
</main>
## Google Analytics
-Hugo ships with internal templates supporting Google Analytics, both [Google Analytics 4][GA4] (GA4) and Universal Analytics.
+Hugo ships with an internal template supporting [Google Analytics 4][GA4] (GA4).
-**Note:** Universal Analytics are deprecated. For details, see [Universal Analytics will be going away].
+**Note:** Universal Analytics are [deprecated].
[GA4]: https://support.google.com/analytics/answer/10089681
-[Universal Analytics will be going away]: https://support.google.com/analytics/answer/11583528
+[deprecated]: https://support.google.com/analytics/answer/11583528
### Configure Google Analytics
googleAnalytics = "G-MEASUREMENT_ID"
{{</ code-toggle >}}
-**Google Universal Analytics (analytics.js)**
-{{< code-toggle file="hugo" >}}
-googleAnalytics = "UA-PROPERTY_ID"
-{{</ code-toggle >}}
-
### Use the Google Analytics template
-You can then include the Google Analytics internal template:
-
-```go-html-template
-{{ template "_internal/google_analytics_async.html" . }}
-```
-
-**Note:** The async template is _not_ suitable for Google Analytics 4.
+Include the Google Analytics internal template in your templates where you want the code to appear:
```go-html-template
{{ template "_internal/google_analytics.html" . }}
```
-If you want to create your own template, you can access the configured ID with `{{ site.Config.Services.GoogleAnalytics.ID }}`.
+To create your own template, access the configured ID with `{{ site.Config.Services.GoogleAnalytics.ID }}`.
## Disqus
-Hugo also ships with an internal template for [Disqus comments][disqus], a popular commenting system for both static and dynamic websites. In order to effectively use Disqus, you will need to secure a Disqus "shortname" by [signing up for the free service][disqussignup].
+Hugo also ships with an internal template for [Disqus comments][disqus], a popular commenting system for both static and dynamic websites. To effectively use Disqus, secure a Disqus "shortname" by [signing up for the free service][disqussignup].
### Configure Disqus
-To use Hugo's Disqus template, you first need to set a single configuration value:
+To use Hugo's Disqus template, first set up a single configuration value:
{{< code-toggle file="hugo" >}}
disqusShortname = "your-disqus-shortname"
{{</ code-toggle >}}
-You also have the option to set the following in the front matter for a given piece of content:
+You can also set the following in the front matter for a given piece of content:
* `disqus_identifier`
* `disqus_title`
### Use the Disqus template
-To add Disqus, include the following line in templates where you want your comments to appear:
+To add Disqus, include the following line in the templates where you want your comments to appear:
```go-html-template
{{ template "_internal/disqus.html" . }}
* `_internal/disqus.html`
* `_internal/google_analytics.html`
-* `_internal/google_analytics_async.html`
* `_internal/opengraph.html`
* `_internal/pagination.html`
* `_internal/schema.html`
{{ partial "subheader.html" . }}
<main>
<div>
- <h1>{{ .Title }}</h1>
- <!-- Renders the li.html content view for each content/posts/*.md -->
- {{ range .Pages }}
- {{ .Render "li" }}
- {{ end }}
- </ul>
+ <h1>{{ .Title }}</h1>
+ <ul>
+ <!-- Renders the li.html content view for each content/posts/*.md -->
+ {{ range .Pages }}
+ {{ .Render "li" }}
+ {{ end }}
+ </ul>
</div>
</main>
{{ partial "footer.html" . }}
{{ define "main" }}
<main>
<div>
- <h1>{{ .Title }}</h1>
- <!-- ranges through each of the content files associated with a particular taxonomy term and renders the summary.html content view -->
+ <h1>{{ .Title }}</h1>
+ <!-- ranges through each of the content files associated with a particular taxonomy term and renders the summary.html content view -->
{{ range .Pages }}
- {{ .Render "summary" }}
+ {{ .Render "summary" }}
{{ end }}
</div>
</main>
{{< code file="layouts/_default/section.html" >}}
{{ define "main" }}
<main>
- {{ .Content }}
- {{ range .Paginator.Pages }}
- <li>{{ .Title }}
- {{ partial "summary.html" . }}
- </div>
- </li>
- {{ end }}
- </ul>
- {{ partial "pagination.html" . }}
+ {{ .Content }}
+ <ul class="contents">
+ {{ range .Paginator.Pages }}
+ <li>{{ .Title }}
+ <div>
+ {{ partial "summary.html" . }}
+ </div>
+ </li>
+ {{ end }}
+ </ul>
+ {{ partial "pagination.html" . }}
</main>
{{ end }}
{{< /code >}}
#### `.Inner`
-If a closing shortcode is used, the `.Inner` variable will be populated with the content between the opening and closing shortcodes. If a closing shortcode is required, you can check the length of `.Inner` as an indicator of its existence.
+If a closing shortcode is used, the `.Inner` variable will be populated with the content between the opening and closing shortcodes. To check if `.Inner` contains anything other than white space:
+
+```go-html-template
+{{ if strings.ContainsNonSpace .Inner }}
+ Inner is not empty
+{{ end }}
+```
A shortcode with content declared via the `.Inner` variable can also be declared without the content and without the closing tag by using the self-closing syntax:
</section>
<aside id="meta">
<div>
- <section>
- <h4 id="date"> {{ .Date.Format "Mon Jan 2, 2006" }} </h4>
- <h5 id="wordcount"> {{ .WordCount }} Words </h5>
- </section>
+ <section>
+ <h4 id="date"> {{ .Date.Format "Mon Jan 2, 2006" }} </h4>
+ <h5 id="wordcount"> {{ .WordCount }} Words </h5>
+ </section>
{{ with .GetTerms "topics" }}
<ul id="topics">
{{ range . }}
weight: 20
---
-The Hugo community uses a wide range of preferred tools and has developed plug-ins for some of the most popular text editors to help automate parts of your workflow.
-
## Sublime Text
* [Hugofy](https://github.com/akmittal/Hugofy). Hugofy is a plugin for Sublime Text 3 to make life easier to use Hugo static site generator.
* [Hugo Language and Syntax Support](https://marketplace.visualstudio.com/items?itemName=budparr.language-hugo-vscode). Hugo Language and Syntax Support is a Visual Studio Code plugin for Hugo syntax highlighting and snippets. The source code can be found [here](https://github.com/budparr/language-hugo-vscode).
* [Hugo Themer](https://marketplace.visualstudio.com/items?itemName=eliostruyf.vscode-hugo-themer). Hugo Themer is an extension to help you while developing themes. It allows you to easily navigate through your theme files.
* [Front Matter](https://marketplace.visualstudio.com/items?itemName=eliostruyf.vscode-front-matter). Once you go for a static site, you need to think about how you are going to manage your articles. Front matter is a tool that helps you maintain the metadata/front matter of your articles like: creation date, modified date, slug, tile, SEO check, and many more...
-* [Syntax Highlighting for Hugo Shortcodes](https://marketplace.visualstudio.com/items?itemName=kaellarkin.hugo-shortcode-syntax). This extension add some syntax highlighting for Shortcodes, making visual identification of individual pieces easier.
+* [Syntax Highlighting for Hugo Shortcodes](https://marketplace.visualstudio.com/items?itemName=kaellarkin.hugo-shortcode-syntax). This extension adds some syntax highlighting for Shortcodes, making visual identification of individual pieces easier.
## Emacs
## Vim
-* [Vim Hugo Helper](https://github.com/robertbasic/vim-hugo-helper). A small Vim plugin to help me with writing posts with Hugo.
+* [Vim Hugo Helper](https://github.com/robertbasic/vim-hugo-helper). A small Vim plugin that facilitates authoring pages and blog posts with Hugo.
* [vim-hugo](https://github.com/phelipetls/vim-hugo). A Vim plugin with syntax highlighting for templates and a few other features.
[formats]: /content-management/formats/
## Page variables
.AlternativeOutputFormats
-: contains all alternative formats for a given page; this variable is especially useful `link rel` list in your site's `<head>`. (See [Output Formats](/templates/output-formats/).)
+: Contains all alternative formats for a given page; this variable is especially useful `link rel` list in your site's `<head>`. (See [Output Formats](/templates/output-formats/).)
.Aliases
-: aliases of this page
+: Aliases of this page
.Ancestors
-: get the ancestors of each page, simplify [breadcrumb navigation](/content-management/sections#example-breadcrumb-navigation) implementation complexity
+: Get the ancestors of each page, simplify [breadcrumb navigation](/content-management/sections#example-breadcrumb-navigation) implementation complexity
.BundleType
-: the [bundle] type: `leaf`, `branch`, or an empty string if the page is not a bundle.
+: The [bundle] type: `leaf`, `branch`, or an empty string if the page is not a bundle.
.Content
-: the content itself, defined below the front matter.
+: The content itself, defined below the front matter.
.Data
-: the data specific to this type of page.
+: The data specific to this type of page.
.Date
-: the date associated with the page; `.Date` pulls from the `date` field in a content's front matter. See also `.ExpiryDate`, `.PublishDate`, and `.Lastmod`.
+: The date associated with the page. By default, this is the front matter `date` value. See [configuring dates] for a description of fallback values and precedence. See also `.ExpiryDate`, `.Lastmod`, and `.PublishDate`.
.Description
-: the description for the page.
+: The description for the page.
.Draft
-: a boolean, `true` if the content is marked as a draft in the front matter.
+: A boolean, `true` if the content is marked as a draft in the front matter.
.ExpiryDate
-: the date on which the content is scheduled to expire; `.ExpiryDate` pulls from the `expirydate` field in a content's front matter. See also `.PublishDate`, `.Date`, and `.Lastmod`.
+: The date on which the content is scheduled to expire. By default, this is the front matter `expiryDate` value. See [configuring dates] for a description of fallback values and precedence. See also `.Date`, `.Lastmod`, and `.PublishDate`.
.File
-: filesystem-related data for this content file. See also [File Variables].
+: Filesystem-related data for this content file. See also [File Variables].
.Fragments
: Fragments returns the fragments for this page. See [Page Fragments](#page-fragments).
.FuzzyWordCount
-: the approximate number of words in the content.
+: The approximate number of words in the content.
.IsHome
: `true` in the context of the [homepage](/templates/homepage/).
.IsNode
-: always `false` for regular content pages.
+: Always `false` for regular content pages.
.IsPage
-: always `true` for regular content pages.
+: Always `true` for regular content pages.
.IsSection
: `true` if [`.Kind`](/templates/section-templates/#page-kinds) is `section`.
: `true` if there are translations to display.
.Keywords
-: the meta keywords for the content.
+: The meta keywords for the content.
.Kind
-: the page's *kind*. Possible return values are `page`, `home`, `section`, `taxonomy`, or `term`. Note that there are also `RSS`, `sitemap`, `robotsTXT`, and `404` kinds, but these are only available during the rendering of each of these respective page's kind and therefore *not* available in any of the `Pages` collections.
+: The page's *kind*. Possible return values are `page`, `home`, `section`, `taxonomy`, or `term`. Note that there are also `RSS`, `sitemap`, `robotsTXT`, and `404` kinds, but these are only available during the rendering of each of these respective page's kind and therefore *not* available in any of the `Pages` collections.
.Language
-: a language object that points to the language's definition in the site configuration. `.Language.Lang` gives you the language code.
+: A language object that points to the language's definition in the site configuration. `.Language.Lang` gives you the language code.
.Lastmod
-: the date the content was last modified. `.Lastmod` pulls from the `lastmod` field in a content's front matter.
-
- - If `lastmod` is not set, and `.GitInfo` feature is disabled, the front matter `date` field will be used.
- - If `lastmod` is not set, and `.GitInfo` feature is enabled, `.GitInfo.AuthorDate` will be used instead.
-
-See also `.ExpiryDate`, `.Date`, `.PublishDate`, and [`.GitInfo`][gitinfo].
+: The date on which the content was last modified. By default, if `enableGitInfo` is `true` in your site configuration, this is the Git author date, otherwise the front matter `lastmod` value. See [configuring dates] for a description of fallback values and precedence. See also `.Date`,`ExpiryDate`, `.PublishDate`, and [`.GitInfo`][gitinfo].
.LinkTitle
-: access when creating links to the content. If set, Hugo will use the `linktitle` from the front matter before `title`.
+: Access when creating links to the content. If set, Hugo will use the `linktitle` from the front matter before `title`.
.Next
: Points up to the next [regular page](/variables/site/#site-pages) (sorted by Hugo's [default sort](/templates/lists#default-weight--date--linktitle--filepath)). Example: `{{ with .Next }}{{ .Permalink }}{{ end }}`. Calling `.Next` from the first page returns `nil`.
: Points up to the next [regular page](/variables/site/#site-pages) below the same top level section (e.g. in `/blog`)). Pages are sorted by Hugo's [default sort](/templates/lists#default-weight--date--linktitle--filepath). Example: `{{ with .NextInSection }}{{ .Permalink }}{{ end }}`. Calling `.NextInSection` from the first page returns `nil`.
.OutputFormats
-: contains all formats, including the current format, for a given page. Can be combined the with [`.Get` function](/functions/get/) to grab a specific format. (See [Output Formats](/templates/output-formats/).)
+: Contains all formats, including the current format, for a given page. Can be combined the with [`.Get` function](/functions/get/) to grab a specific format. (See [Output Formats](/templates/output-formats/).)
.Pages
-: a collection of associated pages. This value will be `nil` within
- the context of regular content pages. See [`.Pages`](#pages).
+: A collection of associated pages. This value will be `nil` within the context of regular content pages. See [`.Pages`](#pages).
.Permalink
-: the Permanent link for this page; see [Permalinks](/content-management/urls/)
+: The Permanent link for this page; see [Permalinks](/content-management/urls/)
.Plain
-: the Page content stripped of HTML tags and presented as a string. You may need to pipe the result through the [`htmlUnescape`](/functions/htmlunescape/) function when rendering this value with the HTML [output format](/templates/output-formats#output-format-definitions).
+: The Page content stripped of HTML tags and presented as a string. You may need to pipe the result through the [`htmlUnescape`](/functions/htmlunescape/) function when rendering this value with the HTML [output format](/templates/output-formats#output-format-definitions).
.PlainWords
-: the slice of strings that results from splitting .Plain into words, as defined in Go's [strings.Fields](https://pkg.go.dev/strings#Fields).
+: The slice of strings that results from splitting .Plain into words, as defined in Go's [strings.Fields](https://pkg.go.dev/strings#Fields).
.Prev
: Points down to the previous [regular page](/variables/site/#site-pages) (sorted by Hugo's [default sort](/templates/lists#default-weight--date--linktitle--filepath)). Example: `{{ if .Prev }}{{ .Prev.Permalink }}{{ end }}`. Calling `.Prev` from the last page returns `nil`.
: Points down to the previous [regular page](/variables/site/#site-pages) below the same top level section (e.g. `/blog`). Pages are sorted by Hugo's [default sort](/templates/lists#default-weight--date--linktitle--filepath). Example: `{{ if .PrevInSection }}{{ .PrevInSection.Permalink }}{{ end }}`. Calling `.PrevInSection` from the last page returns `nil`.
.PublishDate
-: the date on which the content was or will be published; `.Publishdate` pulls from the `publishdate` field in a content's front matter. See also `.ExpiryDate`, `.Date`, and `.Lastmod`.
+: The date on which the content was or will be published. By default, this is the front matter `publishDate` value. See [configuring dates] for a description of fallback values and precedence. See also `.Date`, `.ExpiryDate`, and `.Lastmod`.
.RawContent
-: raw markdown content without the front matter. Useful with [remarkjs.com](
+: Raw markdown content without the front matter. Useful with [remarkjs.com](
https://remarkjs.com)
.ReadingTime
-: the estimated time, in minutes, it takes to read the content.
+: The estimated time, in minutes, it takes to read the content.
.Resources
-: resources such as images and CSS that are associated with this page
+: Resources such as images and CSS that are associated with this page
.Ref
-: returns the permalink for a given reference (e.g., `.Ref "sample.md"`). `.Ref` does *not* handle in-page fragments correctly. See [Cross References](/content-management/cross-references/).
+: Returns the permalink for a given reference (e.g., `.Ref "sample.md"`). `.Ref` does *not* handle in-page fragments correctly. See [Cross References](/content-management/cross-references/).
.RelPermalink
-: the relative permanent link for this page.
+: The relative permanent link for this page.
.RelRef
-: returns the relative permalink for a given reference (e.g., `RelRef
+: Returns the relative permalink for a given reference (e.g., `RelRef
"sample.md"`). `.RelRef` does *not* handle in-page fragments correctly. See [Cross References](/content-management/cross-references/).
.Site
-: see [Site Variables](/variables/site/).
+: See [Site Variables](/variables/site/).
.Sites
-:
returns all sites (languages). A typical use case would be to link back to the main language: `<a href="{{ .Sites.First.Home.RelPermalink }}">...</a>`.
+:
Returns all sites (languages). A typical use case would be to link back to the main language: `<a href="{{ .Sites.First.Home.RelPermalink }}">...</a>`.
.Sites.First
-: returns the site for the first language. If this is not a multilingual setup, it will return itself.
+: Returns the site for the first language. If this is not a multilingual setup, it will return itself.
.Summary
-: a generated summary of the content for easily showing a snippet in a summary view. The breakpoint can be set manually by inserting <code><!--more--></code> at the appropriate place in the content page, or the summary can be written independent of the page text. See [Content Summaries](/content-management/summaries/) for more details.
+: A generated summary of the content for easily showing a snippet in a summary view. The breakpoint can be set manually by inserting <code><!--more--></code> at the appropriate place in the content page, or the summary can be written independent of the page text. See [Content Summaries](/content-management/summaries/) for more details.
.TableOfContents
-: the rendered [table of contents](/content-management/toc/) for the page.
+: The rendered [table of contents](/content-management/toc/) for the page.
.Title
-: the title for this page.
+: The title for this page.
.Translations
-: a list of translated versions of the current page. See [Multilingual Mode](/content-management/multilingual/) for more information.
+: A list of translated versions of the current page. See [Multilingual Mode](/content-management/multilingual/) for more information.
.TranslationKey
-: the key used to map language translations of the current page. See [Multilingual Mode](/content-management/multilingual/) for more information.
+: The key used to map language translations of the current page. See [Multilingual Mode](/content-management/multilingual/) for more information.
.Truncated
-: a boolean, `true` if the `.Summary` is truncated. Useful for showing a "Read more..." link only when necessary. See [Summaries](/content-management/summaries/) for more information.
+: A boolean, `true` if the `.Summary` is truncated. Useful for showing a "Read more..." link only when necessary. See [Summaries](/content-management/summaries/) for more information.
.Type
-: the [content type](/content-management/types/) of the content (e.g., `posts`).
+: The [content type](/content-management/types/) of the content (e.g., `posts`).
.Weight
-: assigned weight (in the front matter) to this content, used in sorting.
+: Assigned weight (in the front matter) to this content, used in sorting.
.WordCount
-: the number of words in the content.
+: The number of words in the content.
## Writable page-scoped variables
[.Scratch][scratch]
-: returns a Scratch to store and manipulate data. In contrast to the [`.Store`][store] method, this scratch is reset on server rebuilds.
+: Returns a Scratch to store and manipulate data. In contrast to the [`.Store`][store] method, this scratch is reset on server rebuilds.
[.Store][store]
-: returns a Scratch to store and manipulate data. In contrast to the [`.Scratch`][scratch] method, this scratch is not reset on server rebuilds.
+: Returns a Scratch to store and manipulate data. In contrast to the [`.Scratch`][scratch] method, this scratch is not reset on server rebuilds.
## Section variables and methods
{{ page.Title }}
```
-There are one caveat with this, and this isn't new, but it's worth mentioning here: There are situations in Hugo where you may see a cached value, e.g. when using `partialCached` or in a shortcode.
+There are one caveat with this, and this isn't new, but it's worth mentioning here: There are situations in Hugo where you may see a cached value, e.g. when using `partialCached` or in a shortcode.
## Page-level params
{{ $.Param "author.display_name" }}
```
+[configuring dates]: /getting-started/configuration/#configure-dates
[gitinfo]: /variables/git/
[File Variables]: /variables/files/
[bundle]: /content-management/page-bundles
command = "hugo --gc --minify"
[context.production.environment]
-HUGO_VERSION = "0.115.4"
+HUGO_VERSION = "0.116.1"
HUGO_ENV = "production"
HUGO_ENABLEGITINFO = "true"
command = "hugo --gc --minify --enableGitInfo"
[context.split1.environment]
-HUGO_VERSION = "0.115.4"
+HUGO_VERSION = "0.116.1"
HUGO_ENV = "production"
[context.deploy-preview]
command = "hugo --gc --minify --buildFuture -b $DEPLOY_PRIME_URL"
[context.deploy-preview.environment]
-HUGO_VERSION = "0.115.4"
+HUGO_VERSION = "0.116.1"
[context.branch-deploy]
command = "hugo --gc --minify -b $DEPLOY_PRIME_URL"
[context.branch-deploy.environment]
-HUGO_VERSION = "0.115.4"
+HUGO_VERSION = "0.116.1"
[context.next.environment]
HUGO_ENABLEGITINFO = "true"
projects / brevno-suite / hugo / commitdiff