Bug 3384 - Rethinking the global navigation bar
Summary: Rethinking the global navigation bar
Status: RESOLVED FIXED
Alias: None
Product: Websites
Classification: Unclassified
Component: All (show other bugs)
Version: trunk
Hardware: i586 Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Romain d'Alverny
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 2997
  Show dependency treegraph
 
Reported: 2011-11-18 20:53 CET by Romain d'Alverny
Modified: 2012-05-24 23:04 CEST (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:


Attachments
diff of screenshot (202.71 KB, image/png)
2012-05-14 19:58 CEST, Manuel Hiebel
Details

Description Romain d'Alverny 2011-11-18 20:53:17 CET
Description of problem:
We have a global navigation bar for mageia.org domain. Its goal is, with a consistent design charter, to help visitors/users to direct themselves through the whole domain.

In its current form, it provide a permanent set of links to several categories/apps. However it could be made better/different:
 - linking to specific subapps (current form)
 - linking to spaces (somehow as mandriva.com or apple.com do)
 - linking to a single home site through a single badge (see mozilla.org several sites), leaving each local domain/zone/app to its own sub-navigation scheme
 - something else.

This bug is open to discuss (with actual mockups) a redesign of this nav bar for 2012.

 - if using text, the nav bar should be translatable and take into account the current locale of the website;
 - the navbar should accomodate being used in a fixed, fluid, dynamic, whatever layouts;
 - it must not consist of too many items
 - it should accomodate touch devices (not too large, but large enough action items)
Comment 1 Romain d'Alverny 2012-05-14 19:11:49 CEST
A sample candidate has been made available.

See it tested (temporary URL) at http://www.mageia.org/en/about/?testnav=1

Documentation about its use is available: http://www.mageia.org/_nav/ (see code in http://svnweb.mageia.org/web/www/trunk/_nav/

Status: NEW => ASSIGNED
Assignee: mageia-webteam => rdalverny

Romain d'Alverny 2012-05-14 19:12:21 CEST

Blocks: (none) => 2997

Comment 2 Manuel Hiebel 2012-05-14 19:23:56 CEST
the title is with http://www.mageia.org/en/2/?testnav=1 in a webkit browser (epiphany in mga1) is not in blue, and with firefox it seems a bit to big.

otherwise it looks nice :)
Comment 3 Romain d'Alverny 2012-05-14 19:40:47 CEST
(In reply to comment #2)
> the title is with http://www.mageia.org/en/2/?testnav=1 in a webkit browser
> (epiphany in mga1) is not in blue,

What webkit release is epiphany based on? It means it doesn't render this set of rules:

    background: #2383C2;
    background: -webkit-linear-gradient(top, #3494D3 0%, #2383C2 50%);
    background: -moz-linear-gradient(top, #3494D3 0%, #2383C2 50%);
    background: -o-linear-gradient(top, #3494D3 0%, #2383C2 50%);
    background: linear-gradient(top, #3494D3 0%, #2383C2 50%);

and I'm not sure why.

> and with firefox it seems a bit to big.

Would you mind a screenshot? I can't reproduce a very different title here. :-p Thanks!
Comment 4 Manuel Hiebel 2012-05-14 19:58:49 CEST
Created attachment 2314 [details]
diff of screenshot

>What webkit release is epiphany based on? 

I don't know but I can confirm with midori, and it works with chromium-browser 18.

In fact its the two banners (title and usual) with is to big to me :)
Comment 5 Romain d'Alverny 2012-05-14 20:03:57 CEST
Ha, right, but in the second screenshot, check the URL; you need the ?testnav=1 query string to see the new navbar candidate. :-p
Comment 6 Manuel Hiebel 2012-05-14 20:07:47 CEST
(In reply to comment #5)
> Ha, right, but in the second screenshot, check the URL; you need the ?testnav=1
> query string to see the new navbar candidate. :-p

It was only to show the same page in the same browser.

For webkit it seems fixed with http://svnweb.mageia.org/web/www/trunk/_nav/css/source.css?r1=1066&r2=1087, thanks
Comment 7 Romain d'Alverny 2012-05-24 23:04:07 CEST
Released in production, propagation to other sites coming in the next days.

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.