Arunan will rant be talking about his experiences of working with existing and legacy projects, that have poor or no documentation; why style patterns help you learn, do less tedious work, and make you a “rock– star” in the eyes of future developers of what you are working on now; and how to make your own style-guide framework.
15. Developer Documentation
• Define coding conventions for front-end
• Additional info on why some non-standard ways of
implementation was required
• Coding rules for the team
Eg:
• http://csswizardry.com/2012/04/my-html-css-coding-style/
• https://github.com/necolas/idiomatic-css