django-tailwind-alpine-htmx VS turbo-django

I didn't follow any specific tutorial but there is one resource that was most helpful for me: https://github.com/AccordBox/django-tailwind-alpine-htmx It helped me see that you can have all your javascript in one place in an organized manner. That's when I decided to add Vite. If you follow this carefully, you should be able to set up Django with Vite and use it conveniently.

You can check my tutorial series https://www.accordbox.com/blog/django-tailwind-css-alpinejs-tutorial/

You can use Alpine.js + HTMX + Tailwind CSS https://github.com/AccordBox/django-tailwind-alpine-htmx

Indicative of how marvelously stable Django is that none of these roadmap items have to do with the software.

I came back to the old workhorse for some experimentation recently and was delighted, delighted (!), I tell you, at how familiar, comfortable, and productive it was.

Started exploring a Turbolinks/Turboframes implementation (https://github.com/hotwire-django/turbo-django) that Just Worked. Amusingly, mid-hack, the repo owner marked it as unmaintained.

But it works! Nothing needs doing! Another victim of the cult of constant improvement.

Yes Turbo is created by the team behind Ruby on Rails and it's an evolution of Turbolinks with bunch of other functionality added. But Turbo can be adapted to other languages and backend frameworks (and already has!). This Turbo thing is not Rails specific.

If you would like to try something different, there is this new thing called hotwired: https://github.com/hotwire-django/turbo-django Basically, it's about generating HTML on the backend and pushing it to the frontend. thru WebSockets. It's not production-ready yet (for Django at least) so it's more like a fun fact for now.