| | February 20168CIOReviewOff with its Head: The Future of Content ManagementBy Sandeep Sood, VP-Software Engineering, Capital Oneoftware is getting smaller. The era of the monolithic, all-in-one enterprise solution is giving way to a range of focused tools that do a few things exceptionally well. The content management system (CMS) is no exception to this trend. Any CMS that supports a large enterprise's website probably took many months (and many millions) to implement, and it undoubtedly includes functionality to author, template, store, render and present every single page of the website. In some cases, this all-in-one CMS may still be the right choice for an organization. However, many enterprises are beginning to realize that a more light-weight, focused solution may provide more flexibility and control.The Headless CMSThis lightweight CMS option is often referred to as "headless" or "decoupled", because it is not used to render a site or application. With the front-end functionality (or "head") removed, the tool is now a specialized backend focused on delivering content via an API. Most enterprise websites already take advantage of several APIs. Therefore, one way to look at the headless CMS is that it simply takes the API revolution to its logical next step: if companies are already getting maps and pricing data from an API, why shouldn't their text and images be delivered the same way? Application agnosticEnterprises need to manage content assets and publish them. They aren't making just web pages anymore...they are feeding content to a bevy of applications on a variety of device types. As this becomes the norm, content management becomes a service like anythin g else. Organizations need APIs that are available to serve content on demand, in a manner that is decoupled from design or functionality. Since the headless CMS decouples itself from design and presentation, it stores and delivers content to all kinds of applications more seamlessly than the current, traditional CMS. For example, if a company codes the front-end of their website in Angular, the site can get the content it needs, without any constraints or implications to the design and functionality of the front-end code. Then, when they upgrade part (or all) of their site's design, the new website uses the same content API. In contrast, a traditional CMS is extremely expensive to upgrade, and with each passing year, the amount of legacy content grows, causing each successive upgrade to become more and more expensive. The headless CMS is also ideal for Android and iOS users, since they are accustomed to using APIs Sopinionin my
< Page 7 | Page 9 >