Overview

Background

This project will deliver improved functionality for EdWeb by implementing a more flexible approach to the support for JavaScript. This will allow a better offering to our website users, improved audience communications, better information provision, reduce duplication of effort and duplication of data sources and better analytics data to inform decision making. The project will do this by introducing the ability to publish functionality that requires external JS to function including 3^rd party services. In addition, it will support scripts that improve website analytics and tracking and script libraries that allow the flexibility to meet business needs.

Scope

The scope of this project is to implement the Request for Change (C1603-112) approved by the EdWeb CAB. The project will comprise of one development iteration in December 2016 and January 2017. The user stories will be prepared by UWP and estimated. In particular this will allow the implementation of Click4assistance and Dotmailer functionality. 

Key dates

• R&D iteration w/c 21/11/16
• Iteration part 1 - 12/12/16 - 23/12/16 - 10 days
• Post Christmas Iteration part 2 - 04/01/16 - 13/01/17 - 6 days

Objectives

The objective is meet the business expectation that we should be able to support JavaScript and 3rd party tools as a means to meet our audience needs and improve our understanding of Website usage.

Deliverables

In one development iteration the project will deliver the required code changes, in detail:

For a user with the 'system administrator' role:

• ability to manage a new javascript library which will contain a mixture of:
  • physically uploaded scripts;
  • script URLs referenced by CDN;
  • script URLs where the script is hosted by a 3^rd party.
• ability when adding a new library entry to specify that it be placed in either the header or body.
• ability when adding a new library entry to specify the order in which the script is loaded in EdWeb.
• ability when adding a new library entry to manage parameters for the script which allow it to be customised.
• ability to view a full list of the uploaded script library, edit their loading order, disable or delete scripts. Just to note there will be some system scripts loaded first e.g. Google Analytics that system admins will not be able to reorder.

For a user with a new 'script user' role (to be added to the CMS as part of this work):

• a new CMS user role, to be separate from the existing Tech User role
• ability to associate one or more scripts from the new javascript library with an EdWeb page (regardless of page content type);
• ability for Homepages to specify for *each* script that it applies to the page alone or all pages in the homepage group;
• ability for non-Homepages to specify for *each* script that it applies to the page alone;
• ability where a script is parameterised to specify parameter values;
• ability to be able to position the JavaScript functionality anywhere within the page content e.g. the placing of a dotmailer form anywhere within the content of the page or placing a Click4assistance pop-up window anywhere within the content of the page.

Benefits

This functionality will deliver the ability to meet business needs in a cost effective and flexible manner. Specifically this means:

- a clearer understanding of user behaviour; - more active, targeted user engagement (through the use of email marketing software such as Dotmailer and the Click4assistance live chat facility); - further flexibility in content delivery.

Success Criteria

The project can be declared a success when the Javascript library is available in EdWeb LIVE as outlined, and it can support the desired Click4assistance and Dotmailer functionality.