@zamiang: Open Sourcing Force blog post

This is a blog post announcing open sourcing Force along with some anecdotes about modularity, .env files and the updates they brought to Ezel. Since you put in a lot of effort setting Force up to be open source I encourage you to add to/modify this post as much as you want. I just wanted to get the ball rolling on it.
This one could be clearer (seems like a lot in one sentence!)

The short story is that we moved from a monolithic rails app to a couple of Node servers on Heroku. This vastly improved the performance of our site and our own development speed. Using the patters in Ezel, we are able to tailor assets packages to specific pages and render some of the page on the server - this cut our pageload in half (from 6.5 seconds to under 3 seconds). Additionally, our tests take about 5 minutes (down from around 5 hours!) with little reduction in coverage. Performance numbers aside, our real win was dramatically improved development speed due to some architecture decisions we made.