Skip to content

Commit f2da96f

Browse files
authored
Updates to Features section (SharePoint#1706)
* Refresh of Features > API * Refresh of Features > API Take 3 * Edit of Site-theming section * Edited Site theming and related topics * Updated Features section of TOC * Edited new Groupify section * Edit pass * Fixes * Minor edits
1 parent 0b1e72e commit f2da96f

20 files changed

+392
-251
lines changed

docs/apis/alm-api-for-spfx-add-ins.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ ALM APIs are natively provided by using REST APIs, but there are additional CSOM
2929
## REST API
3030

3131
> [!TIP]
32-
> ALM APIs are also supported for the [site collection app catalog](../general-development/site-collection-app-catalog.md). URLs for the site collection app catalog operations are exactly the same, but you can change the `tenantappcatalog` as `sitecollectionappcatalog`. Notice also that you will need to enable site collection app catalog in your site collection or you will get an exception when trying to use these APIs.
32+
> ALM APIs are also supported for the [site collection app catalog](../general-development/site-collection-app-catalog.md). URLs for the site collection app catalog operations are exactly the same, but you can change the `tenantappcatalog` to `sitecollectionappcatalog`. Notice also that you will need to enable the site collection app catalog in your site collection or you will get an exception when trying to use these APIs.
3333
3434
### Add solution package to the app catalog
3535

@@ -161,7 +161,7 @@ By using [PnP PowerShell](https://docs.microsoft.com/en-us/powershell/sharepoint
161161
### Add and publish your app to the app catalog
162162
Adding your app (.sppkg file, .app file) to the app catalog is a prerequisite to making your app available for use on your SharePoint sites. You can do this by using the following cmdlet:
163163

164-
```PowerShell
164+
```powershell
165165
Add-PnPApp -Path ./myapp.sppkg -Scope Tenant
166166
```
167167

@@ -226,6 +226,7 @@ Get-PnPApp -Scope Tenant
226226
Using the [Office 365 CLI](https://sharepoint.github.io/office365-cli?utm_source=msft_docs&utm_medium=page&utm_campaign=Application+Lifecycle+Management+ALM+APIs), you can automate deploying, publishing, installing, upgrading, and retracting your apps. The Office 365 CLI is a cross-platform command-line interface that can be used on any platform, including Windows, MacOS, and Linux. To learn more about these commands, see the following sections.
227227

228228
### Add and publish your app to the app catalog
229+
229230
Adding your app (.sppkg file, .app file) to the tenant app catalog is a prerequisite to making your app available for use on your SharePoint sites. Use the [add](https://sharepoint.github.io/office365-cli/cmd/spo/app/app-add/?utm_source=msft_docs&utm_medium=page&utm_campaign=Application+Lifecycle+Management+ALM+APIs) command to do this:
230231

231232
```shell
@@ -245,6 +246,7 @@ spo app deploy --id <app id> --skipFeatureDeployment
245246

246247

247248
### Remove the app from the app catalog
249+
248250
You may want to remove an app that you added earlier, and you can do this by using the [remove](https://sharepoint.github.io/office365-cli/cmd/spo/app/app-remove/?utm_source=msft_docs&utm_medium=page&utm_campaign=Application+Lifecycle+Management+ALM+APIs) command:
249251

250252
```shell
@@ -253,6 +255,7 @@ spo app remove --id <app id>
253255

254256

255257
### Use apps on your site
258+
256259
After the app is added to the app catalog and published, you can install the app to your site by using the [install](https://sharepoint.github.io/office365-cli/cmd/spo/app/app-install/?utm_source=msft_docs&utm_medium=page&utm_campaign=Application+Lifecycle+Management+ALM+APIs) command:
257260

258261
```shell

docs/apis/communication-site-creation-rest.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Create SharePoint Communication site using REST
33
description: Create and get the status of a new modern SharePoint Communication site by using the REST interface.
4-
ms.date: 02/08/2018
4+
ms.date: 4/19/2018
55
ms.prod: sharepoint
66
---
77

@@ -26,7 +26,7 @@ The URL for Communication site REST commands is based on `_api/sitepages/communi
2626

2727
## Create Communication site
2828

29-
```
29+
```json
3030
url: /_api/sitepages/communicationsite/create
3131
method: POST
3232
body:
@@ -59,7 +59,7 @@ New in this API is the concept of `SiteDesignID`. Much like the in-product site
5959

6060
If successful, this method returns a `200, OK` response code and simple JSON object in the response body with the following details.
6161

62-
```
62+
```json
6363
{
6464
"d":{
6565
"Create":{
@@ -76,7 +76,7 @@ If successful, this method returns a `200, OK` response code and simple JSON obj
7676

7777
The REST API for getting the status of a modern SharePoint Communication site:
7878

79-
```
79+
```json
8080
url: /_api/sitepages/communicationsite/status?url='https%3A%2F%2Fcontoso.sharepoint.com%2Fsites%2Fcomm1'
8181
method: GET
8282
body: none
@@ -88,7 +88,7 @@ If successful, this method returns a `200, OK` response code and simple JSON obj
8888

8989
If the site exists, the response returns the site status and site URL:
9090

91-
```
91+
```json
9292
{
9393
"d":{
9494
"Status":{
@@ -100,9 +100,11 @@ If the site exists, the response returns the site status and site URL:
100100
}
101101
```
102102

103+
<br/>
104+
103105
If the site does not exist, the response returns a site status of 0 with no URL.
104106

105-
```
107+
```json
106108
{
107109
"d":{
108110
"Status":{

0 commit comments

Comments
 (0)