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
Makeswift
Score 8.0 out of 10
N/A
Makeswift is a composable visual editor for headless websites and storefronts. From BigCommerce, the page builder aims to put marketers in the driver's seat without compromising on site performance or developer experience.
$79
per month
Pricing
Drupal
Makeswift
Editions & Modules
No answers on this topic
Starter
$79
per month
Team
$299
per month
Enterprise
Contact Sales
plans start at 10 users, 100 monthly publishes, and 10 locales
Offerings
Pricing Offerings
Drupal
Makeswift
Free Trial
No
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Drupal
Makeswift
Features
Drupal
Makeswift
Security
Comparison of Security features of Product A and Product B
Drupal
8.1
74 Ratings
1% below category average
Makeswift
8.0
1 Ratings
2% below category average
Role-based user permissions
8.174 Ratings
8.01 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Drupal
7.6
69 Ratings
2% below category average
Makeswift
8.5
1 Ratings
9% above category average
API
7.264 Ratings
9.01 Ratings
Internationalization / multi-language
8.160 Ratings
8.01 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
Makeswift
7.5
1 Ratings
4% below category average
WYSIWYG editor
6.171 Ratings
10.01 Ratings
Code quality / cleanliness
8.175 Ratings
9.01 Ratings
Admin section
6.878 Ratings
7.01 Ratings
Page templates
5.577 Ratings
6.01 Ratings
Library of website themes
5.468 Ratings
5.01 Ratings
Mobile optimization / responsive design
6.572 Ratings
9.01 Ratings
Publishing workflow
6.876 Ratings
8.01 Ratings
Form generator
6.372 Ratings
6.01 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.
Makeswift is an excellent choice when you need to create high quality landing pages. Since it removes the code process, you can move from a design concept to a live site easily. It is particularly helpful for designers who want total creative freedom, as the interface feels more like Figma than a normal website builder. Plus, it’s a lifesaver for collaborative teams because the real time editing allows different people to create and design at the same time without any friction. On the other hand, it might not be the right tool if you are trying to build a complex web application like a custom dashboard or an e-commerce store with thousands of filters. It’s also important to note that while it is no code for design work, the initial setup like getting custom components or the localhost environment running usually requires a developer’s assistance.
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.
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.
Once you are inside the builder, the daily experience is incredibly smooth. It really does feel like a strong design tool rather than a clunky website builder. The drag and drop feature is fluid and the collaboration mode makes working with my team feel natural rather than a headache. It’s intuitive enough that I can jump in and make significant changes without feeling like I need a manual next to me.
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.
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.
Essentially the learning curve. I chose Makeswift because it feels much more like a design tool (like Figma) than a development environment. It gives the designers the control to create what they want. It allows to move faster, collaborate in real time without locking each other out of pages, and still gives the developers the freedom to drop in custom components when we need something specific.
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.