My main use case for Crownpeak Digital Experience Management is the migration from Crownpeak to Adobe Experience Manager (AEM), where the entire content is in Crownpeak and there is an API exposed for each page or resource. We invoke those APIs from AEM to create the pages in AEM.
In terms of challenges regarding my use case and the migration process, there were many pages in Crownpeak, and each page has a unique URL. The challenge was that when we ran this in batch mode, we had to make a unique call every time, and there is no process in Crownpeak that can give the response in JSON for more than one resource. This resulted in having to make a call to Crownpeak for each individual page.
To manage this limitation during the migration, we maintained a spreadsheet where we listed more than 500 URLs and ran those through our input spreadsheet. Our scripting logic read each URL in a loop, making the API endpoint calls to Crownpeak.
Crownpeak Digital Experience Management positively impacts my organization by providing all content in the form of API, so we do not have to manually review how the pages are created on Crownpeak Digital Experience Management platform. Instead, we rely on the API response that contains all the necessary information, which smoothly creates the pages in AEM.
I have noticed measurable outcomes, such as faster migration time due to the lightweight JSON response. Crownpeak Digital Experience Management API response is quite fast, and our logic to parse the JSON and create the pages in AEM is also fast, making it a highly efficient approach to migrate content from Crownpeak Digital Experience Management to AEM.
In my opinion, the best feature Crownpeak Digital Experience Management offers is its headless approach, which allows the JSON response to be consumed by any platform, making it excellent for any front-end application, including React or Angular applications, which can consume this data exported by Crownpeak Digital Experience Management in the form of API.
This headless capability benefits my projects because any consumer platform using any kind of front-end application, whether it is plain HTML, CSS, or JavaScript, or any front-end framework such as React, can make calls to Crownpeak Digital Experience Management API and render it. This leads to no tight coupling between the API response and the consumer platform, resulting in a flexible approach.
Regarding features that stand out apart from the headless approach and flexibility, Crownpeak Digital Experience Management provides the entire content, including page title, metadata properties, descriptions, and tags, ensuring a comprehensive API response that creates a full page without leaving any areas where we need to do manual work.
Crownpeak Digital Experience Management can be improved by providing APIs that group content rather than giving the response for one page at a time. For example, having all article content exposed in one API, as well as news and blog content, would help reduce time-consuming individual API calls.
Regarding needed improvements, I think that reading the JSON can be quite complex. If Crownpeak Digital Experience Management could provide a CSV format where all content is exported, it would help content authors review or make changes before creating pages in AEM, especially since they are not very proficient in reading JSON files.
I have been using Crownpeak Digital Experience Management for one year.
Crownpeak Digital Experience Management is a good platform if you want to leverage the headless approach, centralizing content management while allowing various platforms to consume that content from a centralized place where you can easily update and modify it.
I gave Crownpeak Digital Experience Management a rating of seven out of ten because of a couple of challenges. The API is a one-to-one resource with one API endpoint, and Crownpeak Digital Experience Management could have grouped multiple resources into one API response. Additionally, the JSON format is quite complex and not easy for our content team to update; exporting data in CSV for multiple pages would help significantly.