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
Jotform
Score 8.4 out of 10
N/A
Jotform Enterprise is a digital workspace productivity tool that provides a platform for organizations. The aim of Jotform Enterprise is to give companies an easy-to-navigate tool that makes reaching out to customers, collaborating with coworkers, and collecting e-signatures and data a more seamless process. Jotform Enterprise strives to enable companies to make data-driven decisions without compromising when it comes to quality and security. It doesn’t matter what type of…
$0
Pricing
Drupal
Jotform
Editions & Modules
No answers on this topic
Free
$0.00
Bronze
$34.00
Monthly
Silver
$39.00
Monthly
Gold
$99.00
Monthly
Enterprise
Custom
Offerings
Pricing Offerings
Drupal
Jotform
Free Trial
No
Yes
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
Jotform
Features
Drupal
Jotform
Security
Comparison of Security features of Product A and Product B
Drupal
8.1
74 Ratings
1% below category average
Jotform
-
Ratings
Role-based user permissions
8.174 Ratings
00 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Drupal
7.6
69 Ratings
2% below category average
Jotform
-
Ratings
API
7.264 Ratings
00 Ratings
Internationalization / multi-language
8.160 Ratings
00 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
Jotform
-
Ratings
WYSIWYG editor
6.171 Ratings
00 Ratings
Code quality / cleanliness
8.175 Ratings
00 Ratings
Admin section
6.878 Ratings
00 Ratings
Page templates
5.577 Ratings
00 Ratings
Library of website themes
5.468 Ratings
00 Ratings
Mobile optimization / responsive design
6.572 Ratings
00 Ratings
Publishing workflow
6.876 Ratings
00 Ratings
Form generator
6.372 Ratings
00 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
Drupal
6.5
77 Ratings
13% below category average
Jotform
-
Ratings
Content taxonomy
6.971 Ratings
00 Ratings
SEO support
6.272 Ratings
00 Ratings
Bulk management
6.367 Ratings
00 Ratings
Availability / breadth of extensions
6.570 Ratings
00 Ratings
Community / comment management
6.569 Ratings
00 Ratings
Survey Format & Appearance
Comparison of Survey Format & Appearance features of Product A and Product B
Drupal
-
Ratings
Jotform
7.9
163 Ratings
1% below category average
Survey templates
00 Ratings
8.6139 Ratings
Themes
00 Ratings
7.5147 Ratings
Custom logo/branding
00 Ratings
7.6153 Ratings
Survey Content
Comparison of Survey Content features of Product A and Product B
Drupal
-
Ratings
Jotform
8.9
150 Ratings
5% above category average
Changes to live survey
00 Ratings
9.1126 Ratings
Question design help
00 Ratings
9.0124 Ratings
Multiple question types
00 Ratings
8.7147 Ratings
Survey Logic
Comparison of Survey Logic features of Product A and Product B
Drupal
-
Ratings
Jotform
9.4
126 Ratings
12% above category average
Survey logic flexibility
00 Ratings
9.4126 Ratings
Survey Reporting & Analytics
Comparison of Survey Reporting & Analytics features of Product A and Product B
Drupal
-
Ratings
Jotform
8.3
153 Ratings
3% above category average
Response tracking
00 Ratings
8.0144 Ratings
Data export
00 Ratings
9.0146 Ratings
Standard reports
00 Ratings
7.8132 Ratings
Custom reports
00 Ratings
8.2124 Ratings
Analytics
00 Ratings
8.6114 Ratings
Survey Administration & Security
Comparison of Survey Administration & Security features of Product A and Product B
Drupal
-
Ratings
Jotform
9.1
127 Ratings
5% above category average
Access controls
00 Ratings
9.0123 Ratings
Compliance
00 Ratings
9.1116 Ratings
Survey Distribution
Comparison of Survey Distribution 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.
We use it for mostly community surveys and I absolutely prefer it over any other survey program out there. It is easy to create, easy to understand and easy to navigate. I love the QR code option it creates for you to share your form/ survey with others. It really is the best out there!
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.
As a seasoned user who relies on seamless online forms for a multitude of purposes, I can confidently attest that JotForm has not only simplified the form creation process but has also elevated it to new heights.JotForm's interface is a masterpiece of intuitive design. Even if you're a newcomer to the world of online form creation, the platform's user-friendly layout will have you crafting professional-grade forms in no time.
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 honestly have not used the support feature with Jotform. From what I can see when I look information up, everything I want to do something that I can't figure out myself it seems to not be a possible solution or edit that Jotform is currently capable of.
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%
the most valuable things that Jotform give free trial, so the resistant users can get the experiences of the easiness and more handling to the digital things
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.
Typeform is better hands down [in my opinion]. It's not even a comparison as [I feel] JotForm doesn't work properly and [from my experience I think] their support is very problematic. I would suggest using Typeform or using GravityForms as an alternative to JotForm. Whatever you do, [I feel you shouldn't] depend on JotForm for something that is important to your business or research project.
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.
It saved me time. Within minutes I was able to create and share forms to collect demographic data.
While struggling to use another software, I thought of Jotform and it was able to assist me with collating the data I had to confirm results previously obtained.
I could not easily identify what new information was provided in a resubmission by a respondent.