SharePoint Hub Sites

-
What is SharePoint Hub Site?

 Hub sites are new intranet building blocks in office 365 (only no OnPremise support yet, not even SP2019). In the new flat world of modern SharePoint, each unit of work gets a separate site collection. Hub sites allow us to eliminate the inflexibility and governance limitations of “dreaded” subsites, while providing a way to replicate one of the key benefits of subsites — a way to create a shared experience among related sites. Hub sites can help kill subsites, but not without a little planning.

 Modern SharePoint has given users power to create multiple types of sites, Team Site, Communication sites and Hub sites. A lot of people really gets confused about all three. I'll briefly sum up the three 
  • Team site: Collaborate with members of a project or organizational team
  • Communication site: Communicate to a broad group of people or the entire organization
  • Hub site: Connect related sites to create a shared navigational and content experience
A hub site is not really a new type of site — it’s basically a capability that you enable for an existing site — either a team site or a communication site. Most hub sites will be communication sites, but there is no technical requirement that forces this to be true.

A Hub site gives you three things 
  • Shared Navigation and Branding
  • Roll-up Content and Search
  • A home destination for the hub
When should you create a Hub Site:-

Create Hub site when you really think its necessary. You don't need to create a hub site for just a single site. A hub is basically a family of sites.Think about hub sites for key functions that your users need to get work done—for example: HR, Finance, Communications or Public Relations, Legal, and IT. These functions may be represented in different organizational departments or business units in large organizations or combined into the role of a few people in smaller organizations.
An HR has following sub-functions:-
  • Benefits
  • Compensation
  • Talent acquisition
  • Performance Management
  • Training
All the above functions can be a separate site collection and all these sites can be treated as family of HR hub.

Initially, your organization is limited to 50 hub sites. You may not need a hub site for every function, so it's important to do some planning before you create hubs.

If you are a global SharePoint admin in office 365, you can convert any site to a hub site using below PS command

Register-SPOHubSite URL 

You can also demote a hub site using below command,Make sure you do this before you delete the hub site. When you demote a hub site, any sites still associated with the hub site will be automatically disassociated

Unregister-SPOHubSite URL

Here is a great article which gives you the details on Hub Sites Planning


Comments

Post a Comment

Popular posts from this blog

Read all lists/views/fields using pnpjs in spfx webpart

-
Image
Recently I started exploring pnp js with spfx webparts. I wanted to explore few things which are more of basic functionality for any webparts. In this Post I'll explain How to read all the lists from a site and bind to dropdown in spfx webpart Read all the views for a selected list and bind to 2nd dropdown. Get all the fields/columns for a selected view and render then as checkboxes in spfx webpart. I have created a react spfx project and imported all the sp,web from @pnp/sp library. i mport { sp , Web , List } from '@pnp/sp' ; First step is to declare 3 collections for above 3 requirements so that you can use them in getPropertyPageConfiguration() method. private listDropDownOptions : IPropertyPaneDropdownOption []; private viewDropDownOptions : IPropertyPaneDropdownOption []; private fieldsListCollection = [];   Use these collections in getPropertyPageConfiguration() method. protected getPropertyPaneConfiguration (): IPropertyPaneConfigura
Read more

Deploy artifacts with spfx webparts

-
Image
SharePoint framework (commonly known as spfx ) webparts can be used to deploy the artifacts like js/css/image files etc. There are multiple options to host your artifacts.  First option is to host to CDN (like azure) Other option is to include that within the package and then deploy to appcatalog along with sppkg file. Host to CDN In order to host the webparts to Azure or any CDN,  open copy-assets.json file in config folder of your spfx webpart and update the CDN path. This CDN path can be any SharePoint library or Azure CDN. Basically any path which is accessible using http protocol. If you are publishing to Azure CDN please make sure to add the azure credentials in deploy-azure-storage.json file. Deploy to AppCatalog In case you want to deploy the artifacts to app catalog, package-solution.json file under config folder and make sure that includeClientSideAssets is set to true . Once this is set when you will deploy the webpart to the webpart gallary. 
Read more
-
Wrapping Global Navigation in SharePoint 2013 In SharePoint 2013 if number of links in the global navigation increases, the links are not wrapped by default. The links were aligned in single line. Sometimes the links are more in number that people started complaining about search bar is not available even though the search bar is available in the right corner of the page. Users never realized the horizontal bar at the bottom of the page. If we scroll to the right corner of the page we can see the search bar. Talking about user experience this looks very weird.  In order to fix this issue some of the css classes needs to be updated which will help in wrapping the global navigation in SharePoint 2013. Below are the some of the css classes:- .ms-core-pageTitle{     font-size:2em; } .ms-core-listMenu-horizontalBox ul, .ms-core-listMenu-horizontalBox li, .ms-core-listMenu-horizontalBox  .ms-core-listMenu-item, .ms-core-listMenu-horizontalBox > ul > li > table {
Read more