Feature suggestion for developemnt #238
Description
As per title, no problem here, tailwind works great and the gem too. As it is designed.
But i find during development, it is a whole lot faster to prototype in the browser.
Using the development tool (inspector) i add/remove/modify classes in the browser until i am happy and then copy the result into the template. Have another look and move on.
This saves all the reloads and while that may not sound a lot, it adds up. The approach is in line with tailwind i find, and actually got the idea from a video Sam Selikoff, emberconf.
Off course for this to work, one needs the complete tailwind build (300k), so the classes are actually available.
I know i can (and do) achieve this quite easily with an if and the cdn. But i though it would be nice if it were integrated and documented as an at least alternative workflow. If it were integrated, tailwind configuration changes/additions would also be available.