I had been procrastinating learning tailwind for so long. Never thought I’d learn it in 12 mins on a random wednesday at 2am lol. Great content

Okay so I'm convinced this guy collab with fbi to provide us content we often searching for

I almost gave up finding a Short and Neat Tailwind CSS tutorial but Here it is. Thanks Universe

The purge mode is essential for this video, since you specified JIT mode. Without a purge config, your resulting CSS will be empty (or really just the normalization). Your styles would be purged. The remark is valid though if you use AOT mode. (JIT => Use purge config to only include the styles needed; AOT => Build ALL classes and remove those that are unused)

Your tutorials are something special as I am able to follow them and learn while I am in my lunch break without my computer

Tbh Fireship, I love your videos so much I watch them as a C && C++ Dev. I have no use for these, but they're just wonderfull to look at.

There are so many tutorials and guides out there for everything you can imagine, but your videos are by far the most efficient in conveying useful information per time of them all. Big kudos to you, keep it up, thanks!

Hope this channel gets big. I learnt a lot in the last 2-3 years. I really love videos about new technologies and how to use them. Keeps me connected.

I really just started learning about TailWindCss and this is the best thing I've ever experienced. FrontEnd used to be so hard for me because I couldnt put what I had in my head, into code with CSS, but with this, its so easy. For some reason, bootstrap never made sense to me, but this does - thank you!

Yo! I started learning tailwind css yesterday. 100% accurate video.

Really grateful for your channel in general. I've learned so much over the past few weeks watching videos from you. You're a seriously great teacher.

Thanks to this tutorial I tried implementing tailwind in my Svelte project and fell in love with it, thank you very much!

Great video, clear and concise! Been meaning to look into Tailwind for awhile now Looks interesting, but I'm not quite sold yet. The biggest issue for me is how it muddies up your HTML/JSX. It's also yet another layer of abstraction to learn and another link in your toolchain that can break. The benefits over plain old CSS or styled components don't seem worth it personally, but I'll have to try it for myself before judging.

This one was super interesting and useful. Even so I love crafting with CSS, when it comes to production level, my experience suddenly becomes a slow agony. Most popular solutions were not for me (to name a few: Material, Bootstrap, CSS in HOCs, ...), so I left with SASS/BEM. Despite the growing popularity of Tailwind, I couldn't find time to look at its side, but after another tutorial about it FROM YOURS, now I have changed my mind and will try it on my next project as well ( I guess it will be definitely worth it ). Apart from that, I want you to accept my gratitude for all things you are doing in this channel. In addition to helping those who are interested in learning to go with web development carrier (at the moment the most popular and demanded one... or not), you also promote the industry itself forward by popularizing little-known projects and most importantly sharing your opinion and experience with community. So yeah, like and subscribe is unambiguous and mandatory!

Jeff your videos are so amazing you condense and explain things so well!

You make things super simple and understandable. I love it. More content please.

this is personally the one I most awaited for ❤️. less gooo 🔥🚢

The pace, information, and flow of this entire video is on point! I learned more in this video that feels like "the right way" than I have on many other videos.

your videos are the best, the quality, the tutorial, the design... everything is so perfect with you

Even though I’ve been using Tailwind for some time, I still decided to wach this, and I’ve learned about the group utility! Thanks!

For someone (me) thats neglected their CSS skills for the last 10 years, relearning via trailwind + this tutorial is literally everything I wanted. It removes all the reasons I hated doing CSS in the first place. Great work

Been a frontend dev for almost 10 years. I was there when float was still the standard and i still haven't sold on Tailwind. It's probably good for smaller projects that require fast and minimal setup, but on enterprise level seems like convoluted and would be hell to maintain, especially when you need to reference the element for DOM manipulation in JS. Call me old-fashioned but i love clean minimal html with relatively go readability.

By far one of the best coding channels I've come across, if not the best for consistent quality uploads!

Thank you so much for explaining Tailwind CSS in such a simple and beautiful way.

I am starting to use tailwind tomorrow on a project, And here you got me a tutorial thanks fireship

Yeah so, yet again, you're providing the tutorial the week I need it.. Love it!

I've been working with Tailwind for the past year and I don't want to work differently any more. I kept nudging my friends to also use it, but most of them were not ready to make a switch. Thanks for this video, I will forward this to them and hope that this will tip the scales. :)

Previously i though that custom css is the best way to write css but Tailwind is really awesome 🔥🔥🔥 thank you so much ! Awesome content 🤘

Great video as always. Concerning dark mode by default its only enabled for color-related classes. So for instance if you wanted use display to hide an image in dark mode you would have to extend it in the config under variants, extend. Then add the class you are extending such as display:['dark']. Then you could do something like dark:hidden on the image to hide it in dark mode. You can extend any utility to be able to trigger changes on dark mode by extending it via the config.

This just feels like writing css in the form of class names. I actually really like CSS. Modern CSS can do so much, and combine that with a preprocessor like SCSS and you have unlimited power.

Dude you did this for me haha I was literally looking for this right now. Not at all expecting the fireship channel cuz I knew you had nothing yet... damn great timing

Man your channel has taken a place in my heart love you guys ❤

Seriously, JavaScript Mastery and Fireship are the only 2 channels that really makes coding look very cool and interesting. Keep up the good work man!

I love the speed at which you present. It’s fast enough that I don’t need to speed up the video. But I wouldn’t want to watch without my morning coffee or I might not keep up. 😆

I was waiting for this for so long. Thank you so much. ♥🔥🔥🔥🔥🔥

For those having issue following 9:32 and getting an error at hover:rounded-xl, you'll have to add this piece of code in your tailwind.config.js: variants: { extend: { borderRadius: ['hover'], }, },

Actually there are tailwind libraries such as Daisy ui which has a bunch of components. Rly like that library ✨

There is only a few people that: 1. understand a topic, 2. are good in explaining and 3. make a video and even explain it!. Brilliant!

These tutorials are amazing. I can watch a 10 hour video loop of this.

This coming in while I'm struggling with semantic UI is heavenly. Sadly, I am too far gone.

Seems a lot like adding styles directly to the styles attribute? Does this not go against keeping the structure seperate from the styling? Does the power come in with custom components?

at first I sceptical on tailwind, but with your video which almost a year ago, now I know I need this lib

best tailwind vid iv seen so for thanks for explaining the classes as you go.

I think tailwind def has its advantages (specially regarding perf), although readability is not that great and creating custom classes to group different utility classes work, but it is not optimal. I like my css to be where the mark is and not in other file. I am huge fan of styled components (from an ergonomics stand point - readability and working with props, etc) it is better than tailwind but it looses on perf since it requires some runtime work, as well as it takes more from you since you don't habe anything ready out of the box. I think in the near future we will be seeing something hybrid, i.e. performant, scalable and quick to get started (like tailwind) and ergonomic and readable like styles components. They are both good approaches but they have some weakness. Nice video!

Honestly after being a react dev who uses Tailwind, and then switching to Vue. My man, Vite and tailwind setup is just like moving your fingers. Here you don't have to use Craco, like in react

Your tutorials have really help me get into code, thank you !

DAMN! all the tailwind essentials packed in 12minutes !!!! you rock bro

Oh my gosh, THE COINCIDENCE! I was quite recently repeatedly clicking the Discord navbar with great fascination and thinking about replicating it myself since it's just so cool, what with the circle to squircle icons and sliding server folders.

I'm still not sold on the class name bundle, dog. Craco seems cool though, but I usually avoid create-react-app The grouping system also seems rather inelegant

Wow, amazing video, my team started to use it and I wanted to know how it works and why it's so useful, thanks a lot for this tutorial! 😁💯

Fireship at it again. Thnx for this great video about tailwind. I was sceptical at first whether to use it or not seeing that it has a lot of similarities to bootstrap. But this video introduced new things about tailwind I didn't know before. Now I finally using tailwind.

Thank you for tutorial! :) To be honest, looks like a hard way to write inline css with all of it's downsides and almost no pros.

I wish there was a vscode extension that could hide the tw classes and expand on click

Thank you for the great video Fireship! Really needed this.

Jeff, you are the tailwind of tutors. Your work is masterpiece.

Love the video; just curious why you used 'rounded-3xl' instead of 'rounded-full' to ensure that you'd get circles at any size/scale?

One of the best programming channels on KZfaq!

Didn't know we could build a part of Discord in a few minutes. Love you so much !!.🥰

IMO Tailwind is great for prototyping, fine for small projects but I can't imagine using it in something bigger with such tight coupling of markup and styles.

It's not learning as such it's memorising the various CSS classes. I've used it for a few projects but I prefer writing my own CSS.

Amazing video as always. Totally agree, tailwind is the fastest for custom styling. For standard, I would use a component library, like material-ui (with emotion) since it has already a lot of functionality attached. For simple projects, bulma is very nice as well.

Just the video I was looking for. Thanks 😁

I've never been a fan of Tailwind, it has far too many drawbacks in my opinion. It's a great way to write incredibly verbose and unmaintainable syntax in your markup, with no clear separation of markup and styling as it's all slammed together in one hot mess. What you're "saving" in CSS, really just gets added back into your HTML. As a good front-end developer, you should be able to create any Tailwind (or any other library) component from scratch. I'm actually far more efficient writing plain CSS/CSS-in-JS against any design requirement, than using any component or UI library as I find myself spending more time reading through their documentation trying to figure out how to do something basic such as changing a color rather than implementing it myself. And instead of learning CSS which is your bread and butter for making things look nice on the internet, you'll be spending more time learning all these Tailwind specific classnames, which is a non-transferable skill-set when the hype train for this is over. Nevertheless, great tutorial, and I'm sure Tailwind has it's use case (solo developer/small project/quick mocks/design inspiration) but in terms of working with a team at enterprise scale it's a pass for me.

Using the @apply directive in Tailwind seems like an anti-pattern to me, especially with React where the functional component itself already abstracts away most of the complexity. Might as well write normal CSS at that point.

This was a good tutorial. Showing different approaches to using tailwind. I liked it.

video quality is next level, superb as always

Question for some senior dev: Isn't this basically just giving the powers of css to the html 'style' attribute? Like, in the case: ``` hello ``` Here, styling is done using the style attribute, instead of class defined css styling. I imagine for tailwind, the styling attribute would be replaced by something like: ``` hello ``` Although this also gives powers exclusive to css: ``` hello ``` Is my comparison valid? Is this a return to heavy use of the html styling attribute, but in a more powerful and cleaner form? I have ~1y full stack web dev experience.

great content! thanks, by the way, is Tailwind CSS suitable for a medium to big size project?

Excellent video, love the way you cover topics!

explained so nicely in short and sweet manner thanks you sir :)

I use tailwind with vite and svelte or react just because together they seems a stack like JAMStack.

Don't be offended and I have not yet worked with tailwind but is tailwind not almost like the HTML style attribute? Sure, you can slightly group multiple single style definitions in a class but you "bloat" you class attribute instead of your style one. You basically move half the style definitions into your HTML when you could have them all in your CSS file with selectors. (Other than that, great video.)

Wow! Thank you for this. The productivity tips like apply were super helpful!

You are the person who finally convinced me to give Tailwind a try :P Great job with this video :)

0:57 that couple pixels left align box throws me off balance

came with speed of light but due to network acting as medium light got diffracted

Your awesome you somehow manage to make all your videos interesting for me please don't ever stop uploading

tailwind is one of those exceptional things which are just done right which makes them stand out and super good

Honest to god, i still think that using standard CSS (or even SASS) with a decent internally standardized set of css vars is more than enough and tailwind is just a more complex bootstrap++. It makes styles not standard for a css dev and html more polluted than ever. Good tutorial tho

The thing I dislike about Tailwind and other similar tools is that it makes it harder for the end user to overwrite and customize css for specific elements. I learned css in the first place because I have astigmatism that makes it very hard to read dark theme sites, and I'm also extremely nearsighted, meaning the font size on most sites is not good for me. Zooming in isn't an option either because I don't need the UI bigger, I just need body text bigger. But sometimes there's elements with like a billion different classes and I don't want to change everything on the page to have a font size of, say, 20 instead of 16, or whatever. I just want to change the main text. But sometimes (not always, but I've seen it quite often) there's not even any semantic named classes at all. Nothing to identify element A from element B in a completely different part of the site, serving a completely different purpose. So I can't just change element A without affecting element B, unless I use extremely roundabout selectors like body>.container>div:nth-of-type(2)>div or whatever. I've had to do this because of lack of semantic classes. Semantic classes don't *only* help developers but they also help the end user in accessibility. In your demo code, you have which leaves me with no real way to target this element and this element alone. I do understand this is just a demo, but again I've seen this kind of thing in production sites. I would really love to see if there's a way to, for example, write the code like this, but have it compile down somehow into css within a class for that given element that those helper classes get applied to. I do like the @apply feature a lot and I think that's a great way to use it because it leaves a semantic class. But I really just can't get behind using those classes outright in the html (or jsx or whatever). But for now, while tailwind and similar stuff seems to make life easier for devs, it makes it harder on the technically minded end-users who have accessibility needs, and are just trying to do what they can to access content. I don't need larger sidebar text but I do need larger body text. Sometimes both are the same element with shared helper font size classes... And I can't do anything to adjust this for myself, locking me out of viewing so much content on the web. I really wish there was a better solution, but for now I think there's not (at least that I know of)... If there is a way to have the best of both worlds (easy source code but semantic production code) that would be great and I'd love to know about it. But until then I can't really say I like this, because it makes my everyday browsing of the web just a worse experience, sadly. If only developers at least added a semantic class to things in addition to these helper classes, there wouldn't even be any issue. But a lot of times (like in your demo code) there sadly isn't even *any* semantic class names on that element.

Wasn’t aware of @layer @apply trick. Okay Tailwind is a killer. Best channel for dev.

I was thinking of learning tailwind css and then i saw your video. Youre a ninja

Might be useful for some backend only developers I know who don't know anything about CSS but still get tasks that require some design related stuff. But I prefer the normal way. And if you're experienced front end developer you'd optimize the css.

Do you recommend putting huge classes in a smaller class by using @apply or keep the code small by splitting the code base into multiple components? Thanks for your videos btw, love them!

Sounds great for generating utility classes on the fly. Sounds insane to use this by itself.

I'm having an issue while creating the custom CSS class. It's saying The `hover:rounded-xl` class does not exist. Except my hover class for the text-white and bg green are working completely fine. What is up with that?

Tailwind + IntelliSence is the holy grail for frontend styling

wow tailwind handling the formating at the div class in a cleaner manner is like going back to html2 and using style

Okay you got me - I'm a believer in this library now

so this is basically CSS but you save 2 keystrokes

Is it just me or is anyone else not able to even get past installing dependencies because they conflict so much?

what a superb tutorial. extremely well done.

such a wonderful and clean tutorial...Thank a ton sir.

Everytime i see a tutorial or some kind of recommendatios for css frameworks, i dont find any reason why i should wrap my brain around a system that uses 2000 classes for a process, that maybe takes longer in vanilla, but isnt as appealing as creating my own Project and give my code a structure that i have my own personal control over. I mean, thats why i learned CSS for, or am i wrong? Am i the only one who gets a headache when i try to learn anything about hundrets of those js libraries, css frameworks, cms systems or a sea of code editors you have to study thousands of Pages of Documentations first for every single one of them to know how to even start coding…. Maybe im to old for this, idk…

😕 div soup + class soup = impossible to debug

awesome content. Great work Fireship

The "red button" part was funny :)🤣 Thanks for your awesome tuts

I’m still incredibly turned off by the class name soup. I’d imagine it would become quickly difficult to maintain and conflicts in styling will be obfuscated pretty easily making for a frustrating debugging experience. I see tailwind as a tool for a POC with a short planned lifespan. I don’t see how it can work in a larger app with a long term planned life

I'm giving you thumbs up because you're an excellent content creator, but I still despise the utility class approach to CSS. I'm OK with the idea of using utility classes/mixins with preprocessors, but leaving the HTML out of it. Depending on others' idea of a style language (utility classes, CSS-in-JS) is to deprive oneself of the richness of real CSS for actually nothing that a little discipline and a good naming scheme can't already accomplish.

Wow, this makes sense to me, even if I'm a noob. Thanks Fireship.