I agree this need fixing, but it's not clear (to me at least) how it should work.
For me, these are desired features (actually constraints, in this case):
- User-centered Web 2.0 approach (Home can usually be My Home)
- Consistent paths between navbar and navigation tree
Currently the tree looks like this when logged in, call it version A:
My home
- Site home
- - Blogs
- - Front page activity
- My profile
- My courses
- - Course 1
- - Course 2
- etc
Navbar for site stuff: My home > Site home > Blogs
Navbar for course activity: My home > My courses > Course name > etc
Alternative version B:
Site home
- Blogs
- Front page activity
- My home
- My profile
- My courses
- - Course 1
- - Course 2
- etc
Navbar for site stuff: Site home > Blogs
Navbar for course activity: Site home > My courses > Course name > etc
My home is never seen on the navbar with this idea ...
Alternative version C:
Site home
- Blogs
- Front page activity
- My home
- - My profile
- - My courses
- - - Course 1
- - - Course 2
Navbar for site stuff: Site home > Blogs
Navbar for course activity: Site home > My home > My courses > Course 1 > etc
My home and site home are now visible most of the time in the navbar, but My home disappears when looking at site things, and also the Navigation is now really indented, causing space issues in the block. Also the list of Blogs etc can get rather long, and can't be folded away in the nav block.
Alternative D:
Merge My home into the Site home (with perhaps tabs to choose between them?), so then:
Home
- Site information
- - Blogs
- - Front page activity
- My profile
- My courses
- - Course 1
- - Course 2
- etc
This would mean the frontpage itself could truly be customised by users, even more like facebook.com. The only trouble would be how to make sure the "site" page is still accessible when required, and how that would look.
Alternative E: What's your suggestion?
Could really use your input and thoughts about all this!!