Architecture · 2016–now · Platform Wars
Jamstack
Pre-render + CDN + APIs. The brand cooled; the pattern (static where possible) stuck.
Jamstack mutated delivery by putting HTML at the edge and admitting dynamic bits can be APIs. The marketing cooled when every page needed auth and personalization anyway. The pattern stuck under new names like partial prerender.
Context
Frameworks fought for the runtime
Front-end frameworks consolidated power; TypeScript became the floor; serverless and Jamstack rebranded old ideas with better CDNs. Blockchain-for-CRUD and big-bang rewrites collected the decade’s dumbest budgets. The winners were boring platforms with ecosystems. The losers were narratives that skipped product-market fit.
Compare with
Related
Practice · 2014–now
SPA for Every Page
Client-side apps as the only architecture. Great for apps; absurd for brochures.
$ Marketing sites and docs portals shipped multi-megabyte JS bundles for content that wanted HTML. SEO and performance teams spent years unwinding "modern" defaults.
Framework · 2016–now
Svelte / SvelteKit
Compile away the framework. Less runtime theater, more shipped HTML — including this site.
Framework · 2016–now
Next.js
React with routing, SSR, and deployment opinions. The default answer when someone says "we need a web app."