static-rendering

Pre-render route HTML at build time using getStaticProps or static params.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/quanngynx/GDGO-2026.Servexa-Warranty-AI --skill static-rendering-quanngynx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: static-rendering
Source: https://github.com/quanngynx/GDGO-2026.Servexa-Warranty-AI/tree/main/servexa-warranty-ai/.agents/skills/static-rendering
Command: npx skills add https://github.com/quanngynx/GDGO-2026.Servexa-Warranty-AI --skill static-rendering-quanngynx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Static rendering reduces slow server response and heavy client JavaScript by serving pre-built HTML, improving TTFB, FCP, LCP, and overall performance when pages don’t need to change per request.

Core Features & Use Cases

  • Pre-render HTML at build time (SSG): Generate route-specific HTML during the build so the client can receive ready-to-display content quickly.
  • Support for dynamic routes with generated paths: Use build-time path generation to pre-create pages like product details or blog posts.
  • Optional freshness with ISR: Regenerate or update static pages periodically when content changes without requiring a full rebuild.
  • Use cases: About pages, marketing pages, product listings, blog posts, and any public content where personalization and authentication gating are not required at request time.

Quick Start

Use static generation by pre-rendering your routes at build time with getStaticProps (Pages Router) or static parameter generation (App Router), and deploy the output to a CDN for edge-cached performance.

Frequently Asked Questions about static-rendering

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I pre-render Next.js pages at build time to improve LCP?

Pre-render Next.js pages at build time using getStaticProps or static parameter generation to serve ready-to-display HTML, reducing client bundle size and improving LCP without per-request server processing.

What is static rendering and when should I use it for my website?

Static rendering generates route-specific HTML during the build process instead of at request time. Use static rendering for marketing pages, product listings, and blog posts where content can be fetched during the build and served as cached static HTML.

Can I use dynamic routes with static generation for product detail pages?

Yes, you can use dynamic routes with static generation by using build-time path generation like getStaticPaths or static params APIs. This pre-creates pages such as product details or blog posts so they can be served as cached static HTML.

Does static rendering support incremental updates when content changes?

Yes, static rendering optionally supports incremental updates via ISR to regenerate static pages periodically when content changes. This maintains content freshness without requiring a full rebuild of the entire site.

When should I not use static rendering for my application?

Avoid static rendering when pages require authentication gating or personalization at request time. If the needed data cannot be fetched during the build, static rendering is not suitable for that specific route.

How do I deploy pre-rendered HTML to a CDN for edge caching?

Deploy the static output generated by getStaticProps or static parameter generation to a CDN. This enables edge-cached performance by serving pre-built route HTML directly from locations closest to the user.