Transforming to modern site pages from inside the SharePoint UI
The SharePoint Page Transformation UI is currently a beta release. The solution is continuously evolving, checkout the sp-dev-modernization GitHub repository to stay up to date on the latest changes. If you encounter problems please file an issue in the sp-dev-modernization GitHub issue list.
If you want to give your end users the option to self-service modernize pages then using the SharePoint Page Transformation UI makes a lot of sense as it offers your end users UI extensions (ribbon buttons) to launch page transformation:
A second key feature is that the UI integration also allows your end users to accept or discard the generated pages:
Installing the Page Transformation UI in your tenant
The Page Transformation UI installation consists out of 3 steps:
- Installing and configuring the Azure AD protected Azure function app
- Installing and configuring the SharePoint Modernization center site
- Enabling the page transformation UI for the site collections that need it
Checkout the Page Transformation UI deployment guide for step-by-step guidance and check out below video to learn how to set up the page transformation UI solution.
Upgrading from the preview release to the beta release
Upgrading from preview to beta is easy as explained in the upgrade guide.
Page Transformation UI high level architecture
Below steps describe the high level flow of the solution:
- From any of the UI elements the users triggers the creation of a modern version of the selected wiki or web part page. This will be done by calling a "central" proxy page which is hosted in the modernization center site collection
- The "central" proxy page contains an SPFX web part that makes a call to an Azure AD secured Azure Function
- The Azure Function uses the SharePoint Modernization Framework to create a modern version of the page. This created modern version does contain a banner web part which provides the end user with the option to keep or discard the created page. Important to understand is that this modern page is a new page with name like migrated_oldpagename.aspx
- If the page is discarded, a feedback dialog is shown asking the user for a reason why the page was not good. This information is then stored in a central list in the modernization center site collection.
- If the users keeps the page then the modern page gets the name of the original page and the original page is renamed with an old_ prefix