Skip to content
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

How does our design system work with Tailwind? #201

Open
setphen opened this issue Oct 1, 2021 · 0 comments
Open

How does our design system work with Tailwind? #201

setphen opened this issue Oct 1, 2021 · 0 comments

Comments

@setphen
Copy link
Contributor

setphen commented Oct 1, 2021

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:

  1. 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.

  1. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant