Honestly, I have not had the time to move beyond 1-to-1 editing/publishing of static content into developing interactive solutions, although I am seriously exploring an XML export of real-time course catalog/schedule data from our main ERP system to provide a better online class schedule search interface...
I am hoping to have something started in test before the end of this calendar year.
SUNY Stonybrook already did that (using OmniUpdate) and their freshman catalog is now online (using XML/XSL) and is published simultaneously as XHTML and PDF each time it's updated. It's online at: http://sb.cc.stonybrook.edu/bulletin/current/
We've been using OmniUpdate's OU Campus CMS since October 2006.
Some of the features I like best?
Platform-independence (I can manage content anywhere, on any platform, with no issues...if you can FTP to a directory, you can manage the content within using OmniUpdate's CMS)
Simple to train non-technical users (For the last year and a half, I've been sending a simple 5-step, online training video I created to show end users how to manage their content, and I haven't had a need for an in-person training session since)
PEOPLE USE IT (one of my biggest frustrations with rolling out a new web service is when nobody uses it after I set it up and make it available...EVERYONE who tries OmniUpdate's CMS continues to use it and almost never call me with support questions)
Template set-up is simple (but you can get crazy powerful with it if you want)
What are my least favorite things about it?
it's not free (so I have to continue to justify the expense to management who are of the mindset that an open source CMS would be a superior option)
"OU Campus users and administrators: There are only two more days to vote for your favorite gadget ideas in the 2015 Gadget Challenge! Cast your votes by tomorrow, September 4 at 5:00 PM Pacific Time. The top five ideas will go on to the finals, so…"