From 11beb13db0023b4ecd035bd2815a22e5871095ac Mon Sep 17 00:00:00 2001 From: Ashlesha-MSFT Date: Mon, 22 Jun 2026 18:01:52 +0530 Subject: [PATCH 1/9] Remove 'See Also' section from SPFx documentation Removed the 'See Also' section from the document. --- docs/spfx/sharepoint-framework-why.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/docs/spfx/sharepoint-framework-why.md b/docs/spfx/sharepoint-framework-why.md index 1091228468..ee9d04cf94 100644 --- a/docs/spfx/sharepoint-framework-why.md +++ b/docs/spfx/sharepoint-framework-why.md @@ -37,7 +37,3 @@ Historically, developers created web parts as full trust C# assemblies that were However, current development models usually involve JavaScript running in a browser making REST API calls to the SharePoint and Microsoft 365 back-end workloads. C# assemblies don’t work in this world. Developers needed a new development model. The SharePoint Framework is the next evolution in SharePoint development. - -## See Also - -- [Why did Microsoft create the SharePoint Framework (SPFx)?](https://www.voitanos.io/blog/spfx-5w1h-why-did-microsoft-create-sharepoint-framework/) From 3f9c0adb337b43cbb829c7d794e7bdecf1b3ba60 Mon Sep 17 00:00:00 2001 From: Ashlesha-MSFT Date: Mon, 22 Jun 2026 18:03:12 +0530 Subject: [PATCH 2/9] Clean up SASS links in configure-sass.md Removed duplicate links for SASS updates in SPFx documentation. --- docs/spfx/toolchain/configure-sass.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/spfx/toolchain/configure-sass.md b/docs/spfx/toolchain/configure-sass.md index 60957c01f6..7535295a2b 100644 --- a/docs/spfx/toolchain/configure-sass.md +++ b/docs/spfx/toolchain/configure-sass.md @@ -66,5 +66,4 @@ Refer to the Heft Sass plugin documentation for more information how to configur - [SharePoint Framework v1.16.1 release notes](../release-1.16.1.md) - [Heft-based toolchain (SPFx v1.22.0+)](sharepoint-framework-toolchain-rushstack-heft.md) - [Gulp-based toolchain (legacy)](sharepoint-framework-toolchain.md) -- [Stefan Bauer: What’s new with SASS in SPFx v1.16.0](https://n8d.at/whats-new-with-sass-in-spfx-1-16-0)\ -- [Andrew Connell: Unboxing the SharePoint Framework (SPFx) v1.16.1 release](https://www.voitanos.io/blog/sharepoint-framework-v1-16-1-whats-in-latest-update-of-spfx/) +- [Stefan Bauer: What’s new with SASS in SPFx v1.16.0](https://n8d.at/whats-new-with-sass-in-spfx-1-16-0) From 8cc96a535282dfae98d3b92b905a9dc129a881a9 Mon Sep 17 00:00:00 2001 From: Ashlesha-MSFT Date: Mon, 22 Jun 2026 18:05:09 +0530 Subject: [PATCH 3/9] Update documentation on SPFx environment variable usage Removed link to external resource for setting environment variable. --- docs/spfx/set-up-your-development-environment.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/spfx/set-up-your-development-environment.md b/docs/spfx/set-up-your-development-environment.md index f053a5f8e8..fed381d855 100644 --- a/docs/spfx/set-up-your-development-environment.md +++ b/docs/spfx/set-up-your-development-environment.md @@ -140,7 +140,6 @@ The SPFx build toolchain will replace this value on the fly with a value defined Developers can use the `SPFX_SERVE_TENANT_DOMAIN` OS environment variable to specify the tenant domain (or site URL) for serve configurations across different SPFx solutions. If a URL in the serve configuration (for example, `pageUrl` for Field Customizer) contains the `{tenantDomain}` placeholder, it will be automatically replaced with the variable's value. -For more information on how to set the environment variable on your developer environment, including Windows or macOS, see [Setting the SharePoint Framework Hosted Workbench Test Site](https://www.voitanos.io/blog/set-spfx-hosted-workbench-test-site/). ## Optional tools From 7bebb6f14edc564f57a28132bbbc4262182501a3 Mon Sep 17 00:00:00 2001 From: Ashlesha-MSFT Date: Mon, 22 Jun 2026 18:06:41 +0530 Subject: [PATCH 4/9] Update development environment documentation Removed external link for node version managers and adjusted formatting. --- docs/spfx/set-up-your-development-environment.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/spfx/set-up-your-development-environment.md b/docs/spfx/set-up-your-development-environment.md index fed381d855..6f758a08ef 100644 --- a/docs/spfx/set-up-your-development-environment.md +++ b/docs/spfx/set-up-your-development-environment.md @@ -167,8 +167,6 @@ Depending on your scenario, you may need to maintain different development envir - Node version managers > [!TIP] -> For more information on node version managers, see [Better Node.js Install Management with Node Version Manager](https://www.voitanos.io/blog/better-node-js-install-management-with-node-version-manager/). -> > - [Node Version Manager (NVM)](https://github.com/creationix/nvm): for macOS > - [Fast Node Manager (FNM)](https://github.com/Schniz/fnm): cross-platform (Windows and MacOS) > - [Node Version Switcher (NVS)](https://github.com/jasongin/nvs): cross-platform (Windows and MacOS) @@ -195,7 +193,7 @@ In case the certificate is not added to the Trusted Root Certification Authority ### Unable to Install Packages with npm - Corporate Proxies -If your development environment is behind a corporate proxy, you need to configure npm to use that proxy. Refer to the [npm-config](https://docs.npmjs.com/misc/config) documents on how to configure your development environment behind a corporate proxy... specifically the **proxy** & **http-proxy** settings. More information: [Configure npm for a corporate web proxy](https://www.voitanos.io/blog/node-npm-fix-proxy-config/) +If your development environment is behind a corporate proxy, you need to configure npm to use that proxy. Refer to the [npm-config](https://docs.npmjs.com/misc/config) documents on how to configure your development environment behind a corporate proxy... specifically the **proxy** & **http-proxy** settings. ## See also From 79e59f7d9c110f086176058ac292397cc647d2c9 Mon Sep 17 00:00:00 2001 From: Ashlesha-MSFT Date: Mon, 22 Jun 2026 18:07:57 +0530 Subject: [PATCH 5/9] removed voitanos link --- docs/spfx/sharepoint-2016-support.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/spfx/sharepoint-2016-support.md b/docs/spfx/sharepoint-2016-support.md index 5855518054..13f6a9169a 100644 --- a/docs/spfx/sharepoint-2016-support.md +++ b/docs/spfx/sharepoint-2016-support.md @@ -107,4 +107,3 @@ For more information, see [issue #1002](https://github.com/SharePoint/sp-dev-doc - [SharePoint Framework Legacy Toolchain: Gulp & Webpack](toolchain/sharepoint-framework-toolchain.md) - [Set up your SharePoint Framework Gulp-Based development environment](set-up-your-development-environment-gulp-toolchain.md) - [SharePoint Framework development tools and libraries compatibility](compatibility.md) -- [Definitive guide for developers: SharePoint Framework for SharePoint Server 2016](https://www.voitanos.io/blog/definitive-guide-sharepoint-framework-sharepoint-server-2016/) From 1c07c1b7fa9c52d0fb1f7fac1998ddfba8c52108 Mon Sep 17 00:00:00 2001 From: Ashlesha-MSFT Date: Mon, 22 Jun 2026 18:19:23 +0530 Subject: [PATCH 6/9] Update batch requests article metadata and content --- docs/sp-add-ins/make-batch-requests-with-the-rest-apis.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sp-add-ins/make-batch-requests-with-the-rest-apis.md b/docs/sp-add-ins/make-batch-requests-with-the-rest-apis.md index 62a4d76e09..2aa7d69e4b 100644 --- a/docs/sp-add-ins/make-batch-requests-with-the-rest-apis.md +++ b/docs/sp-add-ins/make-batch-requests-with-the-rest-apis.md @@ -12,7 +12,7 @@ This article describes how you can batch queries and operations against the REST ## Executive summary of the $batch option -SharePoint Online (and on-premises SharePoint 2016 and later) and the Office 365 APIs implement the OData `$batch` query option, so you can rely on [the official documentation](https://www.odata.org/documentation/odata-version-3-0/batch-processing) for details about how to use it. (Another option is to see Andrew Connell's blog posts on the subject beginning at [Part 1 - SharePoint REST API Batching](https://www.voitanos.io/blog/part-1-sharepoint-rest-api-batching-understanding-batching-requests).) +SharePoint Online (and on-premises SharePoint 2016 and later) and the Office 365 APIs implement the OData `$batch` query option, so you can rely on [the official documentation](https://www.odata.org/documentation/odata-version-3-0/batch-processing) for details about how to use it. The following is a reminder of the major points: From 0ab83125f9654d9e194237667c61cfd563dd632f Mon Sep 17 00:00:00 2001 From: Ashlesha-MSFT Date: Mon, 22 Jun 2026 18:21:50 +0530 Subject: [PATCH 7/9] Remove links to definitive guides for SharePoint Framework Removed links to definitive guides for SharePoint Framework for SharePoint Server 2019 and Subscription Edition. --- docs/spfx/sharepoint-2019-and-subscription-edition-support.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/spfx/sharepoint-2019-and-subscription-edition-support.md b/docs/spfx/sharepoint-2019-and-subscription-edition-support.md index 59cfc60642..2407627754 100644 --- a/docs/spfx/sharepoint-2019-and-subscription-edition-support.md +++ b/docs/spfx/sharepoint-2019-and-subscription-edition-support.md @@ -131,5 +131,3 @@ For more information, see [issue #1002](https://github.com/SharePoint/sp-dev-doc - [SharePoint Server 2019 development platform](../general-development/sharepoint-2019-development-platform.md). - [SharePoint Framework Legacy Toolchain: Gulp & Webpack](toolchain/sharepoint-framework-toolchain.md) - [Set up your SharePoint Framework Gulp-Based development environment](set-up-your-development-environment-gulp-toolchain.md) -- [Definitive guide for developers: SharePoint Framework for SharePoint Server 2019](https://www.voitanos.io/blog/definitive-guide-sharepoint-framework-sharepoint-server-2019/). -- [Definitive guide for developers: SharePoint Framework for SharePoint Server SE](https://www.voitanos.io/blog/definitive-guide-sharepoint-framework-sharepoint-server-subscription-edition/). From b70ce2491a838906eaa219ec12b8d74bcee61ff0 Mon Sep 17 00:00:00 2001 From: Ashlesha-MSFT Date: Mon, 22 Jun 2026 18:25:45 +0530 Subject: [PATCH 8/9] deleted voitanos link Clarified the installation instructions for Heft, emphasizing the option to install it globally. --- docs/spfx/toolchain/customize-heft-toolchain-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/spfx/toolchain/customize-heft-toolchain-overview.md b/docs/spfx/toolchain/customize-heft-toolchain-overview.md index 0c76e5aa38..8fa67e2da9 100644 --- a/docs/spfx/toolchain/customize-heft-toolchain-overview.md +++ b/docs/spfx/toolchain/customize-heft-toolchain-overview.md @@ -32,7 +32,7 @@ npx @rushstack/heft --help ``` > [!TIP] -> Similar to Gulp, Heft is installed locally within your project. However, [unlike Gulp that requires installing the Gulp CLI globally](https://www.voitanos.io/blog/mea-culpa-always-install-gulp-cli-globally-not-gulp/), you can install the same Heft npm package globally to simplify running Heft commands. +> Similar to Gulp, Heft is installed locally within your project. If you prefer, you can also install Heft globally to simplify running Heft commands. > > ```console > npm install @rushstack/heft --global From 7a0db1ba2354700913ca2fa043566b94c60a8210 Mon Sep 17 00:00:00 2001 From: Ashlesha-MSFT Date: Mon, 22 Jun 2026 18:28:55 +0530 Subject: [PATCH 9/9] removed voitanos link --- .../set-up-your-development-environment-gulp-toolchain.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/spfx/set-up-your-development-environment-gulp-toolchain.md b/docs/spfx/set-up-your-development-environment-gulp-toolchain.md index 5ac5d4de25..e65f493d73 100644 --- a/docs/spfx/set-up-your-development-environment-gulp-toolchain.md +++ b/docs/spfx/set-up-your-development-environment-gulp-toolchain.md @@ -152,7 +152,6 @@ The SPFx build toolchain will replace this value on the fly with a value defined Developers can use the `SPFX_SERVE_TENANT_DOMAIN` OS environment variable to specify the tenant domain (or site URL) for serve configurations across different SPFx solutions. If a URL in the serve configuration (for example, `pageUrl` for Field Customizer) contains the `{tenantDomain}` placeholder, it will be automatically replaced with the variable's value. -For more information on how to set the environment variable on your developer environment, including Windows or macOS, see [Setting the SharePoint Framework Hosted Workbench Test Site](https://www.voitanos.io/blog/set-spfx-hosted-workbench-test-site/). ## Optional tools @@ -190,8 +189,7 @@ Depending on your scenario, you may need to maintain different development envir - Node version managers > [!TIP] -> For more information on Node version managers, see [Better Node.js Install Management with Node Version Manager](https://www.voitanos.io/blog/better-node-js-install-management-with-node-version-manager/). -> +> For more information on Node version managers. > - [Node Version Manager (NVM)](https://github.com/creationix/nvm): for macOS > - [Fast Node Manager (FNM)](https://github.com/Schniz/fnm): cross-platform (Windows and MacOS) > - [Node Version Switcher (NVS)](https://github.com/jasongin/nvs): cross-platform (Windows and MacOS) @@ -218,7 +216,7 @@ In case the certificate is not added to the Trusted Root Certification Authority ### Unable to Install Packages with npm - Corporate Proxies -If your development environment is behind a corporate proxy, you need to configure npm to use that proxy. Refer to the [npm-config](https://docs.npmjs.com/misc/config) documents on how to configure your development environment behind a corporate proxy... specifically the **proxy** & **http-proxy** settings. More information: [Configure npm for a corporate web proxy](https://www.voitanos.io/blog/node-npm-fix-proxy-config/) +If your development environment is behind a corporate proxy, you need to configure npm to use that proxy. Refer to the [npm-config](https://docs.npmjs.com/misc/config) documents on how to configure your development environment behind a corporate proxy... specifically the **proxy** & **http-proxy** settings. ## See also