[iFelix]

No shadcn is great but we rebuilt every component from scratch. And we use styled components, not tailwind.

Storybook here: https://storybook.twenty.com

When it's mature enough we'll isolate this into a UI lib anyone can use

[hannes0]

> rebuilt every component from scratch. And we use styled components, not tailwind.

Honest question: Why?

[charlesTwenty]

Hi, I'm Charles and leading the engineering work on Twenty!

We've made the bet to invest on a tailored design for our components. Using an existing UI library is a strength to use robust components and move faster, but I've always struggled to customize it.

There is always a point where you want something custom that is not supported by the library and you start hacking into it. On previous projects, I've almost always used existing UI libraries. For Twenty, this is a long term project and the initial burden of creating UI components vs customizing existing ones will be marginal on the long run.

IMO, if you have strong design requirement (and you have enough resources ofc), don't go with UI librairies ; I take as much inspiration as I can from them, I may fork one but I would not hack their API

[iFelix]

We want our design to match exactly Figma. Shadcn could have been an option because their approach is to have users copy/paste the code, so it could have worked. But copying styles from Figma isn't much more work, it wasn't painful

[paradox460]

Nice to see someone else using styled components instead of tailwind.