Urs Hunkler

Following several requests and proposals here in the forum I have created the "Master Issue: Moodle page optimization" MDL-10665 in the Moodle Tracker as a collection place:

Collection of proposals how to optimize Moodle page structures of the courses, modules, resources and so on. The goal is to get every Moodle page XHTML 1.0 strict compliant and to assure a consistent CSS hook structure. Moodle Themes will become much smaller and easier to create and more flexible.

Please add your issues as single "Themes" related issues in the Tracker and link them to this "Master Issue". Thank you very much for your contributions.

Those contributors confident with XHTML, CSS, PHP and the Moodle code may consider to add proposals or patches to solve the issue.

Urs

PS: Please understand that your contributions are all welcome and very helpful but that there can't be any guarantee that your proposal may make it's way into the Moodle code.

Peter,

thank you very much for your helpful detailed information about areas in Moodle with optimization possibilities. If you don't mind you may add your findings to the Moodle tracker under Themes. There they never will get lost . You may link your contribution to the issue http://tracker.moodle.org/browse/MDL-10665

Hi Patrick,

thank you for your contribution. Great idea - an additional body class would help a lot. By the way - you do not list the properties for the chat window.

After a short check in the source code for those popup windows I can say, that there is no easy and fast solution. They are build differently.

Can you please add an issue in the Moodle tracker that your idea doesn't get lost. I may have some time later to create a solution.

A short link to my topic Article "The Market Maturity Framework is Still Important" in the developer forum - the topic is quite fundamental for theme work.

This morning I read the short article The Market Maturity Framework is Still Important and got some understanding how Moodle may evolve.

Jared Spool analysed that development stages mostly can be described with a simple four-stage progression:

• Stage I is Technology
• Stage II is Features
• Stage III is Experience
• Stage IV is Integration

I see Moodle as a relatively young and very successful program in Stage II - features. I work mostly in the area of experience and really don't understand why features are more important than experience. Features may be good for the product - experience is important for people.

Following the framework I would pinpoint Moodle to be proceeding towards the end of the features stage II. I at least hope so. Moodle version 2.0 might be a nice signal like "We are mostly complete now." and in a casual coincidence with the framework manifest the closure of stage II.

So it's time to prepare for the third stage - Experience. When I am not wrong stage III is waiting before the doors. All efforts to prepare a focus change towards the Moodle user experience will be well invested. (I'll repeat this insight to be able to stand the "torture" of the hopefully dieing away Moodle features stage

My activities will focus on base work for the Moodle experience area now.