Rise of the Jamstack — Mathias Biilmann
summary
Argues that shifting to a prebuilt front end plus client-side JavaScript and APIs fixes performance, security, and scale: Smashing Magazine rebuild uses Hugo + a Victor Hugo boilerplate, content and products stored in Git, comments serving 200,000 threads as static files, and continuous builds that finish in 13 seconds. Provides open source pieces: Netlify CMS for Git-backed editing, GoCommerce with order/payment endpoints, JSON Web Tokens for stateless auth.
AI-written summary · about
chapters (7)
- 0:00Introduction to Jamstack
- 1:05Background and experience
- 3:34Limitations of legacy stacks
- 7:23The Jamstack architecture
- 10:23Smashing Magazine case study
- 14:04Open source tool ecosystem
- 26:08Best practices and conclusion
related talks
35mThe Rise of JAMStack
56mJAMstack
31mJAMStack - The Total Victory of JavaScript
40mJAMstack: Silly Name. Serious Stuff
19mA Skeptic’s Intro To The Jamstack
44mJAMstack: Web Apps at Ludicrous Speed
50mDo we really need this JAMstack thing? And what even is it?
12mCMS and JAMstack: A Tale of Innovation in Web Development