sharepoint online – Can we show Hub Site Navigation on classic pages

I have a modern communication site collection which is defined as a Hub Site. and a classic team site which is connected to the Hubsite. now inside the classic site if i use the modern UI the Hub site navigation will be shown which is fine, but if i have a classic page then the Hub site navigation will disappears.. so is there a way to enable the Hub site navigation on classic page?

gui design – Same Side Navigation for bigger and smaller screens?

I am trying to find a way to navigate amongst rather complex content using an “admin” side navigation. The goal have been to use same navigation regardless of mobile or desktop.

Am I thinking in the right direction or do I have to reconsider?

Live mockup:

Using Hamburger

Bigger screens: The menu should open and close at same level as content. 
Smaller screens: The menu should open and close above content

Resize Windows

Bigger screens: Full menu as default
Smaller screens: No menu as default

Using menu buttons (Home etc)

Bigger screens: Select the active link and stay open
Smaller screens: Select the active link and close

At reloading page

Bigger screens: The menu level select persists and active links should be selected
Smaller screens: The menu should stay closed

Using link on the content

Bigger screens: The menu should stay open at current level and select active link
Smaller screens: The menu should stay closed

information architecture – Evolution of authentication-based navigation

Consider the case where an unauthenticated user sees a main navigation with a few items:

Wireframe of navigation with three tabs

In the old days, someone with admin privileges might log in and simply see additional items exclusive to their role:

Wireframe of navigation with five tabs

In some systems, all of those items would be dumped into an “Admin” menu.

It seems this isn’t what is done anymore – it obviously creates a confusing experience for a user who is inadvertently in an unauthenticated state and doesn’t recognize it.

What are better alternatives to role-based or authentication-based items in the same menu? Adding secondary/utility menus seems to be a popular solution, but even that seems like a dated pattern. Are admins now taken to their own highly differentiated “admin experience”, and is this practical in most cases? What if the admin only needs access to one additional function, such as managing users – is it worth creating a wholly unique experience for that user?

Disable “parasitic” link behaviour on navigation menu

I’ve Worpress site with JetOne theme installed

When I click root menu element in the main navigation menu to open it click action for selected link also triggered that’s the matter. The problem is present on mobile view for that theme.
I already tried

.ct-main-navigation > .menu-item > a {
    pointer-events: none;

But this trick just disables link for root elements of menu.
How to achive the goal right way?

I’ve another idea: recreate navigation using wp_nav_menu_items hook, but I don’t want to break original design and don’t know how to do that exactly.

magento2.3 – Modify In Stock functionality of Layered Navigation

In a specific requirement, we need to have out of stock product listed on website for back orders, magento does offer it very well, but I am looking to have a filter for layered navigation, if chosen it should only list products which has got qty >0 , means readily available, if I enable that qty and stock status in layered navigation along with option of show out of stock products, it always list out of stock products too, while I dont want them if that filter is selected.

navigation – Menu link tree only loads enabled elements in subtree regardless of parameters

When loading a menu tree without any custom parameters:

$tree = Drupal::menuTree()->load('my-menu-name', new MenuTreeParameters());

The returned tree DrupalCoreMenuMenuLinkTreeElement() includes disabled items, which is what I want. I did not set onlyEnabledLinks() or addCondition('enabled', 1) to the MenuTreeParameters.

For some reason, though, every subtree returned beyond the root level excludes disabled items. Even if I re-query each subtree, it still happens:

foreach ($tree as $element) {
    // Do stuff
    $parameters = new MenuTreeParameters();
    $subtree = Drupal::menuTree()->load('my-menu-name', $parameters);

The only way I have found to include disabled items so far has been to re-query each subtree twice with $parameters->addCondition('enabled', 1); and $parameters->addCondition('enabled', 0);, which is ridiculous.

I can’t find anything in the documentation to suggest this is the correct behavior of Drupal, but I’m hoping someone can spot something I’m missing before I submit a bug report. This is in Drupal 9.1.

How to remove the user profile folder from navigation pane in Windows Explorer?

How do I remove the user profile folder from navigation pane in Windows Explorer on Windows 10?

enter image description here

Seems like none of the currently recommended solutions work no more, including editing the following Registry keys:

HKEY_CURRENT_USERSOFTWAREClassesCLSID{59031a47-3f72-44a7-89c5-5595fe6b30ee} and

setting the DWORD key System.IsPinnedToNameSpaceTree to 0.

Is reversing the menu order on mobile navigation a good idea?

I work at a place where they are keen on reversing the order of the navigation items on mobile menus.

The menu is at the bottom of the screen, and the order is reversed, so Home (basically the three most important menu items) are on the bottom of the list while on desktop they would be most left of the list:

Desktop menu:

Home | About Us | Pricing | Whaterver

Mobile menu

About Us

I have found one case online where this practise is suggested.
To me, it is very counter intuitive since logically the most important thing is on top, and not on the bottom of the list.

I can see that the bottom items are more easily reachable with the thumb like this, but I imagine users would be spending more time trying to find the Home button in the list, since they would start to look at the top of the list.

Is there any extensive testing done on this subject? Any insights?

angular 2+ – Is it a good practice to restrict refresh , reload & back navigation of a browser(In some special cases only) ? If yes how can we implement that?

The user can’t be navigated to the previous page when we click on back navigation. In some cases, we are able to navigate when the page is refreshed/reloaded. need to restrict to a couple of pages, not throughout the app.
Actually, I’m using this

        constructor( private location: LocationStrategy){
history.pushState(null, null, window.location.href);  
this.location.onPopState(() => {
  history.pushState(null, null, window.location.href);