Menu Search
Jump to the content X X
SmashingConf London Avatar

We use ad-blockers as well, you know. We gotta keep those servers running though. Did you know that we publish useful books and run friendly conferences — crafted for pros like yourself? E.g. our upcoming SmashingConf London, dedicated to all things web performance.

Author:

Varya Stepanova is a senior developer for SC5 (Helsinki, Finland) with a major specialisation in frontend components and similar experience at Yandex (Moscow, Russia) and TMG (Amsterdam, the Netherlands) behind her back.

Juuso Backman works for SC5 as a senior developer. Nine years of full stack development in various domains have taught him to love test automation. Likes to sit on the drum throne as well.

Twitter: Follow Varya Stepanova & Juuso Backman on Twitter

How To Automate Style Guide-Driven Development

Style guides — especially living ones — are useful in many aspects of development and maintenance, so it’s little wonder that developing them has become a highly recommended and a popular practice. But even with the clear benefits, taking the necessary steps to create and start using style guides is easier said than done, as quite often the challenge is cultural, requiring changes in people’s mindsets.

Automating Style Guide-Driven Development

In order to make the transition as painless as possible, equipping yourself with the most helpful tools and automating as many steps as possible become important. These living style guides promote a systematic approach to composing layouts, which used to be just a task within the user interface development process. Incorporating style guides into the development process places importance on the tools used to build the component catalogue.

Read more...
1

↑ Back to top