anchor.diff:  word count overall and by author, time spent editing overall and by author, and
   so forth.
   
  +* Isomorphic rendering of editor's server-side and client-side for performance.
  +
   Please
   mailto:sales@vivosys.com?subject=Interested%20in%20the%20Ritzy%20Service[let us
   know] if your company or startup may be interested in such a service.
  
positive.code: ** Insert HTML at a particular position specified by the native data model
  ** Event callbacks for inserts, deletions, changes, and selections
  ** Command and status support for text attributes e.g. to support a toolbar
  
  * A skinnable toolbar that leverages the editor API (medium).
  
  
negative.code: * Once tests are in place, refactoring to make the editor code more modular /
  easier to understand (hard).
  
  * Performance improvements. Performance is pretty poor right now but much can
  be done to improve it. Some ideas:
  ** Create finer-grained React components (see refactor above) to avoid
  re-rendering the entire editor on updates (this should be a big win).
  ** Implement `shouldComponentUpdate` and/or `PureRenderMixin` to avoid
  unnecessary component renders.
  ** Implement some type of indexing for characters.
  ** Use immutable collections as much as possible e.g.
  http://facebook.github.io/immutable-js/
  ** Cache frequently used / slow operations where possible.
  
  * Module loader support i.e. inclusion via Browserify, Webpack, etc. (medium).
  
  