##Digital Team - Development Guidelines
The point of having development guidelines is to have a common vocabulary of coding so people can concentrate on what you’re saying rather than on how you’re saying it. We present global development rules here so people know the vocabulary, but local rules are also important. If code you add to a file looks drastically different from the existing code around it, it throws readers out of their rhythm when they go to read it. Avoid this.
Before reading this, you should have a general understanding for specificity, javascript, jQuery, HTML and CSS.
If you're visiting from the internet, feel free to learn from this guidelines. This is a guide we use for our own apps internally at Sancho BBDO inspired by other guidelines. We encourage you to set up one that works for your own team.
##Guides:
##Linters:
A lint tool performs static analysis of source code and flags patterns that might be errors or otherwise cause problems for the developer.
Below you can get the settings files you can use on your projects:
##Tools:
- JS Hint: Is a tool to detect errors and potential problems in JavaScript code and can be used to enforce coding coventions.
- CSS Lint: This tool points out problems with your CSS code. It does basic syntax checking as well as applying a set of rules to the code that look for problematic patterns or signs of inefficiency.
- HTML Inspector: It is a code quality tool to help you and your team write better markup. It's written in JavaScript and runs in the browser.
- jsBeutifier: This little beautifier will reformat and reindent bookmarklets, ugly JavaScript.
- CSS Compressor: Use this utility to compress your CSS to increase loading speed and save on bandwidth as well.
- Sprite Cow: This site helps you get the background-position, width and height of sprites within a spritesheet as a nice bit of copyable css.