Hi,
I'm the author of http://www.staticms.com
This tool was initially intended at bridging the gap between flat file CMS and more dynamic needs. It is focused on pure speed, with many "infrastructure side" performance optimizations. What I wanted to do was "kill the ****ing database, it is not in its rightful throne behind a corporate website" (but may be in an ecommerce or forum or blog)
Its concept is simple: You have a config, with URL templates, that maps to functions (resize this, markdown that...) that may use simple files in a tree structure called "distribution".
However, when I tried to sell it to some web agencies around my place, the only answer I got was: "What? Theres no online backend system with plugins? How are my customers adding their pictures galleries?"
I then added a feature that allows proxying a pure CMS (for instance, Wordpress), through my system to get optimizing on the fly and integrated CDN, and it now works.
But now, I'm in direct competition with http://www.mobify.com or http://www.fasterize.com which are optimizing proxys (albeit more "automatic" than mine)
What do you think of this approach? Does it suit some needs?
PS: Blog post on how to configure StatiCMS to proxy a WordPress "static" (no comments, and the likes.. in fact, no "POST" really) website: http://blog.staticms.com/pour-survivre-restons-caches/ (in French)