Updated files related on the SP2016 Feature Pack 2 release.

Author: VesaJuvonen

docs/spfx/enterprise-guidance.md

@@ -161,7 +161,7 @@ What you cannot backup is the actual solution artifacts such as script bundles a
 
 ## SharePoint Framework Roadmap
 
-The SharePoint Framework reached General Availability (GA) in February 2017. General Availability means that IT and developers can supportably use SharePoint Framework in production. Beyond General Availability, we would expect that the set of scenarios where we would see SharePoint Framework-based components are built and used will expand beyond web parts scenarios, and into areas like list and site customizations. For more information about the SharePoint Framework see the dedicated [SharePoint Framework Roadmap article](https://dev.office.com/sharepoint/docs/spfx/roadmap). Also, the SharePoint team is looking to bring the SharePoint Framework to SharePoint 2016 on-premises during 2017, as part of a future Feature Pack.
+The SharePoint Framework reached General Availability (GA) in February 2017. General Availability means that IT and developers can supportably use SharePoint Framework in production. Beyond General Availability, we would expect that the set of scenarios where we would see SharePoint Framework-based components are built and used will expand beyond web parts scenarios, and into areas like list and site customizations. For more information about the SharePoint Framework see the dedicated [SharePoint Framework Roadmap article](https://dev.office.com/sharepoint/docs/spfx/roadmap). SharePoint Framework client-side web parts are also available in on-premises with SharePoint 2016 Feature Pack 2.
 
 Major changes or introduction of new major features will be announced through the Office 365 Message Center, found in your tenant admin - something that an Office 365 administrator already should have on their daily routine to check. Another important resource is the [Office Developer blog](http://dev.office.com/blogs) where you will find even more details and updates.
 

docs/spfx/known-issues-and-common-questions.md

@@ -19,15 +19,16 @@ You should update your Yeoman template packages. We have updated certification c
 
 - *Date - 6th of June*
 
-SharePoint Extensions with additional customizations capabilities for the SharePoint Online is now available for dev preview. We do not have public GA date currently. You can start learning how to build these extensions reading following tutorials.
+SharePoint Extensions with additional customizations capabilities for the SharePoint Online is now available as Release Candiate release. We do not have public GA date currently. You can start learning how to build these extensions reading following tutorials.
 
 * [Getting started with SharePoint Framework Extensions](http://aka.ms/spfx-extensions)
 
 **Will SharePoint Framework be available in on-premises?**
 
 - *Date - 6th of June*
+- *Updated - 12th of September*
 
-SharePoint Framework client-side web parts will be released to SharePoint 2016 as part of the Feature Pack 2 (FP2). 
+SharePoint Framework client-side web parts are now available as part of the SharePoint 2016 Feature Pack 2 (FP2). 
 
 ## Additional resources
 Please use following resources to provide feedback, comments and questions towards SharePoint engineering. 

docs/spfx/roadmap.md

@@ -10,7 +10,8 @@ First release of the SharePoint Framework will contain support for client-side w
 - Similar feature capabilities as in SharePoint Online
 - Target is to provide common development platform across on-premises and the cloud
 - Leveraging modern toolchain and open source on on-premises environments
-- Targeting SharePoint 2016 version during calendar year 2017
+
+> SharePoint 2016 support for client-side web parts was shipped with SharePoint 2016 Feature Pack 2 during September 2017.
 
 ## General improvements
 

docs/spfx/set-up-your-development-environment.md

@@ -65,7 +65,7 @@ Enter the following command to install the Yeoman SharePoint generator:
 ```
 npm install -g @microsoft/generator-sharepoint 
 ```
->**Note:** Yeoman generator for SharePoint is targeted to get deployed globally with the initial General Availability (GA) version. There are some known issues if it's installed locally to the project, which are planned to be addressed post GA.
+>**Note:** Yeoman generator for SharePoint can be installed both globally and locally. In this case we are installing the Yeoman generator for SharePoint to be available globally. 
 
 
 ## Optional tools

docs/spfx/sharepoint-2016-support.md

@@ -0,0 +1,69 @@
+# SharePoint Framework development with SharePoint 2016 Feature Pack 2
+
+SharePoint 2016 Feature Pack 2 support SharePoint Framework client-side web parts in classic SharePoint pages. 
+
+Introduction to SharePoint Framework development in SharePoint 2016 Feature Pack is also covered in following video at [SharePoint PnP YouTube Channel](https://www.youtube.com/watch?v=LGLMxnmHk6U&list=PLR9nK3mnD-OXZbEvTEPxzIOMGXj_aZKJG). 
+
+<a href="https://www.youtube.com/watch?v=LGLMxnmHk6U&list=PLR9nK3mnD-OXZbEvTEPxzIOMGXj_aZKJG">
+<img src="../../images/spfx-fp2-youtube-video.png" alt="Screenshot of the YouTube video player for this tutorial" />
+</a>
+
+## When to use which SharePoint Framework version?
+
+Since SharePoint Online and SharePoint 2016 has different release cycle for the new capabilities, they do support different capabilities also for the SharePoint Framework. SharePoint Online is always using the latest version of the SharePoint Framework, but SharePoint 2016 will support the version, which is matching server-side dependencies of the deployed packages.
+
+SharePoint 2016 Feature Pack 2 has support for the SharePoint Framework client-side web parts hosted in the classic SharePoint pages with SharePoint Framework v1.0. This means that when you are targeting your customization to SharePoint 2016 platform, you'll need to use SharePoint Framework v1.0.2 version due server-side version dependency. 
+
+If you are planning to use same client-side web parts in both SharePoint 2016 and in SharePoint Online, you will need to use the SharePoint Framework v1.0.2 as your baseline version to ensure that the web part works in both environments. 
+
+## Installing SharePoint Framework version for SP2016 development
+
+You should ensure that you are using the right version of SharePoint Framework in your development machine. You can check the currently globally installed SharePoint Framework Yeoman template package version by executing following command. 
+
+```
+npm list -g --depth 0
+```
+
+This will list the globally installed packages, including their versions. You can uninstall newer version by using following command.
+
+```
+npm uninstall -g @microsoft/generator-sharepoint
+```
+
+To install v1.0.2 version of the SharePoint Framework Yeoman templates, you can execute following command.
+
+```
+npm install -g @microsoft/[email protected]
+```
+
+## Hosting your SharePoint Framework solution for on-premises deployment
+
+Getting SharePoint Framework client-side web parts deployed to on-premises will require two distinct actions. 
+
+- Deployment of the solution package to SharePoint app catalog
+- Hosting JavaScript files in centralized ___location
+
+You can host JavaScript files in any suitable ___location for you depending on the environment details. These files can be for example hosted in following locations.
+
+- **Azure CDN** - Similar setup as with SharePoint Online. Does require end users to have Internet connectivity
+- **Local server in corporate network** - Server hosting the JavaScript files for the corporate network. This can be using whatever technology as long as files are accessible with http requests.
+- **SharePoint 2016** - You can also host your files in the local SharePoint farm. You can for example define a standardized site in your farm where all the SharePoint Framework assets are being hosted. Notice though that by default .json files are not allowed to be uploaded to SharePoint 2016 libraries, so farm level settings will need to be adjusted for this option.   
+
+> You can find more details on the blocked file types in SharePoint 2016 from following support article: [Types of files that cannot be added to a list or library](https://support.office.com/en-us/article/Types-of-files-that-cannot-be-added-to-a-list-or-library-30be234d-e551-4c2a-8de8-f8546ffbf5b3#ID0EAADAAA=2016)
+
+## Development environment considerations 
+
+When you are developing SharePoint Framework client-side web parts, you should have normally Internet connectivity to access npm packages. This is required when solutions are being scaffold using SharePoint Framework Yeoman templates.
+
+If Internet access is not available for the development machines, you can also setup local on-premises registry for needed npm packages. This does however require additional software and significant amount of work to operation and to update based on new versions and packages in actual npm gallery.
+
+> [Team-based development on the SharePoint Framework](team-based-development-on-sharepoint-framework.md) guidance includes different options around the development environment setup also when you might need to support multiple SharePoint Framework versions. 
+
+## How to determine which SharePoint Framework version was used for a solution?
+
+If you have already existing SharePoint Framework solutions and you'd like to confirm the used SharePoint Framework version for them, you'll need to confirm this potentially from following locations. 
+
+- **.yo-rc.json** file in solution root folder defines used SharePoint Framework Yeoman template version when the solution was created.
+- **package.json** file in the solution root folder contains references to versions when the solution was created.
+- **npm-shrinkwrap.json** file in the solution root folder will contain information on the exact versions, if you have used the `npm shrinkwrap` command for the solution to lock-down the exact versions.
+-- **package.json** file in *node_modules\@microsoft/sp-webpart-base* folder contains a *version* attribute matching used SharePoint Framework version, if you have installed packages to your solution.

docs/spfx/sharepoint-framework-overview.md

@@ -1,6 +1,6 @@
 # Overview of the SharePoint Framework
 
-The SharePoint Framework (SPFx) is a page and web part model that provides full support for client-side SharePoint development, easy integration with SharePoint data, and support for open source tooling. With the SharePoint Framework, you can use modern web technologies and tools in your preferred development environment to build productive experiences and apps that are responsive and mobile-ready from day one. The SharePoint Framework works for SharePoint Online and soon also for on-premises (SharePoint 2016 Feature Pack 2).
+The SharePoint Framework (SPFx) is a page and web part model that provides full support for client-side SharePoint development, easy integration with SharePoint data, and support for open source tooling. With the SharePoint Framework, you can use modern web technologies and tools in your preferred development environment to build productive experiences and apps that are responsive and mobile-ready from day one. The SharePoint Framework works for SharePoint Online and also for on-premises (SharePoint 2016 Feature Pack 2).
 
 Key features of the SharePoint Framework include:
 

images/spfx-fp2-youtube-video.png

@@ -7,6 +7,7 @@
 		<Item text="Tools and libraries" url="spfx/tools-and-libraries" SEODescription="Learn about the tools and libriaries you will need to use to build your SharePoint Framework solutions."/>
 		<Item text="Set up your Office 365 tenant" url="spfx/set-up-your-developer-tenant" SEODescription="Set up an Office 365 tenant so that you can test and debug your SharePoint client-side web parts" />
 		<Item text="Set up your development environment" url="spfx/set-up-your-development-environment" SEODescription="Set up and configure your development environment to build SharePoint client-side web parts" />
+		<Item text="SharePoint 2016 support" url="spfx/sharepoint-2016-support" SEODescription="SharePoint Framework development with SharePoint 2016 Feature Pack 2" />
 		<Item text="Debug solutions with VS Code" url="spfx/debug-in-vscode" SEODescription="Debug SharePoint Framework solutions in Visual Studio Code" />
 		<Item text="Enterprise Guidance" url="spfx/enterprise-guidance" SEODescription="SharePoint Framework Enterprise architecture and development guidance." />
 		<Item text="Team-based development" url="spfx/team-based-development-on-sharepoint-framework" SEODescription="Team-based development on SharePoint Framework." />