anchor.diff:  To access each route, the <b>controller</b> and <b>method</b> can be used. For
   example, <code>url_for("my_controller.get_demo")</code> would return
   <b>/demo</b>.  The reverse router can also resolve parameters, so
  -<code>url_for("my_controller.get_smiley", { id: "12"})</code> will generate
  -<b>/smiley/12</b>.
  -
  -<p>
  -The router's build function is available as <b>ctx.router.build</b> in the
  +<code>url_for("my_controller.get_add", { id: "12"})</code> will generate
  +<b>/add/12</b>.
  +
  +<p>
  +The router's build function is available as <b>api.router.build</b> in the
   server controller and <b>url_for</b> inside templates.
   </p>
   
  
positive.code:   developers are working together on one or more projects.</div> </p>
  
    <p>
  
    <b>Familiarity</b> - Components are simple backbone views with a known
    lifecycle: initialize, render, destroy.  How the component updates its DOM
    tree is up to the developer. It could be MVVM and a data binding engine or
    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>
  
    <p>
    <b>Dynamicism</b> - <s>superfluous</s> has no compilation step. You can
  
negative.code:   <h3>Server</h3>
  
    <p>
    In superfluous, the server is composed of <a
    href="http://www.senchalabs.org/connect/">connect middleware</a> running on
    <a href="http://nodejs.org">node.js</a>. The server is responsible for
    sending <b>apps</b> (a <b>page</b> can be considered a type of app) to the
    client.  The server hosts multiple web apps, each handling a URL path and
    it's sub paths.
  
    <p>
    In addition to delivering the app to the client, the server is generally
  