The idea that a JAMstack site is nothing more than a static site generator run once and left alone refuses to die. Jason Lengstorf lists the capabilities he keeps hearing attributed to other architectures but that the JAMstack handles fine:
- Loading data asynchronously
- Processing files, such as image manipulation
- Reading from and writing to a database
- User authentication and protecting content behind a login
The correction is older than the misconception. Articles about JAMstack routinely describe pre-rendering whatever can be pre-rendered and leaving the rest to client-side JavaScript and APIs, an approach Phil laid out in his piece on static-first sites with serverless rendering as a fallback.
The confusion persists in public
Lengstorf treats the misunderstanding as a live problem rather than a straw man, citing a Reddit question posted while he was writing. He declines to relitigate the difference between an "app" and a "site," but the question illustrates how much uncertainty remains.

Two jokes, opposite assumptions
Tim Chase turned the debate into verse with a Dr. Seuss pastiche that Lengstorf calls tongue-in-cheek. Its premise is the mirror image of the first misconception: that the JAMstack cannot function without client-side JavaScript, as the closing lines put it:
It does not work with JS off.
Phil answered in the same meter, and his reply is the more useful summary. You do not need all three parts; JavaScript is an option you may use, and if you do, the gains come from progressive enhancement.
It’s up to you. For you to choose.
JavaScript’s just an option you might use.
And if you do, success might be
From enhancing things progressively.
Whether a site leans on the client is a function of its requirements and use cases, he continues. The one constant is the core discipline: serve things statically and pre-render.
Where the discussion continues
The full treatment appears in Lengstorf's article on Smashing Magazine. The newsletter and sponsor blocks below belong to the original page rather than to this argument.




