How should I write the guidelines for the design (colors, dimensions .etc) for the front end developer to use?
At the moment I just create an overlay on top of my design and write notes in that overlay.
How do you do it?
Thank you!
-
3You need to ask this question of your front end developer. – DA01 Dec 5 '14 at 16:33
-
Yah, I did. This is why I asked here. We are trying to figure out a better way of sending deliverables. – Sebastian Dec 5 '14 at 17:33
What most people do in this situation is to provide the developers with a pattern library / design library /style guide. This is what I provide the developers at my company with.
Its basically a wiki that shows the developer what they need to build out say the navigation for example. It will provide them with all the information they will need to remake your design so that it meets your design requirements. Its up to you how granular you think you need to be to get these guys to successfully understand how to remake your vision correctly.
Here are two examples: http://ux.mailchimp.com/patterns http://www.starbucks.com/static/reference/styleguide/
Good article to read: http://alistapart.com/article/creating-style-guides
answered Dec 5 '14 at 21:40
If you don't like doing it on a layer (which sounds fine to me), print it out and mark it up by hand.
Somehow you have to indicate an object or call it by name and write a list of characteristics describing it. Whether you do that in the program or on paper is up to you and your developer.
answered Dec 5 '14 at 18:46
Lauren-Clear-Monica-IpsumLauren-Clear-Monica-Ipsum
20.1k7 gold badges58 silver badges96 bronze badges
-
As a FE developer I'd personally rather have a virtual copy of the notes, preferably on the design files themselves – Zach Saucier Dec 6 '14 at 8:24
