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
Figma
Score 9.0 out of 10
N/A
Figma, headquartered in San Francisco, offers their collaborative design and prototyping application to support digital product and UI development.
$15
per month per editor
Pricing
Drupal
Figma
Editions & Modules
No answers on this topic
Professional
$144
per year
Organization
$540
per year
Starter
Free
Offerings
Pricing Offerings
Drupal
Figma
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
Figma
Features
Drupal
Figma
Security
Comparison of Security features of Product A and Product B
Drupal
7.9
72 Ratings
4% below category average
Figma
-
Ratings
Role-based user permissions
7.972 Ratings
00 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Drupal
7.2
67 Ratings
7% below category average
Figma
-
Ratings
API
6.562 Ratings
00 Ratings
Internationalization / multi-language
7.958 Ratings
00 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Drupal
6.2
76 Ratings
23% below category average
Figma
-
Ratings
WYSIWYG editor
5.769 Ratings
00 Ratings
Code quality / cleanliness
7.973 Ratings
00 Ratings
Admin section
6.276 Ratings
00 Ratings
Page templates
5.575 Ratings
00 Ratings
Library of website themes
5.466 Ratings
00 Ratings
Mobile optimization / responsive design
6.370 Ratings
00 Ratings
Publishing workflow
6.574 Ratings
00 Ratings
Form generator
6.070 Ratings
00 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
Overall, I would give my rating of Drupal a 7/10 because there is an easy user experience for those without a website background but there is some technology work required to build more website capabilities that aren't as user-friendly. Drupal is specifically well suited to update content (like changing Relationship Manager cards when there is employee turnover), post announcements (putting up a holiday banner to let our customers know the dates we will be closed over Thanksgiving, Christmas, etc., and creating a sophisticated website hierarchy of pages (for our firm, several dropdowns depending on if you're looking for personal banking, business banking, investment banking, about us, etc.).
I would recommend if you need to start from scratch a product UI or any customer journey that you need to implement that requires designing and visualizing different steps to complete a process. I would recommend that any design/UI/UX team brainstorm and make proposals that they can compare and discuss in a visual way.
It has excellent security features and consistent updates.
It allows for extensive customization with the integrated themes and core code, especially when you first install it. This allows our dev team to get creative with marketing initiatives.
There is a large online community of Drupal users that consistently help answer any questions and issues
Figma allows us to create universal content. This means that if multiple designers want to re-use a piece of content, and if everyone's content should be dynamically updated from time to time, we can easily accomplish this by turning design elements into a universal instance. Then, if an update is needed, we can push the change out to all assets at once. It's very efficient and ensures we're all updating content accordingly.
Figma also allows us to set parameters for the company's brand guide and share them across various designers. This way, we can easily pull from approved brand fonts, colors, and more, which allows our assets to remain unified across multiple touchpoints.
Figma also allowed us to create and install our own plugin, which we use to export every slide we have in a frame at one time, versus the default export feature, which limits you to one slice at a time. This is particularly useful for us when we're working on email templates, since we tend to have a ton of slices in any given series.
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.
It will be great if Figma will consider having the Pages where interactions can be stitched together among the Pages and not just one page with so many Frames to create the stand-alone clickable prototype that can be used to simulate the intended UX
Bring back the Inspect Mode tab right on the right-side panel of the main workspace instead of hiding behind the Dev Mode.
Figma Slides feature could be improved quite a bit more in order to be easier to assemble slides into a presentation deck and having pre-built templates for slides can be useful too.
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.
Figma is a pretty cool tool in many areas. My team almost uses it on daily basis, such as, brainstorming on product/design topics, discussing prototypes created by designers. We even use it for retrospectives, which is super convenient and naturally keeps records of what the team discusses every month. Furthermore, I do see the potential of the product - currently we mainly use it for design topics, but it seems it is also a good fit for tech diagrams, which we probably will explore further in the future.
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.
There's a bit of a learning curve, but generally I think it's both more powerful and intuitive that other UX design tools. Most of what I need to do as a designer can be done in this platform, from basic wireframes to creating a design system, to creating pixel perfect designs, to prototyping to dev handoff.
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 haven't used their support lately but in the past, they had a chat that I used often. They often responded in a few hours and were able to give a satisfactory solution. I would imagine it's less personal now but the community has expanded drastically so there are more resources out there to self serve with a bit of Google magic.
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.
In-person training has its own benefits - 1. It helps in resolving queries then and there during the training. 2. I find classroom or in-person training more interactive. 3. Classroom or in-person training could be more practical in nature where participants can have an hands on experience with tools and clarify their doubts with the trainer.
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.
Online training has its own merits and demerits - 1. Sometimes we may face issues with connectivity or the training content 2. The way training is being delivered becomes very important because not everyone is comfortable taking online training and learning by themselves. 3. With the advancement of technology online training has become popular but there is a segment of people who still prefer class-room training over online one.
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.
Miro is more user-friendly than Figma, but is less robust in terms of web prototyping and graphic design. While Figma isn't made to be used as a design tool, our team has taken to using it as such because it's richer in functions and personalizations compared to Miro and Figma.
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.