Forum Discussion
SharePoint Modern Team sites Vs Communication sites
You no longer need a wiki page library. Just use modern site pages. They are just as editable by your site members as the wiki pages were, but being modern they come with responsive design and are mobile compatible which wiki pages aren't.
And while I realize that people are unlikely to intentionally navigate to your wiki page library on their phones, it's very possible (even likely) that one person might email a link to a page to another person and you have no way of knowing what device that person will use to read that email & click on that link.
I would strongly suggest you give the modern sites & pages a try. You may find you like them. I did. And I did.
Rachel_Davis @john john
I think this question is best answered when thinking about your objective. Since SharePoint Communication and Team sites store content, it is best to think about your content and permissions structure before selecting either a Communication or Team Site.
Consider Content and Permissions When Choosing a Site Type
There have been several articles written explaining the Document Life Cycle. We have used these for our strategy, which is:
My Stuff - individuals save to OneDrive for Business for work that they are not ready to share (with the Team or company-wide). OneDrive for Business allows work to be shared with either read only or write permissions with individuals in or outside the company.
Team Stuff - Team Sites are created (with O365 Groups) so the team can collaborate. Anyone in the team has view and editing access to the documents. Any team wanting the additional benefit of the MS Teams application (Chats, online meetings, etc.), can easily use this application as well. In fact, we've noticed that the easiest way to create a Team site is through the Teams application. I do not believe there is a limitation on the number of team members assigned to a team site.
Everyone's Stuff - Communication sites are created to share (PUBLISH) company documents for everyone to view and use as well as for company news. There are fewer users (publishers) than there are readers.
Hub Sites Organize the Organization's Site Collections
Hub sites are easily created from existing communication sites and you can also add team sites to your hub. This gives you a shared look and feel and it is just as easy to associate a communication or team site to a hub as it is to dis-associate one. One advantage of the hub site is roll-up news from all the sites you associate with the hub (this is the default setting, but can be changed). Another advantage is that nobody can see what they aren't supposed to see. In other words, only users who have permission to see a connected Team site will see content from that site. In the Modern experience, using hub sites also provides a better search experience that is user-specific.
Much has been written above that seems to describe the former Classic architecture. In the Modern experience, subsites are NOT recommended. The hub provides the organization for each site collection that associates to it. Hubs are established (and governed) by IT. As a hub owner, you can opt to create an approval before a site (team or communication) joins. If you are a site that wants to join a hub, choose wisely because you can only join one hub. Per the September 2018 Ignite conference, having an association to more than one hub is not in the roadmap. You can, however, connect more than one hub and create a "Super Hub". We shall see...
