Static site development long predates the term Jamstack. Developers used it mostly to put a blog or open-source documentation on GitHub Pages, and while some pushed larger commercial projects onto static sites, that was far from common.

Static sites carried a reputation as a relic of the 90s. Phil Hawksworth, in his IJS talk on static being a loaded term, framed the problem as a question of semantics:

Are we talking about a static experience, or are we talking about a static architecture?

That ambiguity confuses developers and non-developers alike. What distinguishes today's static sites from their 90s counterparts is a set of technologies that did not exist then:

  • JavaScript matured into a language capable of building full browser applications; Gmail, launched in 2004, was the first mainstream app to make heavy use of Ajax.
  • Static Site Generators (SSGs) brought dynamic-site features like layouts and content separated from code. Jekyll, the first widely popular SSG, arrived in 2008.
  • CDNs stopped being enterprise-only. AWS Cloudfront, launched in 2008, made a CDN a few-minutes, few-dollars setup at small scale.
  • Git workflows and the CI/CD tooling around them replaced error-prone FTP deployments.
  • Ecosystem tools can now be dropped into a static site for search, eCommerce, databases, comments and more.

Jamstack changed the perception of static sites, and Matt Biilmann coined the term in 2016 to capture the benefits of modern static sites without the baggage of static. Cassidy Williams' description gets at the core:

Jamstack is about building web applications in the same style as mobile applications: the UI is compiled, and then data is pulled in as needed.

WordPress developers in particular took to it. Set against intricate theming and plugin APIs, the simplicity and control of an SSG felt refreshing, and a community formed around the decoupled approach.

Growth pushes against the original limits

As Jamstack's popularity grew, so did project size and complexity. Its principles moved beyond websites into web applications, and static sites soon hit their technical ceiling. Platforms responded with features and workflows that extended Jamstack principles, letting larger and more complex applications take a Jamstack approach.

That evolution is exciting, but it has left the community without agreement on what Jamstack means. Succinct definitions draw a clear boundary; the term is meanwhile applied to more and more dynamic behavior, with some of the community on board and some not. Ambiguity and perception were the reasons the term was coined, and there is a risk of coming full circle. The problem is hard because the original meaning and the newer, more dynamic usage overlap so heavily; one idea floated was "Jamstack" for static use and "Jamstack++" for dynamic, but that would have created more confusion than it resolved.

Matt Biilmann captured the tension in Netlify's announcement of Distributed Persistent Rendering (DPR):

For any technology, the hardest part is not establishing simplicity, but protecting it over time.

DPR is an elegant answer to the pain of prebuilding large sites: for a 100k page site, prebuilding a subset and building the rest on demand at first request meaningfully cuts build time. But it sits right on the edge of the Jamstack picture, and whether it falls inside or outside the umbrella has rippling consequences.

Do existing definitions absorb DPR?

Sean Davis' definition resonates with the original spirit:

Jamstack is an architecture for atomically building and delivering precompiled, decoupled front-end web projects from the edge.

Folding DPR into that definition takes work, since it adds on-demand generation to the precompiled model. The official Jamstack definition fits more comfortably:

Jamstack is the new standard architecture for the web. Using Git workflows and modern build tools, pre-rendered content is served to a CDN and made dynamic through APIs and serverless functions.

DPR delivers content either through a serverless function or as a static file from a CDN, so it falls within that wording. The definition itself has already shifted: before late 2020, the version posted on Jamstack.org read:

Fast and secure sites and apps delivered by pre-rendering files and serving them directly from a CDN, removing the requirement to manage or run web servers.

Introducing "serverless" makes sense as the technology becomes approachable to front-end developers, the predominant Jamstack audience. It also runs against core Jamstack principles of pre-rendering and decoupling, which raises the question of whether those principles need updating too.

Five directions forward

The term has been a major catalyst for static site generators and gave the industry a language for pre-rendering and decoupling. Looking ahead, five possible directions stand out:

  1. Jamstack is fixed to its original meaning of prerendering and decoupling, and dynamic, Jamstack-inspired approaches get their own name.
  2. Jamstack evolves, with definitions and principles expanded — and the meaning likely becoming more ambiguous.
  3. Jamstack names the community: a set of guidelines with no hard and fast rules.
  4. Jamstack has removed the baggage of static, so we can speak of static vs. hybrid vs. dynamic websites.
  5. Jamstack becomes mainstream enough that we simply call it modern web development.

People in all five camps are pulling in different directions, which drives much of the confusion and discussion. What is clear is the passion this community has for the approach. The need is for consensus and a path forward; absent that, the likely outcome — for better or worse — is a mix of options 3, 4 and 5.