The JAMstack Is Dead. Long Live the Runtime!

Markdown in Git sounds like the simplest possible way to manage content. No CMS. No dashboards. No abstractions. Just files, version control, and AI agents that can grep the codebase.

But once content needs to scale — across pages, teams, products, and automation — that simplicity starts to crack. Asset management sneaks back in. Permissions reappear. Content models emerge. Queries get rebuilt. And before long, you’re running a backend again.

In this episode of The Node (& More) Banter, Luca Maraschi & Matteo Collina unpack the debate sparked by “You should never build a CMS” — and explain why deleting the CMS doesn’t delete the problem, it just moves it into code.

We’ll cover:
✅ Why “content = page” breaks down as soon as content needs to be reused, queried, or governed
✅ How markdown + git quietly recreates CMS features — just without calling them that
✅ Why git workflows work for code but fall apart for real content collaboration
✅ Why AI agents need structured, queryable content — not grep and string matching
✅ How the JAMstack model collapses once content becomes dynamic, shared, and automated
✅ Why runtime-first architectures (and Node) are unavoidable in modern content systems

The takeaway?
You can delete the CMS UI — but you can’t delete the runtime. The JAMstack era is ending, and what replaces it is content infrastructure built for APIs, agents, and systems that need to reason, not just render.