Cascade Server vs Drupal

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

Read full review

• Content Types... these are amazing. Whereas a more simplistic CMS like Wordpress will basically allow you to make posts and build pages, Drupal 8 gives you the ability to define different types of content that behave differently, and are served up differently in different areas of the website.
• Extensibility... it scales, ohhhh does it scale. They've really figured out server-side caching, and it makes all the difference. Once a page has been cached, it's available instantly to all users worldwide; and when coupled with AWS, global redundancy and localization mean that no matter where you're accessing the site, it always loads fast and crisp.
• Workflows... you have the ability to define very specific roles and/or user-based editorial workflows, allowing for as many touchpoints and reviews between content creation and publication as you'll require.

Read full review

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

Read full review

• Drupal's admin side is very powerful and flexible, but it's a little bit harder to wrap one's mind around. If a customer is familiar with using a basic WordPress site, showing them the full Drupal back-end might be overwhelming and confusing at first. Luckily you can easily limit and customize the admin pages that each role sees.
• Drupal is huge and complex. Doing simple things is generally simple, but more advanced capabilities of Drupal have a higher learning curve (as can be expected). You can build a Drupal site quickly, but don't expect to build your dream site with loads of custom features in a week.
• Ready-made themes are more sparse than something like WordPress. If you're most interested in simply plugging an existing theme in and using it, you won't find as many professional-looking themes out of the box. There are some, but with Drupal, the best results are usually achieved by finding a good base theme and creating your own child theme based off of it.

Read full review

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

Read full review

• Our overall site traffic has grown exponentially since we have moved to it.
• We have been able to bring a standardized format to all of our resources and communications.
• Promoting new products is much easier due to the easy to use interface of Drupal, we can get a new product launch page up in record time compared to our old platform.

Read full review