Content Management System
In 2005, the current Content Management System (CMS) in use, Adobe Publishing Server, was installed for the maintenance of the College website. This software provided a streamlined approach for departmental webmasters to access and to maintain their sites through the use of our campus network identification system (LDAP).
As the Web Communications industry has changed over the years, so have strategies – from both a technical and marketing perspective. Reflecting those changes have been an increase in departmental campus web usage, the addition of two web resource positions (Web Content Manager, Media Specialist), and the expansion of the Web Team to include representatives of the Public Relations and Admissions departments. A major highlight of change, however, was the 2009 redesign of the College website, resulting in the launch of a new, uniform look and feel, and perpetuation of a web marketing strategy.
To the contrary, Adobe Publishing Server has not been maintained by the vendor to accommodate the advances in the Web Communications industry. There have not been any subsequent upgrades in the software, and this CMS has since been retired by the vendor. As a result, campus webmasters have been subject to software downtime and lagged performance. A number of Contribute-related problems (on campus) are reported in any one day – hindering business processes. There has also been an overall unreliability with the software when attempting to maintain websites while off campus.
In addition to the in-house technical problems imposed by the software, the CMS is incapable of taking advantage of the newest features offered through the latest advances in technology, including 1) integration with social media tools such as Facebook, Twitter, and others, 2) an automated Mobile presentation – which would serve approximately 20% of those accessing our website, and 3) built-in Search Engine Optimization (SEO) optimization tools, among other advancements. Our website management infrastructure as it exists is out of date, and incompatible with the technologies offered today. It can neither partake in, nor compete with today’s leading web marketing strategies.
The web team ascertained that we needed to find a robust CMS that would facilitate our current web maintenance efforts and manageability, while providing a competitive web presence given the current and future state of web technology.
The web team selected a number of vendors, both open source and proprietary, creating a matrix that evaluated cost and product feature, as well as on campus resources and personnel.
After careful consideration, the web team came to the conclusion that the vendor that meets current needs and future goals is Terminal 4.