November 16, 2015
Jamstack term coined
Matt Biilmann published "What is the JAMstack?" on November 16, 2015 — naming the JavaScript, APIs, and Markup architecture NetlifyA platform for deploying static sites and serverless functions — Git push to production. had been enabling.
What it was for
JamstackJavaScript, APIs, and markup — sites built as static front ends with serverless backends. described pre-rendered sites served from CDNs with serverless APIs — decoupling the frontend from monolithic backends. The term gave a vocabulary to static site generators, headless CMSs, and GitA distributed version control system — commits, branches, and merges for tracking source code history.-based deploy workflows that defined modern web development.
Why it's here
JamstackJavaScript, APIs, and markup — sites built as static front ends with serverless backends. named the architectural shift from LAMP monoliths to composable frontends.
Why it mattered
It unified static generators, headless CMSs, and CDN deploys under one movement.
What it solved
TeamsMicrosoft Teams — chat, video calls, and Office integration for workplace collaboration. building decoupled sites lacked a shared term to describe their approach.
Media
- ImageNetlify
Netlify, Public domain, via Wikimedia Commons
Related
- Netlify launchedApril 7, 2015
- Next.js open sourcedOctober 25, 2016
- Contentful founded2013