Ideally, no component library will need to be made to build this project. However, I currently don't have the bandwidth to develop my own component library for this and future projects. Additionally, accessibility is a great concern for me. I need everyone who visits my website to use it to it's full extent, this would require researching accessibility guidelines which are exhaustive and not dooable for me in this moment of time.
✅ Goals
Goal 1: Find an accessible component library
Goal 2: Ensure component library is performant and provides seamless user experience
...
🎯 Solution Summary
📝 History/Context
Initially, I was considering DaisyUI for the component library for my personal website, but after further research and disucssions among peers, I had some concerns raised to me.
DaisyUI is purely tailwindCSS, this means that animations and interactive performance could suffer
Since DaisyUI is entirely tailwindCSS, I would have to configure the accessibility myself
DiasyUI's community figma component library is lacking in comparison to others (ex. shadcn/ui)
DiasyUI, explained above why I won't use DaisyUI.
TailwindCSS, tailwindCSS purely won't be scalable, I've done it before, it is too much work.
MaterialUI: I love material-ui, it also is very accessible, however, shadcn/ui has taken the web-dev community by storm.
🛠 Problem Statement
Ideally, no component library will need to be made to build this project. However, I currently don't have the bandwidth to develop my own component library for this and future projects. Additionally, accessibility is a great concern for me. I need everyone who visits my website to use it to it's full extent, this would require researching accessibility guidelines which are exhaustive and not dooable for me in this moment of time.
✅ Goals
Goal 1: Find an accessible component library Goal 2: Ensure component library is performant and provides seamless user experience ...
🎯 Solution Summary
📝 History/Context
Initially, I was considering DaisyUI for the component library for my personal website, but after further research and disucssions among peers, I had some concerns raised to me.
💡 Solution
Shadcn/ui for Svelte will be used.
🤔 Other options considered
DiasyUI, explained above why I won't use DaisyUI. TailwindCSS, tailwindCSS purely won't be scalable, I've done it before, it is too much work. MaterialUI: I love material-ui, it also is very accessible, however, shadcn/ui has taken the web-dev community by storm.