Tailwind is the most counterintuitive yet obvious-in-hindsight CSS tool (or of any class - no pun intended) I've worked with.<p>I know the general sentiment towards Tailwind is "I spent years getting my separation of concerns with HTML/CSS down, but now you're telling me all that is backwards and CSS Zen Garden is blasphemy?" I was in the same boat. Tailwind just felt wrong, and with 15+ years of experience, I've come to trust my intuition. After watching several videos, and reading all the canonical articles on Tailwind, I still wasn't convinced this was anything more than a fad full of bad practices.<p>But the one thing I'll let trump my intuition is curiosity. So I used Tailwind on a medium-sized project for a couple months and was blown away by the productivity and maintainability. It took using it for a couple weeks to "get it". I had a positive ROI on this project, even considering the learning curve!<p>If you still think "Tailwind feels wrong, what am I missing?" I'd suggest reflecting on the following:<p>1) You probably haven't actually delved into Tailwind on a non-trivial project. I understand learning a new framework isn't a trivial undertaking, but it's the only thing standing in your way of discovering your "truth".<p>2) If you feel Tailwind is too much like inline styles, think of the difference between the infinite possibilities of strings defining a "type" vs. a discrete enum type. Tailwind classes are the enum type values.<p>3) If you're struggling to abstract reusable higher-level classes/components, the problem might actually be with inconsistent and non-modular design, not CSS tooling. If every page or section is a "unique work of art" then you may have poor UX/design.
Framework author here! Don't miss the new landing page, it is probably the part I was most excited to share :)<p><a href="https://tailwindcss.com/" rel="nofollow">https://tailwindcss.com/</a><p>Crazy amount of effort went into building all of these interactive examples, so proud of how it turned out.<p>The trailer in the blog post is absolutely 100% a joke in case it's not obvious. The music was scored for us by a friend, and that's a real life professional opera singer at the end chanting "utility first" in Latin. It's completely absurd and absolutely outrageous, just laugh at it :)
The things I love the most about TailwindCSS:<p>1. After purged the CSS file is really, really small.<p>2. Hopping into all of my projects and not having to remember new class names.<p>3. Not having to come up with new class names.<p>4. Not worrying about making a change in a class and having unintended consequences.<p>5. Not skipping back and forth between HTML or CSS files.<p>That said, if you don't dig it, there are plenty of other great frameworks, naming conventions and approaches that people use. Or start from scratch and roll your own.<p>For frameworks I flirted with InuitCSS for a bit. It's pretty nice and after digging through the code I realized it's not as complex as it first appears.<p>I also like Andy Bell's approach with Cube CSS.
I don't do front end dev, and haven't for a very long time, but can someone help me understand how this doesn't lead to inflexible hard to maintain soup? Just to take colours, for a moment. Ordinarily I might define semantic classes, let's say "primary-nav" or "prominent-action" and apply them to relevant things (and use relative selectors for things inside them, etc.). So if I want to change the colour of all prominent-actions across my web app, I just do it in one place. This seems to be demo-ing adding a particular colour class to everything I want to be that colour. So... If I change my mind, what now? I have to find all those places and change the applied class? Search and replace?<p>This seems like the literal opposite of the clean separation I always understood to be the point of styling being separate to markup...
"Incompatibility with IE11, so you can tell the man upstairs 'sorry boss it's out of my hands, blame Tailwind'..."<p>I know it's said tongue-in-cheek, but popular frameworks taking this stance is valuable when convincing clients, leaders, authority, etc. to not require IE support. I've consulted on dozens of front-end projects, and showing the stance of "industry leaders" is the most convincing argument.
What often gets missed in the tailwind debate is how it forces you to use a design system. When you’re writing CSS by hand it can quickly get out of control when you need to bump something up or down, left or right by a notch. If you add padding it should be related to font size, line-height, etc on some sort of cohesive, harmonious scale. By using a Tailwind class of py-2 rather than writing a CSS class you can be confident that the change will fit with the design system as a whole. This is much better for most people than creating your own design system from scratch every time you need to make a web page. Once your design starts to solidify, just extract out common components like “button” out of the html using @apply.
For those complaining about dense HTML using Tailwind, the headline feature of 2.0 should be @apply for everything: <a href="https://tailwindcss.com/docs/functions-and-directives#apply" rel="nofollow">https://tailwindcss.com/docs/functions-and-directives#apply</a><p>It lets you move all of those excessive class attributes into your CSS, where it realistically belongs. And that makes your CSS look a little more like CSS. But you get guard rails on it by applying a known set of properties to each rule. It's really the best of all worlds.
I've been writing CSS since the beginning of the web2.0 days and so it was really hard for me to adjust to the Tailwind approach. It's by no means perfect, but after working almost exclusively with it (and Tailwind UI) I am a big believer. I find myself wanting all the utilities almost immediately as soon as I am back on any other project/codebase.
Tailwind smells like using a style attribute but with properties that are fewer characters. It's fully embracing what everyone said to avoid. What am I missing?
Their marketing is good, they do a primo job at conveying the message in a nice looking way, but the end result is still HTML littered with hundreds classes, that gets hard to maintain and impossible to refactor.
I used to a skeptic, to the point where I thought it was completely ridiculous. Then I realized that I was over-using inline styles anyway since I was always afraid of messing with old CSS. I was adding layers of overwrites just not to accidentally change something unrelated.<p>Now I can't imagine myself ever writing regular CSS again. I just love how I can look at the HTML and instantly "visualize" how the component will look just by seeing the classes. No more mysterious cascades where it's hard to pinpoint where the styling is coming from. It makes iteration so fast and responsive design has never been easier.
I use TailwindCSS for some personal projects, works great, no major complaints. But as a dev in the government sector, I'm disappointed in the way they just whimsically dump Internet Explorer 11 in their release notes [1], as if it's a minor thing / cool to hate on.<p>In my bubble, there's no alternative right now. Switching to a more modern browser requires an enormous amount of agility throughout the pipeline that does not exist. To adopt a shiny new browser, agencies would need to push browser updates to all their client machines every ~4-6 weeks [2]. Solution providers need to perform continuous testing on their web apps (browser vendors do not guarantee minor updates are backwards compatible), creating patches, which need to be submitted to the government for regression testing... and oops that took too long and the next EOL is here.<p>With Microsoft's surprise obsolescence of Internet Explorer 11 across all its cloud offerings 1Q 2021, we're headed straight into a brick wall. Very interested to see what shakes out here.<p>I suspect initially we'll see the government just deploy and use older unsupported copies of Chrome/Edge browser, under the guise of "well it's better than IE11 right?". Longer term, ...?<p>[1] <a href="https://blog.tailwindcss.com/tailwindcss-v2#incompatibility-with-ie11" rel="nofollow">https://blog.tailwindcss.com/tailwindcss-v2#incompatibility-...</a><p>[2] Vendors do not support these versions after EOL for any reason. Firefox has an ESR branch, bless them, but some agencies have now increased scrutiny of Mozilla software for recent political/security reasons.
I've gone through the following phases:<p>1. Write old school circa 2008 CSS.<p>2. Oh shit, it's a real pain in the ass to do layout and make a responsive grid. Let me use a framework. Sweet!<p>3. Hmm.. its kinda painful to write css selectors all day long. They're reusable but I am having to get out of comfy JS IDE setup to go change some CSS properties in a different file.<p>4. Tailwind arrives. OMG. This is awesome! Never have to leave the context. Just stack properties as you like and compose your components!<p>5. HTML looks completely unreadable. It's a goddamn mess.<p>6. I want to go back to 2005. No frameworks. Just write non-responsive CSS, one for each screen (yeah, you read that right. I don't want to compromise the layout for responsiveness. I'd rather handcraft one for each device size give or take a few pixels). Custom crafted like a piece of fine art. CSS grid/layout is a lot better with css grid and flexbox. Things have improves since the 960-grid days. No frameworks at all and its fucking liberating.<p>Edit: I currently use reset/reboot css to clean up default rendering + sass (only use variables + mixins). I am happy like a daisy.
Looked into tailwind 2-3 times and simply couldn't see the appeal. Working on analytical-dashboards in react, I mostly end up writing css straight in js using material-ui's makestyles. There's only so many components to style before I start reusing them and the css needed to make something 'not-look-too-crappy' is actually quite low.<p>Now after learning all the css basics, I'd have to learn yet another 'system' again? I think I'll pass.<p>On the other hand if I'd be constantly restyling webpages with hundreds of different components etc., I might consider it again...
I've seen some incredible things built with Tailwinds, but it still hasn't clicked for me. It seems like you're learning a completely different language for styling and layout. I also have some gripes with optimization in that the suggested solution to eliminating unused CSS is to use a tool that finds classes in HTML files, which is a pretty rudimentary way to accomplish that. (However, I'm sure in more advanced codebases, particularly JavaScript ones, there's probably a better utility to use.)
What kind of projects do people use Tailwind for? and what's the general role of the person using it? I haven't found a use for it myself as a predominantly front-end dev but I've met a few devs who like it a lot but found that they were generally less comfortable writing plain css without a framework. No shade towards Tailwind intended, just not a paradigm I've gotten on board with yet and trying to understand.
I think tailwind is the first thing I’ve ever realized I’m a hipster about. I’ve been using it since early on and bought tailwind UI the instant it came out. I love it.<p>But now that’s it’s super popular I can’t help but wish it was still a quite little secret. Every other product hunt or show hn seems to be using tailwind with all the default configurations so they all have the tailwind look, just as every new startup used to have the bootstrap look.<p>And there are so many tailwind UI knockoffs and tailwind tutorials out there it is insane.<p>I’m super happy for Adam and all the success he and the team are having. Tailwind is a truly great library and now ecosystem.
Forgive me if this comes across condescending or patronising. Genuinely not my intent...<p>So many people reach for a solution without really understanding their own problem.<p>I'm talking specifically about maintainable code. And maintainable CSS code at that.<p>For scaling CSS imagine a continuum with complete isolation one end (BEM, ECSS et al) and complete abstraction at the other (started with 'Atomic CSS', which then spawned countless others including Tailwind).<p>My experience is that either end of that continuum leads to an approach that can scale well and be maintainable. Mixing of approaches is where people come unstuck because they don't understand why that is problematic.<p>Understanding that fundamental (more here: <a href="https://css-tricks.com/scaling-css-two-sides-of-a-spectrum/" rel="nofollow">https://css-tricks.com/scaling-css-two-sides-of-a-spectrum/</a>) goes a long way to dealing with the problem.<p>My preference is isolation (which I detailed at <a href="https://ecss.io" rel="nofollow">https://ecss.io</a> and in the book 'Enduring CSS' about 5 years back — not mentioned to pimp myself, I don't give a hoot if you buy/read)). I like code that is easy to reason about and delete (I like deleting code far more than writing it!) and that suits my mental model.<p>I also believe our job as a front-end developer is to accommodate designs, not turn around and say, "sorry, we don't have a class for 8px margin, it will have to be 5px or 10px". I'm not suggesting this or that framework can't accommodate this need, just highlighting why I feel the way I do and choose the solution I do.<p>Think about how __you__ want to build and maintain code. Don't just jump on something because everyone else does. Analyse your problem. Where are your actual pain points. Find the solution to your own issues. Otherwise you'll just swap one set of problems for another.<p>A framework may very well meet your needs. And by all means listen to others extolling its virtues but that will not save you from a lack of due diligence!<p>[ends attempting to dispense fatherly advice]
> Incompatibility with IE11, so you can tell the man upstairs "sorry boss it's out of my hands, blame Tailwind"<p>For those who don't know, IE11 is the last major release of IE. Between a major frontend framework feeling confident dropping IE, and Apple dropping Intel it kind of feels like the end of an era.
So the biggest advantage of tailwind in my opinion is that it enforces some structure in CSS. I work on small, highly custom designed/branded websites (like marketing product sites) often times with bunch of freelancers of differing skill levels that i might have never worked with before. We also often pass the site to someone else to maintain and upgrade after its finished. For my usecase Tailwind has been simply revelation.<p>If you look at CSS methodologies like BEM, ITCSS, CubeCSS they require developers to learn them and be very disciplined to follow them. These methodologies are probably very effective in orgs where employees work long term. In my case it's always just matter of time before they start to break down. It just takes too much time to onboard devs.<p>Maybe it's not so much about Tailwind being better or the "right way" but about it making very clear how you should structure CSS (put it in html and tailwind.cofing). Other frameworks like bootstrap also enforced something but Tailwind is not UI kit. It infinitely more customizable it can have any look.<p>Tailwind creates less technical debt? Maybe that's how to describe it? For others it will be the exact opossite.
Can't wait to upgrade to v2.0. I've used Tailwind CSS/UI very extensively over the last year or more. The time I've saved in my day to day client dev work is incredible. Some of my notable recent projects using the framework include:<p><a href="https://www.hawking.org.uk" rel="nofollow">https://www.hawking.org.uk</a> (Adam Wathan often uses it as an example of how different sites built in Tailwind can look - <a href="https://twitter.com/adamwathan/status/1298932488769875968" rel="nofollow">https://twitter.com/adamwathan/status/1298932488769875968</a>)<p><a href="https://www.paced.email" rel="nofollow">https://www.paced.email</a> (While a bit more Tailwind-esque, the framework has allowed me to concentrate on functionality while knowing the product will look great in the end).<p>Happy the TailwindLabs team is getting the exposure they deserve. Congratulations folks. Thank you for the awesome tools!
While it may seems like a great idea, I just finished a project for a client on Tailwind.<p>First of all it's not free, to use UI components it would cost many hundreds of dollars.<p>But maybe cost is not an issue for all, on the other hand productivity might be.<p>I found myself terribly less productive, having many classes like:<p><pre><code> <div class="mt-8 mx-4 flex flex-col items-center font-medium text-base ..."
</code></pre>
it's very hard to add or remove a rule compared to CSS where each rule is on it's own line.<p>Also some pretty significant issue for me was hot-reloading taking a lot of time, whereas in CSS you can just refresh linked stylesheet, with tailwind you need to reload complete page, and if your page is hosted on a Django/Symfony/RoR application in development mode, you better have to be patient at each CSS modification !
I don't get why Tailwind is so hot. Do any of you actually maintain large custom design systems?<p>Where the same system is used across multiple code bases, with varying components, where you need to be able to accurately replace the look of a component, that might be coded in multiple dev environments (Angular, PHP, React...)?<p>If so, you would be running away from this approach fast. BEM/ITCSS all the way. How would you globally replace something that is marked up like this (example appears somewhere else in this thread)? How would you assert what this code means across projects?<p><pre><code> class="text-4xl sm:text-6xl lg:text-7xl leading-none font-extrabold tracking-tight text-gray-900 mt-10 mb-8 sm:mt-14 sm:mb-10"
</code></pre>
With BEM/ITCSS, you would have a custom namespace like `auk`:<p><pre><code> class="auk-btn auk-btn--primary"
</code></pre>
And you can reason about it, maybe in project 2 it is<p><pre><code> class="auk2-btn auk2-btn--primary"
</code></pre>
So now you can refactor the old buttons out to replace the new buttons. Good luck with the mess above.<p>If people say: you can use `@apply`. Yeah. If you write your whole stylesheet in `@apply` logic, why are you using Tailwind at all?<p>Design tokens and the re-use of design variables is not a Tailwind thing by the way. Some people seem to be acting like it is. We've had variables in Sass for over since 2009. People have been doing clever things with variable maps (arrays) in Sass since forever. There's no way Tailwind can take credit for this.<p>I've written extensively about why Tailwind is problematic:<p>(1) <a href="https://johanronsse.be/2019/11/11/thoughts-on-tailwind-css/" rel="nofollow">https://johanronsse.be/2019/11/11/thoughts-on-tailwind-css/</a><p>(2) <a href="https://johanronsse.be/2020/07/08/why-youll-probably-regret-using-tailwind/" rel="nofollow">https://johanronsse.be/2020/07/08/why-youll-probably-regret-...</a><p>(3) <a href="https://johanronsse.be/2020/08/20/hey-your-api-surface-is-causing-unnecessary-complexity/" rel="nofollow">https://johanronsse.be/2020/08/20/hey-your-api-surface-is-ca...</a><p>Don't fall for it! The marketing is sweet but the choice will hurt you in the end.
I took over a fairly large project which used tailwind v1. Have a low-hate relationship with it.<p>I like how fast you can do stuff, but when when a designer creates something a bit custom it all falls part really quick.<p>I understand it solve the issue with reusability and style-guides, but for modern apps that would also mean everything should already be react componentized, so you shoudl not really care about css at that point idealy.<p>I rather use a mix styled-components (easily extendable if you need something custom) and css-variables for dark mode and defining global variables like colors,paddings etc. Plus I route-split so page only has it's related styles.
Re: bloated HTML. Has anyone built a vscode extension that can toggle the style classes on/off?<p>Would also be cool to hover on a HTML block and see it highlighted in a browser hot-reload view.
I used to like web development some 15 years ago. Ever since frameworks became a thing, I stopped doing any web development. I simply couldn't get myself to setting up a bunch of tools just to process some byzantine file formats to a usable CSS. It was a really great feeling when I discovered Tailwind. Not only building custom, trimmed stylesheets required a single command, everything about using it just clicked. Kudos to people behind it!
1. Tailwind is awesome.<p>2. I hate the new website, sorry. The old one was clean, focused and clearly portrayed what TW does. The new one is IMHO big, loud, and a lot less focused.<p>3. I have had endless issues compiling with npm[1], and am using yarn just because of tailwind. Anyone else with this issue?<p>4. 30 minutes to upgrade is a lot when you manage thirty sites. Though if it is not worth it, no one is forcing me to upgrade.<p>5. There are some really awesome tools out there that complement tailwind, like tail-animista.vercel.app and tailwind.ink, and some collections like bestoftailwind.com.<p>6. tailwindui is really nice, and gives the best of both worlds compared to something like uikit.<p>Partly I feel that the creation of tailwindui took the wind out of the sails of sites like tailwindcomponents.com (of which there are quite a few) which is a shame, since a community can do more than even a dedicated team.<p>But partly I wish they would filter, organize and promote all the neat tools that there are on tailwindui.<p>[1]: <a href="https://github.com/tailwindlabs/tailwindcss/discussions/1891" rel="nofollow">https://github.com/tailwindlabs/tailwindcss/discussions/1891</a>
I'm quite interested in frontend technology and enjoy to take a look at announcements like these. But at the same time my knowledge about JavaScript is extremely limited. So just out of curiosity:<p>Why is the theme fontSize defined as<p><pre><code> xs: ['0.75rem', { lineHeight: '1rem' }]
</code></pre>
rather than something like<p><pre><code> xs: { size: '0.75rem', lineHeight: '1rem' }
?</code></pre>
Tailwind released 2.0, but it is a result of constant work releasing new versions gradually and listening to the users. This is a very active project and it is good to keep an eye on new things <a href="https://newreleases.io/npm/tailwindcss" rel="nofollow">https://newreleases.io/npm/tailwindcss</a>. Actually, 2.0.1 is out already. :)
For those using libraries / frameworks like React / Angular / Vue / Blazor / Etc. just try Tailwind. It's awesome and fits very well with component based UI systems.<p>You will have a slight learning curve, but I recommend you try to learn the classes, style your components <i>without looking at the docs</i> for a week or so, and believe me, your productivity will shoot up, and most importantly, you will start <i>thinking</i> in terms of <i>design, look & feel</i>, rather than how do I encapsulate this in css class.
> Extra wide 2XL breakpoint, for designing at 1536px and above<p>Is it still common for folks to use pixels in their CSS? I moved to em and the rest around 1999 (I think). What is the reason to stick to pixels?
Tailwind and utility-first in general is a major win in my book if for one thing only; I don’t have to think about naming my elements at the html level at the start.<p>Huge speed increase that gives me immediate results. You can absolutely spot and define those names, but you don’t have to think of them up front, allowing you to move forward more abstractly. Readability and maintainability <i>seem</i> like an inefficient nightmare but so far I have felt no pain or burden.<p>Hats off to the Tailwind team. This is the way.
For anyone who's interested, I put together a repos to bootstrap a react with typescript and tailwind project.<p>It's intentionally fairly barebones, but I've found it useful to get a wide variety of projects started quickly: <a href="https://github.com/figelwump/react-typescript-tailwind-bootstrap" rel="nofollow">https://github.com/figelwump/react-typescript-tailwind-boots...</a><p>I've come to love Tailwind, after a few failed attempts at using it. Recommend trying it!
These look like great improvements! I've been using Tailwind one a medium-large solo project and I can confidently say the whole project is MUCH better designed than it would have been without Tailwind, while still looking very custom.<p>Tailwind is not the one true way to do CSS, but it saves me from myself. I think of Tailwind vs Regular CSS how I think about TypeScript vs Regular JS. I <i>could</i> do everything and more in JS, but I'd make so many more mistakes along the way.
I've been using tailwind for a chess game (<a href="https://github.com/JMS55/chessmatch" rel="nofollow">https://github.com/JMS55/chessmatch</a>) and so far it's been really good, and the first time CSS has clicked for me. My only complaint is that the html templates can get kind of messy, but that can probably be solved with @apply or splitting the template into pieces.
Can anyone comment on the current state of React Bootstrap versus Tailwind?<p>There was a relatively recent React Round Up episode where people seemed unconvinced on tailwind: <a href="https://podcast.app/rru-react-tools-codebase-management-and-more-with-brice-ayres-e101838552/?utm_source=ios&utm_medium=share" rel="nofollow">https://podcast.app/rru-react-tools-codebase-management-and-...</a>
This isn't how you HTML, people! <a href="https://threadreaderapp.com/thread/1329156451416244224.html" rel="nofollow">https://threadreaderapp.com/thread/1329156451416244224.html</a><p>I don’t have too many programming hills to die on, but taking full advantage of the glory that is HTML5 is one of them. Tailwind is…the opposite of that!
I switched from tahyons to tailwinds like 3 years ago and been using it every since on all my React projects. I have tried all the CSS-in-JS stuff etc nothing compares to the dev speed with Tailwinds. Checkout <a href="https://42papers.com" rel="nofollow">https://42papers.com</a> it's all tailwinds and has a darkmode too.
I occasionally write HTML/CSS, and have always just grabbed Bootstrap, Pure, something. I've briefly looked at TailwindCSS a couple of times and always end up at: where are the some of the common, basic components? It seems like those are paid for items. Am I on the hook to be e.g. a button designer if I don't buy the bundle?
Incredible work by Adam and team. I'm using Tailwind from beginning and I have so used to it that I'm not even thinking to go back to whatever Bootstrap, Bulma, etc. It's such a joy to work with TW. Once you try to tinker around with Tailwind there is no back, trust me.
Probably the best invention i added to my tool belt for a long time.<p>Never was i able to move so quickly to style components in a way that works and you only have to learn one set of keywords. Reminds me a little bit of vim learn once apply everywhere :).<p>Props to the creators of tailwind !
Half-OT: Are there good UI toolkits out there based on Tailwind?<p>I read it is really flexible, but I don't want to start from zero. Most of the time I want to throw some pre-made UI components together and then sprinkel them with customizations when required.
CSS/Stylus framework inspired by Tailwind, trying to respect the content semantics <a href="https://github.com/holtwick/windy-css" rel="nofollow">https://github.com/holtwick/windy-css</a>
I really think writing component-scoped and BEM named CSS with Tailwind is the sweet spot here.<p>For example:<p><pre><code> .menu {
@apply w-full h-12 bg-gray-100 flex flex-row items-center;
&__icon{
@apply h-8 w-8 object-fit;
}
}</code></pre>
This is an awesome news. Thanks to the team at Tailwind.<p>I migrated a big-ish project to TailwindCSS about a year and a half. I like it for the fact that I can train juniors to be productive and part of the big project quickly while the experienced developers can graduate to using it as a utility for their styles.<p>For those worrying about not being able to work on the type scales, etc. I would suggest trying to use Tailwind as your utility and write your own SCSS.<p>Try this out for your Styles.<p>1. Includes Tailwind CSS.<p>2. Create separate components for repeatedly used set of Tailwind classes. See examples at <a href="https://github.com/valinorearth/valinor.earth/tree/master/src/css" rel="nofollow">https://github.com/valinorearth/valinor.earth/tree/master/sr...</a><p>This is our Startup's website built in the open. A bit overkill but was our attempt to do a multi-lingual Static Site with 11ty + Tailwind + AWS s3 + Cloudfront + Github Actions/CI and other interesting toolsets.<p>For instance,<p><pre><code> .button {
@apply inline-block py-2 px-4;
@apply no-underline bg-water-600 text-white;
@apply border border-water-600 rounded;
@apply transition duration-100 ease-in-out transform;
@apply leading-tight;
}
</code></pre>
For any number of team-size, I suggest maintaining design-tokens in the Tailwind Config. Of course, do post-process your styles with the likes of PostCSS — postcss-import, autoprefixer, etc.<p>For those asking for simpler CSS/Styles, I believe Tailwind might not be the right one for you. I don’t really write codes these days (quite a few years actually) but I tend to do a lot of marketing landing pages, brochures-types for prospective customers, and throw-away prototypes.<p>These days, I like the plethora of classless CSS available for me to choose from. I might have even created one for our internal use based off the NordTheme color palette (will try extending it with TailWind). Here are some of them for you to start off - <a href="https://github.com/dbohdan/classless-css" rel="nofollow">https://github.com/dbohdan/classless-css</a><p>I have come back full circle and now just write in plain CSS for the marketing pages. I was once a purist and started with tools such as Hotdog Professional, Ultradev as an IDE.<p>Tools such as Tailwind has their places and we are standardizing it for all of our websites, customer dashboard, admin, etc. Check out the Tailwind’s own TailwindUI at <a href="https://tailwindui.com" rel="nofollow">https://tailwindui.com</a>
For someone who really wants to learn CSS from scratch, is it a bad idea that I start learning CSS by using tailwind?<p>I am mostly a backend dev and trying to learn UI dev since I need it for some side projects.
Any great alternative to material-ui? It's going to be open core and will make us pay for "advanced enterprise features" like a date range picker.
Wow, the homepage for Tailwind has me excited to try this. I haven't seriously considered using a full on UI framework since early Bootstrap versions :)
Tailwind is great, my main issue when I used it was that I felt restricted by the limited set of sizes. I wish it was possible to use e.g. "m-7px".
Always have been a huge fan of Tailwind CSS just for the amount of passion that is clearly behind it. The whole utility-only approach is not for me - I prefer a middle ground with utilities and pre-built component classes. Although I am also building a CSS framework, I can only wish them the best of luck. This update looks freaking amazing!<p>Edit: Removed link to avoid self-promotion.
This is neat. I actually wrote my css similar to this 10 years ago, but was laughed at by "the smart devs". I'm glad to see I was right all along.<p>Don't let imposter syndrome get you kids, it's a hell of waste of time.