aboutsummaryrefslogtreecommitdiffhomepage
path: root/content/en/methods/page/Next.md
diff options
context:
space:
mode:
Diffstat (limited to 'content/en/methods/page/Next.md')
-rw-r--r--content/en/methods/page/Next.md40
1 files changed, 2 insertions, 38 deletions
diff --git a/content/en/methods/page/Next.md b/content/en/methods/page/Next.md
index 57fc1f2f8..ff0525700 100644
--- a/content/en/methods/page/Next.md
+++ b/content/en/methods/page/Next.md
@@ -1,6 +1,6 @@
---
title: Next
-description: Returns the next page in a global page collection, relative to the given page.
+description: Returns the next page in a site's collection of regular pages, relative to the current page.
categories: []
keywords: []
action:
@@ -12,42 +12,6 @@ action:
- methods/pages/Prev
returnType: page.Page
signatures: [PAGE.Next]
-toc: true
---
-The behavior of the `Prev` and `Next` methods on a `Page` object is probably the reverse of what you expect.
-
-With this content structure:
-
-```text
-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
-
-{{% note %}}
-Use the opposite label in your navigation links as shown in the example below.
-{{% /note %}}
-
-```go-html-template
-{{ with .Next }}
- <a href="{{ .RelPermalink }}">Prev</a>
-{{ end }}
-
-{{ with .Prev }}
- <a href="{{ .RelPermalink }}">Next</a>
-{{ end }}
-```
-
-## Compare to Pages methods
-
-{{% include "methods/_common/next-prev-on-page-vs-next-prev-on-pages.md" %}}
+{{% include "methods/page/_common/next-and-prev.md" %}}