Using daisyUI in a real CMS (TallCMS) — what worked really well

[tallcms]

I’ve been building an open-source CMS (TallCMS) on Laravel + Filament, and in a recent update I refactored the UI to go fully daisyUI-native.

Wanted to share a few practical observations for anyone considering it:

What improved immediately

1. Much less verbose markup
   Once components became daisyUI-native, the templates got noticeably simpler.
   Easier to read, easier to maintain, and faster to iterate on.

2. Speed of development
   I stopped thinking in terms of low-level Tailwind utilities and started thinking in components.
   That shift alone sped things up quite a bit.

3. Themes are actually usable out of the box
   The preset themes aren’t just demos — they’re solid baselines.
   I built a theme manager on top of them and it worked surprisingly well.

Trade-offs
You give up some low-level control vs pure Tailwind
You need to “lean into” daisyUI patterns — mixing styles halfway doesn’t feel great
Key takeaway

For me, daisyUI hits a really good balance:

👉 Faster development
👉 Cleaner markup
👉 Consistent UI without overthinking design

https://github.com/tallcms/tallcms/blob/main/docs/dev-themes.md