There was a video I watched recently about using screen steps in exactly this way. Users would request help, and the response would be a either a new or existing article on how to do what the user needed to do. In this way, the help system was a "living document" to quote an oft misused phrase. Neat idea.
Bob On Mar 23, 2012, at 1:39 PM, Phil Davis wrote: > Hi Pete, > > I use a "squeaky wheel" approach to user docs. Instead of creating volumes of > info that only I will read, I use ScreenSteps to create very visual "how to" > web pages on issues where users ask questions. The apps I build for my > clients all use the same "Help Topics" plugin that appears in the app's Help > menu. When users open it, they see a list of the How-To pages available for > that app which are stored on the client's web server. If they click an item > in the list, their web browser opens with the info displayed. > > There's nothing like having the Help info right there when & where you need > it! > > Best - > Phil Davis _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
