I stumbled upon J.D. Meier's blog, and see these interesting ideas of Code Sample Maps and Scenario Maps.

Code Sample Maps

For each area (ADO.NET, ASP.NET, etc.) we did a map of Code Samples pulling from All-in-One Code Framework, Channel9, CodePlex, Code Gallery, MSDN Dev Centers, and MSDN Library.  You can see their code samples roundup at -- http://blogs.msdn.com/b/jmeier/archive/2010/11/01/code-sample-collections-roundup-for-ado-net-asp-net-silverlight-wcf-windows-azure-and-windows-phone.aspx.

Scenario Maps / Customer Needs

http://blogs.msdn.com/b/jmeier/archive/2010/10/31/scenario-maps-roundup-for-ado-net-asp-net-silverlight-wcf-windows-azure-and-windows-phone.aspx

In J.D.Meier's words: "Scenario Maps are a simple way we collect, organize, and share user scenarios for a given problem space or technology.  They serve as a fast and scannable index of the problems that users face.  They are one of the most effective ways to see the forest from the trees.  Rather than get lost in a single scenario, they are a step back and a look across all the key scenarios.  This helps for ranking and prioritizing the problems for a given space. "

You are encouraged to scan the Scenarios Map and either share your scenarios in the comments or email your scenarios to feedbackandthought at live.com.  Be sure to share your scenarios in the form of “how to blah, blah, blah …” – this makes it much easier to act on and update the map.