为应用程序提供帮助的好/坏方法是什么？
我正在开发各种应用程序，最终用户既是工程师又是销售员。 某些操作和选项可能并非对所有用户来说都是显而易见的。 所有应用程序都附带 PDF 和纸质手册 - 但当然没有人阅读它们！
我想通过包含动态上下文相关帮助来提高应用程序的可用性。 一种选择是使用 MSDN 并使用 F1 调用网页 - 然而互联网访问并不总是可用，即使这对某些人来说也太费力了。
另一个想法是当选项悬停在上方时弹出描述 - 就像工具提示一样。
我对其他人对此的看法以及这种情况下的最佳实践感兴趣。
沿着与这篇文章类似的主题常见的是什么UI 误解和烦恼？ 我想就这两点展开讨论：
最好的解决方法是什么？
您使用的现有应用程序中的哪些帮助功能让您高兴或烦恼……？
I'm in the process of developling various applications for whom the end users are both engineers and salesman. Some of the operations and options may not be immediately obvious to all users. All applications are delivered with a PDF and paper manual - but of course nobody reads them!
I would like to improve the usability of the applications by including dynamic context sensitive help. One option would be alá MSDN and have F1 call up a web page - however internet access will not always be available and even this will be too much effort for some.
Another idea is to have descriptions pop up when an option is hovered over - like a tooltip.
I'm interested in other peoples views on this and what are best practices in this situation.
Along a similar theme to this post What are common UI misconceptions and annoyances? I'd like to start a discussion regarding these two points:
What would be the best way to go about it?
What help features in existing applications you use either delight or annoy you..?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
根据我的经验，除了程序员之外，没有人会阅读帮助。 因此，当您拥有技术和非技术目标受众时，您最终会提供两种完成所有操作的方法：
带有几个选项的向导。
具有很多选项的属性编辑器。
无论哪种情况，图片通常都比文字更适合记录。 因此，一张或 3 张带有绿色大箭头和圆圈的屏幕截图指出什么是做什么，比索引、详尽的帮助文件要更进一步。
In my experience nobody but programmers reads the help. So when you have a technical and non-technical target audience you end up providing 2 ways of doing everything:
A Wizard with a few options.
A property editor with lots of options.
In either case, pictures are usually better than words for documentation. So a screenshot or 3 with big green arrows and circles calling out what does what will go a lot further than an indexing, exhaustive help file.
根据我的经验，为每个选项提供更多定义/清晰度的工具提示将非常有帮助。 此外，您可以通过让默认屏幕包含一些常见的简单选项并提供可提供更多控制的高级部分来提高可用性。
In my experience it would be very helpful to have a tooltip on each option that provides a little more definition/clarity for each option. Additionally, you can improve usability by having the default screen contain a few common, simple options and providing an advanced section that provides more control.
我目前正在从事一个类似的副项目。 我们有一款现有产品供人们日常工作使用。 该产品有一个固有的学习曲线，因此用户会接受一定程度的培训，并可以向他人寻求帮助。 即便如此，我们知道它总体上需要更多帮助和用户文档。
我们通过对最终用户进行快速调查来启动这个帮助增强项目（提供抽奖作为奖励）。 我们还将与必须处理帮助请求的支持人员交谈。 这将揭示一些痛点，并使我们清楚地了解如何集中时间和精力。 资源。
有关何时使用内联提示与工具提示等的指南可以在各种样式指南中找到，例如：
http://developers.sun.com/docs/web-app-guidelines/uispec4_0/11-help.htm
请记住，仅复制和 将现有手册中的文本粘贴到上下文帮助提示中。 您将需要帮助编写全新的内容。 看看您是否可以从技术作家/文案撰稿人那里获得一些时间。
I'm currently working on a similar side-project. We have an existing product that's used by people as part of their day job. There is an inherent learning curve on the product, so users receive some degree of training and have people they can turn to for assistance. Even so, we know it needs more help and user documentation in general.
We are starting this help enhancement project by running a quick survey on the end users, (offering a prize draw as an incentive). We will also speak to the support staff who have to deal with help requests. This will uncover some of the pain points, and will give us a clear idea of how to focus our time & resources.
Guidelines on when to use inline tips vs tool tips etc can be found in various style guides, e.g. here:
http://developers.sun.com/docs/web-app-guidelines/uispec4_0/11-help.htm
Bear in mind that it's probably a bad idea to just copy & paste the text from your existing manuals into contextual help tips. You're going to need help writing completely new content. See if you can get some time from a technical writer / copywriter.