[HN Gopher] Building a Design System at a Startup
___________________________________________________________________
Building a Design System at a Startup
Author : sunaden
Score : 25 points
Date : 2021-02-28 06:49 UTC (16 hours ago)
(HTM) web link (medium.com)
(TXT) w3m dump (medium.com)
| xnx wrote:
| Don't. There are many existing systems to choose from. Very
| unlikely another design system the user has never encountered
| before will add value.
| felipellrocha wrote:
| Feels a little to strong for something that provides deep value
| for a company and _must_ be unique to your brand in order to
| truly differentiate yourself.
| dmitriid wrote:
| Most design systems solve things specific to that particular
| company. _And_ the vast majority of available design systems
| (that is whose documentation or even components are opensourced
| or publicly available) are any combination of the following:
|
| - abject shit. A material-ui or bootstrap wannabe with poorly
| thought-out colors, spacing, and interactions. And often has
| the same problems with sizes, affordances, contrast etc.
|
| - underpowered. Contains too few components beyond the simplest
| of the simplest buttons and a tab control.
|
| - underspecified (about 99.99999% of all design systems). Does
| not have any documentation on how elements interact, how they
| look and work together in complex layouts.
| mattwad wrote:
| That's not entirely true. Even if you use something as full-
| featured as Material UI, there's still opinions on how elements
| are composed, when to use font colors and sizes, etc. Without
| documenting what to do in common cases, every page will end up
| looking slightly different. I'm the only dev on my team but I
| already started a styleguide to help me see how CSS changes
| affect all components, and as a way to copy/paste common
| patterns.
___________________________________________________________________
(page generated 2021-02-28 23:00 UTC)