Overview

Background

The migration of all University website content to a new CMS infrastructure (EdWeb/Drupal) requires development of CAM systems – undergraduate and postgraduate degree finders - in order that our high-profile content will function and display correctly.

We must ensure:

• our page layouts function correctly in the responsive layouts of EdWeb
• that all current functional aspects continue to work as expected via the new proxy environment

We intend to also exploit new Drupal proxy features such as integrated navigation and improved meta data handling to improve the user interaction and discoverability of prospectus content. The changing navigational approach requires review and revision of the applications' content output in terms of ordering and grouping.

Scope

Development requirements are primarily focused around the PG (Postgraduate) and UG (Undergraduate) degree finders website output as delivered to the CMS proxy function (detailed as ‘other’ on the original proposal).

We must ensure our page layouts function correctly in the responsive layouts of EdWeb, that all current functional aspects continue to work as expected via the new proxy environment and also exploit new Drupal proxy features such as integrated navigation and improved meta data handling to improve the user interaction and discoverability of prospectus content.

• Update source application output html:
  • review and amend in-page navigation so it can be merged with UoE nav panel where relevant (optional proxy feature)
  • review and update html code for compliance with Drupal proxy
  • HTML5 & Bootstrap compliant code
  • amend existing layouts to use Bootstrap responsive grid layouts
  • update element styles to match new UoE design and use central CSS where possible
  • update content output ordering and groupings to utilise Bootstrap components and better present content to meet user
  • needs and priorities
  • remove content outputs identified as redundant to user needs
• Additions to source application html output:
  • support web-proxy breadtrail using existing page logic
  • output new (or amend) H1's for use by proxy using existing data
  • H1 value is also passed to proxy for Drupal meta page title segment
  • take advantage of Drupal's (more) friendly url handling where possible
• Publish meta data on source application output and make available to Drupal proxy
  • keywords (exists for programmes and used for search but does not currently output to page)
  • description (create from existing data values)

The following is out of scope for the project as they are enhancements. These are expected to be included in a subsequent small enhancements project in 15/16 once the key scope above has been delivered. It is important that the above scope can be delivered in line for the migration of the websites, as needed for UWP010, so minimising additional work will help to realise this.

• Administrative system:
  • PG: add one new radio button to programmes (Level 1 edit screen) for Placement/internships (Y/N)
  • UG: add one new markdown field for programmes (programme edit screen) - additional costs.
• Data requirements:
  • PG: "work placement" data support
  • UG: no additional data required

Objectives

The aim of the project is to update the html output for the degree finders to a standard that will allow successful integration into the EdWeb environment from a functional, technical, IA and design perspective. The new output should take advantage of EdWeb proxy features to integrate application navigation and meta data.

These developments will need to fit into the deadlines set for the migration by the University Web Programme through UWP010.

The project will not follow the full standard project process, but will follow the amended process used for STU246 as much as possible, as this was deemed successful by the project team and recommended to be repeated for this project in the STU246 completion report. Note that applications management will peer test and sign off the build, and there will be no separate SDS other than for the URL Rewrite as the business requirements are sufficiently detailed.

Deliverables

Updated PG application, enabling migration to the EdWeb proxy, at a time that is consistent with the migration by the University Web Programme.

Updated UG application, enabling migration to the EdWeb proxy, at a time that is consistent with the migration by the University Web Programme.

The detail of the specification is described in the Business Requirements, with the exception of the Administrative system and Data requirements sections, which are out of scope as described above.

Benefits

1. Improve prominence of / navigation path to programme content and make it easier to move between programmes (analytics show a low % of users access programme information). Applicants want to know that a) their degree is offered, b) they can get in and c) the programme content matches up with what they want to do. This is all at programme level.
2. Improve overall navigation (observations on the degree finder from Russel's research is that it is hard to tell difference between the subject and programme and not sure how to navigate).
3. Simplify content, reduce number of choices/links and amend language so that prospective students are more likely to find what they need more effectively
4. Simplify path, remove 'parent' subjects, e.g. languages and cultures, medicine and health so that students follow a less complex structure.
5. Remove current subject image and replace with student pic for quote (authentic student voice) to support improvement of the student experience.

Success Criteria

PG Priorities:

• Improve the navigation path to programme content and make it easier to move between programmes
• Exploit the improved EdWeb proxy features to introduce page specific meta-data and relevant headings
• Modify page layouts to ensure compatibility with the EdWeb responsive templates
• Use Bootstrap and EdGel design components to ensure the content presentation complements the new EdWeb design
• Amend content ordering and prioritisation to better meet user needs and exploit the layout opportunities the new design allows

UG Priorities:

• Prospectus content remains functional and accessible.
• Maintain integrity of prominent aliases and incoming links.
• Amend layouts and content groupings to use Bootstrap responsive grid layouts and UI features.
• Revise current in-page navigational elements so they can be merged with EdWeb navigational components where relevant.
• Publish meta data on source application and make available to Drupal proxy.