• beeb@lemmy.zip
    link
    fedilink
    arrow-up
    5
    ·
    edit-2
    9 hours ago

    A lot of ui frameworks are based on tailwind and allow you to customize the components with more tailwind. It’s really a win because:

    • it’s not “just inline classes”, it’s a design system (spacing, colors, breakpoints etc are well structured and not random)
    • it is way less verbose than vanilla css and easier to remember
      • brian@programming.dev
        link
        fedilink
        arrow-up
        2
        ·
        7 hours ago

        shadcn is the primary one for react at least. they’ve done a great job filling the space where you’re trying to build up a design system but don’t want to start from scratch, but they’re great if you just want prebuilt components too

        all the components build on something else like radix, and are pretty simple themselves. normally just the radix component with styles. Installing a component just copypastes the source into your project at configured locations.

        if you’ve ever fought against something like mui to get it to fit design changes or change specific behavior, shadcn is great. at some point the extension points of a library aren’t enough, but if you own all the code that’ll never be a problem.

        • dubbel@discuss.tchncs.de
          link
          fedilink
          arrow-up
          2
          ·
          4 hours ago

          I don’t use react, but needed a decently looking frontend complement library that didn’t look dated, and found basecoat, which is shadcn but without react to be really neat.

          Might be interesting for the htmx crowd here.