Merge lp://staging/~ronnie.vd.c/ubuntu-website/top-nav into lp://staging/~ubuntu-website-community/ubuntu-website/light-base-theme

The top-nav should use a better, *more* semantic code.

KuZeKo, what do you mean by "*more* semantic code"

Without all those "span"s , using a "nav" or a "ul>li>a" etc.

Changed the span elements to more descriptive HTML tags

Far better. :-)

consider using <span class="{something}">|</span> and converting the top-nav in aside

Is this a fix for a bug or something? Afaik the loco theme/websites do not necessary require the top navigation bar. It was introduced on planet, and imho there it should stay: on third party loco services, not on loco webpages.

Reasons:
1. It will confuse people. http://ubuntu.ro/ has a planet, a news page and a launchpad project, by placing the introduced by you navigation bar, how do I help user to make the correct decision which link he should follow?
2. It is useless on most of the loco websites, since not everyone has a wiki/planet/news page, and they usually have a "placeholder" that redirects visitors anyway to ubuntu.com
3. I don't see why I need a login/logout link above my main menu.

I wouldn't merge this into WordPress theme, since I don't see how it can help end-users, and as a result, I will not support this merge into base theme. But, I encourage you to write a patch to the themes for planet/forum, where it makes sense to have a top bar like that.

There is al least one bug in website-content for it https://bugs.launchpad.net/ubuntu-website-content/+bug/680814. The request came from loco.ubuntu.com, but why not share the code with the whole community. Its like all the other code in the base-theme: use it when you need it, leave it out when you dont need.

I can imagine there are loco's who would also like to have a top bar. So why not include it in the base-theme. Also, each loco/website can decide which links they place in the top-nav, as long the top-nav is consistent on the whole domain.

Also the login is optional, it is possible to place the login on other parts of the webpage, the base-theme does not force you to have it in the top-left corner. But if the domain has a lot of different apps, then i think its good to have to login button on the same place each page (single sign-on should be awsome, but thats usually too much work for a loco)
NOTE: a user can be confused when he/she is logged-in at one app, but needs to login on the other.

[ Quote Stas Sușcov ]
> Is this a fix for a bug or something? Afaik the loco theme/websites do not
> necessary require the top navigation bar. It was introduced on planet, and
> imho there it should stay: on third party loco services, not on loco webpages.

As they say "Melius abundare quam deficere", if we can have this as an optional element, go for it. There are already a couple of "optional" elements in this theme.

It was my understanding that light-base-theme was there to provide a common way of implementing any particular design feature. As long as there is more than one site that might want this, it should be in there so that we're not duplicating effort or, worse, making it different on every site.

I will be merging this into light-django-theme, and hope that it is merged into the others as well.

Links were realtive, ill made them absolute by adding http://