Note: You are currently viewing documentation for Moodle 1.9. Up-to-date documentation for the latest stable version is available here: Standards.

Standards: Difference between revisions

From MoodleDocs
No edit summary
 
(15 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== How to Style Moodle Standard Page Elements and and Page Parts ==
{{Themes}}
Similar functions or similar content should look and feel the same on all Moodle pages. The more consequent these principles are implemented the easer and less hindering the VLE will interfere the working/learning process. The Vision is that Moodle pages build on the same function patterns (PHP and JavaScript) and design patterns (XHTML and CSS).


=== Lists ===
== Styling standard page elements and parts ==
Lists are widely used all over Moodle. They appear in the sideblocks, they are used on the course pages. Many developers currently use lists for navigation as in the SCORM or the CMS module. I regularly use them for navigation lists in HTML blocks. If all lists would use the same XHTML and CSS it would be very easy to design Moodle themes consistent with few changes. Actually all lists are different. The consequences are that the special CSS for every list type lets the Moodle CSS files grow and that theme design gets more difficult and tedious.


I took all following examples from the List-o-Matic Website [http://www.accessify.com/tools-and-wizards/list-o-matic/list-o-matic.asp] for easy reproduction. You find detailed descriptions in the Listutorial
Similar functions or content should look and feel the same on all Moodle pages. The more consistently these principles are implemented, the easier the learning environment will be to use. The vision is that Moodle pages build on the same function patterns (PHP and JavaScript) and content patterns (XHTML) and design patterns (CSS). Otherwise, if each module or block requires particular code, then the Moodle files and CSS grow, and the design gets more difficult and tedious.
[http://css.maxdesign.com.au/listutorial/index.htm].


==== Resources about Lists on the Web ====
== Lists ==
<nowiki>[1]</nowiki>
[http://www.accessify.com/tools-and-wizards/list-o-matic/list-o-matic.asp List-o-Matic]<br />


<nowiki>[2]</nowiki> [http://css.maxdesign.com.au/listutorial/index.htm Listutorial]<br />
Lists are widely used in Moodle, including in sideblocks and on course pages. Many Moodle developers use the up-to-date combination of unordered lists and CSS styling for navigation, for example the SCORM module. If all lists use the same XHTML and CSS it is easy to design Moodle themes consistently and with few changes. Actually all lists are different.
 
; External links
*[http://www.accessify.com/tools-and-wizards/developer-tools/list-o-matic/ List-o-Matic]
*[http://css.maxdesign.com.au/listutorial/index.htm Listutorial] - descriptions about XHTML/CSS lists
*[http://www.moronicbajebus.com/playground/cssplay/explorer-list/ Styling nested lists]
 
== See also ==
 
[[W3C validation]]
 
[[Category:Administrator]]
[[Category:Developer]]
[[Category:Themes]]
 
[[ja:スタンダード]]
[[de:Design-Standards]]

Latest revision as of 09:32, 24 June 2010



Styling standard page elements and parts

Similar functions or content should look and feel the same on all Moodle pages. The more consistently these principles are implemented, the easier the learning environment will be to use. The vision is that Moodle pages build on the same function patterns (PHP and JavaScript) and content patterns (XHTML) and design patterns (CSS). Otherwise, if each module or block requires particular code, then the Moodle files and CSS grow, and the design gets more difficult and tedious.

Lists

Lists are widely used in Moodle, including in sideblocks and on course pages. Many Moodle developers use the up-to-date combination of unordered lists and CSS styling for navigation, for example the SCORM module. If all lists use the same XHTML and CSS it is easy to design Moodle themes consistently and with few changes. Actually all lists are different.

External links

See also

W3C validation