Feb 05 2019 03:28 PM - edited Feb 05 2019 03:52 PM
I want to start a new project for one of our customers, as the first draft we want to create a site collection with these components:-
now i want the site collection to be on the root, and we already have the root site collection created for us which is based on the classic team site. so i have these questions:-
Thanks
Feb 05 2019 05:55 PM
Hello @john john
I would be inclined to use the root site collection with a redirect page to a communication site in /sites. When the Set "Communication Site" as Root site collection feature is complete I would convert the root site collection to a communication site and then migrate the communication site content (from /sites) to the root.
Make sense?
I hope this helps.
Norm
Feb 05 2019 10:54 PM
Feb 06 2019 05:14 AM
@Norman Young wrote:Hello @john john
I would be inclined to use the root site collection with a redirect page to a communication site in /sites. When the Set "Communication Site" as Root site collection feature is complete I would convert the root site collection to a communication site and then migrate the communication site content (from /sites) to the root.
Make sense?
I hope this helps.
Norm
@Norman Youngthanks a lot for your reply.
So are you trying to say the following:-
1. Keep the root classic team site collection as-is. and then create a communication site under "https://ourtenant.sharepoint.com/sites/IntranetABC/" to act as a temp root site? .
2. once the "Set "Communication Site as Root site collection" feature become available.. i can migrate the content from the "https://ourtenant.sharepoint.com/sites/IntranetABC/" to the root? not sure when we should expect this feature to be available?
Thanks
Feb 06 2019 05:20 AM - edited Feb 06 2019 05:21 AM
Feb 06 2019 05:20 AM - edited Feb 06 2019 05:21 AM
@Juan Carlos González Martín wrote:
At Ignite Microsoft announced they will provide a cmdlet to convert the root SPO site of a SPO tenant into a communication site
https://techcommunity.microsoft.com/t5/Microsoft-SharePoint-Blog/Build-your-modern-intranet-with-Sha...
This cmdlet is still not there AFAIK, but there are workarounds to get what you need:
- Via SPFx Extension + creating a modern page as home page for your root site collection: http://sharepoint.handsontek.net/2019/02/05/convert-classic-root-sites-to-modern-sharepoint/
- via redirectio: https://techcommunity.microsoft.com/t5/SharePoint-Developer/Convert-Classic-root-site-to-Communicati...
@Juan Carlos González Martín thanks for the reply. i actully read these links before , but i have these comments:-
for this link https://techcommunity.microsoft.com/t5/Microsoft-SharePoint-Blog/Build-your-modern-intranet-with-Sha... the replies are saying that this approach is not supported
for this link http://sharepoint.handsontek.net/2019/02/05/convert-classic-root-sites-to-modern-sharepoint/ it is saying to add modern pages + "Create a full width landing page" app inside our classic team site. so at the end my site is a classic team site with modern experience. but i want my root site to be an actual communication site ..
can you advice on my above 2 points?
Thanks
Feb 06 2019 05:48 AM
Hi @john john
Yes that is what I was getting at. The value to the customer is the root URL and the modern communication site experience. The value to you is developing the communication site once using the modern experience. Migrating the communication site content can happen down the road when Set "Communication Site" as Root site collection is rolled out.
Norm
Feb 06 2019 05:58 AM
@Mark Kashmannone of your recent RoadMap Pitstop posts have mentioned this long overdue feature. Can you PLEASE provide us a status update. The silence on this much needed feature is frustrating.
Aug 23 2019 03:29 AM
There is a new method to achieve this supported by Microsoft, I've wrote a blog post explaining how to do it.
All you have to do is to execute the site swap cmdlet available on the latest version of the SharePoint Online Management Shell.