Going back 15 years, we’ve seen the core of providing websites shift across various types of “platforms” - from Web Content Management (WCM) to Enterprise Content Management (ECM) to Customer Experience Management (CEM). Every iteration involved another set of technologies, and associated migration headaches.
Each expansion also consumed more and more of the resulting presentation tier. At first, this was mostly a good thing as no standard mechanisms existed to facilitate efforts. However, in the last few years alone key frameworks have arisen to tackle this job much more effectively, such as: EmberJS (2007), AngularJS (2009), and Backbone.js (2010). Suddenly, the templating systems embedded within a CMS platform were not only unnecessary - but were actively getting in the way of good website design - much like a certain iceberg.
Cloud CMS allows you to fly over this barrier with an API-first approach. No more shuffling deck chairs - sorry Leo. We’ll take it from here…
With Cloud CMS, you’re free to select any presentation framework and build your customized look-and-feel that focuses on both your content, as well as your customer. No meddling in the page delivery, no unsupported add-ons, no unnatural or customized CMS configurations - just a pure API driven solution, done right and provided natively.