Initial Try .NET wiki push. Added themes.

Home.md

@@ -1 +1 @@
-Welcome to the try wiki!
+Welcome to the Try .NET  wiki!

TRY-.NET-Roadmap.md

@@ -1,7 +1,6 @@
-## Roadmap Over View 
+## Roadmap Overview 
 ---------------------
-Edited by Maria Naggaga PM 9/22/2017 
-Icon 
+
 
 | Icon          | Description   |
 | ------------- | ------------- |
@@ -10,31 +9,29 @@ Icon
 | blocked       | :key:         |
 | Released      | Content Cell  |
 | Stretch goal  | :tophat:      |
-## Themes 
 
-## Overview 
-Try .NET with Microsoft - dot.net  and docs.microsoft.com
-* Try .NET without leaving the browser
-* Enables new users to experiment and explore language syntax.
-* Use is restricted to Microsoft owned sites 
-    dot.net, docs.microsoft.com, asp.net, etc.
-* Console style output only
+## Try .NET Roadmap 2018 
+----------------------------
 
-Learn .NET with Microsoft - docs.microsoft.com
-* Build your first app without leaving the browser
-* Learn .NET without installing tools
-* Long lived user sessions working on a code base
-* Primarily used for tutorials on docs.microsoft.com
-* Beyond console - support ASP.NET content
+In 2017 we did a limited preview of Try .NET on docs.microsoft.com. Try .NET is a an inline code runner the scratchpad that enables people to experiment and learn .NET Core in the browser. 
 
-Learn .NET from your training provider
-* Make our infrastructure available to third party training providers
+*Note: Currently, Try.NET only supports C# but, we plan to support F# and VB in the near future.*
 
-Engaging .NET content everywhere
-* Engaging content wherever you encounter .NET
-* Runnable code snippets for websites, labs, blogs, etc.
-* Easy and free to for consumers to get started
+As we explore the next iteration of the service, we have created a set of themes that will work towards to provide value to our users. 
 
-Lighting up .NET everywhere 
-* Bing C# runnable snippets 
-* Teams and slack snippets
+### Try .NET Themes 
+
+- **Friction-free Exploration**: Try .NET  was created to enable users to test and explore .NET core in the browser.   In September 2017, we launched the first login-free Try .NET experience across docs.microsoft.com including [quick starts](https://docs.microsoft.com/en-us/dotnet/csharp/quick-starts/) and [reference documentation](https://docs.microsoft.com/en-us/dotnet/api/system.datetime?view=netcore-2.1). Over the course of the year, we will continue to expand these experiences across docs and 3rd party documentation.
+- **Simple to Embed**: As we grow our customer and user base, we want to enable seamless end to end experiences. It is not only essential for us to create friction-free user experiences but, to allow all .NET content developers to embed Try .NET easily to their documentation, blogs or websites. 
+- **Smooth transition to tools and services**: Getting started, exploring and testing with Try .NET is excellent. As a service, we want to enable our users to save their work to smoothly to repo or storage of your choice or easily open up their code in an editor(E.g. Code or VS).
+
+## Friction-free Exploration 
+
+From the begin(September 2017), we have worked to create easy ways for developers to explore and test .NET code in the browser.  For example, over the past six months, we have focused on supporting multiple console applications(*see image A and B*).  
+
+![image A](https://user-images.githubusercontent.com/2546640/31156287-a357ca5e-a881-11e7-88b9-100d09712a40.gif)
+*Image A*
+![image B](https://user-images.githubusercontent.com/2546640/31154776-60fc3820-a877-11e7-9330-ba7cdaa7e639.gif)
+*Image B*
+
+We still have a so much more we are eager to get done. Our community has asked for more  .NET Core app support.  As Try .NET expands to support more .NET Core applications, you will see a significant focus on the basic developer expectations.