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.

Introduction to Best Practices in UX design for LibGuides: Best Practices - Technical


Below are a recap of some best practices in naming and describing your LibGuide as well as custom code for blocking any LibGuides that you do not want to appear in Google.

Naming Conventions

The following are the naming conventions for the LibGuides system. Please use these for any new LibGuides you create and be aware that some of your previous LibGuides will be converted to this convention. Be aware that these conventions only apply to what your LibGuide is called on the backend. The public-facing page can be named whatever you want.

Active guides should have LIVE after the title. This marks a guide that is currently in use.

Ex. OER Commons LIVE

If your guide is incomplete or are under construction, but you plan to make it active in the near future, you should place DRAFT after the title.

Ex. Subject Guide for ENGL 3050 DRAFT

If you have a guide you are testing layouts or generally experimenting on, with the assumption it will be deleted, then you should place TEST after the title. Guides with the TEST convention will be automatically purged periodically. Do not store information you wish to keep in one.

Ex. New Research Layout TEST

If you have a guide that you regular pull boxes from or copy to make a new guide, it should have TEMPLATE after the title. These guides will not be deleted.


If you have any questions about this system, please contact Jonathan Bradley

Search Engine

If you do not want a particular guide you've created to be crawled by Google and other search engines, add this snippet of code to the "custom JS/CSS" section of the page.

<meta name="robots" content="noindex" />

Here is a tutorial video on how to accomplish this.

Reusing Content

"Copying" a box means there are no links between your box and the original.  You can update your box without affecting the orginal, but any updates to the original won't show up in your text.

"Linking" a box retains links between your box and the original.  Updates to the original will show up in all the linked boxes.  You can't customize a linked box.