Thanks for your comments on selecting a webCMS. Like you, we are opting not to go with an open source solution. I agree, cheaper up front, perhaps, but we just don't have the technology support to effectively build from scratch. I would truly like to learn from your experience - and yep, got the 2008 wCMS report and find it very valuable. We've narrowed it down to 3 "finalists," Cascade Server, Ingenuix - which I note you selected, and OmniUpdate. We meet as a group next week to go over the research I've compiled in over the last 3 months and to have folks share their thoughts on the wCMS report summaries of each of these 3, although all but Ingenuix are at later and enhanced versions. Feel free to contact me at TL-North@wiu.edu or email@example.com. Thanks, tere
"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