hugo/docs/content/en/templates/introduction.md

title	linkTitle	description	categories	keywords	menu	weight	aliases	toc
Templating	Templating	Hugo uses Go's `html/template` and `text/template` libraries as the basis for the templating.	fundamentals templates	go	docs parent weight templates 20	20	/layouts/introduction/ /layout/introduction/ /templates/go-templates/	true

{{% note %}} The following is only a primer on Go Templates. For an in-depth look into Go Templates, check the official Go docs. {{% /note %}}

Go Templates provide an extremely simple template language that adheres to the belief that only the most basic of logic belongs in the template or view layer.

Basic syntax

Go Templates are HTML files with the addition of variables and functions. Go Template variables and functions are accessible within {{ }}.

Access a predefined variable

A predefined variable could be a variable already existing in the current scope (like the .Title example in the Variables section below) or a custom variable (like the $address example in that same section).

{{ .Title }}
{{ $address }}

Parameters for functions are separated using spaces. The general syntax is:

{{ FUNCTION ARG1 ARG2 .. }}

The following example calls the add function with inputs of 1 and 2:

{{ add 1 2 }}

Methods and fields are accessed via dot notation

Accessing the Page Parameter bar defined in a piece of content's front matter.

{{ .Params.bar }}

Parentheses can be used to group items together

{{ if or (isset .Params "alt") (isset .Params "caption") }} Caption {{ end }}

A single statement can be split over multiple lines

{{ if or
  (isset .Params "alt")
  (isset .Params "caption")
}}

Raw string literals can include newlines

{{ $msg := `Line one.
Line two.` }}

Variables

Each Go Template gets a data object. In Hugo, each template is passed a Page. In the below example, .Title is one of the elements accessible in that Page variable.

With the Page being the default scope of a template, the Title element in current scope (. -- "the dot") is accessible simply by the dot-prefix (.Title):

<title>{{ .Title }}</title>

Values can also be stored in custom variables and referenced later:

{{% note %}} The custom variables need to be prefixed with $. {{% /note %}}

{{ $address := "123 Main St." }}
{{ $address }}

Variables can be re-defined using the = operator. The example below prints "Var is Hugo Home" on the home page, and "Var is Hugo Page" on all other pages:

{{ $var := "Hugo Page" }}
{{ if .IsHome }}
    {{ $var = "Hugo Home" }}
{{ end }}
Var is {{ $var }}

Variable names must conform to Go's naming rules for identifiers.

Functions

Go Templates only ship with a few basic functions but also provide a mechanism for applications to extend the original set.

Hugo template functions provide additional functionality specific to building websites. Functions are called by using their name followed by the required parameters separated by spaces. Template functions cannot be added without recompiling Hugo.

Example 1: adding numbers

{{ add 1 2 }}
<!-- prints 3 -->

Example 2: comparing numbers

{{ lt 1 2 }}
<!-- prints true (i.e., since 1 is less than 2) -->

Note that both examples make use of Go Template's math functions.

{{% note %}} There are more boolean operators than those listed in the Hugo docs in the Go Template documentation. {{% /note %}}

Includes

When including another template, you will need to pass it the data that it would need to access.

{{% note %}} To pass along the current context, please remember to include a trailing dot. {{% /note %}}

The templates location will always be starting at the layouts/ directory within Hugo.

Partial

The partial function is used to include partial templates using the syntax {{ partial "<PATH>/<PARTIAL>.<EXTENSION>" . }}.

Example of including a layouts/partials/header.html partial:

{{ partial "header.html" . }}

Template

The template function was used to include partial templates in much older Hugo versions. Now it's useful only for calling internal templates. The syntax is {{ template "_internal/<TEMPLATE>.<EXTENSION>" . }}.

{{% note %}} The available internal templates can be found here. {{% /note %}}

Example of including the internal opengraph.html template:

{{ template "_internal/opengraph.html" . }}

Logic

Go Templates provide the most basic iteration and conditional logic.

Iteration

The Go Templates make heavy use of range to iterate over a map, array, or slice. The following are different examples of how to use range.

Example 1: using context (.)

{{ range $array }}
    {{ . }} <!-- The . represents an element in $array -->
{{ end }}

Example 2: declaring a variable name for an array element's value

{{ range $elem_val := $array }}
    {{ $elem_val }}
{{ end }}

Example 3: declaring variable names for an array element's index and value

For an array or slice, the first declared variable will map to each element's index.

{{ range $elem_index, $elem_val := $array }}
   {{ $elem_index }} -- {{ $elem_val }}
{{ end }}

Example 4: declaring variable names for a map element's key and value

For a map, the first declared variable will map to each map element's key.

{{ range $elem_key, $elem_val := $map }}
   {{ $elem_key }} -- {{ $elem_val }}
{{ end }}

Example 5: conditional on empty map, array, or slice

If the map, array, or slice passed into the range is zero-length then the else statement is evaluated.

{{ range $array }}
    {{ . }}
{{ else }}
    <!-- This is only evaluated if $array is empty -->
{{ end }}

Conditionals

if, else, with, or, and and not provide the framework for handling conditional logic in Go Templates. Like range, if and with statements are closed with an {{ end }}.

Go Templates treat the following values as false:

• false (boolean)
• 0 (integer)
• any zero-length array, slice, map, or string

Example 1: with

It is common to write "if something exists, do this" kind of statements using with.

{{% note %}} with rebinds the context . within its scope (just like in range). {{% /note %}}

It skips the block if the variable is absent, or if it evaluates to "false" as explained above.

{{ with .Params.title }}
    <h4>{{ . }}</h4>
{{ end }}

Example 2: with .. else

Below snippet uses the "description" front-matter parameter's value if set, else uses the default .Summary Page variable:

{{ with .Param "description" }}
    {{ . }}
{{ else }}
    {{ .Summary }}
{{ end }}

See the .Param function.

Example 3: if

An alternative (and a more verbose) way of writing with is using if. Here, the . does not get rebound.

Below example is "Example 1" rewritten using if:

{{ if isset .Params "title" }}
    <h4>{{ index .Params "title" }}</h4>
{{ end }}

Example 4: if .. else

Below example is "Example 2" rewritten using if .. else, and using isset + .Params variable (different from the .Param function) instead:

{{ if (isset .Params "description") }}
    {{ index .Params "description" }}
{{ else }}
    {{ .Summary }}
{{ end }}

Example 5: if .. else if .. else

Unlike with, if can contain else if clauses too.

{{ if (isset .Params "description") }}
    {{ index .Params "description" }}
{{ else if (isset .Params "summary") }}
    {{ index .Params "summary" }}
{{ else }}
    {{ .Summary }}
{{ end }}

Example 6: and & or

{{ if (and (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")) }}

Pipes

One of the most powerful components of Go Templates is the ability to stack actions one after another. This is done by using pipes. Borrowed from Unix pipes, the concept is simple: each pipeline's output becomes the input of the following pipe.

Because of the very simple syntax of Go Templates, the pipe is essential to being able to chain together function calls. One limitation of the pipes is that they can only work with a single value and that value becomes the last parameter of the next pipeline.

A few simple examples should help convey how to use the pipe.

Example 1: shuffle

The following two examples are functionally the same:

{{ shuffle (seq 1 5) }}

{{ (seq 1 5) | shuffle }}

Example 2: index

The following accesses the page parameter called "disqus_url" and escapes the HTML. This example also uses the index function, which is built into Go Templates:

{{ index .Params "disqus_url" | html }}

Example 3: or with isset

{{ if or (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr") }}
Stuff Here
{{ end }}

Could be rewritten as

{{ if isset .Params "caption" | or isset .Params "title" | or isset .Params "attr" }}
Stuff Here
{{ end }}

Context (aka "the dot")

The most easily overlooked concept to understand about Go Templates is that {{ . }} always refers to the current context.

• In the top level of your template, this will be the data set made available to it.
• Inside an iteration, however, it will have the value of the current item in the loop; i.e., {{ . }} will no longer refer to the data available to the entire page.

If you need to access page-level data (e.g., page parameters set in front matter) from within the loop, you will likely want to do one of the following:

1. Define a variable independent of context

The following shows how to define a variable independent of the context.

{{< code file="tags-range-with-page-variable.html" >}} {{ $title := .Site.Title }}

{{ range .Params.tags }}
• {{ . }} - {{ $title }}
{{ end }}

{{< /code >}}

{{% note %}} Notice how once we have entered the loop (i.e. range), the value of {{ . }} has changed. We have defined a variable outside the loop ({{ $title }}) that we've assigned a value so that we have access to the value from within the loop as well. {{% /note %}}

2. Use $. to access the global context

$ has special significance in your templates. $ is set to the starting value of . ("the dot") by default. This is a documented feature of Go text/template. This means you have access to the global context from anywhere. Here is an equivalent example of the preceding code block but now using $ to grab .Site.Title from the global context:

{{< code file="range-through-tags-w-global.html" >}}

{{ range .Params.tags }}
• {{ . }} - {{ $.Site.Title }}
{{ end }}

{{< /code >}}

{{% warning "Don't Redefine the Dot" %}} The built-in magic of $ would cease to work if someone were to mischievously redefine the special character; e.g. {{ $ := .Site }}. Don't do it. You may, of course, recover from this mischief by using {{ $ := . }} in a global context to reset $ to its default value. {{% /note %}}

Whitespace

Go 1.6 includes the ability to trim the whitespace from either side of a Go tag by including a hyphen (-) and space immediately beside the corresponding {{ or }} delimiter.

For instance, the following Go Template will include the newlines and horizontal tab in its HTML output:

<div>
  {{ .Title }}
</div>

Which will output:

<div>
  Hello, World!
</div>

Leveraging the - in the following example will remove the extra white space surrounding the .Title variable and remove the newline:

<div>
  {{- .Title -}}
</div>

Which then outputs:

<div>Hello, World!</div>

Go considers the following characters whitespace:

• space
• horizontal tab
• carriage return
• newline

Comments

In order to keep your templates organized and share information throughout your team, you may want to add comments to your templates. There are two ways to do that with Hugo.

Go templates comments

Go Templates support {{/* and */}} to open and close a comment block. Nothing within that block will be rendered.

For example:

Bonsoir, {{/* {{ add 0 + 2 }} */}}Eliott.

Will render Bonsoir, Eliott., and not care about the syntax error (add 0 + 2) in the comment block.

HTML comments

You can add html comments by piping a string HTML code comment to safeHTML.

For example:

{{ "<!-- This is an HTML comment -->" | safeHTML }}

If you need variables to construct such HTML comments, just pipe printf to safeHTML.

For example:

{{ printf "<!-- Our website is named: %s -->" .Site.Title | safeHTML }}

HTML comments containing Go templates

HTML comments are by default stripped, but their content is still evaluated. That means that although the HTML comment will never render any content to the final HTML pages, code contained within the comment may fail the build process.

{{% note %}} Do not try to comment out Go Template code using HTML comments. {{% /note %}}

<!-- {{ $author := "Emma Goldman" }} was a great woman. -->
{{ $author }}

The templating engine will strip the content within the HTML comment, but will first evaluate any Go Template code if present within. So the above example will render Emma Goldman, as the $author variable got evaluated in the HTML comment. But the build would have failed if that code in the HTML comment had an error.

Hugo parameters

Hugo provides the option of passing values to your template layer through your site configuration (i.e. for site-wide values) or through the metadata of each specific piece of content (i.e. the front matter). You can define any values of any type and use them however you want in your templates, as long as the values are supported by the front matter format.

Use content (Page) parameters

You can provide variables to be used by templates in individual content's front matter.

An example of this is used in the Hugo docs. Most of the pages benefit from having the table of contents provided, but sometimes the table of contents doesn't make a lot of sense. We've defined a notoc variable in our front matter that will prevent a table of contents from rendering when specifically set to true.

Here is the example front matter:

{{< code-toggle file="content/example.md" fm=true copy=false >}} title: Example notoc: true {{< /code-toggle >}}

Here is an example of corresponding code that could be used inside a toc.html partial template:

{{< code file="layouts/partials/toc.html" >}} {{ if not .Params.notoc }}

{{ .Title }}

{{ .TableOfContents }}

{{ end }} {{< /code >}}

We want the default behavior to be for pages to include a TOC unless otherwise specified. This template checks to make sure that the notoc: field in this page's front matter is not true.

Use site configuration parameters

You can arbitrarily define as many site-level parameters as you want in your site's configuration file. These parameters are globally available in your templates.

For instance, you might declare the following:

{{< code-toggle file="hugo" >}} params: copyrighthtml: "Copyright © 2017 John Doe. All Rights Reserved." twitteruser: "spf13" sidebarrecentlimit: 5 {{< /code >}}

Within a footer layout, you might then declare a <footer> that is only rendered if the copyrighthtml parameter is provided. If it is provided, you will then need to declare the string is safe to use via the safeHTML function so that the HTML entity is not escaped again. This would let you easily update just your top-level configuration file each January 1st, instead of hunting through your templates.

{{ if .Site.Params.copyrighthtml }}
    <footer>
        <div class="text-center">{{ .Site.Params.CopyrightHTML | safeHTML }}</div>
    </footer>
{{ end }}

An alternative way of writing the "if" and then referencing the same value is to use with instead. with rebinds the context (.) within its scope and skips the block if the variable is absent:

{{< code file="layouts/partials/twitter.html" >}} {{ with .Site.Params.twitteruser }}

{{ end }} {{< /code >}}

Finally, you can pull "magic constants" out of your layouts as well. The following uses the first function, as well as the .RelPermalink page variable and the .Site.Pages site variable.

<nav>
  <h1>Recent Posts</h1>
  <ul>
  {{- range first .Site.Params.SidebarRecentLimit .Site.Pages -}}
      <li><a href="{{ .RelPermalink }}">{{ .Title }}</a></li>
  {{- end -}}
  </ul>
</nav>

Example: show future events

Given the following content structure and front matter:

content/
└── events/
    ├── event-1.md
    ├── event-2.md
    └── event-3.md

{{< code-toggle file="content/events/event-1.md" copy=false >}} title = 'Event 1' date = 2021-12-06T10:37:16-08:00 draft = false start_date = 2021-12-05T09:00:00-08:00 end_date = 2021-12-05T11:00:00-08:00 {{< /code-toggle >}}

This partial template renders future events:

{{< code file="layouts/partials/future-events.html" >}}

Future Events

{{ range where site.RegularPages "Type" "events" }} {{ if gt (.Params.start_date | time.AsTime) now }} {{ $startDate := .Params.start_date | time.Format ":date_medium" }}
• {{ .LinkTitle }} - {{ $startDate }}
{{ end }} {{ end }}

{{< /code >}}

If you restrict front matter to the TOML format, and omit quotation marks surrounding date fields, you can perform date comparisons without casting.

{{< code file="layouts/partials/future-events.html" >}}

Future Events

{{ range where (where site.RegularPages "Type" "events") "Params.start_date" "gt" now }} {{ $startDate := .Params.start_date | time.Format ":date_medium" }}
• {{ .LinkTitle }} - {{ $startDate }}
{{ end }}

{{< /code >}}