Marion Kelt The library website

Presentation Summary How do we manage it? Updating and revision process Using analytics Site redesign Questions

How do we manage it? The library web site is managed by the Library Web Group. This is made up of our Director of Library Services and representatives from each team: Academic Liaison Librarians, The Library Desk and Collections and Discovery. The group meet every two weeks, but cancel if there is nothing to discuss. This is very important! The group discuss all major changes such as new web pages, revised content, summer website review and changes to the menu structure. This allows all teams the opportunity to assess the proposed updates. Minor changes such as broken links, typos, spelling mistakes do not go to the group but are fixed as soon as possible when notified.

Who does the building and maintenance? Explain the difference between where a resource is produced and where it is used. Where it is used is the relevant bit with regard to copyright law. Each team has responsibility for the content and layout of their web pages. Each team should also ensure that the content and layout of their pages follows the website style guide, which covers: Plain English usage such as no passive sentences Preferred terminology Rules on capitalisation Rules on actual page design such as use of headers and illustrations Guardian online style guide as backup! To ensure consistency across the website all changes on T4 will be made by two members of the C&D team. All changes or requests for new pages are sent to one group mailbox. The team member monitoring the box decides on whether the request is major or minor.

Major updates and revisions Explain the difference between where a resource is produced and where it is used. Where it is used is the relevant bit with regard to copyright law. Each summer the whole site is checked and revised. We have a spreadsheet listing all the pages with the name of the team responsible for the content. This spreadsheet includes Google Analytics for each page with data on changes in traffic from the previous year. Part of this process is to highlight pages with very little use and decide whether to delete or revise them. Analytics are also used to identify content for the blue “shortcut” tiles on the home page. Changes and updates are then sent to the mailbox for action.

Site redesign Explain the difference between where a resource is produced and where it is used. Where it is used is the relevant bit with regard to copyright law. Every so often you should take a step back and look at the overall web site. You can fall victim to “site creep” where extra pages get added just to shut up persistent people! A group structure helps avoid that! We decided to aim for: Fast load times. Short, concise pages. Use in-page navigation for longer pages. Navigation should be clear and intuitive. It should be clear what someone will get when they click a link. Current content and links. Where possible use external sites instead of re-creating content. Relevant content and links. Write globally. Where possible write generic pages, don’t recreate the same content in multiple directories. Consistent CSS. Pages, images, videos should be same style, format and size throughout the site.

Site redesign Other drivers: New technologies available Explain the difference between where a resource is produced and where it is used. Where it is used is the relevant bit with regard to copyright law. Other drivers: New technologies available Changes in structure or offering of your service Need to add forms for feedback or other uses In our case, we had two main ones: Our analytics showed a growing need for a mobile friendly design, so when the T4 template became available, we volunteered! Our service had changed, so we wanted an easy to use, logical menu system. Accessibility. We have in house experts who will help and advise on site design Remember things like ALT text for videos Check with GCU web team for new developments in templates and content types

Lessons learned Explain the difference between where a resource is produced and where it is used. Where it is used is the relevant bit with regard to copyright law. Before you start, have a really good look at what other similar services websites are like. Look at as many as you can stand. Note good and bad points and discuss …. Make a map! Map out your site structure before you start! This can evolve as you go. Always include an A-Z list of pages on your site. Don’t be afraid to ask! If you don’t ask, you don’t get! I am still pestering the web team for new developments …. Consider having a group in charge, it gives a more rounded product as each team has a voice. It is very aggravating but worth it in the end! Be very stern about what is the group’s remit (write it down)! Sometimes content has to be kicked back to individual teams for revision more than once before group discussion.

Thank you Marion Kelt m.kelt@gcu.ac.uk