Web Content Guidelines working group

Owned by Emily Toner
Last updated: Mar 30, 2018

See also: Web Content Guidelines - DRAFT. 

Project Name

Web Content Guidelines working group 

Project Objectives

  • Create an editorial style guide for the new TUL content management system in development, to be used by content contributors
  • Define policies and rules for data input and formatting of services in the new TUL content management system, to be used by content contributors
  • Incorporate accessibility requirements/best practices for both objectives above

Project Scope

The team for this project is a sub-group of the Strategic Partners working group, which is tasked with providing hands-on support for the Website Redesign Project. Additional support may be offered by other contributors.

The table below defines the general scope of the work involved for each objective and the people who will be contributing to those goals/tasks.

ObjectiveScopeStrategic Partners/Other Contributors

Create an editorial style guide for the new TUL content management system in development, to be used by content contributors

  • Based on the LibGuides Editorial Guidelines, developed in summer 2017


  • Statement about who audience is and what these policies are for (i.e. new content management system vs. other platforms such as LibGuides)
  • Institutional branding and standardized language for specific locations/collections, services, and commonly-used words
  • Voice and tone (ex. using the active voice) 
    • Examples of good/bad web copy that demonstrate the right voice and tone
  • Linking standards, including naming conventions and how links open

Rachel Cox (Unlicensed)

Jackie Sipes

(consult with Beckie as needed)

Define policies and rules for data input and formatting of services in the new TUL content management system, to be used by content contributors

  • Formatting requirements for each metadata field (ex. set values for target audience)
  • "Writing for the Web" standards for name and description fields (ex. sentence and paragraph length) 
    • Consider Search Engine Optimization approaches
  • Description of what does and does not belong in each metadata field 

Jasmine Clark

Holly Tomren (consult with regarding metadata profiles)

Include accessibility requirements/best practices for both


Chris Doyle

Out of Scope

  • Defining text styling, such as bold, italics, underlining, color, etc. – This should be standardized across the website and should not be an option for content contributors in the CMS editor. 
  • Defining policies and rules for data input and formatting of other content types (Building, Space, Collection, Resource, Event, Person, Group)