Comment by ericmcer

Why are you doing this? Developer efficiency? Consistency in UI/UX? New behaviors existing libraries don’t support? Some manager thought it would be a good idea?

Just stay mindful of why you are being tasked with doing this so you can make sure you push it and generate metrics in the right way to demonstrate it is a “success”. There are a couple libraries that generate “demo” websites for React components, those can be flashy and get eyes on your work. You could also generate charts showing adoption rates and other things that make it seem like the library is very useful.

You must have some existing reusable component system as well right? Can you just centralize that and then everyone is already subscribed for once the updates go out?