KDE Visual Design Group/KirigamiHIG/NavigationPatterns/PageRow: Difference between revisions
(Started article.) |
No edit summary |
||
Line 12: | Line 12: | ||
* Pages can for example be [[../List | Lists]] or [[../Grid | Grids]], or a detail view of a particular item. | * Pages can for example be [[../List | Lists]] or [[../Grid | Grids]], or a detail view of a particular item. | ||
* Make sure to set meaningful page titles, so they can create a useful breadcrumb trail | * Make sure to set meaningful page titles, so they can create a useful breadcrumb trail | ||
* For the command structure, see the [[../../CommandPatterns | Command Patterns]] | |||
=== Desktop/tablet-specific === | === Desktop/tablet-specific === |
Revision as of 15:40, 2 May 2016
When to use
Column-based navigation is ideal for navigating through a hierarchically organized information space, where users often go back and forth between different levels of the hierarchy.
(TODO: Image)
How to use it
General
- Use one page/column for each level of the hierarchy (or more generally, for each step of the navigation).
- Pages can for example be Lists or Grids, or a detail view of a particular item.
- Make sure to set meaningful page titles, so they can create a useful breadcrumb trail
- For the command structure, see the Command Patterns
Desktop/tablet-specific
- Consider using multiple-width columns where you need more horizontal space to present the content of a column properly