Repository navigation
docs: place shell param-order rule with build-time shells - #101680
Merged
Merged
Conversation
Contributor
Tests PassedCommit: 3263de1 |
github-actions
Bot
added
the
Documentation
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
| - `/tops/[product]`, `/shorts/[product]`: category header rendered, product shows fallback | ||
| - `/[category]/[product]`: both show fallback | ||
|
|
||
| Shells leave params open only from the end of the route. A URL can't leave a middle segment unknown, so there is no `/[category]/tee` shell. A visit with an unlisted category gets `/[category]/[product]`, whatever the product. |
Contributor
There was a problem hiding this comment.
what does it mean to "leave params open"
| A cached function's output is serialized into an **RSC payload**, at build time or at runtime. This payload is what everything else works from. Next.js renders it into HTML, keeps it in a server or remote store, or sends it to the browser, and [`cacheLife`](/docs/app/api-reference/functions/cacheLife) sets how long each copy stays fresh: | ||
|
|
||
| - **Prerendered HTML.** The payload is rendered to HTML and stored on disk when self-hosting, or in your platform's durable storage behind a CDN. That HTML is the [static shell](#prerendering) at build time and the concrete page after an [ISR](#incremental-static-regeneration) upgrade, with [`revalidate`](/docs/app/api-reference/functions/cacheLife#revalidate) and [`expire`](/docs/app/api-reference/functions/cacheLife#expire) controlling when it's rebuilt. | ||
| - **Prerendered output.** The payload is rendered to HTML, and both are stored on disk when self-hosting, or in your platform's durable storage behind a CDN. A direct visit gets the HTML, and a client navigation gets the RSC payload. Together they are the [static shell](#prerendering) at build time and the concrete page after an [ISR](#incremental-static-regeneration) upgrade, with [`revalidate`](/docs/app/api-reference/functions/cacheLife#revalidate) and [`expire`](/docs/app/api-reference/functions/cacheLife#expire) controlling when it's rebuilt. |
Contributor
There was a problem hiding this comment.
both what? payload and html?
aurorascharff
approved these changes
Nov 12, 2026
aurorascharff
approved these changes
Nov 12, 2026
aurorascharff
marked this pull request as ready for review
November 12, 2026 21:38
Contributor
|
Vercel Agent finished reviewing your changes and approved this pull request. Review steps (36.9s)Preparing the workspace 13.0s |
aurorascharff
approved these changes
Nov 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Possible follow-ups
Gaps surfaced while answering the discussion, to stack on top of this PR:
navigation()case is covered, in "Keep the prefetch static"./[category]/[product],/tops/[product]) regenerate on therevalidateandexpireof the content inside them. The docs cover only the static shell and the concrete page.generateStaticParamsproduces a shared shell on upgrade (/shoes/[product]), while one with it upgrades straight to the concrete URL.