*ATTENTION:* In the "Delegate" chapter, I mistakenly mentioned that the classes of the parent elements are inherited by the child elements. That’s not accurate! What I meant to say is that the some styles applied by those classes are inherited, not the classes themselves. Apologies for the confusion! What are your thoughts on this video? Like this comment if you want to see more videos about Tailwind CSS or let me know in the comments, what kind of content you want to see next on this channel.
Nice! I'm just starting to be familiar with tailwind. As an old school css user, I was a little bit reluctante to use any css framework since I was used to use sass on BEM architecture. But now by developing some apps with React I didn't found sass as useful as used to be. Tailwind is so easy to use I didn't even need to learn it is so intuitive specially if you already master css. However tips like this are gold, thank you!
Thanks for your feedback and for sharing a bit of your backstory, David! I really appreciate it. I completely agree - Tailwind’s intuitive nature truly shines when you already have a strong CSS foundation. I’m so glad you found the tips helpful. Best of luck with your projects! 😉
At 1:14, in fact classes are not inherited by child elements , its happening because some css styles like "color" are inherited by design, and some are not, so maybe this was what you meant but it could be misunderstood.
You're absolutely right! Thanks for pointing that out - that’s exactly what I meant to convey. Another viewer mentioned it as well, and while I can't update the video, I think adding this information to my pinned comment is a great idea. 😉
I’m just at the beginning of the video. But quick note: not the css classes are inheriting but the specific css rules. And not all of them! For example “color” (the css rule behind text-red-500) does. This isn’t a tailwind specific thing rather a CSS specific thing.
You're absolutely right, Richárd! Thanks for pointing that out - that’s exactly what I meant to convey. 😉 At 2:39 in the video, I clarify that this isn’t a Tailwind-specific behavior and also mention that it can't be used for everything. Hope that was understandable?
One advantage of class is that we can reuse it instead of editing all h1 tag one by one, and it is best practice to implement to make ur code clean and will be easier to maintain if we have define class And, h1 style will also override the stylesheet so need to be carefull
@@SamarthaRawal-j9z in this case, if you have two tags then you need to write className='text-[84px]" twice (in each tag) - so you actually cant reuse it. Second: if you use className='text-[84px]" you actally want to override stylesheet - so where is the point of not use "style" directly?
@@gbkEmilgbkbecause he chose to use the framework, both are the same but one is in css format and the other is in tailwind. If you choose to use tailwind stick to it, mix only when necessary.
Sorry but nothing crazy here. For example on the last example, you can just give a text color on the button and use hover: instead of peer and group. No need to overcomplicate things.
Thank you for your feedback, Oğulcan! I have to agree - in hindsight, these examples may not have been the best choice to highlight the advantages of the peer and group utilities. I’ll make sure to include clearer and more impactful examples in future videos. Your input helps me grow, so I really appreciate it! 😉
I'm sorry the video didn't meet your expectations! It seems like you're already well-versed in Tailwind CSS, which is quiet impressive. I appreciate your feedback and will work on sharing more advanced content in the future as well. 😉
@lukas.webdev likely the cringe begging for likes and subs, specifically the tailwind site nonsense. Just casually ask somewhere in the video, you don't gotta be weird about it...
@@_jovian Got it - thanks for pointing that out. I didn’t give it much thought at the time, but I understand now and won’t do it again. Sorry about that!
@@fatema8eee I understand why you feel that way, and I appreciate you sharing your thoughts. I’ve already taken your feedback into account and won’t approach it the same way in the future. My goal is to create value, not to annoy anyone!
![BLACK BAG - Official Trailer [HD] - Only in Theaters March 14](http://i.ytimg.com/vi/Du0Xp8WX_7I/mqdefault.jpg)
*ATTENTION:* In the "Delegate" chapter, I mistakenly mentioned that the classes of the parent elements are inherited by the child elements. That’s not accurate! What I meant to say is that the some styles applied by those classes are inherited, not the classes themselves. Apologies for the confusion!
What are your thoughts on this video?
Like this comment if you want to see more videos about Tailwind CSS or let me know in the comments, what kind of content you want to see next on this channel.
I have been using tailwind for almost 2 years now and this group thing is what I learned here thank you Lukas
I'm glad I could help and I really appreciate your feedback! 😉
Nice! I'm just starting to be familiar with tailwind. As an old school css user, I was a little bit reluctante to use any css framework since I was used to use sass on BEM architecture. But now by developing some apps with React I didn't found sass as useful as used to be. Tailwind is so easy to use I didn't even need to learn it is so intuitive specially if you already master css. However tips like this are gold, thank you!
Thanks for your feedback and for sharing a bit of your backstory, David! I really appreciate it.
I completely agree - Tailwind’s intuitive nature truly shines when you already have a strong CSS foundation. I’m so glad you found the tips helpful. Best of luck with your projects! 😉
At 1:14, in fact classes are not inherited by child elements , its happening because some css styles like "color" are inherited by design, and some are not, so maybe this was what you meant but it could be misunderstood.
You're absolutely right! Thanks for pointing that out - that’s exactly what I meant to convey. Another viewer mentioned it as well, and while I can't update the video, I think adding this information to my pinned comment is a great idea. 😉
@@lukas.webdev Oh i just saw @nemethricsi's comment =), yeah pinning comment will do, best of luck
@@komeiltaheri Thanks, I really appreciate it! :)
I’m just at the beginning of the video. But quick note: not the css classes are inheriting but the specific css rules. And not all of them! For example “color” (the css rule behind text-red-500) does.
This isn’t a tailwind specific thing rather a CSS specific thing.
You're absolutely right, Richárd! Thanks for pointing that out - that’s exactly what I meant to convey. 😉
At 2:39 in the video, I clarify that this isn’t a Tailwind-specific behavior and also mention that it can't be used for everything. Hope that was understandable?
@@lukas.webdev Right I've heard that so I should have listened further :)
sorry for asking but... eg. in 9:59 what is the difference bietween
One advantage of class is that we can reuse it instead of editing all h1 tag one by one, and it is best practice to implement to make ur code clean and will be easier to maintain if we have define class
And, h1 style will also override the stylesheet so need to be carefull
@@SamarthaRawal-j9z in this case, if you have two tags then you need to write className='text-[84px]" twice (in each tag) - so you actually cant reuse it. Second: if you use className='text-[84px]" you actally want to override stylesheet - so where is the point of not use "style" directly?
@@gbkEmilgbk why u are using normal css use tailwind both are same.
@@gbkEmilgbkbecause he chose to use the framework, both are the same but one is in css format and the other is in tailwind. If you choose to use tailwind stick to it, mix only when necessary.
@@IgorPcar both are not the same - because tailwind is additional (redundand?) layer of abstraction(?) over CSS
Sorry but nothing crazy here. For example on the last example, you can just give a text color on the button and use hover: instead of peer and group. No need to overcomplicate things.
Thank you for your feedback, Oğulcan! I have to agree - in hindsight, these examples may not have been the best choice to highlight the advantages of the peer and group utilities. I’ll make sure to include clearer and more impactful examples in future videos. Your input helps me grow, so I really appreciate it! 😉
these are the most basic tailwind tips. I was looking for something better.
True. it just pro for him
I'm sorry the video didn't meet your expectations! It seems like you're already well-versed in Tailwind CSS, which is quiet impressive.
I appreciate your feedback and will work on sharing more advanced content in the future as well. 😉
"Don't use tailwind, like a pro"
Interesting take! 😄
Child/Children
Dislike for lie
I'm sorry if something came across as misleading. Could you clarify what you mean exactly?
@lukas.webdev likely the cringe begging for likes and subs, specifically the tailwind site nonsense. Just casually ask somewhere in the video, you don't gotta be weird about it...
@@_jovian We should dislike and report the video. Unsubscribe also if subscribed.
@@_jovian Got it - thanks for pointing that out. I didn’t give it much thought at the time, but I understand now and won’t do it again. Sorry about that!
@@fatema8eee I understand why you feel that way, and I appreciate you sharing your thoughts. I’ve already taken your feedback into account and won’t approach it the same way in the future. My goal is to create value, not to annoy anyone!