Changed the setup to reflect how Unmesh and I ran the classes these past couple weeks. Added some subjects, moved others around

Razpudding · Razpudding · commit 3b1be7e12af6 · 2016-11-25T16:14:44.000+01:00
diff --git a/README.md b/README.md
@@ -4,36 +4,40 @@ Brainstorm JavaScript module
 Here is an overview of the brainstorm sessions for the JavaScript modules.
 Feel free to make suggestions or add anything.
 If everyone can help out with elaborating on the different subjects that would be great!
+What you see below is a rough layout for the first three Javascript modules. Feel free to deviate from this layout but try to cover all of the subject matters listed.
 
 
 # What
-
-## Git introduction (one week)
-  * publish your websites on Git (UI)
-  * branch and push, clone
-
-## Module 1
+  
+## Module 1 (3 weeks)
+ * what is a CLI
+ * Basic Git commands by CLI 
+ * publish your websites on Git (UI)
+ * branch and push, clone
  * Intro Javascript (What is it, where can you use it for)
- * Basic datatypes (array strings numbers objects)
+ * Querying the DOM
+ * Basic datatypes (array, string, number, bool)
  * Loops, if statements
- * Function decleration and excecution (code flow)
- * Scope
+ * Browser debugging & ClI debugging
 
-## The browser environment the CLI env (two weeks)
-* what is a CLI
-* Git commands by CLI
-* Browser debugging vs ClI debugging
 
-## Module 2
+## Module 2 (3 weeks)
+ * Code conventions
+ * Function declaration and excecution (code flow)
+ * Scope
+ * Github documentation (readme, description, open sourcery)
+ * Git tracking, terminology
  * Advanced datatypes(objects)
  * Code flow
  * JavaScript functions, callbacks (events)
+ * Writing a multi function program (or game :)
 
-## Module 3
- * Http protocols
+## Module 3 (3 weeks)
+ * HTTP requests
+ * APIs!
  * JSON
- * API's
- * Unit testing
+ * Polling external data dynamically
+ * (Unit testing)
 
 ## Optional: 
  * Code patterns
@@ -43,10 +47,11 @@ If everyone can help out with elaborating on the different subjects that would b
 
 # How
 
- * More interaction, working together in class
- * Verbal checks in class, see if they get it (maybe by presenting their work very shortly in class)
- * Smaller assignments of our own, not via FCC
- * Check in with students during the week, small questionaire?
+ * Try to find an example you can expand on. For instance coding a website that lists the students in the class along with their Github Repos. This way you can show anything from DOM querying to objects (for each student) and even load up the Github API
+ * Live coding in class to show how certain features work.
+ * Ask students to present their work, let them know failing while coding isn't just accepted it's encouraged. Fail often and fail early.
+ * Homework is listed on Trello and handed in on Github
+ * There's no strict lesson plan, adapt to students' need and level. Try to make up more advanced challenges for quick learners.
  * Test after every module, if students fail they can't move on to the rest of the program. It is possible to redo a module (one time).
 
 
