Add-ons/Terminology: Difference between revisions

Add-ons/Terminology (view source)

Revision as of 00:09, 28 July 2017

767 bytes added , 28 July 2017

m

→‎Usage Guidelines: more details

AmyT

Confirmed users

1,605

edits

@@ Line 15: / Line 15: @@
 ===Usage Guidelines===
-*“Add-ons” and “Extensions” should not be used interchangeably.
+*'''Avoid using the terms interchangeably''' - “Add-ons” and “Extensions” should not be used interchangeably, but in accordance with their definition.
-*Copy should say “Cool new extensions” rather than “Cool new WebExtensions”
+*'''"WebExtensions" refers to the technology and not add-ons built with the technology''' - For example, “Cool new extensions” rather than “Cool new WebExtensions”
-*"WebExtensions" should still be used when talking about the API that extensions are built on
+*'''"WebExtensions" can still be used as a standalone term'''" - It is ok to use the word "WebExtension(s)" without "API" following it, as long as you are describing the technology and not an add-on built with the technology. For example:
-*For MDN extension documentation, formal cases (like the main title of the page) should say "Browser extensions", and thereafter "extensions" as an informal shorthand
+**To distinguish from a legacy add-on: "Your WebExtension add-on displays a 'compatible with Firefox 57+' banner."
+**To describe the new system: "We're moving to a WebExtensions model for add-on development."
+*'''"API" or "APIs"?''' - The system, or the technology underlying add-on development is the WebExtensions API. Comprising it are WebExtensions APIs that expose certain parts of Firefox to add-on developers.
+*'''"Browser extensions"''' - For MDN extension documentation, formal cases (like the main title of the page) should say "Browser extensions", and thereafter "extensions" as an informal shorthand
 =addons.mozilla.org (AMO)=