anchor.diff:  }</code></pre>
   </div>
   </div>
  +
  +<p>Each <b>server controller</b> has a <b>routes</b> and <b>post_routes</b>
  +method that tell the app where to find the handler for that given sub-route.
  +</p>
   
   <h3>MVC</h3>
   
  
positive.code: 
    <p>
    <b>apps</b> and <b>pages</b> are very similar, but with one difference: a
    page has no client controller, while an app does. Apps and pages live at top
    level URLs and are responsible for delivering a rendered page to the client
    web browser.
    </p>
  
    <h3>File Layout</h3>
  
negative.code:   </p>
  
    <p>
    <b>Re-usability</b> - Components are <b>Backbone.Views</b> that encapsulate
    re-usable portions of rendering, event handling and data synchronization
    code. Using components on a site adds structure, well defined behaviors and
    division of responsibilities. Every component is responsible for managing its
    sub DOM, so the responsibilities are clear cut.
    <br />
  
    <div class="alert">Many large web codebases today are using Component based
  