Skip to Main Content
It looks like you're using Internet Explorer 11 or older. This website works best with modern browsers such as the latest versions of Chrome, Firefox, Safari, and Edge. If you continue with this browser, you may see unexpected results.

RRC Guides : STYLE

Use these standards to create guides within the RRC Guide Collection.



The Style guide outlines the set of visual standards that will be applied to the creation of RRC Guides. This guide addresses user profiles, naming conventions, new guide metadata, colour and navigation, fonts and styles as well as graphics guidelines.

Its purpose is not to restrict owners but provide them with a structure to ensure that Guides within the collection maintain a consistent "look and feel". This makes them more intuitive to users and provides us with a more coherent, professional image.  


What do we call these things?

“GUIDES” or "RRC GUIDES" was determined to be the most generic and user-friendly term without being redundant or jargon. "LibGuides" is the name of the Springshare software product, but does not adequately explain to students and other users what Guides are and what they do.

What goes into a Guide?

Guides should contain resources within the collection and the web RELEVANT to the subject the guide is about. Sources should be up-to-date. An exhaustive list is not necessary as this is the launching off spot of research, not a catalog of all possible sources. 

Create focused guides

Guides should be focused on a topic, a course, an assignment, an outcome (like finding grants), etc. Huge, unwieldy guides are hard to navigate. These guides are jumping off spots for users, not textbooks. Keep It Simple!

What doesn’t go into a Guide? 

Any repetitive information (ex. "How to use OneSearch") that might appear on multiple guides (or pages) should be excluded from Guides. This type of information should be its own Guide and depending on content, included in Library 101 subject area. All guides have links pointing toward Library 101 content.