Page tree
Skip to end of metadata
Go to start of metadata

Document version 0.3 (YA & AJM)

Stakeholders

  1. BUCS managers
  2. BUCS staff
  3. Bath users
  4. Web Development Team

Abstract

The BUCS website is currently managed using Server-Side Includes (SSIs) which give a consistent look-and-feel to the pages and make them easier to edit. However, there is currently little structure to the site and no quality control of content. Therefore we propose to make the BUCS website the first website to be incorporated into the new Content Management System.

Problem Definition

  • There is a lack of structure to the way the information is organised on the BUCs website. This makes it difficult for users to find information. There is also a lot of legacy content on the site.
  • There is no quality control of content at the moment. There are some editing guidelines, but it is doubtful if they are being followed.
  • No-one is assigned the duty of managing content on the website.

Use cases

User

Users need to find information about our services quickly and effectively. They may need to have a variety of ways to access information, e.g. searching, role analysis, topic categories.

Site editor

There would be various roles in relation to the website (e.g. overall site editor, section editor, page editor) with different permissions in relation to creating, editing, publishing, deleting and archiving content.

  • Editors, focused on easy creation and publishing of content. They are frequent users.
  • Administrators, focused on administrating the CMS, e.g. managing users and roles.
  • Developers; focused on creating templates. Want this to be well documented and easy to learn.
  • Occasional user, wants a CMS to employ standard constructs so that everything is intuitive and easy to re-learn after having not used the system for a while.
  • Super user: Wants to be able to do as much as possible from a single dashboard with few clicks.
    _ does this list of roles really fit with the "Background" on BUCS Website Project Plan? - PhilWilson_

Requirements

  • we need to meet with major stakeholders to discuss these.
  • Content must be structured effectively to make it easier for users to find.
  • There should be quality control of content, so the new system will require workflow and versioning.
  • There would be various roles in relation to the website (e.g. overall site editor, section editor, page editor) with different permissions in relation to creating, editing, publishing, deleting and archiving content.
  • Both editing interface and published content should conform to usability and accessibility guidelines.
  • Some content may need to be re-used in different sections of the site.
  • New system should integrate with existing means of managing content on the site, e.g. FAQ system, BUCS Today.

Key Performance Indicators (KPIs)

  • Less content but with a sharper focus
  • Reduction in support calls and requests for information
  • Increase in user & staff satisfaction
  • Increased awareness of BUCS operations and services
  • will need metrics on current status for these to derive any meaning.

NB - this is only a draft version of the document, as I have sketched in the details very lightly, as we need to meet with Rod etc to discuss

See also: Content analysis resources
and BUCSWebsiteContentAnalysis and BUCS Website Project Plan

  • No labels