Unverified Commit b79052e0 authored by Aurora Scharff's avatar Aurora Scharff Committed by GitHub

docs: reframe prefetching around automatic vs. controllable behavior (#95896)

## Why

Follow-up to feedback on the 16.3 partial-prefetching docs. The blog's
"Fewer requests and lower bandwidth from visible Links" is an automatic,
framework-level benefit, not a dev-facing knob, yet the prefetching docs
still lead with the pre-Cache-Components model and never explain the
shared-shell behavior that produces it.

## What changed

- **`getting-started/linking-and-navigating`**: added an opt-in Cache
Components callout to the prefetching section. `<Link>` prefetches a
per-route App Shell, and many links to the same route reuse one shell,
so a page with many links makes fewer prefetch requests. The default
(non-Cache-Components) model description is unchanged.
- **`guides/prefetching`**: restructured into two halves:
- **What Next.js prefetches automatically** (static vs. dynamic,
automatic prefetch, the App Shell model, scheduling, client cache)
  - **Controlling prefetching** (manual, hover, extend/eject, disable)

Promoted and expanded the Cache Components / App Shell section as the
home for the shared-shell / fewer-requests story, and scoped the legacy
`staleTimes` tables to non-Cache-Components apps. All content-bearing
anchors are preserved (including `#extending-or-ejecting-link`, the only
one linked from other docs). Prose swept against the Vercel technical
writing style guide.

Docs-only. Related: DOC-6496.
parent 2a25442b
...@@ -95,6 +95,8 @@ By skipping or partially prefetching dynamic routes, Next.js avoids unnecessary ...@@ -95,6 +95,8 @@ By skipping or partially prefetching dynamic routes, Next.js avoids unnecessary
height="748" height="748"
/> />
> **Good to know:** See the [Prefetching guide](/docs/app/guides/prefetching) for the full behavior, including how to control prefetching per link and how it changes when you adopt [Partial Prefetching](/docs/app/guides/adopting-partial-prefetching).
To improve the navigation experience to dynamic routes, you can use [streaming](#streaming). To improve the navigation experience to dynamic routes, you can use [streaming](#streaming).
### Streaming ### Streaming
......
This diff is collapsed.
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