Render

The Render method on a Page object renders a view template with the given page as context.

The VIEW argument is the name of a view template, optionally preceded by a slash-separated directory path. Do not include a file extension. Hugo resolves the template via the template lookup order, so the same VIEW value may map to different view templates depending on the page being rendered.

Consider this layout structure:

layouts/
├── books/
│   └── summary.html
├── baseof.html
├── home.html
├── page.html
├── section.html
├── summary.html
├── taxonomy.html
└── term.html

And this template:

<ul>
  {{ range site.RegularPages }}
    {{ .Render "summary" }}
  {{ end }}
</ul>

When rendering content of type “books”, the Render method calls:

layouts/books/summary.html

For all other pages, the Render method calls:

layouts/summary.html

As a best practice, place view templates together in a dedicated subdirectory. Hugo does not reserve a directory name for view templates as it does for _partials, _shortcodes, and _markup. The examples below use _views, where the underscore prefix differentiates it from other path segments and conveys its purpose, but a directory named foo would work equally well.

With path segments, consider this layout structure:

layouts/
├── _views/
│   └── summary.html
├── books/
│   └── _views/
│       └── summary.html
├── baseof.html
├── home.html
├── page.html
├── section.html
├── taxonomy.html
└── term.html

And this template:

<ul>
  {{ range site.RegularPages }}
    {{ .Render "_views/summary" }}
  {{ end }}
</ul>

When rendering content of type “books”, the Render method calls:

layouts/books/_views/summary.html

For all other pages, the Render method calls:

layouts/_views/summary.html

Although similar to the partial function, there are key differences.