Fantastic documentation tool for component library development
August 30, 2022

Fantastic documentation tool for component library development

Colin Finger | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with zeroheight

As UX Engineer I am responsible for maintaining and developing a component library as well as aiding other users in using the component library and contributing to it. The basis for the development of components is our Design System which is showcased in Zeroheight, so any work we do directly correlates to the information we get from Zeroheight. Zeroheight is filled with information by our Designers and not within my realm of work, however I am able to give feedback to our Designers from the viewpoint of a developer to improve Zeroheight and make it's contents more accessible for the contributors and UX Engineers that we have.
  • showcasing components and other topics
  • ease of seeing detailed information on components (colors, paddings, sizes etc.)
  • ease of finding information
  • possibility of going to previous versions of the design guideline
  • when opening a component image (which opens a new page where the detailed information like paddings and colors are shown), the zoom can only be done by buttons, I'd prefer to be able to use my mouse scroll and for vertical / horizontal scrolling to do ctrl+scroll or ctrl+shift+scroll or something like that
  • communication between designer, developer and ux engineer
  • documentation
  • a single source of truth, so that no discrepancies or misunderstandings can occur
  • increased quality, as less misunderstandings or communication problems occur
  • increased speed of development, as it is a single source of truth for us. The developer can rely on the information in Zeroheight being correct so that he doesn't have to iterate his code again and again.
I have used and still use Sketch and Zeplin too, but they serve other purposes for us. Sketch is used to design the components themselves and they are then exported to Zeroheight where they are showcased and enriched with textual information. Zeplin is used to design application pages, and again the components are exported to Zeplin from Sketch. But Zeroheight is mainly used for the development of the components themselves as well as a documentation for our design guideline in general. It is also used by us for design tokens and patterns, as well as other information on the design guideline, so if someone wants to understand the "why" of a design decision, the explanation can be usually found in Zeroheight too.

Do you think zeroheight delivers good value for the price?

Not sure

Are you happy with zeroheight's feature set?

Yes

Did zeroheight live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of zeroheight go as expected?

I wasn't involved with the implementation phase

Would you buy zeroheight again?

Yes

For creating and maintaining a component library, it is a fantastic tool that creates an interface between Developers, UX Engineers and Designers. It is easy to get both general information about a component, but also incredibly detailed information when looking at the component on a pixel-level, where information on paddings, margins, colors, fonts etc. can be easily accessed.