Tailwind #31
Replies: 1 comment
-
👋🏻 TL;DR: We didn't run with Tailwind because our themes don't use it (yet 😉) tailwind.mp4Here’s a summary of the video transcript:
The overall message is about the incremental, cautious adoption of Tailwind CSS, balancing its utility with the team’s existing styles and development philosophy. |
Beta Was this translation helpful? Give feedback.
-
This project is brilliant. Congrats and thanks to the Archetype team for this effort! My agency builds enterprise Shopify themes for merchants in Liquid, and we've been exploring and experimenting with theme architecture and tools for some time now. Archetype's component-based framework coupled with Figma tokens is exactly where we've been heading - finding this project turned on all the lights in the room for us.
That said - we love Tailwind. Moving to individual css/sass per component is going to be a hard-sell for our team. Can someone explain the reasons why Tailwind is not preferred for component-based theme development? I get that Tailwind requires a build, but the benefits of using it (especially with massive improvements in Figma-to-code solutions looming on the horizon) would seem to outweigh whatever concerns exist around using a build process (which I would be curious to understand as well). I'm also interested in evaluating the appetite/viability of forking this project to create a Tailwind version, so if anyone has thoughts on that, or would also be interested in that, make it known.
Beta Was this translation helpful? Give feedback.
All reactions