CommonSpot vs. Percussion CMS

Commonspot is well suited for web content management to be conducted by individuals with low-level web skills.

Incentivized

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

• I think CommonSpot's greatest strength is its ease of use. It's relatively intuitive in it's usage, so it therefore makes it easy to train new people to use it.
• Within my usage of it, our options were limited, which again added to it's ease of use.

Incentivized

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

Incentivized

• Commonspot needs to improve on its authoring feature. It is impossible to author on more than one page at a time . (One must always click on "View work on all changes") before switching between pages otherwise, the changes will not be saved.
• CommonSpot does not support sharing the definition of any custom element or any template layouts. Therefore, one must recreate these in each site.
• In Commonspot, a user who has to manage content in multiple sites will have to log in to each site to see and act on any actions.

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

I had no previous background in content management, and found it very easy to use. If I could figure it out, I am pretty certain that just about anyone else could as well.

Incentivized

Commonspot works in tandem with Zendesk very well to accomplish tasks an an efficient manner.

Incentivized

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

Incentivized

• I was working in a religious institution and based upon our usage and audience, there was no ROI to speak of. Our usage was more for providing information than having any type of interaction. In that instance, it worked very well.

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