article optimization

Author: jansenbe

docs/transform/modernize-connect-to-office365-group-scanner.md

@@ -45,27 +45,27 @@ With that filter applied let's have a look at the typical warnings:
 ![Office 365 Group connection warnings](media/modernize/groupifyscanner_ready_5.png)
 
 - **SiteHasSubSites**: A group is connected to the root site of the site collection and not to individual sub sites. In the modern team and communication sites, the use of subsites is de-emphasized but having sub sites is fully supported. Important to understand is that you can't use group connected services on your sub sites.
-- **ModernUIIssues**: Since connecting to a group brings a modern home page this might result in existing customizations being "ignored" on that modern home page. The details of which modern UI issues were found by the scanner can be found in the next section. You can optionally stick with your "current" home page if you run Office 365 Group connection using the API's or using the "bulk Office 365 Group connection" scripts.
-- **DefaultHomePageImpacted**: The default home page based upon this site's web template differs a lot from the new home page you get by connecting to a group. You can optionally stick with your "current" home page if you run Office 365 Group connection using the API's or using the "bulk Office 365 Group connection" scripts. Another alternative is creating a new modern home page, as is shown in the "bulk Office 365 Group connection" script.
+- **ModernUIIssues**: Since connecting to a group brings a modern home page this might result in existing customizations being "ignored" on that modern home page. The details of which modern UI issues were found by the scanner can be found in the next section. You can optionally stick with your "current" home page if you run Office 365 Group connection using the API's or using the "Bulk Office 365 Group connection" scripts.
+- **DefaultHomePageImpacted**: The default home page based upon this site's web template differs a lot from the new home page you get by connecting to a group. You can optionally stick with your "current" home page if you run Office 365 Group connection using the API's or using the "bulk Office 365 Group connection" scripts. Another alternative is creating a new modern home page, as is shown in the "Bulk Office 365 Group connection" script.
 - **ADGroupWillNotBeExpanded**: When you group-connect via the user interface, you have an option to define the Office 365 group's owners and members; when you bulk group-connect, the sample script explained later does the same. However, because an Office 365 group can only contain persons as Owners or Members, this means that if today you granted access to your SharePoint site by using an Azure Active Directory (Azure AD) security group, you can't add that Azure AD security group as an Office 365 group owner or member. If you want to only rely on the permissions defined on the Office 365 group, you must add all individual Azure AD group members as part of the group-connection process, but having identical access defined on both the SharePoint site and the Office 365 group is not needed, making this not a blocking issue.
 
 ### Modern UI Warnings
 
 ![Detailed modern UI warnings](media/modernize/groupifyscanner_ready_6.png)
 
-- **MasterPageUsed** or **AlternateCSSUsed**: Custom master pages or alternate CSS is not used on modern pages. If your site depends on these, you might want to verify that, because your custom master pages and CSS will not work on the modern home page that the site gets. Checkout the [Modernize branding](modernize-branding.md) article to learn more.
+- **MasterPageUsed** or **AlternateCSSUsed**: Custom master pages or alternate CSS is not used on modern pages. If your site depends on these, you might want to verify that, because your custom master pages and CSS will not work on the modern home page that the site gets. Checkout the [Modernize branding](modernize-branding.md) article to learn more on the possible remediation steps.
 - **UserCustomActionUsed**: Using user custom actions that embed JavaScript is common for customizing sites, but this does not work for modern pages. If you have user custom actions, you can build alternatives by using SharePoint Framework Extensions and install those to your site. See the ModernizationUserCustomActionScanResults.csv and checkout the [Modernize customizations](modernize-customizations.md) article for more details.
-- **PublishingFeatureEnabled**: The publishing features are not compatible with the modern page feature, which is a requirement due to the modern home page being set.
-- **ModernPageFeatureDisabled**: Because the site gets a modern home page after group-connection creation, it's important that the modern homepage feature is enabled.
-- **ModernListsBlockedAtSiteLevel** or **ModernListsBlockedAtWebLevel**: Preventing the modern user interface for lists and libraries is not blocking group-connection, but because group-connection is typically part of a site modernization, it makes no sense to prevent lists and libraries to use the modern user interface on an Office 365 group-connected site.
+- **PublishingFeatureEnabled**: The publishing features are not compatible with the modern page feature, which is a requirement due to the modern home page being set. If the publishing capabilities are not used on your site then you can disable them.
+- **ModernPageFeatureDisabled**: Because the site gets a modern home page after group-connection creation, it's important that the modern homepage feature is enabled. Use the remediation steps outlined in [Transform classic pages to modern client-side pages](modernize-userinterface-site-pages.md) to fix this.
+- **ModernListsBlockedAtSiteLevel** or **ModernListsBlockedAtWebLevel**: Preventing the modern user interface for lists and libraries is not blocking group-connection, but because group-connection is typically part of a site modernization, it makes no sense to prevent lists and libraries to use the modern user interface on an Office 365 group-connected site. Use the remediation steps outlined in [Maximize use of modern lists and libraries](modernize-userinterface-lists-and-libraries.md) to fix this.
 
 ### Permission Warnings
 
 ![Permission warnings](media/modernize/groupifyscanner_ready_7.png)
 
 - **SharingDisabledForSiteButGroupWillAllowExternalSharing**: The default configuration for Office 365 group-connected sites is to allow sharing with externals, but you might have disabled sharing with externals for your site. It's recommended to sync the SharePoint site external sharing settings with the settings of the connected Office 365 group.
+- **PrivateGroupButEveryoneUsedOutsideOfAdminOwnerMemberGroups**: The scanner proposes to create the group either as private or public, and it does this based on the existence of the everyone claims inside the SharePoint site's administrators, owners, or members groups. However, you may have used the everyone claims outside of these groups, which is indicated by this warning. Typically this is fine, use this warning to evaluate whether you want to change a group from private to public.
 - **SubSiteWithBrokenPermissionInheritance**: If you have subsites with unique permissions, these do not inherit the permissions defined on the connected Office 365 group. Since Office 365 services that come via the group do not apply to sub sites this typically is not an issue.
-- **PrivateGroupButEveryoneUsedOutsideOfAdminOwnerMemberGroups**: The scanner proposes to create the group either as private or public, and it does this based on the existence of the everyone claims inside the SharePoint site's administrators, owners, or members groups. However, you may have used the everyone claims outside of these groups, which is indicated by this warning.
 
 ## Understand which sites are not ready for Office 365 Group connection
 
@@ -87,6 +87,6 @@ With that filter applied let's have a look at why a site is not ready.
 
 ![Group connection blockers](media/modernize/groupifyscanner_notready_5.png)
 
-- **PublishingFeatureEnabled**: Sites that have publishing enabled do not support modern pages and by default connecting to a group will result in switching the site home page to a modern page.
+- **PublishingFeatureEnabled**: Sites that have publishing enabled do not support modern pages and by default connecting to a group will result in switching the site home page to a modern page. If the publishing capabilities are not used on your site then you can disable them.
 - **SiteHasOffice365Group**: This site already has an Office 365 group connected and a site can only by connected to one Office 365 group.
 - **IncompatibleWebTemplate**: The used web template is not supported to be connected.

docs/transform/modernize-userinterface-lists-and-libraries.md

@@ -61,6 +61,26 @@ Certain field types (BCS external data, Geolocation, OutcomeChoice in edit mode,
 
 Classic list view and edit pages are editable by users, so you could, for example, add additional web parts on a list view page. If you've done that, the list no longer shows in modern. To remediate this, the only approach you can take is to drop the added web parts from the list pages.
 
+### Modern and library user interface blocking at site or web level
+
+The modern list and library user interface can be blocked for a complete site collection (site level) or for one or more sites (web level). Remediating this can be done by disabling the respective site or web scoped features as shown in below PnP PowerShell snippet:
+
+```PowerShell
+$minimumVersion = New-Object System.Version("2.24.1803.0")
+if (-not (Get-InstalledModule -Name SharePointPnPPowerShellOnline -MinimumVersion $minimumVersion -ErrorAction Ignore))
+{
+    Install-Module SharePointPnPPowerShellOnline -MinimumVersion $minimumVersion -Scope CurrentUser
+}
+Import-Module SharePointPnPPowerShellOnline -DisableNameChecking -MinimumVersion $minimumVersion
+
+Connect-PnPOnline -Url "<your site url>"
+
+# Disable the modern list site level blocking feature
+Disable-PnPFeature -Identity "E3540C7D-6BEA-403C-A224-1A12EAFEE4C4" -Scope Site -Force
+# Disable the modern list web level blocking feature
+Disable-PnPFeature -Identity "52E14B6F-B1BB-4969-B89B-C4FAA56745EF" -Scope Web -Force
+```
+
 ## See also
 
 - [Modernize the user interface](modernize-userinterface.md)

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

@@ -14,6 +14,24 @@ The SharePoint PnP Modernization framework ([Nuget](https://www.nuget.org/packag
 > [!IMPORTANT]
 > The SharePoint PnP Modernization framework is currently in preview. If you encounter problems please file an issue in the [PnP Tools GitHub issue list](https://github.com/SharePoint/PnP-Tools/issues).
 
+## Before you start
+
+By default the modern site page capability is enabled on most sites but maybe it was turned off afterwards. If that's the case either the [SharePoint "Modern" user interface experience scanner](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.UIExperience.Scanner) or the [SharePoint Modernization scanner](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.Modernization) will tell you which sites have turned of the modern page feature. To remediate this use below sample PnP PowerShell script:
+
+```PowerShell
+$minimumVersion = New-Object System.Version("2.24.1803.0")
+if (-not (Get-InstalledModule -Name SharePointPnPPowerShellOnline -MinimumVersion $minimumVersion -ErrorAction Ignore))
+{
+    Install-Module SharePointPnPPowerShellOnline -MinimumVersion $minimumVersion -Scope CurrentUser
+}
+Import-Module SharePointPnPPowerShellOnline -DisableNameChecking -MinimumVersion $minimumVersion
+
+Connect-PnPOnline -Url "<your web url>"
+
+# Enable modern page feature
+Enable-PnPFeature -Identity "B6917CB1-93A0-4B97-A84D-7CF49975D4EC" -Scope Web -Force
+```
+
 ## Overview of the page transformation solution
 
 Below picture explains the page transformation in 4 steps:

docs/transform/modernize-userinterface.md

@@ -65,14 +65,14 @@ After you analyze the sites that you want to modernize, you can continue with th
 
 - Modernize your user experience by:
 
-  - **Enabling lists and libraries to show in the modern user interface** by replacing customizations, removing incompatible columns from the used views, or (as a last resort) moving data into a modern user interface-compatible list type.
-  - **Connecting your site to an Office 365 group**, which gives your site a modern home page and enables your site to use, for example, a mailbox or Microsoft Planner, which then enables you to use a modern version of a calendar and task list.
-  - **Creating modern client-side pages** and configuring these to be "similar" to your key classic wiki and web part pages. Programmatic page transformation should be done for the key pages of your sites; transforming all pages is resource-intensive and often not needed. To assist in this triage, the SharePoint Modernization scanner can give you usage information about the current wiki and web part pages.
+  - **[Enabling lists and libraries to show in the modern user interface](modernize-userinterface-lists-and-libraries.md)** by replacing customizations, removing incompatible columns from the used views, or (as a last resort) moving data into a modern user interface-compatible list type.
+  - **[Connecting your site to an Office 365 group](modernize-connect-to-office365-group.md)**, which gives your site a modern home page and enables your site to use, for example, a mailbox or Microsoft Planner, which then enables you to use a modern version of a calendar and task list.
+  - **[Creating modern client-side pages](modernize-classic-sites.md)** and configuring these to be "similar" to your key classic wiki and web part pages. Programmatic page transformation should be done for the key pages of your sites; transforming all pages is resource-intensive and often not needed. To assist in this triage, the SharePoint Modernization scanner can give you usage information about the current wiki and web part pages.
 
 - **Communicate to your end users about the completed changes**; the site will work differently in a modern version, so your users need to be aware of that.
 
 ## See also
 
-- [Maximize use of modern lists and libraries](modernize-userinterface-lists-and-libraries.md)
 - [Modernize your classic SharePoint sites](modernize-classic-sites.md)
+- [Maximize use of modern lists and libraries](modernize-userinterface-lists-and-libraries.md)
 - [Transform classic pages to modern client-side pages](modernize-userinterface-site-pages.md)