@TedJenkler
Posted
Hi Larisa,
In most cases, I find Tailwind to be easier than traditional CSS because the documentation is incredibly fast and accessible. I suggest using ChatGPT or referring to the documentation whenever you get stuck—with time, you’ll start remembering all the Tailwind classes effortlessly.
One tip that might help: Have you installed the Tailwind CSS IntelliSense plugin for VS Code? It provides class name suggestions as you type, making it much easier to work with Tailwind. Without it, I can understand why it might feel challenging.
The big advantage of Tailwind is the speed of development. I’ve completed projects in just a few hours that would take days to finish with CSS or SCSS. However, for larger projects, I still believe SCSS is the better option, but for small projects, Tailwind wins hands down in every aspect.
Hope this was helpful.
Best, Teodor
Marked as helpful
@LarisaKampe
Posted
@TedJenkler Thank you so much for response!
I have the plugin, but I guess try so much to think about what the class is and what I have to do to make it work at the same time and when I find the class it seams so obvious and logical that I forgot what else do I need to do 😅. But since I made this page with regular css I will try to make this same web with tailwind as well, guess I'll have the 'steps' already done.
Thank you again! :)
@LarisaKampe
Posted
@TedJenkler
Hello! I have done it in tailwind also! Thank you for your help, it was easier than expected and with little theme setup it was really quick end efficient to do it!
The link for the tailwind version: https://frontend-practise5-tailwind.netlify.app/
I will try to do more challenges in tailwind too!
Thank you again! :)
