SharePoint Online is continuously evolving and improving, which is a great thing for you as a consumer of the service. One of the key features is the availability of modern sites, which are modern (Office 365 group-connected team sites) or communication sites, combined with improved functionality that can be consumed from a beautiful, responsive, modern user interface. To learn more about modern checkout the SharePoint classic and modern experiences article and get inspired by the SharePoint Look Book or simply provision these modern sites in your tenant using the SharePoint Online Provisioning Service.
All of this is great, but you might ask yourself, I have lots of classic sites…how do I bring them into the modern SharePoint world? The answer is (in-place / cross-site) modernization: you can fully transform (or “modernize”) a classic site team sites into modern, optionally Office 365 group-connected, sites by following the SharePoint modernization guidance. Check out the Modernize your SharePoint pages blog post to learn more about the page modernization basics.
A key part of modernizing your sites is transforming your classic pages into modern client-side pages. This transformation is possible using the SharePoint PnP Modernization framework, which is a .Net library that you can use via either .Net code, PnP PowerShell or the Page Transformation UI tool.
June 2019 updates for page transformation
The key new capability in page transformation is the ability to also modernize publishing pages, next to the wiki and web part pages which were supported from day one. Whereas page transformation for wiki and web part pages typically happens in-place, publishing page transformation always happens cross-site. In a typical publishing portal modernization, a new information architecture is designed for the modern portal consisting out of communication sites, hubs, site page content types, page templates…Check out the Modernize classic publishing portals article to learn more about publishing portal modernization.
Below list contains the main features of publishing page transformation:
- Page layout specific transformation due to the possibility of using a page layout mapping which: