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.7 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
WebWave
Score 9.5 out of 10
N/A
WebWave — an alternative for agencies and freelancers for creating custom websites for clients with the support of CMS. Using CMS with no sacrifices WebWave is a CMS platform that gives a designer precision up to 1 px in every single detail just like in more sophisticated graphic programs such as Photoshop while remaining a drag and drop software. This is to make creating websites much faster without loosing on details. Spend less time talking WebWave…
N/A
Pricing
Drupal
Webflow
WebWave
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
No answers on this topic
Offerings
Pricing Offerings
Drupal
Webflow
WebWave
Free Trial
No
Yes
Yes
Free/Freemium Version
No
Yes
Yes
Premium Consulting/Integration Services
No
No
Yes
Entry-level Setup Fee
No setup fee
No setup fee
$7 per month
Additional Details
—
Up to a 22% discount available for annual pricing.
WebWave is easy to use and the learning curve is also less compared to Webflow. They also have custom Html, CSS, and Javascript options which I didn't see on Dorik.com. WebWave is comparatively cheaper in comparison to Webflow. WebWave is in a good direction to becoming a good …
In terms of flexibility and functionalities, WebWave falls behind Webflow. However, practically anyone with a basic understanding of web development or who can use a word processor will be able to teach themselves how to utilize WebWave. Webflow, on the other hand, is far more …
Due to WebWave's innovative and intuitive layer-based design system, it is infinitely more user-friendly than both Webflow and WordPress. Webflow's websites feel lighter and faster, but I'm sure WebWave will address this as they mature. Webflow's animation features are also …
Verified User
Technician
Chose WebWave
price, ease of use, and using a notes system with the client over the top of the page are all improvements against Webflow
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.
Since the purpose in my case is to build a small professional looking site to present project outcomes and other research, I can create custom fields and design experimentations. Webflow builds sites that are super professional, with many amazing templates that don't look cheap. Additionally, I can test responsive layouts. Apart from this, I used 1-2 static pages to illustrate key findings for example what a multilingual site could look like with screenshots without needing CMS in free version, which are all the valuable skills to acquire. Compared to WordPress, Webflow is expensive with limited free features, although it has really cool additional features that will make the site I build stand out.
Well suited: Small businesses and entrepreneurs: WebWave is an excellent option for small businesses and entrepreneurs who need a professional-looking website without spending a lot of time and money. It's easy to use, customizable, and offers fast load times and responsive design. Less appropriate: Large e-commerce websites: If you're looking to create a large e-commerce website with a vast number of products and advanced features, WebWave may not be the best option. Its e-commerce functionality is limited compared to other website builders, and it may not be able to accommodate the needs of a large-scale online store. Also, if you need much coding, you would rather have it with something that is wordpress-based.
Saves time- because I don't have to do double entry of content.
It saves money. I like that it is an all-in-one system, so I don't have to host elsewhere.
Flexibility - Webflow provides me with a lot of flexibility in my webpage design, allowing me to adjust pages as needed, depending on the content types.
WebWave's site builder is the platform's truly innovative feature. I've never come across another service that deploys a layer-based approach in web design, as most of them usually deploy a grid-based system. This is an incredible alteration that ensures WebWave behaves much like a traditional graphic design tool, thereby resulting in an experience that is a lot more intuitive and instinctive. I believe this has the potential to radically change the way people approach no-code web design.
WebWave provides automatic, daily backups and a free SSL certificate for every website. This results in excellent security.
WebWave's support team is first-class! I had some teething-issues in the beginning, but the support team quickly got me back on track.
WebWave's community/forum is an excellent place to vote and request new features. This proves the development team is committed to making WebWave better by listening to their users.
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.
Brand recognition is still behind WordPress, which can make it a challenging sell for clients looking to play it safe in their CMS decision.
The CMS is ideal for smaller datasets, but higher content sites introduce some minor challenges.
Alignment between designers and developers is key prior to implementation. The flexibility of the platform requires careful planning to avoid over-engineering.
Some scope for improvement in UX (colors are not very appealing). It is simple to use but design is a little dated. Especially in the builder section, I'd like to see modern design for buttons and maybe gradients also: as this is where visual motivation is also important
Some edits take effect only after pressing OK. That should be eliminated as it's an unnecessary addition. It's also kind of annoying to do that again and again, which can add up to a lot as we do so many small tweaks while building the website.
Few things (maybe glitches) in design. The rectangle below the footer was uneditable for me. I spent quite some time trying to figure it out so I'm convinced it's a glitch.
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.
Webflow is very easy for a beginner to get started with and achieve good results, but to achieve an expert level of understanding requires experience and some web development knowledge. HTML5, CSS3 and JavaScript knowledge aren't required to use Webflow, but an expert will know BEM class naming patterns, be able to create reusable elements and design systems, and add 3rd party integrations that require custom code.
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.
I haven't had to engage them from a support perspective; however, there is a considerable user community for tips/ideas/troubleshooting and the like. I believe the Pro plan supports additional resources but we didn't find that the cost justified the outcome. Overall the need for support has been relatively minor.
1. The support person does not seem to understand the issues, and seems like they go off to talk to somebody and revert back every 5 to 10 minutes. It takes up a lot of time. 2. There is a lack of reading material to address simple issues like changing the website name in the dashboard, pasting a code, etc.
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 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.
A lot more design control and easier to create a custom site, and then also to scale that site going forward. There's a lot about WordPress I miss, though, when it comes to managing a blog—user permissions, SEO control, edit HTML version of posts.
WordPress is a more flexible and adaptive content management system than Webwave. In addition to the functionalities that are already built-in, I am unable to add any customizable plugins or add-ons. However, in the majority of cases, the inherent features of Webwave are sufficient for developing a website that serves its intended purpose. Webwave also makes it possible for you to add animations and the appearance of each of your design elements, whereas WordPress builders require additional plugins in order for users to access most of such capabilities. Webwave has several essential design features available internally, thus saving money and time.
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.
