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
The SharePoint Framework (SPFx) is a page and web part model that provides full support for client-side SharePoint development, easy integration with SharePoint data, and support for open source tooling. With the SharePoint Framework, you can use modern web technologies and tools in your preferred development environment to build productive experiences and apps that are natively responsive and mobile-ready. The SharePoint Framework works for SharePoint Online and for on-premises (from SharePoint 2016 Feature Pack 2 forward). You can built client-side web parts and SharePoint Framework Extensions with the SharePoint Framework.
25
25
26
26
### Articles
27
-
*[Overview of the SharePoint Framework](https://docs.microsoft.com/sharepoint/dev/spfx/sharepoint-framework-overview)
28
-
*[Overview of SharePoint client-side web parts](https://docs.microsoft.com/sharepoint/dev/spfx/web-parts/overview-client-side-web-parts)
29
-
*[Overview of SharePoint Framework Extensions](https://docs.microsoft.com/sharepoint/dev/spfx/extensions/overview-extensions)
*[SharePoint Add-ins compared with SharePoint solutions](https://docs.microsoft.com/sharepoint/dev/general-development/sharepoint-add-ins-compared-with-sharepoint-solutions)
64
-
*[Transform farm solutions to the SharePoint Add-in model](https://docs.microsoft.com/sharepoint/dev/solution-guidance/transform-farm-solutions-to-the-sharepoint-app-model)
@@ -108,8 +108,8 @@ Farm Solutions are distributed as SharePoint solution packages that farm adminis
108
108
109
109
### Articles
110
110
111
-
*[Build farm solutions in SharePoint](https://docs.microsoft.com/sharepoint/dev/general-development/build-farm-solutions-in-sharepoint)
112
-
*[SharePoint Add-ins compared with SharePoint solutions](https://docs.microsoft.com/sharepoint/dev/general-development/sharepoint-add-ins-compared-with-sharepoint-solutions)
111
+
*[Build farm solutions in SharePoint](/sharepoint/dev/general-development/build-farm-solutions-in-sharepoint)
112
+
*[SharePoint Add-ins compared with SharePoint solutions](/sharepoint/dev/general-development/sharepoint-add-ins-compared-with-sharepoint-solutions)
113
113
114
114
## Script Editor or Content Editor web part
115
115
@@ -122,4 +122,4 @@ This however raises a security challenges as scripts can be deployed to SharePoi
122
122
Moreover any custom code hosted within the Script Editor web part does not have any kind of maintenance capability, governance, or life-cycle management. That's why starting from 2017 Microsoft introduced the [SharePoint Framework](#SharePointFramework) model, which is similar to the Script Editor web part, but works in the "modern" UI, supports the no-script flag and provides centralized governance and control for the SharePoint administrators.
123
123
124
124
### Articles
125
-
*[Migrate existing Script Editor web part customizations to the SharePoint Framework](https://docs.microsoft.com/sharepoint/dev/spfx/web-parts/guidance/migrate-script-editor-web-part-customizations)
125
+
*[Migrate existing Script Editor web part customizations to the SharePoint Framework](/sharepoint/dev/spfx/web-parts/guidance/migrate-script-editor-web-part-customizations)
0 commit comments