Archive for May 13, 2014

LibGuides v2 Default Template Update

Hey LibGuides v2 Admins – this one’s for you! We pushed out an update to our default templates (for both tabbed nav and side nav) today, which requires some work on your side. 😉

Our code update only updates the default templates – it doesn’t touch your custom templates since those are, well, custom, and we don’t want to do anything to mess with them. This means, of course, that if/when we make changes to the base (default) templates, you also need to update your custom templates with the new / modified info.

  • If you are using the default templates for your guides, you don’t need to lift a finger. This update has already applied to those guides!
  • If you are using custom templates for your guides, though, you’ll want to pay attention to the next section of this post so you know how to update your templates.

In this case, we removed the gray bar that has the page name / print icon on the public side of the system. (The {{guide_nav_info}} keyword.) Previously, removing that keyword meant that you also removed the incredibly important admin side functions, but not anymore! The admin functions will remain where they are on the admin side, but the public side will be that much cleaner. W00t! 🙂

Before:
Public view of a LibGuides v2 guide before the template change.

After:
2014-05-13_LG2PublicGuide-After

And so, fearless LibGuides Admins, here’s what you need to do to update your custom templates:

  1. Go to Admin > Look & Feel > Guide Pages Layout > Edit a custom template.
  2. Delete this line / keyword:
    {{guide_nav_info}}

    Do not delete the surrounding <div> tags (as previously mentioned, oops!) because that will remove the super-important menus from the admin side!

    See Screenshot

  3. Add the {{page_title}} keyword to your template. In the default template, we added it just after guide title, so that line now looks like this:
    <h1 id=”s-lg-guide-name”>{{guide_title}}: {{page_title}}</h1>

    See Screenshot

  4. Add the print icon to the footer. Look for the ul tag in the footer area. Add another li tag after the one for the guide’s URL:
    <li id=”s-lg-guide-print-url”>
    <a href=”{{guide_print_url}}”><i class=”fa fa-print” title=”Print Page”></i> Print Page</a>
    </li>

    See Screenshot

  5. Save your changes.

Repeat these steps for all custom templates in your system.

If you do not make this change, at least the step to delete the {{guide_nav_info}} keyword from your templates, you will see a message on the public side of your guides telling you that it needs to be removed:

Error message if you do not update a custom template.

You also now have another Keyword Parameter option! You can choose to display the guide title on all pages of the guide, or just the homepage.

Enjoy…and let us know if you have any questions. 🙂

Beautiful Website Design, Made Possible with LibGuides v2 CMS

Wexler_homeThe library team at Furman University has done some amazing work with customizing LibGuides v2 CMS templates to create a website for The Peter Wexler Digital Museum at Furman University. Even though the site isn’t finished yet, and they’re still customizing their responsive design, they agreed to share it with us. We went ahead and picked their brains to share their amazing work with our community…

Q. Can you explain the Peter Wexler Project that the Furman University Library is undertaking?

A. The “Peter Wexler Digital Museum at Furman University” is a digital collection that features the life’s work of Peter Wexler, a New York theater producer, designer, and artist. The collection will be built in CONTENTdm and use LibGuides v2 as its front end. The really cool thing about this digital collection is that Peter saved virtually every draft of every design he ever created in the last 50+ years, so that viewing those items in chronological order can offer some insight into his creative process.  Another cool thing about this project is that there are very few digital collections of theater design materials, so the theater arts community has already expressed their interest in the collection after a presentation at the annual conference of USITT earlier this year.

Q. What were you using, previously, to share & display the Wexler Project? How do you envision the LibGuides v2 role in this project? 

 But I think that the bottom line, coolest thing about LibGuides v2 is the potential for using the new template functionality to create layouts that are not only responsive but also make it easier for our content authors to create more usable LibGuides for our users.

A. We decided to use LibGuides v2 to build the front end to The Peter Wexler Digital Museum for several reasons.  First, LibGuides is currently our primary website platform so we’re very familiar with its functionality, flexibility and openness.  We’ve always been able to figure out how to do what we want to in LibGuides, no matter how “outside the box”, and once we’ve got something in LibGuides we know that we can re-use it (within LibGuides) or embed it on other platforms (using LibGuides APIs).  Second, we wanted the Peter Wexler Digital Museum front end to be responsive, and we needed to learn responsive website design, so the timing of the LibGuides v2 beta, which is built to be responsive, presented a happy confluence. [Note: LibGuides v2 utilizes Bootstrap 3.0.1] We also wanted a project to focus on to help us learn the capabilities of the new LibGuides v2 templates model.

Q. You’ve been playing with LibGuides v2 for a few months now! Which features are you most excited for and why?

A. There are so many things in LibGuides v2 that sound awesome that it’s hard to pick just a few.  It would be easy to say responsive design, enhanced content-types, the new A-Z list functionality, or single sign-on across all LibApps.  But I think that the bottom line, coolest thing about LibGuides v2 is the potential for using the new template functionality to create layouts that are not only responsive but also make it easier for our content authors to create more usable LibGuides for our users.

Q. How do you envision these features and overall flexibility and openness of v2 impacting the Furman Library? 

A. Providing a device-agnostic design is very important to us.  Like everyone else, we’re seeing increased use of mobile devices.  The university rolled out a new responsive design last summer so being able to create responsive LibGuides that better meet the needs of our users is a great enhancement.  Having more options to embed LibGuides content via APIs will help us do a better job of integrating with other university web platforms.

Q. You’re a librarian with big plans! What do you plan to do with LibGuides v2 in the future?

LibGuides has really become a core tool in our web presence.

A. Well, LibGuides has really become a core tool in our web presence.  I’m interested in finding out whether a responsive design will result in increased use of our content on small, mobile devices.  I’m also working on a bunch of Google Analytics custom event trackers that I hope will give us some insights into how our users are actually interacting with our content and how we can help them to become more successful at accomplishing their most important tasks.

 

If you’re interested in learning more about LibGuides v2, templates or loads of the other cool features, be sure to sign-up for our LibGuides v2 training sessions!

Wexler Digital Portfolio

Digital Portfolio