Apr 17 2018 03:16 PM
We have a relatively large organization (over 1000 employees) and about a dozen departments, each with several teams in them, serving the administrative side of our organization. We're looking at two potential models for hubs and trying to evaluate which makes sense.
I'm not sure which fits with the hub model that Microsoft is building out. If you could have hubs above hubs, then it is obvious that each department would be a hub. Without nested hubs, then I'm not sure what to do. Can you syndicate news and documents from a hub to another site (that would include content from the child sites)? Anyone else thinking through this all right now?
Apr 18 2018 07:20 AM
We are in the same predicament.
We've also thought that having hubs on hubs would work best for us.
My opinion is swaying more to Option 2.
Apr 18 2018 07:57 AM
Apr 18 2018 08:39 AM
Apr 18 2018 08:52 AM
Apr 18 2018 08:54 AM
Apr 19 2018 09:44 AM
I would recommend multiple hubs and in terms of navigation use a global navigation application customizer that is deployed across each site collection. Once thing I am not clear on is if an application customizer is deployed to a hub site if it pushes out to all attached site collections associated with it.
Apr 19 2018 12:03 PM
Multiples hubs has a few other benefits, in my opinion, not listed yet:
Apr 23 2018 10:34 AM
The #2 option is more inline with how the product feature is designed. And I do feel gives the best foot forward for each department to get the most of what they need from a day-to-day pov.
Each department will retain more freedom in their own space, with all the benefits hub sites offer for cross-site nav, news and such.
It would be feasible to create a distinct hub site or custom portal to help the whole company find each department - if this is a goal. But this is merely manually configuring the nav to point to each department hub as you cannot associate one hub under another. However, the cross-site nav element can be programmed with anything, so it may help with organizing - but to be clear, only the department hub sites would get the value of roll up and scoped search - and each department remain a little more autonomous.
Creating a simple custom portal (front door) to all is not uncommon, and an area of great interest to our customers, our partners in this space, and Microsoft.
And one small note, the hub sites planning guide is in final mile review, and I'll update the launch blog and make a little tweet noise about it from @SharePoint.
Cheers,
Mark
Apr 24 2018 05:52 AM
@Mark Kashman wrote:
Creating a simple custom portal (front door) to all is not uncommon, and an area of great interest to our customers, our partners in this space, and Microsoft.
Hi Mark,
So in the context of a small organisation (350 people) wanting to have an Intranet portal for the entire organisation , that perhaps rolls up content from division sites (and/or team and project sites), best practice may be to create a custom portal using a communication site (or is a publishing site recommended here?) and allow the site owners to use Hero and news web parts to manually link to articles across multiple sites (rather than to have automatic roll up of content from sub-hub sites that the site owners of the hub site have limited control of).
Hub sites could be created for each division (or functional area) within the organisation. teams within the division/functional area would each have their own team (or team site) which could be connected to the appropriate divisional hub site. the advantage here being that if an organisation changes e.g. a new division is created and a team is moved to the new division, it is now very easy to associate the existing team site with the new hub site for the division.
thanks,
colm
Dec 04 2018 11:23 AM
Jan 02 2020 07:17 AM
I am also curious what the decision was and how things are going with the approach you've taken. Thank you!