MODX vs. Percussion CMS

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

Best suited for large organizations where everyone knows how to deal with Java in an increasingly Java unfriendly world. Said organization should be willing to pay a huge price for a piece of dinosaur technology

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

• Separate CMS environment publishes to remote server environment - great for security
• Highly scalable
• Full scale workflow allows for custom routing, approving, etc..

Incentivized

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

Incentivized

• One word: JAVA! We don't live in the 1990's anymore! An AJAX/DHTML environment seems a long time coming.
• Horrible end-user experience, learning curve. Our end users' inability to easily use the archaic, Java-based interface, means they send the web developer their content requests. This creates a huge bottleneck and completely defeats the purpose of a CMS.
• Image mangement and integration with content is aweful and time consuming. An image processing tool called ImedImage was developed for Percussion at one point, and left completely stagnant with very little support.
• Implementation is extremely complicated, given the complexity of the system. Sure, scalability is a good thing, but there is very little out-of-the box function. Don't expect to implement a site as quickly as with other CMS platforms.

Incentivized

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.

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

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

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

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

Good system

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

No contest. I can't wait to get off of Percussion CMS.

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.

• 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

• We are locked into Percussion CMS simply due to the expense and complexity of migrating to another solution (and the lack of time and budget to do so). I long for the day when I am no longer required to support Percussion CMS, to say the least.

Incentivized