HomeBlogNewsletter

šŸ§‘šŸ¾ā€šŸŽØ Should you allow style overrides? (#48)

Happy Monday!

I'll be sending out more job opportunities on Thursday! If your company is hiring (and you think it's a great company that you'd tell your friends to work at), fill out this form!


One of the first decisions you have to make when starting a design system's component library is whether you will allow style overrides.

This can be a controversial topic. I've had (passionate) discussions about this topic on 3 of the 4 design systems I've worked on.

At the time of this writing, 168 people have voted on this Twitter poll.

Like most design systems questions -- I think that it depends heavily on the business needs the design system is trying to solve.

| Restrict style overrides | Allow style overrides | | ------------------------------------------------------------------ | ------------------------------------------------------------------------ | | - You want to enforce design consistency across multiple codebases | - You need to support vastly different visual, multi-product experiences | | - You want to raise design inconsistency to the DS maintainers | - You are building foundational components anyone can use |

Reply to this email and let me know what you think!

--

If you like this newsletter it would really help me if you shared it with your friends. Tweet about it, post on LinkedIn, and share in slack channels. Building this community can lead all of us to more job opportunities, guest posts, and connections.

Talk soon,

Mae ā€‹

Do you want design systems tips and tricks sent to your inbox?

Ā© 2022 Mae Capozzi