Using daisyUI as a first-class design system in an open-source CMS (feedback welcome)

[tallcms]

Hi daisyUI maintainers and community 👋

I wanted to share a real-world project where daisyUI is used as a first-class design system, and hopefully get some feedback from people who know daisyUI deeply.

I'm building TallCMS, an open-source CMS for Laravel (TALL stack + Filament), and we’ve gone “daisyUI-native” by design rather than treating it as just a UI add-on.

Some highlights of how we’re using daisyUI:

• Many content blocks are implemented directly as daisyUI components (cards, alerts, stats, tabs, etc.)
• Theme scaffolding includes daisyUI presets as a first-class option (alongside custom themes)
• We lean on daisyUI tokens and component semantics to keep markup concise and consistent
• Preset themes act as a baseline that users can extend rather than something rigid

This has helped a lot with:

• Reducing Tailwind verbosity
• Faster iteration when building new blocks
• Making themes more approachable for non-designers

That said, I’d really value feedback from the daisyUI community on:

• Any anti-patterns you’ve seen when daisyUI is used at “system” level rather than page-level
• Gotchas with long-term theming or preset extension
• Component patterns you think work especially well (or poorly) for CMS-style builders
• Anything you’d do differently if you were designing this today

Project links (for context, not promotion):

• Website: https://tallcms.com
• GitHub: https://github.com/tallcms/tallcms

Happy to open issues or start deeper technical discussions if there’s interest.
Thanks — and massive kudos to the daisyUI team for the work on this project 🙏