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
Contentful
Score 7.5 out of 10
N/A
Contentful is a cloud based CMS solution that provides the ability to manage content across multiple platforms.The editing interface allows for managing content interactively and provides developers the ability to deliver the content with the programming language and template framework of their choice.
$0
PowerDMS by NEOGOV
Score 7.0 out of 10
N/A
PowerDMS by NEOGOV is a software platform designed to recruit, train, equip, and protect employees across their careers, used for policy management, community engagement, and staff scheduling.
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.
First of all, I would say the technological advancement it has. AEM consists of a comprehensive web content management system, including more marketing-friendly site templates, easy-to-use developer tools, and AI-powered content generation tools for [a] better customer …
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.
It's a great all rounder for content projects. It's easy in the basics and powerful in the complex, data heavy scenarios. Extending the platform is straightforward and the SDK gives you everything you need. If you have many many varying content types , it gets expensive and perhaps not the best choice .
This software is very well suited for law enforcement agencies of all sizes from 5 to 5000 officers. There is a mobile app that allows officers to quickly and easily search while out in the field or on a call. They can quickly review a policy, locate a form, pull up a map and much more using either the mobile app or the desktop application.
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.
Policy management- [Users] sign for, and can take [tests] to prove understanding of policy right in the application. As [the] policy is updated, old versions are retained, so that we not only know what a policy contains, we can track changes and provide information on what a policy was at any given time in the past.
Training- Users receive notifications when training is due and are guided to complete the training. If the training requires recertification, PowerDMS can be configured to alert the user that re-training is needed, without a supervisor needing to keep track. All documents used in training, including presentations and videos, can be contained in the PowerDMS course, so we can prove not only that an employee was trained, but exactly what curriculum was use din any given training.
Accreditation Assessment- [Our] accreditation standards manual is uploaded directly into PowerDMS. Proofs are accomplished using the actual policy and procedure, as well as the documents created during the workday. There is absolutely no duplication of effort.
Communications accountability- Email [can] be read and forgotten. With PowerDMS, a document can be distributed for user signatures, insuring that the user took affirmative action to read and understand the document.
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.
Contentful uses "references" to allow you to build very modular content. If I have a "slider" content type, I can create a "slide" content type which references a "button" content type, and so forth. This works well, but I occasionally wish there was a better solution for one-off content, like a settings page. Currently, this is done for creating an entire content type called "settings" with a single entry. Not a big deal, but not ideal, either.
There are a few quirks with GatsbyJS integration, etc, but these issues are being fixed and improved upon very quickly.
A minor gripe, but Contentful does not have a way to organize fields within an entry. Entries with many fields are somewhat tiresome to scroll through.
The Workflow process in PowerDMS is not as easy to grasp as some of the other concepts and requires a little more explaination, especially for non-administrative background users.
Users are unable to view the steps in a Workflow template in order to determine which Workflow would work best for their needs when routing documents.
It would be great to have multiple message options for past due inbox notifications in addition to the options for past due tasks to encourage users to go to their inbox to review their messages.
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 have had nothing but positive experiences with PowerDMS from day one. If we ever run into a situation we are unsure of, PowerDMS support has ALWAYS been able to answer us basically immediately. I really love that they are constantly seeking to improve and expand.
Adobe Experience Manager overall is fairly easy to use and caters to a wide range of users when it comes to their technical abilities. It has the flexibility to enable UI/UX designers to pop in and easily design new content with drop in components. It also has sufficient capabilities for those who are more technically inclined and want to dig more into custom code or solutions
It is a very easy to use and configure application. I find that it is on the user to manage the content after the models have been created, yet I still do not encounter issues finding or creating new components for our site. It is easy to set up and easy to navigate.
There is a learning curve as with any software system and I have found those users who consistently use the system more have a much higher success rate than those who only log in to sign off on documents. Now that most users have been in the system for over 2 years I consistently hear how much easier the processes are than they originally thought they would be
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.
We use PowerDMS in the cloud so our performance might be different from other users who use on-premise. The program has always been up with very minimal downtime and always seems responsive and snappy when navigating the UI and searching documents. We don't currently have any integrations with other software.
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.
I just wish we had some in-state support. The contacts I have had with customer support have been great. Awesome communication, problem-solving, and support. I have talked to and met Stephanie Williams (CSA for Power DMS) at the most recent Entrust conference. She was professional and devoted time to addressing our agency needs.
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
Implementation of PowerDMS was near seamless. The product was able to input existing policies and procedures within a few hours, which helped to lay the foundation for future use. Having PowerDMS on-boarding readily available was also a huge benefit.
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
Easy to use and much more organized as a single platform versus multi. The layout is clean and easy to read and we don’t have to worry about certain users safe guarding data or content then losing it when they leave the company. It’s a one stop shop for imagery
PowerDMS is a lot different than Linkedin Learnings. In PowerDMS you have to create your own courses versus in Linkedin Learnings they provide extensive content on a wide variety of subject matter. Linkedin Learnings is what we have used in our organization for Bias Training and Ethics Training. PowerDMS is the repository for documents and Trainings, so the systems work very differently
Instead of being directly involved in the tool purchase, I am involved in analysis or what we can use to maximize the tool. Small organizations may find it expensive. However, if the team or organization focuses more on your ROI or the features you will get, then it will definitely be worth it. Pricing is based on a number of factors, including team size or the use of the tool. The user can select the pricing option that best fits their needs based on the number of form submissions they make or the number of pages they wish to publish on their global/multisite sites.
The professional services team within adobe is one of the best in terms of technical and solutioning knowledge. However, considering the billing charges of adobe professional services team, it is always recommended to involve them during platform initial setup or when a complex solution is to be built with platform customizations.
too soon to tell on increased conversion rates based on external marketing factors in play but having increased visibility into customer engagement trends will most likely lead to improvement of our conversion rates.
There have been productivity gains from the perspective of actually migrating all of our externally managed sites to the same in-house Adobe Experience Manager platform and then being able to utilize those universal components.
Contentful has saved us valuable development time that was previously spent doing deploys for minor content updates.
Contentful has helped us maintain consistent documentation, reducing time needed to review for consistency.
Can't say we've really experienced any negative ROI impacts from using Contentful, but we've run into some limitations in adding too many content models and the next pricing tier is substantially more expensive.
Created efficient processes for approving document revision
Migrated what originally was a paper system to electronic
Accessible for any employee by logging in, employees do not have to seek out policy and procedure binders, and updated documents can be automatically sent to inboxes when updated.
