Forum Discussion
When to use Team site (classic experience ) which uses modern UI Vs Team sites / Office 365 groups
I would use a comm site for my intranet sites because you get a modern top navigation which looks much better than the left quick launch bar. Eventually in near future we'll get the option to change this on all sites thou but for now comm site is the only way.
Classic vs Team (Group site) is only difference is one is connected to a Office 365 group and the other isn't. With that the site has the Group added to default security (Owner, editor) and can be managed with the group. You can tie Teams / Planner etc. to it. And you get the extra webparts because they are group connector webparts which require a group to be used.
As you discovered you can turn classic site into a group connected site (Groupify) so you can go either method, but the modern way is either using Communication sites for stand alone sites, and then Team site(Group site) for collaboration sites / teams etc.
I use Communication sites for all my org facing intranet sites (Home, HR, IT, Finance etc. ) and they are all joined to a Hub (not subsites) where the Home site is the hub, then join the department sites to that hub, rolling up search and content to all the joined sites. This is the "modern" way of doing subsites.
ChrisWebbTech wrote:I use Communication sites for all my org facing intranet sites (Home, HR, IT, Finance etc. ) and they are all joined to a Hub (not subsites) where the Home site is the hub, then join the department sites to that hub, rolling up search and content to all the joined sites. This is the "modern" way of doing subsites.
Hi Chris, thanks for the useful reply. I have never used Hub sites in sharepoint before, so it is a new area for me which i have never touch. now in my current case i just created a classic Team site and i set it as our home site for the intranet. then i was planning to create sub-sites for our departments, but before i did so i asked this question to make sure i am doing things correctly in the Modern world. but seems the modern way is to use Hub sites and joining sites to this Hub site, instead of just creating sub-sites.
so now for me to follow the modern way ,i am not sure if i can do these steps:-
1. can i convert my current classic team site to be a hub site, without loosing our current data? as our current classic team site already contain many modern pages + documents ?
2. also our current classic site contain some classic pages, which we are embedding inside modern pages using the Embed modern web part. we use some classic pages as they allow us to add JavaScript code to them. so can we still use/create classic pages in hub sites, and embed these classic pages inside the hub site's modern pages?
3. One of the main benefits i usually get from using site collection and sub-sites, is that columns and content types created at the root site (site collection) will be available to all the sub-sites without having to set content type hubs or any things else, also i have the ability to have a sub-sites which inherit their permissions from its root site, finally i also have the ability to have sub-sites of each sub-site. so i am not sure if these features/capabilities are also offered for us when we use site collections linked to Hub Sites?
4. last point, if i follow my current appraoch of using classic team sites and classic team sub-sites, as i have more experience in them, and using hub sites meaning i need extra time to start my actual work.. then how will it be easy to change my structure to follow the Hub sites and linking them to modern site collections in the future ? is there an available tools which can support such an operation/migration ?
can you advice on my above 4 points?