Update New Tab Content FAQ Page [Desktop V130]
Categories
(support.mozilla.org :: Knowledge Base Content, task)
Tracking
(firefox130+ fixed)
People
(Reporter: jimthomas, Assigned: lsiebert)
References
Details
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.
Content access restriction: 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
Attention: Any content not marked as confidential will be accessible to both NDAd and non-NDAd contributors with a Bugzilla account. Drafts for non-confidential content will also follow the same access policy, being open to comments for anyone with the link. Non-confidential Bugzillas can benefit from contributions by community contributors, while confidential Bugzillas will be handled exclusively by staff.
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 Desktop (Windows)
Firefox for Desktop (macOS)
Firefox for Desktop (Linux)
Select the type of request.
Choose one or more below and delete others. [REQUIRED]
Both:
KB content update/ new content
In-product link request
Please summarize the request, emphasizing any user-facing changes. Include historical context or background information if it helps users understand the new feature or changes. [REQUIRED]
Context Here: https://docs.google.com/document/d/1u2m1Ko9Kdu0gDOVcC61nBp_CZJNKMIuOgHkBeSVRf2E/edit
We would like to replace the in-product FAQ link (currently https://support.mozilla.org/en-US/kb/pocket-recommendations-firefox-new-tab) with a new one that more generally covers content in new tab (not necessarily from pocket).
##Are the user-facing changes mentioned above final for the production release, or is the feature experimental or in beta? (Final, Experimental or Beta) [REQUIRED]
Final
Please indicate if this is an on- or off-train release. If applicable, add the product version number to the end of the Summary field using the format: Summary [Product V123]. If this is an off-train release, please use the format: Summary [Product off-train] [REQUIRED].
On-Train Firefox 130
What is the anticipated release date? [REQUIRED]
Note: Content is typically published at, or within, 48 hours of the release.
Sept 3, 2024
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
We need the link by Aug 1 to update in the code.
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
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]
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]
Yes, Jim Thomas
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
Comment 1•1 year ago
•
|
||
KB content update/ new content
In-product link request
<snip>
We would like to replace the in-product FAQ link (currently https://support.mozilla.org/en-US/kb/pocket-recommendations-firefox-new-tab) with a new one that more generally covers content in new tab (not necessarily from pocket).
For the record, the in-product link is the "Learn more" link next to "Thought-provoking stories" on the New Tab page. The link goes to https://getpocket.com/firefox/new_tab_learn_more ...which redirects to https://support.mozilla.org/en-US/kb/pocket-recommendations-firefox-new-tab
Comment 2•1 year ago
|
||
(from comment #1)
For the record, the in-product link is the "Learn more" link next to "Thought-provoking stories" on the New Tab page. The link goes to https://getpocket.com/firefox/new_tab_learn_more ...which redirects to https://support.mozilla.org/en-US/kb/pocket-recommendations-firefox-new-tab
There's another in-product link in the Firefox settings Home panel (about:preferences#home page). The Recommended stories "How it works" link also goes to https://getpocket.com/firefox/new_tab_learn_more ...which redirects to https://support.mozilla.org/en-US/kb/pocket-recommendations-firefox-new-tab
We'd like to update the url in the code before the soft code freeze this week. Is it possible to generate or agree on the permalink on support.mozilla.org this week before the content is ready? Maybe we could add a placeholder page for testing.
| Assignee | ||
Comment 4•1 year ago
|
||
(In reply to Jim T from comment #3)
We'd like to update the url in the code before the soft code freeze this week. Is it possible to generate or agree on the permalink on support.mozilla.org this week before the content is ready? Maybe we could add a placeholder page for testing.
Hey Jim, sure thing! Here’s the info you’ll need:
- In-product link: https://support.mozilla.org/1/firefox/%VERSION%/%OS%/%LOCALE%/new-tab
- Placeholder article: https://support.mozilla.org/en-US/kb/new-tab
- Guide to linking to SUMO articles: https://support.mozilla.org/en-US/kb/a-guide-to-linking-to-support-articles#w_in-product-links-to-sumo
| Assignee | ||
Comment 5•1 year ago
|
||
Updated•1 year ago
|
| Assignee | ||
Comment 6•1 year ago
|
||
(In reply to Jim T from comment #3)
We'd like to update the url in the code before the soft code freeze this week. Is it possible to generate or agree on the permalink on support.mozilla.org this week before the content is ready? Maybe we could add a placeholder page for testing.
Hey Jim! Thanks for the solid draft your team put together—it gave us a great foundation to work from. We’ve made a few tweaks to align it with SUMO’s guidelines and reordered some sections to better match how users typically interact with SUMO content. The goal was to make it as smooth and user-friendly as possible. Everything’s polished up now and ready for your review!
https://docs.google.com/document/d/1Aoi_0KMuOqbVpCCk77IDiXkaC1cm6v18pyIkU7dr-Z0/edit
Just checking: after this is live, do you want us to take down https://support.mozilla.org/en-US/kb/pocket-recommendations-firefox-new-tab, or can they both coexist in the KB?
Comment 7•1 year ago
|
||
Lucas, what do you mean by take down https://support.mozilla.org/en-US/kb/pocket-recommendations-firefox-new-tab? Move to Administration category? Archive (mark Obsolete)? Redirect to the new article? Please don't delete the article without editing the articles that link there to remove the links - see https://support.mozilla.org/en-US/kb/pocket-recommendations-firefox-new-tab/links
| Assignee | ||
Comment 8•1 year ago
|
||
The updated content is live! https://support.mozilla.org/en-US/kb/new-tab
| Assignee | ||
Comment 9•1 year ago
|
||
(In reply to Alice Wyman from comment #7)
Lucas, what do you mean by take down https://support.mozilla.org/en-US/kb/pocket-recommendations-firefox-new-tab? Move to Administration category? Archive (mark Obsolete)? Redirect to the new article? Please don't delete the article without editing the articles that link there to remove the links - see https://support.mozilla.org/en-US/kb/pocket-recommendations-firefox-new-tab/links
Hey Alice! Thanks for pointing that out. By “take down,” I just meant moving it to the Administration category or marking it as Obsolete—not deleting it. We’ll definitely update the links before doing anything. Appreciate you keeping an eye on this and helping us out!
Updated•1 year ago
|
Comment 10•1 year ago
|
||
(In reply to Lucas Siebert from comment #9)
(In reply to Alice Wyman from comment #7)
Lucas, what do you mean by take down https://support.mozilla.org/en-US/kb/pocket-recommendations-firefox-new-tab? Move to Administration category? Archive (mark Obsolete)? Redirect to the new article? Please don't delete the article without editing the articles that link there to remove the links - see https://support.mozilla.org/en-US/kb/pocket-recommendations-firefox-new-tab/links
Hey Alice! Thanks for pointing that out. By “take down,” I just meant moving it to the Administration category or marking it as Obsolete—not deleting it. We’ll definitely update the links before doing anything. Appreciate you keeping an eye on this and helping us out!
Hi, Lucas,
The Firefox settings Home panel (about:preferences#home page) Recommended stories "How it works" link still goes to https://getpocket.com/firefox/new_tab_learn_more ...which redirects to https://support.mozilla.org/en-US/kb/pocket-recommendations-firefox-new-tab so it might be better not to mark it obsolete or move it to the Administration category for the time being.
Description
•