CALI - How to Do Everything With LibGuides: Learning Outcomes

I didn't want to try to break them down more. Perhaps you could alter this to be appropriate for what you want folks to be able to do?

1. Participants will be able to list potential users of LibGuides at their institution.
2. Participants will learn about organizing content, addressing technical issues, incorporating various document formats, print, audio, video, and using LibGuides with other services.

1. Attendees will be able to identify 2 concerns with migration.
   1. Attendees will be able to explain what a database is in LibGuides.
      • In LibGuides a database is the name for links that are listed on the A-Z Databases list. These could be any website, and not just databases. No user can alter the links from a guide, and the links must be altered in the ADMIN area. In theory, this centralizes the process of updating the links, so that any change need only be made in one place.
   2. Attendees will be able to explain how a guide's layout can affect access to its content for users of mobile devices.
      • A layout that includes multiple columns displays differently on Libguides version 2. On a mobile device a column on the left will display a to its right to make one large column on a smartphone. This can make it difficult for mobile users to see content the same way as desktop users.
2. Attendees will be able to identify several reasons to change LibGuides' default settings.
   • Some examples are here: to match their institution's primary website's colors, fonts, or general appearance;
   • to comply with their institution's policies (perhaps called something like web governance, standards, or style guide);
   • to make LibGuides more accessible to users using mobile devices.
3. Attendees will be able to change LibGuides' from its default settings.
   1. Attendees will be able to explain how to change the settings under ADMIN ➨ LOOK AND FEEL ➨ Language Options to change the labels in LibGuides.
      • For example, enter words in the Custon Value field under various Base Language Values to change the field labels in Libguides. (ADMIN ➨ LOOK AND FEEL ➨ LANGUAGE OPTIONS)
      • Enter " " in the Custon Value field under various Base Language Values to remove visible field labels in LibGuides.
   2. Attendees will be able to find the CUSTOM JS/CSS field in the ADMIN area for the whole site and, for those with CMS access, in an individual guide.
      • To do this, go to ADMIN ➨ LOOK AND FEEL ➨ CUSTOM JS/CSS as an administrative user on the system, or go to GUIDE LAYOUT ➨ GUIDE CUSTOM JS/CSS on a particular guide for those with CMS privileges.
   3. Attendees will be able to identify changes to the styles of other LibGuide sites that could be used on their own site when those changes are clearly noted.
      • To do this, go to another school's LibGuides and view the html source. In most browsers you would right-click an empty area of the page and select "view source." Then look for content between both instances of this comment "<!-- BEGIN: CUSTOM HEAD JS/CSS -->." See if the code has clear labelling that lets you know what it will do.
   4. Attendees will be able to copy potential style changes and paste them into their site to evaluate.
      • To do this, select code from another site or from the LibGuide for this session and copy and paste it into the CUSTOM JS/CSS field in your LibGuide between the appropriate tags. Click save and view your site to see the changes.