Updates to align with modernization content move

Author: jansenbe

docs/community/repositories.md

@@ -22,6 +22,7 @@ There are numerous SharePoint Developer GitHub repositories, which all have diff
 | [sp-dev-docs](https://github.com/SharePoint/sp-dev-docs) | Source for SharePoint dev documentation exposed at http://docs.microsoft.com/sharepoint/dev/ |
 | [sp-dev-fx-webparts](https://github.com/SharePoint/sp-dev-fx-webparts) | Samples and tutorial code around SharePoint Framework client-side web parts |
 | [sp-dev-fx-extensions](https://github.com/SharePoint/sp-dev-fx-extensions) | Samples and tutorial code around SharePoint Framework extensions |
+| [sp-dev-modernization](https://github.com/SharePoint/sp-dev-modernization) | Solutions, tools and script to help you modernize your sites |
 | [sp-dev-solutions](https://github.com/SharePoint/sp-dev-solutions) | More polished and fine-tuned reusable solutions built with the SharePoint Framework |
 | [sp-dev-list-formatting](https://github.com/SharePoint/sp-dev-list-formatting) | Various [column formatting](https://docs.microsoft.com/en-us/sharepoint/dev/declarative-customization/column-formatting) json files shared among the community |
 | [sp-dev-site-scripts](https://github.com/SharePoint/sp-dev-site-scripts) | Various [Site Script and Site Design](https://docs.microsoft.com/en-us/sharepoint/dev/declarative-customization/site-design-overview) json files shared among the community |

docs/features/groupify/groupify-overview.md

@@ -32,7 +32,7 @@ After your site is connected to an Office 365 group, it behaves like a modern gr
 ## See also
 
 - [Connect a classic SharePoint team site to a new Office 365 group](../../transform/modernize-connect-to-office365-group.md)
-- [SharePoint Modernization scanner tool](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.Modernization)
+- [SharePoint Modernization scanner tool](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization)
 - [PowerShell cmdlet to connect a SharePoint team site to a new Office 365 group](https://docs.microsoft.com/en-us/powershell/module/sharepoint-online/Set-SPOSiteOffice365Group)
 - [Modernize your classic SharePoint sites](../../transform/modernize-classic-sites.md)
 

docs/scenario-guidance/Branding.md

@@ -53,7 +53,7 @@ In 2016, the SharePoint Online team released "modern" collaboration sites. These
 ### Solutions
 
 - [SharePoint Framework Extension samples](https://github.com/SharePoint/sp-dev-fx-extensions)
-- [SharePoint "Modern" user interface experience scanner](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.UIExperience.Scanner)
+- [SharePoint Modernization scanner](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization)
 
 ### Videos
 
@@ -80,7 +80,7 @@ The classic SharePoint user experience is based on ASP.NET master pages and page
 ### Solutions
 
 - [SharePoint 2013/2016/Online Responsive UI](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.UI.Responsive)
-- [SharePoint "Modern" user interface experience scanner](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.UIExperience.Scanner)
+- [SharePoint Modernization scanner](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization)
 - [PnP Starter Intranet for SharePoint 2013/2016 and SharePoint Online](https://dev.office.com/patterns-and-practices-detail/11128)
 
 ### Videos
@@ -161,7 +161,7 @@ Because Microsoft SharePoint is built on top of Microsoft ASP.NET, it supports m
 
 ### Solutions
 
-- [SharePoint "Modern" user interface experience scanner](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.UIExperience.Scanner)
+- [SharePoint Modernization scanner](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization)
 - [PnP PowerShell branding cmdlets](https://docs.microsoft.com/en-us/powershell/sharepoint/sharepoint-pnp/sharepoint-pnp-cmdlets?view=sharepoint-ps#branding)
 - [Transformation tool](https://github.com/SharePoint/PnP-Transformation/tree/master/Transformation%20Tool%20-%20CSOM#introduction)
 
@@ -195,7 +195,7 @@ Cascading style sheet (CSS) plays a large role in SharePoint branding. To succes
 - [SharePoint 2013/2016/Online Responsive UI](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.UI.Responsive)
 - [Activate the PnP Responsive UI Add-on using PnP PowerShell](https://msdn.microsoft.com/en-us/pnp_powershell/enablepnpresponsiveui)
 - [CSS Injection Pattern sample](https://github.com/SharePoint/PnP/tree/master/Samples/Branding.CustomCSS)
-- [SharePoint "Modern" user interface experience scanner](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.UIExperience.Scanner)
+- [SharePoint Modernization scanner](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization)
 - [Transformation tool](https://github.com/SharePoint/PnP-Transformation/tree/master/Transformation%20Tool%20-%20CSOM#introduction)
 
 ### Samples

docs/transform/modernize-scanner.md

@@ -20,7 +20,7 @@ This scanner is a key tool to use if you want to prepare for modernizing your cl
 
 Since SharePoint Online continuously evolves and more and more modern capabilities are added it's important to always download the latest version of the scanner. Downloading is as simple as:
 
-- Going the [scanner download page](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.Modernization)
+- Going the [scanner download page](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization)
 - Download the zip file mentioned in the "Quick start guide" section
 - **Unpacking the zip file to folder on your computer**. Once you've downloaded the tool, unzip it to a local folder which will contain the SharePoint.Modernization.Scanner.exe and webpartmapping.xml files
 
@@ -162,8 +162,8 @@ SharePoint PnP Modernization scanner 2.2.0.0
 Copyright (C) 2018 SharePoint PnP
 ==========================================================
 
-See the PnP-Tools repo for more information at:
-https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.Modernization.Scanner
+See the sp-dev-modernization repo for more information at:
+https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization
 
 Let the tool figure out your urls (works only for SPO MT):
 ==========================================================

docs/transform/modernize-userinterface-site-pages-configuration.md

@@ -10,7 +10,7 @@ ms.prod: sharepoint
 When you use the page transformation framework you do have a lot of control on how the page transformation is done. The model to control this is by specifying the correct configuration as part of the `PageTransformationInformation` instance that you use to launch page transformation. In this article you'll learn more about the available options.
 
 > [!IMPORTANT]
-> The SharePoint PnP Modernization framework is continuously evolving, checkout [the release notes](https://github.com/SharePoint/PnP-Tools/blob/master/Solutions/SharePoint.Modernization/Modernization%20Framework%20release%20notes.md) to stay up to date on the latest changes. If you encounter problems please file an issue in the [PnP Tools GitHub issue list](https://github.com/SharePoint/PnP-Tools/issues).
+> The SharePoint PnP Modernization framework is continuously evolving, checkout [the release notes](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization/Modernization%20Framework%20release%20notes.md) to stay up to date on the latest changes. If you encounter problems please file an issue in the [PnP Tools GitHub issue list](https://github.com/SharePoint/sp-dev-modernization/issues).
 
 ## Overwrite option
 

docs/transform/modernize-userinterface-site-pages-dotnet.md

@@ -8,7 +8,7 @@ ms.prod: sharepoint
 # Transforming to modern site pages using .Net
 
 > [!IMPORTANT]
-> The SharePoint PnP Modernization framework is continuously evolving, checkout [the release notes](https://github.com/SharePoint/PnP-Tools/blob/master/Solutions/SharePoint.Modernization/Modernization%20Framework%20release%20notes.md) to stay up to date on the latest changes. If you encounter problems please file an issue in the [PnP Tools GitHub issue list](https://github.com/SharePoint/PnP-Tools/issues).
+> The SharePoint PnP Modernization framework is continuously evolving, checkout [the release notes](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization/Modernization%20Framework%20release%20notes.md) to stay up to date on the latest changes. If you encounter problems please file an issue in the [PnP Tools GitHub issue list](https://github.com/SharePoint/sp-dev-modernization/issues).
 
 The page transformation engine is built using .Net and is distributed as a [nuget](https://www.nuget.org/packages/SharePointPnPModernizationOnline) package. Once you've added the nuget package you'll see that 2 additional files are added to your solution:
 

docs/transform/modernize-userinterface-site-pages-model.md

@@ -10,7 +10,7 @@ ms.prod: sharepoint
 The heart of the page transformation solution is the model that feeds the transformation: the model tells the engine which web part properties are important, allows you to manipulate these properties and dynamically choose a mapping for your web part.The page transformation model is expressed in XMl and comes with a schema that's used to validate the correctness of the model.
 
 > [!IMPORTANT]
-> The SharePoint PnP Modernization framework is continuously evolving, checkout [the release notes](https://github.com/SharePoint/PnP-Tools/blob/master/Solutions/SharePoint.Modernization/Modernization%20Framework%20release%20notes.md) to stay up to date on the latest changes. If you encounter problems please file an issue in the [PnP Tools GitHub issue list](https://github.com/SharePoint/PnP-Tools/issues).
+> The SharePoint PnP Modernization framework is continuously evolving, checkout [the release notes](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization/Modernization%20Framework%20release%20notes.md) to stay up to date on the latest changes. If you encounter problems please file an issue in the [PnP Tools GitHub issue list](https://github.com/SharePoint/sp-dev-modernization/issues).
 
 ## Page transformation high level architecture
 

docs/transform/modernize-userinterface-site-pages-powershell.md

@@ -8,7 +8,7 @@ ms.prod: sharepoint
 # Transforming to modern site pages using PowerShell
 
 > [!IMPORTANT]
-> The SharePoint PnP Modernization framework is continuously evolving, checkout [the release notes](https://github.com/SharePoint/PnP-Tools/blob/master/Solutions/SharePoint.Modernization/Modernization%20Framework%20release%20notes.md) to stay up to date on the latest changes. If you encounter problems please file an issue in the [PnP Tools GitHub issue list](https://github.com/SharePoint/PnP-Tools/issues).
+> The SharePoint PnP Modernization framework is continuously evolving, checkout [the release notes](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization/Modernization%20Framework%20release%20notes.md) to stay up to date on the latest changes. If you encounter problems please file an issue in the [PnP Tools GitHub issue list](https://github.com/SharePoint/sp-dev-modernization/issues).
 
 The page transformation engine can also be used from PowerShell. This allows it to be integrated in a site modernization script that besides page transformation also does other things like installing solution, connecting the site to an Office 365 group and applying tenant branding. A good example of an all-up modernization script can be found [in the Office 365 Group connect article](modernize-connect-to-office365-group.md).