Add the ability to hide the hub site navigation via some setting or powershell.

The hub site navigation is a list of static links with no security trimming and no way to target an audience. With the introduction of SharePoint SPFx extensions we have the ability to create a header on top of the page. The most common usecase in this scenario is to create a customized menu. However if hub sites are used and you need a customized menu you will have two menu's at the top.

Here are a few business scenario's for a customized menu

1. Company has a project management system in SharePoint. They would like to show all projects a user has access to in the menu.


2. My Links: User has the possiblity to add personal links to a menu and show them in the menu on all sits. Can even be targeted links manged by IT so specific groups of people


3. A large company has users from all over the world. They translate some of their pages into multiple languages. They would like to link to the page with the correct language for that user.


4. Company wants a global menu accross all sites. many hubsites are also involved. They do not want to manage the links at many locations.

It would therefore be nice (if needed) to turn off the hub site navigation on the hub site and all associated sites.

Changes which were implemented by Microsoft in Office 2016 and SharePoint Online, as well as list view thresholds make entering SharePoint metadata on documents prohibitive.

Office 2016 Desktop Applications:

One significant change in Office 2016 was the removal of the document information panel (DIP). When the DIP displayed in Office applications (pre-2016), it was obvious even to the most casual SharePoint users that there were document properties which should be assigned values, as well as how to enter these values. By contrast, with the DIP removed in 2016:

1. It is not obvious to the casual user that there are document properties that need to be filled in.




2. It is not be obvious to the casual user how they would go about entering values for document properties.




3. It is impossible for any users to distinguish which document properties are of interest to the organization (SharePoint Document Properties), and which are simply standard document properties which are of no consequence ( since both SharePoint Properties and standard document properties are jumbled together in the "Info" screen).




4. It takes two extra clicks to get to the document properties screen where this information can be entered (The user must click on the "File" tab, then the "Show All Properties" link).

Besides the issues mentioned above, there is presently a bug in Office 2016 desktop applications whereby SharePoint document properties of type "Person" cannot be entered in Office 2016 desktop applications on initial save.

In SharePoint Online:

When selecting "+New-->Word Document" from a document library in SharePoint Online, the new document is opened in Word Online by default (even if your library is configured to "open in the client application"). assuming the user chooses to work with the document in Word Online:

1. It is not obvious to the casual user that there are document properties that need to be filled in.




2. It is not be obvious to the casual user how they would go about entering values for document properties.




3. In situations where there are required fields, the casual user would not enter any values, resulting in the document being stuck in a checked-out state, and invisible to other users.




4. It takes many clicks to enter metadata on the document, since the user would first have to find the document (potentially through a search/retrieve process), then access the properties via the right click menu.

SharePoint Online also forces users to organize documents into folders because critical operations such as "open with explorer" only works if there are less than 5,000 items in any given container (see https://support.office.com/en-us/article/Manage-large-lists-and-libraries-in-Office-365-B4038448-EC0E-49B7-B853-679D3D8FB784#bkmk_basics ). Expecting users to enter document metadata to organize files, while organizing content into folders to avoid hitting list view threshold issue is not realistic.

In closing:

Practically speaking, these issues prevent many of our users from taking advantage of SharePoint's metadata organization capabilities, and affect the overall adoption of SharePoint in our organization.

Thanks.

Please enable a breadcrumb for navigating pages on SharePoint. Even if its just for Modern Pages... or Communication Sites.

Scenario:
We have our intranet on our main site collection (consisting of 6 sub-sites exc. the root site) and one of the biggest problems I come across from end users is that they dont know where they are.  They clicked a link from the homepage or from a news article, its taken them to the page they wanted to go to... but they have no idea where that is.
 
The problem this causes is the user cannot find a way to navigate back... when the news page disappears from the latest news feed or the link from the homepage is deleted, they're stuck and have to resort to searcnavigation hing (which doesnt always pull back the result they need).
 
A solution similar to the one that Franck Cornu implemented on the PnP Starter Intranet would be great.  It uses the metadata navigation taxonomy to display the logical stucture as breadcrumbs accross the top of the page.

Overview of the PnP Starter Intranet: http://thecollaborationcorner.com/2016/08/22/part-1-functional-overview-how-to-use-the-solution/#.WVPkcYWcFaQ