engine VS shadcn/ui

It's not, but I appreciate you sharing this anyway – thank you!

I was referring mostly to GSS: https://gss.github.io/

I think it was an interesting idea that unfortunately didn't really work out. This was before both flex and grid layouts were a thing, so anything new in this space was exciting really. It's a much better css layout world today than it was 8-10 years ago, and particularly grid layout is a very welcome change, but I can't help but think some great ideas have been left by the wayside. Maybe for good reasons, but still.

I'd love to see something like constraint layouts in pure CSS. It's an incredibly powerful tool when building user interfaces.

I was really excited to see GSS (http://gss.github.io), however at the time it was far too slow to be usable in real projects.

It's been a while since I messed with it. IIRC, the way it satisfies the constraints tends to support some really complex adaptive sizing behaviors once you learn to anticipate it. But I never ended up using it seriously, because flex is usually (and possibly always) good enough, and I don't think the web port https://github.com/gss/engine ever saw much adoption. Not completely sure they offered a way of talking about lists of child elements.

Shadcn UI

You can access shadcn/UI using the following links. Official Site Github Repo

I build an Angular or React app or smart component that uses the store in an Nx monorepo. I use the Shadcn UI in React apps, and the Shadcn-based spartan/ui in Angular apps, so I can use almost the same app architecture both in Angular and React.

Finally, for our front end, we’re going to be pairing Next.js with the great combination of TailwindCSS and shadcn/ui so we can focus on building the functionality of the app and let them handle making it look awesome!

Shadcn/ui: I've never tried it before but have always wanted to switch from MaterialUI

Honestly the ergonomics of heavily customizable generic component libraries aren't great. Copy and pasting a simple component to make the specific customizations you want helps reduce JS ecosystem churn and dependency pain. Popularity of libraries like shadcn/ui [1] are good acknowledgements of that.

[1] https://ui.shadcn.com/

shadcn/ui

This model is very similar to the popular shadcn workflow. After files are creating in your local repo, you can modify them and check them into source control.

Link: https://ui.shadcn.com/