Next

PAGE.Next

page.Page

The behavior of the Prev and Next methods on a Page object is probably the reverse of what you expect.

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

When you visit page-2:

• The Prev method points to page-3
• The Next method points to page-1

{{ with .Next }}
  <a href="{{ .RelPermalink }}">Prev</a>
{{ end }}

{{ with .Prev }}
  <a href="{{ .RelPermalink }}">Next</a>
{{ end }}

Compare to Pages methods

The Next and Prev methods on a Pages object are more flexible than the Next and Prev methods on a Page object.

locally defined

Build the page collection every time you call PAGES.Next and PAGES.Prev. Navigation between pages is relative to the current page’s position within the local collection, independent of the global collection.

With a local collection, the navigation sort order is the same as the collection sort order.

globally defined

Build the page collection once, on a list page. Navigation between pages is relative to the current page’s position within the global collection.

With a global collection, the navigation sort order is fixed, using Hugo’s default sort order. In order of precedence:

1. Page weight
2. Page date (descending)
3. Page linkTitle, falling back to page title
4. Page file path if the page is backed by a file

For example, with a global collection sorted by title, the navigation sort order will use Hugo’s default sort order. This is probably not what you want or expect. For this reason, the Next and Prev methods on a Pages object are generally a better choice.