Support:Style Guide: Difference between revisions

Plugins does not contain a hyphen
(Plugins does not contain a hyphen)
 
(14 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<small>[[Support|Support]] » [[Support:Style_Guide|Style Guide]]</small>
The support.mozilla.com style guide aims to make the Firefox support Knowledge Base consistent, resulting in a knowledge base, that is easy to read and contribute to. These are not rigid rules. If you feel you have good reason not to follow any of these guidelines, feel free not to follow them. Conversely, do not be surprised if your contributions are edited, to comply the style guide.
The support.mozilla.com style guide aims to make the Firefox support Knowledge Base consistent, resulting in a knowledge base, that is easy to read and contribute to. These are not rigid rules. If you feel you have good reason not to follow any of these guidelines, feel free not to follow them. Conversely, do not be surprised if your contributions are edited, to comply the style guide.


 
==Preferred style guides==
==Common inconsistencies==
If you have questions about usage and style not covered here, I recommend referring to [http://www.amazon.com/gp/product/0131428993/ Read Me First! A Style Guide for the Computer Industry], or the [http://www.economist.com/research/StyleGuide/ Economist style guide]. Failing that, use the [http://www.amazon.com/gp/product/0226104036/ Chicago Manual of Style].
*Plug-ins contains a hyphen (it is not plugins).<br/>
*Add-ons contains a hyphen (it is not addons).
*Links to the main Mozilla.com web site should not contain the locale.
**<span style="color: #006600">Good</span>: http://www.mozilla.com/firefox
**Bad: http://www.mozilla.com/en-US/firefox
 


==Terminology==
==Terminology==
In cases where you are not sure of proper terminology, or if an element has more than one name, use the term in the user-interface. For instance, in the customize toolbar screen, the term used for the location bar is "Location" bar, not "Address" bar, or "URL" bar. Other often used terms:
In cases where you are not sure of proper terminology, or if an element has more than one name, use the term in the user-interface. For instance, in the customize toolbar screen, the term used for the location bar is "Location" bar, not "Address" bar, or "URL" bar. Other often used terms:
*It's "web feeds", not "RSS feeds".
* Plugins does not contain a hyphen (it is not plug-ins).
*It's "search engines", not "search plug-ins".
* Add-ons contains a hyphen (it is not addons).
*Home page is two words, not one.
* It's "web feeds", not "RSS feeds".
*Web site is two words, not one.
* It's "search engines", not "search plug-ins".
* Home page is two words, not one.
* Web site is two words, not one.


==Links to Mozilla.com==
Links to the main Mozilla.com web site should not contain the locale.
* '''<span style="color: #006600">Good</span>''': http://www.mozilla.com/firefox
* Bad: http://www.mozilla.com/en-US/firefox


==Preference names / values==
==Acronyms and abbreviations==
[We still need to figure out what we can do with this on tikiwiki.]
When using a term, that may be presented as an acronym or abbreviation, use the method of presentation that is used in the user-interface; and do not separate the letters of an acronym by a period.
* '''<span style="color: #006600">Good</span>''': SSL 3.0
* Bad: S.S.L. 3.0
* Bad: Secure Sockets Layer 3.0


===Acronyms not found in the user-interface===
In cases where an acronym is not in the user-interface, introduce its expansion in parenthesis on the first mention.
* '''<span style="color: #006600">Good</span>''': RSS(Really Simple Syndication) links
* Bad: RSS links


==User scripts (user.js, userChrome.css, userContent.css)==
===Abbreviations not found in the user-interface===
[We still need to figure out what we can do with this on tikiwiki.]
In cases where an abbreviation is not in the user-interface, use the long version.
* '''<span style="color: #006600">Good</span>''': information
* Bad: info


===Plurals of acronyms and abbreviations===
For plurals of acronyms or abbreviations, add s, without the apostrophe.
* '''<span style="color: #006600">Good</span>''': CD-ROMs
* Bad: CD-ROM's


==File names / paths==
==Capitalization==
File names and file paths should presented in italics.
Capitalize the following items:
* Proper nouns
* The letters of many abbreviations and acronyms
* The first letter of the first word in numbered or bulleted lists
* The first letter of each term that identifies the name of a key on the keyboard
* The first letter of the first word of a complete sentence
* The first letter of the first word of a complete sentence following a colon
* The first letter of the first word in a title or heading
** '''<span style="color: #006600">Good</span>''': How to make Firefox your default browser
** Bad: How To Make Firefox Your Default Browser


==Dates==
* For dates use the format: January 1, 1990.
** '''<span style="color: #006600">Good</span>''': December 31, 2007
** Bad: December 31st, 2007
** Bad: 31 December, 2007


==Keyboard shortcuts==
* Alternatively, you can use YYYY-MM-DD
[We still need to figure out what we can do with this on tikiwiki.]
** '''<span style="color: #006600">Good</span>''': 2007-12-31
** Bad: 31-12-2007
** Bad: 12-31-2007


==Whitespace==
* One newline after section titles, two before.
* Two newlines between paragraphs
* One newline after lists


==Menu paths==
==General spelling, grammar, and punctuation==
[We still need to figure out what we can do with this on tikiwiki.]
 
 
==Acronyms and Abbreviations==
When using a term, that may be presented as an acronym or abbreviation, use the method of presentation that is used in the user-interface; and do not separate the letters of an acronym by a period.
*<span style="color: #006600">Good</span>: SSL 3.0
*Bad: S.S.L. 3.0
*Bad: Secure Sockets Layer 3.0
 
 
==Dictionaries==
United States English spelling is preferred.
United States English spelling is preferred.
*<span style="color: #006600">Good</span>: color
* '''<span style="color: #006600">Good</span>''': color
*Bad: colour
* Bad: colour


If you're unsure of spelling, refer to [http://www.answers.com Answers.com].
If you're unsure of spelling, refer to [http://www.answers.com Answers.com].


===Latin abbreviations===
Common Latin abbreviations (etc., i.e., e.g.) may be used in parenthetical expressions and in notes. Use periods in these abbreviations.
* '''<span style="color: #006600">Good</span>''': Search engines (e.g. Google) can be used ...
* Bad: Search engines e.g. Google can be used ...
* Bad: Search engines, e.g. Google, can be used ...
* Bad: Search engines, (eg: Google) can be used ...


==Links to Bugzilla and other references==
===Pluralization===
Links to any bug pages on Bugzilla should be treated as references. [We still need to figure out what we can do with this on tikiwiki.]
Use English-style plurals, not the Latin- or Greek-influenced forms.
* '''<span style="color: #006600">Good</span>''': viruses
* Bad virii


===Serial commas===
Use the serial comma. The serial (also known as "Oxford") comma is the comma that appears before "and" in a series of three or more items.
* '''<span style="color: #006600">Good</span>''': Clear your cache, cookies, and history.
* Bad: Clear your cache, cookies and history.


==Article Title/Section Capitalization==
==Common types of text==
When creating the name of an article, capitalize the first word and any proper nouns.
*<span style="color: #006600">Good</span>: How to set the Home page
*Bad: How To Set The Home page


===Preference names / values===
Enclose preference name and values in the designated preference tags.


==Latin Abbreviations==
===User scripts (user.js, userChrome.css, userContent.css)===
Common Latin abbreviations (etc., i.e., e.g.) may be used in parenthetical expressions and in notes. Use periods in these abbreviations.
Enclose user scripts in the designated code tags.<br>
*<span style="color: #006600">Good</span>: Search engines (e.g. Google) can be used ...
<nowiki>{img src=images/code.png}%%% {CODE()}
*Bad: Search engines e.g. Google can be used ...
text
*Bad: Search engines, e.g. Google, can be used ...
{CODE}</nowiki>
*Bad: Search engines, (eg: Google) can be used ...


===File names / paths===
Enclose file names and file paths in the designated filename tags.


==Plurals of acronyms and abbreviations==
===Keyboard shortcuts===
For plurals of acronyms or abbreviations, add s, without the apostrophe.
Enclose keyboard shortcuts in the designated keyboard tags.<br>
*<span style="color: #006600">Good</span>: CD-ROMs
<nowiki>{TAG(tag=kbd)}text{TAG}</nowiki>
*Bad: CD-ROM's


===Menu paths===
Enclose menu paths in the designated menu tags.<br>
<nowiki>{DIV(class=mnu,type=>span)}text{DIV}</nowiki>


==Pluralization==
==References==
Use English-style plurals, not the Latin- or Greek-influenced forms.
Links to any bug pages on Bugzilla should be treated as references. [We still need to figure out what we can do with this on tikiwiki.]
*<span style="color: #006600">Good</span>: viruses
*Bad viri
 
 
==Dates==
*For dates use the format: January 1, 1990.
**<span style="color: #006600">Good</span>: December 31, 2007
**Bad: December 31st, 2007
**Bad: 31 December, 2007
 
*Alternatively, you can use YYYY-MM-DD
**<span style="color: #006600">Good</span>: 2007-12-31
**Bad: 31-12-2007
**Bad: 12-31-2007
 
==Serial Commas==
Use the serial comma. The serial (also known as "Oxford") comma is the comma that appears before "and" in a series of three or more items.
*<span style="color: #006600">Good</span>: Clear your cache, cookies, and history.
*Bad: Clear your cache, cookies and history.
1,365

edits