Adobe Experience Manager is a combined web content management system and digital asset management system. The combined applications of Adobe Experience Manager Sites and Adobe Experience Manager Assets is offered by the vendor as an end-to-end solution for managing and delivering marketing content.
N/A
RWS Tridion Sites
Score 9.0 out of 10
N/A
RWS Tridion Sites provides web content management capabilities, connecting people, processes, and information across teams, brands, and markets, to deliver impactful online experiences globally. RWS Tridion Sites' DPX platform enables the use of either traditional or headless publishing. It includes advanced features such as automated personalization, multilingual capabilities and Semantic AI. The BluePrinting® technology at the core of RWS Tridion Sites simplifies reuse and…
Adobe Experience Manager, built on Java, means that the pool of developers available to work on the platform is large. Adobe Experience Manager's front-ends and client library management tooling mean that front-end developers can feel at home despite a lack of Java knowledge.
We wanted a CMS which is known in market, which have a good ecosystem. With Adobe Experience Manager, we get integration with Target, Tag management, and other Adobe products.
Adobe Experience Manager provides way more. It is a much more holistic tool to help us manage the entire customer Journey. I, however, do not have enough power to make those decisions. I did not in fact choose Adobe Experience Manager, but I do like it better.
Adobe's integration with all of its other products requires digital marketing, making its system stand out from the rest. AI integration takes it to the next level.
I selected Adobe Experience Manager because it was the easiest to connect to our platforms, the best cost for the size of our company, and I was using Adobe for almost everything else at the time. I think this was the best solution for our smaller company at the time.
Interwoven teamsites, Documentum, Adobe - teamsites and documentum are old and limited. Adobe rocks but I like where I am and Tridion does a lot of the same things. No need to reinvent the wheel or move to a lateral product.
It is a nuclear missile compared to the other handguns and knives on the market today. But it also requires nuclear technicians and expertise that a handgun doesn't require. Do you need to decimate your competition and you have the investment capabilities necessary to put a …
Tridion is much better for multi-site installations, though Sitecore is a bit easier for content editors to know content types are being used based on visual icon indicators. We've had content editors pick the wrong templates by accident, but Sitecore's visual indicator …
Adobe CQ is SDL Tridion main competitor. Sitecore is designed for smaller companys. Adobe CQ is all java and thus has limitations. Sitecore is also all .net and has limitations. Both use a dynamic model and everything is compiled at runtime. SDL Tridion can be published in a …
Tridion again seemed to be more enterprise level then EpiServer, EpiServer allowed for faster ramp up time of a intuitive .NET framework, but Tridion seemed to have more tools and overall functionality once the CMS was customized towards the needs of the customer.
Verified User
Anonymous
Chose RWS Tridion Sites
I did not play a role in selecting this product so I can't say how it stacked up. I do know that Tridion is an improvement over the last CMS.
Verified User
Anonymous
Chose RWS Tridion Sites
I feel that SDL Tridion's User Interface is to difficult for content authors to understand. I worked with a client that used Tridion for years and she still would get lost in the UI and had to ask questions. There was close to 30% of continual time spent on the project simply …
Verified User
Anonymous
Chose RWS Tridion Sites
SDL Tridion is far superior to CommonSpot. It is much more user friendly and increases efficiency.
Verified User
Anonymous
Chose RWS Tridion Sites
I believe the biggest selling factor for SDL was its customer service and it ability to be responsive. We knew that it was a company that was going to be around for a long time and would continue to provide the support that we would need in the long term.
Tridion's strength is really hosting multiple websites across development, test stage and production.
Verified User
Anonymous
Chose RWS Tridion Sites
The decision to purchase Tridion was made at a corporate level removed from the technical teams. Against our previous open source solution, this has been wildly expensive, impossible to find experienced developers for, and has required completely retooling our organization.
Verified User
Anonymous
Chose RWS Tridion Sites
SDL has a better API and also handles high server load much better. Also, the built-in integrations for translations are more suited for performing lots of translations for many sites. However, Umbraco, like Tridion, has a great community and finding solutions with both …
Verified User
Anonymous
Chose RWS Tridion Sites
We didn't chose WordPress because can't handle the traffic we generate. Sitecore is what we are currently looking at and it looks like a much better alternative to Tridion.
Adobe does a great job in managing sites. Its user interface for authors is intuitive and leaps and bounds better than SDL Tridions new 2013 UI. The ease of install and management makes Adobe CQ a much better product. However, Adobe CQ (AEM) has limitations. It cannot scale as …
Features
Adobe Experience Manager
RWS Tridion Sites
Security
Comparison of Security features of Product A and Product B
Adobe Experience Manager
8.4
Ratings
3% above category average
RWS Tridion Sites
9.0
Ratings
9% above category average
Role-based user permissions
8.40 Ratings
9.00 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Adobe Experience Manager
8.0
Ratings
1% below category average
RWS Tridion Sites
9.1
Ratings
16% above category average
API
7.80 Ratings
8.30 Ratings
Internationalization / multi-language
8.10 Ratings
10.00 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Adobe Experience Manager
7.5
Ratings
4% above category average
RWS Tridion Sites
8.5
Ratings
8% above category average
WYSIWYG editor
7.40 Ratings
8.00 Ratings
Code quality / cleanliness
6.70 Ratings
8.00 Ratings
Admin section
7.00 Ratings
9.00 Ratings
Page templates
7.60 Ratings
9.00 Ratings
Library of website themes
7.30 Ratings
8.20 Ratings
Mobile optimization / responsive design
7.80 Ratings
9.00 Ratings
Publishing workflow
8.10 Ratings
9.00 Ratings
Form generator
7.60 Ratings
8.30 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
I'll answer the second one because I mean, the first one I don't have an issue with. The second scenario is we oftentimes have the need to spin off very small campaign style sites or sites that generate leads but are unbranded and that sort of thing. So that's hard to do in AEM because you have to then create another organization within AEM to do that. And we're talking about sites that are maybe five to 10 pages in size. So we've been investigating Edge, but then that's a different workflow, so we'd have to train people on that. So it would be nice if there was something within the AEM structure that could allow you to do something very similar to Edge, where you make some small micro sites that are not necessarily branded, that you could still host within the platform and not have to retrain everybody on a completely different platform.
SDL Tridion works well for organizations with a large website with a lot of content to continuously create and manage. The use of page templates and component presentations makes creating new pages fairly straightforward. It can be a little cumbersome when it comes to trying to "break from the norm" and build web pages that are outside of the template-driven format; however, there are ways around this to create pages that break away from the normal page-template format of the website. In this regard, SDL Tridion can be pretty flexible, allowing us to create a lot of custom functionality to keep up with constantly changing web trends.
It allows us to scale so that we can make a change on a global footer. And it applies to all of the different property websites. It allows us to set up components and compartmentalize things in a way. The big thing is that it's scalable. And then it also ties into Adobe Analytics and other Adobe products. So we are a complete Adobe shop. Every Adobe product that we can use, we use. I don't think we do it for marketing so much, but for doing target testing and analytics, data scientists are using the same product and so it all speaks.
There are some glitches in permissions inheritance that require us to toggle a save on permissions in groups that inherit from a group that was recently updated.
Large packages require stopping the workflow launcher OSGi components or many workflows will slow down the server.
Locked pages are hard to find unless I use /siteadmin... I often hear that the CQ tools will go away, but if we lose that, some small things might be harder to do, like finding locked pages.
If you are hoping to orbit the planet with a CMS, Tridion is built to leave the solar system. It is a very very powerful solution built for very serious enterprise businesses in hope of robust capabilities, which could be good or bad.
Supporting business users is a hefty lift and requires significant training and regular retraining, and support.
It's a niche solution that originally came out of Europe and was largely unknown in America. But today it's growing in popularity across the United States.
Finding capable support, and developers specializing in Tridion capabilities isn't always easy. And 8 years ago it was nearly impossible, involving finding European developer support shops in order to get the assistance needed. This is changing though and American developer firms are becoming more widely available.
We had and still have a fantastic experience using Adobe CQ. Lots of flexibility, great integration with other Adobe products we already use and a powerful technology make it a great fit for our corporate environment. Also as the community grows, it makes it easier to network with other developers and users to get new ideas on how to continue to get the best out of the software.
I am giving this a semi-high rating because we have already got Tridion up and running and we are still in the process of moving the sites over to Tridion. It is unlikely we will be moving things to a new CMS AGAIN in the near future as the cost to get Tridion was high.
Considering I'm completely self-taught on Adobe Experience Manager, I have to rate usability quite high since plenty of aspects were easy to figure out on my own. With its cloud-based platform, access from anywhere it super great for overall usability. Edits can also be made pretty quick and easy, which is another great feature.
The editor user interface is very user friendly and in-site editing makes simple updates fast and easy. The extensibility of Tridion is a big plus and the ability to add our own options into the default Tridion interface helps us integrate with external systems. Finally, the user permissions and security system helps us deploy it within our large organization.
Being part of Adobe Suite means you are already notified when the tool has any outages. However, I have never faced unplanned outages. Whenever you face any issue with the site, it is clearly stated if there were any planned outages and how quickly you will be back to normal. So, I will say that even the outages are planned and managed in a great way like their other services.
With respect to performance, Adobe experience manager is one of the best in the CMS space. We didn't observe frequent slowness on platform, however the systems which are accessing experience manager should be of good specifications without which slowness would be observed. Adobe experience manager works well in integration with other solutions, unless the destination application is designed to trigger frequent calls to AEM.
Adobe Experience Manager, in all its capacity, is a great alternative to any other CMS you are using. It helps in rapid development and makes life easier for maintaining the website for multi-language sites. Technical know-how is eliminated at content authoring. Better documentation in terms of live examples with videos would be appreciated.
Depending on your individual needs, It is really quite simple to create an authoring experience for a website that looks really good. I have been part of many implementations and many teams and have seen many projects that were super successful and others that were not implemented well. AEM has room for a lot of flexibility in the implementation process compared to other CMS like SharePoint
SSO is one fits all, so we don't have to have a separate SSO for each application of Adobe The integration with Analytics works perfectly and bring directly value really quickly Target remains more complicated to set up, but can also bring a lot of value once integrated with the rest of the Adobe platform The fact that the solution is Cloud services is also a big advantage for maintenance
Interwoven teamsites, Documentum, Adobe - teamsites and documentum are old and limited. Adobe rocks but I like where I am and Tridion does a lot of the same things. No need to reinvent the wheel or move to a lateral product.