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
Concrete CMS
Score 9.2 out of 10
N/A
Concrete CMS (formerly Concrete5) is a free and open source, PHP built content management system for content on the web and also for intranets. It is optimized to support the creation of online magazines and newspapers.
N/A
Drupal
Score 7.0 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.
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 …
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 …
I think AEM is specific to the client's needs and is not necessarily comparable to all other platforms. However, when compared feature to feature I think AEM many times is a leader in the industry. While WordPress has progressed in the WYSIWYG interface it is not there still …
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 …
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 …
Concrete CMS
Verified User
Professional
Chose Concrete CMS
We did not select Concrete5 as we inherited it. If selecting again, we would use WordPress, Drupal or another CMS to meet our needs.
I believe WordPress and Drupal to be superior products. But Concrete5 holds its own against them. I selected Concrete5 for real estate and marketing firms for the ease of use and updating. The drop and drag editor is hard to beat.
Concrete5 is easier to use than Drupal or Joomla, and beats them in terms of features. WordPress gives Concrete5 a run for its money as far as extension and theme availability, as well as user base and support availability. But Concrete5 beats WordPress hands down with features …
Concrete5 is much easier to use than Drupal and has more functionality set up out of the box with just enough add-ons to get the job done. I have used both WordPress and Drupal, and this sits between them. Concrete5 is not quite as easy as WordPress but much easier than Drupal …
My initial test was to time how long it took to create a very basic site from scratch with no prior knowledge. Concrete CMS won decisively. Over time, I've worked on projects that use other systems, and the challenges I encounter always affirm my choice to stay with Concrete …
Concrete5 compares very well to other content management systems such as Wordpress, Drupal, Expression Engine and Joomla. Concrete5 seems to have the easiest learning curve from development standpoint and much easier to use for the end user.
Concrete5 was far easier to use than alternatives--which is very important when handling support issues for clients. As a developer, the architecture makes it easier to extend the core functions elegantly without overwriting core code. Although a few other CMS platforms have …
If your web team is tired of dealing with CMS training issues, you need to consider Concrete5. If your technical team and host are tired of dealing with website security issues, you need to consider Concrete5. If you're pulling your hair out over frequent update patches …
Concrete5 is by far the easiest for the end user. The user who edits the website can do so with very little training and not just with regards to the content. New pages and functions are easy to create and install. SEOand contact form functions are built in as standard.
I adopted Concrete5 after an end-user trial. With a variety of well known and lesser known CMS (including the above) in their fresh install state, I asked a group of users to register an account and then add a page with some text and an image on it. Concrete5 came out top by a …
Concrete5 is superior in most usecases to all other commonly used CMS platforms. The only thing where Joomla is outpreforming it is bulk editing. WordPress needs at least 20 plugins to do what Concrete5 does out of the box.
Programming C5 templates and custom views is a dream, …
Concrete5's UI is a bit more dated compared to WordPress, and the ecosystem for plugins is smaller. But out of the box, Concrete5 does more with its clean code than WordPress does. WordPress's UI and large plugin/community around it is its biggest strength as a product, not the …
Concrete5 is probably the most user friendly for clients. I selected Concrete5 mostly because I found out about it and didn't really believe its capabilities and had to try it out. It pretty much is what a non-tech savvy person would want in a CMS for content management.
WordPress has a very confusing unintuitive admin section for the user to use while Concrete5 was much more intuitive and effective for people not use to working with a CMS solution. Components are selectable by areas you create in the page template and allows a user to quickly …
I find significant advantages over these other products. As a designer, I appreciate not having to design within a rigid structure, or shoehorn a design into particular format. As a developer, the security, useability and developer support from the core Concrete5 developers and …
Personally I feel that WordPress is overly complicated and not as efficient as Concrete5. For example, Wordpress is a blogging platform hacked into a CMS, where Concrete5 is almost like a foundation with a CMS component. Concrete5 is very similar to Drupal just without the …
Concrete5 absolutely shines in comparison. While there are areas where one system may perform a specific task better than Concrete5, when it comes to the whole package Concrete5 can't be beat.
Concrete5 is the least contrived CMS I've ever run across. It's easily the quickest to theme and get up and running whereas Wordpress or Drupal could take months to get a Theme made Concrete5 can get one in a week. There's no reason to re-invent the wheel with loops and the …
WordPress - Getting better as WCMS but still primarily for blogging sites. Joomla - Very robust system with large community however can be complex for authoring and site management. Adobe CQ (AEM) - Enterprise class system with large price tag.
Concrete5 is my first choice if you compare it with smaller solutions like Wordpress,Joomla or Drupal because of its ease to use and flexibility. However, solutions for bigger projects like Sitecore or Umbraco are in their own league. They perform where Concrete5 is not very …
I was overall pleased with the UI and the clarity of the development process. The upgrade process is a breeze, the CMS is light, powerful, and the community forum is great. Job is simply done with great results.
I tried WordPress back when it was @ 2.5 or so. It was very blog oriented. Have used CMS Made Simple. I liked it but it got to be outdated. Drupal has a higher learning curve and would take a lo more training and time to implement.
I often use Perch for smaller site builds because it is simpler, lighter, and faster than Concrete5. Perch has become more and more capable and along the way is taking over some of the medium-size sites I build. WordPress was designed for blogs, and its ubiquity has made it a …
Comparing Concrete5 to Drupal and Joomla are easy. Joomla has a steep learning curve, and Concrete5 does not, this means if I have to teach a client to use a CMS, Concrete5 will be a much smoother process. Drupal also tends to have a bit of a learning curve, but beyond that …
Years ago when I personally was early on in my web development learning path, I tried to learn and use Drupal. Its complexity and difficulty proved to be too much, at least for me personally at that point in time. Finding and using Concrete5 was a real nice experience after …
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 …
Director of UX development, social media and SEO/SEM
Chose Drupal
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 has the best community and support system of any other CMS that I have used. Drupal is more flexible from A-Z including installation, building and customizing the CMS. The only other (free) CMS that is close, in my opinion, is Dot Net Nuke.
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.
Suitable if you are part of small to large scale companies or web-houses which have PHP developers and frontend engineers with some budgets. [Also suitable if] you or your client want to build a website that requires some features or uniqueness [and needs] some customization and freedom. Additionally suitable if you want this project to be DevOps based project or if the project requires very tight security and is inside of a closed network.
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.
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.
As a dev, the Page object (coupled with page attributes, nav menus and page lists) makes structuring a website or web app a dream. The separation of page templates from page types also helps, the former being about layout while the latter is more conceptual.
As an admin, you pretty much have as much control as the developers of the site decide to give you.
The versioning system allows admins to roll changes back and work on changes before publishing them.
The permissions system is exceptionally powerful, allowing roles and/or individual users to be included or excluded from each permission.
The attributes system allows pages, files and users to be given custom properties of various types (e.g. text, image, colour).
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.
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.
Its a very solid, very consistent package that never lets you down or leaves you frustrated. It gets a 10/10 because its so much better than anything else currently available. It also gets a 10/10 because, even if not compared to others, it does not leave you wanting for features or functionality. It is an excellent piece of software that will answer almost every CMS need.
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.
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.
I have used it on over 30 projects in the past 3 years and it's still a pleasure to work in. Doesn't always have all the answers, no CMS does, but I still find it very easy to use from prototyping to working to final project. Also there is no problem working on a localhost then moving to a live site, like there is with WordPress. It's my go to app in my CMS quiver.
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.
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.
Since it's not tied to a central server (other than for authorizing updates and assigning licenses to specific sites), it's available pretty much 100% of the time.
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.
The site works extremely well, the front end flies, searches and form submissions are very fast indeed. The reason its a 9 not a ten? the back end can be a little slow at times, and this is unfair, because for the backend to be so amazing, it has to do a huge amount of work!
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.
Concrete5 is open-source and has an incredibly strong, polite, and supportive community. You can get an answer to nearly anything you want to do with Concrete5 by googling for it, searching the Concrete5 discussion forums or stack overflow, or posting your question to the forum. Members are very courteous and do not look down on those with less knowledge. And answers are always quick, informative, and supportive.
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.
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.
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
Build off of an existing theme to speed up the creation of custom designed themed. Bootstrap is a good one but there are many others that are probably much simpler to build from than the Bootstrap one was. Make sure you host on a Unix/Linux server so you don't have to install PHP or MySQL separately. It's just smoother on those platforms.
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%
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
WordPress at the time was riddled with security breaches in the news and while Concrete5 was smaller (and therefore a smaller attack vector), after eleven years of use, Concrete5 has only had one published incident with an add-on that resolved within hours and with excellent communication. You can talk to the CEO and the CTO (or the rest of the team). They are very engaged and you're working with a small company of people who care, not a call-center with people just waiting to go home.
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.
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.
Concrete5 is the customer-facing side of our business. It's where we host the site that potential customers see before they choose to purchase and create an account with us. We are able to keep that site clean, user-friendly, and with a lot of available options for customers to interact with thanks to Concrete5
The ability to have multiple users and admins for the site means that we all members of our team can go in and create new content, fix or troubleshoot issues, and edit the site easily.
Our CRM isn't directly integrated with Concrete5, so when customers go to make a purchase with us, they have to leave our Concrete5 site.