The Infodome Dispatch

From Carolyn Baber.

Usability and best practices:

Researched-Based Web Design & Usability Guidelines

Usability.gov Your guide for developing usable & useful Web sites

Webcontent.gov Your Guide to Managing U.S. Government Websites

Design stuff:

Nifty corners

CSS Design stuff

Gliffy looks to be a neat little tool. You can see more discussion and some examples at David Lee King’s blog.

Interesting wiki for library staff at the University of Minnesota.

Notice in the upper right side of the nav bar that there’s a new page about developing content for Infodome. I’ve tried to condense the instructions from the pagemaster’s guide into this quick reference. Next step: work with John P. to simplify those evil selectfiles pages. I’d like to get rid of them, but I’m not sure how yet.

From Marilyn, a link to the U of Notre Dame Library webiste strategic plan.

This is part of a message I sent to Webteam this morning outlining a process for making, recommending, and stewarding change in the Library Web presence. I’m curious to see how it works out.

STEP ONE:
Please review our charge before the next meeting. I’ve posted it on the blog here.

STEP TWO:
We need to agree on the vision for our Website. To recap, my general concept is this, with perhaps sub-points below each item:

1. All the content users need in an easy to use and engaging format.

2. Content development so easy that technical skills are moot.

3. Professional look and feel, in keeping with our Library brand.

STEP THREE:
Review the strategic planning documents for ideas, projects, directions that are Web-y. List each in one of the above three categories. Add anything else we think is important.

I would like these items to be discreet. Instead of something amorphous like ‘massive website redesign,’ for instance, we can say ‘review major categories using card-sort tests and change as needed,’ ‘update content and layout of 2nd level navigation pages,’ and ‘improve layout and design for a more professional look.’

STEP FOUR:
Sort the items into these categories:

A. Just do it.
B. Discuss with appropriate people, then just do it.
C. Needs some planning, do that and then just do it.
D. Needs broad input, recommend a team be formed.
E. Should wait for IST Director.
F. Ideas, directions, etc. for future discussion.

STEP FIVE:
For items in categories A, B, and C list in temporal order and note who to confer with for each. For those items in categories C-F, create documentation of some sort that goes to whomever we decide it should go to.

STEP SIX:
Move forward. Rinse and repeat as necessary.

This charge was drafted back when I started working here. The Website has become so central to the mission of our organization, that it can be overwhelming. It’s good to go back to the basics and consider what we are charged to do:

The overall charge of this team is to make recommendations regarding the Library Website and issues that surround the Library’s portal to the world. This team is not necessarily comprised of everybody in the Library who is contributing Web content or is involved in html production, but is a steering committee that will gather input (both internal and external to the Library), make recommendations, research and implement solutions, serve as a clearinghouse for Web-based projects, and recommend policy. This team will further be engaged in an iterative process of evaluation and improvement.

The team will be comprised of five to seven members from various Library units, and will be chaired by the Electronic Systems and Services Librarian. Membership is open to all interested SDSU Library and Information Access faculty and staff. Volunteers will be solicited and selected by the Electronic Systems and Services Librarian and approved by the Dean of the Library and Information Access. Ex officio members may be selected by the Chair to serve as consultants.

Presentation on a Georgia State U Library CMS project

CMSWatch.com

David Walker has a short piece about Xerxes here (I’ve asked him for a login so we can see it together).

More on David’s various projects here.