Getting Started with Static Site Generation
Learn how static site generation pre-renders pages at build time for maximum performance and SEO benefits.
This is an example app built with General Translation to demonstrate static site generation with i18n. Not a real blog.
Every page on this site is pre-rendered at build time for each supported locale using generateStaticParams. No runtime translation fetching, no loading states -- just instant, fully translated HTML served from the edge.
Learn how static site generation pre-renders pages at build time for maximum performance and SEO benefits.
Pre-rendering translations at build time eliminates runtime overhead and delivers instant page loads in every language.
Translated metadata, locale-specific URLs, and pre-rendered HTML give search engines exactly what they need.
This site uses generateStaticParams to enumerate every combination of locale and page slug at build time. Next.js then pre-renders each combination into a static HTML file.
Translations are generated ahead of time with the GT CLI and bundled as JSON files. At build time, each locale loads its translations and renders fully translated HTML. The result is a site where every page in every language is a static file, ready to be served instantly from a CDN.
Combined with generateMetadata, each locale path also gets translated page titles, descriptions, and Open Graph tags for optimal multilingual SEO.
This is an example app built with General Translation to demonstrate static site generation with i18n. Not a real blog.
Every page on this site is pre-rendered at build time for each supported locale using generateStaticParams. No runtime translation fetching, no loading states -- just instant, fully translated HTML served from the edge.
Learn how static site generation pre-renders pages at build time for maximum performance and SEO benefits.
Pre-rendering translations at build time eliminates runtime overhead and delivers instant page loads in every language.
Translated metadata, locale-specific URLs, and pre-rendered HTML give search engines exactly what they need.
This site uses generateStaticParams to enumerate every combination of locale and page slug at build time. Next.js then pre-renders each combination into a static HTML file.
Translations are generated ahead of time with the GT CLI and bundled as JSON files. At build time, each locale loads its translations and renders fully translated HTML. The result is a site where every page in every language is a static file, ready to be served instantly from a CDN.
Combined with generateMetadata, each locale path also gets translated page titles, descriptions, and Open Graph tags for optimal multilingual SEO.