Merges JS and Javascript content

Author: vovimayhem

README.md

@@ -16,7 +16,7 @@ Icalia Guides is the programming style used at [Icalia Labs](http://icalialabs.c
   * [Rails](stack/rails)
   * [Git](stack/git)
   * [Sass](stack/sass)
-  * [Javascript](stack/js)
+  * [Javascript](stack/javascript)
   * [Swift](stack/swift)
 
 

stack/javascript/README.md

@@ -1,11 +1,34 @@
 # Javascript Best Practices
 
+This is a guide to work with Javascript on IcaliaLabs projects.
+
+## General Guidelines
+
+When working with javascript try to follow this simple rules:
+
+* Use camelcase for method/variable naming
+* Never use global variables
+* Encapsulate logic in classes, as they are easier to test. Use syntax transpiler for this, such as [babel](http://babeljs.io/).
+* Use underscore at the beginning for private methods naming
+* Prefer to isolate javascript code on individual files
+* Prefer not to use the script tag on HTML for inline javascript code
+
 ## Package management
 
-Always use `yarn` instead of plain `npm`:
-  - Yarn package resolution performance is better
-  - Yarn selective dependency resolution is required to [deal with vulnerable sub-dependencies](#dealing-with-vulnerable-sub-dependencies)
-  - Yarn workspaces feature may become commonly required
+* Always use `yarn` instead of plain `npm`:
+  * Yarn package resolution performance is better
+  * Yarn selective dependency resolution is required to [deal with vulnerable sub-dependencies](#dealing-with-vulnerable-sub-dependencies)
+  * Yarn workspaces feature may become commonly required
+
+## Code Review
+
+There are simple guidelines when providing code review to a teammate. The most particular are:
+
+* Review for bad variable names
+* Review bad class definition
+* Review for class names
+* Review for correct dependencies invocation
+* Review for specs
 
 ## Dealing with vulnerable sub-dependencies