Turbo Frames Explored... for Fun and Profit
summary
Turbo Frames powers pagination, lazy-loading, modals, multi-step wizards and even a polling “job pinger” pattern using Hotwire/Turbo + Stimulus on Rails 7 — running in production at Agent Pronto. Examples include server-rendered pagination that takes two lines of Ruby, eager and viewport-triggered image/HTML loads (including a slow 300‑digit π endpoint) as eager vs lazy lazy loading, a modal system that works as modals without JavaScript, and history‑advancing wizards; overall it cuts front‑end code and works reliably.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:19Hotwire and Turbo Frames
- 3:04Turbo Drive and Frames
- 6:52Pagination with Turbo Frames
- 8:35How Turbo Frames work
- 13:31Four Turbo Frames use cases
- 13:52Lazy loading with Turbo Frames
- 17:17Lazy loading beyond images
- 18:23Job pingers with Turbo Frames
- 20:09Modals without JavaScript
- 23:39Multi-step forms with Turbo Frames
- 27:34Hotwire and Stimulus
- 30:18Closing
- 30:39Q&A: Infinite scroll
- 31:01Q&A: Nested Frames and performance
- 31:22Q&A: Drag and drop
- 31:42Q&A: Unsuitable use cases
- 32:04Q&A: Form state management
- 32:45Q&A: Browser history
- 33:28Q&A: Analytics and legacy JS
- 34:53Q&A: Stability and Rails upgrades
- 35:57Q&A: Testing Turbo Frames
- 36:39Q&A: Converting to Stimulus
related talks
32mHotwiring My React Brain
38mMaking a difference with Turbo
30mThe Future of Rails as a Full-Stack Framework powered by Hotwire
43mTurbo Boosting Real-world Applications
09mHotwire Cookbook and common use cases
32mRevisiting the Hotwire Landscape after Turbo 8
14mRails 5, Turbolinks 3, and the future of View-Over-the-Wire
32mRevisiting the Hotwire Landscape after Turbo 8