Skip to content

Commit e65b1b7

Browse files
authored
Update site-design-overview.md (SharePoint#7279)
- Removed image of the table I added (added image by accident) - Added note to JSON about channel sites
1 parent 387491e commit e65b1b7

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

docs/declarative-customization/site-design-overview.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -110,7 +110,7 @@ The following example is a script that has two top-level actions. First, it appl
110110

111111
Each action in a site script is specified by a **verb** value in the JSON. In the previous script, the first action is specified by the **applyTheme** verb. Next, the **createSPList** verb creates the list. Notice that the **createSPList** verb contains its own set of verbs that run additional actions on only the list.
112112

113-
Available actions include:
113+
**Available actions include:**
114114

115115
- Creating a new list or library (or modifying the default one created with the site)
116116
- Creating site columns, content types, and configuring other list settings
@@ -121,12 +121,13 @@ Available actions include:
121121
- Triggering a Power Automate flow
122122
- Installing a deployed solution from the app catalog
123123
- Setting regional settings for the site
124-
- Adding principals (users and groups) to SharePoint roles
125-
- Setting external sharing capability for the site
124+
- Adding principals (users and groups) to SharePoint roles**
125+
- Setting external sharing capability for the site**
126126

127127
For a complete list of available actions and their parameters, see the [JSON schema](site-design-json-schema.md).
128128

129129
> [!NOTE]
130+
> ** These actions are automatically blocked for channel sites
130131
> For libraries and lists, use the PowerShell command [Get-SPOSiteScriptFromList](/powershell/module/sharepoint-online/Get-SPOSiteScriptFromList) to create the site script syntax from an existing SharePoint list.
131132
132133
Site scripts can be run again on the same site after provisioning. Site scripts are non-destructive, so when they run again, they ensure that the site matches the configuration in the script.
@@ -229,11 +230,13 @@ RestRequest("/_api/Microsoft.SharePoint.Utilities.WebTemplateExtensions.SiteScri
229230

230231
In the previous example, the **Add-SPOSiteScript** cmdlet or **CreateSiteScript** REST API returns a site script ID. This is used for the **SiteScripts** parameter in the subsequent call to the **Add-SPOSiteDesign** cmdlet or **CreateSiteDesign** REST API.
231232

233+
232234
| Parameter | Value | Site template type |
233235
| :------------------- | :------------------- |:----------------|
234236
| WebTemplate | 64 | Team site template |
235237
| WebTemplate 1 | 64 | Team site (with group creation disabled) |
236-
| WebTemplate | 68 | Communication site template |![image](https://user-images.githubusercontent.com/55893502/130493853-b72bb035-eb03-4d9a-b5f2-87c38d942a11.png)
238+
| WebTemplate | 68 | Communication site template |
239+
237240

238241

239242
For step-by-step information about creating a site template, see [Get started creating site templates](get-started-create-site-design.md).

0 commit comments

Comments
 (0)