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
Drupal
Score 6.7 out of 10
N/A
Drupal is a free, open-source content management system written in PHP that competes primarily with Joomla and Plone. The standard release of Drupal, known as Drupal core, contains basic features such as account and menu management, RSS feeds, page layout customization, and system administration.
N/A
Sitecore Digital Experience Platform
Score 8.7 out of 10
N/A
The Sitecore Experience Platform (Sitecore XP) is a digital experience platform used to build websites and create customer experiences online. The solution boasts fast content authoring, built-in personalization features, testing and other optimizations, as well as analytics and marketing features.
Flawless management of digital assets and content supporting personalized content delivery. Seamless navigation and user experience on AEM platform WYSIWYG (What You See Is What You Get) editor makes AEM stands out from the crowd which is not available in the Drupal Headless …
We have selected Adobe Experience Manager for its unified compliance-ready tool kit (e.g AI-driven personalization, RBI- compliant multilingual templates) and enterprise scalability.
Verified User
Partner
Chose Adobe Experience Manager
End to end capabilities as well as integrations with upstream and downstream systems to make work flows, easier and faster time to market
I think AEM is more robust for an enterprise-sized company. It has more security around it, and then definitely you have to have enough knowledge to be able to use it and then interact. It enables a lot of the integration with other third-party tools. So we use Salesforce and …
Adobe Experience Manager is an enterprise digital marketing platform that has an edge over other CMS platforms in multiple ways 1. Easy content authoring 2. Pre-defined authoring and publishing workflows 3. In-built multi-site authoring 4. Support for multi-lingual websites.
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 …
The main reason why we acquired Adobe Experience Manager with a lot of peace of mind is that it has very good recommendations from other people, we took the exhaustive task of investigating very well its operation, advantages and disadvantages and from all the descriptions we …
It really comes down to how much money you are willing to spend (Adobe is more) and the skill set of your developers (Sitecore is .NET vs. Adobe is Java).
Ease of setup and use makes Adobe Experience Manager one of the best content management systems that is available in the market. The fact that the underlying frameworks are largely open source, helps in facilitating third party integrations more seamlessly. The default options …
Of all the different CMS tools I have used and implemented, Adobe Experience Manager (CQ) is the most robust and feature-full. The reliance on Apache Technologies was a real smart decision for CQ's architecture which ensured future scalability, testability and extensibility.
Much simpler than SharePoint and by far much easier to develop as well. Getting a unique look and feel into a SharePoint is like pulling teeth compared to Adobe Experience Manager. I also felt that the authoring experience was simpler and easier in Adobe Experience Manager as …
Drupal is the king of enterprise opensource content management systems. It is the most robust and comes from the most forward thinking community. Drupal 8 is designed for the next evolution in web design and development. WordPress and Joomla! are stuck in the web 2.0 revolution …
We evaluated many CMS systems and Drupal came out on top because of its flexibility and that its open source. We didn't always know everything we would be asked to build and Drupal allowed us to be nimble enough to do what needed to get done. We also liked that it handled …
Drupal is not as powerful, extensible, or easy to use as Sitecore, but it is free, whereas Sitecore can be quite expensive. It offers a similar service as Umbraco, but from a PHP codebase. For clients that need a free CMS system, it is the clear choice for those with a PHP …
Drupal is simply the most robust open source content management solution available. It also does a great job stacking up against other licensed solutions like sitecore or CQ5.
The decision to select Sitecore was not ultimately mine, but the fact that we were able to leverage in-house Microsoft .Net (C#) experience on a platform that had a library of extensions, but also allowed us to customize and keep private our confidential IP has been a big help. …
Really the only comparable product to Sitecore DXP is Adobe Experience Manager. Both are very well established and robust content management platforms. Products like Contentful and Contentstack are very lightweight and do not have as many built-in features like DXP, so it is …
Of all the competitors listed above, Sitecore owned, by far, the best combination of power, easy-of-use, and extensibility. It easily outperformed the other paid-for CMS systems. Its power is especially noticeable in its ability to handle very complex workflows, security …
Sitecore provides an incredible amount of capabilities, endless customization and seamless integration. Each customer situation is unique, but in general, these are the driving forces behind the selection.
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.
If you want to set up a basic Not For Profit (NFP) Membership system and content base, Word Press is easier than Drupal. However, if you have specific needs that require a fair bit of customisation then Drupal is the best CRM available. If the webmaster is confident with PHP and SQL, Drupal allows a lot of creativity.
Sitecore offers Content Hub with Product Content Management and Content Management Platform. The Digital Experience Platform and Content Hub can both host structured content and publish the finalized version to Experience Edge. Both platforms offer different ways to manage content. During a technical and business evaluation, the evaluation panel must understand the difference between a Content Modelling focused approach, or a layout management focused approach. Sitecore Digital Experience Platform is also best not to be used to host many files and images in the Media Library. That responsibility should be offloaded to a digital asset management company like Sitecore Content Hub DAM. The technology evaluation panel must also understand how to work with a Headless CMS, where the HEAD needs to be hosted, and the costs associated with the HEAD. Composable DXP is fantastic, but everyone must understand the various cost components. Marketers and the data team will need to go into the CDP and Personalize the platform with an excellent understanding of how a composable "installation" works. All the Martech vendors have similar challenges that data and development teams need to work through with a full experience. Any CDP/analytics platform will, at some stage, require further data enrichment from other sources. Understanding the Sitecore Search features and limitations is also essential.
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.
Comprehensive Solution: Sitecore offers a fully integrated suite of products that cover the full spectrum of DXP capabilities, including search, personalization experimentation and more, delivering a complete composable DXP solution for customers.
Beyond Headless: XM Cloud provides more than just headless capabilities, featuring in-built tools like authoring host, page editor, etc., enabling faster and more powerful implementations.
Focus on AI: Sitecore has now got an excellent AI offering called Stream; it looks promising; however, it would be too early to give feedback on the same.
Customization: Sitecore's backend is highly customizable, allowing for deep modifications through pipelines and patch configurations.
Can sometimes be difficult to troubleshoot bugs/issues as they arise
Sometimes difficult to set up restrictions on how components can be designed to make sure they fit in with existing content
While the integration with Adobe target works fairly well, the process can be a bit opaque and hard to understand, making it difficult to troubleshoot when issues arise
This is not an easy CMS to work with if you don't have a good understanding of website development. It isn't "plug-and-play" like Wordpress or Shopify.
Over time, doing major updates to the system can be taxing, especially if you aren't well-versed enough in doing system updates in line with your "child" theme and code.
The CMS can become somewhat cumbersome with server resources if not carefully optimized while you build and customize it to your liking.
Experience Editor is a little old fashioned and sometimes slow to use.
Bulk operations in the Content Editor
Sitecore serialization is should be part of the Content Editor to provide visual reference for items which are serialized and will be overwritten by future deployments similar to what Unicorn does so well
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.
The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.
Sitecore has proven that it can deliver on its promise of a robust, reliable enterprise CMS solution with plenty of features. Also, they keep updating it with more and better features. Now that we are highly trained on it we have started on getting the most out of it and we plan to keep doing more of that in the future.
It depends if it is from an administrator point of view or from a business content author point of view. I think from business author point of view the solution is good and with the GEN AI capabilities coming it is doing better and better, however from an administration point of view there are still a lot of improvements to ease the maintenance of user access management and as well as the integration configuration aspect.
As a team, we found Drupal to be highly customizable and flexible, allowing our development team to go to great lengths to develop desired functionalities. It can be used as a solution for all types of web projects. It comes with a robust admin interface that provides greater flexibility once the user gets acquainted with the system.
Once you learn how to use the platform and can put a solid strategy in place to manage it long-term, it becomes a lot easier to use. The tricky part is working with resources who are familiar with the platform to navigate some of the common implementation and configuration pitfalls. Although Sitecore has worked very hard to overcome some of these from their earlier product versions by creating wizards and improving their support documentation, at the end of the day it is still a very complex and powerful system that needs to be implemented carefully in order to foster the best possible user experience for authors. So it could be rated very usable or not usable at all based on how much planning took place and the quality of the implementation.
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.
Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).
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.
Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.
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.
As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.
1. Customized software development & maintenance. 2. Technology Consulting - Consulting-based services for technology solutions data engineering or cloud solutions. 3. Used for tapping into multiple data sources such as CRM and marketing automation systems and, creating automated data extracts with a high-end visual representation of data. 4. Implemented for scheduling an existing report to automatically refresh and be delivered to specific users at a specific regular interval.
I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.
The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.
Sitecore captures and remembers every single interaction your customers and prospects have in any part of the system, allowing you to build comprehensive, ever-learning profiles of each individual. From email marketing, to social media, to online shopping, Sitecore remembers where each interaction left off so you can automatically continue the conversation. Sitecore helps you manage your content for each and every experience your customers enjoy. Customize what content you want and the system will take care of how it's displayed.
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
Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%
Make sure you work with a partner that can help you take advantage of the entire platform. Specifically we see a lot of customers not taking advantage of Sitecore DMS and thus missing a huge opportunity. Sitecore is a platform that is meant to be constantly optimized and improved upon.
Overall, I prefer AEM as an enterprise site management tool. It allows levels of access control and delegation, while leaving the server management and updates to a specialized team. I do miss the flexibility of being able to search and replace that I have in a WordPress site, and I miss the ability to have one file for redirects like I had in percussion
Drupal can be more complex to learn, but it offers a much wider range of applications. Drupal’s front and backend can be customized from design to functionality to allow for a wide range of uses. If someone wants to create something more complex than a simple site or blog, Drupal can be an amazing asset to have at hand.
Sitefinity is improving but at the time of decision making it had nothing that could compare with the A/B testing and personalisation features that Sitecore offers. This was a key differentiator and ultimately ensured Sitecore was purchased. WordPress isn't really comparable and isn't within our technology stack, which is mostly Microsoft.
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.
Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.
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.
ROI depends on what features the customer wants to leverage from Sitecore. Sitecore is not just a CMS. It's CEP platform which comes with Analytics, Personalization, A/B Testing, and Email for marketers modules etc., out of the box.
Based on my experience some of the customers lean towards third party services. This is primarily due to lack of the understanding of these features. If a customer leverages these out of the box features ROI will be high. It depends on how much is being [sent] to third parties services.
Sitecore has very good accelerators in the market. These accelerators allows you to create response sites very quickly. If a simple campaign site takes 50K to build the site may save at least 50% of that cost. Examples of site accelerators are Brainjocks, Keystone, Cognifide etc.