Adam Wathan
Full-stack developer, creator of Tailwind CSS; writes at adamwathan.me and makes courses and screencasts for web developers.
Adam Wathan did not write this page.
We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.
-
by
Their wordsIt was functional and declarative, rather than procedural and imperative like Sass, and it had one killer feature Sass didn't have: classes as mixins.
-
by
Their wordsThe utilities were the only things that were truly "portable", while the component styles were always too opinionated to reuse on another design.
- 19 months earlier
-
by
Our reading
Tailwind CSS has the potential to be a high-impact project for helping people build software.
Their wordsThe more I've heard from people using Tailwind CSS, the more I've realized it has the potential to be the highest impact project I've ever worked on in terms of fulfilling that goal.
↗Software developer, author, and host of Full Stack Radio.adamwathan.me 1st of 2 in this piece
-
by
Their wordsMuch like Evan has done with Vue.js and Taylor has done with Laravel, I think there is potential to fund a lot of Tailwind development through corporate sponsorship, especially once v1.0 is out and if I can continue to grow the user base.
↗Software developer, author, and host of Full Stack Radio.adamwathan.me 2nd of 2 in this piece
- 17 months earlier
-
by
Their wordsI noticed something else when I started focusing on creating reusable classes: The more a component does, or the more specific a component is, the harder it is to reuse.
↗Software developer, author, and host of Full Stack Radio.adamwathan.me