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
Jadu CMS
Score 1.1 out of 10
N/A
Jadu is a PHP based proprietary content management system from the company of the same name. Its architecture is cross platform and runs in Windows in the .Net framework, Linux, and Solaris.
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.
Jadu is miles behind these and many other CMSs. The others are much more up to date with their code and ease of use. The ability to customize other CMSs is much easier and the code structure actually makes sense. Jadu was selected because it had a portal out of the box.
I was not part of the team that evaluated other products during the CMS search. I did however use our old CMS from Luminis, which was not a great product. It's almost not fair comparing the two products because Jadu blew it out of the water. I do know that our company …
Compared to Wordpress, Jadu provides excellent rights and access management. It can be fined tuned at any level to get the options right to just what you are looking for. It is not quite as user friendly or able to be updated as Wordpress but may be better for larger …
Features
Adobe Experience Manager
Jadu CMS
Security
Comparison of Security features of Product A and Product B
Adobe Experience Manager
8.4
Ratings
3% above category average
Jadu CMS
2.0
Ratings
122% below category average
Role-based user permissions
8.40 Ratings
2.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
Jadu CMS
6.0
Ratings
26% below category average
API
7.80 Ratings
3.00 Ratings
Internationalization / multi-language
8.10 Ratings
9.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
Jadu CMS
3.6
Ratings
74% below category average
WYSIWYG editor
7.40 Ratings
3.00 Ratings
Code quality / cleanliness
6.70 Ratings
1.00 Ratings
Admin section
7.00 Ratings
2.00 Ratings
Page templates
7.60 Ratings
8.00 Ratings
Library of website themes
7.30 Ratings
00 Ratings
Mobile optimization / responsive design
7.80 Ratings
7.00 Ratings
Publishing workflow
8.10 Ratings
1.00 Ratings
Form generator
7.60 Ratings
3.00 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.
The power of Jadu is incomparable. The set of features provided by alternative solutions like Drupal just don't stand up to Jadu. Jadu is continuously working on development and adding new tools. They even recently started releasing bi-weekly updates. We find it to be perfect for managing large websites, even if you have thousands of pages.
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.
Reliability. The LAMP-powered server/software rarely has any problems and can handle hundreds of concurrent users without issue. It was developed with scalability in mind.
Ease of Use. Our users find the backend GUI very easy to use. The layout is intuitive and follows the same format throughout the entire control panel.
Powerful. Even if it doesn't do something you would like it to out of the box, the code is well formatted and easy to customize.
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.
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.
We recently migrated to Jadu and will not be leaving any time soon. As we learn more and more about how to effectively utilize all the feature we are happier with the end result that the product provides. Our journey with Jadu is still growing but the future is looking bright.
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.
For the common user, Jadu is very easy to use and to understand. For the more complex user/administrator, there's a lot of power to be harnessed in HTML editing, creating widgets, editing styles, creating workflows, and other advanced features Jadu can work up for the customer.
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
I was not part of the team that evaluated other products during the CMS search. I did however use our old CMS from Luminis, which was not a great product. It's almost not fair comparing the two products because Jadu blew it out of the water. I do know that our company researched several companies and felt that Jadu was the company that would suit our needs the best.
Jadu have forced us to spend more time figuring out new ways around it database. We have actually turn to updated json files by hand because of how bad the system is for widget.
Jadu has cost us a lot of time just waiting for pages to load.