---
name: next-js-rendering-strategies-453d60617d1a
description: SSG, SSR, ISR, Streaming, and Partial Prerendering (PPR).
metadata:
  labels: [nextjs, rendering, isr, ssr, ssg]
  triggers:
    files: ['**/page.tsx', '**/layout.tsx']
    keywords: [generateStaticParams, dynamic, dynamicParams, PPR, streaming]
---

# Rendering Strategies (App Router)

## **Priority: P0 (CRITICAL)**

Understanding how Next.js renders content determines performance and cost.

## Strategy Selection Matrix (Scaling & Cost)

| Strategy | Ideal For              | Data Freshness       | Performance (TTFB)          | Scaling Risk                         |
| :------- | :--------------------- | :------------------- | :-------------------------- | :----------------------------------- |
| **SSG**  | Marketing, Docs, Blogs | Build Time           | **Instant** (CDN)           | **None**                             |
| **ISR**  | E-commerce, CMS        | Periodic (e.g., 60s) | **Instant** (CDN)           | **Low** (Background Rebuilds)        |
| **SSR**  | Dashboards, Auth Gates | Real-Time (Request)  | **Slow** (Waits for Server) | **Critical** (1 Request = 1 Compute) |
| **PPR**  | Personalized Apps      | Hybrid               | **Instant** (Shell)         | **Medium** (Streaming Holes)         |

## Scaling Patterns

### 1. The "Static Shell" Pattern (Preferred)

- **Goal**: Make most of the page **Static** to hit the CDN cache.
- **Pattern**:
  - Render the generic layout (Logo, Footer, Navigation) as **Static**.
  - Wrap personalized/slow components (User Profile, Cart Count, Recommendations) in `<Suspense>`.
- **Result**: **TTFB (Time to First Byte)** is near-instant (~50ms) because the shell is cached. User perception is fast, even if DB is slow.

### 2. Avoiding "SSR Waterfalls"

- **Problem**: In naive SSR, the server waits for _every_ fetch to finish before sending _any_ HTML.
  - _Scenario_: DB Call (200ms) + Auth Check (100ms) + 3rd Party API (500ms) = Blank screen for 800ms.
- **Solution**:
  - Move slow fetches **down** the component tree into Suspense boundaries.
  - Do not `await` everything in the root `page.tsx`.

## 1. Static Rendering (SSG) - **Default**

- **Behavior**: Routes are rendered at **build time**.
- **Usage**: Marketing pages, Blogs, Documentation.
- **Dynamic Routes**: Use `generateStaticParams` to generate static pages for dynamic paths (e.g., `/blog/[slug]`).

  ```tsx
  export async function generateStaticParams() {
    const posts = await getPosts();
    return posts.map((post) => ({ slug: post.slug }));
  }
  ```

## 2. Dynamic Rendering (SSR)

- **Behavior**: Routes are rendered at **request time**.
- **Triggers**:
  - Using Dynamic Functions: `cookies()`, `headers()`, `searchParams`.
  - Using Dynamic Fetch: `fetch(..., { cache: 'no-store' })`.
  - Explicit Config: `export const dynamic = 'force-dynamic'`.

## 3. Streaming (Suspense)

- **Problem**: SSR blocks the entire page until all data is ready.
- **Solution**: Wrap slow components in `<Suspense>`. Next.js instantly sends the initial HTML (static shell) and streams the slow content later.

  ```tsx
  <Suspense fallback={<Skeleton />}>
    <SlowDashboard />
  </Suspense>
  ```

## 4. Incremental Static Regeneration (ISR)

- **Behavior**: Update static content after build time without rebuilding the entire site.
- **Time-based**: `export const revalidate = 3600;` (in layout/page) or `{ next: { revalidate: 3600 } }` (in fetch).
- **On-Demand**: `revalidatePath('/posts')` via Server Actions or Webhooks.

## 5. Partial Prerendering (PPR) - _Experimental_

- **Concept**: Combines Static shell + Dynamic holes.
- **Config**: `export const experimental_ppr = true`.
- **Behavior**: The build generates a static shell for the route (served instantly from Edge), and dynamic parts stream in.

## Runtime Configuration

- **Node.js (Default)**: Full Node.js API support.
- **Edge**: `export const runtime = 'edge'`. Limited API, starts instantly, lower cost.


---
Source attribution: ngxtm
Original project: https://github.com/ngxtm/devkit/blob/9439f27ce3fa7fe53ff9278a1ee9a44bffa70eba/rules/nextjs/rendering/SKILL.md
License: MIT
License information: https://opensource.org/license/mit
Original upstream instructions; downloaded from Mega AI Hub.

## Upstream license notice

MIT License

Copyright (c) 2024

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.



# Mega AI Hub resource metadata

Creator / publisher: ngxtm
Original project: https://github.com/ngxtm/devkit/blob/9439f27ce3fa7fe53ff9278a1ee9a44bffa70eba/rules/nextjs/rendering/SKILL.md
Attribution basis: Source repository record

Fields of work: Design, Development & Engineering, Product Management
Roles: Frontend Developer, Full-Stack Developer, Growth Product Manager, Product Manager, UX Designer
Specialties: Backend, Frontend
Tools: Nextjs
Country applicability: Country not specified
Classification basis: Source catalog labels
Instruction SHA-256: b40f255a8fe223145333eeb101fe70de67b1caf9ad22239fc3a2aa9f899f2a3c