docs: remove Vercel mentions and improve deployment page #78557
Merged
+226
−265
Conversation
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
Closed
|
All broken links are now fixed, thank you! |
conico974
reviewed
Apr 25, 2025
|
Related follow-up PR: I need to document the currently experimental interface for extending the Example: #76687 |
serhalp
reviewed
Apr 25, 2025
docs/01-app/05-api-reference/05-config/01-next-config-js/incrementalCacheHandlerPath.mdx
Show resolved
Hide resolved
|
Thank you for the feedback @serhalp – I'm going to iterate here and merge this, and then will follow up to improve your point around managing version skew. This might be something which could influence the Deployment Adapter API design. |
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.
This PR prunes references to Vercel in the documentation. Some of the mentions were egregious and unneeded. Others were documenting specific behavior for how Next.js runs on Vercel, which is better suited for the Vercel documentation.
It also restructures our deployment documentation to remove any previous bias toward Vercel. Rather than separating self-hosting (Node.js server, Docker, static export) into its own section from managed platforms, it now lists them all together. Vercel is listed under "Adapters", alongside Netlify, Cloudflare, and AWS Amplify (in alphabetical order). These are the companies we're working with on the Deployment Adapters API, who currently maintain their own adapters and will eventually migrate to use this new API. We've started working on that API.
For different features in the docs, like ISR or Middleware, this PR also adds a new feature matrix that shows the different deployment options and whether this feature is supported. For example, features that require using the server are not supported with static exports. Additionally, when there is configuration possible (like changing the caching behavior of ISR) we link back to our guide which explains these options in detail.
This PR also updates the Middleware section of the self-hosting guide to mention Node.js runtime support.
I've also removed the "Managed Next.js (Vercel)" entry for the docs sidebar, as it is not necessary and Vercel should not have additional priority there over other providers.
Netlify has confirmed they're okay with the specific feature matrix link included in the adapters section, and I did my best to include the Cloudflare and Amplify versions based on their documentation. If any of the providers want to see changes to those links, please let me know and I'll open a PR.