Drupal vs. Live Center - Live Reporting vs. MODX

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.

Incentivized

As we have to show the highlights of our blogs in the main page of our website. We choose Live Center as here it is very easy to embed those blogs in the home page. Also, this embeding thing was done by content creator so we don't have to reach to developer always.

Incentivized

[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.)

• Drag and drop functionality is easy to use
• Easy to switch between straight text and HTML content
• Ability to easily have multiple environments so that pages can be built in b/c-stage before they are approved and published
• Solid user experience where it's clear how to navigate the platform

Incentivized

• Ease of use - the MODX platform is very easy to use for someone who may have limited experience in content management.
• Content blocks - the content blocks within MODX add to the usability and customization of the website being managed.

Incentivized

• 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.

Incentivized

• The flow of comments could be improved.
• The ability to turn off auto updates on a live blog doesn't exist.
• Could add more reporting functionality.

Incentivized

• The user interface was confusing at times.
• Not a plug and play CMS system.
• The site manager doesn't always run fast.

Incentivized

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.

However for a general CMS [MODX] is hard to beat.

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.

Incentivized

Great and easy to use for both the coder and the end user. Especially if setup correctly by the coder.

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).

We have not had it go down due to bugs etc. especially when comparing it to other cms out there.

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.

Incentivized

Damn its fast. really good page speed out of the box.

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.

Incentivized

Great community support on slack.

If you have a paid plugin great support also esp from modmore

If you have cloud hosting MODX support is fast and all servers are optimized for MODX

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%

Incentivized

Good system

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.

Incentivized

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.

Incentivized

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.

Incentivized

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.

• Given the endless possibilities that Drupal can have, we tend to have great support going on when we get a website launched
• It has become much much faster and easier for us to launch a new project due to reusability
• Configuration management in Drupal helps greatly with CI/CD, saves us costs

• Increased security permissions of the users and freelancers who worked on our website.
• Gave our developers the ability to create any page that they wanted with custom code.
• Hindered our Marketing team's ability to stay on top of our content strategy with changes.

Incentivized