navigation – External links: Specifies whether and how they should be distinguished from internal links and opened

How important is it to distinguish between the two? Will the users mind? Most websites do not distinguish between internal and external links. They just let users drive over the link to see or click and find out.

If necessary, I prefer to stick to the Wikipedia convention, as this is a well-known site, so the icon is recognizable.

Otherwise, you can use dotted underlines for one link type and solid underlines for another type. Or use double underline for one and simple underline for the other. You could even use different link colors to make them stand out even more, but that's probably not appropriate in most cases.

The last option is to put external links in a separate section (Wikipedia does the same on most pages). This clearly indicates to users that they are external links, and allows users to easily find / avoid them.

In most cases, however, it is completely unnecessary for users to "warn" that a link is external. Avoid linking to bad websites or irrelevant content.

Java – How do I avoid circular dependencies in the abstraction of navigation in desktop applications?

I'm trying to extract some features from my desktop application (JavaFX) to change views.

So, what I think is:

Navigator interface with methods such as goToAccountsOverview (). goToAccountDetails (Account Account) etc. The implementation depends on a View Factory to create the views and a Viewing ViewChanger to change the displayed view.

Depending on the status of the application, there are several navigator interfaces, starting with:

  • NotConnectedStateNavigator (goToConnectToDatabase (). goToCreateDatabase () etc)

  • Connected State Navigator (goToAccountsOverview (). goToAccountDetails (Account Account) etc)

So each state has its own navigator and view factory and a common view changer. The view factories and navigators do not share a common interface (createView (ViewEnum v) and goToView (view view) respectively).

During implementation, I come across a problem. An example of the problem is the following:

In that Account Overview View There is a table with all accounts. Each account has a button to display the details. If you press this key, navigate to Account Details View with the ViewModel of the account (I'm using some kind of MVVM).

It would call for that connectedStateNavigator.goToAccountDetails (accountVM) what would call viewChanger.changeView (connectedStateViewFactory.createAccountDetailsView (accountVM))).

So the Account Overview View needs the Connected State Navigatorthat needs that Connected State View Factorywho must be able to construct the original Account Overview Viewthat needs that Connected State Navigator etc.

Some codes to explain it better:

public class AccountsOverviewView {
public AccountsOverviewView (ConnectedStateNavigator navigator, ...) {
accountDetailsButton.onClick (e -> navigator.goToAccountDetails (account));

public class ConnectedStateNavigator {
public ConnectedStateNavigator (ConnectedStateViewFactory viewFactory, ...) {...}

public void goToAccountDetails (Account account) {
viewChanger.changeView (viewFactory.createAccountDetailsView (account));

public class ConnectedStateViewFactory {
public ConnectedStateViewFactory (ConnectedStateNavigator navigator, ...) {...}

public View createAccountsOverviewView () {
return new AccountsOverviewView (new AccountsOverviewViewModel (navigator, ...));

public View createAccountDetailsView (Account account) {...}

How could I do that better to avoid this cyclical reference?
Is the use of a setter or an asynchronous event system the only solution?

Permissions – Custom Navigation bypasses SharePoint Group and uses AD Groups

I have a custom SharePoint 2016 on Prem navigation with links that only certain people can see. I'm currently using an SP group and updating it manually when a new employee is hired with their AD account. I want to bypass the SP group and use AD groups so I do not have to update manually anymore. Hope that makes sense. Below is my code for reading from the SP group.

var allowedGroups = [“IT”];
var isInAllowedGroup = false;

var userid = _spPageContextInfo.userId;
var requestUri = _spPageContextInfo.webAbsoluteUrl + & # 39; / _api / web / CurrentUser / Groups? $ select = Id, Title & # 39 ;;

// alert (requestUri);
var requestHeaders = {"accept": "application / json; odata = verbose"};
$ .ajax ({
URL: requestUri,
contentType: "application / json; odata = verbose",
Header: requestHeaders,
Success: onSuccess,
Error: onError

Function onSuccess (data, request) {
var s = & # 39; & # 39 ;;
for (var i = 0; i <data.d.results.length; i ++)
s + = data.d.results[i]Title + # 39; & # 39 ;;

var groupName = data.d.results[i].Title;
if (allowedGroups.indexOf (groupName)> -1)
isInAllowedGroup = true;

if (isInAllowedGroup) {
$ ("# IT"). Css (& # 39; display & # 39 ;, block & # 39;);


Function onError (error) {
( "Error");


Thanks in advance.

navigation – How does the information architecture of a UGC-based website / app work?

This question is difficult to answer without additional information about the purpose or what you / the user wants to achieve.

But if we use Twitter or Instagram as an example of user-generated content, hashtags are nothing more than labels. This is a known and flexible system.

If the categories / labels are predefined, I would suggest making suggestions for the generated content. Suggestions may be based on the text the user has written or the user is searching for tags and receiving synonym or suggestion labels based on the search term.

navigation – What is a user-friendly way to exit a preview screen?

I have a mobile Android application that allows users to set the layout of the on-screen items through a form. The user can also preview the custom layout in full screen mode. However, the use of the back key (soft key) is not available, and a navigation header provides more clutter. Is there a clean, intuitive approach to responding to user input to finish the preview?

I thought about adding a button Tap to exit Approach. A button is not very desirable because it adds clutter. In addition, it can be assumed that the button is part of the preview. Allows the user Tap to exit is fine, but I find the approach vulnerable to accidental touch and not immediately intuitive for a user. Responding to multiple touches in a given time frame is not a terrible approach. double-tap.

SharePoint 2019 – Link to Top Bat Navigation

Forgive my english, as it is not my native language.

I'm absolutely new to sharepoint. Today I have SharePoint 2019 installed on Windows Server 2019. The first root site was created. An alternate access mapping for the site has been created. And that's it. If I remember correctly, I did not make any changes.

At the moment there are some problems.

Error 1:

Image 1

Blue logo

If I click on the big SharePoint logo as in picture 1, I go to the start page. It's good.

Picture 2

The link refers to the local source

If I click on the SharePoint text that is next to the 9 dots, I will be redirected to the local source, as you can see in the picture-2 http: // sp / my / _layouts

How can we fix this? Please lead me through the process.

Issue 2:

If I log in locally using http: // sp, credentials will only be requested once. When I try to sign in to the domain, multiple login credentials are requested, for example, more than seven times. I need help solving this problem

The resolution for these will persist for every subsite I create, if so, I can still apply the solution globally.

Thank you for your time.


navigation – Responsive Design – Large number of screens

I am currently working on a very complex web project. The site is huge, over 300 screens. We are redeveloping an existing product so that the familiarity of customers plays a role.

Navigating the old site is so difficult that there is a screen search feature that can bypass site navigation. In my opinion, that just feels like admitting that their navigation is completely broken.

The pages vary from very large forms, pages, wizards, wizards with complex form data and large data tables, and undoubtedly things I have not even seen.

The idea was that this redevelopment would be mobile first. The problem is that the team designed the desktop and recreated the old navigation pretty much.

The question is whether it is feasible at all for such a complex location to be mobile first. Are there guidelines for such a complex navigation?

The site is hard enough to be used on the desktop, just to be desktop-friendly, let alone mobile-friendly, or come by first. I know, personally, I would not even try it on a mobile device.

At some point I have to give some advice on the mobile strategy, and I already see a suite with at least 3 apps. Even creating a native app in a single app would be a challenge that I do not want to accept.

responsive – navigation feedback with multiple hierarchy levels

I design a responsive website with 3 hierarchical levels. I wanted to get some feedback and feedback on the following navigation.Enter image description here

Level 1 contains a list of body systems, eg. B.: Cardiovascular
Level 2 contains the type of view, eg. B.: X-ray, standard
Stage 3 contains a list of organs, eg ventricles
Level 4 is the detail page.