Server-Side Rendering
Renders pages on the server before sending them to the client.
CoreConceptLab
34 Concepts Explained
Renders pages on the server before sending them to the client.
Pre-renders pages at build time for better performance.
Allows building backend APIs inside Next.js applications.
Routes are automatically created based on the file structure in the pages directory.
Introduced in Next.js 13, provides a new file-based routing system using the app directory.
Reusable templates that wrap around pages or routes.
Fetch data using getStaticProps, getServerSideProps, or client-side hooks.
Customize the HTML document structure using _document.js.
Override the default App component using _app.js for global styles and providers.
Deploy Next.js apps to platforms like Vercel, Netlify, or custom servers.
Run code before a request is completed, useful for authentication and redirects.
Optimize images automatically using the Next.js Image component.
Manage metadata such as titles and meta tags.
Organize routes into groups without affecting the URL structure.
Support multiple languages and locales with built-in i18n routing.
Serve images, fonts, and files from the public directory.
Improve performance by caching API responses.
Defines routes automatically based on the file system in the pages directory.
React components rendered on the server by default for better performance.
Renders pages on the server at request time for dynamic content.
Allows static pages to be updated after build without rebuilding the entire site.
Create routes with parameters using square brackets in the file name.
Custom error pages and error boundaries for better UX.
Manage SEO with metadata, canonical tags, and structured data.
React components rendered on the client, useful for interactive UI.
Pre-renders pages into static HTML at build time.
Define backend endpoints inside the pages/api directory.
Provides client-side navigation with prefetching.
Built-in loading states for routes and components.
Implement login and session management using libraries like NextAuth.js.
Manage environment-specific settings using .env files.
Test Next.js apps using Jest, React Testing Library, or Cypress.
Improve app speed using lazy loading, code splitting, and caching.
Add middleware to API routes for validation, logging, or authentication.