We tried to make the guidelines strict enough to make the pages look consistent and clean, but flexible enough to allow for creativity and to accommodate different types of content. In general, we recommend that LibGuides creators:
- Follow the web style & writing guidelines already in practice.
- Keep it simple!
Recommendation |
Why? |
Example |
|---|---|---|
Marion should set up a page for each subject, with Vera database descriptions on first page, in rich text type box, with as much white space as possible and clean fonts (no italics), in two-column page layout. |
Simple for Marion to add, simple for librarians to edit, copy, etc., provides a clean start for librarians |
|
Use of LibGuides is optional. |
Some guides are too complex for LibGuides, and some creators will prefer html |
|
All publication types, subject pages, databases cheatsheets, course pages, etc. will be called "Research guides" instead. |
Users don't care what they're called... Simplify! |
Publication type, subject page, course page, database cheatsheet |
Follow existing web guidelines whenever possible, including use of color and recommended fonts. |
Keep consistent with rest of Libraries' pages. |
|
Make font in box titles bigger and bolder. (Darcy's working on.) |
Set apart the title from the rest of box content. |
|
Use "friendly" URLs (shortcut URLs) for all pages. |
Easier for users to remember, cleaner looking on page |
|
Contact information should always display in top right. People shouldn't be required to use the designated profile box. |
To make the location of contact info consistent. Different guides/groups have different needs, and default profile box is limiting. |
|
Label the profile box (and all boxes!) wisely:
|
Make content of box obvious to users. |
|
Staff photo use guidelines should be followed, but people should hide the photo box if they don't use it. No avatars! |
Some people are adamantly opposed to posting their picture, but some like putting a face to the library. Avatars are distracting, and could vary wildly. |
|
Adding chat contact info is optional. People are welcome to embed Meebo boxes, but color should match with our color scheme. |
Not everyone likes chat! Meebo offers some gaudy color schemes, so some guidelines would help. |
|
Set a maximum of one row of tabs (5 or 6, max). Subtabs may be used, but should be kept as simple as possible and labelled wisely. |
To make navigation easy, and to reduce clutter. |
|
When given an option, people should have links open in a new tab/window. |
To make navigating back to the page easier. |
|
No limits on comments feature, besides being set to "moderated." |
Some people may find this useful, but others might not want comments on their page. |
|
No set limit to number of boxes allowed on page, but if it looks cluttered or if scrolling is excessive, creator should consider reorganizing or using Dreamweaver |
Allow freedom of choice and allow content to govern design |
|
Creators should choose to "link to" or "copy" wisely. Any time the content should be maintained by one person, use link to (ex., search box on template page) |
People won't have to maintain content unnecessarily. |
|
Don't use tags feature for now. |
Looks cluttered, could get unwieldy quickly. If some people use tags more than others, it could seem as if certain topics are underrepresented. |
|
2 and 3 column layouts are both usable. |
Lets the content inform design. |
|
Members of the task force (& Nicole & Darcy?) will offer 4 or 5 hour-long sessions in July to teach procedures & policies for using LibGuides. Training will be aimed at people making pages for public use, but anyone is welcome. |
Learning is fun! Focusing on training people to make public pages is manageable. |
|
Questions answered by UIG:
- Where should people store images? LibGuides doesn't currently have an option to upload images to their site.
- There's a new tool that's being developed by MIT called Thalia, and it's kind of like a Flickr for MIT. Hopefully, that will be ready soon, but in the meantime, people can store images on the server, as they have been with Dreamweaver guides.
- Who should choose 5 custom questions in profile page? (We recommend to NOT make answering them mandatory!)
- They did kind of think that this could be part of our charge, but Darcy and I will work on coming up with some ideas.
- Set page categories/subjects so they're consistent with categories across Libraries' site.
- Nicole and I will work on changing the guides so that they're consistent with Multisearch catagories. Marion will add the subjects when she sets up the page.
- Who to invite for training?
- ps-lib.
- Will people be allowed to make pages for staff use?
- Not yet. UIG will recommend that people use wikis for staff training for now.