Web 界面：显示许多静态字段的好方法是什么？
我的 Web 应用程序有显示许多静态字段的页面。
我知道糟糕的布局总是会导致信息过载和可读性差。
我的问题：
对于布局包含许多静态字段的屏幕，是否有任何最佳实践或启发法？
通常，我会参考 Bill Scott 和 Theresa Neil 的优秀书籍，但我似乎找不到任何指导这个问题。
以下是我倾向于遵循的一些准则：
My web applications have pages that display many static fields.
I know that poor layout invariably leads to information overload and poor readability.
My Question:
Are there any best-practices or heuristics for laying out a screen that contains many static fields?
Ordinarily, I would reference Bill Scott and Theresa Neil's excellent book, but I can't seem to find any guidance for this issue.
Here are some guidelines that I'm inclined to follow:
- Group related fields.
- Position the major (or parent) fields towards the top and the left. Position the minor (or child) fields towards the bottom and right.
- Don't feel obliged to fill every pixel. Consider white space if it will improve readability.
- Favor progressive disclosure wherever possible.
- Consider an accordion control.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
也许按需详细信息方法会很有效。问问自己哪些数据与用户绝对且立即相关，并对这些数据进行分组，同时隐藏其他数据。您始终可以提供“展开”链接或控件，以允许用户根据需要查看详细信息。
（很高兴看到您正在研究界面设计模式。它们经常被忽视！）
Perhaps a Details on Demand approach would work well. Ask yourself which data are absolutely and immediately relevant to the user and group those, while hiding the other data. You can always provide an 'Expand' link or control that would allow a user to view the details if desired.
(It's good to see that you're looking at interface design patterns. They are often overlooked!)
我从事人力资源软件工作，多次遇到这个问题。当我们引入折叠控件或任何渐进式披露模式时，我们在反馈中不断看到的一件事是，我们的用户不喜欢这些类型的“web 2.0”（他们的话哈哈）页面不打印的方式。因此，请提醒您，如果您的用户群仍然坚持打印大页数据（包括打印媒体样式表）。
根据您的数据集有多大，我会认真考虑一些搜索功能或排序机制。很多时候，当数据集很大时，不同的用户有不同的优先级，允许定制是满足广泛受众的唯一方法。
I work on HR software and have faced this problem many times. One thing that we keep seeing in feedback when we introduce collapse controls or any progressive disclosure pattern really is that our users don't like the way those types of "web 2.0" (their words lol) pages don't print out. So just a reminder if your user base still insists on printing large pages of data include a print media stylesheet.
Depending on how large your set of data is I'd seriously consider a some search functionality or a sorting mechanism. Many times when the data set is large different users have different priorities and allowing customization is the only way to satisfy a wide audience.
我认为您几乎回答了自己的问题，特别是与渐进式披露相关的重要领域的分组。
I think you pretty much answered your own question, especially the grouping of important fields tied to progressive disclosure.