Luwak: a content management solution

Abstract

PurposeTo inform librarians about the benefits, costs, and technologies involved in implementing a content management system.Design/methodology/approachA discussion of how XML is used to separate content from presentation, how this technology is used in a home‐grown freeware application, and the results of converting a static website into a database driven one through the use of this application.FindingsDemonstrates that converting to a dynamic, application driven web site results in a more flexible, efficient, and consistent web presence.Research limitations/implicationsEvery library is unique and what worked well at Rensselaer might not work as well elsewhere. Luwak is currently only available to organizations at Rensselaer.Practical implicationsA useful primer on how a conversion like this happens and on the sort of features that can make a database driven web application run smoothly.Originality/valueThis paper provides a unique account of one libraries' experience in making the sort of transition that will become increasingly important for all library web sites.