Middlebury

Difference between revisions of "LibGuides"

m (Miscellaneous advanced tips)
m
 
(108 intermediate revisions by 5 users not shown)
Line 1: Line 1:
[[File:Libguides.PNG]]
+
'''Deprecated''': See the '''LG Help''' page and '''Style Guidelines''' page of [http://go.middlebury.edu/lgtemplate this guide] '''instead'''''.
  
===== Basics =====
+
'''You must be logged into LibGuides to see these pages.'''
Some help for creating and editing LibGuides:
+
*[http://guides.middlebury.edu/c.php?g=431955&p=2946427 Style Guidelines]
*[http://go/libguides%20http://guides.middlebury.edu Go/libguides] (main Middlebury platform)
+
*[http://guides.middlebury.edu/c.php?g=431955&p=2981523 LG Help]
*[http://guides.middlebury.edu/admin_help.php LibGuides Help from Springshare]
 
*[http://mediawiki.middlebury.edu/wikis/LIS/images/f/fb/LibGuides-StepByStep.pdf LibGuides Step-By-Step] (PDF)
 
 
 
===== Midd LibGuides Reusable Content=====
 
Always consider whether you can start with reusable content rather than starting from scratch. Find links for the following reusable content in the "Admin Alerts" box of your LibGuides Dashboard:
 
*Storage Guide: Reusable Content
 
*Databases A-Z
 
*Links Archive: SubjectsPlus migration
 
*Template
 
 
 
===== Tips for Creating LibGuides =====
 
{|
 
|-
 
| ''Note:
 
*Style/design issues that guide creators cannot change because they are default for site consistency
 
**Color of headings
 
**Box borders
 
**Tab styles and colors''
 
|}
 
* '''Columns''': Follow the template. Landing page has 2 columns: left column is wide and right column is narrow. Subsequent pages have no more than 3 columns: if using 2 columns then left column is wide; if using 3 columns then center column is wide.
 
* '''Page length''': Try to keep landing page content above the fold
 
* '''Intro Text''': Include brief contextualizing information, plus brief overview of contents and how researchers might use the guide. No need to provide a welcome message from the librarian; these do not have an impact on researchers.
 
* '''Guide Text''': Keep it brief! users mainly want links, examples. Be vigilant; do not rely on jargon or acronyms.
 
*'''Tabs''' (quantity): Limit to 1 row (but may have sub-pages)
 
* '''Tab headings''': Keep it brief (but not too brief!): make informative/intuitive to students.
 
**Example: “Which style should I use?”
 
**If you need more space than a tab allows, use the "Description" field. The text in this field appears when the user hovers over the tab.
 
*'''Add''':
 
**(1) “Ask a librarian” sidebar box widget, and
 
**(2) your profile box in right column
 
* '''Friendly URL''': Always provide a "Friendly URL" (Guide Settings > Change Guide Information).
 
*'''Profile Guidelines'''
 
**Box title: Subject Specialist
 
**Profile image: Your photo
 
**Website/blog: optional
 
**Contact info:
 
***Davis Family (or Armstrong Science) Library ____
 
***802.___.____ (phone number: use periods, not dashes)
 
***___@middlebury.edu (email address: type it out)
 
***Subject specialty (liaison departments): ________
 
**Customize profile page
 
***Fill in: Office hours (optional)
 
 
 
===== Miscellaneous advanced tips =====
 
*Box header with no title (for images, etc.)
 
**Instead of typing in a title, type the HTML code for space: '''&nbsp'''
 
*Create a scrolling box (Rich -text box):
 
**In Plain-text editor, add this at the top of HTML code (in <>brackets): ''div style="height: 300px; overflow: auto;"''
 
**And add this closing at the bottom of the text in HTML brackets: ''/div''
 
**[http://guidefaq.com/a.php?qid=2186 Detailed instructions for other boxes, too]
 
*Create a tabbed box
 
**[http://guidefaq.com/a.php?qid=21006 Detailed instructions]
 
*Suggestions from Stacy's Usability Document:
 
**"Welcome" statements: viewers skip
 
** Search box: viewers don't see/use
 
**Tabs: viewers don't notice or don't see sub-tabs
 
 
 
===== Suggestions from LibGuides Best Practices Webinar=====
 
*Consider including persistent links to database search results (like our MIDCAT searches for language DVDs). (This is called the “Worked Example Theory.”)
 
*Naming conventions: [Add here.]
 
*Always include alt tags for images (This i sfor accessibility; screen readers can read alt tags.)
 
*Web writing guides: [Add here.]
 
*Use the appropriate box type. For example, use a ‘links’ box for links (this allows stats and link-checking).
 
*[http://centerforplainlanguage.org/about-plain-language/guidelines-for-creating-plain-language-materials/ Guidelines] from the Center for Plain Language (plain language is a civil right!)
 
*[http://www.plainlanguage.gov/howto/quickreference/quicktips.cfm Quick Tips] from plainlanguage.gov
 
*Reduce cognitive load; we may have a reader's attention for only 3 seconds. Readers are easily overwhelmed by too much content, too many choices.
 
*Reduce the amount of text. Cut it in half, then cut it in half again.
 
 
 
===== How to create/edit database descriptions =====
 
[Add content here. If you (guide author) see a database description that needs to be updated site-wide, what to do? Workflow (including CM staff). Is it possible to create a customized description but preserve the shared URL?]
 
 
 
See this link about A-Z list and links/descriptions:http://help.springshare.com/content.php?pid=146532&sid=1245463
 
 
 
===== How to add a url to a link description =====
 
See this [http://guidefaq.com/a.php?qid=7676 LibGuide FAQ].
 
  
 
[[Category:LibGuides]]
 
[[Category:LibGuides]]
 
[[Category:Subject Guides]]
 
[[Category:Subject Guides]]
[[Category:Libguides]]
+
[[Category:Guides]]
[[Category:Lib guides]]
+
[[Category:Research & Instruction]]

Latest revision as of 10:51, 15 September 2016

Deprecated: See the LG Help page and Style Guidelines page of this guide instead.

You must be logged into LibGuides to see these pages.

Powered by MediaWiki