Skip to content

Commit

Permalink
Started French version of Contributor guidelines
Browse files Browse the repository at this point in the history
  • Loading branch information
Paul Jackson authored and Paul Jackson committed Jul 24, 2012
1 parent 49ad7c0 commit 8466c56
Show file tree
Hide file tree
Showing 3 changed files with 62 additions and 3 deletions.
26 changes: 24 additions & 2 deletions README.md
Expand Up @@ -34,7 +34,7 @@ The toolkit complies with the new Standards on Web Accessibility and Web Usabili
* [Validate your CSS](http://jigsaw.w3.org/css-validator/#validate_by_uri+with_options) with the following changes to the default settings:
* **Profile:** CSS level 3
* **Vendor extensions:** Warnings
* [JSLint your JavaScript code](http://www.jslint.com) with the following changes to the default settings:
* [Validate your JavaScript code](http://www.jslint.com) with the following changes to the default settings:
* **Tolerate dangling _ in identifiers:** true
* **Tolerate missing 'use strict' pragma:** true
* **Assume browser:** true
Expand Down Expand Up @@ -69,4 +69,26 @@ La Boîte à outils est conforme à la Norme sur l'accessibilité des sotes Web
## Resources clés

* [Exemples pratiques](http://wet-boew.github.com/wet-boew/demos/index-fra.html)
* [Conditions régissant l'utilisation](http://www.sct.gc.ca/ws-nw/wet-boew/conditions)
* [Conditions régissant l'utilisation](http://www.sct.gc.ca/ws-nw/wet-boew/conditions)

## Contributor guidelines

* Pull requests are welcome. Please make sure your changes are to the latest code and limit the commit range to just the files you intended to change (to avoid conflicts).
* New components should be added in a feature-* branch (e.g., feature-lightbox).
* Licensing for all new components and supporting code must be compatible with the MIT license used by WET.
* New plugins should use pluginTemplate.js as the basis for the JavaScript code.
* Include the WET terms and conditions comment block in all text-based source files that fall under Crown Copyright.
* [Validate your HTML markup](http://validator.w3.org/nu/). Markup should be well-formed HTML5.
* To test for well-formed markup, validate with an XHTML5 preset and a checkmark next to "Be lax about HTTP Content-Type".
* [Valider votre CSS](http://jigsaw.w3.org/css-validator/validator.html.fr#validate_by_uri+with_options) avec les changements suivants aux paramètres :
* **Profil :** CSS niveau 3
* **Extensions Proprétaires :** Avertissements
* [Valider votre code JavaScript](http://www.jslint.com) avec les changements suivants aux paramètres :
* **Tolerate dangling _ in identifiers :** true
* **Tolerate missing 'use strict' pragma :** true
* **Assume browser :** true
* Formatting recommendations:
* Indent with tabs using the [Style K&R](http://fr.wikipedia.org/wiki/Style_d%27indentation#Style_K.26R)
* Use single quotes for strings in JavaScript (so unescaped double quotes can be used for attributes in HTML output)
* Supported browsers (should be tested against):
* [Browser test baseline - YUI Graded Browser Support](http://yuilibrary.com/yui/docs/tutorials/gbs/) (excluding IE6)
2 changes: 1 addition & 1 deletion docs/index-eng.html
Expand Up @@ -133,7 +133,7 @@ <h1 id="wb-cont">Web Experience Toolkit (WET)</h1>
<li><strong>Vendor extensions:</strong> Warnings</li>
</ul>
</li>
<li><a href="http://www.jslint.com">JSLint your JavaScript code</a> with the following changes to the default settings:
<li><a href="http://www.jslint.com">Validate your JavaScript code</a> with the following changes to the default settings:
<ul>
<li><strong>Tolerate dangling _ in identifiers:</strong> true</li>
<li><strong>Tolerate missing 'use strict' pragma:</strong> true</li>
Expand Down
37 changes: 37 additions & 0 deletions docs/index-fra.html
Expand Up @@ -117,6 +117,43 @@ <h1 id="wb-cont">Boîte à outils de l’expérience Web (BOEW)</h1>
</ul>
</section>

<section><h2>Contributor guidelines</h2>
<ul>
<li>Pull requests are welcome. Please make sure your changes are to the latest code and limit the commit range to just the files you intended to change (to avoid conflicts).</li>
<li>New components should be added in a feature-* branch (e.g., feature-lightbox).
<ul>
<li>Licensing for all new components and supporting code must be compatible with the MIT license used by WET.</li>
<li>New plugins should use pluginTemplate.js as the basis for the JavaScript code.</li>
<li>Include the WET terms and conditions comment block in all text-based source files that fall under Crown Copyright.</li>
<li><a href="http://validator.w3.org/nu/">Validate your HTML markup</a>. Markup should be well-formed HTML5.</li>
<li>To test for well-formed markup, validate with an XHTML5 preset and a checkmark next to "Be lax about HTTP Content-Type".</li>
</ul>
</li>
<li><a href="http://jigsaw.w3.org/css-validator/validator.html.fr#validate_by_uri+with_options">Valider votre CSS</a> avec les changements suivants aux paramètres&#160;:
<ul>
<li><strong>Profil&#160;:</strong> CSS niveau 3</li>
<li><strong>Extensions Proprétaires&#160;:</strong> Avertissements</li>
</ul>
</li>
<li><a href="http://www.jslint.com">Valider votre code JavaScript</a> avec les changements suivants aux paramètres&#160;;:
<ul lang="en">
<li><strong>Tolerate dangling _ in identifiers&#160;:</strong> true</li>
<li><strong>Tolerate missing 'use strict' pragma&#160;:</strong> true</li>
<li><strong>Assume browser&#160;:</strong> true</li>
</ul>
<li>Formatting recommendations:
<ul>
<li>Indent with tabs using the <a href="http://fr.wikipedia.org/wiki/Style_d%27indentation#Style_K.26R">Style K&amp;R</a></li>
<li>Use single quotes for strings in JavaScript (so unescaped double quotes can be used for attributes in HTML output)</li>
</ul>
<li>Supported browsers (should be tested against):
<ul>
<li><a href="http://yuilibrary.com/yui/docs/tutorials/gbs/">Browser test baseline - YUI Graded Browser Support</a> (excluding IE6)</li>
</ul>
</li>
</ul>
</section>

<dl id="gcwu-date-mod" role="contentinfo">
<dt>Date de modification&#160;:</dt><dd><span><time>2012-05-11</time></span></dd>
</dl>
Expand Down

0 comments on commit 8466c56

Please sign in to comment.