Page Comparison

JS

University of Washington

define scope of guide content clearly on page 1
include link to writing for the web guidelines - we need these, but should they specifically target LibGuides or should they include all of our content?
good profile box guidelines - we need these (with guidelines about how chat boxes, email buttons, and LibCal myscheduler buttons should be configured; multiple ways to get help should be included)
template example - I like that they include this, but I'm still confused about the utility of the templates because the guide authors can still control the language and content I think; not sure how much of it can be locked down with the template function. Also, in this particular example, I'm not sure about the way they've divided guide pages/sections by source type - is this how users need to navigate? especially considering discovery environment and users' tendency not to navigate this way
language about reusing content with link to boxes that are maintained
U of Wash - I like that they organize "Adding Content" by content type in the LG system - makes sense; also includes something about proxying resources - great
Overall seems to be organized by the process of creating an actual guide - this makes sense
nice job of succinctly referencing usability findings that provide rationale for the standard
their "essential best practices" are not specific enough - not sure these are necessary

BU

section for responsive design & box order
editorial guidelines
emphasizes instructor collaboration for course guides - i think our usability testing of course guide backs up the need for this
Maintaining your guide section do not like the organization - too many boxes, hard to follow, sort of looks like our current best practices guide

KSU

I like the layout of the standards; simple and includes a justification at the end of each category
508 compliance & maintenance schedule - we will need these

UCLA

like that it includes exemplary guides
like the "preferred terminology"
way too much content overall - seems like it would be overwhelming for guide authors

Questions I have

Should we be separating content by source type (books, articles, etc.) Is this how users search for it? Is it relevant in the Blacklight discovery environment?
How many tabs should a guide be limited to? (personal opinion: one page guides; exceptions could be granted if author submits justification for this, but what would the parameters be?)
What does a default template look like? What elements does it contain?
What content and labeling do we want to be uniform across guides?

EBT

Some of the sections in these guidelines that we may want to include in our own:

Versions Compared