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
DNN Platform
Score 9.0 out of 10
N/A
The DNN Platform (formerly DotNetNuke) is a free web content management systems (CMS) from DNN Corporation headquartered in San Mateo, California.
N/A
Pricing
Cascade CMS
DNN Platform
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Cascade CMS
DNN Platform
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Cascade CMS
DNN Platform
Considered Both Products
Cascade CMS
Verified User
Professional
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.
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.
DNN [Platform] is great for organizations of any size who wish to have a robust CMS to manage their site. DNN is not ideal for a small site that is better suited to a super easy to user interface such as Wix. DNN [Platform] is plenty strong enough for enterprises and large entities.
Very easy to use CMS - Ease of use is paramount with CMS products to minimise on support calls. Also the template structure of pages ensures that content editors cannot inadvertently corrupt the layout of the page.
Powerful application framework - The existence of APIs for all functionality within the CMS provides limitless scope in terms of developing bespoke applications which sit within the CMS.
Commercially supported option available - For larger clients, the comfort factor of having a direct line to the developers of the application is a big selling point.
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).
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.
My experience with Joomla! was over six years ago so a lot could have changed. However, I prefer DNN over Joomla because DNN offers more modules and a better administration user interface.
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.
DNN helps us win bids on projects through the improvements the community has done over the past few years; we were ready to scrap it all together but it has made great strides
DNN's community has come back and is actively working to improve and expand the capabilities of the cms
on a negative note, the confusion between evoq and dnn has caused us headaches