Skip to main content
University of Bath

Creating an Event page

How to use Typecase (Content Publisher) to create a webpage promoting a planned event to students, staff or visitors.

When to create an Event

Create an Event to:

  • provide information about a planned ceremony, workshop, session or lecture
  • retrospectively highlight important outcomes of a past event

Don't create an Event:

  • to highlight the outcomes of a past event which already has its own Event page - update the existing page instead
  • for an internal, invite-only occasion (like a meeting of the Council or a committee)

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 Event

Your Event title should:

  • be unique and descriptive - if the event is recurring create a separate Event for each occurrence and include the date in the title ('Open Day September 2015', not 'Open Day')
  • be limited to 65 characters if possible so users can read it in entirety on search results

Your title should not:

  • include the word 'event' (this is automatically displayed on the page)
  • contain commas or dashes as this will create confusing URLs - use a colon instead if you need to separate phrases
  • include a question mark unless it is the official name

Writing an Event summary

Use the summary to explain your Event and its purpose, for example:

Title: University Open Day 16 June 2016
Summary: Open days are a great way to experience life at the University of Bath. Find out about our courses, attend talks, meet staff and students and tour our campus.

Adding labels

We use labels to pin content items onto Topic pages. Only add a label if you know that your content item is going to be part of a Topic.

Labels are not typical website 'tags'. Don't add a label just because you think it might be relevant. You must know what labels the Topic uses. If you don't know, ask your Faculty Web Editor or contact the Digital team at

To add a label to a content item, select from the drop-down list in the Labels section and click 'Add label'. You can add a maximum of 12 labels to a single content item.

Adding location details for your Event

Things to remember when adding location details:

  • include a space in the middle of the postcode (BA2 7AY, not BA27AY)
  • in the Accessibility field, include the relevant DisabledGo link for your location

Selecting an audience

Use the drop-down list in the publishing platform to select your main audience, the types of people who can attend your event. If there are no restrictions to attendance (selecting 'Everyone'), then no audience information will be displayed on the web page. Selecting the correct audience is also important for displaying events in filtered lists and search results.

You can add more details about the type of audience who will be interested in your event in the 'Audience detail' field. For example, 'Administrative staff, undergraduate Chemistry, postgraduate Chemistry'. This will help visitors quickly identify if the event is aimed at them. 

Writing an Event description and speaker profile

There are special fields in the publishing platform for you to write your Event description and speaker profile. Here you can give details such as the itinerary and subjects to be discussed.

Things to remember when writing your Event description and speaker profile


  • write concisely and in plain English
  • break content up into sections that are easy to scan
  • use headings to structure the content and help users to navigate
  • consider breaking up long sentences or dense paragraphs into bulleted lists
  • create links to other content relating to the Event (like Campaigns, Announcements, Projects or external sources) where relevant
  • make it absolutely clear when an action is required by the user ('To register for Open Days, you must contact the Open Days team ...' rather than 'Contact the Open Days team....'; 'You must book your place on a tour...' rather than 'Book a place on a tour...'


  • replicate complicated documents, like conference itineraries - these can be provided as Publications if required
  • use technical words unless it has already been explained on the page
  • use obvious headings ('Further information' or 'Introduction') - users don’t want an introduction, they want the most important information
  • 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 Event

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.

Generating a call to action

Calls to action in Events pages are automatically generated. What the call to action says depends on the booking method selected from the drop-down list.

By choosing:

  • 'Booking not required', text displays on the event page saying: 'No booking required'.

  • 'Email', your event page call to action will say: 'Email to book a place'.

  • 'Website', your event page call to action will say: 'Register for this event'.

  • 'Booking application', your event page call to action will say: 'Register for this event'.

  • 'Booking is closed', your event page call to action will say: 'Booking is now closed'.

Adding responsible organisations and groups

After you have added all your content - including any images, media and contact details - you will be 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.