Website Approval Process

All new website requests must go through the Web Operations Team.

For a website request to be granted, it needs to be shown that the content is important to a wide audience, that it cannot be appropriately placed on an existing website, and that there are resources available to develop and maintain the content to a high standard, in line with the rest of the University websites. All new websites will be built in our new CMS, Drupal.

Before requesting a new website, consider the following questions:

  • Why is this website required?
  • Who is the target audience?
  • Is there no other appropriate location for this content to be placed?
  • Who will develop the content?
  • Who will be responsible for maintaining the site?
  • What is the title of the site?
  • What should the URL be?

If the Web Operations Team are satisfied that the request meets the above requirements, we will set up a development site for you. You will need to provide a basic site structure (the names of pages and where they sit in the site navigation) for us to build a shell of the site. Someone in your team will then need to register for Drupal training, after which we will grant them access to edit the site.

Once the site has been built, you need to notify us that it is finished. We then undertake a “pre-go live check” which can take 1 to 2 weeks, depending on the size of the site. During this time, no further editing can be done on the site. If you are able to give us advance warning of when you will send us the completed site, this is preferred.

Once we have completed the pre-go live check, we will send you a list of any amendments that need to be made before the site can go live (for example, images that need to be changed, links that are broken, typos in the text and so on). Once these amendments have been made, we will approve the site to go live. 

Approval process

  1. Request a new site from the Web Operations Team and/or your faculty (if you sit under a faculty).
    Provided this is granted -
  2. Discuss URL options for the site with your faculty (or head of area if a departmental site) and seek approval from the Web Operations Team
    Note: a URL must be agreed upon by all parties before a development site is setup.
  3. Provide the site structure (names of pages and position in the site navigation)
  4. Undertake training (1-2 team members)
  5. Build the site
  6. Complete the site and send back to your faculty (or head of area if a departmental site) to check over
    Note: the faculty will look over your website and provide feedback and assistance if needed with any changes required.
  7. Send back to the Web Operations Team to do a pre-go live check
  8. Pre-go live check done by Web Operations Team (depending on the size of the site and our workload, allow 1-2 weeks)
  9. Any edits are discussed/sent back to your team
  10. Once edits are made, the site is sent to our developer team to be made live (allow 1-2 days)
  11. Site goes live

Checklist to consider before sending a completed site to the Web Operations Team: