Cascade CMS (formerly Cascade Server) by Hannon Hill is a content management system, with built-in tools to help users eliminate stale content, increase digital outreach, and promote end-user adoption and accountability. Cascade CMS is designed for decentralized web teams in most major industries, including higher education, government, healthcare, and technology.
Included is Clive, an engagement and real-time personalization tool for collecting information and using it to craft personalized…
N/A
Drupal
Score 6.7 out of 10
N/A
Drupal is a free, open-source content management system written in PHP that competes primarily with Joomla and Plone. The standard release of Drupal, known as Drupal core, contains basic features such as account and menu management, RSS feeds, page layout customization, and system administration.
N/A
Evoq Content
Score 8.7 out of 10
N/A
Evoq Content is a content management system within the Evoq business suite. Evoq Content is extensible with many modules that add caching, advanced content approval workflow, granular permissions, document management, mobile accessibility of content, web farm support, and an ecommerce engine.
Because the (bad) Cascade decision was made quickly by a small team, we have a larger team and a longer timeline, with a growing list of functionality that we expect a replacement system to have. We've been looking into a number of other products to replace Cascade. Highest on …
WordPress was never evaluated when we decided on Cascade around 2008. We looked for an enterprise level system that would have vendor support and had more developer resources at the time. Our resources have diminished so having plugin solutions like WordPress would solve many …
We knew we didn't have the department size (i.e., human resources) or time to work with open source products like Drupal and Joomla, and while we still use WordPress for offshoot blogs by some departments and programs, we needed a more robust CMS that would centralize design …
We selected Cascade Server because it manages users more easily. It also requires less coding skills than MS SharePoint does. Drupal on the other hand is freeware so your user support for Drupal is what you would get for not paying for something. Cascade Server dumbs it down …
Drupal has the best community and support system of any other CMS that I have used. Drupal is more flexible from A-Z including installation, building and customizing the CMS. The only other (free) CMS that is close, in my opinion, is Dot Net Nuke.
Drupal is a highly expensive tool and is not offering anything extraordinary at a high price. If I keep its pricing in account then there should be some extraordinary features but unfortunately, there isn’t anything special about it; rather it was slow in its working. All these …
A few products stack up against DNN like Wordpress, Drupal, SharePoint. Drupal, Wordpress, Joomla all are php based systems, while DNN, SharePoint were all .NET systems which is what I preferred. Comparing SharePoint to DNN, first would be the cost of SharePoint server along …
Features
Cascade CMS
Drupal
Evoq Content
Security
Comparison of Security features of Product A and Product B
Cascade CMS
8.0
19 Ratings
2% below category average
Drupal
8.1
73 Ratings
1% below category average
Evoq Content
10.0
6 Ratings
20% above category average
Role-based user permissions
8.019 Ratings
8.173 Ratings
10.06 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Cascade CMS
7.1
13 Ratings
9% below category average
Drupal
7.6
68 Ratings
2% below category average
Evoq Content
10.0
5 Ratings
25% above category average
API
7.012 Ratings
7.063 Ratings
10.05 Ratings
Internationalization / multi-language
7.37 Ratings
8.159 Ratings
10.05 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Cascade CMS
7.1
19 Ratings
9% below category average
Drupal
6.4
77 Ratings
20% below category average
Evoq Content
10.0
8 Ratings
25% above category average
WYSIWYG editor
6.119 Ratings
5.970 Ratings
10.08 Ratings
Code quality / cleanliness
6.018 Ratings
8.074 Ratings
10.06 Ratings
Admin section
8.019 Ratings
6.577 Ratings
10.07 Ratings
Page templates
9.017 Ratings
5.776 Ratings
10.07 Ratings
Library of website themes
5.52 Ratings
5.667 Ratings
10.06 Ratings
Mobile optimization / responsive design
7.015 Ratings
6.571 Ratings
10.05 Ratings
Publishing workflow
9.019 Ratings
6.775 Ratings
10.07 Ratings
Form generator
6.47 Ratings
6.271 Ratings
10.06 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
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.
If you want to set up a basic Not For Profit (NFP) Membership system and content base, Word Press is easier than Drupal. However, if you have specific needs that require a fair bit of customisation then Drupal is the best CRM available. If the webmaster is confident with PHP and SQL, Drupal allows a lot of creativity.
If you just need to implement a website that is dynamic but not real big in Data Processing almost anyone can do so with very limited knowledge as long as you know how to use a Word Processor and your Browser. If you don't have experience with setting up a Server to run a website there are Companies like PowerDNN, Rackspace and WinHost that can help and I recommend them in that order if you are using DNN. If you need a more sophisticated e-commerce website and don't have much experience with Servers, SQL Server etc. then you should find a consultant to help you install and setup not just the DNN Platform but also select the proper Modules to accomplish what you want to do. If you need a highly customized website that is very data intensive and you are not experienced then be sure to save yourself the time and money by finding a qualified Consultant to help you. The beauty of DNN is that it can handle as simple or as complicated of an Application as you need depending on what your needs are and how far you want to take it.
DNN is a feature-rich, open-source project with a flexible license. This let us use it without licensing costs for custom solutions or as-is with no custom code just plug-in modules.
DNN is written in Microsoft .NET C#. This allows our developers and our customers to use their existing skill set to install and maintain the solution.
DNN is made for Windows platform, allowing us and our customers to deploy solutions to existing Windows servers or in some cases hosted platforms.
DNN integrates with Windows authentication allowing us to deploy intranet solutions and use single sign-on for improved user experience and security.
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).
This is not an easy CMS to work with if you don't have a good understanding of website development. It isn't "plug-and-play" like Wordpress or Shopify.
Over time, doing major updates to the system can be taxing, especially if you aren't well-versed enough in doing system updates in line with your "child" theme and code.
The CMS can become somewhat cumbersome with server resources if not carefully optimized while you build and customize it to your liking.
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.
The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.
Even though DNN is a good CMS, I have worked with other CMSs which are far more robust at this point, and would not be overly inclined to select DNN unless cost of the product is the most important factor along with staying on .NET. DNN is a whole package so unless the client has a requirement of including authentication, authorization for users, eCommerce, sticking to something simple is a better option.
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.
As a team, we found Drupal to be highly customizable and flexible, allowing our development team to go to great lengths to develop desired functionalities. It can be used as a solution for all types of web projects. It comes with a robust admin interface that provides greater flexibility once the user gets acquainted with the system.
Evoq proved to be a solid backbone for our property-management portal, handling ≈300 active rental listings without performance hiccups. The page-builder made it straightforward to craft listing templates that surface photo galleries, floor-plan PDFs, and embedded map pins, while role-based workflows let leasing agents edit unit details (price, availability, pet policy) without touching global site settings—a big win for operational control.
For the management side, the platform’s extensibility let us plug in a third-party rent-payment widget and an automated maintenance-ticket form with minimal custom code. Evoq’s built-in analytics have already highlighted which neighborhoods and bedroom counts drive the most traffic, guiding our marketing spend.
Two caveats:
Search & filter logic – Out-of-the-box search was too shallow for renters who expect Zillow-style filtering. We had to commission a custom module for filter chips (price range, amenities, walk score), which added time and cost. Mobile image optimization – High-resolution gallery images affected load times on 4G; a CDN or Evoq’s Digital Asset Optimizer add-on is advisable.
Overall, Evoq delivers reliable content governance and enough flexibility to support both consumer-facing listings and back-office property-management workflows, provided you budget for advanced search customization and image delivery tuning.
Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).
Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.
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.
As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.
I don't see how it could get any better unless they moved their staff into our offices. You have available to you any type of Support you need or want, both paid and free from thousands of developers and consultants all over the world. You might even find some on Mars if you look hard enough.Also, with all of the available resources available from your Browser you can literally find the answer to any question you have in a matter of minutes.
I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.
The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.
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.
Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%
Evoq proved to be a solid backbone for our property-management portal, handling ≈300 active rental listings without performance hiccups. The page-builder made it straightforward to craft listing templates that surface photo galleries, floor-plan PDFs, and embedded map pins, while role-based workflows let leasing agents edit unit details (price, availability, pet policy) without touching global site settings—a big win for operational control.
For the management side, the platform’s extensibility let us plug in a third-party rent-payment widget and an automated maintenance-ticket form with minimal custom code. Evoq’s built-in analytics have already highlighted which neighborhoods and bedroom counts drive the most traffic, guiding our marketing spend.
Two caveats:
Search & filter logic – Out-of-the-box search was too shallow for renters who expect Zillow-style filtering. We had to commission a custom module for filter chips (price range, amenities, walk score), which added time and cost. Mobile image optimization – High-resolution gallery images affected load times on 4G; a CDN or Evoq’s Digital Asset Optimizer add-on is advisable.
Overall, Evoq delivers reliable content governance and enough flexibility to support both consumer-facing listings and back-office property-management workflows, provided you budget for advanced search customization and image delivery tuning.
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.
Drupal can be more complex to learn, but it offers a much wider range of applications. Drupal’s front and backend can be customized from design to functionality to allow for a wide range of uses. If someone wants to create something more complex than a simple site or blog, Drupal can be an amazing asset to have at hand.
Drupal is a highly expensive tool and is not offering anything extraordinary at a high price. If I keep its pricing in account then there should be some extraordinary features but unfortunately, there isn’t anything special about it; rather it was slow in its working. All these things actually forced us to move to Evoq that is just perfect in its working. Its working speed, interface, and UX are so simple that none of our team members find it tough to utilize. It has so many features like content scheduling and rich text edit. It allows easy editing of the text as well, and one can directly add text according to need.
Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.
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.
DNN have given us the ability to have basic sites for clients up and running in a very short time. This makes the client happy.
DNN has taken the trivial, simple tasks of changing text on a page or an image on a page and put it into the hands of the client. They do not have to pay us to do it and that also frees up more time for us to spend on development.