6 docs tagged with "Content Management Systems (CMS)"

In the following recipe, we will merge content items from the CMS with product records from a commerce engine in order to populate product pages, whether a Product Detail Page (PDP), Product Listing Page (PLP), landing page, or anywhere products are featured with extended information. This is a typical use case in a headless commerce implementation -- needing to match up additional data with product data, be it pricing or inventory or product care instructions. Frequently developers write glue code in the frontend to address this use case and end up making multiple API calls and stitching together data from the backends. An orchestration layer can configure this data unification.

Splitting Traffic with Multiple Data Sources

Connecting content in your headless CMS with customer data in your CDP

You can implement a solution based on this recipe that explains how to create a personalized email message using user data from a Customer Relationship Manamagement System (CRM) or Customer Data Platform (CDP) and content from the Kontent.ai Content Management System (CMS) and using Twilio to send an email message.

In this tutorial, you will learn how to connect Conscia with a headless CMS to orchestrate personalized experiences for your users. We will use Contentstack as an example, but all headless CMSs work in exactly the same way.

In this recipe, we are merging together data for a full-page article view, where a visitor can read a blog post and then find related articles to read next. These related articles are being supplied by Algolia Recommend's Related Products model. This same recipe can be used for featuring related products in an online storefront using any kind of machine learning model.