mirror of
https://github.com/gohugoio/hugo.git
synced 2024-11-14 20:37:55 -05:00
83bef6955e
e161ea09d Add one more Chinese file to workaround reflect: Zero(nil) b595b3a21 Add more Chinese translation 56e4e95d9 Use lang.Merge to "fill in the gaps" for untranslated pages ef079406c Merge commit '650fac3a4e7d256f4505402ab44cfc3c804b8dea' 650fac3a4 Squashed 'themes/gohugoioTheme/' changes from a1768ebb..f31a3dc8 322eff899 Add Chinese language for menus d90b886e0 Fix Markdown table syntax in previous commit 737f3dfca Update the leaf bundle vs branch bundle table 09fa1bc4e Clarify that `.Now` is obsolete 879ea3f6a Make release notes somewhat more consistent 0113e2051 Move 0.40.2-relnotes into content/en/news 77578f5bf Move content/ into new contentDir content/en/ 4dcf7c709 Fix "reflect: Zero(nil)" error in showcase 63dd25505 Release 0.40.2 2076c0d56 releaser: Prepare repository for 0.41-DEV 070fe565e releaser: Add release notes to /docs for release of 0.40.2 4ce52e913 releaser: Bump versions for release of 0.40.2 41907c487 Fix typos in syntax-highlighting.md 91753ef3d Add missing backtick b77274301 Remove duplicate release notes (0.27, 0.27.1, 0.35) 6e00da316 Remove obsolete content/release-notes/ directory 00a6d8c02 Change en dash back to `--` in 0.38.2-relnotes 51b32dc00 Update archetypes.md d0e5c2307 Release 0.40.1 4538a6d5b releaser: Prepare repository for 0.41-DEV 91b391d70 releaser: Add release notes to /docs for release of 0.40.1 e0979d143 releaser: Bump versions for release of 0.40.1 7983967c2 Clean images fe3fdd77d Polish showcase for Flesland Flis e6dde3989 Showcase - Flesland Flis AS by Absoluttweb 73aa62290 Revive @spf13's special Hugo font add67b335 Release Hugo 0.40 c0a26e5a6 Merge branch 'temp40' beeabaaae releaser: Prepare repository for 0.41-DEV e67d5e985 releaser: Add release notes to /docs for release of 0.40 6cdd95273 releaser: Bump versions for release of 0.40 bee21fb9b Revive the other Hugo logos too 4f45e8fe1 Fix the link type attribute for RSS in examples 8c67dc89a Fix example in delimit doc e7f6c00d5 Revive the logo used on the forum 82b0cd26e Merge commit 'a215abf70e018f4bf40d6c09d8bd148d8684b33d' 119c8ca58 Merge commit 'd2ec1a06df8ab6b17ad05cb008d5701b40327d47' db4683bd2 Improve .Get docs 05260b886 .Get function: fix syntax signature git-subtree-dir: docs git-subtree-split: e161ea09d33e3199f4998e4d2e9068d5a850f042
121 lines
4.3 KiB
Markdown
121 lines
4.3 KiB
Markdown
---
|
|
title: Content View Templates
|
|
# linktitle: Content Views
|
|
description: Hugo can render alternative views of your content, which is especially useful in list and summary views.
|
|
date: 2017-02-01
|
|
publishdate: 2017-02-01
|
|
lastmod: 2017-02-01
|
|
categories: [templates]
|
|
keywords: [views]
|
|
menu:
|
|
docs:
|
|
parent: "templates"
|
|
weight: 70
|
|
weight: 70
|
|
sections_weight: 70
|
|
draft: false
|
|
aliases: []
|
|
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 `post` 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.
|
|
|
|
```
|
|
▾ layouts/
|
|
▾ post/
|
|
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.
|
|
|
|
|
|
```
|
|
▾ 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/<TYPE>/<VIEW>.html`
|
|
2. `/layouts/_default/<VIEW>.html`
|
|
3. `/themes/<THEME>/layouts/<TYPE>/<VIEW>.html`
|
|
4. `/themes/<THEME>/layouts/_default/<VIEW>.html`
|
|
|
|
## Example: Content View Inside a List
|
|
|
|
The following example demonstrates how to use content views inside of 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" download="list.html" >}}
|
|
<main id="main">
|
|
<div>
|
|
<h1 id="title">{{ .Title }}</h1>
|
|
{{ range .Data.Pages }}
|
|
{{ .Render "summary"}}
|
|
{{ end }}
|
|
</div>
|
|
</main>
|
|
{{< /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" download="summary.html" >}}
|
|
<article class="post">
|
|
<header>
|
|
<h2><a href='{{ .Permalink }}'> {{ .Title }}</a> </h2>
|
|
<div class="post-meta">{{ .Date.Format "Mon, Jan 2, 2006" }} - {{ .FuzzyWordCount }} Words </div>
|
|
</header>
|
|
{{ .Summary }}
|
|
<footer>
|
|
<a href='{{ .Permalink }}'><nobr>Read more →</nobr></a>
|
|
</footer>
|
|
</article>
|
|
{{< /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" download="li.html" >}}
|
|
<li>
|
|
<a href="{{ .Permalink }}">{{ .Title }}</a>
|
|
<div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>
|
|
</li>
|
|
{{< /code >}}
|
|
|
|
[lists]: /templates/lists/
|
|
[lookup]: /templates/lookup-order/
|
|
[pagevars]: /variables/page/
|
|
[render]: /functions/render/
|
|
[single]: /templates/single-page-templates/
|
|
[spf]: http://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/
|