1. GUIDES & VISUAL RAIL
Whether you're using the standard Windows 8 visual rail or you’ve created your own that makes sense for you app, don’t stray from those guides in different pages of your app.
Do maintain a consistent visual rail and set of guides throughout your app.
2. BACK BUTTON
Don’t neglect to include a way back for the user, or implement a non-native way of doing so.
Do provide a back button in the top left corner of the page.
3. STICKY CONTENT
Avoid allowing the back button and header to scroll offscreen with the page’s content.
Do design the header to remain persistent in the UI, if possible.
Don’t try to maintain your app’s logo from the homepage if it means that the title of the detail page becomes can’t be positioned correctly.
Do consider alternate ways of including your app’s logo, if maintaining it on every page of your app is important.
5. ADDITIONAL CONTENT
Don’t make the detail page a larger version of its parent page, with no additional content or information.
Do make the user’s investment of visiting a new page worthwhile by providing new information and content in addition to the information from the parent page.
Don’t include breadcrumbs or other navigation on the canvas.
Do consider placing navigation in the top app bar to avoid forcing users into a lot of clicks to navigate from the detail page.
7. HUB ORDER
Don’t ignore the order in which you choose to arrange the hubs on the detail page.
Do order the hubs based on their importance to the user.
8. VISUAL LOOK & FEEL
Don’t dramatically change the visual identity of your app between pages without good reason.
Do maintain a consistent design language when moving from page to page within your app.
9. OTHER CONSIDERATIONS
Don’t disregard everything else that’s important to laying out a page in Windows 8, from Designing the Hub View
Do observe all the guidelines found in this handbook, including those that are applicable beyond the detail page specifically.