Unverified Commit fa4c0def authored by Joseph's avatar Joseph Committed by GitHub

docs: ISR w/ Cache Components - `experimental.partialFallbacks` (#93299)

Continuation of: https://github.com/vercel/next.js/pull/92619

Completing the ISR with Cache Components story.

- [x] mention to cacheHandler and cacheHandlers - these work fine
together (aka with cacheComponents activated)
- [x] prefetch behavior - background revalidation
- [x] link to demo app
- [x] update version history in partialFallbacks config
- [x] align with partialFallbacks config flag removal

Closes: https://github.com/vercel/next.js/issues/91951
parent 5795d659
...@@ -13,6 +13,8 @@ description: Learn how to create or update static pages at runtime with Incremen ...@@ -13,6 +13,8 @@ description: Learn how to create or update static pages at runtime with Incremen
</details> </details>
> **Good to know**: This guide covers ISR without Cache Components. If you are using [`cacheComponents`](/docs/app/api-reference/config/next-config-js/cacheComponents), see [ISR with Cache Components](/docs/app/guides/incremental-static-regeneration-cache-components) instead.
Incremental Static Regeneration (ISR) enables you to: Incremental Static Regeneration (ISR) enables you to:
- Update static content without rebuilding the entire site - Update static content without rebuilding the entire site
......
...@@ -2,6 +2,9 @@ ...@@ -2,6 +2,9 @@
title: Building public pages title: Building public pages
description: Learn how to build public, "static" pages that share data across users, such as landing pages, list pages (products, blogs, etc.), marketing and news sites. description: Learn how to build public, "static" pages that share data across users, such as landing pages, list pages (products, blogs, etc.), marketing and news sites.
nav_title: Public pages nav_title: Public pages
related:
links:
- app/guides/incremental-static-regeneration-cache-components
--- ---
Public pages show the same content to every user. Common examples include landing pages, marketing pages, and product pages. Public pages show the same content to every user. Common examples include landing pages, marketing pages, and product pages.
......
...@@ -311,7 +311,7 @@ When using [Cache Components](/docs/app/getting-started/caching) with dynamic ro ...@@ -311,7 +311,7 @@ When using [Cache Components](/docs/app/getting-started/caching) with dynamic ro
> **Good to know**: If you don't know the actual param values at build time, you can return a placeholder param (e.g., `[{ slug: '__placeholder__' }]`) for validation, then handle it in your page with `notFound()`. However, this prevents build time validation from working effectively and may cause runtime errors. > **Good to know**: If you don't know the actual param values at build time, you can return a placeholder param (e.g., `[{ slug: '__placeholder__' }]`) for validation, then handle it in your page with `notFound()`. However, this prevents build time validation from working effectively and may cause runtime errors.
See the [dynamic routes section](/docs/app/api-reference/file-conventions/dynamic-routes#with-cache-components) for detailed walkthroughs. See the [dynamic routes section](/docs/app/api-reference/file-conventions/dynamic-routes#with-cache-components) for detailed walkthroughs, or [ISR with Cache Components](/docs/app/guides/incremental-static-regeneration-cache-components) for prerendering a subset of routes and serving fallback shells for the rest.
### With Route Handlers ### With Route Handlers
......
--- ---
title: cacheComponents title: cacheComponents
description: Learn how to enable the cacheComponents flag in Next.js. description: Learn how to enable the cacheComponents flag in Next.js.
related:
links:
- app/getting-started/caching
- app/guides/incremental-static-regeneration-cache-components
- app/api-reference/directives/use-cache
- app/api-reference/directives/use-cache-remote
--- ---
Cache Components enables component and function-level caching using the [`use cache`](/docs/app/api-reference/directives/use-cache) directive. Data fetching is dynamic by default, and you choose what to cache at the page, component, or function level. Next.js prerenders a static HTML shell that is served immediately while dynamic content streams in when ready, letting you mix static and dynamic content within a single route. Cache Components enables component and function-level caching using the [`use cache`](/docs/app/api-reference/directives/use-cache) directive. Data fetching is dynamic by default, and you choose what to cache at the page, component, or function level. Next.js prerenders a static HTML shell that is served immediately while dynamic content streams in when ready, letting you mix static and dynamic content within a single route.
......
...@@ -94,7 +94,7 @@ Custom path mappings that provide shorthand references for frequently used direc ...@@ -94,7 +94,7 @@ Custom path mappings that provide shorthand references for frequently used direc
## Incremental Static Regeneration (ISR) ## Incremental Static Regeneration (ISR)
A technique that allows you to update static content without rebuilding the entire site. ISR enables you to use static generation on a per-page basis while revalidating pages in the background as traffic comes in. Learn more in the [ISR guide](/docs/app/guides/incremental-static-regeneration). A technique that allows you to update static content without rebuilding the entire site. ISR enables you to use static generation on a per-page basis while revalidating pages in the background as traffic comes in. Learn more in the [ISR guide](/docs/app/guides/incremental-static-regeneration) or, when using Cache Components, [ISR with Cache Components](/docs/app/guides/incremental-static-regeneration-cache-components).
> **Good to know**: In Next.js, ISR is also known as [Revalidation](#revalidation). > **Good to know**: In Next.js, ISR is also known as [Revalidation](#revalidation).
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment