|
|
| Line 1: |
Line 1: |
| (This wiki is under construction)
| |
|
| |
|
| =Logo=
| |
|
| |
| =AMO=
| |
|
| |
| =Terminology=
| |
| As of July 2017, we are moving away from calling extensions built with WebExtensions APIs "WebExtensions", and towards calling them simply "Extensions".
| |
|
| |
| ===Background===
| |
| When we first decided to move add-ons to a new API model, we needed a name for it that 1) was searchable 2) was distinguishable from legacy extensions and 3) signals its cross-browser interoperability. “WebExtensions” did all three, and we used it to describe extensions built with this new API.
| |
|
| |
| Now that we’re close to completing the transition and supporting just one API for building extensions, we need to gradually drop the term “WebExtensions”.
| |
|
| |
| ===Glossary and Usage===
| |
| Here are the proposed definitions, based on our discussion at SF all-hands:
| |
|
| |
| *Browser extensions: extensions that work in different browsers
| |
| *Extensions: pieces of code that extend the capabilities of a browser
| |
| *WebExtensions: a mostly deprecated term that describes a Firefox extension built with WebExtension APIs. Can still be used to describe implementation in Firefox.
| |
| *Add-on: an umbrella term that describes different types of code that extend Firefox. Mostly used on AMO. Includes extensions, themes, plug-ins, dictionaries, etc. *Eventually, when everything is built with WebExtension APIs, we will start calling these simply “extensions”.
| |
|
| |
| Here are some usage guidelines:
| |
|
| |
| *“Add-ons” and “Extensions” should not be used interchangeably.
| |
| *For more formal cases (like the main title of the page) we should say "Browser extensions", then use "extensions" as an informal shorthand
| |
| *Copy should say “Cool new extensions” rather than “Cool new WebExtensions”
| |