EndangeredMassa · August 29, 2015 14:08 · Oct 31, 2014 · Oct 31, 2014 · Oct 31, 2014 · Oct 31, 2014
diff --git a/notes.md b/notes.md
@@ -20,9 +20,13 @@
 * remember to include breaks in the schedule
 
 The overall flow of the workshop works best, in our experience, like so:
-* start with static prototyping with the router and static templates
-* have activities where the attendees build new templates (maybe by extracting bits from an existing template) and hook them up to new routes
-* work in model hook calls to make the templates dynamic
-
-
-
+* present: static prototyping with the router and static templates
+* activity: build new templates (maybe by extracting bits from an existing template) and hook them up to new routes
+* activity: do it again
+* present: route model hook calls to make the templates dynamic
+* activity: make other part(s) of the app dynamic
+* activity: do it again
+* present: introduce controllers and computeted properties
+* activity: add a computeted property or two
+* present: introduce actions
+* activity: add an action
diff --git a/notes.md b/notes.md
@@ -1,7 +1,7 @@
 # Running an Ember.js Workshop
 
 * have visualizations for describing how nested and sibling UI elements map to URLs
-* provide homework to attendess
+* provide prework to attendess
   * make sure Node.js 0.10.* is installed
   * make sure ember-cli is installed
   * provide resources for getting up to a minimum bar, like http://discover-devtools.codeschool.com/

diff --git a/notes.md b/notes.md
@@ -20,9 +20,9 @@
 * remember to include breaks in the schedule
 
 The overall flow of the workshop works best, in our experience, like so:
-- start with static prototyping with the router and static templates
-- have activities where the attendees build new templates (maybe by extracting bits from an existing template) and hook them up to new routes
-- work in model hook calls to make the templates dynamic
-- 
+* start with static prototyping with the router and static templates
+* have activities where the attendees build new templates (maybe by extracting bits from an existing template) and hook them up to new routes
+* work in model hook calls to make the templates dynamic
+
 
 
diff --git a/notes.md b/notes.md
@@ -1,4 +1,4 @@
-# Workshop Notes
+# Running an Ember.js Workshop
 
 * have visualizations for describing how nested and sibling UI elements map to URLs
 * provide homework to attendess

diff --git a/gistfile1.txt → notes.md b/gistfile1.txt → notes.md
diff --git a/gistfile1.txt b/gistfile1.txt
@@ -0,0 +1,28 @@
+# Workshop Notes
+
+* have visualizations for describing how nested and sibling UI elements map to URLs
+* provide homework to attendess
+  * make sure Node.js 0.10.* is installed
+  * make sure ember-cli is installed
+  * provide resources for getting up to a minimum bar, like http://discover-devtools.codeschool.com/
+  * bring your laptop chargers
+* provide a premade starter application to attendees
+  * check in node_modules
+  * check in bower_components
+* describe how to start a new app with ember-cli (you could even do it in front of them), but have their starting point be the result of a new app; this saves time that would otherwise be spent waiting for X people installing dozens of modules
+* your hands-on activities should:
+  * be as realistic as possible
+  * clearly described with obvious desired outcomes
+  * be reimplemented in front of attendees after activity is over, explaining along the way
+  * have clear jump-to points, like git tags or branches, to allow anyone to jump to the appropriate starting point
+  * be timed
+* if using a third party API, make sure you won't hit rate limits
+* remember to include breaks in the schedule
+
+The overall flow of the workshop works best, in our experience, like so:
+- start with static prototyping with the router and static templates
+- have activities where the attendees build new templates (maybe by extracting bits from an existing template) and hook them up to new routes
+- work in model hook calls to make the templates dynamic
+- 
+
+
No results found