Static Site Generation
DevelopmentBuilding every page of a website in advance, once, and storing the result as plain files ready to ship from a CDN. The output is a site that loads in…
Static Site vs Dynamic Site
Static vs dynamic website is the distinction between two ways of generating web pages. A static site is built ahead of time into HTML files and served as-is from a CDN — fast and simple to host. A dynamic site generates pages on each request by pulling data from a database and rendering them on a server. Modern frameworks like Next.js and Astro blur the line by mixing both approaches in the same project, page by page.
The old static vs dynamic debate has shifted. A decade ago, dynamic sites were the only way to get personalization, CMS-driven content, or e-commerce, and static sites meant hand-coded HTML. Today, static-by-default sites pull content from a headless CMS at build time, refresh on every publish, and add dynamic features only where they earn their keep. The result: pages that load in milliseconds, hosting bills measured in cents, and a security surface area close to zero. Most marketing sites should be static-first. Reach for dynamic rendering only when the content genuinely changes per user or per request — pricing, dashboards, personalization.
On a static site, a build process runs whenever content changes — fetching data from the CMS, rendering every page into HTML, and uploading the result to a CDN. Visitors get instant responses because there is no server work happening at request time. On a dynamic site, every request hits a server, which queries a database, runs application logic, and renders HTML on the fly. Frameworks like Next.js and Astro support both modes: static for marketing pages, dynamic for personalized sections, with caching layers in between. The right answer is rarely one or the other — it is choosing the right rendering strategy per page.
Building every page of a website in advance, once, and storing the result as plain files ready to ship from a CDN. The output is a site that loads in…
When a website builds the page on the server before sending it to the visitor's browser. The visitor sees finished content immediately, and Google sees the…
A way of keeping a static site fresh without rebuilding the whole thing every time. New or edited pages get regenerated on the fly, so marketing can publish…
A small, mostly static website that exists to present a company's offer — homepage, about, services, contact — without complex functionality, a content engine,…
A content management system that separates where content is stored from how it's shown, giving marketers a place to publish without rebuilding the front-end…
A modern web framework for building fast, search-friendly websites and apps in React. It is the default choice for serious scale-up sites where speed, SEO, and…
A web framework built for content-heavy sites that need to load instantly. It ships almost no JavaScript by default, which is why marketing sites built in…