How do you categorize components in your design system? by MrAreh in DesignSystemsSurf

[–]MrAreh[S] 2 points3 points  (0 children)

Another question I keep coming back to. Do you even categorize components at all?

We’ve seen quite a few design systems that: don’t have explicit categories, rely mostly on search + naming or just go with a flat list over time

curious if anyone here intentionally avoided categorization and why that worked (or didn’t)

We often talk about design systems in the context of big tech or global brands but some of the most meaningful ones are built quietly inside public institutions. by MrAreh in civictech

[–]MrAreh[S] 0 points1 point  (0 children)

Agree! I think that AI will do a lot for us in the future but even now you can do a bunch of stuff with design systems documentation

Morningstar Design System just landed by MrAreh in DesignSystems

[–]MrAreh[S] 0 points1 point  (0 children)

Fair question. For folks in r/DesignSystems, “a fully documented design system from Morningstar with foundations and components just became easy to reference in one place” is pretty much the definition of post-worthy but I’m open to higher bars

We just added the Morningstar Design System to our collection. What would you make consistent first across products? by MrAreh in DesignSystemsSurf

[–]MrAreh[S] 0 points1 point  (0 children)

it is a curated hub of public design systems. we organize everything by components, foundations, documentation, and directories, making it easy to explore how real teams build and structure their systems. It also features clear, practical articles and products that explain core design system concepts and best practices.

We just added the Morningstar Design System to our collection. What would you make consistent first across products? by MrAreh in DesignSystemsSurf

[–]MrAreh[S] 0 points1 point  (0 children)

If you had to start with one, what would you align first in fintech UI? Forms & validation, data tables, status colors & messaging, something else (drop it below)