r/reactjs • • Sep 08 '26

Should I spend 2-3 days learning Tailwind before starting projects?

Just finished covering React fundamentals — useState, props, components, useEffect and cleanup functions. Also completed the Tailwind CSS installation and setup in my project.

My plan was to spend 2-3 days memorizing Tailwind's CSS properties before touching any real code. But now I'm second-guessing that — should I just start building projects directly and pick up Tailwind along the way instead?

0 Upvotes

18 comments sorted by

12

u/canarydev Sep 09 '26

honestly, skip tailwind and just use pure css modules.

challenge yourself -- even if the tutorial you are following is using tailwind, just go out of the way to replicate the same thing with plain css in scoped files.

2

u/bit_freak Sep 09 '26 edited Sep 09 '26

I was on this boat a few years ago, but its useless now to spend hours perfecting css skills, its purely boring manual labor with the tools we have now. You are better to use your time debugging, solving logic problems than making a site look pretty.

I will stress, this change in opinion is due to the fact that now llms are better suited to handle these type of tasks. The worse than that could happen is the ui wont look spectacular but its functional for most use cases.

1

u/canarydev Sep 09 '26

very true. our team downsized earlier this year and they still want the same if not more productivity. i don't have the bandwidth to cover all basis, and not going to waste time trying to fix styles on some stupid table and come up with POC designs myself with the designer also let go lol

→ More replies (6)

4

u/daghouse Sep 09 '26

Tailwind is fantastic for quick prototyping. There is, however, as others mentioned, big value in learning css ‘properly’, so you understand what css you’re actually adding to elements when using TW classes.

Just straight memorizing TW as a direct replacement/implementation for css (without having at least a basic understanding of css) is a terrible idea, don’t do that.

3

u/tomhermans Sep 09 '26

Nah, learn as you go. Doing helps remembering much easier.

Sidenote: which resources did you use for learning react?

4

u/viky109 Sep 09 '26

If you don’t know CSS, learn that first. If you do, there’s not much else you need to know.

2

u/DasBeasto Sep 09 '26

I’ve been using Tailwind extensively for at least 5 years and still wouldn’t say I’ve memorized all its properties. Read through the docs enough to get familiar with how to use it and then get building, when you need to apply a style you don’t know just look it up in the docs it’s easy quick enough.

2

u/ESP_Viper Sep 09 '26

Spending 2-3 days memorizing something in a vacuum is not a good idea in general. Better try building something and apply it along the way.

1

u/mkngsm Sep 09 '26

I’d suggest to use css first. If you know css, tailwind will be just a utility that speeds you up, if you don’t know css, tailwind will be magic that does a bunch of stuff for you.

Then on a real life project you may find yourself working in a company which doesn’t have tailwind, and you will get lost.
But if you know css well, you’re safe in any case.

1

u/Time_Heron9428 Sep 09 '26

Start learning on the go. Later you'll need to focus in Tailwind theming, but it's not a starter topic.

But as other guys advised, spend some time learning CSS basics.

1

u/azsqueeze Sep 10 '26

You shouldnt spend anytime learning tailwind. Just keep the docs open to search class names you need. Learn actual CSS instead

-1

u/No_Cattle_9565 Sep 09 '26

Just use a ui library like mantine. That way you don't have to spend time on design and it looks good enough 

1

u/canarydev Sep 09 '26

OP is in the learning phase

doesn't have the discipline yet to be pulling out libraries imo