summaryrefslogtreecommitdiff
path: root/docs/src
diff options
context:
space:
mode:
authorGravatar FredKSchott <FredKSchott@users.noreply.github.com> 2021-08-11 22:05:17 +0000
committerGravatar GitHub Actions <actions@github.com> 2021-08-11 22:05:17 +0000
commitb63960f514851ff6d61d722fd698a36020ddc347 (patch)
tree878973594f55e1b8d1528008a74fa7e4a11cb419 /docs/src
parent0f0cc2b9d83ffeee125b85c95d2d51080f21074d (diff)
downloadastro-b63960f514851ff6d61d722fd698a36020ddc347.tar.gz
astro-b63960f514851ff6d61d722fd698a36020ddc347.tar.zst
astro-b63960f514851ff6d61d722fd698a36020ddc347.zip
[ci] yarn format
Diffstat (limited to 'docs/src')
-rw-r--r--docs/src/pages/core-concepts/routing.md2
-rw-r--r--docs/src/pages/guides/pagination.md5
2 files changed, 2 insertions, 5 deletions
diff --git a/docs/src/pages/core-concepts/routing.md b/docs/src/pages/core-concepts/routing.md
index 712a2fba8..42ed0d35d 100644
--- a/docs/src/pages/core-concepts/routing.md
+++ b/docs/src/pages/core-concepts/routing.md
@@ -24,8 +24,6 @@ Sometimes, you need to generate many URLs from a single page component. Astro us
An important thing to keep in mind: Astro is a static site builder. There is no Astro server to run in production, which means that every page must be built ahead of time. Pages that use dynamic routes must export a `getStaticPaths()` function which will tell Astro exactly what pages to generate. Learn more by viewing the complete [API Reference](/reference/api-reference#getstaticpaths).
-
-
### Named parameters
Dynamic parameters are encoded into the filename using `[bracket]` notation:
diff --git a/docs/src/pages/guides/pagination.md b/docs/src/pages/guides/pagination.md
index bcce12e6b..8c1b0e638 100644
--- a/docs/src/pages/guides/pagination.md
+++ b/docs/src/pages/guides/pagination.md
@@ -7,7 +7,7 @@ Astro supports built-in, automatic pagination for large collections of data that
## When to use pagination
-Pagination is only useful when you need to generate multiple, numbered pages from a larger data set.
+Pagination is only useful when you need to generate multiple, numbered pages from a larger data set.
If all of your data can fit on a single page then you should consider using a static [page component](/core-concepts/astro-pages) instead.
@@ -72,7 +72,6 @@ The `page` prop has several useful properties, but the most important one is `pa
The `page` prop includes other helpful metadata, like `page.url.next`, `page.url.prev`, `page.total`, and more. See our [API reference](/reference/api-reference#the-pagination-page-prop) for the full `page` interface.
-
## Nested pagination
A more advanced use-case for pagination is **nested pagination.** This is when pagination is combined with other dynamic route params. You can use nested pagination to group your paginated collection by some property or tag.
@@ -90,7 +89,7 @@ Nested pagination works by returning an array of `paginate()` results from `getS
---
// Example: /src/pages/[tag]/[page].astro
export function getStaticPaths({paginate}) {
- const allTags = ['red', 'blue', 'green'];
+ const allTags = ['red', 'blue', 'green'];
const allPosts = Astro.fetchContent('../../posts/*.md');
// For every tag, return a paginate() result.
// Make sure that you pass `{params: {tag}}` to `paginate()`