What transfers
Your React experience already covers this
React project structure
→ Next.js project structure
Start by mapping where application entry points, reusable modules, configuration, and tests live so the new stack feels navigable.
React state and data flow
→ Next.js state and data flow
Compare how data enters the system, how it is transformed, and where side effects belong before translating syntax.
React production conventions
→ Next.js production conventions
Focus on logging, errors, build output, deployment shape, and performance defaults because those decide whether a stack switch works in real teams.
What's new
Where Next.js asks you to think differently
Next.js is built around routes, layouts, server components, client components, caching, and deployment boundaries. Expect to spend real time on:
App Router
server and client components
caching
metadata and rendering modes
Sample topics
3 of the 17 curated topics on this roadmap
Project Setup & Routing
Imagine you are starting a new E-Commerce Platform and deciding between a plain React SPA with React Router and a Next.js application. The key difference hits you immediately — in React you configure routes manually in code, while Next.js…
Server Components vs Client Components
Imagine you are working on a Banking Application's account dashboard. Some parts — the account balance fetched from the database, the transaction history list — can be rendered on the server with no JavaScript sent to the browser. Other…
Data Fetching Patterns
Imagine you are working on a CRM's contact detail page. The contact's basic info rarely changes (good for static generation), the activity feed updates every few minutes (good for periodic revalidation), and the live online status changes…
14 more topics, in order, with side-by-side React and Next.js code, are in your roadmap after signup.
Create a free account to see your full roadmapOther switches
Related stack switches
Want the longer concept-by-concept comparison? Read the React to Next.js overview.