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
Clickability (discontinued)
Score 7.0 out of 10
N/A
Clickability was a content management system acquired by Upland Software in 2013 which provided a SaaS platform for web content creation, management, publishing, analytics, digital marketing, and online publishing for marketers and enterprises. It has been discontinued, and is no longer available.
N/A
Drupal
Score 7.0 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.
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 …
I think it is on par with what I did with Sharepoint. Sharepoint was not the easiest and you have to do many things twice to get it to actually display. I think the easiest I have used is Wordpress. They make mobile very easy and allow for quick changes and are very social …
Verified User
Former Employee
Chose Clickability (discontinued)
I have mainly worked with open source content management systems like Wordpress, Drupal and Joomla!. Clickability is far more customizable and elegant to code things yourself. The main downfall of Clickabliity is the lack of community developed modules and plugins. If there …
Drupal
No answer on this topic
Features
Cascade CMS
Clickability (discontinued)
Drupal
Security
Comparison of Security features of Product A and Product B
Cascade CMS
8.0
19 Ratings
2% below category average
Clickability (discontinued)
6.9
5 Ratings
17% below category average
Drupal
8.1
74 Ratings
1% below category average
Role-based user permissions
8.019 Ratings
6.95 Ratings
8.174 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Cascade CMS
7.1
13 Ratings
9% below category average
Clickability (discontinued)
6.5
3 Ratings
18% below category average
Drupal
7.6
69 Ratings
2% below category average
API
7.012 Ratings
5.13 Ratings
7.264 Ratings
Internationalization / multi-language
7.37 Ratings
8.02 Ratings
8.160 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
Clickability (discontinued)
6.7
5 Ratings
15% below category average
Drupal
6.5
78 Ratings
18% below category average
WYSIWYG editor
6.119 Ratings
6.85 Ratings
6.171 Ratings
Code quality / cleanliness
6.018 Ratings
6.05 Ratings
8.175 Ratings
Admin section
8.019 Ratings
7.04 Ratings
6.878 Ratings
Page templates
9.017 Ratings
7.04 Ratings
5.577 Ratings
Library of website themes
5.52 Ratings
5.93 Ratings
5.468 Ratings
Mobile optimization / responsive design
7.015 Ratings
5.94 Ratings
6.572 Ratings
Publishing workflow
9.019 Ratings
7.95 Ratings
6.876 Ratings
Form generator
6.47 Ratings
7.01 Ratings
6.372 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.
As a true content management system it is great for site and content creation. It does need some help when it comes to adding functionality for using modern code systems that require server side scripting. For a marketing or public company site, it is an ideal CMS. For a SAAS type site, there could be many road blocks.
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.
Easy to get going for a business that has tons of content they need to manage.
Clickability offers development and design services so you don't really even need IT.
No need to worry about server uptime, storage, bandwidth, etc you have all the reports at your fingers for what you are using.
Simple template and content design system, easy to expand and add.
Powerful CMS and settings with a design and programming guide provided.
AkAMAI and Limelight CDN's can be used for powerful and fast loading in many regions.
Debugging tools to see how long specific templates and content load is exceptional. One can narrow down that this specific template ran X number of times and took this look and had to be stopped at X number of time due to exceeding set limits.
Having a built in Dev, Staging, Production environments for testing makes seeing new features and how they will integrate into your site seamless.
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).
Choosing ad size/placement should be easier than it is. Now, I have to re-create the whole thing.
When you "save" anything a pop-up comes up that is redundant.
Ad list only shows a limited number. It's not until you click on one and cancel it out, then you can see all the listings. A bit tedious and redundant.
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.
As mentioned in the last questions we are going to use a competitor brand next year. I think the issues are trying to find and fix problems from the previous programer. The steep learning curve and lack of mobile and social sharing capabilities. Things that I like are the strength of the programing which comes with a trade off. The ease for those who don't know markup to make updates to the website. Clickability isn't the easiest and can be difficult to find the content that you are interested in. We will not be using it next year.
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.
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.
My experience with Clickability has been mostly positive but there are a few areas for improvement. It's generally easy to learn and use on a daily basis. I can move fast and do my job with speed with needed. But there is some clunky functionality with targeting and page building. My rating would be higher if some improvements were made.
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.
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.
I found that some agents were better then others, usually you have an account representative and that I would consider level 1 support. To get really complex answers you need to talk with an engineer.
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%
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.
Many of other content management systems similar to WordPress need custom installation. The server costs and upgrades quickly add up. Clickability while expensive, eliminated the overhead of managing all the dependency needs for a CMS. Clickability also works with its clients to understand the business needs and proposes the solutions accordingly. They have a good support team.
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 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.
I know a big positive is the fact that it is always-on. We are the leading news corporation for our state, and in many markets, nationwide. We pride ourselves on our strong ethics in the community and thus need to exude reliability to maintain the trust of these communities. Having a website fail periodically erodes that reliable perception.
It has allowed different areas of the company to approach our team and work in a cohesive manner.