Documentation TOC refactoring & updates (SharePoint#5316)

andrewconnell · web-flow · commit 185d6c5b1fe5 · 2020-02-14T11:06:30.000+02:00
- Renamed "Solution guidance" =&gt; "Scenario Guidance"
- Renamed "SharePoint development overview" =&gt; "Archive"
  - contains loads of old content &amp; deemed "outdated" by MSFT
  - will update on an as-needed basis
- Refactored / reorganized:
  - SPFx
  - Addins
  - Community
- Added "Overview" nodes to items that expand
  - Removes the dupe of a section &amp; first node with same name
- Renamed "Features" to "Capabilities &amp; features"
  - Removes confusion if it's a Feature (ie: feature.xml)
  - Moved declarative customization options =&gt; this new section
diff --git a/docs/community/contribute.md b/docs/community/contribute.md
@@ -46,4 +46,3 @@ Awesome! Here are a few suggestions:
 * Suggest a live demo in one of the community calls.
 
 If you have other ideas on how you might contribute, don't hesitate to reach out and let us know.
-
diff --git a/docs/community/social-media.md b/docs/community/social-media.md
@@ -0,0 +1,17 @@
+---
+title: Social Media
+author: andrewconnell
+ms.author: v-johnco
+ms.date: 2/5/2020
+ms.audience: Developer
+ms.prod: sharepoint
+localization_priority: Priority
+---
+
+# SharePoint Development on Social Media
+
+Please monitor and follow us on Twitter:
+
+- [@Microsoft365Dev](https://twitter.com/Microsoft365Dev)
+- [@OfficeDev](https://twitter.com/officedev)
+- [@SharePoint](https://twitter.com/sharepoint)
diff --git a/docs/general-development/sharepoint-2019-development-platform.md b/docs/general-development/sharepoint-2019-development-platform.md
@@ -10,26 +10,26 @@ localization_priority: Priority
 
 Article contains details around supported development capabilities in the SharePoint 2019.
 
-**Supported capabilities**
-
-* Modern and classic pages
-* Modern sites - modern team and communication site
-    * Classic sites are also supported
-* Column formatting - Only supports "Basic Styled Syntax", "Excel Styled Syntax" is not supported. 
-* SharePoint Framework client-side web parts with SharePoint Framework v1.4.x
-* SharePoint Framework extensions in modern experiences with SharePoint Framework v1.4.x
-* Webhooks for list items
-* Asset packaging and automatic JavaScript file hosting from app catalog
-* "Tenant" scoped deployment of SharePoint Framework solutions
-* ALM APIs for add-in and SharePoint Framework solution management
-
-**Not supported capabilities**
-
-* Site Designs and Site Scripts
-* Hub sites
-* Site collection app catalog
-* "Tenant" properties
-* Custom modern themes for communication site or modern team site
+## Supported capabilities
+
+- Modern and classic pages
+- Modern sites - modern team and communication site
+  - Classic sites are also supported
+- Column formatting - Only supports "Basic Styled Syntax", "Excel Styled Syntax" is not supported.
+- SharePoint Framework client-side web parts with SharePoint Framework v1.4.x
+- SharePoint Framework extensions in modern experiences with SharePoint Framework v1.4.x
+- Webhooks for list items
+- Asset packaging and automatic JavaScript file hosting from app catalog
+- "Tenant" scoped deployment of SharePoint Framework solutions
+- ALM APIs for add-in and SharePoint Framework solution management
+
+## Not supported capabilities
+
+- Site Designs and Site Scripts
+- Hub sites
+- Site collection app catalog
+- "Tenant" properties
+- Custom modern themes for communication site or modern team site
 
 You should always have the latest SharePoint Framework version installed and choose the target environment for the newly created solution to be **SharePoint 2019**. This option will create you an optimal solution structure with the matching SharePoint Framework version for SharePoint 2019.
 
diff --git a/docs/spfx/sharepoint-2016-support.md b/docs/spfx/sharepoint-2016-support.md
@@ -56,11 +56,8 @@ The [Team-based development on the SharePoint Framework](team-based-development-
 If you have existing SharePoint Framework solutions and you'd like to confirm which version of the SharePoint Framework was used for them, you'll need to check the following locations:
 
 - **.yo-rc.json**. File in the solution's root folder that stores the SharePoint Framework Yeoman template version used when the solution was created.
-
 - **package.json**. File in the solution's root folder that contains references to package versions used in the solution.
-
 - **npm-shrinkwrap.json**. File in the solution's root folder that contains information about the exact versions used (if you used the `npm shrinkwrap` command to lock down the exact versions of the solution).
-
 - **package.json**. File in the *node_modules/@microsoft/sp-webpart-base* folder that contains a *version* attribute matching the used SharePoint Framework version, if you have installed packages to your solution.
 
 ## See also
diff --git a/docs/spfx/sharepoint-2019-support.md b/docs/spfx/sharepoint-2019-support.md
@@ -0,0 +1,40 @@
+---
+title: SharePoint Framework development with SharePoint 2019
+description: SharePoint 2019 supports SharePoint Framework client-side web parts in classic and pages, as well as extensions in modern pages.
+ms.date: 02/10/2020
+localization_priority: Priority
+---
+
+# SharePoint Framework development with SharePoint Server 2019
+
+SharePoint 2019 supports SharePoint Framework client-side web parts in classic and pages, as well as extensions in modern pages.
+
+## Which version of the SharePoint Framework to use
+
+Because SharePoint Online and SharePoint 2019 have different release cycles for new capabilities, they also have different capabilities when it comes to the SharePoint Framework. SharePoint Online always uses the latest version of the SharePoint Framework, but SharePoint 2019 only supports the version that matches the server-side dependencies of the deployed packages.
+
+SharePoint 2019 supports SharePoint Framework client-side web parts hosted on classic or modern SharePoint pages built by using the SharePoint Framework v1.4.1. SharePoint 2019 also supposed SharePoint Framework extensions hosted on modern SharePoint pages built using SharePoint Framework v1.4.1 This means that when you are targeting the SharePoint 2019 platform, you need to use the SharePoint Framework v1.4.1 due to the server-side version dependencies.
+
+Starting from v1.3, the SharePoint Framework Yeoman generator supports scaffolding solutions that use both the latest version of the SharePoint Framework meant for use with SharePoint Online, and solutions that can be used with SharePoint on-premises based on the v1.1.0 or v1.4.1 of the SharePoint Framework. You don't need to install a separate version of the SharePoint Framework Yeoman generator to scaffold solutions meant for use with SharePoint on-premises.
+
+## Development environment considerations
+
+When you are developing SharePoint Framework client-side web parts, you need Internet connectivity to access npm packages. This is required when solutions are being scaffolded by using the SharePoint Framework Yeoman templates.
+
+If Internet access is not available for the development machines, you can set up a local on-premises registry for the required npm packages. However, this requires additional software and a significant amount of work to set up and maintain local package versions with packages in the actual npm gallery.
+
+The [Team-based development on the SharePoint Framework](team-based-development-on-sharepoint-framework.md) guidance document includes different options for development environment setup including when you might need to support multiple SharePoint Framework versions.
+
+## Determine which version was used for a solution
+
+If you have existing SharePoint Framework solutions and you'd like to confirm which version of the SharePoint Framework was used for them, you'll need to check the following locations:
+
+- **.yo-rc.json**. File in the solution's root folder that stores the SharePoint Framework Yeoman template version used when the solution was created.
+- **package.json**. File in the solution's root folder that contains references to package versions used in the solution.
+- **npm-shrinkwrap.json**. File in the solution's root folder that contains information about the exact versions used (if you used the `npm shrinkwrap` command to lock down the exact versions of the solution).
+- **package.json**. File in the *node_modules/@microsoft/sp-webpart-base* folder that contains a *version* attribute matching the used SharePoint Framework version, if you have installed packages to your solution.
+
+## See also
+
+- [SharePoint Framework Overview](sharepoint-framework-overview.md)
+- [SharePoint Server 2019 development platform](../general-development/sharepoint-2019-development-platform.md)
diff --git a/docs/support-feedback.md b/docs/support-feedback.md
@@ -0,0 +1,37 @@
+---
+title: Support and Feedback
+author: andrewconnell
+ms.author: v-johnco
+ms.date: 2/5/2020
+ms.audience: Developer
+ms.prod: sharepoint
+localization_priority: Priority
+---
+
+# Support and feedback
+
+The SharePoint product team responds to the developer community across several channels.
+
+## Programming questions
+
+**GitHub sp-dev-docs**: We regularly monitor questions submitted to the [GitHub sp-dev-docs issue list](https://github.com/SharePoint/sp-dev-docs/issues). Follow the [guidance](https://github.com/SharePoint/sp-dev-docs/wiki/How-to-Create-Good-Issues) on creating a good issue.
+
+**Stack Overflow**: We listen and respond on [Stack Overflow](http://stackoverflow.com/questions/tagged/microsoft-teams). Follow the [guidance](http://stackoverflow.com/tour) about what makes a good question on Stack Overflow.
+
+[Tag your question](https://stackoverflow.com/tags) with one of the many `sharepoint` or `spfx` tags so that our team and the SharePoint developer community can spot your question.
+
+## Documentation bugs
+
+If you find a bug in the SharePoint developer documentation, open an [issue](https://github.com/SharePoint/sp-dev-docs/issues) on GitHub. Be sure to tell us which topic is factually incorrect or unclear.
+
+To help us fix the problem more quickly, quote the text to be changed.
+
+## Sample application bugs
+
+If you find a bug in one of our samples. Please leave a comment on the sample (if it's in the documentation site) or open an issue (if it's in a sample within one of the [GitHub repositories we maintain](community/repositories.md)).
+
+Be sure to describe the steps to reproduce the bug.
+
+## Feature requests
+
+If our platform doesn't empower you to do what you need, or if you have an idea for a new feature, or change to an existing, please make your features suggestions on the [Microsoft SharePoint Dev Platform feedback portal on UserVoice](https://aka.ms/spdev-uservoice).
diff --git a/docs/toc.yml b/docs/toc.yml

Original file line number	Diff line number	Diff line change
`@@ -46,4 +46,3 @@ Awesome! Here are a few suggestions:`
`46`	`46`	`* Suggest a live demo in one of the community calls.`
`47`	`47`
`48`	`48`	`If you have other ideas on how you might contribute, don't hesitate to reach out and let us know.`
`49`		`-`