Remove DaisyUI

[carletex]

This is something that has been on the table for some time: removing DaisyUI and mimicking the same functionality (only the things we use) with Tailwind classes/utilities (@apply, etc)

There are some PROS:

• Cleaner codebase just with Tailwind
• Allow easier integrations with other libs (e.g. shadcn)
• Extra: if we want to keep going with scaffold-ui, this is also a good thing.

Also, some of the useful functionality doesn't work super smoothly (modals, tooltip). I think they could be easily replicated.

On the other hand, I like themes, color handling, semantic classes, etc. We'd need to find a (TW native) replacement for it.

Let's analyze what we are using from DaisyUI and figure out what we'd need to create the functionality we want. Then, let's decide if it is worth it.

[JulioMCruz]

This sounds great! In my case, I work with Tailwind and ShadCN since many developers use those as a standard. However, I also noticed that many projects already use Daisy UI, which comes from Scaffold-Eth-2. Maybe one option would be to create an extension

[carletex]

Thanks for the feedback @JulioMCruz !

Yes, I think the main idea is to leave only Tailwind to give users more initial freedom: they could install DaisyUI / Shadcn / whatever after spinning SE-2. Rigth now, if you don't want to use DaisyUI... you have to remove it first, and then set up your thing.

I think removing DaisyUI and having a DaisyUI extension would be great!

[matallui]

IMO shadcn would be a good move. Unlike DaisyUI, shadcn is not a dependency. Shadcn is a tool to help you build your own component library. In fact, with the new Registry features they have, one could even start building Web3 components and publishing into a registry, then this template could pull directly from there.

[rin-st]

I'll try to tinker and figure out how much is it takes to change everything to tailwind

For now as I understand we need to change: modal, dropdown, tooltip, table, themes, button, textarea/input and maybe something else