Replies: 3 comments
-
I think we can definitely do what we want to do using just PostCSS. This should decrease build times, and give us a deeper integration with Tailwind, which should be good for how users can configure Captain. The next choice is, do we write a plugin for PostCSS or do we write a plugin for Tailwind? |
Beta Was this translation helpful? Give feedback.
-
I think we should start by writing a plugin for Tailwind, as it has a lot of useful functions built for us. It also allows us raw access to postCSS, so we can effectively write a plugin for postCSS this way even if we wanted to. Seems a no brainer to me. |
Beta Was this translation helpful? Give feedback.
-
The I believe it's ready to release. I'm just finishing documentation, which will then be available at https://captaincss.hexdigital.com |
Beta Was this translation helpful? Give feedback.
-
Please see our overall roadmap first for context before reading this issue.
This is a discussion for the v2 Proposal. Anything we research, discover or ideate for v2 can live here.
Beta Was this translation helpful? Give feedback.
All reactions