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
Webflow
Score 8.0 out of 10
N/A
Webflow is a Website Experience Platform for modern marketing teams, used to visually build, manage, and optimize websites that offer both the consumer experience teams expect and enterprise-grade performance and scale.
$18
per month
Pricing
Drupal
Webflow
Editions & Modules
No answers on this topic
Basic
$18
per month
CMS
$29
per month
Ecommerce - Standard
$42
per month
Business
$49
per month
Ecommerce - Plus
$84
per month
Ecommerce - Advanced
$235
per month
Offerings
Pricing Offerings
Drupal
Webflow
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
—
Up to a 30% discount available for annual pricing.
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
Webflow is great for designing pages and creating a really nice looking website, without needing to be a pro designer. However, trying to scale a company blog for SEO leaves a lot of room for desire. There are various SEO-related shortcomings (like how canonical tags are added to pages) and I also need to add a lot of custom code elements to blog posts to get the desired control. This means adding new posts and getting them looking the way we want takes way more time than it should do. Also doesn't support next-gen images, which is impacting our page speed scores and leaving us behind when it comes to Core Web Vitals update. Finally, the fact that only one person can enter the designer at one time is really annoying. I get that the Editor should be the solution to this, but it's so so so slow and jumpy that this is essentially unusable.
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.
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 Content Management System needs improvement. In my experience, it's very difficult to organise all our content at big volumes. We want to create a resources section where we can categorize our content but there isn't an easy or intuitive way to do it
In my opinion, it's incredibly difficult to create tables in an article
You have to do custom coding for anchor links within an article and it's time consuming and, in my opinion, super annoying
Website designs are not responsive we need to keep designing a separate mobile version
In my opinion, Formatting content in articles is annoying compared to other CMSs like Wordpress, Shopify, Wix, Blogger, etc. Worst experience I've had.
Changes to the nav bar on the homepage do not reflect universally, we needed to do the same changes all over again for our blog and mobile
Content editors need to keep logging in every time they add content
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.
It is extremely easy to use, especially with available templates and guides. It is used primarily by accounts and creative rather than dev. It is also easy to import/export projects or duplicate them for re-use and modification for another client. While it is rarely the end platform for a deliverable, it is often instrumental in pitching.
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).
In my experience, their customer service is an absolute joke, I tried reaching out to them they took forever. I had to keep following up with them as if they never received it in the first place. It’s a new platform, so guidance is needed. Tried the university they offer, in my opinion, it is completely useless, I would just completely move on from this website.
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.
In my opinion, it is horrible, the rendering takes forever. I have the newest MacBook and the platform will still lag and slow down on me. I’m not a developer, I am a designer which makes it worst because I am using the features they are providing not extra coding features. In my opinion, it is a horrible platform really, stay away.
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.
We pay hundreds of dollars a month to Webflow, yet their support is worse than a typical free SaaS product. We were prevented from deploying changes to our site because of how Webflow structures its support. It delayed a product launch for the whole company. Support options? Beg for help on community forums, it took a threat to email the CEO to finally get movement. If there were easy alternatives, we would switch. But for now we just pray nothing breaks and that we don't need to interact with Webflow support.
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.
We loved the feature set and extensibility. It's a little pricey but when we have the time to devote to a project it shows why Webflow is such a good fit. Of course there are lots of other things you can use it for, but it's been working for us for one-off marketing projects.
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.
I feel it doesn’t perform the way it’s supposed to and it doesn’t have any beneficial factors to it. In my opinion, there is no reason to use a platform like this when Wix and Shopify, and WordPress exist. I believe Webflow is a platform that shouldn’t exist and it’s only popular because of the hype it received. I tried it and hate it completely.
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.
