tailwind-symfony-starter VS Tailwind CSS

We also built countless of integration guides with other frameworks, such as Astro, SolidJS, Gatsby, and Flowbite with Symfony being the latest one and we have plans to build quite a few more.

A new integration guide has been published that shows you how to use a well established PHP framework called Symfony together with Flowbite and Tailwind CSS. An open-source starter project has been created as well.

So I have built a free and open-source Symfony starter project that has a fresh install of Symfony and Tailwind CSS with Flowbite installed and a couple of UI examples there. There's also a Symfony and Flowbite/Tailwind CSS integration guide live on our docs.

The awesome open-source community from Flowbite created a Symfony and Tailwind CSS starter project that you can use to skip this integration guide and use it as starting point for your future Symfony, Tailwind CSS and Flowbite projects.

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.