HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
alexpate
awesome-design-systems
Learning & Reference2017–2024
alexpate / awesome-design-systems

awesome-design-systems

💅🏻 ⚒ A collection of awesome design systems

9Distinct people
9Mentions
0Explicit recommenders
26.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

💅🏻 ⚒ A collection of awesome design systems

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year9 dated mentions

Observed mentions: 2017-06-07 13:57:04 UTC to 2024-09-18 00:37:29 UTC.

0122017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC110
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC220
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC211
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC202
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101

What Hacker News says

9 sources
styling native input elements is a major pain in the ass. I would say input is probably the most styleable native input. Checkboxes, radiobuttons, select, file input need a lot of fighting to style them. In many cases, what ends up happening is we create a styled div, and have a transparent input behind it to do the right thing. The web form elements in that way just feels quite broken. There's a reason why there are tons of design systems that replicate a number of form elements using plain div/span elements with css and javascript. https://github.com/alexpate/awesome-design-systems I wish the people designing the spec weren't so disconnected from reality of what people actually want to do with the web. A lot of the problems can be easily solved by giving more styling ability to native form elements and extensibility.
In Updates to form controls and focus
I haven't used carbon as an engineer, but as someone working on design systems, they're overall pretty impressive. For a giant menu of options, see here: https://github.com/alexpate/awesome-design-systems Atlassian, Lightning, Blueprint, and Polaris are some big names that could be worth checking out. And of course there's always bootstrap. > I'm not really a UI person first and foremost Using another company's component library can be a really fantastic head start, then. Especially if you've got a smaller application that doesn't require the whole kitchen sink. You can build fast with stuff that works, and if down the line you want replace it with in-house components, you've already got a north star of sorts. >I worry about an excessive degree of lock-in that will be hard to back out later if needed. It depends. If you clone the repo and
Read the rest
it works for you, you may not necessarily have to keep it updated if you don't want to. I would worry more about being bound to abstractions that are needlessly complex – many of these systems are designed so that small changes to upstream values propagate throughout the system in very deliberate ways, which can make tweaking intermediate values a bit of a landmine. Using a big ass codebase for a couple components means you might have to go spelunking in a big ass codebase.
In Latitude Design System
devj·Jun 25, 2018Submission

Ask HN: Which design system would be apt for an enterprise application?

We are a small startup in the enterprise big data space where we have lots of data in the form of tables, charts, cards, etc and therefore, felt the need to take the help of an 'enterpricey' design system to make our UI consistent. Checked [this awesome list](https://github.com/alexpate/awesome-design-systems). Couldn't pick one though. We do not have designers in our team so the more popular the better. PS: Have already cancelled out Material from our list.
2 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.