The new automated Content REST API makes it very easy to consume content from the CMS via REST. "Hippo always had REST APIs. The main difference is, that in previous versions, a java developer would have to implement the domain specific REST service classes for a tailored REST API on top of Hippo CMS, rather than one being there automatically out-of-the-box. The CMS is now architected to run both use cases side by side, allowing developers to much more quickly experiment with apps and Internet of Things” said Arjé Cahn, CTO of Hippo.
Providing this new agility to app and web developers will improve the overall business agility and innovation flexibility. “The new automatic Content REST API makes it faster and easier to integrate content in the CMS with apps and single page web modules. Providing an app-like user experience on web now requires less API work” Peter Broekroelofs, CTO of Service2Media, added.
By 2018, 50% of enterprises will be managing their content using a hybrid content architecture, the recent Gartner report “Cool Vendors in Content Management 2015” states. The hybrid content architecture of version 10.2 provides both headless CMS capabilities AND a state-of-the-art delivery tier and brings the best of both worlds combined in one system to an organization.
Key benefits of Hippo 10.2 include:
On the 10th of March, Hippo’s Director of Product Marketing Sonja Kotrotsos, will host a webinar around this release. In this webinar Sonja explains why she believes it is essential to have one central platform from which you can deliver content and gain insights across all your channels and why Hippo CMS 10.2 just made that part of your life a little easier.
Read more and sign up here.