Apr 29 2019 08:02 AM
Apr 29 2019 08:10 AM
Apr 29 2019 09:34 AM
Jan 14 2020 09:41 AM
Is there any evidence that Microsoft are going to ‘actually’ deprecate subsites, or is there an element of reading between the lines here? I can see that hub sites have a roll to play as they offer valuable cross-site publishing which has been problematic in the past, but subsites offer site columns, metadata navigation, and permission inheritance. All the features of subsites have not be made available in other ways if you flatten the structure to use site collections alone.. As an example, if you have a site collection for each and every project in an organisation, there is massive administration overhead compared to each project being a subsite of a ‘programme’ site collection.
Jan 14 2020 09:50 AM
@MichM any classic feature, e.g. metadata navigation, is "deprecated" (hence being called 'classic'). Hub sites are adding permission-push down soon.
And remember, deprecated means "may be removed in the future/no new features being developed" and not "removed".
Jan 14 2020 12:25 PM
@Trevor Seward I was told by a Program Manager at Microsoft Ignite that there are no plans to get rid of subsites.
There are lots of use cases where subsites are mandatory.
Here is one:
- Company wide site (communication site), used for announcements
- Department sites (Team sites accessible only for team members)
Give me a solution to display department wide announcement in company wide site.
My suggestion: Create subsites for each department.
If we go for flat structure, are we going to create two site collections for same department? Remember, there will be divisions in each department.
Subsites are MANDATORY !!!!!
Jan 14 2020 12:30 PM
Jan 14 2020 12:45 PM
@Trevor Seward Comm sites can
not be subsites
I have created Communication sites as subsites. (There is a way)
I'm surprised on having public comm sites for each department, each division, each team, ....... !!!!!
Let's assume the department IT.
It will have minimum 5 divisions, each division will have minimum 5 team and each team will have minimum 5 sub teams.
In this case, 1+5x5x5 = 126 public comm sites just for IT !!!!!
[I'm poor in Mathematics, pardon me for any miscalculations ]
Jan 14 2020 12:52 PM
Jan 14 2020 01:18 PM
@Trevor Seward Based on your responses I see that you are worried about permissions. Unfortunately we did not find any issues with that.
There are organizations where SharePoint Admins do not have access to such level.
One site for every team!?
Sorry! Each team produces more content. They need own space to publish their articles. It will be cumbersome if we provide one site for all. (No, No for item level permission. not at all)
Already users are thinking to move their content to CONFLUENCE because of classic SharePoint.
We(IT) got great relief after seeing Modern site features. Users are liking it.
I request Microsoft, not to deprecate subsites.
And they even promised that metadata navigation is coming to modern sites but you are claiming that it will be deprecated !!!!!
Jan 14 2020 01:40 PM
Sep 01 2021 05:24 AM - edited Sep 01 2021 05:28 AM
Hi, Is there any reference on Microsoft Site that suggests best practices is a flat structure over nested?
That would help
Sep 01 2021 05:55 AM
Check below documentation which will help you to understand the need to flat topologies & how to design flat topology:
Please click Mark as Best Response & Like if my post helped you to solve your issue. This will help others to find the correct solution easily. It also closes the item. If the post was useful in other ways, please consider giving it Like.