turbo-rails VS Tailwind CSS

The install notes here link to an issue specific to webpacker. Try that and see if it works?

True, in theory it is. A lot of it is coded in libraries like turbo-rails, though. And these are Rails-specific. But I've seen it being used in some Laravel projects, also I used it with Hanami.

Check out https://github.com/hotwired/turbo-rails/blob/main/app/models/turbo/streams/tag_builder.rb

So apart from the pretty obvious question of "why on earth would you want to do this?", I think there's a misunderstanding here of the intended use case of turbo streams. You have a page, and then some state changes on the server and you want to update the page to reflect that. Incrementing a variable doesn't really qualify as a state change, but perhaps a Product changing from "not good" to "good" would be an event worth broadcasting, which you could do using the Broadcastable concern in turbo-rails.

Use this too: https://github.com/hotwired/turbo-rails

Not mentioned in the article, but it's nice that turbo-rails recently gained the ability to pass ViewComponent objects directly to turbo stream helpers. https://github.com/hotwired/turbo-rails/pull/433

Release notes: https://github.com/hotwired/turbo-rails/releases/tag/v1.4.0

turbo/streams_channel.rb - a way to link a turbo stream with an ActionCable channel.

The readme seems to give a pretty good overview of turbo: https://github.com/hotwired/turbo-rails

Lastly, Tailwind CSS is a utility-first CSS framework packed with classes like flex, pt-4, text-center, and rotate-90 that can be composed to build any design, directly in your markup.

Tailwind CSS

Sidekiq is already configured along with assets, tailwindsCSS.

Finally, for our front end, we’re going to be pairing Next.js with the great combination of TailwindCSS and shadcn/ui so we can focus on building the functionality of the app and let them handle making it look awesome!

You can use any frontend framework you want — react-based tooling, however, has a natural advantage as it models everything as a function of state, which can map 1:1 with the concept in Burr. In the demo app we use react, react-query, and tailwind, but we’ll be skipping over this largely (it is not central to the purpose of the post).

Tailwind CSS: A utility-first CSS framework for rapidly building custom designs.

First, you need to make sure that you have a working Tailwind CSS project…

Tailwind CSS

With better CSS approaches like TailwindCSS and Vanilla Extract (which we're heavily using) it's much easier to maintain the UI and make sure it doesn't change unexpectedly. No more conflicting CSS classes, much less CSS specificity issues and much less CSS code in general.