anchor.diff:  
   <p>
   App Routes are configured in the <b>routes.json</b> file - it is a global index
  -of what apps the server is going to be serving and where. Inside each, app the
  -server controller has a routes member that tells the router which functions to
  -hand requests to.
  +of what apps the server is going to be serving and where. Inside the
  +routes.json, each server controller has an entry that tells the router which
  +controller to hand requests to.
   </p>
   
   <div class="mtl mbl">
  
positive.code: the basics are there.
  </p>
  
  <h4>A danceparty demo</h4>
  <p>
  It's also possible using templates, sockets and controllers to make a slightly more complex app: <a href="http://github.com/okayzed/danceparty.sf">Check out the code</a>
  </p>
  
  <p>
    This example opens the web cam and uploads a client recorded file to the
    server. When a new GIF is uploaded, all clients are notified. Easy :-D
  </p>
  
  
  <div class="components">
    <h3>Components</h3>
  
  
negative.code:     synchronize the currently displayed kitten among each other. Not very
      exciting...  but the potential for something more is here :-D
    </p>
    <h3>A danceparty demo</h3>
    <p>
      It's also possible using templates, sockets and controllers to make a
      <a href="http://dance.nicesho.es">slightly more complex app :-)</a>.
  
  
    </p>
  
    <p>
      This example opens the web cam and uploads a client recorded file to the
      server. When a new GIF is uploaded, all clients are notified. Easy... :-D
      <a href="http://github.com/okayzed/danceparty.sf">Check out the code</a>
    </p>
  
  
  
  
    <h3>An app in the wild</h3>
  