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.
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 think WordPress beats Drupal in every possible way. The upgrades to newer versions are almost trivial, unlike Drupal which, in our experience, requires hundreds or thousands of hours of work and untold sums of money simply to go from one version to the next! In my opinion, …
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 …
Drupal is best for complex applications. It is more suitable for large-scale applications. It is more scalable and structured than the competitor. Provides a strong API structure and a Robust headless architecture, making it perfect for progressive web apps. Highly robust, …
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 …
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 …
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 …
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 …
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 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 …
Overall, I would give my rating of Drupal a 7/10 because there is an easy user experience for those without a website background but there is some technology work required to build more website capabilities that aren't as user-friendly. Drupal is specifically well suited to update content (like changing Relationship Manager cards when there is employee turnover), post announcements (putting up a holiday banner to let our customers know the dates we will be closed over Thanksgiving, Christmas, etc., and creating a sophisticated website hierarchy of pages (for our firm, several dropdowns depending on if you're looking for personal banking, business banking, investment banking, about us, etc.).
It has excellent security features and consistent updates.
It allows for extensive customization with the integrated themes and core code, especially when you first install it. This allows our dev team to get creative with marketing initiatives.
There is a large online community of Drupal users that consistently help answer any questions and issues
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.
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.
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.
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 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.
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.