Posted by kika on March 27, 2004 at 12:13pm
Jump to:
| Project: | Feature |
| Version: | master |
| Component: | User interface |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
The attached PDF by Kristjan (kika) illustrates some usability/UI improvements for the feature module.
| Attachment | Size |
|---|---|
| feature_module_improvements_1.pdf | 115.16 KB |
Comments
#1
I do think inline images are key to make the feature page both explanatory and visually appealing. I'm a bit worried that the page grows unwieldy though and that we fail to communicate the essential information.
If you know what you are looking for, as is often the case, a feature matrix is much easier to work with. Furthermore, as a feature matrix does not contain explanations (it is typically more technical) it can list more features without getting overwhelming.
I suggest we use both, and that we move some of the more technical features (eg. Blogger API support) to the feature matrix. Like that, we differentiate between (i) the essential information and (ii) the more technical information as is often the case in product brochures.
If we agree this is a good way forward, how would such feature matrix look like, and how would this impact the suggested redesign?
#2
Its been about 3 years since last post. Should this issue still be open?