"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…"
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…"
"Hey Charlie, good to see a familiar face on yet another Cascade support forum. We're still ramping up 17 test sites (and counting) in Cascade 6.7.5 and getting ready to launch them. We're calling it project tidal wave."
"The Texas A&M IT department has 10+ sites running Analytics. We're still comparing it to Awstats and NetTracker for ROI on campaigns. The university's Marketing and Communications department operates a Google Search Appliance;…"
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?
"Thanks - I appreciate it! It was a lot of "new" for us. Personally, I'd done a little bit of responsive design (took a class) but nothing at this level. I'd not done HTML5 or really delved into CSS3 and then finding…"
Position SummaryThe School of Engineering and Applied Science (SEAS) in the midst of an exciting period of growth in its capacity to prepare leaders and solve societal problems, and seeks a web developer for the large-scale project of moving the Schools current website to a more modern platform. Reporting to the Director, Engineering Communications, the primary role of the web developer is to setup and build the framework for the new website (utilizing Drupal). The person in this position will…See More
The Albert S. Cook Library seeks a highly skilled and innovative Web Services Specialist to participate in all stages of the application development life cycle. Under the direction of the Information Technology Librarian, this position provides primary web application development support for the Library’s online initiatives. Focusing on services that improve the user experience for the University’s students, faculty, and staff, the Web Services Specialist collaborates with team members, other…See More
We launched a redesign of our site on July 1. It was more than just a new skin, it was a reorganization of the content. In the past we've tried to serve all audiences - current students, prospects, staff, faculty and alumni. It ended up being link overload. It also used internal back office terminology that was confusing to prospects.Our charge was to gear the site toward prospective students and to move all content for current students and faculty & staff behind our existing portal.We…See More