The block keyword in Go templates allows you to define the outer shell of your pages one or more master template(s), filling in or overriding portions as necessary.

Base template lookup

In version 0.20 Hugo introduced custom Output Formats, all of which can have their own templates that also can use a base template if needed.

This introduced two new terms relevant in the lookup of the templates, the media type’s Suffix and the output format’s Name.

Given the above, Hugo tries to use the most specific base tamplate it finds:

  1. /layouts/current-path/template-name-baseof.[output-format].[suffix], e.g. list-baseof.amp.html.
  2. /layouts/current-path/template-name-baseof.[suffix], e.g. list-baseof.html.
  3. /layouts/current-path/baseof.[output-format].[suffix], e.g baseof.amp.html
  4. /layouts/current-path/baseof.[suffix], e.g baseof.html
  5. /layouts/_default/template-name-baseof.[output-format].[suffix] e.g. list-baseof.amp.html.
  6. /layouts/_default/template-name-baseof.[suffix], e.g. list-baseof.html.
  7. /layouts/_default/baseof.[output-format].[suffix]
  8. /layouts/_default/baseof.[suffix]

For each of the steps above, it will first look in the project, then, if theme is set, in the theme’s layouts folder. Hugo picks the first base template found.

As an example, with a site using the theme exampletheme, when rendering the section list for the section post for the output format Calendar. Hugo picks the section/post.calendar.ics as the template and this template has a define section that indicates it needs a base template. This is then the lookup order:

  1. /layouts/section/post-baseof.calendar.ics
  2. /layouts/section/post-baseof.ics
  3. /themes/exampletheme/layouts/section/post-baseof.calendar.ics
  4. /themes/exampletheme/layouts/section/post-baseof.ics
  5. /layouts/section/baseof.calendar.ics
  6. /layouts/section/baseof.ics
  7. /themes/exampletheme/layouts/section/baseof.calendar.ics
  8. /themes/exampletheme/layouts/section/baseof.ics
  9. /layouts/_default/post-baseof.calendar.ics
  10. /layouts/_default/post-baseof.ics
  11. /themes/exampletheme/layouts/_default/post-baseof.calendar.ics
  12. /themes/exampletheme/layouts/_default/post-baseof.ics
  13. /layouts/_default/baseof.calendar.ics
  14. /layouts/_default/baseof.ics
  15. /themes/exampletheme/layouts/_default/baseof.calendar.ics
  16. /themes/exampletheme/layouts/_default/baseof.ics

Define the base template

Let’s define a simple base template (_default/baseof.html), a shell from which all our pages will start.

<!DOCTYPE html>
    <meta charset="utf-8">
    <title>{{ block "title" . }}
      <!-- Blocks may include default content. -->
      {{ .Site.Title }}
    {{ end }}</title>
    <!-- Code that all your templates share, like a header -->

    {{ block "main" . }}
      <!-- The part of the page that begins to differ between templates -->
    {{ end }}

    <!-- More shared code, perhaps a footer -->

Overriding the base

Your default list template (_default/list.html) will inherit all of the code defined in the base template. It could then implement its own “main” block from the base template above like so:

<!-- Note the lack of Go's context "dot" when defining blocks -->
{{ define "main" }}
  {{ range .Data.Pages }}
      <h2>{{ .Title }}</h2>
      {{ .Content }}
  {{ end }}
{{ end }}

This replaces the contents of our (basically empty) “main” block with something useful for the list template. In this case, we didn’t define a “title” block so the contents from our base template remain unchanged in lists.

In our default single template (_default/single.html), let’s implement both blocks:

{{ define "title" }}
  {{ .Title }} &ndash; {{ .Site.Title }}
{{ end }}
{{ define "main" }}
  <h1>{{ .Title }}</h1>
  {{ .Content }}
{{ end }}

This overrides both block areas from the base template with code unique to our single template.