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.
Showing
This diff is collapsed.
Please
register
or
sign in
to comment