Daniel15, on 25 March 2012 - 09:52 PM, said:
I'd try CMS Made Simple. I used it years ago and it was pretty nice (a lot
easier than Mambo/Joomla was at the time), it's probably even better these days.
Umbraco is also great if you're willing to host in a Windows Server environment (as it's .NET-based). It's used by several big companies
(including Microsoft themselves).
I'll be sure and check those out, thanks! The university is almost fully a Windows shop, so going with a .NET-based CMS would be very future proof, as the main IT staff would be able to assist if anything was needed (there's only a handful of Linux guys, and their services aren't available to individual departments) and they weren't lucky enough to have another technologically-inclined student to fund at subsidized wages.
Okay I just posted on Neil's exactly similar question. Basically Wordpress is the biggest cms, then you could move over to Drupal or joomla both also in php.
Wordpress is definitely one that I'm thinking about, however I've heard stories of how involved updates/upgrades are. Is this true? If so, WordPress is out. Once I leave, I'll be lucky to teach someone step by step directions to get to an update button. Let alone teach them the nuances of a tricky upgrade, and how to rollback in case of problems..
Locomotive is fun and uses rails, little harder than Wordpress because of lack of add ons, though I never used any. Lastly blogging wise of you hate my others then have a small section of your site just for the blog. I gotta promote wheat here, I've used it and it's a cool node.js blog engine. Not supper complete but crazy fun. Calipso is a cutting edge of new cms that is also in node. Yea I like node but what ever you choose have a mobile site also.
Cutting edge is a no-no. These people are using Dreamweaver and FrontPage at the moment, with broken links galore. If I ever leave and they don't have someone tech-savvy around to coddle them through upgrades, etc; they'll simply revert. And revert while still having an older, insecure version of the CMS running.
I tend to use modx for a lot sites. It's more of a build it yourself type than Drupal or WP. AI the learning curve is higher but yet gives you lots of freedom.
This has crossed my path as an option. It seemed simple enough to do what most professor's will want to do with it, while allowing the flexibility necessary for someone more competent to customize when needed.
You could always build something with YIi or other favorite flavor framework. But this all depends on how much commitment you want to make.
My actual designation is a teacher's assistant for a class. The website stuff has just been thrown at me once they realized I had a modicum of computer skills. So I want to minimize my commitment. I consider switching over to a CMS system a good investment for minimizing my commitment, as most of what I'm asked to do are arbitrarily easy if the requester only knew how to even access the content.
Why you leave them with will affect what that will have to go through once you leave. Go with something relatively unknown they are screwed. At least with a framework they can back track through what you did, but that could be a hassle too!
This is something very important to me. Even with a framework they'd be screwed. The university provides Dreamweaver templates for departments to use (mandated, actually - unless you modify external software to mimic the templates). So once I left, they'd have limited resources to work with. OIT (main IT guys) would just tell them to use the standard Dreamweaver templates, rather than help fix anything. I have no intentions on leaving anytime in the foreseeable future, and may even transition to a full time staff position taking classes on the side (for free) within the next few months. But regardless of my tenure there, the system needs to be fairly self-sufficient. Something too customized isn't.