5 ms·
> the major stumbling block has been how tailwind is mostly just css translated into its own hard-to-memorize lingo. Autocompletion in your IDE makes this easy
by seanwilson 5y ago
> the major stumbling block has been how tailwind is mostly just css translated into its own hard-to-memorize lingo.
Autocompletion in your IDE makes this easy (the class names are similar to the CSS attributes, even in your examples, so you can usually guess them) and you use the same classes over and over again so you learn them quick. I barely spent 10 minutes in the Tailwind documentation the first few days because of the VSCode extension.
- marstall 5y agoah yes - that would be a big help. alas I am not a vscode user. I use webstorm and haven't been able to figure out how to get tailwind autocomplete to work with it.
- jpbow 5y agoThere's a plugin that you have to install to get it going https://www.jetbrains.com/help/webstorm/tailwind-css.html https://www.jetbrains.com/help/webstorm/tailwind-css.html
- marstall 5y agooh I forgot to mention. ember. it's an ember project. something about handlebars not being supported yet.
- superfad 5y agoOther than autocomplete, I would also suggest using this cheat sheet to help you: https://nerdcave.com/tailwind-cheat-sheet https://nerdcave.com/tailwind-cheat-sheet