Next.js — App Router fluency
Architecture, entry points, routing, and data-flow patterns in the Next.js App Router mental model.
Questions
Plain-language prompts grounded in this codebase. Open any question for a full answer page.
- ClozeL1
In the App Router, routes are defined by folders under the app directory.
- ClozeL1
Shared UI that wraps child segments is defined in layout.tsx.
- ClozeL1
By default, components in the App Router are Server Components.
- ClozeL1
HTTP API endpoints in App Router are defined in route.ts files.
- ClozeL1
SEO titles and descriptions can be exported via the metadata object or generateMetadata.
- ClozeL1
Request interception before a route renders can be done in middleware.ts at the project root (or src/).
- ClozeL1
Cached data can be invalidated with revalidatePath or revalidateTag.
- ClozeL1
The Next.js repo is a monorepo; the framework package lives under packages/next.
- ClozeL1
Official examples that show feature patterns live in the examples directory.