Over the last year the J. Paul Getty Trust's Web presence has evolved from a group of disparate, independently maintained Web sites into a homogeneous consistently branded one. This transformation recently culminated with the implementation of a leading Content Management System (CMS). There were and are many process-changes and challenges in implementing a CMS in an institution such as the Getty. These issues are not unique and span the gamut from social, to business, to technical. This paper will highlight the major issues, describe the route the Getty took, and give an insight into the functionality and capability of a leading CMS application for a content-rich museum Web site. Topics covered include: the maintenance burden of re-launching the Web site before implementing a CMS; preparing for a CMS; CMS requirements; implementation; environment; templating; the templating process; workflow; deployment; the rollout; and future initiatives. (Author/ MES)