Share your experience using Wedia Digital eXperience Management

We use the solution for CMS in e-commerce.

The solution provides good stability. CoreMedia is good for workflow management and user reviews.

It is difficult to scale the solution with respect to the costs and infrastructure. The solution's integration and multimedia could be improved.

I have been using CoreMedia for three to four years.

Around 15 to 16 users in our organization use CoreMedia.

I rate the solution a seven out of ten for scalability.

The solution's technical support team is responsive.

We previously used other solutions like Contentful and WordPress. CoreMedia's licensing is cheaper and not so difficult to customize.

Our customers pay a yearly licensing fee for the solution.

Around three to four engineers are needed for the solution's deployment and maintenance. The solution's e-commerce integration feature has impacted our marketing efforts and catalog management. CoreMedia is stable and strong in terms of editorial things. The solution has helped our organization manage translations for different languages.

Overall, I rate the solution an eight out of ten.

It's a powerful content management system – there's really no competitor in the market right now. The main use case is digital marketing. 

For example, if you have offers you want to publish immediately, and you want extended functionality like Adobe Target and Adobe Analytics on top of those offers, Adobe Experience Manager (AEM) is perfect. You can publish something in minutes. 

Adobe has other tools like Analytics, Target, Scene7, and now Centra (which is based on artificial intelligence). Integrating these products with your CMS gives you powerful digital marketing and customer journey analytics.

I haven't worked extensively with other content management systems like Sitecore, but from my experience with AEM, managing content is very user-friendly. 

I don't need to be a technical expert to change content, set up Target activities, or use those features in AEM. The whole environment is convenient and easy to use. For example, if you create a page in AEM and want to use it for analytics in Target, you just export it using options within AEM.

Area of improvement for Cloud Service:

For the last four years, I've been working on AEM as a Cloud Service. I feel the tool has all the features needed for production, but the problem is with skills. Depending on the skill level of the developers building the components within Adobe Experience Manager, you can have a very streamlined implementation or a very difficult one.

Tool-wise, the Adobe Experience Manager support team is not very responsive when the user faces issues in AEM as a Cloud Service. If I reach out to Adobe for something, they create a ticket, and then I might wait three to four days for a response. When I have issues, I want an immediate response. 

On AEM as a Cloud Service, this is the one thing I think Adobe needs to improve. They should resolve issues within a day so everything runs smoothly for the user.

Area of improvement for on-premises: 

For on-premises AEM, everything is managed by us, but since Adobe Experience Manager was not a very big market earlier (though it's growing now), there are limited clients. 

The cost of the tool is high, and maintenance is heavy – it's very costly. So, the developers working in AEM development might not always have the proper skills to develop the components. 

For example, in a normal website, we often see carousels which represent your website in a very dynamic way. Now, suppose you have two carousels on the page – one at the top and the next at the bottom. They have different purposes. If I'm a skilled developer, I'll create one component and serve both banners with the same component – a single, dynamic component. This makes it easy for content editors in the production environment to drag, drop, and change the content.

But, if I'm not an experienced developer or I don't have knowledge of AEM, I might create two components – one for the top and one for the bottom. Maintenance becomes heavy, and it's harder for the content team to understand which component to use.  A less experienced developer might create multiple components for the same function, increasing complexity and challenges.

Over the last three to four years, this lack of resources and skilled AM developers has created these kinds of issues.

I have been using it for nine years now. 

It's stable. From my understanding, especially with AEM as a Cloud Service, they've resolved those issues. When we were on AEM on-premises, if there was a bug, they'd do service pack installations to fix them. 

Now, since they're on AEM as a Cloud Service, Adobe just releases a new version, and it automatically upgrades in AEM Cloud.

It is an auto-scalable product. In my company, there are a lot of people. We have three developers, almost a hundred people changing content at runtime, and then admins like managers and product owners. 

The response time is long. Response time, plus the expected output I need should be clear. It shouldn't be like I raise a request, they send questions, I ask more questions, and it goes back and forth.

Neutral

We had something called 'Trader' – not an official product name, but a customized tool the company used. The problem was everything was in one place. 

For example, you might have product information in Salesforce, but in Trader, everything was in one place – product information, contacts, analytics. 

The company wanted a distributed environment: content in a different platform, frontend in a different platform, analytics, Adobe Target, Salesforce for product information, MuleSoft for integrations. They divided it across different products, and that migration is currently ongoing.

For AEM as a Cloud Service, Adobe sets everything up, so it's not time-consuming. You just raise a request with Adobe, and they'll create a program for you. If you have three projects, you'll have three programs. 

Under each program, they'll create multiple environments – dev, stage, production. In Adobe Experience Cloud, everything's connected. They have pipelines, a repository, and the admin console where you manage users. It's very easy. You set up a repository, commit your code, and run the pipeline.

For the last three years, it's been on the cloud. Some clients want to work on-premises, and others work on cloud, but I've been working on cloud for the past three years.

It is an expensive tool. 

Before using it, you should have some hands-on experience. Someone should show you a two-day demo of what a developer actually does, how exactly do we use it? 

If you understand how to use it, then it can be beneficial for development as well. Understanding how to use it allows to explain to clients the use cases where Experience Manager is effective.

It is easy to learn. You don't need to be an advanced Java developer. With basic Java knowledge and about 15 days to a month of AEM training, including a week or two of hands-on experience, you should be good to go.

Overall, I would rate the solution an eight out of ten, especially considering AEM as a Cloud Service. The best part is the seamless integration with other products. Everything is connected.  

In my current company, we just started using Adobe Target, and the integration with Experience Manager is very smooth. This, combined with how easy it is to manage digital marketing and publish content, is why I give it that rating. Development happens once, but maintenance is ongoing, and AEM makes maintenance simple.