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
Netlify CMS
Score 9.0 out of 10
N/A
Netlify CMS is an open source Git-based CMS for static site generators. it runs 100% in a browser.
N/A
Umbraco CMS
Score 6.7 out of 10
N/A
Umbraco is an open-source .NET Core CMS with over 700,000 active installs worldwide and with more than 200,000 active community members. It was first released on February 16th, 2005, and is still to this day an open-source project backed by a commercial company. To ensure Umbraco is always running the latest technology, the company has aligned with Microsoft's .NET release schedule to always have the Umbraco CMS…
$0
Pricing
Drupal
Netlify CMS
Umbraco CMS
Editions & Modules
No answers on this topic
No answers on this topic
Umbraco Free
$0
Umbraco Starter
$53
per month
Umbraco Standard
$320
per month
Umbraco Professional
$860
per month
Umbraco Cloud Enterprise
Custom Pricing
per month
Offerings
Pricing Offerings
Drupal
Netlify CMS
Umbraco CMS
Free Trial
No
No
No
Free/Freemium Version
No
Yes
Yes
Premium Consulting/Integration Services
No
No
Yes
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
The Umbraco CMS and all of its core features are the same across all plans.
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 …
Drupal is not as powerful, extensible, or easy to use as Sitecore, but it is free, whereas Sitecore can be quite expensive. It offers a similar service as Umbraco, but from a PHP codebase. For clients that need a free CMS system, it is the clear choice for those with a PHP …
Umbraco provides the best bang-for-the-buck CMS option on a .NET platform for those that cannot afford Sitecore. It is much friendlier to use than Ektron, is free to use, has commercial grade plugins that are not overly expensive, and provides the functionality that most …
Umbraco's templating is far superior than WordPress, Drupal and Joomla, but it's update process is WAY behind those platforms. The release schedule of Umbraco is way to often and most releases are to fix something missed in the previous release and not an improvement or new …
There is not really an alternative when it comes to CMS based on ASP.Net (MVC4 with Razor). There are a few frameworks, like Booststrap; however framework is not content management system. I will compare it to Drupal, because the second one is well known. Against Drupal, …
Features
Drupal
Netlify CMS
Umbraco CMS
Security
Comparison of Security features of Product A and Product B
Drupal
8.1
74 Ratings
1% below category average
Netlify CMS
-
Ratings
Umbraco CMS
9.0
12 Ratings
9% above category average
Role-based user permissions
8.174 Ratings
00 Ratings
9.012 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Drupal
7.6
69 Ratings
2% below category average
Netlify CMS
6.0
1 Ratings
25% below category average
Umbraco CMS
8.5
11 Ratings
9% above category average
API
7.264 Ratings
6.01 Ratings
8.010 Ratings
Internationalization / multi-language
8.160 Ratings
00 Ratings
9.010 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Drupal
6.5
78 Ratings
18% below category average
Netlify CMS
6.1
1 Ratings
24% below category average
Umbraco CMS
8.0
12 Ratings
3% above category average
WYSIWYG editor
6.171 Ratings
9.01 Ratings
10.012 Ratings
Code quality / cleanliness
8.175 Ratings
9.01 Ratings
10.012 Ratings
Admin section
6.878 Ratings
7.01 Ratings
7.012 Ratings
Page templates
5.577 Ratings
3.01 Ratings
8.012 Ratings
Library of website themes
5.468 Ratings
1.01 Ratings
6.011 Ratings
Mobile optimization / responsive design
6.572 Ratings
5.01 Ratings
6.011 Ratings
Publishing workflow
6.876 Ratings
9.01 Ratings
10.012 Ratings
Form generator
6.372 Ratings
00 Ratings
7.010 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
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.
Netlify CMS is well suited when you have very less frequent updates to your content, maybe once a day and very few people need to access your data. You can connect it to Netlify, GitHub, or any platform and have multiple people access it and do as many updates as you wish, but the process is not well-defined and you need to build your own system for that. It is well suited for projects you need to pull off with very low cost, it is essentially free as the software is open source and free to use, and all you need to do is set up your schema correctly and find a deployment pipeline where you can build your static site/API to redeploy whenever the content changes. I personally used a GitHub Login -> Netlify CMS -> next app consumer of content -> GitHub pipelines to run next SSG -> GitHub Pages to deploy the built static site. It might not be appropriate for large teams where users themselves need no-code tools to modify the schema of the content.
Umbraco CMS is the perfect tool for a company that is looking to keep their website updated. The simple to use tools and templates means updating and creating new pages is easy. The WYSIWYG editor is a nice feature, however, for accessibility, there should be some more guidance on what is suitable to be used on the CMS.
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.
Speed for older sites - Umbraco content can load slowly if you have thousands of pages of content. Of course, this would not be a problem for simpler websites
Complexity - since the product is free out-of-the-box, it will take technical expertise to get Umbraco setup properly
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.
Umbraco CMS effectively addresses enterprise content management needs. It's quite mature .NET based CMS, standing out as a leader among its competitors. Websites built with Umbraco are blazing fast. Extensive customization capabilities, and user-friendly content publishing interface makes it an ideal choice for businesses looking for a mature CMS solution.
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.
Working in the admin panel (adding / reviewing / editing content) is very slow. The public facing site speed is dependent on what the pages are doing and how well the code was written (whether it is optimized for speed).
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%
Spend the time to wireframe the content structure prior to diving in. This helps speed the process of implementation and it serves as documentation for end users.
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.
We really can't compare it to full-fledged CMS software, like WordPress, which has a lot of community and support with widgets, plugins, and whatnot. It's not built for that, but you can compare it to Contentful, Ghost, Strapi, etc., which provide similar functionality to a headless CMS with custom schema options, but even among them, it still lacks a lot of functionality, ease of use, and support. But Netlify CMS pros would be of the opinion that compared to other platforms where most schemas need to use their own tools and frameworks, it's very cost-effective. Something new called TinaCMS has come up to compete with Netlify CMS by covering most of its shortcomings, but it's something new being built by the same team that built Forestry CMS and comes with many modern features, yet currently only supports NextJS SSG.
Umbraco's templating is far superior than WordPress, Drupal and Joomla, but it's update process is WAY behind those platforms. The release schedule of Umbraco is way to often and most releases are to fix something missed in the previous release and not an improvement or new feature of the CMS
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.