hugo/content/en/functions/sort.md
Bjørn Erik Pedersen d3927310d5 Squashed 'docs/' changes from 39af43ef1..1798dc0d5
1798dc0d5 Update theme
403fa716e Update CLI documentation (#2092)
aade5a09e Correct media subtype example
53cd9dea6 netlify: Hugo 0.112.3
b78b86cb1 Add source/target warning to resources.Copy (#2091)
50c299729 netlify: Hugo 0.112.2
73197046f Change config.xxx to hugo.xxx throughout the documentation (#2090)
d489d4c6f Add hugo.WorkingDir to docs (#2089)
7487df809 Fix typos (#2088)
6d0572cd6 netlify: Hugo 0.112.1
6838600b2 netlify: Hugo 0.112.0
513e7a80f Merge branch 'tempv0.112.0'
91eb44275 Some more about 0.112.0
bd3b33a27 docs: Regen docshelper
fb3027daf docs: Regen CLI docs
8e7b8e987 Merge commit 'f96384a3b596f9bc0a3a035970b09b2c601f0ccb'
a942ceef4 tpl/tplimpl: Add img loading attribute to figure shortcode  (#10927)
0e0c7b25e tpl/urls: Return empty string when JoinPath has zero args
310ce949a tpl/urls: Add JoinPath template function
ae435ca77 tpl: Add math.Abs
f340139f8 Revert "Update syntax-highlighting.md (#10929)" (#10930)
917a0e24d Update syntax-highlighting.md (#10929)

git-subtree-dir: docs
git-subtree-split: 1798dc0d54ce048dd975863b490cd809ef14268a
2023-05-27 16:59:59 +02:00

3 KiB

title description categories signature menu keywords toc
sort Sorts slices, maps, and page collections.
functions
sort COLLECTION [KEY] [ORDER]
docs
parent
functions
ordering
sorting
lists
true

The KEY is optional when sorting slices in ascending order, otherwise it is required. When sorting slices, use the literal value in place of the KEY. See examples below.

The ORDER may be either asc (ascending) or desc (descending). The default sort order is ascending.

Sort a slice

The examples below assume this site configuration:

{{< code-toggle file="hugo" copy=false >}} [params] grades = ['b','a','c'] {{< /code-toggle >}}

Ascending order

Sort slice elements in ascending order using either of these constructs:

{{< code file="layouts/_default/single.html" copy=false >}} {{ sort site.Params.grades }} → [a b c] {{ sort site.Params.grades "value" "asc" }} → [a b c] {{< /code >}}

In the examples above, value is the KEY representing the value of the slice element.

Descending order

Sort slice elements in descending order:

{{< code file="layouts/_default/single.html" copy=false >}} {{ sort site.Params.grades "value" "desc" }} → [c b a] {{< /code >}}

In the example above, value is the KEY representing the value of the slice element.

Sort a map

The examples below assume this site configuration:

{{< code-toggle file="hugo" copy=false >}} [params.authors.a] firstName = "Marius" lastName = "Pontmercy" [params.authors.b] firstName = "Victor" lastName = "Hugo" [params.authors.c] firstName = "Jean" lastName = "Valjean" {{< /code-toggle >}}

{{% note %}} When sorting maps, the KEY argument must be lowercase. {{% /note %}}

Ascending order

Sort map objects in ascending order using either of these constructs:

{{< code file="layouts/_default/single.html" copy=false >}} {{ range sort site.Params.authors "firstname" }} {{ .firstName }} {{ end }}

{{ range sort site.Params.authors "firstname" "asc" }} {{ .firstName }} {{ end }} {{< /code >}}

These produce:

Jean Marius Victor

Descending order

Sort map objects in descending order:

{{< code file="layouts/_default/single.html" copy=false >}} {{ range sort site.Params.authors "firstname" "desc" }} {{ .firstName }} {{ end }} {{< /code >}}

This produces:

Victor Marius Jean

Sort a page collection

Although you can use the sort function to sort a page collection, Hugo provides built-in methods for sorting page collections by:

  • weight
  • linktitle
  • title
  • front matter parameter
  • date
  • expiration date
  • last modified date
  • publish date
  • length

In this contrived example, sort the site's regular pages by .Type in descending order:

{{< code file="layouts/_default/home.html" copy=false >}} {{ range sort site.RegularPages "Type" "desc" }}

{{ .Title }}

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