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/spfx/roadmap.md
+11-13Lines changed: 11 additions & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -6,15 +6,19 @@ First release of the SharePoint Framework will contain support for client-side w
6
6
7
7
## On-premises support
8
8
9
-
- Shipping as part of Feature Pack
9
+
- Shipping as part of Feature Pack 2 for SharePoint 2016
10
10
- Similar feature capabilities as in SharePoint Online
11
11
- Target is to provide common development platform across on-premises and the cloud
12
-
- Leveraging modern toolchain and open source on “legacy” environments
12
+
- Leveraging modern toolchain and open source on on-premises environments
13
13
- Targeting SharePoint 2016 version during calendar year 2017
14
14
15
+
## General improvements
16
+
17
+
- Easy access to Graph API to access user specific information (GraphHttpClient in dev preview)
18
+
- Site collection app catalog with tenant level control for enabling easier solution deployed
19
+
15
20
## Client-side web parts++ and add-ins
16
21
17
-
- Easy access to Graph API to access user specific information
18
22
- Supporting more complex scenarios and interactions with web parts
19
23
- Part-to-part communication
20
24
- JS Framework isolation
@@ -27,15 +31,14 @@ First release of the SharePoint Framework will contain support for client-side w
27
31
28
32
## JavaScript embedding support (JSLink, User Custom Actions)
29
33
30
-
- The same tool chain and deployment model as clientside web parts.
34
+
- The same tool chain and deployment model as client-side web parts
31
35
- Derive from a strongly typed base class wherever possible rather than manipulating the page DOM directly.
32
-
-Replacing custom actions and JSLinks with SharePoint Framework-based extensions
36
+
-Enable modern extension usage with modern experiences similar as Custom Actions and JS Link in classic experience
33
37
- Work with NoScript via tenant app catalog
34
-
- Work in site collection app catalog
35
-
- PnP community driven migration best practices and tools
36
38
39
+
> This is now available in [developer preview](https://dev.office.com/blogs/announcing-availability-of-sharepoint-framework-extensions-developer-preview).
37
40
38
-
## Application Lifecyle Management
41
+
## Application Lifecycle Management
39
42
40
43
- Streamlined approval experience: no need to know who your tenant admin is anymore
41
44
- Owner initiate the approval process
@@ -53,11 +56,6 @@ First release of the SharePoint Framework will contain support for client-side w
53
56
- Tool Chain Components
54
57
- Additional Yeoman Templates
55
58
56
-
## Full Page Apps
57
-
- Build SharePoint Framework apps, which render in full page mode, rather than as a client-side web part
Copy file name to clipboardExpand all lines: docs/spfx/sharepoint-framework-overview.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ The SharePoint Framework (SPFx) is a page and web part model that provides full
4
4
5
5
Key features of the SharePoint Framework include:
6
6
7
-
* Runs in the context of the current user and connection in the browser. There are no iFrames (no iFrames only in client-side JavaScript injection model).
7
+
* Runs in the context of the current user and connection in the browser. There are no iFrames for the customization (JavaScript is embedded directly to the page).
8
8
* The controls are rendered in the normal page DOM.
9
9
* The controls are responsive and accessible by nature.
10
10
* Enables the developer to access the lifecycle - including, in addition to **render** - **load**, **serialize** and **deserialize**, **configuration changes**, and more.
0 commit comments