zeroheight for Design System Tech, Documentation Automation

Problems

  1. Design of components in app and Pajamas do not match
  2. Pulling in components to Pajamas requires Front End work
  3. Pattern library/Instance sheet being the Single Source of Truth (SSOT)

zeroheight as a solution

Design of components in app and Pajamas do not match

zeroheight has a design tokens API, which in theory, would keep the app up to date with our latest designs from the design system. Not much documentation on it, but that's what I assume that feature does. This also causes

Pulling in components to Pajamas requires Front End work

zeroheight automates the process of updating the design system for us, when we update components, colors, typography, etc. in our pattern library/instance sheet. No need to pull in additional support from FE to do this. This will speed up our documentation process and require less resources in order to push certain components in our docs live.

Pattern library/Instance sheet being the Single Source of Truth (SSOT)

Currently, we are pulling in components from the app to the design system. This requires that we always keep the app up to date. But because we can easily update the pattern library and instance sheets, some app components will be out of date. So if we want our pattern library/instance sheet to be our SSOT, we need to reverse our deployment process. Instead of deploying designs from the app, we need to deploy designs from our pattern library/instance sheets. zeroheight can help us do this by deploying from those files to the design system and from the design system to the app.

Edited by Pedro Moreira da Silva