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:   <div class="controllers">
    <h3>Routes and the Router</h3>
    <p>
    Every app has an entry point on the server, accessed via its top level URL
    (or <b>route</b>). The route tells the router where to find the controllers
    to instantiate the app that the user will be interacting with.  </p>
  
    <p>
    App Routes are configured in the <b>routes.json</b> file - it is a global
  
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
  