You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many projects are adopting Tailwind, including our flagship, Hub.
How can we support developer's desire to use Tailwind while also creating components within our design system?
A couple paths:
Keep the design system the way it is
There's no rule saying that Tailwind cannot be mixed with regular ol' CSS and Sass. However, developers might be reluctant to mix named classes from the design system with Tailwind, and just opt to use Tailwind only.
Create our design system components using Tailwind
We could go all-in and make something like https://tailwindui.com/, but for thoughtbot products. This probably means more maintenance for contributors to tbds, and (maybe) more set-up for folks using tbds in a project.
The text was updated successfully, but these errors were encountered:
Many projects are adopting Tailwind, including our flagship, Hub.
How can we support developer's desire to use Tailwind while also creating components within our design system?
A couple paths:
There's no rule saying that Tailwind cannot be mixed with regular ol' CSS and Sass. However, developers might be reluctant to mix named classes from the design system with Tailwind, and just opt to use Tailwind only.
We could go all-in and make something like https://tailwindui.com/, but for thoughtbot products. This probably means more maintenance for contributors to tbds, and (maybe) more set-up for folks using tbds in a project.
The text was updated successfully, but these errors were encountered: