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 Experience Platform
Score 7.0 out of 10
N/A
N/A
N/A
Pricing
Drupal
Sitecore Experience Platform
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Drupal
Sitecore Experience Platform
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Drupal
Sitecore Experience Platform
Considered Both Products
Drupal
Verified User
C-Level Executive
Chose Drupal
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 …
Well, I'm definitely biased, I've been working with Drupal for 12+ years, and I can say it's appropriate for any size/scale of a project, whether it's a small catalog website or a huge corporation. If I want to dial it down to a specific use case, Drupal is best what most customers/clients that have high-security standards, and need to have extensive editorial experience and control over their website's architecture. Due to its core design, Drupal can connect with each part of its own and any external third-party resources quite easily. For a less-suited scenario, I might say that if you don't have enough budget to get proper work done, sometimes just using WordPress with a pre-designed theme might sound better to you, but if you have the budget and the time, always go with Drupal
3 Scenarios where Sitecore Experience Platform is well suited: 1. Customized AI/ML Model development - Developing and deploying ML/AI models to automate tasks related to the process. e.g., image classification, sentiment analysis or text classification, etc.2. RPA & Chatbots - RPA scripts to automate simpler tasks and integrate with legacy systems (UI path, opensource RPA scripts). Implementation of chatbots training by human agents to respond to redundant queries 3. Data Enrichment - Structuring and enriching data using automated techniques in ML as well as human agent labeling
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.
Sitecore has a decent supply of out of the box components and capabilities that can be fairly easily styled to meet business needs without much customization needed. This often helps speed to market.
Sitecore has had the flexibility of offering on-premise hosting or cloud hosting to meet different needs of clients, though recently they have strongly pushed their cloud-based hosting. This is in alignment with the industry and very helpful for organizations that aren't looking to add another product to the portfolio of packages that their internal IT teams need to manage
Sitecore has a capable UI for editing content. Though some competition may do better in this regard, Sitecore's editing interface is fully capable.
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.
While the UI is capable, some other products in this space have a much more intuitive editing interface. Sitecore could do better in providing an easy to use editing UI.
It would be nice to see a fully managed Sitecore instead of just cloud hosted
The price falls more to the premium side of things. Making the value proposition a bit harder to justify
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's a great CMS platform and there are a ton of plugins to add some serious functionality, but the security updates are too complex to implement and considering the complexity of the platform, security updates are a must. I don't want my site breached because they make it too difficult to keep it up to date.
Implemented for various projects such as:›Market and sales intelligence Competitor tracking Management moves Social media tracking Customized information sourcing. Use web-scraping and parsing for data harvesting where the search is keyword-based and, the content and data extractions are required from various websites•Implemented for diverse requirements:›Social media tracking›Image recognition›Pricing comparison›Competitor content mapping›e-Commerce products’ cataloging, etc.
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.
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.
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 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.
All of these platforms have their pros and cons. Selecting the best fit is a matter aligning corporate need vs features provided. Have a .NET shop with an advanced marketing team looking to push UX forward and willing to pay a premium, then Sitecore may be the right fit. Have an organization centered around Java and only looking for basic CMS capabilities or looking for a budget-friendly option, then there may be better options beyond Sitecore.
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 has allowed us to build up a library of code and base sites we can reuse to save time which has increased our efficiency and thus had a positive financial impact.
Drupal has allowed us to take on projects we otherwise would not have been able to, having a further impact.
Drupal has allowed us to build great solutions for our clients which give them an excellent ROI.
For mature marketing organizations, the analytics that Sitecore allows you to capture have been valuable in pushing forward marketing objectives and giving insight into how to tailor content for the best UX
