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
RWS Tridion Sites
Score 9.0 out of 10
N/A
RWS Tridion Sites provides web content management capabilities, connecting people, processes, and information across teams, brands, and markets, to deliver impactful online experiences globally. RWS Tridion Sites' DPX platform enables the use of either traditional or headless publishing. It includes advanced features such as automated personalization, multilingual capabilities and Semantic AI. The BluePrinting® technology at the core of RWS Tridion Sites simplifies reuse and…
Drupal excels at allowing seasoned programmers to really get creative with marketing initiatives in terms of working with a theme and the core code. That being said, it is definitely much more challenging for average developers and front-end builders to use, especially at …
Drupal has some advantages and disadvantages when stacked up against Wordpress,, including that Wordpress is easier to user for beginners and requires less training to get started. I noticed that while using Drupal, more help and assistance was needed from developers to make …
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, …
I inherited Drupal from a developer who made the website for our nonprofit many years ago. It was increasingly obvious that it wasn't a fit for our organization, which has multiple staff and volunteers who need to edit or update the website but don't have coding experience. Wix …
Drupal requires less to no coding abilities to spin up sites. Even if someone is preparing to develop sites that require technical know how then Drupal provides role based systems to seperate developers from content writers. Drupal 8 and 9 now have a vast array of plugins. Now …
WordPress for sure has a bigger community, a lot of paid extensions which sometimes is easier to purchase and get started, a lot of pre-designed templates to get you going, but nowadays with the scale of the projects we've been working with, and the need for custom-tailored …
We use both, for different projects (Joomla and Drupal). Drupal proved to be more robust, more secure and more integrable with PHP applications. Drupal requires a more senior technical team but allows for more complex activities. It's great if you have a medium to a large …
We first had a WordPress-based website, that evolved to a custom third-party developed content management system. In both cases, that involved additional costs for any change request, any security or any scalability need. WordPress didn't meet enterprise requirements. That also …
Drupal is community-backed making it more accessible and growing at a faster rate than Sitefinity which is a proprietary product built on .NET. Drupal is PHP-based using some but not all Symphony codebase. Updates for Drupal are frequent and so are feature adds.
Drupal is far more usable and stable than Joomla!, and the developer community support is significantly stronger. While Drupal is often compared to WordPress, they are fundamentally different platforms, and in most projects, it's very clear when the requirements are beyond what …
We have used many content management systems — WordPress, Wix, Squarespace, ExpressionEngine, and more. Drupal is more powerful and flexible than most.
We did a comparison of Drupal against Joomla, WordPress, and Ingeniux. We found that its multiple themes available for web pages, user management, comment management, and form generation stands apart from its competitors.
I've used Wordpress sparingly when helping a client with an existing website. I find it much less powerful and robust, and frankly confusing. The way Wordpress websites are set up in the backend doesn't make sense to me after getting used to how Drupal is set up. They're …
Drupal is really the only well-supported open-source CMS that is designed for large, data-rich websites. There just really weren't any good alternatives. There are plenty of CMSs that excel at small to medium-sized websites. But for a large website with lots of structured data, …
Although Drupal is not the most used, it has great performance and is more used in professional projects. It allows us to expand without starting from scratch.
Security-wise and traffic-wise Drupal is built to handle a lot. While the other platforms mentioned ( mainly Wordpress ) are great and have a large community, I would only use Drupal for an Enterprise level platform to build a website on. I first learned about Drupal about 10 …
Drupal supports lots of devices like Mac, Windows, Linux etc. easily, and it is an open source product so there's no cost required. Lots of other products require purchasing, costing a high amount. The support system of Drupal is also good in comparison to other products. The …
Drupal is certainly a more complex animal, comparatively. But its power lies in its flexibility, extensibility, and stability. And the API is fantastic. There's really nothing else like it.
I selected Drupal because of the simplicity upon going live. "Simple" is not the word I would use prior to the site going live though. I have used Jumla (which I believe was part of Drupal as one CMS about 12 or 15 years ago). Jumla is almost identical in capabilities to …
In my mind, Drupal and WordPress are the top open source CMSes, and I rarely recommend not going with an open source CMS. WordPress can be great, especially for single developers, but I find that the code structure and extensibility of Drupal makes it superior for many use …
I've used Squarespace and Wordpress for other businesses, and Drupal was honestly selected due to cost. It does a good job of scaling across our organization - and many units have benefited from having a space to provide content. Squarespace is more modern, and Wordpress may …
Drupal has strong role-based permissions for users, powerful content blocks for editing, and granular customizing options in their views. For a company or organization requiring a lot of customization, Drupal can be a really powerful tool. However, Drupal does require …
Interwoven teamsites, Documentum, Adobe - teamsites and documentum are old and limited. Adobe rocks but I like where I am and Tridion does a lot of the same things. No need to reinvent the wheel or move to a lateral product.
It is a nuclear missile compared to the other handguns and knives on the market today. But it also requires nuclear technicians and expertise that a handgun doesn't require. Do you need to decimate your competition and you have the investment capabilities necessary to put a …
Tridion is much better for multi-site installations, though Sitecore is a bit easier for content editors to know content types are being used based on visual icon indicators. We've had content editors pick the wrong templates by accident, but Sitecore's visual indicator …
Adobe CQ is SDL Tridion main competitor. Sitecore is designed for smaller companys. Adobe CQ is all java and thus has limitations. Sitecore is also all .net and has limitations. Both use a dynamic model and everything is compiled at runtime. SDL Tridion can be published in a …
Tridion again seemed to be more enterprise level then EpiServer, EpiServer allowed for faster ramp up time of a intuitive .NET framework, but Tridion seemed to have more tools and overall functionality once the CMS was customized towards the needs of the customer.
Verified User
Anonymous
Chose RWS Tridion Sites
I did not play a role in selecting this product so I can't say how it stacked up. I do know that Tridion is an improvement over the last CMS.
Verified User
Anonymous
Chose RWS Tridion Sites
I feel that SDL Tridion's User Interface is to difficult for content authors to understand. I worked with a client that used Tridion for years and she still would get lost in the UI and had to ask questions. There was close to 30% of continual time spent on the project simply …
Verified User
Anonymous
Chose RWS Tridion Sites
SDL Tridion is far superior to CommonSpot. It is much more user friendly and increases efficiency.
Verified User
Anonymous
Chose RWS Tridion Sites
I believe the biggest selling factor for SDL was its customer service and it ability to be responsive. We knew that it was a company that was going to be around for a long time and would continue to provide the support that we would need in the long term.
Tridion's strength is really hosting multiple websites across development, test stage and production.
Verified User
Anonymous
Chose RWS Tridion Sites
The decision to purchase Tridion was made at a corporate level removed from the technical teams. Against our previous open source solution, this has been wildly expensive, impossible to find experienced developers for, and has required completely retooling our organization.
Verified User
Anonymous
Chose RWS Tridion Sites
SDL has a better API and also handles high server load much better. Also, the built-in integrations for translations are more suited for performing lots of translations for many sites. However, Umbraco, like Tridion, has a great community and finding solutions with both …
Verified User
Anonymous
Chose RWS Tridion Sites
We didn't chose WordPress because can't handle the traffic we generate. Sitecore is what we are currently looking at and it looks like a much better alternative to Tridion.
Adobe does a great job in managing sites. Its user interface for authors is intuitive and leaps and bounds better than SDL Tridions new 2013 UI. The ease of install and management makes Adobe CQ a much better product. However, Adobe CQ (AEM) has limitations. It cannot scale as …
Features
Drupal
RWS Tridion Sites
Security
Comparison of Security features of Product A and Product B
Drupal
2.0
Ratings
120% below category average
RWS Tridion Sites
9.0
Ratings
11% above category average
Role-based user permissions
2.00 Ratings
9.00 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Drupal
7.7
Ratings
1% above category average
RWS Tridion Sites
9.1
Ratings
18% above category average
API
9.30 Ratings
8.30 Ratings
Internationalization / multi-language
6.00 Ratings
10.00 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Drupal
5.3
Ratings
37% below category average
RWS Tridion Sites
8.5
Ratings
10% above category average
WYSIWYG editor
1.00 Ratings
8.00 Ratings
Code quality / cleanliness
9.30 Ratings
8.00 Ratings
Admin section
3.00 Ratings
9.00 Ratings
Page templates
4.00 Ratings
9.00 Ratings
Library of website themes
3.00 Ratings
8.20 Ratings
Mobile optimization / responsive design
10.00 Ratings
9.00 Ratings
Publishing workflow
9.30 Ratings
9.00 Ratings
Form generator
3.00 Ratings
8.30 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
Drupal
5.0
Ratings
38% below category average
RWS Tridion Sites
7.6
Ratings
3% above category average
Content taxonomy
10.00 Ratings
9.00 Ratings
SEO support
1.00 Ratings
9.00 Ratings
Bulk management
10.00 Ratings
9.00 Ratings
Availability / breadth of extensions
2.00 Ratings
8.30 Ratings
Community / comment management
2.00 Ratings
3.00 Ratings
Best Alternatives
Drupal
RWS Tridion Sites
Small Businesses
ManageWP
Score 10.0 out of 10
ManageWP
Score 10.0 out of 10
Medium-sized Companies
RWS Tridion Sites
Score 9.0 out of 10
Bloomreach - The Agentic Platform for Personalization
We developed a corporate website using Drupal, which features a large number of static pages and several dynamic functions, including a contact us form, location finder, and job posting. We utilized Drupal with some customization to achieve the desired functionalities. We have also worked on e-commerce sites using Drupal, and there is a scope for improvements, specifically in cataloging.
SDL Tridion works well for organizations with a large website with a lot of content to continuously create and manage. The use of page templates and component presentations makes creating new pages fairly straightforward. It can be a little cumbersome when it comes to trying to "break from the norm" and build web pages that are outside of the template-driven format; however, there are ways around this to create pages that break away from the normal page-template format of the website. In this regard, SDL Tridion can be pretty flexible, allowing us to create a lot of custom functionality to keep up with constantly changing web trends.
Content Types... these are amazing. Whereas a more simplistic CMS like Wordpress will basically allow you to make posts and build pages, Drupal 8 gives you the ability to define different types of content that behave differently, and are served up differently in different areas of the website.
Extensibility... it scales, ohhhh does it scale. They've really figured out server-side caching, and it makes all the difference. Once a page has been cached, it's available instantly to all users worldwide; and when coupled with AWS, global redundancy and localization mean that no matter where you're accessing the site, it always loads fast and crisp.
Workflows... you have the ability to define very specific roles and/or user-based editorial workflows, allowing for as many touchpoints and reviews between content creation and publication as you'll require.
Security and new release notifications are a hassle as they happen too often
Allowing them to write PHP modules is a big advantage, but sometimes integrating them is a small challenge due to the version the developer is working on.
If you are hoping to orbit the planet with a CMS, Tridion is built to leave the solar system. It is a very very powerful solution built for very serious enterprise businesses in hope of robust capabilities, which could be good or bad.
Supporting business users is a hefty lift and requires significant training and regular retraining, and support.
It's a niche solution that originally came out of Europe and was largely unknown in America. But today it's growing in popularity across the United States.
Finding capable support, and developers specializing in Tridion capabilities isn't always easy. And 8 years ago it was nearly impossible, involving finding European developer support shops in order to get the assistance needed. This is changing though and American developer firms are becoming more widely available.
I really like Drupal, and besides the one major issue with not being able to update from version 6 to version 7 and I am happy to continuing using it. Hopefully as time goes on they will make it easier to upgrade or provide better tools for mid-level web designers like myself to build out new sites without the help of expensive 3rd party's.
I am giving this a semi-high rating because we have already got Tridion up and running and we are still in the process of moving the sites over to Tridion. It is unlikely we will be moving things to a new CMS AGAIN in the near future as the cost to get Tridion was high.
It has a very steep learning curve. When starting with Drupal, the functionality and setup have to be learned, which is complex in comparison to tools like WordPress. Drupal is more powerful and can create a wider range of applications, but it definitely has a learning curve. I would recommend it to anyone who wants to make a dynamic web application bigger than the scale of a WordPress blog.
The editor user interface is very user friendly and in-site editing makes simple updates fast and easy. The extensibility of Tridion is a big plus and the ability to add our own options into the default Tridion interface helps us integrate with external systems. Finally, the user permissions and security system helps us deploy it within our large organization.
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).
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.
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.
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%
Drupal's capabilities outpace WordPress by miles. Drupal is more customizable, scales better for larger companies and has advanced content types. If you own a small business or work at a startup company, I would recommend WordPress but if your firm is trying to scale and you have more than 50 employees I would recommend Drupal.
Interwoven teamsites, Documentum, Adobe - teamsites and documentum are old and limited. Adobe rocks but I like where I am and Tridion does a lot of the same things. No need to reinvent the wheel or move to a lateral product.
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.
Drupal helped us launch a creative, marketing- and product-focused website with custom coding integrations tailored to our goals.
Drupal allows us to rely on secure and consistently updated core code.
Drupal's code taxing on the server does start to get a bit heavy as you go along with customizations, so at some point, we decided to stop. We want to ensure our Google Page Score remains high, including paying close attention to page load speed.