anchor.diff:    <div id="routes_example" class="collapse no-transition">
     <pre class="prettyprint"><code>{
       "/": "about",
  -      "/demo": "demo",
  -      "/kitten": "kitten"
  -  }</code></pre>
  +    "/demo": "demo",
  +    "/kitten": "kitten"
  +}</code></pre>
   </div>
   </div>
   
  
positive.code: controller</b>. The server controller is the entry point for the app. It
  renders the app by placing <b>components</b> into <b>templates</b> and
  <b>partials</b> and delivers the constructed app to the browser, where the
  client controller is initialized.
  </p>
  
  <div class="mtl mbl">
  
negative.code:   jQuery selectors - it's up to you. if  you don't like the idea of templates
    auto-syncing to data models, don't do it. If you do... go for it :-D </p>
    <p>
  
    <b>Server - Client Cohesion</b> - sometimes, coupling is a good thing. Using
    two controllers allows the app to organize itself in a way that makes sense
    for the server and the client, allowing components to exist in many contexts.
  