We evaluated T4, OmniUpdate, and HannonHill. T4 had cloud issues and wasn't available most of the time. OmniUpdate was promising, but it is push and pull technology. We thought that would be too much traffic. Also, I don't think OmniUpdate had a good, basic role system that integrated with our CAS authentication.
You should know I'm still learning Cascade 6.7.5.
It's XML/XSLT driven for a lot of functionality - like indexing assets. I didn't know XSLT before we started using Cascade, but I'm learning it. I like that users can globally share and reuse assets. That being said, the roles and permissions can be an issue at first; admins need to learn their abilities in the system as much as users need to find out their abilities. It took us about 2 months to find most of what we could do and what we couldn't do and what admins had to turn on for us.
Some of what I don't like is probably attributable to the built-in TinyMCE editor: it fixes HTML trying to make it valid; it alters some valid PHP making it invalid; most of the features of TinyMCE are off by default.
I'd recommend getting an evaluation licence and everyone starts as admins so you can see where links are and what things do. Then, when users are divided into roles and they loose some functionality, they know how to communicate to the admins as to what it was they lost. We did that plus we got the 3 day on-site training for users and admins.
I am new to uwebd and looking for insights into Cascade. Our university has a home grown CMS and we are planning on replacing it. Hannon Hill's Cascade is one of the products we are reviewing. What features do like best that you find really useful and not on most other CMSs? What are your least favorite things about the product?
"There’s a high school student who is a great fit for your institution, yet never engages with your institution online and enrolls elsewhere. Why? Find out during our next webcast with Lance Merker as he dives into the 2018 E-Expectations Trend…"