Right. From the post: "It’s not that we fundamentally disliked the previous approach. We just reached a point where we felt our goals weren’t best served by th

Right. From the post: "It’s not that we fundamentally disliked the previous approach. We just reached a point where we felt our goals weren’t best served by this model. With lots of dynamic data, complex visualizations and a set of “static” interfaces, the traditional way was hindering our development speed and our ability to experiment." It's very much targeted to our specific needs. Our approach is no more universal than Wordpress or Drupal. We have however harvested interesting conclusions from moving away from these CMS and that's mostly what I was interested in sharing. With regards to using Worpress as a middle man for data centric apps, this is the kind of things we've done. My opinion: CMS are good at doing regular type of content CRUD based apps, but it breaks quickly. Moreover, most popular CMS are becoming bloated pretty quickly. Have a look at Jekyll (http://github.com/mojombo/jekyll http://github.com/mojombo/jekyll), it's a much better fit for that.