anchor.diff:  
     <p>
     In <s>superfluous</s>, asynchronous delivery lets you inject a placeholder into a
  -  template and whenever you run a callback with new data, the new data will be
  +  template and when you are finished preparing some HTML, the new HTML will be
     injected into that spot of the page.
   
     This is particularly well suited to data fetching and the callback heavy
  
positive.code: <h2>Features</h2>
  
  <p>
  <b>Speed</b> - <s>superfluous</s> has the initial delivery speed of a server app,
    and the rich interactions of a client heavy app. By delivering the main core
    of the page to the client ASAP, the client can display the app and
    download assets while the slower parts of the page are still generating.
    </p>
    <p>
  
    <b>Flexibility</b> - <s>superfluous</s> handles many boilerplate tasks but
    still leaves the developer freedom to architect their web app - whether it's
    choosing how to render, which data layer to use or how to split the client and server
    responsibilities.
    </p>
  
    <p>
    <b>Re-usability</b> - Components 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.
    <br />
    Components can be rendered on the server or client and treated as the same
    instance. This eliminates much of the tedium of creating rich and re-usable
    interactions.
  
    <div class="alert">Many large web codebases today are using Component based
    page generation on the server to minimize development friction.</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
  
negative.code: client. The server and client both have a 'socket' function that lets them
  setup communication between each other.
  </p>
  
  <h3>The Bridge</h3>
  
  <p>
  The bridge is used by the server to run code on the client. It lets the server
  run client code and takes care of downloading the required files before doing
  so. During app delivery, the bridge lives on <b>api.bridge</b>, while during
  socket communication, the bridge lives on <b>socket.bridge</b>
  </p>
  </div>
  
  <div class="developers">
  <h1>Boilerplate</h1>
  