Modify mozilla.org testing doc; Update SuMo test doc (#257)

* Update sumo.md

Remove the bullet item per Tasos input. The SuMo channel on Discourse is not frequently monitored.

* Updating the mozilla.org doc

* Implement feedback

* Update src/products/mozilla_org/testing.md

Co-authored-by: Francesco Lodolo <flod@lodolo.net>

* Update src/products/mozilla_org/testing.md

Co-authored-by: Francesco Lodolo <flod@lodolo.net>

* Update src/products/mozilla_org/testing.md

Co-authored-by: Francesco Lodolo <flod@lodolo.net>

* Update src/products/mozilla_org/testing.md

Co-authored-by: Francesco Lodolo <flod@lodolo.net>

* Remove white space

* fix merge mistakes

Try to resolve the mess created by conflicts.

* More implementations

Address additional comments

* minor fixes

* Implemented feedbacks

---------

Co-authored-by: Francesco Lodolo <flod@lodolo.net>

Author: peiying2

src/products/mozilla_org/testing.md

@@ -4,15 +4,15 @@
 
 Mozilla.org is highly visible because the site houses the basic info of all Mozilla products, conveys Mozilla’s mission, vision, and values it stands for. Additionally, it promotes initiatives and campaigns in time of these events. The localized versions reach 60% of the Mozilla users globally. It is very important that, not only the main pages are localized, they are thoroughly tested before they are launched on production.
 
+It’s highly advised you to ask other community members to conduct peer review not only on Pontoon, but on staging and production. While not all the languages are required for certain projects, each community can opt in the projects at a later time.
+
 ## Key links
 
 * Production: https://www.mozilla.org/{locale_code}/
 * Staging: https://www-dev.allizom.org/{locale_code}/
 * Repository: https://github.com/mozilla-l10n/www-l10n
 * Pontoon: https://pontoon.mozilla.org/projects/mozillaorg/
 
-It’s highly advised you to ask other community members to conduct peer review not only on Pontoon, but on staging and production. While not all the languages are required for certain projects, each community can opt in the projects at a later time.
-
 ## What to test
 
 ### Pre-l10n test
@@ -29,12 +29,12 @@ It’s highly advised you to ask other community members to conduct peer review
 * Truncation: button text should remain inside the button.
 * Header line break wraps at proper place.
 * Text not overlapping graphic.
-* Terminology consistent with product, and among web pages.
-* Brand names remain in English.
+* Terminology consistent with product across web pages.
+* Brand names remain in English, with a few exceptions due to [declension](https://mozilla-l10n.github.io/styleguides/mozilla_general/index.html#declensions). Check out [these detailed guidelines](https://mozilla-l10n.github.io/styleguides/mozilla_general/index.html#brands-copyright-and-trademark) when working with brands and trademarks.
 * Product names comply to Mozilla guideline and adhere to what the community has agreed to.
 * No corrupted characters.
-* Click on the links on the page, which should take you to the pages of the same language if they are localized, or they will be redirected to en-US if the pages are not..
-* Nav bar terms consistent with the page titles they are linked to (except when Nav bar term is shortened due to space limitation).
+* Click the links on the page to navigate to localized pages in the same language. If a page is not localized, you will be redirected based on your language preference settings (e.g., Fulah > French > English). If no preferences are set, the default is en-US.
+* Navigation terms consistent with the page titles they are linked to (except when the navigation term is shortened due to space limitation).
 * Footer links don’t overlap with one another.
 
 You can make linguistic changes directly in [Pontoon](https://pontoon.mozilla.org/projects/mozillaorg/).
@@ -44,7 +44,7 @@ You can make linguistic changes directly in [Pontoon](https://pontoon.mozilla.or
 * Click the download link, you should be able to download the product in your language, if it is localized, such as Firefox.
 * Font support and readability.
 * Footer: verify that the translation of the link is coherent and the link is functional.
-* Language list: is your language listed as one of the options? Check https://www-dev.allizom.org/en-US to confirm.
+* Language list: is your language listed as one of the options? Check https://www-dev.allizom.org/firefox/all/ to confirm. See [detailed steps below](#firefoxallftl) to get to the language list.
 * Error page: deliberately type a broken link, such as https://www.mozilla.org/firefox/neu/, check whether [404 page](https://www-dev.allizom.org/404/) is localized.
 * If your language is RTL, make sure that the page layout and text flow in the correct directions.
 
@@ -59,10 +59,10 @@ You can make linguistic changes directly in [Pontoon](https://pontoon.mozilla.or
 Updated translations are pushed to the production server regularly throughout the day.
 
 * New page: When a brand new page is available for localization, it will be enabled on production when it’s 80% complete. At that point, if it doesn’t reach 100% completion level, the page will be available on production with English content mixed with translation. Before the page is activated in production, use the staging server for testing.
-* Activated page with new string update (no tags): The strings will appear in English on production right away. Localized content will be pushed to production as soon as translations are available in the repository.
-* Activated page with tagged new string update: The switch to the updated content happens when tagged strings are fully localized. In some cases, there is a defined period of time frame to allow tagged strings to be fully localized. Test the updates on staging server.
-* Activated page with template change: In some cases, a page receives a major update that requires a complete rewrite of the template. If this happens, the old template is kept online only for a defined period of time. When removed, it will cause the URL to redirect users to the English version if the intended localized version is not ready.
-* Activated page missing too many updates: An activated page falling far behind with multiple updates will create bad user experience. We might decide to disable it manually.
+* Activated page with added strings: The strings will appear in English on production right away. Localized content will be pushed to production as soon as translations are available in the repository.
+* Activated page with string updates: The switch to the updated content happens when the replacements of obsolete strings are fully localized. In some cases, there is a defined time frame to show the new strings on production, so test the updates on staging server. The obsolete string will be removed three months after the introduction of the replacement strings.
+* Activated page with template change: In some cases, a page receives a major update that requires a complete rewrite of the template. If this happens, the old template is kept online only for a defined period of time. When removed, it will cause the URL to redirect users to the English version if the intended localized version is not ready, or other user preferred localized versions are not available either.
+* Activated page missing too many updates: An activated page falling far behind with multiple updates will create poor user experience. They may be subjected to removal.
 
 ### Sync and update frequencies
 
@@ -73,43 +73,32 @@ Updated translations are pushed to the production server regularly throughout th
 
 It is safe to say that it will take less than an hour to see your changes reflected on the production server.
 
-When a project has a firm deadline to meet, it will be communicated through the [dev-l10n-web mailing list](https://lists.mozilla.org/listinfo/dev-l10n-web). Be sure to sign up so you receive important community wide information on web related projects. You can also check out the deadline at page level in Pontoon.
-
-## Testing content migrated to Fluent
+When a project has a firm deadline to meet, it will be indicated at the top left corner of the project page in Pontoon and at the page level. When necessary, it will be communicated through [the l10n-community room on Matrix](https://chat.mozilla.org/#/room/#l10n-community:mozilla.org).
 
-This section focuses on review and test after a page is migrated to Fluent.
+## Testing content in Fluent
 
 ### Reviewing and updating [brands.ftl](https://github.com/mozilla-l10n/www-l10n/blob/master/en/brands.ftl)
 
-This new file captures all the brand and product names that appear in all the pages on mozilla.org as of now. As a general rule, brands and product names remain unchanged. The exceptions are:
+This file captures all the brand and product names that appear in all the pages on mozilla.org. As a general rule, brands and product names remain unchanged. The exceptions are:
 
-* Account/Accounts in Firefox Account/Accounts
-* Sync in Firefox Sync
-* Browser in Firefox Browser
+* Account/accounts in Mozilla account/accounts: Mozilla should be treated as a brand, but `account` and `accounts` should be translated. Both the singular and plural forms are used in lower cases. Uppercase is reserved for special use cases where headline case is necessary, for example legal document names and references.
+* Browser/Browsers in Firefox Browser/Browsers.
 
 If your community decides to translate any of these products or feature names, translate it once and translate it in this file. Be sure to have a consensus among active contributors what the translation should be before updating this file. This practice will ensure term use consistency across all pages.  
 
 Please refer to the [guidelines for brands and trademarks](https://mozilla-l10n.github.io/styleguides/mozilla_general/index.html#brands-copyright-and-trademark) when reviewing and updating this file.
 
-### Reviewing and updating migrated files
-
-The project dashboard contains fewer files than before. This list will grow over time as the mozilla.org team continues migrating from .lang to Fluent. Keep track of what is reviewed and what is pending for a review. Here are a few things to check:
-* On the project dashboard, if there is orange color in the status progress bar, click on the orange number of warnings. If the localized string is missing a term reference, chances are, the product or brand name is translated, transliterated or declensed. Insert the variable to replace the translated/transliterated/declensed term.
-* Do not translate words in placeables, like term references.
-* If there is enough bandwidth within a team, work in pairs, one updates the string as a suggestion, another reviews and approves it.
-* Review your changes on production, especially those with brand and product names.
-
 ### Reporting technical issues
 
 Report issues that can’t be resolved in Pontoon by:
-
 * Filing a bug in [Bugzilla](https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Localizations) and selecting your locale.
 * Adding the l10n PM in charge for NI. The l10n PM information appears at the top left corner on the [project page](https://pontoon.mozilla.org/projects/mozillaorg/).
 * Including the file name plus a screenshot and/or URL.
+* If an extra tag is added to a string in order for it make sense in your language, the string will generate an error report. The l10n PM for the project will consult you whether to make this an exception so it will not generate an error report in the future.
 
 ### Reporting vendor translation errors
 
-If the mozilla.org project is not in your Pontoon dashboard, but the site is localized into your locale, it is likely being translated by Mozilla staff or a translation vendor. Report any translation errors from Mozilla staff or a translation vendor by:
+If the mozilla.org project is not in your Pontoon dashboard, but the site is localized into your locale, it is likely being translated by a translation vendor. Report any translation errors by:
 
 * Filing a bug using one of these templates and selecting your locale in the component list:
   * This [template is to report a single error](https://mzl.la/2P9PABx).
@@ -121,38 +110,41 @@ This section focuses on instructions for testing pages with dynamically generate
 
 ### [firefox/accounts.ftl](https://www.mozilla.org/firefox/accounts/)
 
-* Click the **Sign In to Monitor** button, you will be taken to the sign-in page in order to get to the [Firefox Monitor](https://monitor.firefox.com) site.
-* Click on the links under each of the following products:
-   * Firefox browser
-   * Firefox Lockwise
-   * Firefox Monitor
+On the landing page of the Mozilla account page, click on the links under each of the following products which take you to product specific pages:
+* Firefox Browser
+* Firefox Monitor
+* Firefox Relay
+* Mozilla VPN
+* Pocket
+
+If you already have an account, click on the `Manage your account` link on the right side of the landing page, which will take you to the subscription page. If you do not have an account, you will be invited to create an account by providing an email address in the `Sign In` box.
 
 Note: You may see different languages between mozilla.org, the login window, and the products above. If any of these products is not localized in your locale, it will fall back to other languages set as preferred for content language negotiation, assuming any of them is available for the project, or English.
 
 ### [firefox/all.ftl](https://www.mozilla.org/firefox/all/)
 
-On the lower left side of the page:
+On the right side of the page, there is a four-step process to go through in order to download Firefox.
+* Browsers: choose one of the options either for desktop or mobile. Click on the `?` next to the Browsers category, a popup window shows the descriptions of different versions of Firefox browsers available for download. Select one browser to proceed to the next step.
+* Platforms: Click on the `?`, a popup window shows the descriptions of different versions of installers available for download.
+* Languages: A list of languages available in the build depending on what is selected in the above two categories. Check whether your current preferred language is shown by default. Change to a different language, check whether the download summary above the **Download Now** button corresponds to your new selection.
+* Download: The **Download Now** button appears.
+
+On the lower left side of each page, you will see these links:
 * These two sites are in English only: [Check the system requirements](https://www.mozilla.org/firefox/system-requirements/) and [Release notes](https://www.mozilla.org/firefox/notes/).
-* Click on the **Source code** link, you will be directed to the topic on [MDN](https://developer.mozilla.org/docs/Mozilla/Developer_guide/Source_Code) site in your language if it is localized.
+* Click on the **Source code** link, you will be directed to the [Firefox Source Docs](https://firefox-source-docs.mozilla.org/) page which is not localized.
 * The [Firefox Privacy Notice](https://www.mozilla.org/privacy/firefox/) document is localized in limited number of languages.
 * Click on the **Need Help** link, you will be directed to the [SUMO](https://support.mozilla.org/products?utm_source=mozilla.org&utm_medium=referral&utm_campaign=need-help-link) home page.
 
-On the right side of the page:
-* Click on the `?` at the end of **Which browser would you like to download?**, a popup window shows the descriptions of different versions of Firefox available for download.
-* Click on the `?` at the end of **Select your preferred installer**, a popup window shows the descriptions of different versions of installers available for download.
-* Under the section of **Select your preferred language**, check whether your current preferred language is shown by default. Change to a different language, check whether the download summary above the **Download Now** button corresponds to your new selection.
-
 ### [firefox/new/download.ftl](https://www.mozilla.org/firefox/new/)
 
-* Click the **Download Now** button to check the [thank you](https://www.mozilla.org/en-US/firefox/download/thanks) page that triggers an automatic download.
-* Click on the **Advanced install options & other platforms** link, a pop-up window displays options in various platforms.
-* Click on the **Download in another language** link, you will be directed to the [firefox/all](https://www.mozilla.org/firefox/all/) page.
-* Click on the **Fix a problem** link, you will be directed to this [SUMO](https://support.mozilla.org/kb/refresh-firefox-reset-add-ons-and-settings) article in your language if it is localized.
+* Click the **Download Firefox** button to check the [thank you](https://www.mozilla.org/firefox/download/thanks) page that triggers an automatic download.
 * The [Firefox Privacy Notice](https://www.mozilla.org/privacy/firefox/) document is localized in limited number of languages.
+* Click on the **Download options and other languages** link, you will be directed to the [firefox/all](https://www.mozilla.org/firefox/all/) page.
+* Click on the **Firefox Browser support** link, you will be directed to the [SUMO](https://support.mozilla.org/products/firefox) site featuring various topics on Firefox.
 
-### [navigation.ftl](https://www.mozilla.org/)
+### [navigation_v2.ftl](https://www.mozilla.org/)
 
-This page is activated on production whether it is localized or not. It is not an independent page but a file of shared content. When clicking on any of these topics on the navigation bar, **Firefox**, **Projects**, **Developers** or **About**, you will see a drop-down window with subcategory topics. Within each of the topics, there is a description and a few links to help you dive deeper further into a topic which takes you to a different page. When reviewing the content, keep in mind the following:
+The strings in this file are shared content and are activated on production whether they are localized or not. When clicking on any of these topics on the navigation bar, **Firefox Browsers**, **Products**, **Who We Are** or **Innovation**, you will see a drop-down panel with subcategory topics. Within each of the topics, there is a description and a few links to help you dive deeper further into a topic which takes you to a different page. When reviewing the content, keep in mind the following:
 * Not all links take you to a site that’s localizable for all locales.
 * Not all products are offered in your locale.
-* Brand and product names must remain unchanged.
+* Brand and product names must remain unchanged.

src/webprojects/sumo.md

@@ -63,7 +63,6 @@ Only when there is a release or a major change will there be communications to l
 
 * File a [bug for SUMO](https://bugzilla.mozilla.org/enter_bug.cgi?product=support.mozilla.org&component=Localization). This is the quickest way to have a problem resolved.
 * Discuss it in [the SUMO l10n forum](https://support.mozilla.org/forums/l10n-forum).
-* Raise questions in the SUMO category on [Discourse](https://discourse.mozilla.org/c/sumo/).
 * Ping in [the Matrix channel](https://chat.mozilla.org/#/room/#l10n-community:mozilla.org) the l10n PM responsible for the project.
 * Through Pontoon, click the REQUEST CONTEXT or REPORT ISSUE button next to the string and make a comment. This will notify the l10n PM in charge.
 * Send a direct email to the l10n PM responsible for the project. The email address can be found in the profile in Pontoon.