New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature idea: Tailwind config output #8
Comments
As a Tailwind user, I'm not 100% sure a plugin would be super beneficial. You can already just copy-paste the CSS output to your index.css file. I'm transitioning my own tailwind-baseline (https://github.com/apkoponen/tailwind-baseline) plugin from the old "basekick" algorithm to the "capsize" version right now. In the plugin, the idea is that you can just add a |
Personally I agree. Without being a tailwind user, that appears to be just boilerplate wrapped around the css-in-js view. Is there something I'm missing? |
Some people may want to define the class in their config as an alternative to using the css output. @apkoponen that plugin looks interesting, thanks for sharing. |
@apkoponen I always used a capsize similar implementation using before and after pseudoclasses. But I am wondering if it's the right approach. |
Hey there, Congrats on the launch!
I was thinking that a Tailwind plugin output would make a good feature.
I've modified an example from their docs to illustrate how the output could be displayed:
What do you think?
The text was updated successfully, but these errors were encountered: