docs: add Thinking in Next.js guide#93410
Closed
aurorascharff wants to merge 25 commits into
Closed
Conversation
Made-with: Cursor
github-actions
Bot
added
created-by: Next.js DevEx team
Contributor
Failing CI jobsCommit: cd0773c | About building and testing Next.js |
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
Update thinking-in-nextjs.mdx
Contributor
Author
|
Superseded by #93442 (same content, branch now lives on vercel/next.js instead of my fork). |
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
1 participant
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.
What?
A new "Thinking in Next.js" guide that walks through building a small Vercel-style projects dashboard one decision at a time, mirroring the structure of React's Thinking in React.
Why?
Help readers form a mental model of App Router apps as components that decide where their data comes from, what gets reused, and what stays in the browser. The progression covers the eight choices each component answers: hierarchy, static JSX, data fetching, streaming, mutations, client interactivity, caching, and prefetching.
How?
docs/01-app/02-guides/thinking-in-nextjs.mdx, sitting alongsideinstant-navigation.mdx,forms.mdx, etc.vercel-labs/thinking-in-nextjswith one folder per guide step, deployed under*.labs.vercel.devand embedded via<Demo />in each step. Final step: https://thinking-in-nextjs.labs.vercel.dev//docs/guides/thinking-in-nextjs/.