bootswatch VS Tailwind CSS

Bootswatch

The colors primarily, I suppose. Something similar to what you see in https://bootswatch.com/.

That ^ . And I’ve found the Bootswatch page a very helpful visual aid. https://bootswatch.com/

Themes are now supported. Visit Bootswatch for more details. To select a theme use the new option APPSETTINGS_THEME as docker environment variable or in the appsettings.json file.

Others have said Bootstrap already, let me just chime in and point you towards bootswatch (https://bootswatch.com/) , they have great, free themes with great examples, I basically learned bootstrap in large parts by copying example code from their site and tweaking it to my needs / dissecting and trying to understand it.

One very quick thing you can do is to take a look at bootstrap themes. One site which offers them is Bootswatch.

I’ve found Bootswatch is a very quick way of making bootstrap more visually interesting

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.