Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

Navigation 2.0

From MoodleDocs
Revision as of 07:40, 21 January 2009 by Martin Dougiamas (talk | contribs) (New page: ==Goals== Improving navigation in a complex web application like Moodle touches on a lot of areas, but in particular we must aim to hit these goals: ===Clarity=== It should be clearer w...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Goals

Improving navigation in a complex web application like Moodle touches on a lot of areas, but in particular we must aim to hit these goals:

Clarity

It should be clearer what settings affect only yourself, and what settings affect what others see.

It should be clear what is global navigation (whole site), and what is local navigation (within a course or module).

Consistency

All parts of the interface should be consistent. We need to have a set of guidelines and core frameworks to better restrict what developers are allowed to do, while also reworking the core code to implement things like blocks and tabs in consistent ways.

Usability

Users should be able to easily learn what is there for them. Users should be able to move around "their world" within Moodle with a minimum of effort.

Performance

Processing blocks and building up a page with navigation must be very efficient.

Backward compatibility

If possible, plugins should not have to change.

Users should also not find the new interface too different (just better!)

Scope

Blocks

Course view

Pagelib

Use of Templates

Navbar

Jump to Menu

Module tabs+buttons