在网站设计中，使用常见问题解答部分代替几个较小的部分是否有意义？
我正在为我的公司制定新网站设计的要求。我注意到我们有相当多的页面只有几句话的信息。这些页面涵盖了一系列彼此无关且与其他较大部分无关的主题。
我正在考虑将它们合并到常见问题解答页面/系统中。在很多网站上，我觉得我经常在常见问题解答系统中找到其他页面上未包含的有用信息。通常，这就是我在网站上试图查找的确切信息。
我觉得我可以减少包含这些信息的众多较小部分的混乱，或者减少用户试图挖掘一个组织很少的大型“包罗万象”部分的挫败感。
一般来说，将常见问题解答部分作为网站的焦点是一个好的设计还是网站内容/设计不佳的证据？我认为主页应该有一个相当显眼的常见问题解答部分链接。
I am developing requirements for a new website design for my company. I have noticed that we have a fair number of pages that have only a few sentences of information on them. These pages cover a range of topics that are unrelated to each other and unrelated to other larger sections.
I was thinking about incorporating them into an FAQ page/system. On a lot of websites, I feel like I frequently find useful information inside of an FAQ system that is not contained on other pages. Often, it is the exact information I am on the site trying to locate.
I feel like I can either reduce the clutter of numerous smaller sections to contain this information, or reduce the frustration of a user trying to dig through a large "catch-all" section with little organization.
In general, is making the FAQ section a focal point of a website a good design or evidence of poor content/design of the site? I am thinking that the homepage would feature a fairly prominent link for the FAQ section.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
1）最好的可用性解决方案是进行站点搜索。那么，无论信息是在许多小页面中还是在一个大的常见问题解答中，它的相关性就不那么重要了。
2）如果您确实使用常见问题解答，为了解决“用户试图挖掘大型“包罗万象”部分的挫败感”问题，您需要有一个可点击的索引/目录。 Wiki（至少 Attlassian）允许您自动执行此操作，对于自定义网站，您必须在 HTML 或内容管理系统中对其进行编码。
3) 如果这不是真正的常见问题，您可能需要将该包罗万象的页面命名为其他名称，尽管这无论如何都没什么大不了的。
1) The best usability solution is to have a site search. Then it's less relevant whether the info is in many small pages or one big FAQ.
2) To address 'frustration of a user trying to dig through a large "catch-all" section' concern if you do go with the FAQ, you need to have a clickable index/table-of-contents. Wikis (at least Attlassian) let you do this automatically, for custom web site, you have to code it in in HTML or your content management system.
3) If it's not really frequently asked questions, you may want to name that catch-all page something else, although that's not a big deal either way.