Books be Gone: The Future is Living
by Shanda Nelson, Product Designer at GetYourGuide
Don’t have time to read all the amazing facts below? No problem. Here’s the short list…
- The days of exporting red lines and specs to a PDF are gone. By the time you finish the basic principles, it’s outdated. These style guides are typically done unilaterally with one discipline in mind and therefore, they are ineffective for a multi-functional team.
- Creating a Living Guide will take some time in the beginning. However, It pays off with faster build times for new components and pages. Anyone joining an ongoing project can refer to the style guide because it’s made with multiple disciplines in mind and highly usable for non-tech folk.
- A style guide allows standardization of CSS. By using the style guide as an inventory of components and code, both Designers and Developers can quickly see if new designs deviate from current standards, and decide as a team if it’s worth expanding the code and visual language. With the absence of a style guide, this is impossible — new styles are written, resulting in bloated CSS and a messy brand or product.
- Features must automatically update, ensuring that the style guide is current. Use a framework that complies with the team process and testing environment.
- Consistency is easier to maintain with code and visual language.