Use an existing design library or not? #2
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: libscie/researchequals-frontend#2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
With v1, it became a hodgepodge of things. The goal is to get a consistent UI in the new front end, that maintains the reliability, rigor, and accessibility that we are striving for. Most component libraries are too generic and bubbly, which end up not fitting with what we are trying to convey.
Right now, an option I am considering is Carbon Design by IBM. The design language is extensive, and I don't fully agree with IBM's take on design (doh) it does provide a coherent approach that can be adapted.
Open to other options – preferably available in Svelte. I may end up deciding against it or not, i am not sure. Will play around :)