#spfx
What we learn moving organisations onto the Microsoft cloud. Method, not opinion.
Developing for SharePoint Server Subscription Edition: the practices that hold up
Subscription Edition is supported until at least 2035 and its SharePoint Framework ceiling has not moved since 2023. That combination is the whole job: a long runway on an older stack. This is how to build on it well, with code that runs on the version your farm actually accepts.
SPFx before version 1.0: three of our web parts in the official Microsoft samples
The SharePoint Framework developer preview came out in August 2016. Version 1.0 arrived in February 2017. Our first contribution to the official Microsoft 365 samples repository is dated October 2016, five months before there was a 1.0 to build against. Three of our web parts are in that repository today, and this is what each of them is for.
The state of SharePoint in 2026: what is gone, what is current, and what to build on
Every year someone declares SharePoint dead. It never was. But in a matter of months, real parts of it reached the end of the line: the Add-in model and Azure ACS retired in April, and SharePoint Server 2016 and 2019, InfoPath and SharePoint Designer left support in July. Here is what actually ended, what replaced it, and what to build on now, on-premises and in the cloud.
SPFx 1.23.2: upgrading is not changing a number
The previous version was pulled from npm for regressions, and that is the warning: the risk of upgrading the SharePoint Framework is almost never in the SharePoint runtime, it is in the build. What changed in Heft, in Sass and in npm audit, with the code showing how it was, how it is, and how it will be.
Migrating SharePoint without stopping the business
The hard part of a migration is not moving files. It is that nobody stops working while they move.
Nothing matches your search.