TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

DaisyUI – Tailwind CSS Components

474 点作者 jonifico将近 4 年前

49 条评论

armchairhacker将近 4 年前
We&#x27;ve gone full circle - CSS components to inline CSS-in-HTML back to CSS components.<p>But I actually think I will use this. A big problem with CSS is that you end up making overrides no matter how composable you make the classes. And some simple things (e.g. responsiveness) are unintuitive and &#x2F; or annoying to do in CSS. Hence Tailwind&#x27;s &quot;CSS-in-HTML&quot; mini classes. But that doesn&#x27;t fill the core purpose of CSS, bigger general-purpose classes to avoid repetition. Combine the two (general classes + mini classes for slight case-by-case fixes) and you get the best CSS experience I&#x27;ve seen so far (at least I think, I haven&#x27;t tried it yet).
评论 #28006552 未加载
评论 #28009159 未加载
评论 #28007960 未加载
评论 #28006536 未加载
评论 #28006452 未加载
评论 #28015106 未加载
评论 #28007586 未加载
评论 #28007514 未加载
whoisjuan将近 4 年前
I’m not saying this is ugly but the visual execution of some of these components is poor. No good usage of padding in some examples, poor ratios between the typography and the containers, inconsistent use of different line widths and border radius, weird and incosistent design choices in spacing and proportions…<p>I mean. This looks alright and it will certainly make any UI look pretty decent, but the execution is not superb like the actual TailwindUI library which is incredibly well thought from a visual design perspective. Those components are perhaps less shiny than these but they are incredibly functional and way more intentional.<p>This is a good effort though and I hope to see it improving.
评论 #28004954 未加载
评论 #28006519 未加载
评论 #28005219 未加载
评论 #28005231 未加载
评论 #28007317 未加载
评论 #28004969 未加载
评论 #28004952 未加载
btbuildem将近 4 年前
Ok, I&#x27;ll guess I&#x27;ll be the lone voice of dissent here. I don&#x27;t like it. I think it goes against the concept of utility classes &#x2F; functional CSS. As soon as you start making component-level classes, things begin to become opinionated and you lose the universality.<p>My understanding of the functional CSS approach was that you&#x27;d make a button component, and use the variety of &quot;atomic&quot; classes to style it. If you&#x27;re using a &quot;btn&quot; class etc, it muddles the distinction of where the semantics live, and things get harder to reason about &#x2F; debug.
评论 #28008018 未加载
评论 #28008049 未加载
评论 #28008496 未加载
eric4smith将近 4 年前
Very welcome. Sometimes the amount of classes needed in Tailwind is enormous.<p>I paid for the TailwindUI pack too. But as nice as Tailwind is, the guys who built TailwindUI don&#x27;t really get or understand a lot of real-world design patterns.<p>A lot of stuff in there is needlessly complicated. Our team end up trimming down things to 50% of the markup that they use, while retaining full responsiveness.<p>Overuse of flex for simple paradigms is a constant complaint of mine.<p>Hope DaisyUI improves Tailwind in some way.<p>Anyway... sorry to get sidetracked on a sidebar.. lol.
评论 #28006870 未加载
评论 #28009234 未加载
评论 #28007299 未加载
评论 #28006128 未加载
评论 #28007590 未加载
conatus将近 4 年前
Cool to see this out, but there is something about Tailwind I&#x27;ve never really got. And this is not from abstraction, but in production use on a number of pretty large sites.<p>Each Tailwind class corresponds to a CSS property, with a few exceptions where you have utility classes for degrees of that property (for example, padding, margin). Then along come these CSS component libraries, which substitute a thicket of these utility classes for a single class. Including Tailwind UI itself.<p>Given that the relationship of class to property is one to one, why not cut out the middle person and just use CSS directly? There seems no real advantage. You&#x27;ve basically indepedently re-invented CSS, while adding a strange layer of additional abstraction on top. It is nice and fast to write it in the HTML I&#x27;ll grant, but, the speed advantage is not so great that it is worth it compared to the mental overhead of other aspects of working with Tailwind (e.g. having to trim all the classes with automated scripts and so on).<p>Perhaps I am missing something here?
评论 #28011206 未加载
hashedout将近 4 年前
This is a very nice step in making Tailwind more Bootstrap like (read beginner friendly). One common complaint about Tailwind is that it makes the HTML look very full (full of classes).<p>A very good example on OP&#x27;s website for a button:<p>Using tailwind:<p><pre><code> &lt;a class=&quot;inline-block px-4 py-3 text-sm font-semibold text-center text-white uppercase transition duration-200 ease-in-out bg-indigo-500 rounded-md cursor-pointer hover:bg-indigo-600&quot;&gt;Button&lt;&#x2F;a&gt; </code></pre> Using daisy:<p><pre><code> &lt;a class=&quot;btn btn-primary&quot;&gt;Button&lt;&#x2F;a&gt; </code></pre> Although I personally think that the corners at a bit too rounded by default, giving it a very amateur look but I think you can customize that.<p>But a very promising project indeed.
评论 #28004988 未加载
评论 #28005067 未加载
评论 #28005008 未加载
评论 #28004973 未加载
评论 #28007085 未加载
评论 #28005052 未加载
swyx将近 4 年前
Other tailwind component libraries I track:<p>- <a href="https:&#x2F;&#x2F;github.com&#x2F;thedevdojo&#x2F;tails" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;thedevdojo&#x2F;tails</a><p>- <a href="http:&#x2F;&#x2F;tailwindcomponents.com&#x2F;" rel="nofollow">http:&#x2F;&#x2F;tailwindcomponents.com&#x2F;</a><p>- <a href="https:&#x2F;&#x2F;tailwindui.com&#x2F;components" rel="nofollow">https:&#x2F;&#x2F;tailwindui.com&#x2F;components</a><p>- <a href="https:&#x2F;&#x2F;merakiui.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;merakiui.com&#x2F;</a><p>- <a href="https:&#x2F;&#x2F;www.gustui.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.gustui.com&#x2F;</a><p>- <a href="https:&#x2F;&#x2F;mertjf.github.io&#x2F;tailblocks&#x2F;" rel="nofollow">https:&#x2F;&#x2F;mertjf.github.io&#x2F;tailblocks&#x2F;</a><p>- <a href="https:&#x2F;&#x2F;shuffle.dev&#x2F;" rel="nofollow">https:&#x2F;&#x2F;shuffle.dev&#x2F;</a> Tailwind visual builder<p>(from my resources list <a href="https:&#x2F;&#x2F;github.com&#x2F;sw-yx&#x2F;spark-joy&#x2F;" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;sw-yx&#x2F;spark-joy&#x2F;</a>)
NaN1352将近 4 年前
Looks good. I’d really like to use this. Mainly I like that the author used same approach as I do whereby with careful use of low specificity, a custom &quot;btn&quot; class can be further customized just by adding TW classes (ie. not css specificity issues).<p>My only gripe with this is that you should then use a clearly defined and separate naming convention for custom classes, for example SuitCSS is good:<p>Not<p>btn btn-large rounded-full<p>But<p>du-Btn du-Btn—-primary rounded-full<p>ie. PascalCase component names,<p>optional prefix (eg. du for daisy ui, because other apps also have their prefix see eg. Twitch and Algolia css)<p>Bem conventions like double dash for modifier as opposed to a descendant<p><a href="https:&#x2F;&#x2F;github.com&#x2F;suitcss&#x2F;suit&#x2F;blob&#x2F;master&#x2F;doc&#x2F;naming-conventions.md" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;suitcss&#x2F;suit&#x2F;blob&#x2F;master&#x2F;doc&#x2F;naming-conve...</a><p>So yeah I would like to be able at a glance to know where a class is from. &quot;btn&quot; is not from tailwind, but where is it from? What if my app uses multiple components, from third party etc? It’s not clear.<p>Other than that This is better than Bootstrap approach even with custom classes, because you take care of css specificity problem (assuming you can add a tw class anywhere and override the builtin custom classes)...<p>this is the middle way that nobody uses for whatever reason, the one that makes sense, but requires a good basic understanding of css specificity as well as setup stringent css linter<p>Also using a convention would let you use a good linter on the custom selectors<p><a href="https:&#x2F;&#x2F;github.com&#x2F;postcss&#x2F;postcss-bem-linter" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;postcss&#x2F;postcss-bem-linter</a>
评论 #28010029 未加载
jpomykala将近 4 年前
You are trying to solve problems which were created by Tailwind, and you end up with Bootstrap.
评论 #28006488 未加载
FractalHQ将近 4 年前
I am so glad that I took the time to get fast with CSS. I can build unique UIs in real time, and with Svelte Components, everything is automatically scoped to the component. I would waste so much time and gave a lot of analysis paralysis if I had to choose from all these cool looking libraries and frameworks, learn their api’s, and then learn how to override them more and more over time.
eenberg将近 4 年前
That page is extremely slow without hardware acceleration. It (hw-accel) was off for me because I updated some things without restarting Chromium, but I dunno. It doesn&#x27;t &quot;spark joy&quot; with me.
评论 #28007678 未加载
评论 #28008669 未加载
runawaybottle将近 4 年前
My goodness Bootstrap, how far ahead of your time you were. To this day we copy you, god bless you m’lord.<p>Nope, I reject this. We should be so much farther ahead than this. It’s the garbage fullstack developers that need this crap to make a good ui. They don’t belong on the frontend, and I’m pretty tired of it.<p>Our UI&#x2F;UX will get shittier and shittier if we coddle this group.
评论 #28006595 未加载
评论 #28005945 未加载
volkandkaya将近 4 年前
DaisyUI is a great starting point but it is missing a lot to make it functional and then you end up recreating the wheel.<p>I agree with some comments that it is lacking that wow factor that TailwindUI has.<p>I&#x27;m working on <a href="https:&#x2F;&#x2F;versoly.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;versoly.com&#x2F;</a> which is a Tailwind Website builder and have ran into a bunch of issues with Tailwind when it comes to building static sites.<p>I love that Bootstrap offer &quot;btn btn-primary&quot; and it makes it very easy to keep a consistent site.<p>For Tailwind to take off it needs<p>- A list of components (maybe 20 ish, buttons, tabs, navbars being the main ones) - JS for components - Container system (I have built one that works similar to Bootstrap and makes it much easier to create responsive layouts quickly)<p>Once those core parts have been built I believe developers will create more advanced libraries such as lightboxes etc which will save even more time.<p>I&#x27;m a big fan of the new <a href="https:&#x2F;&#x2F;github.com&#x2F;vuejs&#x2F;petite-vue" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;vuejs&#x2F;petite-vue</a> which is only 5kb and comes with a lot of power. Also combining it with something like <a href="https:&#x2F;&#x2F;github.com&#x2F;CaptainCodeman&#x2F;x-transition" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;CaptainCodeman&#x2F;x-transition</a> would be interesting.<p>I really want to see Tailwind grow so if you&#x27;re interested in opensource or want to create paid UI kits feel free dm as I have a ton of ideas.
评论 #28005347 未加载
kemyd将近 4 年前
That&#x27;s an interesting approach with bootstrap-like class names.<p>At Shuffle[1], we create templates for Tailwind, Bootstrap, Bulma, and Material-UI and need to convert UI libraries from one technology to another.<p>We decided to write converters that can transform HTML classes &amp; Tailwind config to Sass config.<p>Probably, we will release it as open-source soon.<p><pre><code> &#x2F;&#x2F; Example: &#x2F;&#x2F; Tailwind.config to Sass &#x2F;&#x2F; button.js const { theme } = require(&#x27;..&#x2F;theme.config.js&#x27;); module.exports = { bootstrap: { &#x27;input-btn-font-size&#x27;: theme.fontSize.sm[0], &#x27;input-btn-padding-y&#x27;: theme.spacing[4], &#x27;input-btn-padding-x&#x27;: theme.spacing[6], }, bulma: { &#x27;size-normal&#x27;: theme.fontSize.sm[0], &#x27;button-padding-vertical&#x27;: theme.spacing[4], &#x27;button-padding-horizontal&#x27;: theme.spacing[6], }, }; &#x2F;&#x2F; HTML export const mappings = [ { from: [&#x27;flex&#x27;, &#x27;flex-wrap&#x27;, &#x27;-mx-4&#x27;], to: [&#x27;row&#x27;] }, } </code></pre> [1] <a href="https:&#x2F;&#x2F;shuffle.dev" rel="nofollow">https:&#x2F;&#x2F;shuffle.dev</a>
cjohansson将近 4 年前
I believe in semantic class-names, I know one can transform tailwind into cleaner markup but it seems to introduce more work than just building from scratch
FrontAid将近 4 年前
That page broke tabbing through interactive elements by using nested focussable elements like this:<p><pre><code> &lt;div tabindex=&quot;0&quot;&gt;&lt;input ...&gt;&lt;&#x2F;div&gt; </code></pre> Because of that, it is sometimes necessary to tab twice to focus the next element. Not sure whether that is a problem of DaisyUI in general or just their website. But it is definitely annoying.
axegon_将近 4 年前
Great! Over the past 6 months or so I&#x27;ve noticed a trend which I like: people are less obsessed with all the modern react-angular-vue-js-everything-html-css-bad notion and a lot of people are starting to admit that this whole sack of gibberish is unmanagable and unmaintainable(the web got it&#x27;s own version of segfaults where something crashes and no one has even the slightest idea why) and we are coming full circle back to the late 2000&#x27;s internet. Which to my mind was the golden age of the internet: you could slap a vga cable onto a potato and it had the computational power to display any page, whereas in recent years a single page eating up 200+ mb of your memory and increasing the cpu usage by 15-20% was a completely normal phenomenon. Oh and let&#x27;s not forget &quot;ew jquery, that&#x27;s 200kb, that&#x27;s horrible&quot; all while bundle.min.js is a 15mb freak. Good job, personally I had completely lost hope, now I am starting to have some.
XCSme将近 4 年前
I am not sure this is production-ready. I had a look over some components and the UI&#x2F;UX is poor in general (bad alignment, padding, bad accessibility, no proper focus traps, no keyboard support, etc.). Maybe some of those are lacking because it is a CSS-only implementation? But you still can&#x27;t use them as it is without proper accessibility support.
tpetry将近 4 年前
I am more impressed by the landing page than the actual components. Is anyone aware of a good component library for landing&#x2F;marketing pages for Tailwind?<p>There are toolkits like <a href="https:&#x2F;&#x2F;frontendor.com" rel="nofollow">https:&#x2F;&#x2F;frontendor.com</a> but they all follow the 5-10 year old &quot;theme&quot; of insanely packed content you had seen on SaaS pages some years ago. Together with many photographs or flat humans... I can&#x27;t find anything with &quot;new&quot; approach which uses more padding, much more detail to typography, bigger fonts etc. shown very good on the <a href="https:&#x2F;&#x2F;tailwindcss.com" rel="nofollow">https:&#x2F;&#x2F;tailwindcss.com</a> landing page. Or any hint where all the new startups get their designers for these new fresh layouts?
评论 #28005155 未加载
评论 #28005369 未加载
评论 #28005292 未加载
timwis将近 4 年前
Interesting side effects of css utility frameworks: I was trying to scrape a website that uses tailwind this week and it’s really difficult, as nothing had a unique class name.
评论 #28005257 未加载
评论 #28006222 未加载
Aeolun将近 4 年前
I tried using Tailwind, but I just couldn’t get into it. It’s like having to learn CSS all over again because the classnames do not map 1-1 with their respective properties, and autocomplete is lacking.<p>Conversely, Chakra UI Box, which does more or less the same thing is super easy to get into.<p>This looks nice, but I kind of feel like we’ve come full circle two full times to get to this point.
评论 #28005606 未加载
DLA将近 4 年前
Using DaisyUI for three projects currently and LOVE the hell out of it. Don&#x27;t get me wrong I love some TailwindUI as well, but the simplicity of Daisy is fantastic. Winning combination for us: DaisyUI + TWCSS + AlpineJS + Go Fiber server &amp; templates.
irrational将近 4 年前
Anyone with experience using Tailwind UI want to comment on how this compares?
评论 #28004944 未加载
评论 #28005617 未加载
评论 #28004957 未加载
tomcooks将近 4 年前
Real nice, pity the &quot;see component&quot; popup that appears when clicking on anyhomepage component prevents from checking it out and there is no way to hide said popup<p>Real nice, looks professional and casual - well done!
评论 #28007779 未加载
soheil将近 4 年前
Oh I pray that I remember this website next time I&#x27;m looking for an HTML&#x2F;css template. Great job, this UI looks so polished and is as modern as it gets.
评论 #28005029 未加载
sgt将近 4 年前
Recently bought Tailwind UI. Haven&#x27;t really used it much except for a concept UI, and didn&#x27;t work completely out of the box (you kind of have to know something about Tailwind the open source project first).<p>Aside from that, it looks like a really convenient way to put together a web UI when you don&#x27;t really want to focus on the UI part of your app too much.<p>Not too expensive either, I think it was $175 or so.
robertwt7将近 4 年前
So much love for tailwind, I love it. Honestly though I haven&#x27;t use any other component than Material-UI for the past couple of years. I was thinking to convince my previous company to buy tailwind-ui just for the sake of curiosity :p but then I know I won&#x27;t use it much. So not sure..<p>In the end the point of all of us using tailwind is because its not &quot;opinionated&quot; like bootstrap right?
hardwaresofton将近 4 年前
In this space also: <a href="https:&#x2F;&#x2F;blocks.wickedtemplates.com" rel="nofollow">https:&#x2F;&#x2F;blocks.wickedtemplates.com</a><p>(NOTE: I did not WickedBlocks&#x2F;WickedTemplates -- it&#x27;s the awesome work of the folks over at WickedTemplates <a href="https:&#x2F;&#x2F;wickedtemplates.com" rel="nofollow">https:&#x2F;&#x2F;wickedtemplates.com</a>, which they shared on HN I believe a while back)<p>I&#x27;m actually working on a little side project right now where I turn wickedblocks into a set of usable native web components (as in drop an &lt;import&gt; tag and the component on your page and you&#x27;re off to the races), because I think that&#x27;s a much more composable way to use these snippets copy &amp; pasting HTML, looks like Daisy needs to be next.<p>[EDIT] A bit annoying to others probably to drop a lede and I have no idea when I&#x27;ll get done and publish it with the blog post so if someone just wants to see the code:<p><a href="https:&#x2F;&#x2F;gitlab.com&#x2F;mrman&#x2F;landing-gear" rel="nofollow">https:&#x2F;&#x2F;gitlab.com&#x2F;mrman&#x2F;landing-gear</a><p>If anyone wants to contribute a snazzy icon I&#x27;d love to take it! There&#x27;s no landing page to showcase it yet but there&#x27;s files like lg-left-header&#x2F;index.html[0] which showcase usage and the intended simplicity.<p>Obviously if you&#x27;re trying to get started, use the blocks as they&#x27;re presented and the awesome work done by WickedTemplates (they&#x27;ve also got some ready-to-go straight out of the box templates and other stuff for you to use on their main site!), but if you&#x27;re interested in lit[1]-powered drop-in components, follow that space.<p>[EDIT2] - For those taking a look at the code, note that there are like... 4 variants of the left-header component. Half of the time spent getting this out (it&#x27;s all simple in theory -- just copy + paste and swap out static text for variables) was figuring out which parts to unify and which parts to keep separate for easy drop-in use. There&#x27;s not much there yet, but it&#x27;s more a matter of me finding time to sit down and make these decisions for every kind of component on the wickedblocks page.<p>There are some concerns like i18n that I&#x27;ve punted on by just making sure that all static text were component inputs, but ideally integration with browser-supported i18n[2] is the proper way to do things in a minimal but standards compliant way.<p>[EDIT3] - Added note to make it clear I didn&#x27;t create WickedBlocks&#x2F;WickedTemplates<p>[0]: <a href="https:&#x2F;&#x2F;gitlab.com&#x2F;mrman&#x2F;landing-gear&#x2F;-&#x2F;blob&#x2F;main&#x2F;lg-left-header&#x2F;index.html" rel="nofollow">https:&#x2F;&#x2F;gitlab.com&#x2F;mrman&#x2F;landing-gear&#x2F;-&#x2F;blob&#x2F;main&#x2F;lg-left-he...</a><p>[1]: <a href="https:&#x2F;&#x2F;lit.dev&#x2F;" rel="nofollow">https:&#x2F;&#x2F;lit.dev&#x2F;</a><p>[2]: <a href="https:&#x2F;&#x2F;developer.mozilla.org&#x2F;en-US&#x2F;docs&#x2F;Mozilla&#x2F;Add-ons&#x2F;WebExtensions&#x2F;API&#x2F;i18n&#x2F;getMessage" rel="nofollow">https:&#x2F;&#x2F;developer.mozilla.org&#x2F;en-US&#x2F;docs&#x2F;Mozilla&#x2F;Add-ons&#x2F;Web...</a>
评论 #28005249 未加载
jcq3将近 4 年前
Yet another bootstrap? I don&#x27;t see any difference. Sorry I&#x27;m not a frontend dev, what&#x27;s the value added of this?
debarshri将近 4 年前
I am new to UI&#x2F;UX. Is it comparable to bootstrap? How is it actually different from the CSS and UI component libraries?
评论 #28007359 未加载
Brajeshwar将近 4 年前
For those wishing to learn the intricacies and beauty of Tailwind, this is a good source. Well written code but might lack the finesse of design. Then use TailwindUI[1] as a kit for your design&#x2F;frontend team.<p>1. <a href="https:&#x2F;&#x2F;tailwindui.com" rel="nofollow">https:&#x2F;&#x2F;tailwindui.com</a>
happy_one将近 4 年前
Is there something exactly like this that doesn&#x27;t depend on tailwind?<p>Using bootstrap themes are what I do now but they always have a limited number of components and don&#x27;t have ready to go, copy-pastable documentation.<p>Ideally I&#x27;d have a library that I can just copy paste beautiful pre-made components.
z3t4将近 4 年前
As an old school web dev I write semantic HTML by hand and try to avoid using classes...
vachi将近 4 年前
My team and I also made a similar library, more so for dashboards. <a href="https:&#x2F;&#x2F;github.com&#x2F;mutable&#x2F;meiosis" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;mutable&#x2F;meiosis</a>
ponyous将近 4 年前
This library highlights the biggest issue of tailwind for me.<p>&gt; Clean HTML<p>The rest of your code will still use bunch of shitty tailwind shortcuts that are really chaotic the moment you build something more than a simplest component.
评论 #28007488 未加载
devops000将近 4 年前
Very cool! Would be great to have tile as checkbox component. <a href="https:&#x2F;&#x2F;youtu.be&#x2F;h_7gV44rA-Q?t=19" rel="nofollow">https:&#x2F;&#x2F;youtu.be&#x2F;h_7gV44rA-Q?t=19</a>
jbverschoor将近 4 年前
So I don&#x27;t understand. People are complaining about bootstrap for defaults. Then daisyui has great defaults, and the same class names. I see no reason to customize daisy.
chris_st将近 4 年前
Really like DaisyUI, it&#x27;s a nice quick way to get a light, consistent page built.<p>I recently found a problem with DaisyUI, put up an issue, and it was promptly and politely fixed.
catmanjan将近 4 年前
I&#x27;ve heard a lot about how great tailwind is, can anyone point to some good examples of people using it? Most of what I can find is just samples
评论 #28005178 未加载
gauchojs将近 4 年前
I feel like designing for the web is so hard compared to elements that work on the phone. This elements look very &quot;phone sized&quot;.
nunodonato将近 4 年前
welcome to bootstrap
bilekas将近 4 年前
This is actually beautiful, and really clean.. I will definitely be giving this a try. Nice job!
sandGorgon将近 4 年前
this is so good!<p>I wish the author would also put up a purchase page on <a href="https:&#x2F;&#x2F;themeforest.net&#x2F;" rel="nofollow">https:&#x2F;&#x2F;themeforest.net&#x2F;</a> . I dont mind optionally paying for it - especially a nicely packaged starter for nextjs, etc
midrus将近 4 年前
This looks awesome. Definitely will use it in my next project. Great work!!!!!
geenat将近 4 年前
Super laggy components.
gcatalfamo将近 4 年前
Could somebody who used both this and Bulma give an overview?
ceiphr将近 4 年前
I love the little Cyberpunk theme example.
csabakissi将近 4 年前
One of the best looking tailwindcss components. I&#x27;m wondering if this library will grow in the future to something much bigger.
thrownaway561将近 4 年前
so you recreate bootstrap with tailwinds... we&#x27;ve come full circle.