This is more awesome than it first appears. They are a SaaS "Create Once, Publish Everywhere" (COPE) provider. NPR popularized the term a few years back, and t

This is more awesome than it first appears. They are a SaaS "Create Once, Publish Everywhere" (COPE) provider. NPR popularized the term a few years back, and the use it in their production environment. I have one client actively using the same architecture in production, and they love it. They use a Django site as the backend, and node.js-powered websites to publish the content. Some links on the topic: http://blog.programmableweb.com/2009/10/13/cope-create-once-publish-everywhere/ http://blog.programmableweb.com/2009/10/13/cope-create-once-... http://www.linkedin.com/groups/Do-you-COPE-Create-Once-3912082.S.117059484 http://www.linkedin.com/groups/Do-you-COPE-Create-Once-39120... http://www.slideshare.net/KMcGrane/adapting-ourselves-to-adaptive-content-12133365 http://www.slideshare.net/KMcGrane/adapting-ourselves-to-ada... http://karenmcgrane.com/2012/09/04/adapting-ourselves-to-adaptive-content-video-slides-and-transcript-oh-my/ http://karenmcgrane.com/2012/09/04/adapting-ourselves-to-ada... http://www.markboulton.co.uk/journal/adaptive_content_management http://www.markboulton.co.uk/journal/adaptive_content_manage... http://meetcontent.com/blog/structured-content-an-overview/ http://meetcontent.com/blog/structured-content-an-overview/ One of the uphill battles they face is the nomenclature. Most people couple their content creation tools with the publishing tools. I.e., we think of a CMS as both the editor and the content renderer. This sort of system decouples that. I think they are smart starting with a PHP library: that seems to target a broad install base, and publishing in PHP using an API is much easier than building a solid CMS in PHP.