Cascade CMS vs. Divi

Cascade Server is well suited with it's WYSIWYG editor being better than most editors that I have used in other systems. In context, editing makes adding content easy compared to the last CMS I used where you had to wing it and view the page outside of the CMS to see if it was correct. The ability mix HTML, CSS, and the Script of your choice anywhere and with ease.

The scenarios were Cascade Server is less appropriate would be in the use of compilers or programs like Visual studio. You need to go out of Cascade Server and go to other environments to perform tasks and then copy the result to Cascade Server. You can write directly in Cascade Server, but it's easier to do in and editor that is specific to a function.

Incentivized

Divi is great if you build multiple websites for clients; however, I'm not sure it is cost-effective if you only make a single site.

Incentivized

• Cascade CMS makes no assumptions about your content. Templates control how the content gets displayed.
• Workflows are intuitive and allow for one or more people to review content before it is published.
• The published site is static (no database connection) which allows for faster page loads and reduced risk of attack.

Incentivized

• It has a very easy-to-use and extremely complete block editor.
• It offers many templates that you can use as a base for your website.
• Customer service has been fast and effective whenever I have needed it.
• Tiene un editor de bloques muy sencillo de usar y extremadamente completo.
• Ofrece muchas plantillas que puedes utilizar como base para tu web.
• La atención al cliente ha sido rápida y efectiva siempre que la he necesitado

Incentivized

• Cascade CMS is not an out-of-the-box pre-built system that you can install, turn on and expect to be serving sites and pages on day one. It's not a blogging system like WordPress, or a drag-and-drop system like SquareSpace (both of which I've used for their own purposes). You need to have someone tasked with management and system administration – and if you implement the on-premise self-hosted version, you ought to have several people. We have the university's IT shop handling infrastructure (server hardware, containers, clustering, operating systems, load-balancing, DNS, database servers, NAS/SAN drives), our Web & Design team managing Cascade CMS (system settings, sites, templates, permissions) and managers coordinating each respective academic unit (A&S, business, education, law, marine science).

• The load time of the builder could be faster. On some websites it takes a long time to load, and may crash the page. (I believe they've said they're working on this stability issue.)
• Warnings on updates if they're difficult for some sites to run. I have one website that has crashed more than once from Divi's theme updates. I always back it up before the update so I restore the site, but this is still a bit of an inconvenience.
• Integrated (or more clearly marked) tutorials within the builder. I migrate site maintenance and ownership to clients after the site is complete and some could use refreshers within the builder on what happens where i.e. the difference between a section, row, module.

Incentivized

Changing systems would require too much effort. Our institution is using Cascade Server, WordPress and Drupal but we only serve 2200 students so we have 1 too many content management systems. Reflecting on current technical resources we would like to drop down to 2. This effort hasn't moved forward because of the extensive work required to migrate content and train users in a new system.

Incentivized

Cascade CMS is completely usable on mobile devices, we can train our content editors in a single 2-hour session, and we support 1,000 users with a very small team.

There is a level of complexity for the system administrators, site managers and web programmers who implement templates and content types. But the complexity is neither arbitrary nor inconsistent – and once learned provides a powerful environment within which we can develop robust sites that are beautiful and powerful, yet easy for our content editors to manage.

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

Amazing customer service and VERY customizable.

Incentivized

Does a great job.

Incentivized

They have always regarded any question or problem we encountered as very important. We have never felt that they ignore or downplay any issue and not once has anything been left unresolved. They also hold an annual conference where users are invited to attend and share their experiences and wisdom with the entire Cascade community. And with the care and support the provide, we all feel a part of that community.

Training was helpful.

Incentivized

Still needed that physical help

Incentivized

The key to any CMS implementation is PLAN, PLAN, PLAN. Proper planning with Cascade can increase your satisfaction exponentially once the site migration/creation is complete. When all is said and done, your implementation can make your site run like a Yugo or Maserati. Be smart and deliberate in your decisions. Drive the Maserati. It is already paid for.

Incentivized

We selected Cascade server seven years ago, and the CMS environment at the time was clearly different than it is today. We decided to go with a vendor solution rather than a free solution because the long term cost in hosting a free solution is not, in fact, free; we've found Cascade to have been an excellent choice for us.

Incentivized

I find Elementor very clunky and find Divi much more intuitive.

Also we purchased a lifetime license for Divi and can use it on unlimited websites, while Elementor there is a yearly subscription per site

Incentivized

I used it only a few times.

Incentivized

• Initially, ROI was positive - because we completely redesigned the website when we implemented Cascade.
• Over time, the inability to keep up with the latest interactive tools has reduced visitors time on site.
• Also over time, the difficulty of use has led to less buy-in by backend users, leading to outdated pages, little timely information, and lower visitors.

Incentivized

• Higher conversion rate
• Theres no needed more tools
• Ive got rid of a CTA tool since with Divi i can make them. Is not that easy, but is functional

Incentivized