Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

Standards: Difference between revisions

From MoodleDocs
Themes
(Created page with "{{Themes}} == 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...")
 
No edit summary
 
Line 3: Line 3:
== 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, and the design gets more difficult and tedious.
Moodle developers come from many different backgrounds with different levels of experience. In the past we have tried to define standards for styling components, but this has been implemented inconsistently.  


== Lists ==
As of Moodle 3.2 the recommendation is for all developers to learn how to apply the classes and components from [[Bootstrap]] in order to create the page layouts and components they want to achieve. Custom HTML and styles are strongly discouraged.
 
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 ==
== See also ==

Latest revision as of 07:29, 1 December 2016


Styling standard page elements and parts

Moodle developers come from many different backgrounds with different levels of experience. In the past we have tried to define standards for styling components, but this has been implemented inconsistently.

As of Moodle 3.2 the recommendation is for all developers to learn how to apply the classes and components from Bootstrap in order to create the page layouts and components they want to achieve. Custom HTML and styles are strongly discouraged.

See also

W3C validation

Retrieved from "https://docs.moodle.org/dev/index.php?title=Standards&oldid=51372"
Powered by MediaWiki