Certainly, the standard recommendation moving forward would be to use modern sites and a flat structure, rather than subsites and/or classic sites. You're right, this changes how we approach things like content types.
The content type story is an interesting one these days:
Content type hubs haven't been updated recently, nor have they been talked about ...
Actually, the Hub site is considered a top-level site collection for other site collections to serves the flat structure, unlike the old Site collection and its subsites structure!
the Hub site has the below characteristics
Created from a team or communication template,
Only created by admin,
Only available in SharePoint online.
Preferred to use with the ...
Typically you would create a template for the use when creating site. You don't have to create a new Document Library, simply add the Content Type with metadata, and remove the default "document" CT.
Then you save the site as a template for later use. When you create a new site you make use of your template, and there is no need for the extra work switching ...
I tested this with my own hub site and took screen grabs.
Edit the left rail navigation
Click on the '+' to get the Add a link dialogChoose "Header" and enter "Display name"Click "OK"
Repeat the process for your sub-itemIf you want to have a link to a document or list item, use the URL optionOtherwise just create another Header
Select your first sub-item ...
You can activate web feature - SharePoint Server Publishing.
After that, Navigation settings will displayed in Site Settings as on picture below. Now it will be possible to add heading without link.
Also you can access navigation settings by the link - http://YOUR_SITE/_layouts/15/AreaNavigationSettings.aspx
We can download the SharePoint Online Management Shell.
And connect SharePoint online admin site and get the hub sites using the PowerShell below.
connect-SPOService -Url https://xxx-admin.sharepoint.com
And get all the sites associated hub site base on the sub site Id.
$sites = Get-SPOSite ...
At this point, search in modern sites is not configurable. So,
Option 1 is to train users to click the breadcrumb on the search page to get to the broader results.
Option 2 is to create a custom spfx search box that redirects to the results page with the desired scope.
Option 3 is to redirect users to a classic search center, configured as desired.
At #MsIgnite, Microsoft just announced a way to convert the root site into a modern communication site using PowerShell, but, this new PS command is not yet publicly available. So, currently, there is no way to directly convert root site to Communication modern site.
Deleting and recreating root site also is not a way because there is no way to create a ...
Another way to approach this is: how much risk is acceptable in my project ?
The flat model and hub sites gives us a lot out of the box, however once we hit the boundries, we hit them at full speed, and only a very limited number of the old tricks we know is available in Modern SharePoint.
One thing is for sure, we'll be writing a lot of PowerShell in the ...
Yes, you can add a root site as Hub in SPO. A classic site collection can be a hub site. Sub site can't be added to hub and the subsite themselves cant be a hub site. Only a Site Collection can be a hub site.
Also, only the modern pages in Site pages library of the classic site collection will have the benefits of the Hub site.
So, you need to enable the ...
To register a site as Hubsite, you can use the below code:
string tenantAdminSiteUrl = "https://tenant-admin.sharepoint.com/";
string userName = "firstname.lastname@example.org";
string password = "password";
using (ClientContext context = new ClientContext(tenantAdminSiteUrl))
SecureString securePassword = new SecureString();
foreach (char c ...
We can register an existing site collection as a Hub site.
Note: Sites that are already associated with another hub can't be converted to a hub site. Make sure the site is not associated with another hub.
We can create up to 100 hub sites for an organization.
Create a hub site in SharePoint Online for your reference:
Yes, you can convert any existing site to a hub site, refer this
I was able to create a classic site, register it as a hub site. Then create a modern communication site and associate it to this hub site.
Ok, quite simply actually.
Thanks to this issue, I found that the DepartmentId corresponds to the hub site.
So, this KQL filters on the hub site :
or (no more working)
or (credits to @Alberto)
if from a web-part.
This feature is not available, yet. What you're looking at is a Microsoft demo tenant to show features that will be rolling out in the future. This was announced at Ignite 2019.
The intelligent intranet powered by Microsoft 365 – Microsoft Ignite 2019 announcements
It is not recommended to delete the default library which was created by Sharepoint itself - it will have some side effect to the setup.
One of the most advice is to not touch default SharePoint libraries such as:
Hide SharePoint library or list
What should we do in this scenario?
For your ...
This can be achieved thru SharePoint online admin center URL as well as PnP PowerShell script.
Go to the https://tenant-admin.sharepoint.com url
Click Active sites link from left side panel then we can see all active sites report in the dashboard.
Then from the “Active sites” dashboard click on “Hub” -> Filter by Hub -> ...
Since left navigation seems important to users, I would use the site with site template which includes left navigation and then control site behavior via permissions (and possibly site/site collection features).
Nested hub sites aren't supported yet, though the request has been on uservoice for a while. For now, we're stuck with manually linking hub sites together, which is a far different experience than what an actual nesting of hub sites could be.
I would reconsider the purpose of the various sites that have been configured. For example, your root site is a communication site, which is designed publishing content to a wide number of users. Perfect. Team sites are designed for allowing a group of users to collaborate together. Is that what they're being used for in this context, or is their primary ...
I realize the classic way of using subsite organize Permission for departments still useful. But when using subsite, you deny the right for using new apps like Team, Share Outlook, Calendar between the members in each department.
I also realize that if you use the modern way, sharing between other site collections is hard, I am still trying to ...
I Prefer not to use a team site in my structure as they can easily go messy and managing it gets hard when there are several of them.
create A top Level Site Collection(from Office 365 admin Panel)
Then create a Subsite for each Department(You can use the new experience, which is the same as team site) At this stage, Breck, the permission level and create ...
Well, this can be achieved by Powershell script. Here you go.
Connect-PnPOnline -Url "https://[tenant].sharepoint.com/[site]" -UseWebLogin
$web = Get-PnPWeb
#0 - Inherit, #1 - AllPages, #2 - ModernOnly, #3 - Hidden enums for Global (Modern Search)
Write-Host "Done" -BackgroundColor Green
you can go to the 'Change the look' option for the hub site and chose a different menu style (Cascading) from the 'Navigation' options. This will narrow down the menu and may be useful for you.
Please note, Mega Menu can also look nice, if there are multilevel content. See the below mega menu:
Basically, you are asking about the Site Collection swapping features. It is possible but feature is not rolled out yet. Last Week SharePoint Conference, Microsoft announced it and will be available by end of this year.
Check this blog and search for Site swap. SharePoint Site Swap (Coming Soon)
But you can change the Root site collection to Modern ...
You need to request the sub-sub child data again using Get-PnPNavigationNode command.
Modify your code as below:
$TopNavs = Get-PnPNavigationNode -Location TopNavigationBar |Select Title,Url, Id
foreach($TopNav in $TopNavs)
$node = Get-PnPNavigationNode -Id $TopNav.Id
Write-Host "TopNav_Id: [" $TopNav.Id "]" "Title: " $TopNav....
Just today I was able to replace the root site collection for our dev tenant with a communication site.
The method I describe below:
Does not use templates in the manner described in a previous answer on this thread.
Will apply any site designs associated with the tenant and/or permit the post-hoc application of any themes or site designs.
Has the added ...
Classic publishing features are not supported in Modern sites. These sites are NoScript sites by default.
What's not supported on "modern" team sites -
-Custom master pages; more extensive branding will be supported later
using alternative options.
-Enabling site or site collection scoped
publishing features; technically, features can be currently ...