Does tailwindCSS fit in Compony?
It should become an option to include Tailwind CSS postCSS plugin in to Compony.
Some things should be taken in to consideration: TailwindCSS is way to big to include and respect the component-behaviour of Compony. Therefor we would need to incorporate PurgeCSS directly with Tailwind CSS: https://tailwindcss.com/docs/controlling-file-size
There is also a catch on scalability: Because this is not just a few utility classes, it feels way to massive to include as a component.
To research: why isn't it possible to include partials from Tailwind CSS instead of including everything and then purging the unused stuff?
We need to find a way to include partials of TailwindCSS as no-one will use everthing from it.
Using it as a CDN wouldn't work, as it contains normalise.css
Preferred way to integrate would be postcss + gulp: https://tailwindcss.com/docs/installation/
What's holding us back at the moment, that it is way to complex and it defines everything from HTML-classes, to config.js variables, all to avoid writing CSS. Which in truth sounds like a shortcut no-one should take.
But then again, everyone liked bootstrap too...