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 8.0 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.
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.
We evaluated many CMS systems and Drupal came out on top because of its flexibility and that its open source. We didn't always know everything we would be asked to build and Drupal allowed us to be nimble enough to do what needed to get done. We also liked that it handled …
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 …
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 …
Verified User
Director
Chose Progress Sitefinity
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 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.
Have looked into WordPress and Drupal but Sitefinity worked better for our application because of its visual studio integration and it seemed to be a much more robust product. Have used Telerik for years and Sitefinity fit in nicely.
Sr. Associate - Project Management and Information Technology
Chose Progress Sitefinity
All continent management systems are built to do basically, the same thing...manage content. When Trellist makes a CMS recommendation to a client, it is primarily based on the project requirements, how easy it is to customize the CMS, how intuitive it is for the content …
We thought it would be better, and especially better suited for .NET and Azure solutions.
In the end, I would say Sitefinity is worse in nearly all aspects, including Microsoft technology integration.
I find that Sitefinity has the heart and soul of an open source CMS in that it is easy to use by everyone, but it definitely has the street cred in the enterprise market that it has a solid API and you can easily build custom applications on the platform.
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
Progress Sitefinity remains a little heavyweight for sites that require basic text content, or a limited number of pages. However, its flexibility (including the range of different content types if supports) make it a good choice for any organization requiring advanced content management capabilities at an affordable price.
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.
'Low-code structured content' (dynamic content types) is one of Sitefinity's most powerful features that allows you to structure content according to business needs, while at the same time dampening editorial freedom to ensure accessibility, meta enhancement, SEO and API consumption can be achieved.
Sitefinity's content provider model allows us to flexibly (by means of admin interface) easily aggregate or separate content sharing within a multi-site instance.
This proofs particularly powerful in emerging situations where there suddenly is a demand for content sharing across countries or regions.
Adaptability at its core.
While there's never a perfect fit for everything, it allows for easy code customization and extension being a .NET application at heart. Giving it a corporate edge over other custom solutions, whether it is on the development side or deployment side (on premise, IaaS or Azure DevOps Paas). And it has enabled us to put the system to use in its core feature - which is to manage content, where on other occasions we were able to take full advantage of its features such as A/B testing and personalization.
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.
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.
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 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.
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
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.