Kill the Back-end: Jamstack and GitHub Actions, More Than a Deploy
summary
Jamstack (JavaScript, APIs, Markup) static sites offer performance, SEO, security and a good dev experience but struggle with user-generated dynamic content. The talk explains how to use GitHub Actions to automate workflows so GitHub can act as a lightweight CMS: receive client-side submissions, validate them, and publish changes without a traditional back-end or database.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:11SPA problems
- 4:38What is Jamstack
- 7:11GitHub Actions basics
- 9:41Jamstack + Actions demo
- 14:18Real-world use case
- 16:48Live demo walkthrough
- 19:20Conclusions and limitations
- 21:49Q&A
related talks
42mJamstack, static sites and Azure
34mHow to JAMstack in a dynamic era
44mSpreading the JAM throughout your CI workflow
05mLightning talk: Give a try to the JAM(stack)
01h 01mGetting Started with GitHub Actions
14mReact on the Jamstack
29mJamstack at Scale
18mDeveloper Workflow Automation with GitHub Actions (CI/CD)