Uniting the Team with JAMstack
summary
A multi-site headless CMS and a Jamstack front end get built in days: Craft CMS is used as a headless source, Eleventy pulls API data to render pages, and Netlify hosts the CDN builds triggered from Slack via a Slack build hook. The site hits a maxed Lighthouse score, early‑bird tickets sell out in two hours, and editors trigger deploys without code. The system runs CMS on existing LAMP infra while the front end lives on Eleventy and Netlify, showing the approach works.
AI-written summary · about
chapters (10)
- 0:00Introduction and project background
- 2:06Developer mindset and project constraints
- 4:55Choosing the right tech stack
- 8:29Introducing JAMstack approach
- 13:21Benefits of JAMstack for performance
- 16:32Planning with content team
- 18:16Building with 11ty and APIs
- 20:06Deployment and hosting strategy
- 21:51Team collaboration with Slack
- 23:18Outcomes and closing remarks
related talks
13mBest of Both Worlds: Combining a headless CMS and Jamstack
12mCMS and JAMstack: A Tale of Innovation in Web Development
34mHow to JAMstack in a dynamic era
05mLightning talk: Give a try to the JAM(stack)
35mThe Rise of JAMStack
30mRise of the Jamstack — Mathias Biilmann
29mJamstack at Scale
26mJAMStackin’