Spreading the JAMstack
summary
JAMstack means pre-render pages and serve them from a CDN so pages require no server work at request time; big claims: sites aim for ~2s load (slower loses nearly a third of visitors), BBC data shows ~10% user loss per extra second, and Pinterest cuts perceived wait 40% and gains ~15% more signups/search traffic. Actual tools and ecosystems named include Gatsby, Netlify / Vercel, and static-site approaches like Next.js, Snowpack and Toast plus APIs (Stripe, Snipcart, GraphCMS) powering production sites for Tesco, Sainsbury’s, BT, EDF and SSE.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:49TECH PODCAST WITH A WHISKEY AMBIENTE
- 1:06KARMARAMA GOOD WORKS
- 2:07Warning!
- 6:46Static Sites
- 7:17What is static?
- 7:54Is my project Jamstack?
- 8:23What's not a Jamstack project?
- 10:24People want things fast
- 10:53How users interact with your site and it will impact rankings
- 11:11Click through rates
- 11:34How fast is fast enough?
- 12:10Performance matters
- 14:3415% increase
- 15:28Security Much smaller attack surface to secure and protect
- 18:25Empower front end developers
- 18:57Powered By modern browsers
- 20:53Enhanced By a rich ecosystem of services
- 21:41stripe
- 21:55Impact Processes and organisation
related talks
40mJAMstack: Silly Name. Serious Stuff
35mThe Rise of JAMStack
31mJAMStack - The Total Victory of JavaScript
50mDo we really need this JAMstack thing? And what even is it?
44mNo, Seriously… What is Jamstack?
19mA Skeptic’s Intro To The Jamstack
34mHow to JAMstack in a dynamic era
12mCMS and JAMstack: A Tale of Innovation in Web Development