Development:XHTML - Revision history

Tsala: category edit

2009-11-26T17:36:38Z

category edit

← Older revision		Revision as of 17:36, 26 November 2009
Line 50:		Line 50:
	* [[Development:Coding\|Other Moodle coding guidelines]]		* [[Development:Coding\|Other Moodle coding guidelines]]

	[[Category:Coding guidelines]]		[[Category:Coding guidelines\|XHTML]]

2009-11-26T17:28:50Z

← Older revision		Revision as of 17:28, 26 November 2009
Line 50:		Line 50:
	* [[Development:Coding\|Other Moodle coding guidelines]]		* [[Development:Coding\|Other Moodle coding guidelines]]

	~~{{CategoryDeveloper}}~~		[[Category:Coding guidelines]]

2009-11-13T10:41:25Z

@@ Line 1: / Line 1: @@
 ==XHTML Strict 1.0==
@@ Line 31: / Line 33: @@
 * As you change core Moodle code, you must update the standard theme so that Moodle looks OK out of the box.
 * If you need to make basic style definitions for a module (or some other sorts of plugin), put them in a file called styles.php in that module. This will be included into every theme.
 == Moodle API ==
@@ Line 40: / Line 48: @@
 * [http://developer.apple.com/internet/webcontent/bestwebdev.html Web Page Development: Best Practices] by the Safari development team at Apple.

2009-09-24T07:55:34Z

missing words added

← Older revision		Revision as of 07:55, 24 September 2009
Line 27:		Line 27:
	How the HTML is laid out should be controlled by CSS in whichever theme is currently selected.		How the HTML is laid out should be controlled by CSS in whichever theme is currently selected.

	* Ensure that the HTML contains enough id="..." and class="..." attributes so that theme designers can easily control how		* Ensure that the HTML contains enough id="..." and class="..." attributes so that theme designers can easily control how it is displayed.
	* Never embed inline styles in the HTML (that is, do not use the style="..." attribute).		* Never embed inline styles in the HTML (that is, do not use the style="..." attribute).
	* As you change core Moodle code, you must update the standard theme so that Moodle looks OK out of the box.		* As you change core Moodle code, you must update the standard theme so that Moodle looks OK out of the box.

2009-09-24T07:53:26Z

missing word added

← Older revision		Revision as of 07:53, 24 September 2009
Line 20:		Line 20:
	* tables should not be used for page layout, just to display tabular information,		* tables should not be used for page layout, just to display tabular information,
	* if something is a heading, it should be marked up using <h''n''> tags, for an appropriate ''n'',		* if something is a heading, it should be marked up using <h''n''> tags, for an appropriate ''n'',
	* <nowiki>if something is a list, it should marked up using <ol>, <ul> or <dl>,</nowiki>		* <nowiki>if something is a list, it should be marked up using <ol>, <ul> or <dl>,</nowiki>
	* see [[Semantic HTML]] for further details		* see [[Semantic HTML]] for further details

2009-08-26T10:19:54Z

← Older revision		Revision as of 10:19, 26 August 2009
Line 5:		Line 5:
	===Well-formed XML===		===Well-formed XML===

	In a well-formed XML document, every opening tag has a matching close tag; tags are properly nested attributes are properly quoted, and the file contains no syntax errors. See [http://www.w3.org/TR/xml/#sec-well-formed the XML specification for a formal definition].		In a well-formed XML document, every opening tag has a matching close tag; tags are properly nested, attributes are properly quoted, and the file contains no syntax errors. See [http://www.w3.org/TR/xml/#sec-well-formed the XML specification for a formal definition].

	While developing, you should have the option Administration ► Server ► Debugging ► XML strict headers turned on. With this option on, your web browser will refuse to display any page that is not well-formed. This makes such problems easy to find and fix.		While developing, you should have the option Administration ► Server ► Debugging ► XML strict headers turned on. With this option on, your web browser will refuse to display any page that is not well-formed. This makes such problems easy to find and fix.

2009-06-11T13:18:05Z

2009-06-11T13:17:40Z

2009-06-09T06:42:46Z

Semantic markup

← Older revision		Revision as of 06:42, 9 June 2009
Line 21:		Line 21:
	* if something is a heading, it should be marked up using <h''n''> tags, for an appropriate ''n'',		* if something is a heading, it should be marked up using <h''n''> tags, for an appropriate ''n'',
	* <nowiki>if something is a list, it should marked up using <ol>, <ul> or <dl>,</nowiki>		* <nowiki>if something is a list, it should marked up using <ol>, <ul> or <dl>,</nowiki>
	* ~~and so on.~~		* see [[Semantic HTML]] for further details

	==Styling==		==Styling==

2009-06-09T06:19:45Z

Styling

← Older revision		Revision as of 06:19, 9 June 2009
Line 25:		Line 25:
	==Styling==		==Styling==

	* ~~Make sure you provide~~ enough ~~CSS ids~~ and ~~classes to enable a designer to modify everything with CSS~~.		How the HTML is laid out should be controlled by CSS in whichever theme is currently selected.
	* Never ~~use~~ inline styles
	* If you need to make basic style definitions for a module, put them in a file called styles.php in that module. This will be included into every theme.		* Ensure that the HTML contains enough id="..." and class="..." attributes so that theme designers can easily control how
			* Never embed inline styles in the HTML (that is, do not use the style="..." attribute).
			* As you change core Moodle code, you must update the standard theme so that Moodle looks OK out of the box.
			* If you need to make basic style definitions for a module (or some other sorts of plugin), put them in a file called styles.php in that module. This will be included into every theme.

	==Moodle API==		==Moodle API==

← Older revision		Revision as of 13:18, 11 June 2009
Line 39:		Line 39:
	== See also: ==		== See also: ==

	* [[http://developer.apple.com/internet/webcontent/bestwebdev.html Web Page Development: Best Practices] by the Safari development team at Apple.		* [http://developer.apple.com/internet/webcontent/bestwebdev.html Web Page Development: Best Practices] by the Safari development team at Apple.

← Older revision		Revision as of 13:17, 11 June 2009
Line 32:		Line 32:
	* If you need to make basic style definitions for a module (or some other sorts of plugin), put them in a file called styles.php in that module. This will be included into every theme.		* If you need to make basic style definitions for a module (or some other sorts of plugin), put them in a file called styles.php in that module. This will be included into every theme.

	==Moodle API==		== Moodle API ==

	* Use the functions in lib/weblib to do as much as possible (print_header(), print_box() etc)		* Use the functions in lib/weblib to do as much as possible (print_header(), print_box() etc)
	* This API will change a lot in Moodle 2.0. See: [[Development:Navigation_2.0]]		* This API will change a lot in Moodle 2.0. See: [[Development:Navigation_2.0]]

			== See also: ==

			* [[http://developer.apple.com/internet/webcontent/bestwebdev.html Web Page Development: Best Practices] by the Safari development team at Apple.