Skip to main content
Are you okay? Emergency/Crisis UOIT Home

Naming conventions

This page provides an overview of the different names that can be set on a page or asset in the CMS as well as preferred naming conventions.

  • Display Name and Title

    Display name - (An inline metadata field) The name of a page or asset that appears in the navigation menu. This is typically the same as the Title of the page, unless the Title is too long, in which case a shortened version is used for the Display Name.

    Title - (An inline metadata field) The full name of a page that appears on the web page (the title at the top of the page content).

    If you wish to rename a page by changing what appears in the navigation menu and/or page title, edit the Display Name and Title fields in the page editor. 

    When setting names for pages and files, it is best to keep date versions generic.

    For example, if the page content or document will be updated or replaced annually (such as for a list of statutory holidays), it is best practice to name the page or document "Statutory holidays", instead of "2016 Statutory holidays". Accordingly, the URL (system name) of the page should be "statutory-holidays", instead of "2016-statutory-holidays". This way, the URL does not need to change year to year and users can bookmark the page without having to update the link every year.

  • System name (URL)

    System name - The name of the asset (folder/page/file) in the CMS sidebar. The system name is what appears in the live URL so it should not contain any spaces or special characters.

    When creating pages and menu subsections in the CMS, the system name is automatically generated based on what is input in the display name field. Any spaces or special characters are automatically removed and replaced with dashes, making it "URL-friendly".

    If you wish to change the URL of a page, change the system name of the page by selecting the Move/Rename menu item from the secondary navigation bar. Follow the tip below for proper naming conventions of system names. Ensure that the Unpublish option (if available) is checked - this ensures that the page at the old URL will be unpublished on the live site. Otherwise, if you just rename the asset and publish it, both the old and new (renamed) asset will exist on the live site. 

    When setting or updating system names for pages and files, it is best to keep date versions generic.

    For example, if the page content or document will be updated or replaced annually (such as for a list of statutory holidays), it is best practice to name the page or document "Statutory holidays", instead of "2016 Statutory holidays". Accordingly, the URL (system name) of the page should be "statutory-holidays", instead of "2016-statutory-holidays". This way, the URL does not need to change year to year and users can bookmark the page without having to update the link every year.