Instead of 'justify-center' and 'items-center' you can use `place-items-center` which combines those two classes. Same with 'w-10 h-10' you can use 'size-10' to combine them too.
I recently found about the "group" class and oh man your video refreshed the concept. Now, it's printed in my brain. Loved to learn and refresh knowledge about other concepts. Thanks a lot Smol
Breakpoint tips: in addition to the regular default breakpoints that work as a min-width, you can prefix them with max- to negate them. For example, the following two styles do the same thing: flex flex-col md:flex-row flex max-md:flex-col (flex-row is the default so no need to specify it) Arbitrary custom breakpoints: regular min-width breakpoints are written like this min-[123px]: And max width is self explanatory max:[987px]: Though sometimes it's better to add custom breakpoints to the Tailwind theme config
I was afraid to use tailwind because I was so used to scss and now I cannot look back! This refresh video is amazing and the simple concepts of it are nice! Thank you
Man, I really wish that Tailwind pseudo classes and pseudo elements had an option to group all of its classes without typing the selector every time, kind of like this before:[absolute bg-green-300 w-full] Or md:[grid-cols-3 text-lg] instead of the current before:absolute before:bg-green-300 before:w-full Or md:grid-cols-3 md:text-lg Great video!!!!!
Nice to know about the group stuff! What I'm missing here is the @apply, which you can use, to keep everything not inline and wrap it in a class that you can reuse
the creator of tailwind admitted to regret the @apply feature..saying it is the most feature breaking and difficult to debug/maintain for them. also, if you think about it, @apply kinda defies the whole purpose of inline styling of tailwind (it's almost like using plain css with class selection). but hey, maybe there are thing you can do only with @apply, i just don't know what are those cases
@@kiryls1207 the purpose of tailwind is to write everything inline? It looks horrible that way, mostly unreadable. The reason why I want to use @apply is to replace it with normal scss later
@@ralify i guess it depends on what makes you more productive. for instance, i don't like to switch constantly from one place to another every time i need to make some adjustment. i also like to have my style near the element it refers to, so whenever i get some design bug, i just need to find the element that's causing it, instead of playing with a centralized mega class containing all the styles of the application. there are clearly pros and cons (code looking kinda cluttered sometimes for example) the method i described was something i really enjoyed doing, where other approaches failed to me by being frustrating most of the times (i guess i'm just a noob, so don't hate me for that ahah)
@@ralify I get the sentiment but it's not that bad if you follow the recommended strategies: use the official IDE plugin to automatically sort your classes so they become predictable, break up your project into components, separate styles into variables or objects, place the styles on the elements that actually need them, and use multiple lines to for the classes. I've been using it for over a year now across various projects and it's rarely a problem.
You can create a loader with much less code, just border-transparent, back with border-top, border-left, rounded 50% and animate:spin. And it will be transparent in the middle too.
Good question. It's because you're constructing a string with tailwind classes and classes must always be separated by a space otherwise they don't work
does not using all these inline css (tailwind) makes things more complicated and difficult to maintain and read. I prefer using tailwind css and simple css both, tailwind for small things and responsiveness and plane css for complicated design and animation.
Instead of 'justify-center' and 'items-center' you can use `place-items-center` which combines those two classes.
Same with 'w-10 h-10' you can use 'size-10' to combine them too.
Nice, thanks
Honestly I learn more from comments then these videos. Thanks for sharing those
Thanks, new to me too
I recently found about the "group" class and oh man your video refreshed the concept. Now, it's printed in my brain. Loved to learn and refresh knowledge about other concepts.
Thanks a lot Smol
Glad you found the video helpful :) thanks for the comment
you're actually goated for this. one of the most helpful tailwind videos out there, i'm not even kidding.
Glad you found it useful my friend :)
watching this 15 mins before an interview, its a good refresher video, thanks!
Good luck with the interview! Glad you enjoyed the video :)
I think it's better to use twMerge() from tailwind merge for dynamic/conditional classes instead of using template strings.
Breakpoint tips: in addition to the regular default breakpoints that work as a min-width, you can prefix them with max- to negate them.
For example, the following two styles do the same thing:
flex flex-col md:flex-row
flex max-md:flex-col
(flex-row is the default so no need to specify it)
Arbitrary custom breakpoints: regular min-width breakpoints are written like this
min-[123px]:
And max width is self explanatory
max:[987px]:
Though sometimes it's better to add custom breakpoints to the Tailwind theme config
group hover blows my mind 🤯, thank you
I was afraid to use tailwind because I was so used to scss and now I cannot look back! This refresh video is amazing and the simple concepts of it are nice! Thank you
Loved the format of this video! Keep these coming. You got a new subscriber!
cheers bro - appreciate the support!
Awesome ! Sir, you just cleared our doubts. Thank you very much sir 🎉
Man, I really wish that Tailwind pseudo classes and pseudo elements had an option to group all of its classes without typing the selector every time, kind of like this
before:[absolute bg-green-300 w-full]
Or
md:[grid-cols-3 text-lg]
instead of the current
before:absolute before:bg-green-300 before:w-full
Or
md:grid-cols-3 md:text-lg
Great video!!!!!
Its is so muxh more complex to implement, and more complex for vs code extension. Everything should be more simple not more complicated
Incredible tutorial! Thank you and keep it up :)
You're very welcome!
Bro, You are pro 🎉🎉🎉
Neat, never heard of the animate functions before
best tuto in chill mode ;)
what about if we want to trigger a something dynamic on hover: ....
That's a very useful video. Thanks!
Nice to know about the group stuff! What I'm missing here is the @apply, which you can use, to keep everything not inline and wrap it in a class that you can reuse
It definitely is missing - so thanks for mentioning it! :)
the creator of tailwind admitted to regret the @apply feature..saying it is the most feature breaking and difficult to debug/maintain for them. also, if you think about it, @apply kinda defies the whole purpose of inline styling of tailwind (it's almost like using plain css with class selection).
but hey, maybe there are thing you can do only with @apply, i just don't know what are those cases
@@kiryls1207 the purpose of tailwind is to write everything inline? It looks horrible that way, mostly unreadable. The reason why I want to use @apply is to replace it with normal scss later
@@ralify i guess it depends on what makes you more productive. for instance, i don't like to switch constantly from one place to another every time i need to make some adjustment. i also like to have my style near the element it refers to, so whenever i get some design bug, i just need to find the element that's causing it, instead of playing with a centralized mega class containing all the styles of the application. there are clearly pros and cons (code looking kinda cluttered sometimes for example)
the method i described was something i really enjoyed doing, where other approaches failed to me by being frustrating most of the times (i guess i'm just a noob, so don't hate me for that ahah)
@@ralify I get the sentiment but it's not that bad if you follow the recommended strategies: use the official IDE plugin to automatically sort your classes so they become predictable, break up your project into components, separate styles into variables or objects, place the styles on the elements that actually need them, and use multiple lines to for the classes. I've been using it for over a year now across various projects and it's rarely a problem.
Excellent video - cheers 👍
Glad you found it useful!
Awesome content! Keep it going! 🎉
By the way, which is the VS Code theme you're using?
Thanks for the comment :) As for the theme, it's the freeCodeCamp theme
awesome video thanks a lot🔥
Love the thumb nail !
Thanks, very informative
Really useful. Great keep going!
what mic do you use? The lighing looks firee!
haha thanks - it's a FiFine apligame I think!
Some great advanced TailwindCSS techniques, beautifully demonstrated. Thanks.
{2024--05-19} - Subscribed!
You can create a loader with much less code, just border-transparent, back with border-top, border-left, rounded 50% and animate:spin. And it will be transparent in the middle too.
before and after is not working in my tailwind can you help , bro ?
If you post your code in the discord channel I can take a look!
thank you, very good tut
Glad you found it useful :)
Omg G. Thank you so much
thanks a bunch man
thx for sharing, learned a lot, a quick question, why space for dynamic inputs?
Good question. It's because you're constructing a string with tailwind classes and classes must always be separated by a space otherwise they don't work
@@Smoljames got it, thx!
Thank you that's useful
More than welcome!
you missing something very basic. tailwind extension that suggested classname 😊
This is tailwind basics my guy
Helpful video. However, if you can, try to improve on the video quality
sure - just curious, what do you mean by improve on video quality? It's already 1080p no?
Well , Its difficult to see the screen. Do you have a GitHub repo for the code? Maybe that will help us view the code clearly
Stop starin at me while I’m watching the video
But i like staring --_--
Why is it called advances techniques and then you proceed to show basic skills that you learn in every 20 minutes guide
That's front end Devs for you my guy
does not using all these inline css (tailwind) makes things more complicated and difficult to maintain and read. I prefer using tailwind css and simple css both, tailwind for small things and responsiveness and plane css for complicated design and animation.
A totally valid way to code :) I personally find it easy to maintain as I know what I'm looking for in the styling but everyone has a preference!
It's not advanced techniques, just basic classes usage
ikr
and all these comments about this being useful... just read the docs bro wtf
who use h1 in the button man
fair haha
This not a advance tutorial. All techniques are just basic.