Docs IA 2.0: Move ISR page to guides (#79283)

delbaoliveira · web-flow · commit f6081d019c13 · 2025-05-21T08:34:00.000+01:00
Closes: https://linear.app/vercel/issue/DOC-4670/isr Redirects: vercel/front#45793
diff --git a/docs/01-app/01-getting-started/08-partial-prerendering.mdx b/docs/01-app/01-getting-started/08-partial-prerendering.mdx
@@ -34,7 +34,7 @@ To understand Partial Prerendering, it helps to be familiar with the rendering s
 
 ### Static Rendering
 
-With Static Rendering, HTML is generated ahead of time—either at build time or through [revalidation](/docs/app/building-your-application/data-fetching/incremental-static-regeneration). The result is cached and shared across users and requests.
+With Static Rendering, HTML is generated ahead of time—either at build time or through [revalidation](/docs/app/guides/incremental-static-regeneration). The result is cached and shared across users and requests.
 
 In Partial Prerendering, Next.js prerenders a **static shell** for a route. This can include the layout and any other components that don't depend on request-time data.
 
diff --git a/docs/01-app/02-guides/incremental-static-regeneration.mdx b/docs/01-app/02-guides/incremental-static-regeneration.mdx
@@ -1,5 +1,6 @@
 ---
-title: Incremental Static Regeneration (ISR)
+title: How to implement Incremental Static Regeneration (ISR)
+nav_title: ISR
 description: Learn how to create or update static pages at runtime with Incremental Static Regeneration.
 ---
 
diff --git a/docs/01-app/02-guides/index.mdx b/docs/01-app/02-guides/index.mdx
@@ -12,8 +12,8 @@ description: Learn how to implement common UI patterns and use cases using Next.
 
 ### Revalidating Data
 
-- [Using ISR to revalidate data after a certain time](/docs/app/building-your-application/data-fetching/incremental-static-regeneration#time-based-revalidation)
-- [Using ISR to revalidate data on-demand](/docs/app/building-your-application/data-fetching/incremental-static-regeneration#on-demand-revalidation-with-revalidatepath)
+- [Using ISR to revalidate data after a certain time](/docs/app/guides/incremental-static-regeneration#time-based-revalidation)
+- [Using ISR to revalidate data on-demand](/docs/app/guides/incremental-static-regeneration#on-demand-revalidation-with-revalidatepath)
 
 ### Forms
 
diff --git a/docs/01-app/02-guides/production-checklist.mdx b/docs/01-app/02-guides/production-checklist.mdx
@@ -74,7 +74,7 @@ While building your application, we recommend using the following features to en
 
 - **[API Routes](/docs/pages/building-your-application/routing/api-routes):** Use Route Handlers to access your backend resources, and prevent sensitive secrets from being exposed to the client.
 - **[Data Caching](/docs/pages/building-your-application/data-fetching/get-static-props):** Verify whether your data requests are being cached or not, and opt into caching, where appropriate. Ensure requests that don't use `getStaticProps` are cached where appropriate.
-- **[Incremental Static Regeneration](/docs/pages/building-your-application/data-fetching/incremental-static-regeneration):** Use Incremental Static Regeneration to update static pages after they've been built, without rebuilding your entire site.
+- **[Incremental Static Regeneration](/docs/pages/guides/incremental-static-regeneration):** Use Incremental Static Regeneration to update static pages after they've been built, without rebuilding your entire site.
 - **[Static Images](/docs/pages/api-reference/file-conventions/public-folder):** Use the `public` directory to automatically cache your application's static assets, e.g. images.
 
 </PagesOnly>
diff --git a/docs/01-app/02-guides/self-hosting.mdx b/docs/01-app/02-guides/self-hosting.mdx
@@ -85,7 +85,7 @@ This allows you to use a singular Docker image that can be promoted through mult
 
 Next.js can cache responses, generated static pages, build outputs, and other static assets like images, fonts, and scripts.
 
-Caching and revalidating pages (with [Incremental Static Regeneration](/docs/app/building-your-application/data-fetching/incremental-static-regeneration)) use the **same shared cache**. By default, this cache is stored to the filesystem (on disk) on your Next.js server. **This works automatically when self-hosting** using both the Pages and App Router.
+Caching and revalidating pages (with [Incremental Static Regeneration](/docs/app/guides/incremental-static-regeneration)) use the **same shared cache**. By default, this cache is stored to the filesystem (on disk) on your Next.js server. **This works automatically when self-hosting** using both the Pages and App Router.
 
 You can configure the Next.js cache location if you want to persist cached pages and data to durable storage, or share the cache across multiple containers or instances of your Next.js application.
 
diff --git a/docs/01-app/02-guides/static-exports.mdx b/docs/01-app/02-guides/static-exports.mdx
@@ -285,7 +285,7 @@ Features that require a Node.js server, or dynamic logic that cannot be computed
 - [Redirects](/docs/app/api-reference/config/next-config-js/redirects)
 - [Headers](/docs/app/api-reference/config/next-config-js/headers)
 - [Middleware](/docs/app/building-your-application/routing/middleware)
-- [Incremental Static Regeneration](/docs/app/building-your-application/data-fetching/incremental-static-regeneration)
+- [Incremental Static Regeneration](/docs/app/guides/incremental-static-regeneration)
 - [Image Optimization](/docs/app/api-reference/components/image) with the default `loader`
 - [Draft Mode](/docs/app/guides/draft-mode)
 - [Server Actions](/docs/app/building-your-application/data-fetching/server-actions-and-mutations)
@@ -307,7 +307,7 @@ export const dynamic = 'error'
 - [Redirects](/docs/pages/api-reference/config/next-config-js/redirects)
 - [Headers](/docs/pages/api-reference/config/next-config-js/headers)
 - [Middleware](/docs/pages/building-your-application/routing/middleware)
-- [Incremental Static Regeneration](/docs/pages/building-your-application/data-fetching/incremental-static-regeneration)
+- [Incremental Static Regeneration](/docs/pages/guides/incremental-static-regeneration)
 - [Image Optimization](/docs/pages/api-reference/components/image) with the default `loader`
 - [Draft Mode](/docs/pages/guides/draft-mode)
 - [`getStaticPaths` with `fallback: true`](/docs/pages/api-reference/functions/get-static-paths#fallback-true)
diff --git a/docs/01-app/03-building-your-application/01-routing/13-route-handlers.mdx b/docs/01-app/03-building-your-application/01-routing/13-route-handlers.mdx
@@ -127,7 +127,7 @@ The following examples show how to combine Route Handlers with other Next.js API
 
 ### Revalidating Cached Data
 
-You can [revalidate cached data](/docs/app/building-your-application/data-fetching/incremental-static-regeneration) using Incremental Static Regeneration (ISR):
+You can [revalidate cached data](/docs/app/guides/incremental-static-regeneration) using Incremental Static Regeneration (ISR):
 
 ```ts filename="app/posts/route.ts" switcher
 export const revalidate = 60
diff --git a/docs/01-app/03-building-your-application/02-data-fetching/01-fetching.mdx b/docs/01-app/03-building-your-application/02-data-fetching/01-fetching.mdx
@@ -87,7 +87,7 @@ export default async function Page() {
 }
 ```
 
-If you are not using any [Dynamic APIs](/docs/app/getting-started/partial-prerendering#dynamic-rendering) anywhere else in this route, it will be prerendered during `next build` to a static page. The data can then be updated using [Incremental Static Regeneration](/docs/app/building-your-application/data-fetching/incremental-static-regeneration).
+If you are not using any [Dynamic APIs](/docs/app/getting-started/partial-prerendering#dynamic-rendering) anywhere else in this route, it will be prerendered during `next build` to a static page. The data can then be updated using [Incremental Static Regeneration](/docs/app/guides/incremental-static-regeneration).
 
 To prevent the page from prerendering, you can add the following to your file:
 
@@ -131,7 +131,7 @@ export default async function Page() {
 }
 ```
 
-If you are not using any [Dynamic APIs](/docs/app/getting-started/partial-prerendering#dynamic-rendering) anywhere else in this route, it will be prerendered during `next build` to a static page. The data can then be updated using [Incremental Static Regeneration](/docs/app/building-your-application/data-fetching/incremental-static-regeneration).
+If you are not using any [Dynamic APIs](/docs/app/getting-started/partial-prerendering#dynamic-rendering) anywhere else in this route, it will be prerendered during `next build` to a static page. The data can then be updated using [Incremental Static Regeneration](/docs/app/guides/incremental-static-regeneration).
 
 To prevent the page from prerendering, you can add the following to your file:
 
@@ -259,7 +259,7 @@ export default async function Page() {
 }
 ```
 
-This example caches the result of the database query for 1 hour (3600 seconds). It also adds the cache tag `posts` which can then be invalidated with [Incremental Static Regeneration](/docs/app/building-your-application/data-fetching/incremental-static-regeneration).
+This example caches the result of the database query for 1 hour (3600 seconds). It also adds the cache tag `posts` which can then be invalidated with [Incremental Static Regeneration](/docs/app/guides/incremental-static-regeneration).
 
 ### Reusing data across multiple functions
 
@@ -390,7 +390,7 @@ export const getPost = cache(async (id) => {
 
 ### Revalidating cached data
 
-Learn more about revalidating cached data with [Incremental Static Regeneration](/docs/app/building-your-application/data-fetching/incremental-static-regeneration).
+Learn more about revalidating cached data with [Incremental Static Regeneration](/docs/app/guides/incremental-static-regeneration).
 
 ## Patterns
 
diff --git a/docs/01-app/05-api-reference/05-config/01-next-config-js/assetPrefix.mdx b/docs/01-app/05-api-reference/05-config/01-next-config-js/assetPrefix.mdx
@@ -71,6 +71,6 @@ While `assetPrefix` covers requests to `_next/static`, it does not influence the
 
 - Files in the [public](/docs/pages/api-reference/file-conventions/public-folder) folder; if you want to serve those assets over a CDN, you'll have to introduce the prefix yourself
 - `/_next/data/` requests for `getServerSideProps` pages. These requests will always be made against the main domain since they're not static.
-- `/_next/data/` requests for `getStaticProps` pages. These requests will always be made against the main domain to support [Incremental Static Generation](/docs/pages/building-your-application/data-fetching/incremental-static-regeneration), even if you're not using it (for consistency).
+- `/_next/data/` requests for `getStaticProps` pages. These requests will always be made against the main domain to support [Incremental Static Generation](/docs/pages/guides/incremental-static-regeneration), even if you're not using it (for consistency).
 
 </PagesOnly>
diff --git a/docs/01-app/05-api-reference/05-config/01-next-config-js/incrementalCacheHandlerPath.mdx b/docs/01-app/05-api-reference/05-config/01-next-config-js/incrementalCacheHandlerPath.mdx
@@ -43,7 +43,7 @@ Returns `Promise<void>`.
 | --------- | ---------------------- | ----------------------------- |
 | `tag`     | `string` or `string[]` | The cache tags to revalidate. |
 
-Returns `Promise<void>`. Learn more about [revalidating data](/docs/app/building-your-application/data-fetching/incremental-static-regeneration) or the [`revalidateTag()`](/docs/app/api-reference/functions/revalidateTag) function.
+Returns `Promise<void>`. Learn more about [revalidating data](/docs/app/guides/incremental-static-regeneration) or the [`revalidateTag()`](/docs/app/api-reference/functions/revalidateTag) function.
 
 ### `resetRequestCache()`
 
diff --git a/docs/02-pages/02-guides/draft-mode.mdx b/docs/02-pages/02-guides/draft-mode.mdx
@@ -159,7 +159,7 @@ Then, send a request to `/api/disable-draft` to invoke the API Route. If calling
 
 Draft Mode works with `getServerSideProps`, and is available as a `draftMode` key in the [`context`](/docs/pages/api-reference/functions/get-server-side-props#context-parameter) object.
 
-> **Good to know**: You shouldn't set the `Cache-Control` header when using Draft Mode because it cannot be bypassed. Instead, we recommend using [ISR](/docs/pages/building-your-application/data-fetching/incremental-static-regeneration).
+> **Good to know**: You shouldn't set the `Cache-Control` header when using Draft Mode because it cannot be bypassed. Instead, we recommend using [ISR](/docs/pages/guides/incremental-static-regeneration).
 
 ### Works with API Routes
 
diff --git a/docs/02-pages/02-guides/incremental-static-regeneration.mdx b/docs/02-pages/02-guides/incremental-static-regeneration.mdx
@@ -1,7 +1,8 @@
 ---
-title: Incremental Static Regeneration (ISR)
+title: How to implement Incremental Static Regeneration (ISR)
+nav_title: ISR
 description: Learn how to create or update static pages at runtime with Incremental Static Regeneration.
-source: app/building-your-application/data-fetching/incremental-static-regeneration
+source: app/guides/incremental-static-regeneration
 ---
 
 {/* DO NOT EDIT. The content of this doc is generated from the source above. To edit the content of this page, navigate to the source page in your editor. You can use the `<PagesOnly>Content</PagesOnly>` component to add content that is specific to the Pages Router. Any shared content should not be wrapped in a component. */}
diff --git a/docs/02-pages/02-guides/preview-mode.mdx b/docs/02-pages/02-guides/preview-mode.mdx
@@ -230,7 +230,7 @@ You can pass an object to `setPreviewData` and have it be available in `getStati
 
 The preview mode works on `getServerSideProps` as well. It will also be available on the `context` object containing `preview` and `previewData`.
 
-> **Good to know**: You shouldn't set the `Cache-Control` header when using Preview Mode because it cannot be bypassed. Instead, we recommend using [ISR](/docs/pages/building-your-application/data-fetching/incremental-static-regeneration).
+> **Good to know**: You shouldn't set the `Cache-Control` header when using Preview Mode because it cannot be bypassed. Instead, we recommend using [ISR](/docs/pages/guides/incremental-static-regeneration).
 
 ### Works with API Routes
 
diff --git a/docs/02-pages/03-building-your-application/01-routing/07-api-routes.mdx b/docs/02-pages/03-building-your-application/01-routing/07-api-routes.mdx
@@ -177,7 +177,7 @@ The included helpers are:
 - `res.json(body)` - Sends a JSON response. `body` must be a [serializable object](https://developer.mozilla.org/docs/Glossary/Serialization)
 - `res.send(body)` - Sends the HTTP response. `body` can be a `string`, an `object` or a `Buffer`
 - `res.redirect([status,] path)` - Redirects to a specified path or URL. `status` must be a valid [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). If not specified, `status` defaults to "307" "Temporary redirect".
-- `res.revalidate(urlPath)` - [Revalidate a page on demand](/docs/pages/building-your-application/data-fetching/incremental-static-regeneration#on-demand-revalidation-with-revalidatepath) using `getStaticProps`. `urlPath` must be a `string`.
+- `res.revalidate(urlPath)` - [Revalidate a page on demand](/docs/pages/guides/incremental-static-regeneration#on-demand-revalidation-with-revalidatepath) using `getStaticProps`. `urlPath` must be a `string`.
 
 ### Setting the status code of a response
 
diff --git a/docs/02-pages/03-building-your-application/02-rendering/05-client-side-rendering.mdx b/docs/02-pages/03-building-your-application/02-rendering/05-client-side-rendering.mdx
@@ -6,7 +6,7 @@ related:
   links:
     - pages/building-your-application/rendering/server-side-rendering
     - pages/building-your-application/rendering/static-site-generation
-    - pages/building-your-application/data-fetching/incremental-static-regeneration
+    - pages/guides/incremental-static-regeneration
     - app/building-your-application/routing/loading-ui-and-streaming
 ---
 
diff --git a/docs/02-pages/03-building-your-application/03-data-fetching/01-get-static-props.mdx b/docs/02-pages/03-building-your-application/03-data-fetching/01-get-static-props.mdx
@@ -61,9 +61,9 @@ You should use `getStaticProps` if:
 - `getStaticProps` runs in the background when using [`fallback: true`](/docs/pages/api-reference/functions/get-static-paths#fallback-true)
 - `getStaticProps` is called before initial render when using [`fallback: blocking`](/docs/pages/api-reference/functions/get-static-paths#fallback-blocking)
 - `getStaticProps` runs in the background when using `revalidate`
-- `getStaticProps` runs on-demand in the background when using [`revalidate()`](/docs/pages/building-your-application/data-fetching/incremental-static-regeneration#on-demand-revalidation-with-revalidatepath)
+- `getStaticProps` runs on-demand in the background when using [`revalidate()`](/docs/pages/guides/incremental-static-regeneration#on-demand-revalidation-with-revalidatepath)
 
-When combined with [Incremental Static Regeneration](/docs/pages/building-your-application/data-fetching/incremental-static-regeneration), `getStaticProps` will run in the background while the stale page is being revalidated, and the fresh page served to the browser.
+When combined with [Incremental Static Regeneration](/docs/pages/guides/incremental-static-regeneration), `getStaticProps` will run in the background while the stale page is being revalidated, and the fresh page served to the browser.
 
 `getStaticProps` does not have access to the incoming request (such as query parameters or HTTP headers) as it generates static HTML. If you need access to the request for your page, consider using [Middleware](/docs/pages/building-your-application/routing/middleware) in addition to `getStaticProps`.
 
diff --git a/docs/02-pages/03-building-your-application/03-data-fetching/03-get-server-side-props.mdx b/docs/02-pages/03-building-your-application/03-data-fetching/03-get-server-side-props.mdx
@@ -105,4 +105,4 @@ export async function getServerSideProps({ req, res }) {
 }
 ```
 
-However, before reaching for `cache-control`, we recommend seeing if [`getStaticProps`](/docs/pages/building-your-application/data-fetching/get-static-props) with [ISR](/docs/pages/building-your-application/data-fetching/incremental-static-regeneration) is a better fit for your use case.
+However, before reaching for `cache-control`, we recommend seeing if [`getStaticProps`](/docs/pages/building-your-application/data-fetching/get-static-props) with [ISR](/docs/pages/guides/incremental-static-regeneration) is a better fit for your use case.
diff --git a/docs/02-pages/04-api-reference/03-functions/get-static-paths.mdx b/docs/02-pages/04-api-reference/03-functions/get-static-paths.mdx
@@ -177,7 +177,7 @@ Shortly after, `getStaticProps` finishes and the page will be rendered with the
 
 This ensures that users always have a fast experience while preserving fast builds and the benefits of Static Generation.
 
-`fallback: true` will not _update_ generated pages, for that take a look at [Incremental Static Regeneration](/docs/pages/building-your-application/data-fetching/incremental-static-regeneration).
+`fallback: true` will not _update_ generated pages, for that take a look at [Incremental Static Regeneration](/docs/pages/guides/incremental-static-regeneration).
 
 ### `fallback: 'blocking'`
 
@@ -190,7 +190,7 @@ If `fallback` is `'blocking'`, new paths not returned by `getStaticPaths` will w
 - When complete, the browser receives the `HTML` for the generated path. From the user’s perspective, it will transition from "the browser is requesting the page" to "the full page is loaded". There is no flash of loading/fallback state.
 - At the same time, Next.js adds this path to the list of pre-rendered pages. Subsequent requests to the same path will serve the generated page, like other pages pre-rendered at build time.
 
-`fallback: 'blocking'` will not _update_ generated pages by default. To update generated pages, use [Incremental Static Regeneration](/docs/pages/building-your-application/data-fetching/incremental-static-regeneration) in conjunction with `fallback: 'blocking'`.
+`fallback: 'blocking'` will not _update_ generated pages by default. To update generated pages, use [Incremental Static Regeneration](/docs/pages/guides/incremental-static-regeneration) in conjunction with `fallback: 'blocking'`.
 
 > **Good to know**: `fallback: 'blocking'` is not supported when using [`output: 'export'`](/docs/pages/guides/static-exports).
 
@@ -253,7 +253,7 @@ export default Post
 | Version   | Changes                                                                                                                                                                                                     |
 | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `v13.4.0` | [App Router](/docs/app/building-your-application/data-fetching) is now stable with simplified data fetching, including [`generateStaticParams()`](/docs/app/api-reference/functions/generate-static-params) |
-| `v12.2.0` | [On-Demand Incremental Static Regeneration](/docs/pages/building-your-application/data-fetching/incremental-static-regeneration#on-demand-revalidation-with-revalidatepath) is stable.                      |
-| `v12.1.0` | [On-Demand Incremental Static Regeneration](/docs/pages/building-your-application/data-fetching/incremental-static-regeneration#on-demand-revalidation-with-revalidatepath) added (beta).                   |
-| `v9.5.0`  | Stable [Incremental Static Regeneration](/docs/pages/building-your-application/data-fetching/incremental-static-regeneration)                                                                               |
+| `v12.2.0` | [On-Demand Incremental Static Regeneration](/docs/pages/guides/incremental-static-regeneration#on-demand-revalidation-with-revalidatepath) is stable.                                                       |
+| `v12.1.0` | [On-Demand Incremental Static Regeneration](/docs/pages/guides/incremental-static-regeneration#on-demand-revalidation-with-revalidatepath) added (beta).                                                    |
+| `v9.5.0`  | Stable [Incremental Static Regeneration](/docs/pages/guides/incremental-static-regeneration)                                                                                                                |
 | `v9.3.0`  | `getStaticPaths` introduced.                                                                                                                                                                                |
diff --git a/docs/02-pages/04-api-reference/03-functions/get-static-props.mdx b/docs/02-pages/04-api-reference/03-functions/get-static-props.mdx
