Reviews (1-25 of 72)
- Easy to use, especially compared to other open source CMS.
- Robust user community to address issues and to provide advice.
- Steep learning curve (but easy to use once you learn the system).
- Poorly written or unsupported plug-ins can be a security liability.
- Open source framework and localization.
- Multiple themes and skins for user's webpages and websites.
- Allowing them to write PHP modules is a big advantage, but at times integrating them is a slight challenge due to the version on which the developer is working.
- Security and new release notifications are a hassle as they happen too often, but are still a good thing to have.
- All my websites use it, so every website I create an manage is on one platform.
- Drupal is infinitely scalable, so as my clients' needs change, it's relatively easy to alter the current website rather than start from scratch.
- Drupal has a feature called "Views", which enables me to create custom content display modes for each client, without reinventing the wheel every time.
- Robust community for support.
- Search engine friendly.
- Extremely powerful, but easily scaled down for simple sites.
- Steep learning curve, but worth it.
- Modules with similar jobs can be confusing - This can be a pro or a con, depending on the day. Sometimes it's nice to have choices, but other times there can be 3 or 4 modules that all do 90% of what you need, but none that do it all. Drupal requires creative thinking to get various modules to work together to complete a task.
- Some modules get abandoned or don't work the way you intended.
I joke it took me nearly 2 years to get "pretty good" at Drupal. It was a commitment I made to learn it and use it for my entire business in the long term. If you need something easy and quick for right now, then don't start learning Drupal. It requires time and patience. When I started I was proficient at HTML but had never used a CMS before. If you already use other CMS's with MySQL and PHP, then you will already know how all that works. So it probably won't take you two years. Plus, I learned on Drupal 5, which was not at all designer-friendly. That was put together by coders and it showed. Today, Drupal 7 and 8 are much more user-friendly.
- Drupal is a open source product, hence we have the access to the code base. We can customize the application in the way we want.
- Drupal's ctools suite which has plugins, contents, and caches are the set of APIs supports the developers to build the application in a more customized way.
- Custom dynamic and responsive themes.
- Integration compatibility with all third-party applications.
- Scalability - tested with more than 50,000 concurrent users.
- It's not an LMS by the way, hence cannot track learning activities. It always has a dependency of integrating with any LMS. However, they have Opigno LMS within Drupal. Opigno LMS features should be improved.
- Drupal 7 and Drupal 8 have vast differences from the development perspective. The product updates should be gradually improved.
- Drupal has no compatibility with SCORM/AICC/TinCan contents. Since this is a CMS, it would be great if we can launch these eLearning contents from Drupal application without having any additional plugins/integrations
It is less appropriate for organizations looking for GxP application. This is open-source and code verification needs to be done by the architecture team in order to qualify the application for GxP.
- Drupal has a large support community. Many businesses and organizations have adopted it, and it has a large developer base, so it's likely to be around for a long time.
- Drupal is designed around the concept of structured data so that the data you put into it is reusable and can easily be referenced or accessed by other pages, or exposed through APIs to other systems.
- Drupal is well suited for building large, complex websites.
- Drupal has a steep learning curve due to its flexibility and complexity. Because it's so flexible and customizable, sometimes it's daunting trying to figure out the best way to do something.
- Some aspects of the system don't receive the support and attention they need, particularly contributed modules. It can take months (or years) for bugs to get resolved, or for new features to be developed. Many of the contributed modules are poorly supported. It's common to find modules that still haven't been migrated to the latest version of Drupal, even though it's been out for over 2 years. It's also common to discover a bug, only to find out that a patch was already submitted to fix that bug months ago, but hasn't been merged into the module yet.
- Upgrading to new versions of Drupal core can sometimes be painful and challenging, depending on how you've customized it or what modules you've enabled.
- Sometimes it's difficult to figure out how to customize a particular aspect of the system because you have to work within the framework it provides.
- Producing pages - I can start and complete a new page in Drupal in just a few minutes. It is really easy to understand and very straight forward.
- Updates - Drupal is constantly being updated with security patches, new versions and works with most new web technologies
- Cross Browser friendly
- Organization leaves a little to be desired. In the version that we are using ( 7 ) - sometimes when you remove an asset, it is hard to see if there are any other versions of the assets on different pages.
- The asset library can be a little more organized. Finding something that you uploaded can be difficult to locate if you do not know where it was originally posted.
- Is easy to install and has a very professional and clean interface.
- Has a lot of free and paid add-ons for anything you can think of. You can also design your own because there is enough documentation for that.
- Drupal is excellent for websites with a lot of content, also where you require high personalization of the permissions and details of the users.
- Has excellent options to implement your websites in different languages.
- As the new versions evolve, they become incompatible with older complements.
- For those who start, the learning curve is steep.
Being a global brand, Drupal 8 was the CMS (built by developers for developers) that provided the most extensible launchpad with localization and language support, as well as great workflow and collaboration tools for content creators.
Drupal 8 is utilized by brand ambassadors to submit content for review, internal editors to review content, race directors to manage events and venues, as well as marketers to post landing pages. It ensures consistent branding across the board.
- 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.
- This is NOT the most intuitive CMS. You really need to take the time to understand how Drupal 8 works--how content is served up--if you're going to administer a site. Whereas WordPress is very "flat" and simple, Drupal 8 is much more dynamic. You utilize Views to access your content/data and "blocks" to build out beautiful landing pages (similar to widgets in WordPress). I had to prepare a TON of documentation for the client--so many user guides.
- It is not very friendly to engineers. It probably took 3 to 4 times longer to build out a Drupal 8 site as opposed to had we built it as a static site with perhaps a WordPress back-end (though you would have required multiple WordPress instances to manage localization and other things, which is what we were replacing).
- It seems that the Drupal 8 consortium (or whatever) is trying to push the ball forward a little too far, rather than consistently maintaining a solid foundation. There were many times when my engineers had to build entirely custom modules to compensate for known bugs in Drupal 8. I have good engineers and we still lost weeks to deploy a workaround. Your organization might not be so lucky as to have an appropriate caliber of engineers, though I hope it is!
It is not great if you just need a static website, and you aren't deploying more than just a simple blog. It's not great if you don't have senior-level developers to maintain the site. If you're the type of company that needs your website to be "done" then you've come to the wrong place. A Drupal 8 website is itself a living organism that requires an ongoing commitment.
- Great templating, there's a wide variety of free and commercial ones
- Great formatting, be it with fonts or images
- Great support, specially when it comes to security
- We could use more templates
- Easier installations
- Easier ways to upgrade
- Drupal is great at managing any amount of content, and any type of content. Its flexibility and customizability are two of its greatest strengths.
- Drupal isn't just a CMS, Drupal lets you build the CMS that website editors will be using. Its backend customization and admin features are awesome and are being expanded by the community all the time.
- There are thousands of contributed modules and themes freely available. Not only is Drupal open source, but all the best modules and themes people have built are available for free as well!
- Drupal's community is big, prolific, and welcoming. Not only can you use other's community contributions, but the community is always happy to help others building their own Drupal sites or custom modules and themes for the rest of the community. If you ever get stuck, the forums or Drupal Slack are incredible resources for assistance.
- Drupal's admin side is very powerful and flexible, but it's a little bit harder to wrap one's mind around. If a customer is familiar with using a basic WordPress site, showing them the full Drupal back-end might be overwhelming and confusing at first. Luckily you can easily limit and customize the admin pages that each role sees.
- Drupal is huge and complex. Doing simple things is generally simple, but more advanced capabilities of Drupal have a higher learning curve (as can be expected). You can build a Drupal site quickly, but don't expect to build your dream site with loads of custom features in a week.
- Ready-made themes are more sparse than something like WordPress. If you're most interested in simply plugging an existing theme in and using it, you won't find as many professional-looking themes out of the box. There are some, but with Drupal, the best results are usually achieved by finding a good base theme and creating your own child theme based off of it.
On the other hand, if all you need is a small static site, and you don't need to let people edit content or control the site on the web, then Drupal might be overkill. Simply utilize a code framework or a static site generator, and you can save time and money in that case.
- Very flexible CMS (Content Management System)
- Coding is not required; however, could be useful
- Offers various levels of control
- Themes for layout and color schemes are available at reasonable prices
- Drupal does have a learning curve that requires time, especially if new to CMSs. Therefore, before starting one should be prepared by making a site on their own time prior to offering Drupal as a service.
- Documentation is lengthy but thorough. Some of this gets complicated and the community of users is not as large as some others, such as WordPress or HTML, JS, JQuery, CSS etc.
- The languages used to develop Drupal are a variety and they are multiple. Therefore, if the developer would like to use it and tweak the code, they must know a number of web programming languages.
- Managing content blocks. Drupal is very effective at providing a standard way to move content across systems.
- User management of content. Users have complete control over their spaces. It requires some training, but users can update content and create alerts without the need for a web developer.
- Overall design. Drupal looks pretty good, and provides a good structure for simple text, graphics, and links.
- Drupal is not intended for visualizations or other interactive content - this is an emerging field that could be better.
- While mobile responsive, I wouldn't call Drupal the most modern design. It's functional, but not beautiful.
- Users have control over their content, but it can be difficult to figure out how to do what you are trying to do.
- Easily create custom content types which can be used and reused in multiple views around a website.
- Granular control of websites on a per page basis.
- Allows tiered user access to support users having different access to content and administration capabilities.
- Steep learning curve
- Resource intensive
- Making a development mistake can result in hours of debugging trying to figure out what went wrong.
- It has a document repository that makes it easy to store necessary documents
- It has an image repository where users can store images
- it has the ability to have many users across the organization
- it can be a bit buggy at times
- it's not the most intuitive user experience
- while it's nice there is a photo repository, the folder structure could be formatted a bit better
- Very powerful out of the box
- Highly customizable
- Good community
- Steep learning curve
- Resource intensive
- Custom coding and templates can be difficult
- Painfully slow for features and fixes to be added to Drupal core
- Content Management
- Document and Media Management
- SEO Management
- API Integration
- Easy to manage updates
- User management
- Can be extremely difficult to ramp up to production
- If built poorly, nearly impossible to fix without a full rebuild
- Drupal core updates can be a pain in the butt.
- Drupal is an open source CMS and has a vibrant community supporting it.
- Drupal's core package offers a great out-of-box product that can easily be modified to meet any business need.
- The community dedication to contrib modules is second to none. There's a module for just about everything you could imagine, want, or need on a website.
- Excellent administrative framework and user-based interface allows for custom role creation and specific access levels based on credentials.
- Being open source, there isn't a company solely dedicated to it, which can sometimes represent challenges for bugs associated with specific modules.
- Frequent releases require upgrading to maintain support for active components.
- Flexibility and options are vast, but not necessarily intuitive for the non-experienced or web novices.
- Requires a developer.
- Drupal separates data from presentation, which is very important when you are trying to build a website. It is great at letting the back end developers focus on data structure and the front end focus on presentation.
- You can change anything you need to, or find someone who already has. Since its open source you can find a developer who can help you with a problem.
- Its been around for a long time and there are many mods that have been created to solve many problems.
- It can be daunting to a developer who has no experience with Drupal at first. There is a learning curve and it may not be for everyone.
- Because there are so many choices for mods and add-ons its hard to pick which ones are the best.
- There are not as many people with Drupal 8 experience out there even though its been over a year since its release.
I think it's less appropriate if you do not have developer support for it. Drupal isn't for the faint of heart or people who are used to something like Wordpress.
- User management was great in Drupal, we were able to create custom roles for users and assign them special permissions based on their roles.
- Customization of Drupal was a real strength, we were able to customer our site to look exactly the way we wanted and mocked up in our early brainstorming sessions. There is a vast array of add-ons available to Drupal for themes and customization that anyone can take advantage of.
- Add-on modules were the real strength of drupal, because anyone in the world could develop and offer new add-on functionality for drupal and those developers could share it with the whole drupal community and help each other advance the add-on module together.
- The community is really the best part of Drupal, there is a huge pool of developers all contributing and helping each other to advance Drupal with new features and better security all the time.
- The one thing that Drupal could improve on are the upgrade paths for updating the system between each major release of the software, when drupal moved from version 7 to version 8, most people could not do the upgrade for many months, while they waited on the add-on modules they used to be updated to work with version 8 as well. I think involving the module developers earlier on, on new major update releases could help fix this.
- Add-on modules can sometimes be slow to update or fix problems because some developers aren't that active in updating their add-on modules
- Some module developers build modules that only serve their own immediate need and are not willing to update or advance their modules to expand its functionality to serve others similar needs. Other developers are usually offered to take over and customize the project for their own needs but sometimes the documentation for existing modules can be lacking, depending on the developer.
Drupal may not be the best option for a company looking for a really simple and easy to update website with minimal functionality though, those companies may want to look into a WordPress site instead.
- Easy access and more often than not, our student's are able to navigate through our webpage and find exactly what information they need.
- Drupal Customer Service agents are extremely helpful, polite and knowledgeable.
- Direct communication on edits/updates to software to the customer (myself, etc.) rather than our IT department that doesn't always relay information.
- The Drupal core ships with a granular, field level content construction toolset. The very popular views module is now part of the core Drupal CMS and enables the creation of complex content types, it's way more than a blogging tool.
- Drupal is especially adept at integration with enterprise grade CRM and ERP systems. Because all of the data in Drupal is naturally available for mapping at the field level, there is a ready environment for connecting to restful API systems.
- Drupal scales exceptionally well with multisite and multiuser environments. Large universities can standardize on a common codebase of Drupal and then roll it out to the entire campus. Individual colleges can customize their themes and content but do not need to worry about figuring out their own module stack.
- Drupal is complex, it will take time and expertise to shape it into the tool you need it to be for your use case. WordPress can be installed and is ready to go for blogging out-of-the-box, but Drupal will need more setup up front to build out the functionality needed.
- Finding strong Drupal expertise can be challenging for companies. Although the developer community is over a million strong, there are still few companies that truly have an expert Drupal developer on staff.
- Drupal can be overkill for small websites with just a few pages or limited functionality. Many new flat file responsive tools can do well to build a basic brochure site without the overhead of a CMS like Drupal.
- Security is an ongoing struggle for all users of opensource CMS solutions. If you choose Drupal for your website, you will need a plan for security updates to ensure you are one step ahead of the hackers.
- Drupal has the most flexible and robust site building tools available for quick site-building; it is possible to have a Drupal site up and running in your local development environment within a minute and immediately get to work.
- It makes user management a breeze with the ability to easily create new user accounts and assign roles that govern access to content types and overall site management. It is therefore much easier to hand off a Drupal site to your customers and be confident they won't break it, while still finding it easy to manage their content.
- Drupal has many dependencies that can conflict with your local development environment at times and it can therefore be cumbersome to set up a Drupal site on a new machine or one that has other development environments on it that may use different PHP versions or paths to the PHP executable.
- Drupal lags behind WordPress in terms of the number of themes and modules available, due to its smaller user base.
- It has a much higher learning curve than WordPress, and to use it to the utmost you will need to pick up some degree of understanding about SQL, PHP, CSS, and Drupal components.
Drupal Scorecard Summary
Feature Scorecard Summary
What is Drupal?
Drupal is a free and 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 common to content management systems. These include a dashboard with a menu management system, RSS feeds, page layout customization and themes to aid this, and system administration tools. Drupal offers access statistics, more advanced search features, caching and feature throttling (to improve performance if needed), descriptive URLs, multiple users with controllable privileges, access control and restrictions, and workflow tools (triggers). There are over 30,000 addons or modules to expand Drupal's functionality.
Drupal Technical Details