1947157 - Move linux security warning content into own page

Status: RESOLVED FIXED

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

Description

[:gerard-majax]

The content was added in https://support.mozilla.org/en-US/kb/install-firefox-linux#w_security-features-warning but the inability to link directly to the anchor is really limiting, so we could welcome a dedicated page.

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

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 Desktop (Linux)

Select the type of request.

Choose one or more below and delete others. [REQUIRED]
KB content update/ new content
In-product link request
Existing link is at https://searchfox.org/mozilla-central/rev/bc00d156c8a5452689cd66cbce30fe10c6594977/toolkit/content/aboutSupport.js#1471

Please summarize the request, emphasizing any user-facing changes. Include historical context or background information if it helps users understand the new features or changes. [REQUIRED]

Moving the content of the anchor https://support.mozilla.org/en-US/kb/install-firefox-linux#w_security-features-warning into its own page

##Are the user-facing changes mentioned above for the production release, or is the feature/change experimental/ beta? (Production, Experimental or Beta) [REQUIRED]
All channels

Are the new features or changes region-specific? Are they going to be released in a gradual rollout? [REQUIRED]

No

Please indicate if this is an on- or off-train release [REQUIRED]

N/A ?

What is the anticipated release date? [REQUIRED]

When it's done ?

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

N/A

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

Localization is already done, e.g. french https://support.mozilla.org/fr/kb/installer-firefox-linux#w_avertissement-concernant-les-fonctionnalites-de-securite
So we can just move the localized content as well (or let contributors know they just have to resubmit)

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

N/A

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

N/A

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

N/A

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

Comment 1

[Seburo]

Please can I pick this one up?

Comment 2

[Lucas Siebert]

Placeholder article: https://support.mozilla.org/en-US/kb/linux-security-warning
In-product redirect: https://support.mozilla.org/1/firefox/%VERSION%/%OS%/%LOCALE%/linux-security-warning
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

Comment 3

[:gerard-majax]

Attachment: Bug 1947157 - Use In-Product link for dedicated usernamespaces fix page r?jld!

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/769d3291c8e4
Use In-Product link for dedicated usernamespaces fix page r=jld

Comment 5

[Sandor Molnar[:smolnar]]

https://hg.mozilla.org/mozilla-central/rev/769d3291c8e4

Comment 6

[:Gijs (he/him)]

Is there some other bug to update the placeholder SUMO page to point to the content in comment 0? Right now I saw https://support.mozilla.org/en-US/kb/linux-security-warning?as=u&utm_source=inproduct on a local build which just says "Placeholder bug 1947157" which isn't quite as informative. :-)

Comment 7

[Lucas Siebert]

(In reply to :Gijs (he/him) from comment #6)

Is there some other bug to update the placeholder SUMO page to point to the content in comment 0? Right now I saw https://support.mozilla.org/en-US/kb/linux-security-warning?as=u&utm_source=inproduct on a local build which just says "Placeholder bug 1947157" which isn't quite as informative. :-)

Hey Gijs! I accidentally cleared the previous need-info. The placeholder article was created when we got the ticket, but the content hasn’t been moved over yet. Paul has kindly offered to help out. Dayana, could you assign this to Paul and loop in Jo T / Kiki? Let me know if you need anything to get this moving. Thanks!

Comment 8

[Dayana]

(In reply to Seburo from comment #1)

Please can I pick this one up?

Hello! This has been assigned to you.

Comment 9

[Dayana]

Hey Jo! Could you help us validate and add this to the Asana Content Roadmap? Once that's done, cross-link the task in a comment here. Thanks!

Comment 10

[:gerard-majax]

Can this be moved quickly?

Comment 11

[:gerard-majax]

People are now getting onto the place holder and nightly moves to beta soon

Comment 12

[Seburo]

Are we keeping the warning on the existing page and then just duplicating that into the new page? That could be better than having some kind of pointer to a second page and means more users will see it in the context of the install article.

If we are going to duplicate the content (not normally a fan of this, but could be the better approach in this instance), should be easy enough for me to look at tonight (what do we want to title this new article?). If we want to use some kind of link, I guess we could use text like "Please see this article (link) to guidance around security warnings."..?

Comment 13

[:gerard-majax]

(In reply to Seburo from comment #12)

Are we keeping the warning on the existing page and then just duplicating that into the new page? That could be better than having some kind of pointer to a second page and means more users will see it in the context of the install article.

If we are going to duplicate the content (not normally a fan of this, but could be the better approach in this instance), should be easy enough for me to look at tonight (what do we want to title this new article?). If we want to use some kind of link, I guess we could use text like "Please see this article (link) to guidance around security warnings."..?

Whatever is the easiest, I know several people had difficulties finding the information on the long install page because of the lack of correct anchor link, so if we just link to the new page from there that would be fine for me. But if you want to keep it duplicated for some time it's also fine. What I dont like is people landing on the placeholder page with no information :(. And there's mostly no reason for duplicated content to diverge.

Comment 14

[Seburo]

Lets duplicate the warning in the new page.

What do you want the title of the new page (which just has the warning) to be?

"Linux Security Features Warning" ..?

Comment 15

[:gerard-majax]

(In reply to Seburo from comment #14)

Lets duplicate the warning in the new page.

What do you want the title of the new page (which just has the warning) to be?

"Linux Security Features Warning" ..?

That would work for me, is it complicated to change it after if we want to improve later?

Comment 16

[Seburo]

Very easy to change it later as required.

Should be able to publish a draft for you to approve here later tonight.

Comment 17

[Seburo]

Draft for your approval - https://docs.google.com/document/d/1BcyuIi0CfrjX6XWzE2Iav4plN94_GFsnwTH8WcuLkAM/edit?usp=sharing

If you are happy with this, I will get Kitsune updated and passed to SUMO staff to approve. Once approved the content will go to SUMO L10n to localise.

Comment 18

[:gerard-majax]

Well you copy/pasted, so I dont think there's any mistake, I'm reading the same text as the original content page, that looks fine by me :)

Comment 19

[Seburo]

Ready for review - https://support.mozilla.org/en-US/kb/linux-security-warning/history#preview

Comment 20

[Alice Wyman]

(In reply to :gerard-majax from comment #15)

(In reply to Seburo from comment #14)

Lets duplicate the warning in the new page.

What do you want the title of the new page (which just has the warning) to be?

"Linux Security Features Warning" ..?

That would work for me, is it complicated to change it after if we want to improve later?

The current title for this article, "Linux Security Features Warning" contains unneeded capitalization that doesn't conform to KB standards. See Writing guide for Knowledge Base articles under Title.

If you later want to change the title and just remove unneeded capitalization, no redirect is created, causing broken wikilinks (see bug 1867499). I would change the article title to something like "Firefox security features warning on Linux" or maybe, "Firefox installation on Linux - Security features warning", since this article would likely be included as a link from the Install Firefox on Linux article section, Security features warning.

Comment 21

[:gerard-majax]

fine by me

Comment 22

[Alice Wyman]

(In reply to :gerard-majax from comment #21)

fine by me

Which is fine? Change the article title to "Firefox security features warning on Linux"?

P.S. The KB article URL, https://support.mozilla.org/en-US/kb/linux-security-warning will remain the same (same slug); only the title will change.

Comment 23

[:gerard-majax]

Your suggestion

Comment 24

[:gerard-majax]

This is still empty ?

Comment 25

[Seburo]

I am waiting for SUMO staff to review my edits.

Comment 26

[Alice Wyman]

See https://support.mozilla.org/en-US/kb/linux-security-warning/history (I also have a revision that's pending review).

Comment 27

[Dayana]

Dayani, could you help review and approve these submissions? Thanks!

Comment 28

[Dayani Galindo]

Reviewed changes and approved content.

Comment 29

[Alice Wyman]

I submitted a revision to the Install Firefox on Linux article that's pending, to replace most of the content from the "Security features warning" section with a link to the new article. Otherwise, duplicated content may change in one article but not in the other, as updates are made. See https://support.mozilla.org/en-US/kb/install-firefox-linux/history and https://support.mozilla.org/en-US/kb/install-firefox-linux/revision/294296

Comment 30

[Seburo]

With the the article being so useful, the plan was to keep the warning on both pages for increased visibility regardless of route taken to access it.

Comment 31

[Alice Wyman]

I got a thumbs-up from gerard-majax (see comment 29). I'm fine whatever Dayani decides.

Comment 32

[Dayani Galindo]

(In reply to Alice Wyman from comment #31)

I got a thumbs-up from gerard-majax (see comment 29). I'm fine whatever Dayani decides.

I agree, thanks for stepping up.