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
Magnolia
Score 8.1 out of 10
Mid-Size Companies (51-1,000 employees)
Founded in Switzerland in 1997, Magnolia is a CMS used to build composable digital experiences. Magnolia helps create fully integrated customer experiences and speeds up digital delivery of content. Magnolia boasts 480 enterprise customers, thousands of Community Edition deployments, and more than 200 certified Magnolia Partners around the world. They further state that their enterprise customers include Sanofi, Generali, the Atlassian, The New York Times, Harley Davidson, and Union…
$3,500
per month
Pricing
Cascade CMS
Magnolia
Editions & Modules
No answers on this topic
DX Core
$3500
per month
DX Cloud
$6000
per month
Offerings
Pricing Offerings
Cascade CMS
Magnolia
Free Trial
Yes
Yes
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
Magnolia
Features
Cascade CMS
Magnolia
Security
Comparison of Security features of Product A and Product B
Cascade CMS
8.0
Ratings
1% below category average
Magnolia
8.1
Ratings
0% above category average
Role-based user permissions
8.00 Ratings
8.10 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Cascade CMS
7.1
Ratings
7% below category average
Magnolia
8.1
Ratings
7% above category average
API
7.00 Ratings
8.50 Ratings
Internationalization / multi-language
7.30 Ratings
7.70 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
Magnolia
8.0
Ratings
4% above category average
WYSIWYG editor
6.10 Ratings
8.50 Ratings
Code quality / cleanliness
6.00 Ratings
8.40 Ratings
Admin section
8.00 Ratings
8.00 Ratings
Page templates
9.00 Ratings
8.90 Ratings
Library of website themes
5.50 Ratings
7.00 Ratings
Mobile optimization / responsive design
7.00 Ratings
8.50 Ratings
Publishing workflow
9.00 Ratings
7.50 Ratings
Form generator
6.40 Ratings
6.90 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.
If you need a business CMS that brings along a good amount of features and also give you the chance to develop features on your own, Magnolia would be a good choice. Even if you have not the fitting infrastructure around, Magnolia provides you different ways like SAAS oder PAAS. If you have to review your code our have any problems the team behind will helps in a short time. Without using the connectors it is not so easy to connect special functionalities like Marketing tools or optimization tools. The DAM is very slow if you have an huge amount of documents and pictures to store for your website - you have to add an external DAM.
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.
Versatility of defining actions for custom handlers.
Reloading classes when code is modified in a local dev environment is nice. While it doesn't seem to work when changes extend beyond the method body (i.e., adding methods), it remediates the pain of long startup times.
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!
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.
Magnolia is an innovative CMS, for example it is possible to use the ipad to manage the contents. Magnolia’s team works hard to improve the product; the community is small but active and the support for the enterprise version is good. Magnolia’s team asks the users what they think and what they need, and the new functionalities planned for Magnolia 5.3 are very exciting for example the content personalization.
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.
There are a ton of small things that could make this CMS great Off the top of my head... 1) Better navigation between a component and its corresponding node in the jcr ( devs often have to flip between a page and a spot in the jcr even though there could be a button to take you from a page/component in the pages app to its location in the JCR) 2) Why does a content editor need to open the page to edit the page properties? They could just as easily edit the dialog from the tree view if they have many pages to touch, and it would save them time by not having to render the page.
It's a lean and performant platform. You don't need to put reverse proxy servers in front of it to speed it up (although that does make it go even quicker) as there are various layers of caching built in to the application. While it's a little cryptic, the internal caching system is actually quite configurable and can be tuned to the right sort of content.
Often what tends to surprise many an IT manager is that you can run it on relatively modest hardware. We've often been met with "are you sure ?" but the reality is that it doesn't need a whole lot of horsepower.
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.
You always get an answer based on your SLA. But you always get a solution. That's the successfactor in this case. To often i was frustrated about people in a company without even a clue what there product is about or how to solve a problem. Magnolia's Support Team does a very good job and try to help you in most of the cases
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.
Magnolia DXP offers similar or more capability compared to the other platform, while much easier to implement. For example, Adobe Experience Manager tend to be more monolithic in nature, heavier footprint compared to Magnolia. Hence when implementing a DXP, it is much faster to build using Magnolia, at a much lower TCO. The other platform like Kontent.ai and Strapi are pure headless platform and offer lesser features. What really make Magnolia different is the APAC team, who are all out to support their client in the implementation, ensuring their client maximize their platform and the project implementation is successful. This is some thing that is not experienced when using other platform(s)
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.
We have placed web content management in the hands of the organisation than retained it within the technology team.
We were able to quickly move to MVP and release and we are now focussed on moving the platform forward at some pace whilst not being burdened with BAU work inside the technology team as so much as self-service to trained organisational users
The use of the SAAS/PASS has inbuilt business resiliency as specialist work and aspects such as underlying security is done by Magnolia and we are able to focus internal effort on building out the platform.
