hugo/content/templates/ordering-and-grouping.md

title	linktitle	description	date	publishdate	lastmod	categories	menu	weight	sections_weight	draft	aliases	toc	notes
Ordere and Grouping Hugo Lists	List Ordering and Grouping	You can group or order your content in both your templating and content front matter.	2017-02-01	2017-02-01	2017-02-01	templates	docs parent weight templates 27	27	27	true	/templates/ordering/ /templates/grouping/	true	This was originally going to be a separate page on the new docs site but it now makes more sense to keep everything within the templates/lists page. - rdwatters, 2017-03-12.

In Hugo, A list template is any template that will be used to render multiple pieces of content in a single HTML page.

Example List Templates

Section Template

This list template is used for spf13.com. It makes use of [partial templates][partials]. All examples use a view called either "li" or "summary."

{{< code file="layouts/section/post.html" >}} {{ partial "header.html" . }} {{ partial "subheader.html" . }}

{{ .Title }}

{{ range .Data.Pages }} {{ .Render "li"}} {{ end }}

{{ partial "footer.html" . }} {{< /code >}}

Taxonomy Template

{{< code file="layouts/_default/taxonomies.html" download="taxonomies.html" >}} {{ define "main" }}

{{ .Title }}

{{ range .Data.Pages }} {{ .Render "summary"}} {{ end }}

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

Order Content

Hugo lists render the content based on metadata provided in the front matter..

Here are a variety of different ways you can order the content items in your list templates:

Default: Weight > Date

{{< code file="layouts/partials/order-default.html" >}}

{{ range .Data.Pages }}

• {{ .Title }}

  {{ .Date.Format "Mon, Jan 2, 2006" }}
{{ end }}

{{< /code >}}

By Weight

{{< code file="layouts/partials/by-weight.html" >}} {{ range .Data.Pages.ByWeight }}

{{ .Title }}

{{ .Date.Format "Mon, Jan 2, 2006" }}

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

By Date

{{< code file="layouts/partials/by-date.html" >}} {{ range .Data.Pages.ByDate }}

{{ .Title }}

{{ .Date.Format "Mon, Jan 2, 2006" }}

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

By Publish Date

{{< code file="layouts/partials/by-publish-date.html" >}} {{ range .Data.Pages.ByPublishDate }}

{{ .Title }}

{{ .PublishDate.Format "Mon, Jan 2, 2006" }}

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

By Expiration Date

{{< code file="layouts/partials/by-expiry-date.html" >}} {{ range .Data.Pages.ByExpiryDate }}

{{ .Title }}

{{ .ExpiryDate.Format "Mon, Jan 2, 2006" }}

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

By Last Modified Date

{{< code file="layouts/partials/by-last-mod.html" >}} {{ range .Data.Pages.ByLastmod }}

{{ .Title }}

{{ .Date.Format "Mon, Jan 2, 2006" }}

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

By Length

{{< code file="layouts/partials/by-length.html" >}} {{ range .Data.Pages.ByLength }}

{{ .Title }}

{{ .Date.Format "Mon, Jan 2, 2006" }}

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

By Title

{{< code file="layouts/partials/by-title.html" >}} {{ range .Data.Pages.ByTitle }}

{{ .Title }}

{{ .Date.Format "Mon, Jan 2, 2006" }}

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

By Link Title

{{< code file="layouts/partials/by-link-title.html" >}} {{ range .Data.Pages.ByLinkTitle }}

{{ .LinkTitle }}

{{ .Date.Format "Mon, Jan 2, 2006" }}

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

By Parameter

Order based on the specified front matter parameter. Content that does not have the specified front matter field will use the site's .Site.Params default. If the parameter is not found at all in some entries, those entries will appear together at the end of the ordering.

The below example sorts a list of posts by their rating.

{{< code file="layouts/partials/by-rating.html" >}} {{ range (.Data.Pages.ByParam "rating") }}

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

If the front matter field of interest is nested beneath another field, you can also get it:

{{< code file="layouts/partials/by-nested-param.html" >}} {{ range (.Data.Pages.ByParam "author.last_name") }}

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

Reverse Order

Reversing order can be applied to any of the above methods. The following uses ByDate as an example:

{{< code file="layouts/partials/by-date-reverse.html" >}} {{ range .Data.Pages.ByDate.Reverse }}

{{ .Title }}

{{ .Date.Format "Mon, Jan 2, 2006" }}

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

Group Content

Hugo provides some functions for grouping pages by Section, Type, Date, etc.

By Page Field

{{< code file="layouts/partials/by-page-field.html" >}} {{ range .Data.Pages.GroupBy "Section" }}

{{ .Key }}

{{ range .Pages }}
• {{ .Title }}
  {{ .Date.Format "Mon, Jan 2, 2006" }}
{{ end }}

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

By Page date

{{< code file="layouts/partials/by-page-date.html" >}} {{ range .Data.Pages.GroupByDate "2006-01" }}

{{ .Key }}

{{ range .Pages }}
• {{ .Title }}
  {{ .Date.Format "Mon, Jan 2, 2006" }}
{{ end }}

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

By Page publish date

{{< code file="layouts/partials/by-page-publish-date.html" >}} {{ range .Data.Pages.GroupByPublishDate "2006-01" }}

{{ .Key }}

{{ range .Pages }}
• {{ .Title }}
  {{ .PublishDate.Format "Mon, Jan 2, 2006" }}
{{ end }}

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

By Page Param

{{< code file="layouts/partials/by-page-param.html" >}} {{ range .Data.Pages.GroupByParam "param_key" }}

{{ .Key }}

{{ range .Pages }}
• {{ .Title }}
  {{ .Date.Format "Mon, Jan 2, 2006" }}
{{ end }}

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

By Page Param in Date Format

{{< code file="layouts/partials/by-page-param-as-date.html" >}} {{ range .Data.Pages.GroupByParamDate "param_key" "2006-01" }}

{{ .Key }}

{{ range .Pages }}
• {{ .Title }}
  {{ .Date.Format "Mon, Jan 2, 2006" }}
{{ end }}

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

Reverse Key Order

The ordering of the groups is performed by keys in alphanumeric order (A–Z, 1–100) and in reverse chronological order (newest first) for dates.

While these are logical defaults, they are not always the desired order. There are two different syntaxes to change the order, both of which work the same way. You can use your preferred syntax.

Reverse Method

{{ range (.Data.Pages.GroupBy "Section").Reverse }}

{{ range (.Data.Pages.GroupByDate "2006-01").Reverse }}

Provide the Alternate Direction

{{ range .Data.Pages.GroupByDate "2006-01" "asc" }}

{{ range .Data.Pages.GroupBy "Section" "desc" }}

Order Within Groups

Because Grouping returns a {{.Key}} and a slice of pages, all of the ordering methods listed above are available.

In the following example, groups are ordered chronologically and then content within each group is ordered alphabetically by title.

{{< code file="layouts/partials/by-group-by-page.html" >}} {{ range .Data.Pages.GroupByDate "2006-01" "asc" }}

{{ .Key }}

{{ range .Pages.ByTitle }}
• {{ .Title }}
  {{ .Date.Format "Mon, Jan 2, 2006" }}
{{ end }}

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

Filter and Limiting Lists

Sometimes you only want to list a subset of the available content. A common request is to only display “Posts” on the homepage. You can accomplish this with the where function.

where

where works in a similar manner to the where keyword in SQL. It selects all elements of the array or slice that match the provided field and value. where takes three arguments:

1. array or a slice of maps or structs
2. key or field name
3. match value

{{< code file="layouts/_default/.html" >}} {{ range where .Data.Pages "Section" "post" }} {{ .Content }} {{ end }} {{< /code >}}

first

first works in a similar manner to the [limit keyword in SQL][limitkeyword]. It reduces the array to only the first N elements. It takes the array and number of elements as input. first takes two arguments:

1. array or slice of maps or structs
2. number of elements

{{< code file="layout/_default/section.html" >}} {{ range first 10 .Data.Pages }} {{ .Render "summary" }} {{ end }} {{< /code >}}

first and where Together

Using first and where together can be very powerful:

{{< code file="first-and-where-together.html" >}} {{ range first 5 (where .Data.Pages "Section" "post") }} {{ .Content }} {{ end }} {{< /code >}}