2

Our team has run into a challenge that I imagine is quite common: we were asked to kick off a project using a prebuilt Design System as the foundation (in our case, PrimeNG), and adapt it to our needs in Figma.

At first glance, these systems are designed to be very versatile. But that same versatility ends up being a double-edged sword: the sheer number of component variants creates confusion for designers, who struggle to know which one is “the right” choice for a given use case.

For example, you might find:

  • Text fields with floating labels, inline labels, or stacked labels.
  • Buttons with rounded corners, sharp corners, or outlined styles.
  • Etc

After trying deep customization, we came to the conclusion that it’s more efficient to build our own Design System tailored to the project. Sometimes we borrow or adapt components from PrimeNG, but instead of trying to fully customize PrimeNG and use it as the team’s standard, we decided it’s better to stick to our own system. That way, new team members can immediately use our version without getting overwhelmed by all the original options.

I’d love to hear your thoughts:

How have you handled similar scenarios?

Did you try to adapt and constrain an existing system, or go for a more focused, custom one?

What strategies have worked for you to avoid overwhelming documentation and too many variants?

Looking forward to learning from your experiences!

2 Answers 2

1

I’ve adapted existing design systems or UI kits to projects, but also have run into the issues you touched on, and ended up “borrowing” as a middle-ground strategy just to get the ideas out. Eventually, it lead to creating a more tailored systems.

These prebuilt systems are built to be "everything for everyone", which often means they’re not quite right for anyone without ever running into significant tailoring. I find that when you go the tailored route, design and dev teams are more aligned, and it's easier to document components for other designers that might be onboarded later on with a clear and concise visual language to design with confidence. Stick to your own systems, and build on those.

1
  • Your experience is very similar to mine. Started with an existing system and tailored to what I needed. Commented Sep 18 at 10:23
0

It is great that you have already have a library but to start with you will still need the basics.

  1. Decide a font-family - decided by the branding.
  2. Decide a palette of colors – decided by the branding.
  3. A theme – e.g. bright & cheerful or bold & active, etc.
  4. Language tone – very formal, slightly formal or casual.
  5. Visual language – sharp and bold with sharp cornered elements or friendly with rounded edges, etc. Filled icons and buttons vs. outlined ones.

I may be missing some here, but once you have these defined, you will have a direction. The guidelines should not be very rigid but having the direction will keep things consistent.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.