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
Modern Campus CMS
Score 9.2 out of 10
N/A
Modern Campus CMS (formerly Omni Campus) is a CMS for institutions of higher education. It can be deployed as a cloud-based service or hosted locally. It is built in Java, uses open standards, and is extensible through APIs.
N/A
Pricing
Cascade CMS
Modern Campus CMS
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Cascade CMS
Modern Campus CMS
Free Trial
Yes
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
Required
Additional Details
—
—
More Pricing Information
Community Pulse
Cascade CMS
Modern Campus CMS
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 …
During the RFP process, we also evaluated Hannon Hill Cascade and Terminal Four. Both CMS systems had pros and cons, but overall, OU Campus was an easy choice. The features were better, non-technical users liked the simplicity of the interface, and the price was competitive.
We selected OU Campus after reviewing a number of CMS products and are extremely happy.
Verified User
Anonymous
Chose Modern Campus CMS
Before using OU Campus Content Management System we were using Adobe's DreamWeaver suite for creating and maintaining web pages. The core web development environment was cumbersome to set up. Non-tech people also had trouble understanding how the web works and how web pages are …
I don't know how OU Campus stacks against other products because I have been using OU Campus while I have been employed at my university.
Verified User
Anonymous
Chose Modern Campus CMS
MUCH easier to use than other CMS systems. Quite intuitive. Pleasant interface. Reduces anxiety for beggining users of cms system, and supports stronger users comfortable doing more.
I have evaluated Ektron, PHP Nuke, Drupal, Joomla!, typo3, Reason and SharePoint. OU Campus outshines all of these in the web CMS space. The OU Campus interface is more intuitive, more user-friendly, and the system itself is more flexible and scalable and capable in almost …
Features
Cascade CMS
Modern Campus CMS
Security
Comparison of Security features of Product A and Product B
Cascade CMS
8.0
Ratings
1% below category average
Modern Campus CMS
10.0
Ratings
21% above category average
Role-based user permissions
8.00 Ratings
10.00 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Cascade CMS
7.1
Ratings
7% below category average
Modern Campus CMS
9.3
Ratings
20% above category average
API
7.00 Ratings
8.60 Ratings
Internationalization / multi-language
7.30 Ratings
10.00 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Cascade CMS
7.1
Ratings
8% below category average
Modern Campus CMS
8.9
Ratings
14% above category average
WYSIWYG editor
6.10 Ratings
9.20 Ratings
Code quality / cleanliness
6.00 Ratings
9.20 Ratings
Admin section
8.00 Ratings
9.20 Ratings
Page templates
9.00 Ratings
9.60 Ratings
Library of website themes
5.50 Ratings
10.00 Ratings
Mobile optimization / responsive design
7.00 Ratings
8.80 Ratings
Publishing workflow
9.00 Ratings
9.20 Ratings
Form generator
6.40 Ratings
6.00 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.
This website works well in an academic setting. It's easy to add pages as your site expands/grows. It's really easy to use and modify pages once you know what you're doing, but it can be a little tricky to get the hang of it at first. It is definitely useful to have in-person or virtual training before you dive in.
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.
Assets are easily managed and can be edited independently of the page they exist on.
Version history is handled well. Allows for a comment section to note what changes have been made.
Dependency tags are perfect for media that is used in several places. Upload a photo once, use it in multiple places, edit the photo or its description in one place.
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!
OU Campus could use some improving on their upload changes as far as naming the document because when you are trying to upload the same document with minor revisions, OU Campus requires you to change the name of the document within OU Campus which creates multiple documents in the workfolder.
When naming documents to upload into OU Campus, it would be nice if we could name out documents the way we would instead of having to put an underscore to indicate a space in the document. Most users of OU Campus has not had proper training to know that you need to do that.
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 don't work at the college any longer, but I believe they will renew the license for the OU Campus Content Management System because of all the great benefits they have had since they initially deployed it. The system is very intuitive and easy to use. Department leads love it. The IT department also loves it because it saves them a lot of time and resources.
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.
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.
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.
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.
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.
Increased satisfaction with user experience. OU Campus has made it easier for us to address problems when they arise, making our website more efficient.
Role-based control. Our old CMS made it very easy for users to change fonts and colors on their sections, which was very detrimental to the overall brand. That's not a problem anymore.
Reduced training times. OU Campus is so easy to use, I've been able to cut training times down by half.