As components are repeated and need to be standardized, after meeting with the Design Council I'll create new or modify existing components.

Below is a Date Picker component that was deprecated and needed updating for particular experience needs.

Specifically, it needed to account for having a range, an error, and a header. This required not only the UI to be updated for those unique scenarios, but for the component to allow for Designers to switch between these variants intuitively.

Seen here are the enhancements to the available properties to the Date Picker component, which allow for a variety of combinations to be utilized for different experiences.

As you can imagine, some components end up have a LOT of variants...and even still have new ones to account for as unique experience needs arise across a complex product.

Back to the Date Picker, this and similarly complex components benefit from some design guidance placed alongside the variants, where I'll provide the how-tos. This helps mitigate blindspots Designers may have as far as the inner workings of the component itself.

Once the component design work is done, I'll head into Zero Height to create new or update existing documentation for it. This ends up being the source of truth for Designers and Developers alike, to learn everything about the component—its types and variants, behavior, options, and when or how to use.

Once a nice handful of updates have accumulated, I'll then publish the list of most recent updates in a Release Notes page within Zero Height as a kind of "what's new" area for Designers and Developers to keep up to date.