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
OU Campus
Score 9.2 out of 10
N/A
OU Campus from OmniUpdate is billed as 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.
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.
OU Campus is the best CMS product I've seen, especially when you have a large organization with less staff and resources. Also, its power, if one team likes marketing, handles all pages and that saves a lot of time and effort. I strongly like the components/snippets. Tags all dynamic modules.
The JustEdit feature makes updating content a breeze. With a small staff, we rely on others to update their content. OU Campus makes it easy.
Site-wide find and replace. I use the site-wide find and replace feature for all sorts of things - links, enrollment numbers, department names. It's really helpful.
Customer service. The staff at OU Campus answers questions quickly and is always willing to discuss the most effective ways to take on new projects.
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).
Formatting. The page can sometimes look very differently when published than what it looks like while editing. Some improvements have been made in this area with version 10 however.
Find and replace. The command+F needs to find text on the page while editing, not present an actual find and replace dialog box. At least give me the option to simply "find" the text I'm looking for. The dialog box just gets in the way most of the time.
There is not a way to "unpublish" items. At least not a way that I can think of. I would like the ability to pull a page offline without deleting it. Seems like it should be done simpler.
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.
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.
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.
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 created/maintained. OU Campus Content Management System solved all problems for us.
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.
