Development:Navigation 2.0: Difference between revisions
(→Scope) |
(→Scope) |
||
Line 36: | Line 36: | ||
===Course view=== | ===Course view=== | ||
===Pagelib=== | ===Pagelib=== | ||
=== | ===How HTML is generated=== | ||
===Navbar=== | ===Navbar=== | ||
===Jump to | ===Jump to menu=== | ||
===Module tabs | ===Module tabs and buttons=== |
Revision as of 05:13, 30 January 2009
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
What parts of Moodle might be affected by this work?