SharePoint 2013 has many great ways to help you get things done. We want to highlight a few of these, so we have created scenario pages that explain a specific scenario and provide content to help you understand, implement, and use it easily.

Scenario pages allow you to view key resources based on selected stages of evaluation or adoption. These stages are represented by colored tiles. Click a single tile for a specific stage or Ctrl-click multiple tiles for multiple stages. As you click the tiles, the scenario page lists the resources for each selected stage.

Content and resources are drawn from many Microsoft Web properties: IT content from TechNet, developer content from MSDN, and Information Worker content from Office.com are all integrated into the scenario page experience. All of the resources you need are available in one place, whether you want to understand:

  • Which features must be configured to support the scenario and how to manage them (TechNet content)
  • What namespaces and methods to use to develop customizations for the scenario (MSDN content)
  • Or how to accomplish a specific task in the scenario (Office content)

The following scenario pages are now available:

  • eDiscovery in SharePoint Server 2013 and Exchange Server 2013
    eDiscovery allows you to place electronic holds on documents and email for a legal case or audit. eDiscovery is a great example of a solution that benefits from a scenario page because it provides links to key resources published for SharePoint 2013, Exchange Server 2013, and Lync Server 2013.
  • Personal sites (My Sites) in SharePoint Server 2013
    My Sites technology provides profile data, activity feeds, tagging capabilities, and search results for each SharePoint user in your organization. When you deploy My Sites, each user gets a starting place in SharePoint that brings together the sites, documents, and other information that they care about and helps them share what they know.

We’ll be adding scenario pages over time, so check the SharePoint TechCenter for more!

Please take a look at the scenario pages and tell us what you think. You can leave comments on this blog post or send your comments to itspdocs@microsoft.com or askspdocs@microsoft.com. We’d love to hear from you.

- The SharePoint Content Publishing teams