Section move procedure

Background

This procedure has been created following instances in which sections on the live derby.ac.uk website have been moved or published without following a consistent decision-making process.

This had led to internal stakeholders not being made aware of decisions, broken links, pages missing from search, users not being able to find content eg courses.

Purpose

The purpose of this procedure is to:

• ensure that sections within the derby.ac.uk website are in the correct location for the user and organisation

• prevent broken links and negatively impact the user journey

• ensure we only move content when we have properly considered the impact on all users

• follow a consistent and planned approach to section moves

Scope

This procedure is to be followed when a request is made to:

• Put a section/section(s) live eg moving from ‘test section’ or a pending offline section like ‘work in progress’ to the live website

• Moving a section within the live website structure

• Creating a section within the live website structure

• Changing a section within the live website structure from pending to approved

Definitions

• A ‘section’ in TerminalFour corresponds to a page on the live derby.ac.uk website
• TerminalFour is the Content Management System (CMS) for the derby.ac.uk website

Procedure statements

This is to be followed when a request is made to:

• Put a section/section(s) live eg moving from a pending offline area like work in progress or from the test section to within the main website structure

• Moving a section within the main website structure

• Creating a section within the main website structure

• Changing a section within the main website structure from pending to approved

Before the request is actioned it needs to be approved by either the Senior Web Developer (Peter Briers) or a Digital Content Officer (Toby Bradford or Justin Parsons when back in post).

Procedure

1. The request should be logged as a ticket in JIRA, within Service Desk or a relevant Project Board. The ticket should identify the scope, purpose and justification for the request

2. The ticket should be assigned to one of the approving team members for review. The approval (or otherwise) detail should be added to the ticket

3. Carry out any actions required

4. Update the ticket once the required action has been completed

Related procedures

• Redirect procedure (link TBC)

Document information

Document control

Version control

Version history