Opened 12 years ago
Last modified 12 years ago
#102 closed defect (FIXED)
Top menu / navigation layout
|Reported by:||Jef van Schendel||Owned by:||Jef van Schendel|
We should think about what we want to show in the top right of our pages. **Currently, when a user is logged in, we've got:** [user]'s account home gallery (logout) This is getting crowded! :) **I propose we do this:** - Use [user] as the "home" link, which links to the user's profile page. - Remove the "gallery" link. If the user wants to see his or her own gallery, that can be done by going to the profile page, then clicking "all images" or something similar. **This leaves:** - The "logout" link. At first I also wanted to move this to the profile page, but cwebber pointed out it might be better to keep in the top right. While it may not be an action that is frequently used, it can be of high importance for security. Also, the placing right next to "[user]'s account" makes a lot of sense, I think. - An "upload" button/link. We don't have this yet, but the top right might be a good idea. Similar to for instance YouTube, who have a big bright yellow upload button always at the top. It makes sense, because submitting media is presumably what Mediagoblin is used for. :) Other websites, like for instance Wordpress or Gmail, have a dropdown menu, where you can view info or logout. It's one way to do it, but personally I'm not a big fan. It's hard to make clear graphically that it's a dropdown menu instead of a regular link, they don't always work well on mobile devices and it makes the code more complex.
Change History (4)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
I think all of these changes have been made. We've now got a "Submit media" button in the top left, next to the MediaGoblin logo. There's still discussion over the "Submit" text at `http://bugs.foocorp.net/issues/466 <http://bugs.foocorp.net/issues/466>`_ .
comment:3 by , 12 years ago
|Component:||→ Graphic Design / UI|
|Status:||New → Closed|
comment:3 by , 11 years ago
The original url for this bug was http://bugs.foocorp.net/issues/389 .
Note: See TracTickets for help on using tickets.