Skip to content

Commit 66d91e3

Browse files
skaggejVesaJuvonen
authored andcommitted
Updated to address issue SharePoint#1057 (SharePoint#3529)
Added note about not being able to update navigation elements programmatically.
1 parent e15d856 commit 66d91e3

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

docs/solution-guidance/modern-experience-customizations-customize-sites.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -58,6 +58,7 @@ In numerous areas on the "modern" team sites, the typical customizations are not
5858
- "Classic" publishing features (WCM).
5959
- Activation of community feature or creation of community subsites under "modern" team site.
6060
- Saving site as a template. Also not supported for sub sites in site collections which root site is a group associated team site or communication site.
61+
- Programmatically updating navigation elements.
6162

6263
Because "modern" team sites also have scripting capabilities disabled (it's a so called NoScript site), numerous areas cannot be customized. The impact of NoScript is the same for "modern" or "classic" sites. "Modern" sites have NoScript enabled by default, meaning that scripting capabilities are not available. However, it is possible and supported to disable NoScript settings in both "modern" and "classic" sites to further enable some capabilities.
6364

0 commit comments

Comments
 (0)