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
Progress Sitefinity
Score 7.6 out of 10
N/A
Progress Sitefinity is a content management and customer analytics platform. It supports content management, tailored marketing, multi-channel management, and ecommerce sites.
N/A
Pricing
Cascade CMS
Progress Sitefinity
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Cascade CMS
Progress Sitefinity
Free Trial
Yes
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
Yes
Yes
Entry-level Setup Fee
Optional
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Cascade CMS
Progress Sitefinity
Considered Both Products
Cascade CMS
No answer on this topic
Progress Sitefinity
Verified User
Director
Chose Progress Sitefinity
This was already implemented when I arrived here but have looked into moving it to another platform. The time involved in doing that is just not worth the time right now. Sitefinity does what it is supposed to but it's not the most user friendly and support is not very good.
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.
Progress Sitefinity remains a little heavyweight for sites that require basic text content, or a limited number of pages. However, its flexibility (including the range of different content types if supports) make it a good choice for any organization requiring advanced content management capabilities at an affordable price.
'Low-code structured content' (dynamic content types) is one of Sitefinity's most powerful features that allows you to structure content according to business needs, while at the same time dampening editorial freedom to ensure accessibility, meta enhancement, SEO and API consumption can be achieved.
Sitefinity's content provider model allows us to flexibly (by means of admin interface) easily aggregate or separate content sharing within a multi-site instance.
This proofs particularly powerful in emerging situations where there suddenly is a demand for content sharing across countries or regions.
Adaptability at its core.
While there's never a perfect fit for everything, it allows for easy code customization and extension being a .NET application at heart. Giving it a corporate edge over other custom solutions, whether it is on the development side or deployment side (on premise, IaaS or Azure DevOps Paas). And it has enabled us to put the system to use in its core feature - which is to manage content, where on other occasions we were able to take full advantage of its features such as A/B testing and personalization.
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).
Diagram or illustrate more use cases for server setups, and managing of upgrades.
I'd like to see the ability to synchronize from one server to multiple others at once.
Implementation assistance as part of the purchase rather than farming out to 3rd party, although they did answer every question we asked in order to determine our best architecture setup.
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.
Very big fan of this CMS, as it allows scalability, performance, and everything else. The support is great whenever we need it. As a marketer, the digital/marketing side of things is very easy to use and we've seen strong results from an SEO and marketing perspective. I can't speak to the developer/creative side too much, but in talking with these teams, they do recommend the tool as well.
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.
Support can be pretty good, even though, depending on the level of licensing, it can take longer to hear back from their team. They do have a phone option, which works well. Overall, they are knowledgeable, and helpful when needed. At times, support is able to access the system directly and troubleshoot critical items when needed.
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.
N/A - I was not part of the implementation team. We have had this internally for over 5 years. Based on my experience, ensure that you have documentation on the initial implementation and subsequent upgrades. I would also recommend to have all the documentation on how and why the system was implemented the way it was
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.
It is hands down just easier for our customers to use. The interface and the page builder experience is much better than what we have used in the past and has many enterprise features even in the lower price-point
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.
