Product data is a core of e-commerce and integral part of the customer experience and customer journey. The well-organized product data drives customer acquisition, sales and eventually results in the increasing lifetime value of a customer.
SAP has recently announced a new SaaS offering, SAP Product Content Hub, a cloud-based solution for product and information management (PIM). The new product relies on the SaaS model only.
In this article, I’m basically just going to give a little bit of an introduction to what SAP Product Content Hub is as well as shed some light on what is under the hood in terms of architecture and customizability. Read More »
What content management system you use is of a much higher importance today than it was years ago. Today’s CMS needs to contend with a multi-device world with a wide variety of tablets, mobiles, laptops, and be architecturally ready for new not-yet-existing channels in the consumer’s universe, such as AR/VR and the Internet of Things.
A CMS typically consists of a frontend part, or a «head», and backend. The headless CMS, as their name says, don’t stick to a single predefined “head”. Theoretically you can develop your own if it is good for your case. Another name for headless CMS is API-first, because this interaction is based on APIs.
There are a number of headless content management systems that are mature enough to efficiently replace the built-in Smartedit CMS. Among them I would highlight Contentful, Prismic, DotCMS, Cloud CMS, Amplience, and ContentStack as well-established and innovative products with clear roadmap and good integration capabilities.
One of my recent research projects was aimed at using ContentStack as a headless content management system for SAP Commerce Cloud. This article uncovers the key highlights of the research. As the result of that work, I also created a data migration tool for moving existing CMS content from Commerce Cloud to ContentStack.
What is ContentStack? ContentStack is a SaaS headless CMS with an API-first approach that offers the approach known as Content-as-a-Service. It focuses on managing structured content into data feeds that other applications, such as Commerce Cloud, can consume. You can design a content data model interactively or via the ContentStack API and populate the structures with the content interactively or via the same API.
In this article, I pay special attention to the data migration from Commerce Cloud’s CMS to ContentStack. This exercise helped me to see the complexity in all its glory. Because when you design a system from scratch, you can evade platform’s constraints by designing the structures compatible only with the new CMS. When you need to migrate data, you have to find a solution on how to adapt concepts and data models to get them compatible with Commerce Cloud.
Read More »