docs/content/en/_common/methods/page/next-and-prev.md
Hugo determines the next and previous page by sorting the site's collection of regular pages according to this sorting hierarchy:
| Field | Precedence | Sort direction |
|---|---|---|
weight | 1 | descending |
date | 2 | descending |
linkTitle | 3 | descending |
path | 4 | descending |
The sorted page collection used to determine the next and previous page is independent of other page collections, which may lead to unexpected behavior.
For example, with this content structure:
content/
├── pages/
│ ├── _index.md
│ ├── page-1.md <-- front matter: weight = 10
│ ├── page-2.md <-- front matter: weight = 20
│ └── page-3.md <-- front matter: weight = 30
└── _index.md
And these templates:
{{ range .Pages.ByWeight }}
<h2><a href="{{ .RelPermalink }}">{{ .LinkTitle }}</a></h2>
{{ end }}
{{ with .Prev }}
<a href="{{ .RelPermalink }}">Previous</a>
{{ end }}
{{ with .Next }}
<a href="{{ .RelPermalink }}">Next</a>
{{ end }}
When you visit page-2:
Prev method points to page-3Next method points to page-1To reverse the meaning of next and previous you can change the sort direction in your project configuration, or use the Next and Prev methods on a Pages object for more flexibility.