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
Ingeniux CMS
Score 9.0 out of 10
Enterprise companies (1,001+ employees)
Ingeniux is a provider of web content management and
digital experience software. The vendor states their solutions are built to enable organizations to orchestrate
the entire customer experience – from acquisition through to support and
service – on any device, application, or website. Ingeniux CMS is designed to
manage and deliver modern websites, customer support portals, online
communities, and other customer touchpoints.
The vendor further states Ingeniux builds content…
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.
Such a pathetic tool Joomla was and I still can't understand why we chose Joomla and instead of making our work easy and facilitating it had made it harder to manage for us. The dashboard of it was very perplexing and we were not even able to find features of our needs. Well …
We found the DITA capabilities to give the Ingeniux CMS an upper hand when compared with the other alternatives we evaluated in the discover phase. Though there are a plethora of CMS products and Ingeniux CMS doesn't have a free version either. But their vision for the future …
Ingeniux CMS is intended for large sites, which WordPress and Drupal can sometimes struggle with. Also, it offers far more freedom in development than Cascade Server, as you can use C# and Razor templating to build the pages, and this gives you access to advanced functionality …
IGX has came a long way and is going even further. Once they integrate more self-support for developers, integrate with other languages and provide more detailed specific training, they will stack up to the leaders, Drupal and Joomla. IGX is on their way, I know product …
Features
Adobe Experience Manager
Ingeniux CMS
Security
Comparison of Security features of Product A and Product B
Adobe Experience Manager
8.4
Ratings
3% above category average
Ingeniux CMS
9.1
Ratings
10% above category average
Role-based user permissions
8.40 Ratings
9.10 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Adobe Experience Manager
8.0
Ratings
1% below category average
Ingeniux CMS
8.2
Ratings
5% above category average
API
7.80 Ratings
8.30 Ratings
Internationalization / multi-language
8.10 Ratings
8.10 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
Ingeniux CMS
8.4
Ratings
7% above category average
WYSIWYG editor
7.40 Ratings
8.30 Ratings
Code quality / cleanliness
6.70 Ratings
8.30 Ratings
Admin section
7.00 Ratings
9.10 Ratings
Page templates
7.60 Ratings
7.40 Ratings
Library of website themes
7.30 Ratings
00 Ratings
Mobile optimization / responsive design
7.80 Ratings
8.10 Ratings
Publishing workflow
8.10 Ratings
8.30 Ratings
Form generator
7.60 Ratings
9.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.
This tool is dextrous in managing content and it is a profoundly specialized tool for the management of websites, portals and also assists in the delivery of the content and most amazingly on the time. At a reasonable price, we are enjoying many features. A few of its features need to be improved like customization and templates it provides for the mobile.
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.
Everything you will need for your website will likely need to be built from scratch. There are little to no out-of-the-box modules that come with the CMS.
There is a total absence of a user community for Ingeniux, so obtaining support from anyone other than Ingeniux themselves is non-existent.
Ingeniux is getting better at this but the documentation of their product and feature set is somewhat limited, and generally only available through in-person training sessions, which can be costly.
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.
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.
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
IGX has came a long way and is going even further. Once they integrate more self-support for developers, integrate with other languages and provide more detailed specific training, they will stack up to the leaders, Drupal and Joomla. IGX is on their way, I know product integrity is their main focus and as long as they keep that notion, their success will continue
It has been liked really well by the customers and our inhouse CMS development team could do with lesser head count because of the tool's self driven features.
Taxonomy features are not that robust and thus could be made more rich for users looking to categorize their content.