I hope that this doesn't sound too negative. I basically would like to give a short critique of Moodle and offer some possible solutions. I recognize that Moodle.org doesn't have an visual interface designer working for them. I recognize that the priority has been to get programming and functionality in place with mind for a future evolution to improve how they look and work. As well, I recognize that Moodle is rather a gift to humanity right now, allowing many institutions that could not afford WebCT vista to offer online courses. However, visual design needs to be considered early as part of the workflow in order to properly be implemented and to build a basic design "intelligence" into the software interface.
I hope that they are getting tired of hearing people complain about how Moodle looks and are ready for it to evolve into a more professionally presented package. Good visual design will ennoble all of the good open source programming work that has gone into Moodle. In many ways, I wish I was more of a programmer so that I could offer better back-end solutions.
It would be great if we were able to affect Moodle and make it as attractive and usable as a site like this. http://www.bbc.co.uk/radio4/ Hey, when you compare a lot of sites to Moodle it really must be obvious that it should look better.
Visual design tends to be like a lens that people look through. They don't often don't notice the lens but just see the object of their gaze in a sharper way. I find I usually have to take off the glasses and explain how they are working for people so that we can all speak the same visual language.
PART 1
I think one of the big challenges with doing visual design for Moodle is that designers are rather hamstung in their ability to do their job. Yes everything can be affected from the back-end of Moodle but is better to have trained programmers with a system view coding the PHP so that it is properly done and will not create problems in the future. Besides, it's rather a waste of work to go in an opposite direction than upstream Moodle development. It all needs to be redone with an upgrade and a whole new set of conflicts creep in.
I'll give a brief critique of Moodle and visual design so that you know what we'd like to do. Four basic principles of visual design are contrast, repetition, alignment, and proximity. The big thing that results from using these principles is flow. They eye and the mind flow through the information pleasantly and effortlessly. Just like the Ying-yang logo, white space needs to be considered as an active element and shape as opposed to a space that is empty. Whitespace is a powerful tool for applying these four principles.
1. Contrast is used to set up hierarchies for importance and helping direct the eye around the page. Right now Moodle has very poor contrast, it's mostly text links with icons that are all the same size. What that means is people have to keep reading and rereading to know what to do. There are ways that designers can help. Different images, buttons, and ways of presenting interactivity can use people's visual memory to quickly communicate a function (and make a more visually interesting and engaging page).
2. Repetition is basically consistency. Like elements and functions are grouped and presented in a consistent way which reinforces a positive user experience. Tabs are a type of repetition in websites. It also related to thematic elements which get repeated to create a consistent environment. Curved corners on boxes are a type of repetition.
3. Alignment is a way of grouping like-information together and creating flow. It does relate to readability. One simple example is that people in the West are used to reading from left to right. Hence aligning text to the left is easier to read because it's easier for the eye to find the start of each line. Moodle has lots of alignment problems once you get off the front pages of courses and with modules.
4. Proximity is a really important one that is often forgotten. Basically, a mark on a blank page that is off center will have a magnetism for the side that it is closest to. Two marks on a page have a visual magnetism for each other and that visual magnetism increases as the marks move closer to each other. This is the principle use between the fingers of God and Adam in Michelangelo's sistine ceiling. The little space between the fingers creates electricity. How does this relate to Moodle? There are lots of proximity problems, especially with the displays of tables. There are many points of tension that inappropriately draw the eye. Proximity can be used well to help the eye flow through the page or it can keep fighting against it. Alfresco uses proximity well. It's a basic design intelligence that should be built into the base Moodle system. Proper use of whitespace and considered proportions is a key to using proximity well.
PART 2
Most of the web designers I know have a very good knowledge of HTML and CSS but usually have a passable knowledge of PHP, Javascript, XML, XSLT...but programmers are really trained differently than visual designers and it's unusual to have a lot of masters of both worlds.
Enable designers to do their work with javascript, CSS, and HTML directly in the browser rather than having to go through the server side. This will allow greater flexibility, iterative design, and separate visual designers from the programmer's workflow. Separate presentation from content, right? I'm not talking about removing what's capable now with the theme folder, this would be an additional customization element.
1. Just how in Moodle 2.0 you are planning to enable people to add images from Flickr or Google docs through a web interface, allow people to link to CSS and Javascript through their web browser. If you're moving towards Moodle and Alfresco integration the CSS and Javascript can reside in Alfresco and be imported into the Moodle file system as needed.
2. Allow designers to wrap their own tags around the content of blocks. We can add div tags that will allow us to add background images and transform links into buttons. Does a link to a Moodle book always have to be a text link with a little icon to the left? Why could it not be a small image that shows what the content of the book will be? Give me a big open block and I can design my own columns for course content.
3. CSS can be made specific so that it does not affect the HTML of Moodle itself, for example:
(css)
#mystuff h1 {font-size: 1.8em}
(html)
<div id="mystuff">
<h1>A title that's mystuff size</h1>
</div>
But, is there a better way to do this?
Thanks for considering this,
Ian