That's really excellent, thanks Amy. I agree that having sensible page level structure guidelines would be a good addition and would help with the overall aim of consistency across the interface.
Also related are issues like all the classes in custom menu.
Simon
I've pushed an updated version that should fix those issues.
Simon
Ah table.invisible and a.link-as-button are both totara-specific classes that I must have missed when I was removing totara-specific code. I'll have another look through and remove anything else I missed. Thanks for spotting the other bugs, I'll fix them at the same time.
Simon
At the recent hackfest in Perth there was an interesting discussion on responsive design and how it could potentially be added to moodle's core themes. One of the difficulties is that there is a lack on consistency in how UI elements are created in Moodle, which makes it really hard for theme designers to ensure that all pages across the site are correctly styled. This lack of UI consistency also has an impact on overall usability.
In order to try to tackle this problem in our distribution of Moodle (called Totara) we've developed an "Element library" which we distribute with the code. It provides a set of linked pages with examples of common UI elements. It provides theme designers with a single place to go to check their themes and developers with commented examples, so they can see the best way to implement a particular UI element.
I demoed what we have at the hackfest and there was interest in integrating it into core Moodle, so I've created a bug and shared the code here:
http://tracker.moodle.org/browse/MDL-36558
https://github.com/totara/moodle/tree/mdl-feature-element-library
If you're a theme designer or UI guru and you've got any interest in this concept, or you've got some ideas on how you'd like it to develop, or some time to help identify common UI elements to improve the library, I'd love to hear from you!
Simon
Yeah, good point. I'll re-run it with a lot more and see how that impacts things.
Simon