One of the biggest challenges companies face when starting out on an accessibility journey is the uphill battle in identifying, addressing, and remediating potentially hundreds of thousands of issues across their digital properties. In addition, executives who are tasked with managing the digital accessibility program must increasingly align their efforts with the organization’s Diversity, Equity and Inclusion (DEI) initiative - a wider initiative under which web accessibility falls.
I was recently asked by a customer how you could quickly create a carousel in DXM. Of course, there are several ways to do this but I figured it may help others if I shared this very easy method. Feel free to implement and improve as required.
In this post, I’m going to show you how to create a simple React application that leverages Bootstrap. Then, I’m going to show you how to import it into Crownpeak DXM to allow non-technical practitioners to manage the content within the CMS, which will deploy as JSON into the same environment as the React App, for consumption at runtime.
You can create dashboards in Crownpeak DXM that consume analytical data from almost any source. This example shows you how to achieve this using Google Analytics; however, the same process can be applied for almost any provider.
Content aggregation — sourcing content from several disparate sources, normalising the content, and then making it available to downstream consumers — is often pitched as a key benefit of headless content management. In this article we take a look at content aggregation and how this can be accomplished using DXM.
Demonstrate steps to create an experience in Crownpeak DXM, for marketers & content managers, to build and deploy Salesforce Marketing Cloud (formerly known as ExactTarget) forms without going through a development cycle. On submit, these forms in-turn create a subscriber inside ExactTarget (ET) and saves the same data to a Salesforce data extension.
This is part of series of articles that is looking at “headless” content delivery. Before we take a look at the use cases where headless is considered to be a very good fit, I wanted to look at the two key pieces in most, if not all, headless content delivery: non-web content; and pulling content.