Details pages form the basis of most screens in admin-style applications.

Details pages are usually divided into primary/secondary content columns, showing details for an individual entity such as an order, and keeping the most important content visually separated from less frequently used or non-essential information.

Details pages should:

• Use an application layout component to structure top-level page content, such as primary navigation, page headers and the page content.
• Use a page component to host the page content and optionally divide the page content into columns.
• Use card components to further structure the page content, visually grouping related content on a page.
• Use a page header to call attention to the identifying information about the page. The page header may optionally offer status information or actions that may be important enough to appear before the page content.
• Offer a navigation path back to the parent page or list page using the breadcrumb in the page header.