User Tools

  • Logged in as: anonymous (anonymous)
  • Log Out

Site Tools


mantisbt:style_guide

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
mantisbt:style_guide [2010/10/14 23:01]
daryn
mantisbt:style_guide [2013/04/30 05:54] (current)
dregad
Line 1: Line 1:
-====== ​HTML ======+====== ​Style Guide (DRAFT) ​====== 
 + 
 +===== HTML =====
   * Do use HTML5   * Do use HTML5
   * Do not use tables for layout. ​ Tables may only be used when the content is actually table data.   * Do not use tables for layout. ​ Tables may only be used when the content is actually table data.
   * Do not put business logic in the templates - //Using PHPTAL templating engine will assist with security (automatically escaping strings to prevent XSS attacks), internationalisation and ease of template maintenance. The templates are valid XML documents and can be rendered directly in a web browser without needing to be parsed through the templating engine.//   * Do not put business logic in the templates - //Using PHPTAL templating engine will assist with security (automatically escaping strings to prevent XSS attacks), internationalisation and ease of template maintenance. The templates are valid XML documents and can be rendered directly in a web browser without needing to be parsed through the templating engine.//
  
-====== CSS ======+===== CSS =====
   * The only method allowed for including CSS styling is via including an external CSS stylesheet in the <​head>​ of the document.   * The only method allowed for including CSS styling is via including an external CSS stylesheet in the <​head>​ of the document.
   * Do use a fluid layout   * Do use a fluid layout
Line 19: Line 21:
   * Do not use inline <​style>​..</​style>​ blocks in the body   * Do not use inline <​style>​..</​style>​ blocks in the body
  
-====== Javascript ​====== +===== Javascript ===== 
-  * The only method allowed for including Javascript is via including an external script file in the <​head>​ of the document +  * The only method allowed for including Javascript is via including an external script file in the <​head>​ of the document ​//(or by placing all script tags just before the body closing tag as this seems to be the standard now)// 
-  * The pages should ​be able to function without Javascript enabled. If Javascript is available then it can be used to replace parts of the DOM with more advanced functionality (in the same way jQuery UI operates)+  * The pages must be able to fully function without Javascript enabled. If Javascript is available then it can be used to replace parts of the DOM with more advanced functionality (in the same way jQuery UI operates)
   * Use jQuery exclusively for any javascript based features   * Use jQuery exclusively for any javascript based features
   * Use only jQuery plugins with high rates of usage and active, healthy development   * Use only jQuery plugins with high rates of usage and active, healthy development
   * Do not use inline Javascript in any HTML output   * Do not use inline Javascript in any HTML output
     * No onclick, onmouseover,​ etc. attributes     * No onclick, onmouseover,​ etc. attributes
-    * No inline <​script..>​something();</​script>​ blocks ​//(Perhaps with the exception of placing all script tags just before the body closing tag)//+    * No inline <​script..>​something();</​script>​ blocks
     * Do not use javascript:​something() in hyperlink hrefs.     * Do not use javascript:​something() in hyperlink hrefs.
  
-====== Accessibility and Localization ​======+===== Accessibility and Localization =====
   * Maintain support for right-to-left (RLT) languages in the redesign (related to CSS)   * Maintain support for right-to-left (RLT) languages in the redesign (related to CSS)
   * Investigate accessibility concerns in depth to determine how the pages will work in screen readers, on browsers with extra large font sizes, for colour blind users, etc.   * Investigate accessibility concerns in depth to determine how the pages will work in screen readers, on browsers with extra large font sizes, for colour blind users, etc.
  
-====== User Interface ​======+===== User Interface =====
   * Don't make life hard for power users. ​ Clean up the interface but keep the functionality readily accessible   * Don't make life hard for power users. ​ Clean up the interface but keep the functionality readily accessible
   * Workflow must be as efficient as possible   * Workflow must be as efficient as possible
  
-====== Questions for discussion ​======+ 
 +===== Questions for discussion =====
   - App Mode -- several browsers are now supporting App Mode, do we have any requirements for that?  Are there standards around this?   - App Mode -- several browsers are now supporting App Mode, do we have any requirements for that?  Are there standards around this?
   - Any requirements to have MantisBT grease monkey friendly to allow users to easily customize the page?  Not sure what that means, does it mean naming fields? divs, etc?   - Any requirements to have MantisBT grease monkey friendly to allow users to easily customize the page?  Not sure what that means, does it mean naming fields? divs, etc?
   - Supported browsers / versions? ​ What is the cut off?   - Supported browsers / versions? ​ What is the cut off?
 +    - Firefox 3.0+
 +    - Recent versions of Opera, Chromium, Konqueror, Safari (should almost come for free from I)
 +    - IE7+
 +    - IE6 support, if needed, can come through community contributions
   - Come to some sort of arrangement on how plugins will manipulate the HTML to insert their own buttons, widgets, etc as required.   - Come to some sort of arrangement on how plugins will manipulate the HTML to insert their own buttons, widgets, etc as required.
- + 
mantisbt/style_guide.1287111662.txt.gz · Last modified: 2010/10/14 23:02 (external edit)