About the web standards site

This web standards site is built by a team from the University's Centre for Educational Development (CED), Centre for IT Services (CITS) and the Corporate Communications office (CCO), in consultation with the University's Chief Information Officer, and the Vice President (IT). These standards and recommendations will be updated on a regular basis and are meant to help us achieve a consistent web presence and promote a cohesive NTU brand identity.

Who this guide was written for

This guide has been developed for all NTU employees and contractors responsible for creating and delivering web content through NTU's web properties. It has been structured under the premise that the reader has one or more roles within the creation process;

The Copywriter: the person responsible for writing and crafting the message on each web page. This person may be a communication officer, administrative assistant, faculty or staff member, etc.
The Designer: the person responsible for developing a visual interface or facade to accompany the message. Usually this person will be using some form of graphics application such as Photoshop, Flash, or Fireworks.
The Developer, Webmaster or Coder: the person responsible for assembling the various components required for the modern web page, including, but not limited to, graphics and text content. This person may be using tools such as Adobe (formerly Macromedia) Dreamweaver, Microsoft FrontPage, or other specialized web editing tools.

We identify that that in some cases, the same person may perform more than one of the above roles. The information in this site is important to you, no matter which of these roles you play. The responsibility to make sure that our web content is built to standards and accessible is shared amongst all of us.

This guide was written with the assumption that the reader has some previous experience and expertise in his/her role(s). While every effort has been taken to make this information user-friendly, this guide also employs factual and actual terminology when required, in keeping with its dual role as a standards document. When appropriate, short segments of HTML source code are provided for illustration, however these pages are not and can not form a "how to" guide; but rather they are "what to" and "what not to" references.