University of Bath

Creating a Project page

How to create a page to describe a research or professional services project.

When to create a Project page

Create a Project page to:

  • describe a research or professional services project that the University community is running, involved in or associated with, either in the past, present or future

Don't create a Project page to:

  • promote engagement in a project that already has its own page - use a Campaign page instead

Before you create a new piece of content, search the website to see if it already exists and talk to other people who could be responsible for it. We do not want to duplicate content on the website as this can be confusing for users.

Naming your Project page

Use the official name of the project for your page title. Don’t include the word 'Project' unless it’s part of the official project name ('1 West refurbishment' not '1 West refurbishment project').

Writing a Project page summary

Use the summary to explain what your project is about, describing the focus and aim of the project. Write in plain English, avoiding technical or industry jargon, for example:

Title: 1 West refurbishment
Summary: A major refurbishment of the building, including the addition of new learning facilities, computer laboratories, research facilities and offices.

The summary should be no more than 160 characters.

Writing a Project overview

Provide a detailed description of your project which follows on from the summary.

If your project has multiple phases, provide a shorter project overview then go into detail in the 'Phases' sections of the publishing platform.

Things to remember when writing about your project

Do:

  • write concisely and in plain English
  • break content up into sections that are easy to read, using headings to structure the content and help users to navigate
  • structure your content so that the most important information is at the top
  • consider breaking long sentences or dense paragraphs with a lot of information into bulleted lists
  • create links to other content about the project (like Announcements, Campaigns or external sources) where relevant

Don't:

  • replicate dense internal documents like project proposals - these can be provided on Publications pages if required
  • use technical jargon unless it’s explained on the page
  • use generic or needless headings ('Further information' or 'Introduction') - users don’t want an introduction, they want the most important information
  • write headers as questions
  • structure your content as FAQs - you won’t need them if your content is concise, well-structured and written in plain English

Resources to help you write your Project

The University's style guide will help you make sure you're using the same terminology, style and tone as the rest of the website. This is important so that website users can understand us easily through the consistency of our content.

Our formatting guide will help you create appropriate headers, links, lists and other formatting for your page. This is important because it makes the information we provide clearer to website users.

Adding a call to action

A call to action is the next thing you want the user to do after reading your content. The Content Publisher has special fields for entering a call to action.

Make sure your call to action:

  • is active ('Find out more about...', 'Contact the...', not 'More information is available…')
  • makes the destination of the link clear to the user
  • does not end in a full stop

Your call to action can be a link to a web page, an email address or a phone number.

If your content doesn't have a call to action, choose 'No call to action' and enter a good reason for not having one in the 'Reason for no call to action' box below.

You should always try to think of the next step for the user.

Adding responsible organisations and groups

After you have added all your content - including any images, media and contact details - you will able to select an owner or associated group for your page. This allocates permissions for who in the organisation is able to maintain the content.

A guide for adding responsible organisations and groups is available to help you do this.