CSS "Best Practices" Don't Actually Work – Tailwind CSS Does And It Will Knock Your Socks Off
Switching from traditional CSS to a utility CSS framework like Tailwind will knock your socks off. In this demonstration we'll fly through a few reasons why CSS "Best Practices" don't actually work and just make CSS harder. I'll demonstrate how Tailwind improves your development experience, allows you to rapidly prototype, and will help you fall in love with CSS again. With Tailwind CSS there's no more: - thinking about naming conventions (think BEM) - worrying about organizing your CSS file structure based on templates or components - switching back and forth between template files and CSS files - CSS stylesheets that seem to only ever grow larger Instead, with Tailwind CSS you get: - tiny CSS files in production - rapid prototyping - like, really fast. - best in class tooling (JIT compiler, integration with your favorite compilers) - forced consistency without even thinking about it - and plenty more After a primer we'll put Tailwind up to the test and produce the same UI with both traditional CSS and then in Tailwind. The benefits of Tailwind will be clear. If time permits, we'll take a sneak peak at a JS equivalent of Tailwind called Alpine.js.
Basic understanding of CSS