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
Progress Sitefinity
Score 7.7 out of 10
N/A
Progress Sitefinity is a content management and customer analytics platform. It supports content management, tailored marketing, multi-channel management, and ecommerce sites.
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 …
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 …
It was a much more user-friendly CMS that allows all teams to easily access and utilize the tool to its fullest. Marketers can market without messing up or breaking code. Developers can code without having to worry about SEO/marketing, etc. We are big fans of this tool and …
The stability of Sitefinity and speed are better. The ease of content updates and template creation is by far superior and doesn't require any technical knowledge. Sitefinity doesn't force you into unplanned and forceful updates, like other software for content management that …
We evaluated a range of other platforms before selecting Progress Sitefinity. While many other platforms had a powerful range of features, Progress Sitefinity provided to be a comparable product at a price far more suited to our budget. Above all else, its ease of use gained …
My main experience has been with Drupal and SharePoint besides Sitefinity.
And while many people swear by Drupal because of its open-source nature, often the hidden TCO, its lack of intuitive usage and limited functional implementation (CMS for Web Publishing) has made us choose …
In addition to being a user of Sitefinity, my company is also a Sitefinity Partner. More than a decade ago, we were supporting several CMS platforms and decided we wanted to pick one and be great at it. After analyzing many content management systems, we decided that Sitefinity …
It is hands down just easier for our customers to use. The interface and the page builder experience is much better than what we have used in the past and has many enterprise features even in the lower price-point.
WordPress has a huge community when it comes to custom plugins available. The ability to use functions.php files to add scripts makes it very easy to use and handle. Only issue is that WordPress lacks the ability to scale for a bigger site.
It has way more availability for customization. I feel it is easier to give a client what they want with Sitefinity than with any other product I've used over the last 6 years.
Sitefinity has its advantages and disadvantages. We view it as a useful tool in our toolbox and are always happy to develop a new Sitefinity site when its features align with the needs of our clients. From a content management standpoint, it is easier to work in than some and a …
DNN was very similar from a flexibility and feature perspective but wasn't as polished or professional feeling. Kentico was poor in communication, not replying to email requests and questions. Crownpeak we had been using for many years but wasn't impressed with customer loyalty …
This was already implemented when I arrived here but have looked into moving it to another platform. The time involved in doing that is just not worth the time right now. Sitefinity does what it is supposed to but it's not the most user friendly and support is not very good.
Sitefinity is more robust than WordPress. It is much less expensive than either Oracle or IBM. It has a broad range of functional capabilities and it is very reliable. It is not a leader in security, but this was not our top priority. Its A/B testing is not as extensive as …
We were looking for a CMS that was net-based, as it was the preferred platform based on knowledge and experience. It was also something that we could see sourcing external support if needed. Much wider expert base.
Against WordPress, Sitefinity is easier for content authors to manage content on the site. Against Ektron, seems like the application and administration tools were hacked together, and has poor ongoing support. Sitefinity has a simple approach to managing/organizing pages, …
Best system from a feature/cost point of view. We had specific requirements, one of which was that the system had to be based in a IIS/.net environment.
Price was another factor and ease of implementation with the existing development staff another.
Sitefinity is a closed source solution and for our financial institution customers, that means a great deal. Sitefinity is also not dependent on third-party plugins or addons to do most things. Our customers find that Sitefinity is easier to use when it comes to making edits to …
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.
It's one of the easiest to use, easiest to customize CMS system available on the Microsoft technology stack. Whenever there's an application need for user management, role-based permissions, workflows and page-content, it is simply not done to start custom development from scratch. For complex 'factory-approaches' its architectural implementation shines brightest and allows for hybrid deployments, full Azure DevOps integration and ensures security and governance are not sacrificed
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.
Once templates and custom data has been defined, it is very easy for CMS authors/editors to manage content on the site without knowledge of HTML programming.
Programming templates and custom module and extending the CMS is fairly straightforward for our development team.
Security is in the forefront, with regular updates and enhancements to the product.
Working with support is great, they have extensive knowledge on the product are able to assist if called upon.
Product utilizes .net standards, and also integrates well will standard front end tools such as jquery/bootstrap.
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.
Diagram or illustrate more use cases for server setups, and managing of upgrades.
I'd like to see the ability to synchronize from one server to multiple others at once.
Implementation assistance as part of the purchase rather than farming out to 3rd party, although they did answer every question we asked in order to determine our best architecture setup.
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.
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.
Very big fan of this CMS, as it allows scalability, performance, and everything else. The support is great whenever we need it. As a marketer, the digital/marketing side of things is very easy to use and we've seen strong results from an SEO and marketing perspective. I can't speak to the developer/creative side too much, but in talking with these teams, they do recommend the tool as well.
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.
Support can be pretty good, even though, depending on the level of licensing, it can take longer to hear back from their team. They do have a phone option, which works well. Overall, they are knowledgeable, and helpful when needed. At times, support is able to access the system directly and troubleshoot critical items when needed.
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%
N/A - I was not part of the implementation team. We have had this internally for over 5 years. Based on my experience, ensure that you have documentation on the initial implementation and subsequent upgrades. I would also recommend to have all the documentation on how and why the system was implemented the way it was
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.
We evaluated a range of other platforms before selecting Progress Sitefinity. While many other platforms had a powerful range of features, Progress Sitefinity provided to be a comparable product at a price far more suited to our budget. Above all else, its ease of use gained the highest scores in our testing, and the interface has continued to develop and improve over the past three years.
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.