No subject

work out labels for all common page types and set them as *.KDE.org specs. 
This way we would be treating the navigation in a more global manner, but 
still leave enough freedom for it's own specific pages. If a site doesn't 
offer a top level feature, leave it away. For instance, if a site doesn't 
offer any downloads, then the "Download" link ist dropped on that site.
On KDE.org "Download" would lead you to download.kde.org and on kooka.kde.org 
"Download" would lead to the Kooka download page. 

> I think it would work much better if kde.org was treated seperately from
> the *.kde.org subdomains as each subdomain has it's own requirements for
> content. Sure we could probably use n levels of abstraction to classify the
> existing menu entries into the global ones, but that has more disadvantages
> then advantages IMHO.

Like?

> I like the idea of having the high level categories for kde.org and using
> sperate pages to flesh out the links giving us opportunity to give a little
> detail about the links and leaving the main page uncluttered and easy to
> navigate. Although I think the *.kde.org sites should be allowed their own
> menu structure as you can't really use the same structure for sites as
> diverse as accessibility, printing, women, usability, multimedia and
> development just to name a few.

Sure! If you abstract it enough you can. Show me a site that would not work 
with the labels I mentioned above. I checked the sites you mentioned. From 
what I saw at a glance it would work fine. 
-- 
Bye,
Mat