@@ -13,6 +13,7 @@ First release of the SharePoint Framework contained only support for client-side
13
13
- [ On-premises support for SharePoint 2016 (Feature Pack 2)] ( ./sharepoint-2016-support.md )
14
14
- [ SharePoint Framework Extensions] ( ./extensions/overview-extensions.md )
15
15
- [ Tenant properties] ( ./tenant-properties.md )
16
+ - [ ALM APIs for SPFx solutions and add-ins] ( ../apis/alm-api-for-spfx-add-ins.md )
16
17
17
18
18
19
> [ !NOTE]
@@ -45,12 +46,9 @@ First release of the SharePoint Framework contained only support for client-side
45
46
- Tenant admin gets automatically notified
46
47
- Settings to control the default experience around approval process
47
48
48
- - ALM REST APIs - Deploy, activate, delete and upgrade apps and add-ins
49
- - ALM REST APIs targeted to support * everything* in the App Catalog, including add-ins
50
49
- Automatic CDN hosting for code
51
50
- Package JavaScript bundle into app package, which is automatically then deployed to a library that gets hosted on your tenant Office 365 CDN
52
51
53
-
54
52
## Developer Experience
55
53
- SharePoint Framework Workbench 2.0: Development story for SharePoint Framework Extensions
56
54
- Tool Chain Components
@@ -60,6 +58,12 @@ First release of the SharePoint Framework contained only support for client-side
60
58
61
59
Following chapters are listing older items in the roadmap page, which have been already shipped.
62
60
61
+ ### ALM REST APIs
62
+
63
+ - ALM REST APIs - Deploy, activate, delete and upgrade apps and add-ins
64
+ - ALM REST APIs targeted to support * everything* in the App Catalog, including add-ins
65
+ - CSOM and PowerShell cmdlets released as an open source community initiate
66
+
63
67
### JavaScript embedding support (JSLink, User Custom Actions)
64
68
65
69
- The same tool chain and deployment model as client-side web parts
0 commit comments