Forum Discussion
Modern subsites?
at the Ignite conference it was defintly 100% clear you do not want to create subsites anymore. So this is your first answer.
the Hub is still in development but i think this will definitely be the way to go with SharePoint.
A example why you should choose sitecollections and the instead of subsites is that when you need to move a site to a different department or other sitecollection. this is not possible without migrating if you use a subsite.
Hmm. Okay. Good to know that was the message given. I don't know that I entirely agree with that approach.
Hubs will not be able to be linked to other hubs, so that means only one level of categorization of a site. And while I do understand the problem of moving a site between departments requiring export/import, it is not a scenario I've run into so frequently that subsites should be ruled out categorically.
I agree. I don't really understand how this will work for us. We are a small company with quite a lot of projects and the current modern experience doesn't allow us to organise sites in an easy way. We currently have 9 service areas with programmes and projects underneath those. Many projects relate to each other so have a natural hierarchy and while a flat structure is fine for quick access via the hub, it is not very useful for finding old projects that we regularly need to refer to. We also don't want to spend thousands of pounds contracting consultants to write some bespoke pages for us, especially when there is such a transition between classic and modern.
Does anyone have any links to videos/pages that explain how a company *should* structure their site collections to create a coherent structure in line with our operational needs? Most of the videos i've seen just demo individual site/group creation.
