- https://github.com/shadcn/ui
- https://www.radix-ui.com/
- https://evergreen.segment.com/
- https://element-plus.org/
- https://www.hyperui.dev/
- https://jetbrains.github.io/ring-ui/master/index.html
- https://github.com/N00nDay/stwui
- https://www.melt-ui.com/
- https://captaincodeman.github.io/svelte-headlessui
- https://github.com/techniq/svelte-ux
- Light/dark theme
- Configurable color system
- Interactive docs
- SSR support
- Plug & play (no configs needed)
- TypeScript support
- Fast & clean animations (remember @prefers-reduced-motion)
- Figma
Multiple color palettes could be nice, should be really easy to change if i've designed the system correctly.
Should use https://tailwindcss.com/docs/customizing-colors#default-color-palette as default color palette. Think i want to use Tailwind for developing, but it should not be a dependency for using the library.
Don't really wanna be the one to tell others what icons they should use. Using https://github.com/antfu/unplugin-icons, or maybe just designing the API so that icons should come from somewhere else, sounds appealing.
The documentation page must be stupid simple and fast. Also need to find out what should be shown in the API documentation for every component.
Not sure about this yet... idk if there are components that only need classes to be used, e.g. button or badge. But if this is the case, then two types of styling sheets could be provided:
- enabled (all button elements will automatically be styled)
- disabled (you need to apply button class to style elements)
Begin with components that are most commonly used. Also maybe wait with a11y, because that's a big rabbit hole. My opinionated list of components to start with (in order):
- button
- input (text, textarea)
- select
- checkbox
- dropdown
- switch
- tabs
- dialog
- popover
- tooltip
- toast
- avatar
- label
- radio group
- datepicker
- slider
- menu bar
- navigation menu
Future (UI)