We've been researching a new CMS (currently using Sharepoint) for nearly a year now and just started retroactively documenting our process. I thought I'd put a link to it here in case anyone is interested or may be going through the same process.
It's not all up there of course, I'll be adding content frequently though (at least that's the plan).
Hi Jason - I was going to post on your blog site but it would not allow me to enter comments . . . .
Anyway - interested in your project. We also have to update our CMS as ours is discontinued by the vendor (Serena Collage). Our IT group is implementing SharePoint 2010 for our intranet and there is quite a bit of pressure to use the same product for our website - already own the platform so we do not need to buy anything and they would only have to support one platform. I also have heard the many horror stories about SharePoint so have some concerns. One big difference is that we are using 2010 not 2007. My question for you is have you looked at an upgrade to 2010 as an option?
Thanks for your input.
SharePoint is not an option as a CMS. Don't believe me? http://doteduguru.com/id7800-results-higher-ed-cms-usage-survey-201... You WILL regret it in the long run, I promise.
I can make things real simple:
Ultimately, most of the vendor solutions are pretty equivalent, and it comes down to what will mesh with your environment best. Our research is a good starting place, but my Final Four make for a solid bet under nearly any circumstance.
We did check out 2010, briefly. Somewhat of the same situation, our IS team had started using Sharepoint 2010 for other uses and they brought it up a couple of times. 2010 does fix many issues that 2007 had, but it's still a beast, clunky and hard to expand. Even they admit that Sharepoint should not be used as a CMS. It's a collaboration tool, not for managing content.
Our IS team is behind a new CMS, they're even helping us in the proposal phase now while we get the purchase approved through committees. We have discussed what our fallback plan is, if the purchase of a new CMS isn't approved. Even then, we agreed that moving our site to 2010 wouldn't be a good option. We'd probably go open source before then.
I'll check in to the comments on Posterous.
We have had SharePoint (2007 and now 2010) since first quarter 2010 and have been using OmniUpdate's OU Campus as our CMS since third quarter 2006.
Both are outstanding products, and both fit extremely well together into a cohesive web solutions strategy for an institution.
-- SharePoint allows for powerful collaboration, communication, document workflow management and robust enterprise-level reporting, but is NOT your solution for web content management for a public-facing website.
-- OU Campus (OmniUpdate) allows for powerful web content management from any platform that can be reached/published to via FTP for any web content (not just a site, but data, etc.), but is NOT your answer for internal/external collaboration, enterprise reporting, etc.
If you had a .NET/Visual Studio web applications developer on staff that could customize SharePoint to the extent that it looks/acts like a normal website while still providing the enterprise interfaces behind the scenes, that person would quickly be snatched up by a consulting firm (your institution could not compete with the salary that person would be offered), and you'd be stuck with a hideous, customized beast of a system that would give you shakes and shivers in the night.
If you have any questions about how I've been using both SharePoint and OmniUpdate's OU Campus simultaneously to solve our institution's needs, I'd be happy to elaborate further (as well as to clearly delineate the functional and non-functional requirements that are met by both systems).
Webmaster | Victor Valley College
760-245-4271, ext. 2697
Funny you should mention that part about the staff, that's pretty much what happened here. One of our IS department employees was doing just that, customizing SharePoint to our needs. He left to start his own business (non-SharePoint related though). The director of the IS dept then started customizing SharePoint. Not too much longer after that, he left to work the employee that had previously left. So, SharePoint became that beast that no one could work on or knew what had been modified.
Now, SharePoint 2010 is used here for Team Sites and a few other things. We don't plan to have any carryover to the public site once the new CMS is in place. I would definitely like to hear more on how you use the two together!