[Brajeshwar]

Referencing and being inspired by someone‘s Design System is a good thing. Try looking at a bunch of them to get a better perspective.

However, using someone's Design System may not always be a good choice. Unless, they are lean, non-directional and are mostly patterns that you can adapt to any tech stack or systems. For instance, Google’s Material Design Philosophy is a good starting point and you can leverage it as your base system. You’ll still need to understand the WHYs of the principles. Without understanding the core principles and the WHYs, you’ll be dependent on it in the wrong fashion.

Here is an example without trying to single it out from the other Design Systems. Sometime back, I studied Ant.Design to see if I can adapt to a massive product overhaul. Unfortunately, I realized that it is a system more specific to the way AliExpress does and think about their design. And technically it was in LESS (CSS Pre-Processor).

There are many good, well thought out systems. One being that of AirBNB’s JavaScript styleguide.

Be inspired, and possibly start with a system that has fewer restrictions, a lot of community activity behind it.

[switch007]

> ... and possibly start with a system that has fewer restrictions, a lot of community activity behind it.

Any recommendations?

[bradleyhb]

What’s meant by non directional ?

[Brajeshwar]

Now, I'm not sure if I used the right vocabulary. I meant, it has constraints which lead you one way in a singular path, their way.