You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/solution-guidance/modern-experience-customizations.md
+20-30Lines changed: 20 additions & 30 deletions
Original file line number
Diff line number
Diff line change
@@ -17,6 +17,7 @@ Numerous benefits in the "modern" experiences are called out in the referenced m
17
17
## What are the "modern" experiences in SharePoint Online?
18
18
19
19
The "modern" experiences in SharePoint Online are:
20
+
20
21
-**Modern team sites**
21
22
-**Modern list and library experiences**
22
23
-**Modern site pages**
@@ -26,40 +27,32 @@ The "modern" experiences in SharePoint Online are:
26
27
If you have existing customizations that are business critical for your deployment, we recommend using the following process for adopting the "modern" experiences:
27
28
28
29
1.**Readiness**: Understand the "modern" experiences, know what features they offer, but equally important, understand which features are not (yet) available.
29
-
30
-
2.**Assess**: Assess to what extent your current customizations can work within the "modern" experience. Also assess which of your sites have customizations or features that will not work within the "modern" experiences. These sites and their customizations should be updated or need to stay in "classic". However, other sites should work just fine using the "modern" experiences. The best way to assess your compatibility with the "modern" experiences is by using the [SharePoint Modernization scanner](https://aka.ms/sppnp-modernuiscanner).
31
-
32
-
3.**Solution planning**: Plan the work required for both custom solutions and sites to prepare them to be used with the "modern" experiences.
33
-
34
-
4.**Develop and test**: Apply the needed changes to your customizations and test them.
35
-
36
-
5.**Deploy**: Roll out the updated changes to your SharePoint Online environment.
30
+
1.**Assess**: Assess to what extent your current customizations can work within the "modern" experience. Also assess which of your sites have customizations or features that will not work within the "modern" experiences. These sites and their customizations should be updated or need to stay in "classic". However, other sites should work just fine using the "modern" experiences. The best way to assess your compatibility with the "modern" experiences is by using the [SharePoint Modernization scanner](https://aka.ms/sppnp-modernuiscanner).
31
+
1.**Solution planning**: Plan the work required for both custom solutions and sites to prepare them to be used with the "modern" experiences.
32
+
1.**Develop and test**: Apply the needed changes to your customizations and test them.
33
+
1.**Deploy**: Roll out the updated changes to your SharePoint Online environment.
37
34
38
35
Following are the key scenarios currently supported by the "modern" experiences. We will be updating the list of supported scenarios whenever new capabilities are introduced in SharePoint Online.
39
36
40
-
<br/>
41
-
42
-
|Customization/Article|Description|
43
-
|:-----|:-----|
44
-
|[Provisioning "modern" team sites programmatically](modern-experience-customizations-provisioning-sites.md)| "Modern" team sites can be provisioned by an end user, but you can also create these sites programmatically. |
45
-
|[Customizing "modern" team sites](modern-experience-customizations-customize-sites.md)| "Modern" team sites are sites that bring a fresh, new responsive user experience to SharePoint Online,<br/>showing relevant information on the home page. Typically, these sites also have an associated Microsoft 365 group. |
46
-
|[Customizing "modern" lists and libraries](modern-experience-customizations-customize-lists-and-libraries.md)| "Modern" lists and document libraries bring a better user experience that is faster, more intuitive, and responsive.<br/>This article focuses on the extensibility options, such as user custom actions and branding, which are supported for the "modern" library and list experiences. |
47
-
|[Customizing "modern" site pages](modern-experience-customizations-customize-pages.md)| "Modern" team site pages are fast, easy to author, and support rich multimedia content. Additionally, these pages<br/>look great on any device, in a browser, or from within the SharePoint mobile app.<br/>This article focuses on the extensibility options available within the "modern" page experience. |
48
-
|[SharePoint "modern" sites classification](modern-experience-site-classification.md)|Configure out-of-the-box site classification for modern SharePoint sites. |
|[Provisioning "modern" team sites programmatically](modern-experience-customizations-provisioning-sites.md)| "Modern" team sites can be provisioned by an end user, but you can also create these sites programmatically. |
40
+
|[Customizing "modern" team sites](modern-experience-customizations-customize-sites.md)| "Modern" team sites are sites that bring a fresh, new responsive user experience to SharePoint Online, showing relevant information on the home page. Typically, these sites also have an associated Microsoft 365 group. |
41
+
|[Customizing "modern" lists and libraries](modern-experience-customizations-customize-lists-and-libraries.md)| "Modern" lists and document libraries bring a better user experience that is faster, more intuitive, and responsive. This article focuses on the extensibility options, such as user custom actions and branding, which are supported for the "modern" library and list experiences. |
42
+
|[Customizing "modern" site pages](modern-experience-customizations-customize-pages.md)| "Modern" team site pages are fast, easy to author, and support rich multimedia content. Additionally, these pages look great on any device, in a browser, or from within the SharePoint mobile app. This article focuses on the extensibility options available within the "modern" page experience. |
43
+
|[SharePoint "modern" sites classification](modern-experience-site-classification.md)| Configure out-of-the-box site classification for modern SharePoint sites. |
51
44
52
45
## Converting existing sites to "modern" team sites
53
46
54
47
Existing collaboration sites cannot be converted to "modern" team sites with an associated Microsoft 365 group, but you can however [associate a new Microsoft 365 group](/sharepoint/dev/transform/modernize-connect-to-office365-group) to existing collaboration site. You can also start using modern page and list experiences in the classic sites, which will make them look like a modern group associated team sites.
55
48
56
49
"Modern" lists and library usage can be controlled at site, web, and list/library level. You can find more details about the available options in our ["modern" list and libraries](modern-experience-customizations-customize-lists-and-libraries.md) article.
57
50
58
-
By default, "classic" SharePoint sites use modern pages for any newly added page, and you have the option to change the welcome page to a modern page. Setting a new "modern" page for a "classic" SharePoint site can be done programatically by using CSOM or REST APIs.
51
+
By default, "classic" SharePoint sites use modern pages for any newly added page, and you have the option to change the welcome page to a modern page. Setting a new "modern" page for a "classic" SharePoint site can be done programmatically by using CSOM or REST APIs.
59
52
60
53
## Using modern experiences in the root site collection of a tenant
61
54
62
-
Since 2019, tenants have intially been provided a modern communication site as the root site. If your environment was set up before April 2019, consider swapping in a communication site or a modern team site that isn't connected to a group. If you'd rather stay with the classic site, you can use modern experiences in other ways, such as creating content using modern pages. See https://learn.microsoft.com/en-us/SharePoint/modern-root-site for full details.
55
+
Since 2019, tenants have initially been provided a modern communication site as the root site. If your environment was set up before April 2019, consider swapping in a communication site or a modern team site that isn't connected to a group. If you'd rather stay with the classic site, you can use modern experiences in other ways, such as creating content using modern pages. For more information, see [Modernize your root site](/SharePoint/modern-root-site).
63
56
64
57
> [!CAUTION]
65
58
> It is not supported to delete the existing site collection from the root URL of your tenant. You should not in any circumstances delete the root site collection. Technically this can be performed using APIs, but that can cause the tenant to move into an inconsistent status.
## SharePoint "modern" experiences support for on-premises
87
78
88
79
The SharePoint "modern" experiences are supported in SharePoint 2019 in on-premises. Also as part of the SharePoint 2016 Feature Pack, "modern" experiences will be introduced within the OneDrive for Business experience, and you can take advantage of the SharePoint Framework client-side web parts in the classic page experience.
89
80
90
-
91
81
## See also
92
82
93
-
-[Create connected SharePoint Online team sites in seconds](https://blogs.office.com/2016/11/08/create-connected-sharepoint-online-team-sites-in-seconds/)
94
-
-[New capabilities in SharePoint Online team sites including integration with Microsoft 365 groups](https://www.microsoft.com/microsoft-365/blog/2016/08/31/new-capabilities-in-sharepoint-online-team-sites-including-integration-with-office-365-groups)
83
+
-[Create connected SharePoint Online team sites in seconds](https://blogs.office.com/2016/11/08/create-connected-sharepoint-online-team-sites-in-seconds/)
84
+
-[Microsoft Teams, SharePoint, and Microsoft 365 Groups integration (IT Admins)](/microsoft-365/solutions/groups-sharepoint-teams-governance)
95
85
-[Create a team site in SharePoint Online](https://support.office.com/article/Create-a-team-site-in-SharePoint-Online-ef10c1e7-15f3-42a3-98aa-b5972711777d)
96
-
-[Turn scripting capabilities on or off](https://support.office.com/article/Allow-or-prevent-custom-script-1f2c515f-5d7e-448a-9fd7-835da935584f)
97
-
-["Modern" SharePoint lists are here - including integration with Microsoft Flow and PowerApps](https://blogs.office.com/2016/07/25/modern-sharepoint-lists-are-here-including-integration-with-microsoft-flow-and-powerapps/)
98
-
-[Update on "Modern" Document Libraries and Extensibility](https://developer.microsoft.com/office/blogs/update-on-modern-document-libraries-and-extensiblity)
99
-
-[Switch the default experience for lists or document libraries from "modern" or "classic"](https://support.office.com/article/Switch-the-default-experience-for-lists-or-document-libraries-from-new-or-classic-66dac24b-4177-4775-bf50-3d267318caa9)
86
+
-[Turn scripting capabilities on or off](https://support.office.com/article/Allow-or-prevent-custom-script-1f2c515f-5d7e-448a-9fd7-835da935584f)
87
+
-["Modern" SharePoint lists are here - including integration with Microsoft Flow and PowerApps](https://blogs.office.com/2016/07/25/modern-sharepoint-lists-are-here-including-integration-with-microsoft-flow-and-powerapps/)
88
+
-[Update on "Modern" Document Libraries and Extensibility](https://developer.microsoft.com/office/blogs/update-on-modern-document-libraries-and-extensiblity)
89
+
-[Switch the default experience for lists or document libraries from "modern" or "classic"](https://support.office.com/article/Switch-the-default-experience-for-lists-or-document-libraries-from-new-or-classic-66dac24b-4177-4775-bf50-3d267318caa9)
100
90
-[Office 365 development and SharePoint PnP solution guidance](office-365-development-patterns-and-practices-solution-guidance.md)
0 commit comments