Watching Tailwind Tutorials Is A Waste Of Time

I love Tailwind. It is one of (if not) my favorite ways to style applications. I do have one issue with Tailwind, though, and that is how people go about learning it. In order to truly learn and master Tailwind you do not need to actually learn much at all about Tailwind. Instead you need to master CSS since Tailwind is really just CSS with some slightly different names and a few extra features.

📚 Materials/References:

🌎 Find Me Here:

⏱️ Timestamps:

00:00 - Introduction
00:24 - Best way to learn Tailwind
04:28 - How to learn advanced Tailwind

#TailwindCSS #WDS #CSS

[seananih]

Agree 100%. Used a tutorial to try and learn Tailwind a few months back and stopped after an hour. Tailwind Intellisense and the docs are all you need (Headwind is nice too).

[bakersentamu]

It took me awhile to learn tailwind because I thought needed to learn much stuff but when I dived into the docs, I was able to learn tailwind so fast while implementing it on a project. So, I agree. If you know CSS well then you know tailwind well.

[patricknelson]

It’s worth noting that, while it’s not bad to learn Tailwind first per se, it’s generally _best_ to ensure you still always learn the basics _regardless_ of if you also learn something like Tailwind first. I say this because, as a web developer of >20yrs, my CSS knowledge has only grown and has always been useful over time. But, over that same time, various frameworks have come in and out of style. That said, I’m sure Tailwind may stick around for awhile, it’s just general advice so take that as you will. 😅

[tiagocerqueira]

I 100% approve this advice. I learned pure CSS first and when I decided to jump to Tailwind it was as simple as searching in the docs the equivalent in CSS.

[Audiojack_]

The Tailwind documentation is fantastic. I learned a lot about both Tailwind and CSS just by reading it while using it. I never looked at any tutorial.

[Sahil.]

Heard this guy making a youtube video about master CSS not tailwind and boom now we have a tutorial

[ruskasielu]

Thank you!!! I've been thinking about getting started with Tailwind but the 4hours videos are pretty overwhelming and are sometimes not so useful when you're in a specific situation that's not introduced on the video.
The way you presented things made so much sense and it feels a lot more manageable to learn to work with Tailwind now, so you might have saved me many hours of work !

[Lurvas]

Oh, this was an ad for your ~12.3h 60$ css course, of course! But I get your point, and it's a fair one! Learn CSS first and you'll almost master tailwind by proxy. Good video explaining it!

[qwikdeveloper]

You can learn CSS through tailwind. It goes both ways.

[mohameded]

thank you for these info, I planned to learn Tailwind by taking a course, but after this video, it's so logical for me that just i need to learn how to install and the 5% you said

[wutrax]

I only learned about tailwind when I was having a look at nextjs and tailwind was integrated in the example project. I was somewhat shocked how easy it was to use with just some basic knowledge in css. Once you understand the basic structure (which doesn't require much more effort than just looking up a few things in the documentation), you can pretty much guess what classes you need.
The only part I'm having a bit of a struggle with is the typography-plugin, but I'm not sure, I may be using it wrong.
(Also, small side note: Don't try to use the documentation in Safari)

[codelery]

Really awesome! I think the reason why I find it difficult to watch those long tailwindcss tutorial is what you mentioned here. What people need to understand and spend a little more time is setting a design system for a project. Could you please do a video on that?

[theMiaow]

You are very correct. I started learning tailwind via Intellisense and the docs and, if you have good firm grasp on the css fundamentals, it literally is a waste of time to learn tailwind via tutorial resources.

[johnmichaelvicmudo]

Been planning to watch 4 hours course. Thanks for saving my time!

[bytoxx]

I literally learnt more in this video than other tutorials or guides showing how to use TailwindCSS. I know that's kinda the point, but wow, it really surprised me.

[kapa]

Before I use Tailwind, my CSS skill is basic. Now I'm advanced in CSS through Tailwind because there are bunch of CSS property that I learnt when I'm using it practically. Plus, for beginner it's easier to learn CSS through Tailwind than CSS itself, for example CSS grid, it will be overwhelming for beginner seeing CSS grid property and syntax, but with Tailwind it's as easy as "grid grid-cols-2 gap-4". Up until this point, I don't have any reason to leave Tailwind to vanilla CSS, because the time amount to code just in element class is much less than thinking about naming CSS semantic class name, then moving to CSS file, write a bunch of lines, and move it back, and so on. There is no limitation in Tailwind since you can just use arbitrary value and even arbitrary property, and you can just extend with vanilla CSS and use Sass if you want. Using Tailwind has no cons at all, change my mind.

[constantinci]

Great job. There are only a few, who has a courage to state that "King is naked". Bravo.

[michielarkema]

This is so true Kyle. I personally prefer bootstrap and apply custom styling afterward to make a unique design but the same rules apply.

[md.alamgir]

I found the same. We need good command on CSS first, then tailwind will be very easy. I also agree that we don't need to spend much time watching tutorials, what we need is giving a try immediately. To start initially it needs only to check very few documentations, as shown in this video. In fact, Tailwind is not that much complicated for them who knows CSS well.

[damilolaoni]

I was watching a video on tailwind CSS and felt like I was wasting my time, then I saw ur video in the recommendation. I couldn't agree more.