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
Ingeniux CMS
Score 9.0 out of 10
Enterprise companies (1,001+ employees)
Ingeniux is a provider of web content management and
digital experience software. The vendor states their solutions are built to enable organizations to orchestrate
the entire customer experience – from acquisition through to support and
service – on any device, application, or website. Ingeniux CMS is designed to
manage and deliver modern websites, customer support portals, online
communities, and other customer touchpoints.
The vendor further states Ingeniux builds content…
N/A
Strapi
Score 8.0 out of 10
N/A
Strapi is an open-source software platform that helps developers to easily build, deploy, and manage APIs.
N/A
Pricing
Drupal
Ingeniux CMS
Strapi
Editions & Modules
No answers on this topic
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Drupal
Ingeniux CMS
Strapi
Free Trial
No
No
Yes
Free/Freemium Version
No
No
Yes
Premium Consulting/Integration Services
No
Yes
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
Drupal
Ingeniux CMS
Strapi
Considered Multiple Products
Drupal
Verified User
Analyst
Chose Drupal
We did a comparison of Drupal against Joomla, WordPress, and Ingeniux. We found that its multiple themes available for web pages, user management, comment management, and form generation stands apart from its competitors.
Ingeniux CMS is intended for large sites, which WordPress and Drupal can sometimes struggle with. Also, it offers far more freedom in development than Cascade Server, as you can use C# and Razor templating to build the pages, and this gives you access to advanced functionality …
We found the DITA capabilities to give the Ingeniux CMS an upper hand when compared with the other alternatives we evaluated in the discover phase. Though there are a plethora of CMS products and Ingeniux CMS doesn't have a free version either. But their vision for the future …
IGX has came a long way and is going even further. Once they integrate more self-support for developers, integrate with other languages and provide more detailed specific training, they will stack up to the leaders, Drupal and Joomla. IGX is on their way, I know product …
Strapi
No answer on this topic
Features
Drupal
Ingeniux CMS
Strapi
Security
Comparison of Security features of Product A and Product B
Drupal
8.1
74 Ratings
1% below category average
Ingeniux CMS
9.1
7 Ratings
10% above category average
Strapi
10.0
1 Ratings
20% above category average
Role-based user permissions
8.174 Ratings
9.17 Ratings
10.01 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Drupal
7.6
69 Ratings
2% below category average
Ingeniux CMS
8.2
5 Ratings
6% above category average
Strapi
10.0
1 Ratings
25% above category average
API
7.264 Ratings
8.35 Ratings
10.01 Ratings
Internationalization / multi-language
8.160 Ratings
8.14 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
Ingeniux CMS
8.4
7 Ratings
8% above category average
Strapi
9.0
1 Ratings
14% above category average
WYSIWYG editor
6.171 Ratings
8.33 Ratings
8.01 Ratings
Code quality / cleanliness
8.175 Ratings
8.33 Ratings
00 Ratings
Admin section
6.878 Ratings
9.16 Ratings
10.01 Ratings
Page templates
5.577 Ratings
7.47 Ratings
9.01 Ratings
Library of website themes
5.468 Ratings
00 Ratings
00 Ratings
Mobile optimization / responsive design
6.572 Ratings
8.16 Ratings
00 Ratings
Publishing workflow
6.876 Ratings
8.37 Ratings
00 Ratings
Form generator
6.372 Ratings
9.01 Ratings
00 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.
This is a CMS solution that uses ASP and now XSLT and ASP.NET MVC environment, so make sure your servers are Windows based. Also, be sure to speak about audits to your CMS environment, this can save you time, money and energy if you intend on developing anything custom in the future. The more prepared your environment, the smoother it is to use this powerful cms.
1. If a headless CMS is needed. 2. Need the cms UI to be clean. 3. There is a need for customization options in the UI and API as well. 4. Expertise in javascript and need cms with node js backend. 5. Want auth APIs pre-made. 6. Easy to customize the backend as well. 7. The user interface can be fully customizable.
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.
SEO Management - though our courses are not available free publicly but still within our systems a better search engine for the courses and its content could work very well.
Ingeniux could be more interactive when it comes to exporting/importing documents.
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.
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.
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.
Company employees can easily locate product documentation now. Our team doesn't have to field nearly as many pings and calls from people looking for content.
The writers can manage the content much more easily now. For example, multiple writers can work on individual topics as opposed to passing around Word files.
We can single-source content that is duplicated across the site. This is a huge time saver.