Representing Online Textbooks?
BWJones asks: "How does one represent online texts to best convey information to the reader as there are a number of issues related to online textbook reading and interpretation that are quite different from reading a standard textbook. We have a site dedicated to retinal vision education that went online a number of years ago and is due for a major rewrite/re-creation. This site was one of the original online textbooks and its design attempted to be of use in the early graphical navigation of the web. However, as the content has increased and will continue to do so, navigation has become more cumbersome. I am looking for suggestions to increase its usability while content increases and will entertain all ideas. I am loathe however, to make the browsing requirements too steep as there are folks from all over the world who access this site (about 30k/hits per day) and they do not always have the latest in computer technology."
Represent textbooks online. Problem solved.
Tip #1: Ditch the background images. Solid colour backgrounds = better readability & faster loadtimes. Plus background images are SOOO 1997. :)
Tip #2: Hire a information architecture/usability/UI specialist or team. Worth the money, especially if you have tons of content.
Disclaimer: Yes, I'm a UI specialist.
I would offer (lots) more advice, but it's lunchtime and I'm friggin' hungry. Sorry.
Yo! Yo! Yo!
73x7b00kz b3 r3pr353n71n9 1n 7h3 h0wwz4h!
You need an index.
Also, the table of contents looks like a sea of text. Make the chapter headings much, much larger than the section titles. You already did a good job with the "part" demarcations. This lets the reader see the material in a more hierarchal manner.
You might want to try page-by-section rather than page-by-chapter, and keep the sections short enough so the browser window needn't be scrolled. Powerpoint presentations follow the same rule. (Maybe, leave page-by-chapter as an option if the text is used for reference instead of initial exposure).
Leave references until the end of a part or until the end of the book -- they are not as critical in a textbook as they are in a paper.
Maybe forcibly use larger fonts -- not all users will be savvy enough to increase the size of their default fonts.
Your site is a little annoying with the big fat headline graphics and the blinking.
Any of the books that I actually use are full of book marks and added notes in the margin. For online books to really work for me I need to be able to continue doing this. Too often it means I end up printing the online book.
Add the ability to create an account. Logged in users get a personalized view of the material which they can add bookmarks to as well as a sidebar with their additional notes.
Chris Kuivenhoven is a thief, beware
I think you've got the wrong concept of what you want to do... While you can download textbooks off the net, usually they're meant either for printing out, or displaying on an e-book. But reading a textbook online, at least for me, usually results in a major eye-ache (something your particular readers will especially dislike).
I would recommend you use this little invention called hypertext to build an in-depth document. One way to arrange this would be to have a summary of a few pages, or even a few paragraphs, and then allow people to click on terms and be able to explore them in depth.
One website that's used this methodology with good results is Chilling Effects. I suggest you do a little exploring there.
1) No matter how fun or exciting your text content is, keep site design simple.
2) Personally I like the idea of a navigation bar on the side that reminds the reader where they are in the text, like the Outline view in Acrobat Reader (but don't use PDF!)or the way Google Groups shows threads.
3) Don't do things that break printing. If people need to print out a section, it should print properly. I can't tell you how many times I curse at web page designers when I print out a page to refer to later and the text flows off the right edge of the page!
4) Keep blocks of text small; I am of the opinion that scrolling through large blocks of text on-screen is mentally tiring and turns readers off. By the same token, don't do things that slow page loading down for dialup users!
5) If you include figures or pictures, use inlined thumbnails that load quickly, but are also links to full-sized (and printable?) images. Wrap text around the images in a way that is eye-pleasing and makes sense. Excess white space looks as unprofessional as too little.
6) Avoid flashy things that add nothing to the information you're trying to convey.
7) Read anything written on the subject by Jakob Nielson.
You're at U of Utah, right? Ask the folks in your English, Communication, and Computer Science departments if they have students or classes that need "real world" problems to solve. It could be independent studies, senior projects, whatever. You could benefit from a database, a well-designed templating system (server side includes plus style sheets), and some batch processing of images to decrease file size.
BTW, Nielsen's usability ideas are geared for e-commerce; take them with a grain of salt, since that's not what you're doing.
cbd.
- Background images decrease readability due to visual interference.
- It's my understanding that sans-serif fonts (i.e. Arial, Verdana) are easier to read on screen than serif fonts (like the one you are currently using). The reverse is true for printed matter.
- The full text of the caption doesn't need to be a link. That's almost unreadable at the font size on blue background, with the underlining increasing interference.
- Having your sub-contents for each chapter in a blob of text makes it harder to scan. Vertical/bulleted organization is easier.
And some suggestions:
White or yellow text on a black or dark blue background, or black or navy text on a white background have the highest readability. If you do light on dark, make sure you have a printable version because some default browser settings don't print backgrounds, leaving you with blank printed pages(!)
Use cascading style sheets, allowing you to mess around liberally with formatting until you're happy. This also makes it easy to do a printable version.
Having the Table of Contents on a home page, with each chapter in a sub page is nice if you are reading through the book sequentially, but makes it slightly more cumbersome to jump around. Some other sites that present information like this use frames and have the ToC running down the left side of the screen. This may or may not include ways to expand/collapse submenus.
I would include the Home/Back/Forward buttons at the top and bottom, but the ones at the bottom may go best ABOVE the references, rather than below. Far fewer people are going to be interested in the references than in the main text.
The facts have a liberal bias. --The Daily Show
- Put the caption below the image
- Optionally insert breaks in the caption
- Put the images to the left or right and allow the text to flow around them
This won't work on all of the pages. KallDepth.html for example. You may also (again a horrible bastardization of tables) place the sections of a page in a table, so the images don't run out beyond them.That what was all this school was for... to teach us how to solve our own problems. -- janeowit
PDF or PS is still preferable in many situations which Jakob Nielsen conveniently failed to mention. Making a blanket statement like "Don't use PDF" is simply naive.
I quote:
I think with huge amounts of effort, you could use JavaScript for highlighting or underlining - select the text you want and then press a key sequence that triggers a function - which would have to add something to a database. I think you could then turn around and re-create the highlighting by locating the text - perhaps by string position and length in the unaltered document as opposed to recording the full string - and then adding tags with classes. This could even give you different color highlights.
Bookmarks could function on a similar idea - insert an element like a table that would be left- or right-aligned with an anchor, a label if desired, and a noticable background color.
Margin notes might be best as little icons indicating a note that makes a hidden <div> appear with the note in it.
I don't know how much it would chew on a server, or how difficult it would be to create. Last I knew the JavaScript for document control - selections, specifically - is entirely different for IE and Mozilla, and I couldn't even hazard a guess at other browsers.
That what was all this school was for... to teach us how to solve our own problems. -- janeowit
The thing that frustrates me most about online information sources that were converted from print is that they usually have the TOC and maybe footnotes linked and everything else is just plain text. Every topic/field specific word and/or phrase should be linked in a ideal world so the closer you can get the better. I think the best scenario would be to get a definition for a word/phrase in the status bar (or tooltip popup if you want to go more dhtml heavy) and then clicking would take one to the relevant section on that word/phrase if one exists otherwise it would take one to a more extensive term definition followed by links to other or related info (probably offsite links mostly). Of course scenarios like this only get really viable when you're running a database driven website (maintaining this kind of heavy linking in static pages gets ridiculous real quick) which may or may not be an option.
Another suggestion is to look at SVG for your non-photo images, they can become especially interesting if you have the relevant data in a database and generate the images on the fly.
Also, I agree with some of the other posters in that one should have an online friendly version and a print friendly version (implemented through carefully formated html or pdf, etc) rather than trying to do both or cater to just one. And tasteful use of frames can help provide easier linking to the TOC from every page.
Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins, Grumpy Watkins,
Ruby Sleeps