Standards: Difference between revisions
Helen Foster (talk | contribs) m (Themes standards moved to Standards) |
Helen Foster (talk | contribs) (see also) |
||
| Line 1: | Line 1: | ||
== Styling standard page elements and parts == | == 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, the design gets more difficult and tedious. | 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 == | ||
| Line 7: | Line 7: | ||
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. | 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/list-o-matic/list-o-matic.asp List-o-Matic] | *[http://www.accessify.com/tools-and-wizards/list-o-matic/list-o-matic.asp List-o-Matic] | ||
*[http://css.maxdesign.com.au/listutorial/index.htm Listutorial] - descriptions about XHTML/CSS lists | *[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] | *[http://www.moronicbajebus.com/playground/cssplay/explorer-list/ Styling nested lists] | ||
== See also == | |||
[[W3C validation]] | |||
[[Category:Administrator]] | [[Category:Administrator]] | ||
[[Category:Developer]] | [[Category:Developer]] | ||
[[Category:Themes]] | [[Category:Themes]] | ||
Revision as of 12:40, 5 December 2005
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
- List-o-Matic
- Listutorial - descriptions about XHTML/CSS lists
- Styling nested lists
