Static Regeneration: Supercharging Nextjs with Strapi Webhooks
summary
Combines SSG with a custom ISR-like pipeline using Strapi webhooks, API Gateway, SQS queueing, a 15‑minute cron and a build job that chooses partial builds or full builds. Demo with 1,500 articles shows full build ~40s vs partial ~9s; a client full build was ~15 minutes, so batching updates prevents repeated rebuilds, keeps sites on CDN/S3 without a server, decouples editors from CI/CD, and significantly cuts time and cost.
AI-written summary · about
chapters (13)
- 0:00Introduction and overview
- 1:26Challenges with SSG
- 3:34SSG overview and limitations
- 5:00Introduction to ISR
- 7:04Custom ISR architecture workflow
- 9:18Webhook configuration in Strapi
- 10:00API Gateway role explained
- 10:42SQS for batch processing
- 11:48Cron job scheduling
- 13:36Build system and partial builds
- 15:43Real-world demo results
- 16:47Impact and benefits of solution
- 18:11Final takeaways and conclusion
related talks
11mStrapi at
30mBuild Faster, Better Apps with SSG, Headless CMS & Azure Static Web Apps
27mSSR & SSG in NextJS
30mHow Next.js Scales to Millions of Pages with ISR
33mRebuilding the Future: How We Transformed Our CMS with Strapi
16mWhy I chose Next.js for my Strapi application
21mA Saga of Web Rendering Woes
08mFrom Jamstack to Incremental Static Generation