RU version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
100% Positive
Analyzed from 346 words in the discussion.
Trending Topics
#shadcn#design#llm#defaults#using#components#point#generated#why#system

Discussion (11 Comments)Read Original on HackerNews
This is made easier with the /create UI: https://ui.shadcn.com/create
People use it like a design system, but it’s more like a design system for design systems.
The driving purpose of Tailwind is to provide a massive suite of utility classes to atop a consistent set of design tokens and yet the vast majority of projects using it will be plucking patterns wholesale from TailwindCSS Plus, Flowbite, etc.
Even Bootstrap was designed for customisation but still, a large number of teams who deployed it would stick largely with the defaults. It's just how it goes, and it's a perfectly valid complaint from observers.
I have absolutely nothing against Tailwind and shadcn/ui so don't take this as a criticism. This is aimed squarely at the people who point out that these tools are designed for customisation without acknowledging nearly every deployed example pulls from the same limited pool of defaults, UI components and larger templates. And why wouldn't they, tailored design systems take incredible effort and skill to get right.