Skip to content
TheAIDirector.Win ClaudeJoomla.com ClaudeTemplates.NET

Request: Tailwind CSS adapter (standalone, no DaisyUI)

More
6 days 9 hours ago #24 by frayn
DaisyUI is great but it is 947KB and includes all of Tailwind's utilities. Many of us just want a clean Tailwind adapter without the component layer.

Proposal: A standalone Tailwind adapter that uses Tailwind's utility classes directly in the adapter CSS, or better yet, a PostCSS build that generates only the utilities BaseFrame actually uses.

Benefits:
- Much smaller file size (probably 50-80KB)
- No class name conflicts with Bootstrap
- Full control over the design
- Tailwind's color system maps perfectly to BaseFrame's --bf-* variables

For now, the DaisyUI adapter works well if you do not mind the extra size. Anyone else interested in a lightweight Tailwind option?

Please Log in or Create an account to join the conversation.

More
6 days 7 hours ago #25 by may
Yes! I've been wanting this too. DaisyUI is opinionated about component design which sometimes clashes with how I want things to look. Pure Tailwind would let us use the utility classes without the component assumptions.

I'd even volunteer to help build it. I've been using Tailwind CLI standalone (no Node.js build step) on other projects.

Please Log in or Create an account to join the conversation.

More
5 days 8 hours ago #26 by friend
The Tailwind CLI standalone binary approach would be perfect for BaseFrame's no-build-tools philosophy. You'd run it once to generate the CSS, ship the output file as the lib, and the adapter just maps bf-* classes to Tailwind utilities.

Here's how I'd structure it:
Code:
/* lib/tailwind.css = output of Tailwind CLI scan */ /* adapters/tailwind.css = bf-* to Tailwind mapping */ .bf-card { @apply bg-white rounded-lg shadow-md overflow-hidden; } .bf-card-title { @apply text-lg font-semibold text-gray-900; } .bf-tag { @apply inline-block px-2 py-1 text-xs rounded-full bg-indigo-100 text-indigo-800; }

The @apply directives would compile away during the CLI build step.

Please Log in or Create an account to join the conversation.

More
4 days 9 hours ago #27 by frayn
That's exactly what I had in mind. The @apply approach means the shipped CSS has zero Tailwind runtime — it's just plain CSS that happens to follow Tailwind's design system. Best of both worlds.

Please Log in or Create an account to join the conversation.

Time to create page: 0.237 seconds
Powered by Kunena Forum