@T-Systems-MMS/phonebook-developers

Which position of this option field would you prefer? If we use the first option, it would mean that both your Team and your Bookmarks are ordered in the same way because there is only one field.

In the second version the option field changes when you move between Team and Bookmarks.

Side note: If I use the first option I could make the recent people and the cards for the bookmarks/team start at the same height.

I dislike both versions. Mainly because of the following points:

1. The user has no clear interaction points. Meaning: He can't detect that both headings are clickable and change something
2. The positioning of the "Ordering" switch in both cases makes no sense as it is perceived as being able to change the order of both Menus but only changes the one of the bookmarks

I have drawn a mockup that hopefully solves both problems:

Ok, I can do it this as well. Another idea I had was to mark the menu that is open similarly to issue #523 . That obviously would not solve the problem with the "Ordering" switch.

If everybody prefers @DanielHabenicht, I'll do it that way.

Currently looking like this:

I would like to prefer a dropdown here:

That will help us later to implement more views. But I must also say that the Button My Team
at the bottom is looking really good. I'm not really sure.

The problem is that the shown option only allows us these two views. We can't add a third one.

Maybe this is a solution for the problem:

But this option also not endless and not searchable.

Why should there be multiple views?
I would not want to crowd the dashboard with views. If we add another one there should be a different solution.

But let's not forget that this issue was only about having a default view in the dashboard...

@T-Systems-MMS/phonebook-developers Would you prefer the team-component to be completely gone when the is no user who is logged in or would it be better to simply say 'You aren't logged in yet. Log in in order to see your team.'?

Gone

@T-Systems-MMS/phonebook-developers Should the user get to the team/bookmarked people with urls? Then, there would be extra routes. Otherwise, it could all just be on the dashboard itself.

Also ich hab paul mal gefragt er ist auch für ein Routing
D.h. also alle Anfragen die auf / ankommen sollten auf /dashboard/bookmarks oder /dashboard/team umgeleitet werden
@friedaxvictoria

@DanielHabenicht Soll das dann über ein extra routing gehen oder kann ich das so machen, wie es bis jetzt war (im app-routing.ts)?