Case Study: UCT Web Renewal Project

The University of Cape Town (UCT) owns more than 550 individual websites. They’ve been built over time, based on many different software applications and frameworks and only a handful of the sites are connected. This makes it difficult for students, academics and other audiences to locate accurate information. It’s harder still for web administrators to manage the websites and sharing of content across multiple sites in basically impossible.
 
To bring a level of order to their information and content, UCT launched an integrated Enterprise Content Management (ECM) project. A key part of this was their Web Renewal Project (WRP), which focused on ensuring all web entities affiliated with UCT are centralised and adhere to central governance, policies, security, procedures, processes, roles and responsibilities and frameworks.

To achieve this, UCT adopted Drupal as a framework and contracted 2Stroke (as we were then known) to architecturally design and develop a single browser-based software application, based on the Drupal multi-domain enterprise architecture, to serve a single code- and functional-base to multiple domains (websites) from a single database.

In other words, one secure application that will manage all their websites, web users, content and sharing of it, centrally, with a low cost of ownership in the long run.

To deliver a secure and user-friendly application that meets all the objectives, 2Stroke developed an admin dashboard for technical management and rollout of sites, coupled with an intelligent content management, moderation and revision system.

Through this, the application is able to adhere to domain-specific rules and reactions, initiate and enforce workflows, keep track of all revisions made to content and the sharing of it.

Additionally, a number of predefined content types and applets were rolled out that are able to cater for the multitude of informational and functional requirements of UCT.

To ensure that the system is secure, UCT’s Single Sign On (SSO) policy was adhered. Central Authentication Services (CAS) were used for user authentication, while an interface to UCT’s Active Directory was made via LDAP to obtain additional user information.

The objectives were met and in the first month that the platform was live, two sites were successfully rolled out by UCT staff members, despite them never having worked within a Drupal environment, delivering immediate savings.