Research has identified several patterns in how users scan a web page. Some patterns are natural to a user, like the F-shaped pattern, but can also be problematic because important information may be skipped over because there is a cost to reading poorly formatted content.
Make your guide content easy to scan and comprehend with these tips:
Guides are more than lists. They are instructional tools, telling users not just where but how to do research, which often requires longer narrative or explanatory text. There is an inevitable tension between conflicting purposes: bulleted lists for quick findability, vs. sentences and paragraphs for explanation.
Names of resources whose subject area is not clear, e.g. JSTOR, Francis, PAIS, MLA, CIAO should always have brief descriptions added to them to indicate the type of content.
Avoid describing the database asset using the default scope note from the vendor. Often this type of text is wordy and full of jargon. Aim for clear language with just a few sentences so the reader can scan the description quickly.
Also consider how the database description will read when reused on other guides. Subject specific acronyms and abbreviations may confuse readers who are unfamiliar with the subject.
As students tend to use the first resource listed, it is generally preferable to list them in order of importance rather than alphabetically.
Think about other ways to arrange the sources. For example: in order by importance or value, as you see it; from broad to narrow in subject scope; by date coverage; etc.
It is also desirable to keep lists of resources short – maybe to the top five key resources featured prominently. One may also consider breaking long lists of resources into different boxes based on similar content type.
Use the Book from the Catalog widget to highlight print resources.
Yet, keep mentions of print resources to a minimum. The best resource may be print; however, long lists of resources inaccessible via the web will frustrate or confuse most users.