Forum Discussion
Modern subsites?
One strong argument for the classic sub-site Information Architecture is that important Web Designer Galleries -- the Web Parts gallery, the List templates gallery and the Style Library -- all live in the Site Collection, not in the sub-sites. We maintain important assets in these galleries and in the Style Library: in one place, where a change automatically applies to all the subsites within that site collection.
In a new Information Architecture where all sites are site collections -- and we have 1000s of these site collections -- where do we deploy a common, custom JavaScript that we would traditionally keep in the Style Library? Same question for custom list templates, web parts, themes, solutions and composed looks?
Related to this - if I wish to make a custom list accessible to a number of sub-sites then it must live in the root site of the site collection. I don't see how I can provide this functionality if I adopt the "new" flat infrastructure where subsites are not used
- Chad_V_KealeyFeb 12, 2018Iron Contributor
I know that in our on-prem 2010 environment, subsites were over-used and often created real tangles of permissions and navigation, so we're trying to get people on board with a flatter structure. However, we have a number of cases where that really wouldn't work or make sense. For example, we have a department that handles "Student Conduct Hearings". Each "case" they handle has a unique set of users (viewers) and needs its own site provisioned using a customized site template (with IRM enabled on the doc library). I'm sure we could create our own site collection template, but we want the end users ("owners" of the site) to be able to provision those case sites without our intervention (and we have self-service site creation disabled).
For this purpose, the classic layout of the subsites isn't really a problem, but it's visually jarring to go from a modern site to a classic one.
- Mary F HarveyFeb 15, 2018Iron Contributor
Yes, that's what I'm finding as well. I try to use as flat a structure as possible, but there are certain types of business processes I want to support in SharePoint Online that just work better with a subsite structure in order to be able organize the content and then also bubble up content from all the sites. Hub sites will help as well Site Designs (the ability to "templatize" modern sites), but not in all cases.