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.8 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
Pricing
Cascade CMS
Drupal
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Cascade CMS
Drupal
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Cascade CMS
Drupal
Considered Both Products
Cascade CMS
Verified User
Anonymous
Chose Cascade CMS
Cascade Server is miles ahead in usability and reliability. With DNN, I had to jump through hoops to add and edit content, and trying to customize was not easy.
Our latest round of CMS evaluations we looked at OmniUpdate, Drupal, and Wordpress as possible CMS choices. It quickly became apparent that all of the upper tier products seemed capable of managing strong websites, but upon a deeper investigation of our needs Cascade rose to …
Cascade CMS focuses on managing content and gives you the tools to display this content any way that is needed. While it may lack some features/extensions found in other popular platforms, the user management, workflow and template engine are the best you can get.
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 …
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 …
I didn't have any input when it came to buying/using Cascade server. In fact, before using Cascade I wasn't aware that such a website management system existed! I imagined it was going to be much more complicated--editing individual code and CSS page by page, with very involved …
Hannon Hill was chosen because of the architecture with the Cascade engine being separated from the published pages providing stability and security. The company is also focused on primarily higher education, the user group and feature set. The releases are always …
The version of Sitecore that I use right now doesn't have a UI showing the assembled web page. That suits my current company's needs, but for most people, they want to see their changes within the tool as they make them, visible within their web page. Cascade Server does that …
We felt the overall level of customization that Cascade Server allowed us was the deciding factor in our selection. Its users and groups management was also very robust and provided us a better system, and overall better access, for content managers in our organization.
In my limited experience with WordPress, I found it difficult to retrofit to use as a content managements system for a website. It's a great blogging solution and could easily be used to manage an organization's press releases.
Cascade Server was the software I was required to learn. I have no further experience or suggestions for this software, other than its usage in basic website development functions. AutoCAT software allows for immediate access to basic functions of design, as well as the …
Cascade was the College of Liberal Arts and the department's choice. I was a front-end user and web content developer. I know Cascade is widely used at the College and at other colleges and departments, but I do not know the reasons they selected Cascade.
Cascade is a significant improvement over WebCRMA in virtually all respects: more powerful and intuitive user interface, better multimedia integration, and a a greatly improved function set in terms of editing, reviewing, and publishing content. Although I did not play a role …
It wasn't my personal choice to go for Cascade Server for my organization. But as I already said, Cascade Server is good for managing parent child websites which are uniform in design. I guess the level up to which uniformity can be maintained and traffic can be handled by …
Cascade Server provides more formatting features. It pretty much provides all the features that a standard web service portal has and the website is written in complex programming languages such as c# or VB .Net, JAVA, J2EE, JSP etc. At the same time, Cascade Server provides …
Drupal excels at allowing seasoned programmers to really get creative with marketing initiatives in terms of working with a theme and the core code. That being said, it is definitely much more challenging for average developers and front-end builders to use, especially at …
Drupal has some advantages and disadvantages when stacked up against Wordpress,, including that Wordpress is easier to user for beginners and requires less training to get started. I noticed that while using Drupal, more help and assistance was needed from developers to make …
Director of UX development, social media and SEO/SEM
Chose Drupal
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, …
I inherited Drupal from a developer who made the website for our nonprofit many years ago. It was increasingly obvious that it wasn't a fit for our organization, which has multiple staff and volunteers who need to edit or update the website but don't have coding experience. Wix …
Drupal requires less to no coding abilities to spin up sites. Even if someone is preparing to develop sites that require technical know how then Drupal provides role based systems to seperate developers from content writers. Drupal 8 and 9 now have a vast array of plugins. Now …
WordPress for sure has a bigger community, a lot of paid extensions which sometimes is easier to purchase and get started, a lot of pre-designed templates to get you going, but nowadays with the scale of the projects we've been working with, and the need for custom-tailored …
We use both, for different projects (Joomla and Drupal). Drupal proved to be more robust, more secure and more integrable with PHP applications. Drupal requires a more senior technical team but allows for more complex activities. It's great if you have a medium to a large …
We first had a WordPress-based website, that evolved to a custom third-party developed content management system. In both cases, that involved additional costs for any change request, any security or any scalability need. WordPress didn't meet enterprise requirements. That also …
Drupal is community-backed making it more accessible and growing at a faster rate than Sitefinity which is a proprietary product built on .NET. Drupal is PHP-based using some but not all Symphony codebase. Updates for Drupal are frequent and so are feature adds.
Drupal is far more usable and stable than Joomla!, and the developer community support is significantly stronger. While Drupal is often compared to WordPress, they are fundamentally different platforms, and in most projects, it's very clear when the requirements are beyond what …
We have used many content management systems — WordPress, Wix, Squarespace, ExpressionEngine, and more. Drupal is more powerful and flexible than most.
We did a comparison of Drupal against Joomla, WordPress, and Ingeniux. We found that its multiple themes available for web pages, user management, comment management, and form generation stands apart from its competitors.
I've used Wordpress sparingly when helping a client with an existing website. I find it much less powerful and robust, and frankly confusing. The way Wordpress websites are set up in the backend doesn't make sense to me after getting used to how Drupal is set up. They're …
Drupal is really the only well-supported open-source CMS that is designed for large, data-rich websites. There just really weren't any good alternatives. There are plenty of CMSs that excel at small to medium-sized websites. But for a large website with lots of structured data, …
Although Drupal is not the most used, it has great performance and is more used in professional projects. It allows us to expand without starting from scratch.
Security-wise and traffic-wise Drupal is built to handle a lot. While the other platforms mentioned ( mainly Wordpress ) are great and have a large community, I would only use Drupal for an Enterprise level platform to build a website on. I first learned about Drupal about 10 …
Drupal supports lots of devices like Mac, Windows, Linux etc. easily, and it is an open source product so there's no cost required. Lots of other products require purchasing, costing a high amount. The support system of Drupal is also good in comparison to other products. The …
Drupal is certainly a more complex animal, comparatively. But its power lies in its flexibility, extensibility, and stability. And the API is fantastic. There's really nothing else like it.
I selected Drupal because of the simplicity upon going live. "Simple" is not the word I would use prior to the site going live though. I have used Jumla (which I believe was part of Drupal as one CMS about 12 or 15 years ago). Jumla is almost identical in capabilities to …
In my mind, Drupal and WordPress are the top open source CMSes, and I rarely recommend not going with an open source CMS. WordPress can be great, especially for single developers, but I find that the code structure and extensibility of Drupal makes it superior for many use …
I've used Squarespace and Wordpress for other businesses, and Drupal was honestly selected due to cost. It does a good job of scaling across our organization - and many units have benefited from having a space to provide content. Squarespace is more modern, and Wordpress may …
Drupal has strong role-based permissions for users, powerful content blocks for editing, and granular customizing options in their views. For a company or organization requiring a lot of customization, Drupal can be a really powerful tool. However, Drupal does require …
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.
We developed a corporate website using Drupal, which features a large number of static pages and several dynamic functions, including a contact us form, location finder, and job posting. We utilized Drupal with some customization to achieve the desired functionalities. We have also worked on e-commerce sites using Drupal, and there is a scope for improvements, specifically in cataloging.
Very easy-to-use. I trained over 200 users, and never once heard someone say that it was difficult to figure out. People generally left the training excited to get started managing their content.
Technology independent. We were able to put any language into it that our customers required: .NET, classic ASP, PHP, static HTML.
Customer Support. The Hannon Hill team was truly amazing when it came to helping their customers, including us. They always went above and beyond to fix issues, help customers figure out complex methods for using Cascade Server, and general support.
Annual User's Conference. This was a great event that brought Cascade Server enthusiasts together, and the entire Hannon Hill staff was present and available for customers to talk 1-on-1 with.
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.
Not much that I can add here, except that as a non-programmer, it can be a bit overwhelming to understand all the options and capabilities of the system. We have programmers who have been able to do almost anything we need with the system, but I can't understand it!
Security and new release notifications are a hassle as they happen too often
Allowing them to write PHP modules is a big advantage, but sometimes integrating them is a small challenge due to the version the developer is working on.
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.
I really like Drupal, and besides the one major issue with not being able to update from version 6 to version 7 and I am happy to continuing using it. Hopefully as time goes on they will make it easier to upgrade or provide better tools for mid-level web designers like myself to build out new sites without the help of expensive 3rd party's.
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.
It has a very steep learning curve. When starting with Drupal, the functionality and setup have to be learned, which is complex in comparison to tools like WordPress. Drupal is more powerful and can create a wider range of applications, but it definitely has a learning curve. I would recommend it to anyone who wants to make a dynamic web application bigger than the scale of a WordPress blog.
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 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%
Cascade CMS focuses on managing content and gives you the tools to display this content any way that is needed. While it may lack some features/extensions found in other popular platforms, the user management, workflow and template engine are the best you can get.
Drupal's capabilities outpace WordPress by miles. Drupal is more customizable, scales better for larger companies and has advanced content types. If you own a small business or work at a startup company, I would recommend WordPress but if your firm is trying to scale and you have more than 50 employees I would recommend Drupal.
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.
Drupal helped us launch a creative, marketing- and product-focused website with custom coding integrations tailored to our goals.
Drupal allows us to rely on secure and consistently updated core code.
Drupal's code taxing on the server does start to get a bit heavy as you go along with customizations, so at some point, we decided to stop. We want to ensure our Google Page Score remains high, including paying close attention to page load speed.