images

README.md

@@ -52,7 +52,6 @@ The example application uses the following JavaScript libraries:
 * [Backbone](http://documentcloud.github.com/backbone/) for models, views, routing and history management,
 * [Handlebars](http://handlebarsjs.com/) for view templates.
 
-
 ## The Example Application: Facebook Likes Browser
 
 While traditional site login using e-mail and password is still around, single sign-on gained popularity
@@ -72,6 +71,8 @@ After successful login, your Facebook likes are fetched from the Open Graph and
 
 Besides the likes browsers, there’s a second screen which displays some latest posts on the moviepilot.com Facebook page. This is just another controller in order to demonstrate the change between controllers with proper routing and cleanup.
 
+![Machine](http://img.ly/system/uploads/003/362/032/original_machine.jpg)
+
 ## The Architecture in Detail
 
 The following chapters will discuss the core objects and classes of our application structure.
@@ -225,6 +226,7 @@ As a consequence, our controllers are quite skinny. In most cases, they just ins
 
 There’s no specific reason for this decision, it’s merely a convention on where to put fetching and rendering code – your mileage may vary.
 
+![Dance](http://s3.amazonaws.com/imgly_production/3362020/original.jpg)
 
 ## Event Handling Overview
 
@@ -322,6 +324,8 @@ As mentioned above, Publish/Subscribe is a powerful pattern to promote loose cou
 
 The Publish/Subscribe pattern is the most important glue in our application because it’s used for most of the cross-module interaction.
 
+![Ending](http://s3.amazonaws.com/imgly_production/3362023/original.jpg)
+
 ## Conclusions
 
 By releasing this code into the public, we’d like to start a community discussion on top-level application architecture. “Application” means everything above simple routing, individual models, views and their binding.