--- title: Content view templates description: Hugo can render alternative views of your content, useful in list and summary views. categories: [templates] keywords: [views] menu: docs: parent: templates weight: 110 weight: 110 toc: true --- These alternative **content views** are especially useful in [list templates][lists]. The following are common use cases for content views: * You want content of every type to be shown on the homepage but only with limited [summary views][summaries]. * You only want a bulleted list of your content on a [taxonomy list page][taxonomylists]. Views make this very straightforward by delegating the rendering of each different type of content to the content itself. ## Create a content view To create a new view, create a template in each of your different content type directories with the view name. The following example contains an "li" view and a "summary" view for the `posts` and `project` content types. As you can see, these sit next to the [single content view][single] template, `single.html`. You can even provide a specific view for a given type and continue to use the `_default/single.html` for the primary view. ```txt ▾ layouts/ ▾ posts/ li.html single.html summary.html ▾ project/ li.html single.html summary.html ``` Hugo also has support for a default content template to be used in the event that a specific content view template has not been provided for that type. Content views can also be defined in the `_default` directory and will work the same as list and single templates who eventually trickle down to the `_default` directory as a matter of the lookup order. ```txt ▾ layouts/ ▾ _default/ li.html single.html summary.html ``` ## Which template will be rendered? The following is the [lookup order][lookup] for content views: 1. `/layouts//.html` 2. `/layouts/_default/.html` 3. `/themes//layouts//.html` 4. `/themes//layouts/_default/.html` ## Example: content view inside a list The following example demonstrates how to use content views inside your [list templates][lists]. ### `list.html` In this example, `.Render` is passed into the template to call the [render function][render]. `.Render` is a special function that instructs content to render itself with the view template provided as the first argument. In this case, the template is going to render the `summary.html` view that follows: {{< code file=layouts/_default/list.html >}}

{{ .Title }}

{{ range .Pages }} {{ .Render "summary" }} {{ end }}
{{< /code >}} ### `summary.html` Hugo will pass the entire page object to the following `summary.html` view template. (See [Page Variables][pagevars] for a complete list.) {{< code file=layouts/_default/summary.html >}} {{< /code >}} ### `li.html` Continuing on the previous example, we can change our render function to use a smaller `li.html` view by changing the argument in the call to the `.Render` function (i.e., `{{ .Render "li" }}`). {{< code file=layouts/_default/li.html >}}
  • {{ .LinkTitle }}
    {{ .Date.Format "Mon, Jan 2, 2006" }}
  • {{< /code >}} [lists]: /templates/lists/ [lookup]: /templates/lookup-order/ [pagevars]: /variables/page/ [render]: /methods/page/render/ [single]: /templates/single-page-templates/ [spf]: https://spf13.com [spfsourceli]: https://github.com/spf13/spf13.com/blob/master/layouts/_default/li.html [spfsourcesection]: https://github.com/spf13/spf13.com/blob/master/layouts/_default/section.html [spfsourcesummary]: https://github.com/spf13/spf13.com/blob/master/layouts/_default/summary.html [summaries]: /content-management/summaries/ [taxonomylists]: /templates/taxonomy-templates/