Testing the Document

In a way the hypertext is like a book, which should be proof read. In a way, it is like a program which should be tested. If many people will read your work, a little of your time will save a lot of theirs. While Test, Test, Test and Test is the golden rule, some associated ideas are:
  
Read the document using different client programs, to ensure that it has been formatted in a device independent way.
Monitor the readership of document. This can be done by analysing the server log files. By doing so, one may find that some parts are not being read, perhaps because people are looking in the wrong place for them. People often follow a path and backtrack. If one can guess what the reader is looking for, one could make clues around the link more helpful. 
Make it clear whether you will accept criticism or suggestions from your readers, and how they should send it.
Ask people to solve problems using the document, and report on their success. If they fail, find out what they were looking for, whether it was in the document at all.
How much testing?
Testing takes time. The decision of how much testing you do is based on the quality of the document you wish to provide. One has to balance the reader's time and his own effort.


Hypertext > Styleguide to hypertext > Testing the document