Decide on UI components

Endangered-Language-Alliance / ela-website

Endangered Language Alliance website

1 stars 0 forks source link

Decide on UI components #13

Closed abettermap closed 3 years ago

abettermap commented 3 years ago

Which of these from https://reach.tech/ have a place in our world?

Accordion (never been a huge fan)
Combobox. Could see this, although way out of SOW in every aspect, being used for filtering languages list or searching blog lists.
Disclosure. Simple little guy but useful. We don't have disclosures but seems handy for any place that doesn't need to immediately show its content, but its availability still needs to be known.
Listbox or Menu button. Good for "sort by" type stuff.
Tabs. This is the big one. Is it the way to go for Editor-drive Language content? Seems like it.

abettermap commented 3 years ago

@rperlin-ela If you have a chance to give any of these a skim, please do. I know the response might be the usual Trust The Jason, which is fine, but if any of them look like flat out not useful or applicable, or have a bad smell to them, I can at least cross them off the list of potential components.

abettermap commented 3 years ago

Also try to ignore the styles, it's a bare-bones component library, that's why I picked it since I now prefer styling things myself rather than relying on the monolith of Material. Just going for the main feel of the generic concepts and applicability to what we're doing. It ties in directly with questions like

what needs to be shown first?
Shown always?
Shown at least within the first interaction like scroll or click

These aren't just considerations of "what can we fit on the screen without it being crowded?" It's also about prioritizing and organizing based on what's important, and how to present that effectively.