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
MODX
Score 9.0 out of 10
N/A
The MODX Digital Experience Platform provides everything you need to build, host, and maintain amazing websites your way. The vendor says that with MODX CMS and cloud hosting, users have complete control over their creative vision and the experiences they deliver, without restriction or compromise. They can focus more on building great digital experiences, and less on hosting and maintaining. If you ever need help, MODX Professionals are available worldwide and direct support from…
$0
per installation
Pricing
Drupal
MODX
Editions & Modules
No answers on this topic
MODX Revolution
$0
per installation
PRO - Perfect for customers with typical marketing sites
$19
per month
STUDIO - Perfect for customers who need more power and resources
$49
per month
BUSINESS - Perfect for digital agencies and marketing departments
$99
per month
ENTERPRISE - Perfect for or organizations with custom requirements
Upon Request
Offerings
Pricing Offerings
Drupal
MODX
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
PAYMENT FORMS
MODX Cloud accepts major credit cards and PayPal for your hosting subscription. We can only accept check (cheque) payments on the Enterprise Plan, annually.
CANCELLATION
You may cancel your MODX Cloud account at any time. Before you cancel you'll be reminded to backup and remove all your live websites and then follow the instructions for cancellation. If you cancel within the first month, we'll provide you with a full refund.
REFUNDS
If you cancel within the first month, we'll provide you with a full refund. All other cancellations will be effective at the end of your current billing period. We do not provide refunds for remaining days or months on monthly or annual billing.
After having built sites with WordPress, Joomla, Drupal, october cms, craft cms, magento, presstashop, opencart, os commerce and more it is my number 1 (october cms is 2).
Well, I'm definitely biased, I've been working with Drupal for 12+ years, and I can say it's appropriate for any size/scale of a project, whether it's a small catalog website or a huge corporation. If I want to dial it down to a specific use case, Drupal is best what most customers/clients that have high-security standards, and need to have extensive editorial experience and control over their website's architecture. Due to its core design, Drupal can connect with each part of its own and any external third-party resources quite easily. For a less-suited scenario, I might say that if you don't have enough budget to get proper work done, sometimes just using WordPress with a pre-designed theme might sound better to you, but if you have the budget and the time, always go with Drupal
[MODX is well suited for] all websites, from blogs to corporate sites. It is fast scalable and really good. A small site can be build really fast, and a large site can be made extremely scalable. A website redesign is easy to implement with a new template, without having to redo the content. It got great user groups and users and back-office access can be completely customized.
While ecommerce is possible with some really good plugins I would only use MODX with ecommerce for sites where ecommerce is not the primary role. For pure ecommerce sites rather use a dedicated system like e.g. PrestaShop (i would say the same thing with other ecommerce plugins e.g. WP woo commerce don't do it unless its a site add on.)
Content Types... these are amazing. Whereas a more simplistic CMS like Wordpress will basically allow you to make posts and build pages, Drupal 8 gives you the ability to define different types of content that behave differently, and are served up differently in different areas of the website.
Extensibility... it scales, ohhhh does it scale. They've really figured out server-side caching, and it makes all the difference. Once a page has been cached, it's available instantly to all users worldwide; and when coupled with AWS, global redundancy and localization mean that no matter where you're accessing the site, it always loads fast and crisp.
Workflows... you have the ability to define very specific roles and/or user-based editorial workflows, allowing for as many touchpoints and reviews between content creation and publication as you'll require.
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.
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.
It is the CMS we use the most, not because we know it well but because we literally tried many of other CMS and this one did it for us.
However having said we really do not like the one shoe fits all approach. E..g for eCommerce we usually use PrestaShop etc. if a specialized CMS can do a task rather use that.
It's a great CMS platform and there are a ton of plugins to add some serious functionality, but the security updates are too complex to implement and considering the complexity of the platform, security updates are a must. I don't want my site breached because they make it too difficult to keep it up to date.
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 is community-backed making it more accessible and growing at a faster rate than Sitefinity which is a proprietary product built on .NET. Drupal is PHP-based using some but not all Symphony codebase. Updates for Drupal are frequent and so are feature adds.
The other company that we looked into was WordPress and all of the features that it offered our organization. What MODX offered to us from development to everyday use just made more sense for our organization as a whole. WordPress is still a great CMS platform, just not exactly what we were looking for.
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.
Very scalable. e.g. in the [MODX] manager you can manage multiple websites at once without having to login else where. it is very convenient and this way resources and be easily managed and shared.
Drupal has allowed us to build up a library of code and base sites we can reuse to save time which has increased our efficiency and thus had a positive financial impact.
Drupal has allowed us to take on projects we otherwise would not have been able to, having a further impact.
Drupal has allowed us to build great solutions for our clients which give them an excellent ROI.
