4 ms·
Having used it only for my small typefaster.app project and a couple other small unpublished projects I can’t speak to great detail on advantages or disadvantag
by absoluteunit1 3y ago
Having used it only for my small typefaster.app project and a couple other small unpublished projects I can’t speak to great detail on advantages or disadvantages; I am not a CSS expert. From my limited experience, I found it’s far more convenient and intuitive than any CSS library I’ve used.
It’s concise; writing css directly in my html and not feeling like I’m cluttering the file makes readability great.
Debugging styling in SPAs is significantly easier since I can just glance at the DOM in the browser dev tools and be able to quickly find the CSS causing the styling issue (just looking through the HTML tree, not having to look through styling tool saves time)
DaisyUI is a library built on top of it; a lot of great snippets of styles elements there.
The config file; all custom configs are concise in one file.
It makes things like conditional styling or just if you have any state determining styling, it is very easy to do and readable
But in summary, honestly for me it’s just the direct in-html styling and conciseness. I’m a simple man
- gema_naranyala 3y agoMy personal suggestion based on Tailwind as well: - Ripple UI - Preline UI - Hyper UI - Flowbite, and - Daisy UI
- volkandkaya 3y agohttps://github.com/versoly/versoly-ui https://github.com/versoly/versoly-ui would also work especially well with this stack as it comes with classes like Daisy (btn btn-primary) and JS like Flowbite (tabs).