Meta-frameworks for Frontend Developers
Meta-frameworks such as Next.js and React Router add routing, data loading, server rendering and build tooling on top of React. They let a page be rendered on the server, at build time or in the browser, and handle code splitting, so apps load faster and are easier for search engines to read.
Stage: UI Frameworks · Part of the Frontend Developer roadmap · Last reviewed 19 November 2026
What to learn in Meta-frameworks
- Create routes and nested layouts using file-based routing
- Choose between static, server and client rendering for a page
- Fetch data on the server and pass it to components
- Use loaders and actions in React Router to read and write data
- Explain hydration and why mismatched markup causes errors
Meta-frameworks interview questions
What is the difference between SSR and SSG?
Server-side rendering builds the HTML on each request, so content is always fresh but costs server time. Static site generation builds the HTML once at build time and serves it from a CDN, which is fast but needs a rebuild or revalidation to update.
What is hydration in React?
Hydration is when React attaches event handlers and state to HTML that the server already rendered. The client renders the same tree and reuses the existing DOM. If the server and client output differ, React warns about a hydration mismatch.
Where Meta-frameworks fits in the Frontend Developer roadmap
Meta-frameworks belongs to the UI Frameworks stage (beginner level), which takes about 6 hours. Component thinking with React, plus how the alternatives differ.
Other units in this stage
Back to the full Frontend Developer roadmap