We are in the process of updating some of our creative processes and outputs within our company and one of the items we have been experimenting with is the way we generate our UI Style Guide for the developers and partners.
In the past we have built really extensive documents for each screen in the application or website. Your typical screen shot with pixel perfect dimensions and call outs that everyone has seen before. There have been a pain to create for a long time and in most cases become out dated very quickly.
We want to start implementing a Component Base Style Guide that specifies how UI component and/or patterns should be implements vs having to apply specific instructions on every single UI screen. We think this will create more efficiencies and provide a better documentation for the development teams and make it easier for us to keep updated (especially with Responsive Design).
Our goal is to eventually stop producing the static PDF style guides and build HTML version. But our first step is to produce the PDF version and slowly phase into an HTML.
We have tried this with one major project and it was pretty successful. We built the static PDF component base style guide and we had our UI developers build an HTML version of each component. Than our second development team used the HTML document when building out pages. There were a few minor issues but mostly due to the developers not following the style guide and doing their own thing.
However, we tried this on a smaller project and it was hard for the developers to comprehend. I would say it was 70% successful but required the designers to spend more time with the developers to provide feedback or direction on some pages. This could possibly be a skill set issue on the developers part we are just not sure.
There are many links talking about this particular topic but I wanted to see what other folks in the same situation are experiencing. Is it helping? Are you seeing improvements? Any issues you have encountered?