Adding reference to issue list to main tutorials

VesaJuvonen · VesaJuvonen · commit 1f752afb40ff · 2017-12-08T10:35:31.000+02:00
diff --git a/docs/images/spfx-youtube-tutorial1.png b/docs/images/spfx-youtube-tutorial1.png
diff --git a/docs/spfx/extensions/get-started/build-a-hello-world-extension.md b/docs/spfx/extensions/get-started/build-a-hello-world-extension.md
@@ -161,3 +161,6 @@ This dialog is thrown by your SharePoint Framework Extension. Note that because
 
 ## Next steps
 Congratulations, you've gotten your first SharePoint Framework Extension running! To continue building out your extension, see [Using page placeholders from Application Customizer (Hello World part 2)](./using-page-placeholder-with-extensions.md). You will use the same project and take advantage of specific content placeholders for modifying the UI of SharePoint. Notice that the ```gulp serve``` command is still running in your console window (or in Visual Studio Code if you are using the editor). You can continue to let it run while you go to the next article.
+
+> [!NOTE]
+> If you find an issue in the documentation or in the SharePoint Framework, please report that to SharePoint engineering using the [issue list at sp-dev-docs repository](https://github.com/SharePoint/sp-dev-docs/issues). Thanks for your input advance.
diff --git a/docs/spfx/extensions/get-started/building-simple-cmdset-with-dialog-api.md b/docs/spfx/extensions/get-started/building-simple-cmdset-with-dialog-api.md
@@ -375,3 +375,6 @@ Now you are ready to deploy the solution to a SharePoint site and to have the `C
     Notice how **Command One** and **Command Two** are rendering in the toolbar based on your ListView Command Set customizations. 
 
     ![Additional buttons visible on the toolbar](../../../images/ext-com-dialog-visible-deployment.png)
+
+> [!NOTE]
+> If you find an issue in the documentation or in the SharePoint Framework, please report that to SharePoint engineering using the [issue list at sp-dev-docs repository](https://github.com/SharePoint/sp-dev-docs/issues). Thanks for your input advance.
diff --git a/docs/spfx/extensions/get-started/building-simple-field-customizer.md b/docs/spfx/extensions/get-started/building-simple-field-customizer.md
@@ -402,3 +402,6 @@ Now you are ready to deploy the solution to a SharePoint site and get the field
 In this case, we continued to host the JavaScript from the localhost, but you could just as well relocate the assets to any CDN and update the URL to enable the loading of the JavaScript assets outside of the localhost as well.
 
 The process for publishing your app is identical among the different extension types. You can use the following publishing steps to update the assets to be hosted from a CDN: [Host extension from Office 365 CDN](./hosting-extension-from-office365-cdn.md).
+
+> [!NOTE]
+> If you find an issue in the documentation or in the SharePoint Framework, please report that to SharePoint engineering using the [issue list at sp-dev-docs repository](https://github.com/SharePoint/sp-dev-docs/issues). Thanks for your input advance.
diff --git a/docs/spfx/extensions/get-started/hosting-extension-from-office365-cdn.md b/docs/spfx/extensions/get-started/hosting-extension-from-office365-cdn.md
@@ -106,3 +106,6 @@ When the origin is listed without the `(configuration pending)` text, it is read
 <br/>
 
 Congratulations, you have enabled a public CDN in your Office 365 tenant and taken advantage of it from your solution!
+
+> [!NOTE]
+> If you find an issue in the documentation or in the SharePoint Framework, please report that to SharePoint engineering using the [issue list at sp-dev-docs repository](https://github.com/SharePoint/sp-dev-docs/issues). Thanks for your input advance.
diff --git a/docs/spfx/extensions/get-started/serving-your-extension-from-sharepoint.md b/docs/spfx/extensions/get-started/serving-your-extension-from-sharepoint.md
@@ -165,3 +165,6 @@ When the application has been successfully installed, you can see the header and
 ## Next steps
 
 Congratulations, you have deployed an extension to a modern SharePoint page from the app catalog! You can continue building out your Hello World extension in the next topic, [Host extension from Office 365 CDN (Hello World part 4)](./hosting-extension-from-office365-cdn.md), where you will learn how to deploy and load the extension assets from a CDN instead of from localhost.
+
+> [!NOTE]
+> If you find an issue in the documentation or in the SharePoint Framework, please report that to SharePoint engineering using the [issue list at sp-dev-docs repository](https://github.com/SharePoint/sp-dev-docs/issues). Thanks for your input advance.
diff --git a/docs/spfx/extensions/get-started/using-page-placeholder-with-extensions.md b/docs/spfx/extensions/get-started/using-page-placeholder-with-extensions.md
@@ -247,3 +247,6 @@ You should now see the custom header and footer content in your page.
 
 ## Next steps
 Congratulations, you've built your own custom header and footer using the Application Customizer! To continue building out your extension, see [Deploy your extension to SharePoint (Hello World part 3)](./serving-your-extension-from-sharepoint.md). You will learn how to deploy and preview the Hello World extension in a SharePoint site collection without using **Debug** query parameters. 
+
+> [!NOTE]
+> If you find an issue in the documentation or in the SharePoint Framework, please report that to SharePoint engineering using the [issue list at sp-dev-docs repository](https://github.com/SharePoint/sp-dev-docs/issues). Thanks for your input advance.
diff --git a/docs/spfx/extensions/guidance/using-custom-dialogs-with-spfx.md b/docs/spfx/extensions/guidance/using-custom-dialogs-with-spfx.md
@@ -275,3 +275,6 @@ Click the *Open Custom Dialog box* button to see your custom dialog box rendered
 Choose a color in the *Color Picker* and choose **OK** to test how the code is returning the selected value back to the caller. The selection is then shown using the default alert dialog box.
 
 ![Dialog with picked color details](../../../images/ext-com-dialog-oob-alert-dialog.png)
+
+> [!NOTE]
+> If you find an issue in the documentation or in the SharePoint Framework, please report that to SharePoint engineering using the [issue list at sp-dev-docs repository](https://github.com/SharePoint/sp-dev-docs/issues). Thanks for your input advance.
diff --git a/docs/spfx/set-up-your-development-environment.md b/docs/spfx/set-up-your-development-environment.md
@@ -94,3 +94,6 @@ Here are some tools that might come in handy as well:
 ## Next steps
 
 You are now ready to [build your first client-side web part](web-parts/get-started/build-a-hello-world-web-part.md)!
+
+> [!NOTE]
+> If you find an issue in the documentation or in the SharePoint Framework, please report that to SharePoint engineering using the [issue list at sp-dev-docs repository](https://github.com/SharePoint/sp-dev-docs/issues). Thanks for your input advance.
diff --git a/docs/spfx/web-parts/get-started/add-jqueryui-accordion-to-web-part.md b/docs/spfx/web-parts/get-started/add-jqueryui-accordion-to-web-part.md
@@ -346,3 +346,6 @@ In the page canvas, choose the **+** (plus sign) to show the list of web parts,
 ![Screenshot of a web part that includes a jQuery Accordion](../../../images/jquery-accordion-wb.png)
 
 In the console where you have `gulp serve` running, choose **Ctrl+C** to terminate the task.
+
+> [!NOTE]
+> If you find an issue in the documentation or in the SharePoint Framework, please report that to SharePoint engineering using the [issue list at sp-dev-docs repository](https://github.com/SharePoint/sp-dev-docs/issues). Thanks for your input advance.
diff --git a/docs/spfx/web-parts/get-started/build-a-hello-world-web-part.md b/docs/spfx/web-parts/get-started/build-a-hello-world-web-part.md
@@ -383,3 +383,6 @@ Because you are still developing and testing your web part, there is no need to
 
 ## Next steps
 Congratulations on getting your first Hello World web part running! Now that your web part is running, you can continue building out your Hello World web part in the next topic, [Connect to SharePoint](./connect-to-sharepoint.md). You will use the same Hello World web part project and add the ability to interact with SharePoint List REST APIs. Notice that the `gulp serve` command is still running in your console window (or in Visual Studio Code if you using that as editor). You can continue to let it run while you go to the next article.
+
+> [!NOTE]
+> If you find an issue in the documentation or in the SharePoint Framework, please report that to SharePoint engineering using the [issue list at sp-dev-docs repository](https://github.com/SharePoint/sp-dev-docs/issues). Thanks for your input advance.
diff --git a/docs/spfx/web-parts/get-started/connect-to-sharepoint.md b/docs/spfx/web-parts/get-started/connect-to-sharepoint.md
@@ -370,3 +370,6 @@ Now you can stop the server from running. Switch to the console and stop `gulp s
 ## Next steps
 
 Congratulations on connecting your web part to SharePoint list data! You can continue building out your Hello World web part in the next topic [Deploy your web part to a SharePoint page](./serve-your-web-part-in-a-sharepoint-page.md). You will learn how to deploy and preview the Hello World web part in a SharePoint page.
+
+> [!NOTE]
+> If you find an issue in the documentation or in the SharePoint Framework, please report that to SharePoint engineering using the [issue list at sp-dev-docs repository](https://github.com/SharePoint/sp-dev-docs/issues). Thanks for your input advance.
diff --git a/docs/spfx/web-parts/get-started/deploy-web-part-to-cdn.md b/docs/spfx/web-parts/get-started/deploy-web-part-to-cdn.md
@@ -290,4 +290,7 @@ In order to deploy the assets to your favorite CDN provider, you can copy the fi
 gulp bundle --ship
 ```
 
-As long as you are updating the **cdnBasePath** accordingly, your files are being properly loaded.
+As long as you are updating the **cdnBasePath** accordingly, your files are being properly loaded.
+
+> [!NOTE]
+> If you find an issue in the documentation or in the SharePoint Framework, please report that to SharePoint engineering using the [issue list at sp-dev-docs repository](https://github.com/SharePoint/sp-dev-docs/issues). Thanks for your input advance.
diff --git a/docs/spfx/web-parts/get-started/hosting-webpart-from-office-365-cdn.md b/docs/spfx/web-parts/get-started/hosting-webpart-from-office-365-cdn.md
@@ -24,7 +24,7 @@ Make sure that you have completed the following tasks before you begin:
 You can also follow follow these steps by watching the video on the [SharePoint PnP YouTube Channel](https://www.youtube.com/watch?v=AIb7s_Y02K8&list=PLR9nK3mnD-OXvSWvS2zglCzz4iplhVrKq&index=5). 
 
 <a href="https://www.youtube.com/watch?v=AIb7s_Y02K8&list=PLR9nK3mnD-OXvSWvS2zglCzz4iplhVrKq&index=5">
-<img src="../../../images/spfx-youtube-tutorial2.png" alt="Screenshot of the YouTube video player for this tutorial" />
+<img src="../../../images/spfx-youtube-tutorial4.png" alt="Screenshot of the YouTube video player for this tutorial" />
 </a>
 
 
@@ -174,3 +174,6 @@ Now you have deployed your custom web part to SharePoint Online and it's being h
 ## Next steps
 
 You can load jQuery, jQuery UI and build a jQuery Accordion web part. To continue, see [Add jQueryUI Accordion to your client-side web part](./add-jqueryui-accordion-to-web-part.md).
+
+> [!NOTE]
+> If you find an issue in the documentation or in the SharePoint Framework, please report that to SharePoint engineering using the [issue list at sp-dev-docs repository](https://github.com/SharePoint/sp-dev-docs/issues). Thanks for your input advance.
diff --git a/docs/spfx/web-parts/get-started/provision-sp-assets-from-package.md b/docs/spfx/web-parts/get-started/provision-sp-assets-from-package.md
@@ -470,3 +470,6 @@ Update can take a while, but when the solution status is moved to normal again,
 ![Site contents page with additional New List being created](../../../images/tutorial-feature-solution-new-list.png)
 
 Now we have successfully upgrade this instance to the latest version. This Feature Framework option for SharePoint asset provisioning is pretty much the same as it is for the SharePoint add-in model. Key difference however is that the assets are being provisioned directly to normal SharePoint site, since there's no concept called app / add-in web with SharePoint Framework solutions.
+
+> [!NOTE]
+> If you find an issue in the documentation or in the SharePoint Framework, please report that to SharePoint engineering using the [issue list at sp-dev-docs repository](https://github.com/SharePoint/sp-dev-docs/issues). Thanks for your input advance.
diff --git a/docs/spfx/web-parts/get-started/serve-your-web-part-in-a-sharepoint-page.md b/docs/spfx/web-parts/get-started/serve-your-web-part-in-a-sharepoint-page.md
@@ -177,3 +177,6 @@ In the toolbar, choose **Save and close** to save the page.
 ## Next steps
 
 Congratulations! You have deployed a client-side web part to a modern SharePoint page. You can continue building out your Hello World web part in the next topic, [Hosting client-side web part from Office 365 CDN](./hosting-webpart-from-office-365-cdn.md), where you will learn how to deploy and load the web part assets from a Office 365 CDN instead of localhost.
+
+> [!NOTE]
+> If you find an issue in the documentation or in the SharePoint Framework, please report that to SharePoint engineering using the [issue list at sp-dev-docs repository](https://github.com/SharePoint/sp-dev-docs/issues). Thanks for your input advance.
diff --git a/docs/spfx/web-parts/get-started/use-fabric-react-components.md b/docs/spfx/web-parts/get-started/use-fabric-react-components.md
@@ -251,3 +251,6 @@ gulp serve
 In the toolbox, select your `DocumentCardExample` web part to add:
 	
 ![Image of a DocumentCard Fabric component in a SharePoint workbench](../../../images/fabric-components-doc-card-view-ex.png)
+
+> [!NOTE]
+> If you find an issue in the documentation or in the SharePoint Framework, please report that to SharePoint engineering using the [issue list at sp-dev-docs repository](https://github.com/SharePoint/sp-dev-docs/issues). Thanks for your input advance.
