DEV Community

Oles Maiboroda
Oles Maiboroda

Posted on • Updated on

Control the colors in your project

Sometimes you may face this kinds of projects:

Example

Hard case, huh?

which bring you a little discomfort in the stomach. Today we'll talk about colors in particular and how they can be organized.

Audit

One of the great options is to use online tools, like cssstats.com

Example

dev.to on cssstats.com

The issue with it that it shows only the colors that appear on the single page, so if you have code-splitting, some colors might be missing.
I had a need something that would just show the colors used in the source files, but there wasn't anything, so I had to write a small utility colors-in. It traverses the folder end extracts used colors:

colors-in

Colors in src folder

Fix

Having this you can look at your the designs UI Kit or talk to your design to define the colors you're gonna use across the project.

At that point, we'd a need to "merge" similar colors and there's one approach you can do it. Since all colors are living in 3-dimensional Red, Green, Blue space, we can calculate the distance between them:

colors-in

Euclidean distance

From my empirical feeling, those colors that are having less than 10% color difference can be deprecated in favor of more often used in a pair.

colors-in

Difference between two shades of gray with npmjs.com/package/color-difference

Other things you can do:

  • Unify color format to hex;
  • Agree on 6 digits hex format;
  • Remove unnecessary opacity layer;

In our case we were able to reduce the number of unique color definitions from 29 to 14:
Before:

colors-in

29 color definitions

After:

colors-in

14 color definitions

So if you have that "zoo" - make an Audit. Or if you keep your colors in an organized way - check if you forgot to use it somewhere else with >colors-in src;

Latest comments (0)