Next.js / Basic: routes and execution boundaries
Next.js β Basic: routes and execution boundaries
Connect file routing, React boundaries, source reads and explicit form mutations.
What you will learn
- Separate execution environment, rendering time and request input.
- Project public data and validate server mutation intent.
App Router rendering and application boundaries
Separate route composition, server rendering, browser interaction and domain authority before choosing component boundaries.
Start learningFile routes, layouts and async parameters
Compose route segments and shared layouts while awaiting request parameters under the selected Next 16 contract.
Start learningServer/client boundaries and serializable props
Keep browser interaction small and pass only approved data across the React server/client boundary.
Start learningNavigation, URL state and safe links
Represent shareable state in the URL and preserve safe navigation semantics across links, hooks and prefetch.
Start learningServer data fetching, errors and source shape
Read authorized data through a server-only boundary and distinguish transport success from a valid domain record.
Start learningForms, Server Actions and validated mutations
Treat a Server Action as a callable mutation boundary with untrusted input, current authority and a deliberate result contract.
Start learning