mirror of
https://github.com/ant-design/ant-design.git
synced 2024-12-19 11:58:41 +08:00
2356333c54
* Makes grammatical and typo fixes to the React Docs. * Fixes some spelling and grammar in Pattern docs. * Fixes merge conflict. Updates Pattern docs.
97 lines
4.2 KiB
Markdown
97 lines
4.2 KiB
Markdown
---
|
|
order: 1
|
|
title: Navigation
|
|
---
|
|
|
|
Broadly speaking, anything telling users where they are, where to go and how to get there can be called navigation. We abstract common navigation patterns and provide handy components to help designers and developers build a clear and smooth navigational system. When using navigation or customizing navigational structures, please pay attention to following common pitfalls:
|
|
|
|
- Provide visual and contextual cues as much as possible, to prevent users from getting lost
|
|
- Maintain consistency between form and behavior, or reduce the number of items in navigation, to decrease user's learning cost
|
|
- Minimize page transitions (i.e. reduce the number of page transitions required by a task from several to just once or twice), to ensure that the user travels only a short distance from one page to another
|
|
|
|
---
|
|
|
|
## Commonly Used Navigation Patterns
|
|
|
|
<Table style="font-size:12px;float:right;width:600px;margin-left:60px;margin-bottom:100px;">
|
|
<tr>
|
|
<th></th>
|
|
<th>Side Navigation</th>
|
|
<th>Top Navigation</th>
|
|
</tr>
|
|
<tr>
|
|
<th>Pros</th>
|
|
<td>Hierarchy is easily extensible; Makes room for page content horizontally; Allows fixed position, so that user can navigate to intended page quickly.</td>
|
|
<td>Conforms to common human habit of browsing top-down, easy to browse and click; Content area usually stays in a fixed width (i.e. 1208px), so page layout is more stable and less sensitive to screen sizes.</td>
|
|
</tr>
|
|
<tr>
|
|
<th>Cons</th>
|
|
<td>Sensitive to screen sizes because content area usually resides in a Grid.</td>
|
|
<td>At present, most monitors are widescreen, so top navigation occupies a large area of valuable vertical space while waste a lot of horizontal space; Number and title length of menu items are limited.</td>
|
|
</tr>
|
|
<tr>
|
|
<th>Summary</th>
|
|
<td>Suitable for multi-level, operation intensive and dashboard-like web apps.</td>
|
|
<td>Suitable for landing pages and consumer facing web apps.</td>
|
|
</tr>
|
|
</Table>
|
|
|
|
We categorize common navigation patterns into side and top navigations. Either has its own pros and cons, and should be chosen accordingly.
|
|
|
|
Examples for reference [Commonly Used Layout](/docs/spec/layout#docs-spec-layout-demo-top)。
|
|
|
|
## Side Navigation
|
|
|
|
---
|
|
|
|
<img class="preview-img no-padding" align="right" alt="Structure Example" src="https://os.alipayobjects.com/rmsportal/hutiGZWQYmIspjw.png">
|
|
|
|
Navigational structure consists of following parts:
|
|
|
|
1. Product Logo and Name
|
|
2. Menu Items
|
|
3. Login
|
|
4. Breadcrumb (optional)
|
|
|
|
#### About Breadcrumb
|
|
|
|
> 1. Avoid using breadcrumbs as much as you can, especially when a page contains other navigation components sufficiently telling where users are.
|
|
> 2. Breadcrumb can be categorized as:
|
|
> - Path-Centric: dynamically showing a path of how user reaches current page
|
|
> - Position-Centric: usually fixed, showing position of current page among entire site structure
|
|
> - Property-Centric: showing categorical property of current page
|
|
|
|
<br>
|
|
|
|
<img class="preview-img no-padding" align="right" alt="1st Level Menu Items" src="https://os.alipayobjects.com/rmsportal/IeuIHdFfKCIABHV.png">
|
|
|
|
<img class="preview-img no-padding" align="right" alt="2nd Level Menu Items" src="https://os.alipayobjects.com/rmsportal/kAbbeJekohMtubV.png">
|
|
|
|
<img class="preview-img no-padding" align="right" alt="3rd or Higher Level Menu Items" src="https://os.alipayobjects.com/rmsportal/qaOifucSTWooBTL.png">
|
|
|
|
Here we provide navigation patterns for different kinds of menu hierarchy.
|
|
|
|
|
|
## Top Navigation
|
|
|
|
---
|
|
|
|
<img class="preview-img no-padding" align="right" alt="Structure Example" src="https://os.alipayobjects.com/rmsportal/MVccMQxgCeYfwjS.png">
|
|
|
|
Navigational structure consists of following parts:
|
|
|
|
1. Product Logo and Name
|
|
2. Menu Items
|
|
3. Login
|
|
4. Breadcrumb (optional)
|
|
|
|
<br>
|
|
|
|
<img class="preview-img no-padding" align="right" alt="1st Level Menu Items" src="https://os.alipayobjects.com/rmsportal/KvEsIDOYzknbsPT.png">
|
|
|
|
<img class="preview-img no-padding" align="right" alt="2nd Level Menu Items" src="https://os.alipayobjects.com/rmsportal/xXaCRVPIfmjDyIL.png">
|
|
|
|
<img class="preview-img no-padding" align="right" alt="3rd or Higher Level Menu Items" src="https://os.alipayobjects.com/rmsportal/ollkHeFUFQElelm.png">
|
|
|
|
Multi-level Menu Items.
|