Confirmed users
1,605
edits
Add-ons/Terminology: Difference between revisions
Jump to navigation
Jump to search
m
→Usage Guidelines: small edits
m (→Usage Guidelines: more details) |
m (→Usage Guidelines: small edits) |
||
| Line 15: | Line 15: | ||
===Usage Guidelines=== | ===Usage Guidelines=== | ||
*'''Avoid using the terms interchangeably''' - “Add-ons” and “Extensions” should not be used interchangeably, but in accordance with their definition. | *'''Avoid using the terms interchangeably''' - “Add-ons” and “Extensions” should not be used interchangeably, but in accordance with their definition and befitting the context. | ||
*'''"WebExtensions" refers to the technology and not add-ons built with the technology''' - For example, “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" can still be used as a standalone term''' | *'''"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: | ||
**To distinguish from a legacy add-on: "Your WebExtension add-on displays a 'compatible with Firefox 57+' banner." | **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." | **To describe the new system: "We're moving to a WebExtensions model for add-on development." | ||