In my experience, the setup you describe is a good way to ensure a poor user experience and documentation that nobody reads. I urge you to include at least some degree of context-sensitivity, so that clicking the help link from a given screen takes the user to information about that screen, or better yet, to information about tasks they're likely to be doing there. Making the user search again for information about their usage context is shifting the burden of effort in the wrong direction. Some extra effort on the part of the software developers and documentation writers can make a big difference to how long it takes users to find the information they need, and how frustrated they get in the process.
--Janet On Mon, Feb 21, 2011 at 5:17 PM, Don <[email protected]> wrote: > Thanks for all the suggestions, I think we'll be able to find what we > need by reviewing the options that have been suggested. > > A better description of what we want to do is a searchable online > reference manual. It will be available as it's own website and we'll > just provide a single help button in the application that directs them > to the site. > > Something like a wiki or even wordpress might be what we want, but > we'll look at all the options before choosing. > > Thanks again. > -- Our Web site: http://www.RefreshAustin.org/ You received this message because you are subscribed to the Google Groups "Refresh Austin" group. [ Posting ] To post to this group, send email to [email protected] Job-related postings should follow http://tr.im/refreshaustinjobspolicy We do not accept job posts from recruiters. [ Unsubscribe ] To unsubscribe from this group, send email to [email protected] [ More Info ] For more options, visit this group at http://groups.google.com/group/Refresh-Austin
