Divi vs. Percussion CMS

Divi has cornered the market on a simple, straightforward WordPress theme that gives some major integrations and functions! Now that I've worked within it for years, I have a much better understanding of how robust a system it is. It takes some practice to get accustomed to but once you "get" it, it is so fun to use. I've shown so many small business owners how to use Divi and I feel that it is much easier to learn than other themes with functions that are controlled by coding or shortcodes. I could play in Divi all day, and some days I do, depending on which projects I am working on at the time

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

• Front end builder easy to design
• Exportable and importable layouts and templates
• Integration with wordpress and many plugins
• Individual template builder to apply to certain post types
• Add on cloud to store and sync your own designs, code snippets
• Can create your own api licenses for different websites

Incentivized

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

Incentivized

• Some advanced features need to be complemented with other paid plugins (e.g., attachments in contact forms)
• Certain Divi elements cannot be nested within other Divi elements (e.g., including an element within an accordion)
• Customizing the header is powerful, but making the most of it is more challenging than the rest of Divi's options

• 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

Divi is overall a great tool to use - I think I would need to spend a little more time to dig into the tool to provide more long term feedback.

Incentivized

Divi is a far better-looking and easier-to-learn system than Elements. While Elements has flexible columns and more compatibility with third-party systems (Crockoblock), it has a far steeper learning curve. Divi had a better pricing model and was easier to use to work at speed. We also felt it was far more client-friendly for self-editing.

Incentivized

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

Incentivized

• It's hard to quantify, but it's allowed me to create the face of my website, which currently receives tens of thousands of visits each month. This is largely thanks to Divi.
• It has allowed me to quickly design my own sales and product pages, without having to rely on third-party platforms.
• Divi's lock-in has made it difficult for me to explore other visual builders that might also be interesting for my website.
• Es difícil de cuantificar, pero me ha permitido crear la cara visible de mi web, que en este momento recibe decenas de miles de visitas cada mes. En gran parte es gracias a Divi.
• Me ha permitido diseñar en poco tiempo mis propias páginas de venta y de producto, sin necesidad de depender de espacios de terceros.
• El lock-in de Divi me ha hecho difícil explorar otros constructores visuales que también podrían ser interesantes para mi web.

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