Migrate the portal's "Home Site" links into the "top right personal drop down menu"

Description

There is a certain weight of opinion that says the end user should be unaware that the "Home" area (formerly "My Workspace") is actually a site. It is one of a kind and isnt that much like a Course or Project site. 

The ultimate goal could be to remove "Home" from the top "navigation bar" and migrate that button's functionality into what I'm calling "top right personal drop down menu" (TRPDDM). The idea is, I think, to remove the concept of there being a "Home Site" and to emulate what Twitter / ebay / amazon does: there's useful info in the TRPDDM, you click on it and you get to access the functionality - why do you have to know there's a site called Home?

Examples

  !ebay.png|thumbnail!  

The plan is that we add some "high profile" "My Home" links in the TRPDDM, eg, profile, preferences, calendar, maybe one or two others. We probably wouldnt want all My Home functionality although what is and isnt shown could be configurable.

The consensus seemed to be that we may, initially at least, need a 3 way property 

 1 - just show my Home in navigation bar

 2 - show my Home in navigation bar and in "top right personal drop down menu"

 3 - just show "top right personal drop down menu"

If 2 or 3 is selected then the links to show should be ready from a property. A sensible default should be given.

We may ultimately have 3 as the default (or even only) option.

 

 

Attachments

4
  • 17 Jul 2017, 02:00 PM
  • 11 Jul 2017, 09:51 AM
  • 11 Jul 2017, 09:49 AM
  • 11 Jul 2017, 09:48 AM

Activity

Mark Golbeck September 5, 2024 at 6:03 PM

Since it's been over two years without any further information provided, we're closing this Jira issue for now. If more details become available in the future, we can reopen it. Thank you.

Matthew Jones August 7, 2017 at 1:42 PM

I think the biggest issue for us is the Home page is dynamic and easily changed by changing the !user.* and deleting all users workspaces. I think if this was actually implemented it should be just as easily configured dynamically (maybe the same way) rather than hard coded in the template.

Adam Marshall July 18, 2017 at 3:45 AM

indeed, I'm happy to lead the discussion but am not around very much for the next month or so.

Neal Caidin July 17, 2017 at 2:03 PM

This might benefit from a discussion with the UX group, so I've added the "UX" label.

Adam Marshall July 11, 2017 at 9:55 AM

Calendar has already been done.

Won't Fix

Details

Priority

Affects versions

Assignee

Reporter

Labels

Created July 11, 2017 at 9:38 AM
Updated September 5, 2024 at 6:03 PM
Resolved September 5, 2024 at 6:03 PM

Flag notifications