Closed Bug 1890882 Opened 1 year ago Closed 1 year ago

Rename Firefox Android's "add-ons" to "extensions" in articles and screenshots [Android V126]

Categories

(support.mozilla.org :: Knowledge Base Content, task)

Product:
support.mozilla.org
Component:
Knowledge Base Content
Type:
task

Tracking

(firefox-esr115 unaffected, firefox124 unaffected, firefox125 unaffected, firefox126+ fixed)

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox-esr115 --- unaffected
firefox124 --- unaffected
firefox125 --- unaffected
firefox126 + fixed

People

(Reporter: cpeterson, Assigned: lsiebert)

References

Details

  1. For consistency with Firefox desktop and addons.mozilla.org, Firefox Android is renaming "add-ons" to "extensions" in its UI. We don't need any new SUMO articles, but a number of existing articles (and screenshots) will need to be updated, including:

Those are all the articles I found that mention "add-on" or "add-ons", though I might have missed some.

  1. Since some article titles will change, their URLs will change. Example: https://support.mozilla.org/en-US/kb/find-and-install-add-ons-firefox-android to https://support.mozilla.org/en-US/kb/find-and-install-extensions-firefox-android. Ssince the existing URLs have been been indexed by search engines and may be linked to from blog posts, it would be nice if the old URLs could redirect to the new URLs indefinitely.

Did you check out the steps and FAQs for submitting requests to the CX content team? (yes or no)? [REQUIRED]

**Note: Learn more at https://mozilla-hub.atlassian.net/wiki/spaces/MSS/pages/21430745/Mozilla+Support+Content **

Yes

IMPORTANT NOTICE: FOR TIMELY PUBLICATION, CONTENT REQUESTS MUST BE SUBMITTED AT LEAST 14 DAYS BEFORE THE RELEASE DATE, ENABLING THE SUMO TEAM TO MAKE THEM LIVE WITHIN 48 HOURS POST-RELEASE. PLEASE ENSURE THAT ALL SUBMITTED INFORMATION, INCLUDING FEATURE DETAILS AND VISUAL ASSETS, IS FINAL. IN THE EVENT OF ANY UNFORESEEN CHANGES OR DELAYS NECESSITATING A PUSH TO A SUBSEQUENT RELEASE, PROMPTLY INFORM US TO PREVENT PUBLISHING AS PER THE ORIGINAL SCHEDULE.

Is the content restricted to staff or under embargo (yes or no)? [REQUIRED]

Note: If yes, ensure 'Advanced Fields' are visible by selecting 'Show Advanced Field' at the top right, then scroll to 'Security' and check 'Confidential Mozilla Employee Bug (non-security)'.'

No

Product (ensure to select only one product for each ticket. If your request involves multiple products, file an individual Bugzilla for each)

Choose one below and delete others. [REQUIRED]

Firefox for Android

Select the type of request.

Choose one or more below and delete others. [REQUIRED]

KB content update/ new content

Please provide a summary of the request and outline any user-facing changes. [REQUIRED]

For consistency with Firefox desktop and addons.mozilla.org, Firefox Android's "add-ons" settings have been renamed to "extensions" (in bug 1885561).

Are the user-facing changes mentioned above final? (yes or no)? [REQUIRED]

Yes

Is this an on- or off-train release? Please indicate the product version number, if applicable, and add it to the end of the Summary field using the format of: Summary [Product V123]. [REQUIRED]

On-train release in Fx 126 (release date: 2024-04-14). The UI change is already live in Fx 126 Nightly.

What is the anticipated release date? [REQUIRED]

Note: Content is typically published at, or within, 48 hours of the release.

2024-04-14 (Fx 126's release date)

Does the content need to be published prior to the release date? If so, when? [REQUIRED]

Note: If you don’t let us know if this date changes, it will be published on this date

No

Does the content need to be localized in any languages outside of EN-US? If yes, please indicate which languages. [REQUIRED]

Note: A minimum of 10 days is required for translation requests.

Yes, but won't localizers automatically localize article changes after en-US publication? We don't need to hire a translation service to translate the article changes before en-US publication.

Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]

Please include links to any design assets, visuals, figma files, etc. [REQUIRED]

Note: Ensure to submit only final visual assets relevant to the Production release, excluding Nightly or Beta images, and favor 'Light mode' UI screenshots over 'Dark mode'

Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED]

The "UI Changes" section in the [https://docs.google.com/document/d/1KZX2lIea8FB89BGRaVy5UBSueldYt_NYC_WNjRMbg_I/edit](Android Extensions Copy Changes) spec has instructions (with screenshots) to access the changed strings.

Does the content need approval before publishing? If yes, identify the one approver responsible for this task.

Note: Minor changes such as string updates are directly handled in SUMO, and will not lead to the generation of a pre-publishing draft. [REQUIRED]

No

Assignee: nobody → lsiebert

On it!

Summary: Rename Firefox Android's "add-ons" to "extensions" in articles and screenshots → Rename Firefox Android's "add-ons" to "extensions" in articles and screenshots [Android V126]

Here's the link to the task in the Asana Release Tracker: https://app.asana.com/0/0/1207050884090419/f

You need to log in before you can comment on or make changes to this bug.