When a user reads information at support.mozilla.com, there is a level of trust that automatically exceeds that of other support documentation. This is because we are at *.mozilla.com. It is official support documentation. Information on support.mozilla.com is viewed as coming from Mozilla itself ("Mozilla says to do this."). As a result, the articles, instructions, and even links we choose to provide have to keep that in mind, in the interest of maintaining and upholding that trust.

Table Of Contents

What topics does the Knowledge Base cover?

The Firefox Support Knowledge Base provides articles for helping people use Firefox user-end features, frequently ask questions, and frequently encountered problems.
The Firefox Support Knowledge Base does not provide articles for tips for functionality not supported by Mozilla development. In general, if it is a trick that is considered to be "monkeying around" with Firefox, it does not belong in the Knowledge Base, unless there is considerably high demand for it.

That rule does not apply to troubleshooting articles.

What instructions are acceptable in the Knowledge Base?

"Any functionality that is intended for end-users would not require you to close Firefox and manually edit some text file buried in a hidden directory."

Methods of tweaking Firefox, such as about:config, user.js, userChrome.css, and userContent.css are not recommended for average users. Use of these tools is only allowed in troubleshooting articles.

Add-ons

Linking to add-ons

Recommending and maintaining links to specific add-ons is the responsibility of the addons.mozilla.org website, not Firefox Support. If you'd like to recommend an add-on, just point users to the addons.mozilla.org website (or link to the appropriate category), unless we've got permission. If the add-on is not on AMO, do not suggest the add-on. This includes plugins.

Using add-ons

If an add-on is causing a problem with Firefox functionality that would otherwise work if the add-on is not installed, yes we do document that. Unless there is a specific solution, the recommendation should be to uninstall the problematic add-on.