This was a blog post written for the Homebase Documentation Site showcasing the process that the design system team takes when a community proposal is submitted to change a current component within the system.
The drawer is a widely used overlay component across Wayfair users, from the Mini Cart on Storefront to Pricing Filters on the Pricing Home Products tab in the Partner Home experience. Homebase has received various proposals from a wide range of teams to alter the drawer component to fit their need, though oftentimes, it’s actually a different component that’s needed altogether. But how does Homebase come to that conclusion with proper justification? Below we’ll dive into a specific case study on Homebase’s drawer component and how Homebase ultimately determined not to update it based on a community proposal.
An audit conducted of 17 public-facing design systems was done to examine four areas:
We then narrowed in specifically on drawer- and UI Region-like components to examine where our opportunity areas are.
It did not come as a surprise that most design systems do not support a drawer component with 10/17 systems not supporting a drawer. In order to understand the flexibility in sizes offered by other systems and their components like drawers (such as panels, rails, sidebars, etc.) we looked at all of the various sizes offered.
A box and whiskers plot lets you easily visualize the summary of a set of data. Since we had collected all of the dimensions of Drawer- and UI Region-like components already in our audit, all we needed to do was plot them now to see how Wayfair’s drawer compares to that of the other 17 systems that support similar components. This visualization will show us the range of sizes that are standard to support.
TL;DR: Between Homebase supported Drawer and UI-Regions, the sizes supported fall well within the standard sizes offered when compared to 17 other design systems.
We got you. Take a look at the case studies below, comparing Homebase’s Overlay coverage to that of Atlassian and Material Design Systems: the coverage is quite comparable.
After many activities, it is concluded that between the Drawer and UI Regions, Homebase has many comparable components that other design systems have as well. An output of these exercises has made it clear though that while our Drawer component is serving most use cases, users need additional support implementing UI regions which created an opportunity to build a more flexible component, Sidebar to be created.
A sidebar is a layout component that anchors on either the left or right side of a viewport and
acts as a shell for informational, navigational, or supplementary content.
Process Summary