Urs Hunkler

May be different approach for administrational pages and content pages can benefit. Admin pages may work and look very different from content pages as in many CMS systems.

Oli what differences do you see between web sites and Moodle when looking at the pages Moodle users work with?

And is the Yahoo web catalog or Amazon a web site or a web app? Or is an ecommerce site a web app or a web site?

For me Moodle is an application using web pages for the interface. So all web site interface aspects are valid for Moodle.

Moodle doesn't work with typical web app interface concepts like "Stay on the Page" as a chapter in Designing Web Interfaces, 1st Edition is called, which do more clearly distinguish web app interfaces from web site pages.

May be finding a consensus for the question if the Moodle interface needs to be a web app interface or can work with web site pages is one good starting point for the Navigation 2.0 discussion.

As I see it Moodle has a web page based interface and I think that is ok.

Drop-Down menus seam to be widely discussed in the moment: Designing Drop-Down Menus: Examples and Best Practices by Smashing Magazine.

It's always good to have a broad and well considered base of information when we are going to work on proposals for Navigation 2.0 for Moodle.

A List Apart published an interesting article yesterday. In The Elegance of Imperfection David Sherwin writes about "Wabi-sabi and making websites".

He writes: "Leonard Koren, in his book Wabi-Sabi for Artists, Designers, Poets & Philosophers, describes the following material qualities of wabi-sabi: asymmetry, asperity, simplicity, modesty, intimacy, and the suggestion of a natural process."

I recommend to closely look at and understand those qualities when discussing Navigation 2.0 for Moodle.

Jakob Nielsen has an interesting article about Mega Drop-Down Navigation Menus Work Well in "Alertbox".

Seams to be worth to consider to use "Mega Drop-Down Navifgation Menus" for Moodle.