14 ms·
DaisyUI: Tailwind CSS Components
- PaulHoule 1y agoThis is like "Bootstrap for Tailwind?"
- coneonthefloor 1y agoTailwind has the Bootstrap problem, in that I can tell straight away that a website uses Tailwind, and for some reason that is off putting.
- thornewolf 1y agoPreface: I accidentally mixed up Tailwind and DaisyUI in my brain. The commenter above me is talking about Tailwind and my "Previous Comment" is responding by talking about DaisyUI but accidentally also using the word Tailwind. For previous versions of DaisyUI my main complaint was that it looked childish. V5 fixed this. I misread the parent comment as if they were talking about this same issue. My bad. Previous comment: I'm not sure when you most recently used Tailwind, but V5 is a big improvement on V4. 4 definitely looked somewhat childish. 5 corrected most/all of this.
- sudhirj 1y agoHow does the version of Tailwind itself make difference? The look depends on what styles are applied using Tailwind, not the ability to specify styles. Think the problem is the most tailwind sites have a similar set of styles applied, most likely copies of the docs or examples. TailwindUI is a paid system, but yeah, could be a case of most of the defaults copying that.
- thornewolf 1y agoI'm sorry. Brain fart. Replace Tailwind V4/V5 with DaisyUI V4/V5. After re-reading double brain fart. I misread the comment as complaining about DaisyUI. I then responded as if they were complaining about DaisyUI but ALSO accidentally used "Tailwind" in my comment.
- stefanfisk 1y agoHow can you tell? Or are you referring to Tailwind UI?
- dmlittle 1y agoIt depends on how much effort you put into it vs. just using any of the base templates/components that Tailwind Plus (previously Tailwind UI) has to offer. If you look at their Showcase section[1], you can't tell it's using TailwindCSS for most of them (imo). [1] https://tailwindcss.com/showcase https://tailwindcss.com/showcase
- bickfordb 1y agoYou might be bored by the aesthetics, but isn't usability improved by having familiar with UI components across websites?
- crowcroft 1y agoTailwind is just a different way of writing CSS. UI libraries and websites all end up converging on a common set of ideas because of usability and readability, perhaps you're conflating Tailwind UI libraries with Tailwind itself. Tailwind doesn't inherently force a website to look a certain way any more than flexbox or CSS grids might. I do agree in that if you're using Tailwind you're unlikely to be reaching deep into the full functionality of CSS for animation etc. but most websites aren't doing that whether they're using Tailwind or not.
- mpeg 1y agoTailwind comes with a set of colors, shadows, typography scale, paddings, etc. Sure, you can override them, but most people don't and there is definitely a "tailwind look"
- jmull 1y agoBootstrap fights you when you move away from its built-in look-and-feel. Tailwind is pretty close to neutral. You get the tailwind look by copy-pasting the tailwind components directly and straightforward use of the built-in palette and fonts. But it’s pretty easy to use customized palettes, not that bad to use different fonts (well, the hairy parts are due to HTML, browsers and the web, not tailwind), and it’s probably easier to skip the tailwind components if you know HTML (not a trivial skill but one well worth developing).
- foxygen 1y agoThat is like saying you can tell straight away if a website is using a separate CSS file or style="..." attributes. Non-sense.
- nikkwong 1y agoWhat about the components on Blendful[0]? I agree that everything themed with Tailwind looks the same—but I think it's because the starter templates that are popularly used basically have the same look and feel, which is what this site is trying to escape from. Tailwind also has it's predefined color schemes, which enhance the stylistic lock-in. Of course it's possible to break from the fray with Tailwind, but—I think generally speaking, it's fairly easy to build something that looks decently good, decently easy with Tailwind; and that's why people like it. [0]: https://www.blendful.com https://www.blendful.com
- jug 1y agoDoesn't this miss the point with Tailwind and why we have Tailwind in the first place?
- cdaringe 1y agoYup. And if you use a component based design, the whole premise/problem largely disappears
- savanaly 1y ago>Doesn't this miss the point with Tailwind and why we have Tailwind in the first place? Not for me. Say I have a new app and I want it to have a left nav. I could write my own styles with tailwind or...I could just put a .menu on there and gets all the sensible defaults for padding, spacing, font size, background colors, etc. But having done that, I'll still want to edit the specific padding, spacing, fonts, and background color of the menu to suit my needs. Plus there's...the whole rest of the site, not all of which is made up of DaisyUI components. So I will be wanting Tailwind for all that for the regular reasons one wants Tailwind.
- bricej13 1y agoI think it's the best of both worlds. Tons of free components right out of the box for non-designer developers (like bootstrap), but you still have the power of Tailwind at your fingertips. I think the theming & semantic color support is underrated. You just use `-primary` or `-secondary` classes everywhere instead of hardcoding the colors. The theme colors are then just updated with css variables. Dark mode is free, you don't have to pepper your code with a million "dark:*" classes.
- vitaflo 1y agoYou can just use Bootstrap then, there's no need for the extra abstraction of Tailwind and DaisyUI.
- sudhirj 1y agoThis is a rebuild of the antithesis of Tailwind on Tailwind. Bootstrap had this for decades (Daisy even copies the same semantic class names in some cases). Tailwind was supposed to break away from this, to specific actual styles directly, but looks like we're coming back full circle again. Why not just use Bootstrap?
- k__ 1y agoMaybe Tailwind has better dead code removal.
- 65 1y agoBecause you can use Tailwind on top of DaisyUI, e.g. `btn rounded-lg`
- Calavar 1y agoTailwind is already a full circle. It is essentially a toolkit for using CSS to emulate the pre-CSS era approach of putting styling info inside attributes on the markup (remember the HTML2 days of bgcolor and cellpadding?).
- treyd 1y agoYeah it's turning the crank another half turn. It's insane to me how the webdev ecosystem keeps reinventing itself over and over and over again, trying to solve their previous mistakes without ever reflecting on and learning from why those issues existed in the first place.
- PaulHoule 1y agoI'd say otherwise, it's not circular at all, it's a clean design that uses Tailwind at a low level and builds a high level on top of it.
- purerandomness 1y agoAgain, that's just Bootstrap with extra steps.
- ibash 1y agoThe evolution of the tailwind enthusiast is almost complete. Soon they’ll rejoin the old heads who never liked tailwind.
- Tade0 1y agoI think they'll do another lap for good measure before they settle on that.
- WesolyKubeczek 1y agoI don’t know, it’s like you ask me to use CSS as it meant to be used all along, I don’t understand why I would need tailwind with daisy on top if I could just write CSS with the added benefit of no extra JS. Or use Bootstrap for eye candy. Has been there for years and looks good enough. In any case, it feels like we have come full circle, Red Queen race-style. Yay web development!
- adocomplete 1y agoAt that point, why not just write CSS?
- 7bit 1y agoWhat point?
- Liquidor 1y agoI don't really use Tailwind. I enjoy my (S)CSS. I took a look at https://daisyui.com/components/button/ https://daisyui.com/components/button/ and immediately I see classes that look similar to Bootstrap. So my question is: Why build components on top of something like Tailwind instead of just regular CSS? Or are you able to customize and use Tailwind mixed in with the components? Then sure why not I guess. Otherwise it feels like going full circle here.
- fbn79 1y ago“Do not remove a fence until you know why it was put up.”
- mbb70 1y agoOff topic, but is there a term for the opposite concept? Something like "Decisions acquire a greater illusion of planning and deliberation the further into the past they were made". Feels like assuming there is a reason can be just as damaging as assuming there isn't one.
- metalliqaz 1y agoPerhaps slightly related: https://en.wikipedia.org/wiki/Planck%27s_principle https://en.wikipedia.org/wiki/Planck%27s_principle
- jovdg 1y agoMight be the survivorship bias. Or "history is written by the victor".
- DonHopkins 1y agoHey don't blame Brett for where we ended up!
- tevon 1y agoYou can use mixed in tailwind. Its for consistency (which I quite like). I'm a big fan of just saying "gap-1" and knowing that that will be consistent across the custom components I've written, and the component library
- CGamesPlay 1y agoI used DaisyUI for a recent project and really enjoyed it. It definitely isn't "Bootstrap for Tailwind". While it does have some semantic class names like bootstrap, it's very few comparatively. It does have a semantic palette (customizable), but this is integrated with tailwind, so all your tailwind utility classes share the palette. It also has some unstyled or lightly-styled components (modal, dropdown, etc). These are just like using headless UI, but with less JavaScript. These also work well with the Tailwind utility classes to let you customize the actual display.
- qq99 1y agoI'm surprised that a lot of the comments seem to be missing the reason that this project exists. In many tailwind projects, you inevitably end up wanting to standardize how a button looks, how a field looks, etc., rather than copy+paste the same 20+ tailwind classes that you need to implement a nice looking button in tailwind. Can you just apply it to `button { @apply flex items-center blahblahblah; }` in app.css? Of course you can. Or you can use the btn from DaisyUI. I think DaisyUI is just a shortcut for many common UI components that you will inevitably want to build out and that you will necessarily eventually standardize in any app that grows large enough. How does it differ from bootstrap? Well, you can continue to use tailwind for everything else that DaisyUI has not implemented. It's just an additive layer to tailwind. The project is at its core just a shortcut for common UI components. As a user, my criticism is that many of the DaisyUI components seem to be lacking good contrast, so some just don't seem to be usable. The theming situation is really interesting and quite cool to use, but if you look at the example page, it just feels hard to read. I can't really find a light and dark default theme that look good to me (re: contrast and brightness). I think the color hooks might just not be there but I didn't dig far enough in. For me, I've found a lot of value in being able to easily copy+paste parts of DaisyUI source code, e.g., a particular widget and modifying it to fit my design system, rather than use it in its entirety.
- Calavar 1y ago> In many tailwind projects, you inevitably end up wanting to standardize how a button looks, how a field looks, etc., rather than copy+paste the same 20+ tailwind classes that you need to implement a nice looking button in tailwind. CSS classes already support this natively. The whole point of CSS was move up a level of abstraction, so you could collect related styles into a class and reference that class everywhere you need that same grouping of styles instead of copy/pasting your HTML2 attribute-based styles all over the place. But then we got Tailwind, which uses CSS classes to emulate the pre-CSS behavior of specifying styles at a hyperfine granularity everywhere. And now we get DaisyUI, which emulates class based styling on top of a toolkit that emulates attribute based styling on top of the class based system of CSS. After while we have to admit that this tech stack contortion is the result of picking a tool because of familiarity and not because it is the best fit for the problem.
- rckt 1y agoAnd abstraction of an abstraction of an abstraction of an abstraction... Man, I'm never going to use it, but sometimes it's amazing to see what people can find worth their time.
- nop_slide 1y agoCurrently using Daisy for https://skatevideosite.com https://skatevideosite.com and love it!
- aniforprez 1y agoNot entirely convinced about their graphs where they "improve" over tailwind with just HTML size and "number of class names". Why do these matter exactly? You're basically removing the number of classes in the HTML and adding the CSS anyways so how much are you really saving here? I don't mind the existence of this library obviously but condensing into tiny abbreviated classes seems like the antithesis of tailwind but maybe it's for folks who can't or don't want to define a base button component every time and want a jumping off point. In that case I'd much rather use shadcn or something based on react-aria that gives me solid primitives that I can extend with tailwind classes passed to it in specific instances
- seaal 1y agoI imagine you're using most elements more than once in the HTML so the class names would be repeated X number of times.
- mpeg 1y agoRepeated strings like that should compress pretty well with gzip, which is one of the core ideas behind atomic css performance, alongside the difficulty to remove dead css – with vanilla html/css your css grows unconstrained With atomic css, your css stays a constant size, your html will be bigger but is easier to manage as you naturally add/remove html as page content changes, plus compression should be pretty efficient. I've had to manage legacy frontend codebases with tens of thousands of lines of mostly unused css that were not easy to remove as they might have been used somewhere, that's what led me to start using atomic css. I don't really love tailwind, but I appreciate it has become ubiquitous so I do use it, and the ideas behind atomic css are solid when you maintain a large frontend codebase. It has also led to the rise of self-contained components as opposed to libraries (shadcn and all the others) which I couldn't be happier about.
- rekoros 1y agoI've been using daisyUI for a couple of years and really love it - it's a quick, reliable way to rig up a nice looking/functioning UI with minimal work, while making things appear reasonably uniform across pages/workflows. The combination of Tailwind and daisyUI made it possible for me - a backend developer - to pretentd to be somewhat competent in frontendland, which has been incredibly handy, work-wise.
- iambateman 1y agoThe fact is that without using component-based HTML, Tailwind _is_ a mess and Daisy is probably useful. It's an amusing full-circle moment, where Daisy UI is a spiritual successor to Bootstrap, which did the same thing but with CSS as the underpinning. Inside of a system that splits the HTML into components, Tailwind classes are not a problem...You just end up with <x-button.primary> instead of <button class="primary">.
- wener 1y agoBootstrap is a good practice in old time, tailwind is modern css, daisy ui is a battery included components in pure css based on tw. I use daisy ui in every project I work on, by using daisy ui, I don't need shadcn, I prefer <button> instead of wrap my own <Button>, and menu, dialog etc. With baseui components I have a very powerful toolset that let me build thing's fast and good enough.
- alfonsodev 1y agoMy experience with DaisyUI has been great, is the type of library that: - Is super useful, and keeps adding value over time. - It doesn't get in the way when you don't need it. Gives you prebuilt standards and semantics, (e.g https://daisyui.com/docs/colors https://daisyui.com/docs/colors) and you can extend it like tailwind easily. Bonus: The way it implements themes, it makes sense to me, super easy. Love it!
- varbhat 1y agoI don't like the way how Daisy UI looks. But, I do like the way how Bootstrap or Semantic-UI CSS frameworks look. Has anyone tried to recreate the components of Bootstrap or Semantic UI using Tailwind CSS (including the looks)?
- commotionfever 1y agothis isn't how Tailwind is supposed to be used. you abstract at the level of components, not class names. <Button /> instead of <button class="btn"> then, inside your Button, you get a small bit of markup and your class names. makes it easy to see which markup gets which styles that's also why the other discourage use of @apply, and why "ugly HTML" is rarely am issue. at least not in my experience --- that said, if you're using Tailwind in an environment where there's no components, fragments, partials, whatever - then this might make sense
- nailer 1y ago> why "ugly HTML" is rarely am issue. at least not in my experience Fascinating, 5/5 Tailwind projects I have ever used, from YC companies to multibillion dollar private companies have had "ugly HTML". Not every single HTML element is a component, and top levels of components still need to by styled using tailwind's long lists of classes.
- trollied 1y agoAny website that hijacks scrolling can get in the sea.
- techscruggs 1y agoThat is a rather dismissive attitude that could cause you to overlook some great technologies.
- metalliqaz 1y agoOr it's a quick heuristic to filter out misaligned philosophies.
- ipaddr 1y agoThe biggest advantage is I can have great looking components with simple bootstrap syntax (add a primary or secondary class). When I need to I can write full tailwind syntax if I need something different. Great timesaver and while giving you all of your powertools.
- nnurmanov 1y agoAre there any cool UI libraries for Svelte or Vue? Similar to Baseweb or Grommet?I am planning to move away from ReactJS some day
- james2doyle 1y agoThere are a boatload for Vue: https://www.radix-vue.com/ https://www.radix-vue.com/ https://vuetifyjs.com/en/ https://vuetifyjs.com/en/ https://www.unaui.com/ https://www.unaui.com/ https://vuesax.com/ https://vuesax.com/ https://primevue.org/ https://primevue.org/ https://inspira-ui.com/ https://inspira-ui.com/ https://www.naiveui.com/ https://www.naiveui.com/ And for Nuxt there is https://ui.nuxt.com/ https://ui.nuxt.com/
- assimpleaspossi 1y agoAfter 20 years, my little company still uses just HTML, CSS and JavaScript for everything including two sites I'd bet money most of you visit at least a couple of times a month.
- antonio07c 1y agoYou made Hacker News?, nice
- sgt 1y agoWhat company is this?
- dzonga 1y agoprolly a porn company
- assimpleaspossi 1y agoNo. Restaurant chain and entertainment company
- sgt 1y ago> "including two sites I'd bet money most of you visit at least a couple of times a month." I mean, I don't think I use any restaurant chain web sites. So that leaves an entertainment company. Netflix, Apple TV+, Disney? I mean... you did say most of us will use some of these sites every month. Most of the entertainment web sites that people use all the time are HUGE companies, why would they use your little company (your own words) ?
- kelnos 1y agoI always find these sorts of weird-brags annoying. Either tell us the sites you built that are popular, or just don't comment about it at all.
- andrewmcwatters 1y agoThis is just themed Bootstrap.
- trevor-e 1y agoI agree with others that this is not how Tailwind is meant to be used. For example, the approach shadcn (https://ui.shadcn.com/ https://ui.shadcn.com/) takes is much better IMO. Creating helpers like `btn` makes it very difficult to understand how it works and is not very customizable. Shadcn creates an actual component for you in your codebase and is just trivial Tailwind styles to modify.
- adenta 1y agoThe problem I have with shad is that it’s react based, not HTML based. So if I want to use shad, I can’t mix and match static HTML partials in with app code. To maintain a consistent theme, I would need to make literally everything react.
- gedy 1y ago> I agree with others that this is not how Tailwind is meant to be used. I mean, whatever it's "meant" to be used like, Tailwind is popular enough that it ends up being used in a lot places where how it's meant to be used is a terrible fit. (Big apps, with existing UI code, can't assume a monolithic technology stack, an actual design system with tokens that is not just a react component library, etc). Ultimately, these are webapps and 99% of what we do ends up being the same shit over and over: "here's a button, here's a card", etc and all ends being like what DaisyUI, Bootstrap, etc offers and I'm glad DaisyUI is there to make Tailwind feasible for the people who are hot on it (don't realize it might not be a good fit for what they are doing.)
- trevor-e 1y agoYea sure, there are still some spots where I might find DaisyUI helpful, like building a quick internal admin page for something. And another commenter pointed out this works in non-react projects unlike shadcn. But I would know going into it that it will be a pain to customize/maintain, should I ever need to do that. Maybe that's already the expectation for people familiar with Bootstrap though. My advice is more cautionary for folks who search "Tailwind components library", see DaisyUI as the 4th result, and think "great!"
- 1y ago
- sgt 1y agoFor those interested in how to use this with HTMX, read on. DaisyJS supports HTMX as it can work with just plain HTML without needing a fancy JS framework like Vue or React. You start by setting up something that can serve HTML and with a template engine. My favorite is Django. You also need daisyui, tailwindcss etc in a local NodeJS dir. Those parts aren't too hard, I'll skip over it. Now you make sure you build a solid base.html with HTMX bits added. HTMX will fetch content from the Django views. Now if you were using plain Tailwind you'd probably need to use something like django_components to basically make reusable components instead of using HTML. Not with DaisyJS as it simplifies Tailwind vastly; now you can just use <div class="chat-bubble"> and so on, and you get great looking components. Also use template inheritance and includes, which are basic concepts in Django. All in all this is a really clean solution that builds future proof apps without a messy JS framework and and SPA that you most likely don't need. Anyway I'm a big fan of this approach. I get that people have issues with Tailwind itself but one should rather just consider it as a layer of abstraction that we're now skipping.
- alfonsodev 1y agoTotally agree, I do use it with Go lang and echo framework which is very light, I have a very simple vite config to build the css and js, reload everything with air, and it's fast and simple. Edit: I can't prove it but I think even AI coding is more efficient with this approach, clear server side rendering, plain JS with modern features built with vite and CSS classes.
- intrasight 1y agoAny repos or articles you can reference that further explore this approach?
- sgt 1y agoNot really. I think I'll do that and put it on my Medium or something.
- clickety_clack 1y agoI found daisyui through Jeremy Howard’s (python) fasthtml.
- fkyoureadthedoc 1y agoI've worked with and without tailwind, with and without n other opinionated styling solutions. It honestly doesn't matter. Use whatever you want. Your project gets big enough you're going to make a mess of it anyway. Moving to Scoped CSS in Vue components was a pleasure though at the time.
- mattstrayer 1y agoDaisyUI is the best. so easy to _just start_ something.
- lawn 1y agoI really don't understand why you use Tailwind for a CSS component library. To use your component library now people have to use Tailwind, while if you'd used regular CSS both sites with and without Tailwind could use the library (Tailwind is additive on top of CSS after all). Maybe it appeals to people in the Tailwind bubble, and gain momentum that way?
- metalliqaz 1y agoI mean, that's certainly a valid set of users to target: people already using Tailwind that want some off-the-shelf components.
- drewbitt 1y agoI have used DaisyUI as a base class and then extend on it with additional tailwind classes. Sensible defaults.
- kelnos 1y agoI'm using Tailwind mainly because it came installed by default with create-react-router-app, and it seemed easier to just go with the flow (this is my first web project in about 10 years, so I'm re-learning everything), rather than trying to come up with my own bespoke thing. After learning it a bit, I liked Tailwind. Writing CSS manually sucks. It's fiddly, and often you have to sit around adding and changing random things until it looks the way you want, and you have no idea why what you did worked. Tailwind doesn't completely fix that, but it makes it significantly better. But I don't feel like building my own components from scratch. That's where DaisyUI comes in to make my day easier. But if I want to override any of DaisyUI's choices, I have Tailwind's easier-to-use classes that I can use to easily do so.
- ashdev 1y agoI didn't like Tailwind initially, but after using it for a week, it's hard to go back to regular CSS or even SCSS. I have a project that uses SCSS, and sometimes I wish I was using Tailwind instead, it makes the workflow so much easier. I'd highly recommend people try out Tailwind for a week on their projects before giving up on it. That said, I haven't tried DaisyUI so no opinions on that.
- throwingrocks 1y ago> instead of writing 100 class names for every element, every page, every project, again and again… I'm turned off from daisyUI with marketing like this. The alternative to daisyUI certainly isn't this. I use Tailwind in a similar way that daisyUI does: by putting my utility classes in components and reusing the components. daisyUI's value prop is that not everyone wants to do this for their custom design system. They should just stick to that instead of making false claims.
- JakeSc 1y ago"instead of writing 100 class names For every element, every page, every project, again and again… use semantic class names sunglasses emoji It's descriptive, faster, cleaner and easier to maintain." Semantic class names!? Brilliant. Does it seem like the web is reinventing itself to anyone else?
- kwar13 1y agoWrapper of a wrapper. Front end dev is a mess lol
- rossant 1y agoYou summed it up pretty well.
- klaussilveira 1y agoIt is a shame that https://smacss.com https://smacss.com never caught on and, instead, Tailwind won. DaisyUI is almost there, but it's just one of few projects that follow this architectural guideline.
- elpalek 1y agoQ: Has anyone used claude working with DaisyUI? Don't like claude's default ui choices.
- cafp12 1y agoAny of you that bitch about this actually used it?
- martini333 1y agoSooo... Just like using componenets with Tailwind, as intended?
- guluarte 1y agoi dont get it, this is a wrapper on top of tailwind that is a wrapper on top of css?
- wrs 1y agoTailwind gives me the same feeling of impotent nerdrage that Helm does. In both cases, as soon as I figured it what it was really doing, I was like, no. This is just…wrong. (I’m sure people find it useful in some way, despite that.)
- dang 1y agoRelated: DaisyUI: The most popular component library for Tailwind CSS - https://news.ycombinator.com/item?id=38978290 https://news.ycombinator.com/item?id=38978290 - Jan 2024 (1 comment) My Journey to build daisyUI: Why Tailwind CSS was not enough? - https://news.ycombinator.com/item?id=38727252 https://news.ycombinator.com/item?id=38727252 - Dec 2023 (16 comments) DaisyUI – Tailwind CSS Components - https://news.ycombinator.com/item?id=28004515 https://news.ycombinator.com/item?id=28004515 - July 2021 (166 comments)
- kolanos 1y agoA bit baffled by all the "Why not just use CSS?" comments here. Did we forget how much of a pain CSS still is? For example, I recently made a UI with a series of numbered steps. To the left of each step is a number with a circle around it as a highlight. The CSS I came up with looked like this: .step-number { align-items: center; background-color: #0074cc; border-radius: 50%; color: white; display: flex; font-size: 14px; font-weight: bold; height: 24px; justify-content: center; line-height: 24px; margin-right: 10px; width: 24px; } Did it produce a circle? Of course not. It produced a squished egg shape. What did I have to do? I had to add "min-width: 24px;" to the class. Why? Hell if I know. "width: 24px;" should've done the job. Bootstrap (and now Tailwind) exist for a reason: CSS still sucks.
- b_e_n_t_o_n 1y agoYeah it's odd, CSS is pretty horrible to use and Tailwind eliminates some of its biggest problems (cascading, naming, organisation). DaisyUI isn't some sort of return to traditional CSS, it's a way to componentize your markup if you aren't using a system that has components built in, like React et al. This isn't some sort of full-circle reinvention of the wheel.
- pinoy420 1y ago[dead]
- focusgroup0 1y ago```html <button class="btn"> ``` Congratulations! You've invented Bootstrap.
- vitaflo 1y agoJust with two extra abstractions on top of it to get the same result.
- graypegg 1y agoFiddling with the theme builder, [0] wow I really like how well done it is! Like a few other comments have said, you can tell when a website uses bootstrap/a tailwind theme you've seen before. The customization options do actually give just enough leeway to make something "not daisyUI like" while not looking garish. The colour themes to pick from are a nice touch too, many theme-rollers just give you a single theme and 100s of colours to configure individually yourself. I don't use tailwind myself but I might try it with a this as a theme. [0] https://daisyui.com/theme-generator https://daisyui.com/theme-generator
- comechao 1y agoDaisyUI is like Bootstrap, it's great for me, I'm not a front-end developer. I'm using Rails and DaisyUI to build apps.
- sureglymop 1y agoOnly tangentially related but does anyone know if it's possible to override tailwind locally (in some component) with regular css, perhaps scoped to that component? For example, tailwind typography is really nice but once that prose class is assigned to an element it seems hard to override things inside of that element.
- arathis 1y agoJust switched from Flowbite to Daisy. It’s far simpler, and I don’t have to mess around as much with defining my own button styles etc. As with all tech, Tis all a long road to the middle
- cantalopes 1y agoIs it just me or the tailwind users actually learned what is a semantic css?
- presentation 1y agoOr use a better atomic CSS in JS tool like Panda CSS and just make a mixin however you want (or use their batteries included library if you don’t want to). It’s too bad Tailwind is so popular despite it being so bad at composition and unreadable.
- wetpaws 1y ago[dead]
- upghost 1y agoSo for everyone hating on Daisy and Tailwind, what is the alternative? I do my best to use vanilla CSS, BEM style, with SCSS preprocessing, but it's not incredibly intuitive, it's apparently hard for most "full stack" devs to do because they think it is beneath them so they will reach for something like MaterialUI. I agree with the criticisms about tailwind and Daisy but the problem these seem to solve that vanilla CSS does not is that Tailwind for all of its quirks requires less internal agreement than vanilla CSS. Without internal agreement every dev does their own crazy thing to the CSS and it turns to spaghetti fast. So again my question is, what is my alternative here that gives me this property of "nicely packaged, well documented, modular, scalable CSS" without using Tailwind/Daisy?