Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: Minor formatting fix in Pages Router SSG #54915

Merged
merged 2 commits into from Sep 2, 2023
Merged

docs: Minor formatting fix in Pages Router SSG #54915

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8548d44
Minor formatting fix in 02-static-site-generation.mdx
imageck Sep 2, 2023
9d778cd
Merge branch 'canary' into patch-1
leerob Sep 2, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...3-pages/01-building-your-application/02-rendering/02-static-site-generation.mdx
View file
Open in desktop
Expand Up @@ -108,7 +108,7 @@ However, which `id` you want to pre-render at build time might depend on externa

Later, you might add the second post with `id: 2`. Then you'd want to pre-render `posts/2` as well.

So your page **paths** that are pre-rendered depend on external data**.** To handle this, Next.js lets you `export` an `async` function called `getStaticPaths` from a dynamic page (`pages/posts/[id].js` in this case). This function gets called at build time and lets you specify which paths you want to pre-render.
So your page **paths** that are pre-rendered depend on external data. To handle this, Next.js lets you `export` an `async` function called `getStaticPaths` from a dynamic page (`pages/posts/[id].js` in this case). This function gets called at build time and lets you specify which paths you want to pre-render.

```jsx
// This function gets called at build time
Expand Down