Frontend & UI

Frontend & UI covers the tools that turn markup and logic into interfaces: component libraries, design systems, CSS frameworks, build tools, and dev environments for building and testing UI in isolation. Projects like ui (shadcn), material-ui, tailwindcss, storybook, vite, and radix primitives all fall under this umbrella, but they solve different layers of the problem, from raw styling to fully composed components to the tooling that bundles and previews everything.

Picking between them depends on where you sit in the stack. If you need ready-made components with a consistent look, a kit like material-ui or a copy-paste system like shadcn/ui gets you moving fast. If you want full control over visual design without fighting a component API, a utility-first framework like tailwindcss lets you style directly in markup. Unstyled primitive libraries give you accessible behavior (focus management, keyboard nav, ARIA) and leave the visuals to you, which suits teams with their own design system. Storybook and similar tools sit apart from styling entirely: they're for developing, documenting, and visually testing components outside the app. Vite and comparable build tools handle the dev server and bundling that everything else runs on top of.

When comparing options, look at:

• Bundle size and runtime cost, especially for component libraries shipping their own CSS
• Accessibility support, particularly for interactive components like dialogs, menus, and comboboxes
• Framework lock-in (React-only vs framework-agnostic)
• Customization model: theming via config, CSS variables, or direct source copy
• Maintenance activity and how actively issues get triaged

Most projects in this category are permissively licensed (MIT), so licensing rarely blocks adoption, but it's worth checking before shipping a commercial product.