Build a Kanban Board with Turbo 8 & Tailwind CSS!

[@r123421]

Thanks Phil, this is a nice overview. :) Regarding the questions about morphing. You got it right, it calculates the full page, which is far less efficient in terms of resources than a page broken down into turbo frames or using turbo streams for precise updates. But it's much more efficient in terms of developer time. And I think that's the whole point, it's a tradeoff that we get to make page by page. Low traffic, simple page? Use morphing and go home early. High traffic, high complexity dashboard? Put in the extra work to do the precise stream based updates. I.e. not a panacea but another tool in the Rails toolbox.

[@PhilSmy]

Fair enough! I never think about developer time!

[@FilipeWLima]

Hey Phil! Thanks for this overview. I found it helpful as I'm still out of the loop with some Turbo/Hotwire features. I've just found out your channel and am eager to check out the other videos!

[@PhilSmy]

Glad it was helpful! There are other Turbo videos on this channel. Plus if you need more, just let me know. I love making videos about Turbo and Hotwire. I think they are legitimate alternatives to some front-end Javascript frameworks.

[@haroldpepete]

great video, i think turbo morph is for updaing different parts in the whole page, morph is in charge for changing everything you need without make it in a eplicit way, and if you don;t wanna somothing change in morph process, you have to set data-turbo-permanent atrribute to the elemnt