Maybe we're arguing semantics, but I think calling shadcn a "basis for a design system" is more accurate than a traditional component library. The difference to me is that shadcn lives inside your codebase and you can fully customize it as you please. You cannot customize a component library like MUI nearly to that extent.
Maybe we're arguing semantics, but I think calling shadcn a "basis for a design system" is more accurate than a traditional component library. The difference to me is that shadcn lives inside your codebase and you can fully customize it as you please. You cannot customize a component library like MUI nearly to that extent.