Closed Bug 1929565 Opened 11 months ago Closed 8 months ago

Write & Streamline knowledgebase content for HTTPS-First

Categories

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

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

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: freddy, Assigned: seburo3)

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. All of this is public.

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)
Firefox for Android

Select the type of request.

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

new content

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]

We are shipping HTTPS-First, which is similar to https-only.
The main difference is that https-only is optional whereas https-first is enabled by default and not as strict.

##Are the user-facing changes mentioned above for the production release, or is the feature/change experimental/ beta? (Production, Experimental or Beta) [REQUIRED]
**Note: Specify if the user-facing changes mentioned above are final, experimental, or in beta. This information is crucial for determining the appropriate support and documentation level needed. Please note that SUMO KB articles only support the production version for Firefox.

It's enabled in Nightly and Beta and we aim to release early 2025. We would like to ensure there's proper support material before we release.

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

**Note: Please confirm if these features or changes are limited to specific geographic regions and if they will be implemented gradually. Knowing this helps us tailor our documentation and support resources appropriately.

To be released world wide.

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

**Note: 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].

Train release.

What is the anticipated release date? [REQUIRED]

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

Firefox 133 or 134. Early 2025.

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

Ideally, yes

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]

We have a release plan in https://docs.google.com/document/d/1NfKxh9V8aj-H9sdCb7jz6yYpmpVKz895Juz_PYdJFSA/edit that should cover a lot, but happy to answer question in follow up.

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]

There's a preference dom.security.https_first that can be flipped to true to test this feature.

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]

I can act as an approver but would also be happy to help with content and foreseeing the issues we may want to highlight and address upfront.

Please can I pick this one up?

Assignee: nobody → seburo3
Status: NEW → ASSIGNED
Summary: Write & Streamline knowledgebase content for HTTPS-First → Write & Streamline knowledgebase content for HTTPS-First [VALIDATE - V133/V134]

(In reply to Seburo from comment #1)
Thanks for jumping in to help, Paul! Just let me know if there’s anything you need from my end to get this going.

Hey Paul, just checking in on the status of this. Let me know if there’s anything you need from me to get these updates for Desktop and Android out!

Flags: needinfo?(seburo3)
Summary: Write & Streamline knowledgebase content for HTTPS-First [VALIDATE - V133/V134] → Write & Streamline knowledgebase content for HTTPS-First

Hi freddy. Would welcome your feedback on my draft at

https://docs.google.com/document/d/1kbgNP9vo2SOWfLuLt_frGDjnnHkJy-KRJPQGAUVkE4w/edit?usp=sharing

(This has all the markup ready for Kitsune, subject to any tidying up as I load it.)

Flags: needinfo?(seburo3) → needinfo?(fbraun)

Quick update to mention that I understand that this is an experiment to only 1% of users.

I am currently looking to rewrite sections of my draft this week.

Depends on: 1934587

Hi Simon. Thank you for your time the other night. Would welcome your sign off on this draft:

https://docs.google.com/document/d/1kbgNP9vo2SOWfLuLt_frGDjnnHkJy-KRJPQGAUVkE4w/edit?usp=sharing

Flags: needinfo?(sfriedberger)

Thanks, Paul!

It looks like we really do need to explain the exception mechanism and wait for the blocking bug to resolve to include some screenshots.

Flags: needinfo?(sfriedberger)

Important: Please use this placeholder article when publishing: https://support.mozilla.org/kb/https-upgrades

For the record, a proposed new article was just submitted by sfriedberger with the title HTTPS-First - Upgrades to Secure Connections with content that includes "=WORK IN PROGRESS= NOT ready for review! DO NOT PUBLISH!". See https://support.mozilla.org/en-US/kb/https-first/revision/291212

Flags: needinfo?(seburo3)
Flags: needinfo?(seburo3)

I do not have any idea what is going on - my understanding is that my draft is on hold (not submitted for now) awaiting a product decision.

(For the record) KB article update submitted by sfriedberger (content includes "=WORK IN PROGRESS= NOT ready for review! DO NOT PUBLISH!"). See: https://support.mozilla.org/en-US/kb/https-upgrades/revision/291216

Sorry, I did mean to mention that here. I worked on Paul's draft a bit more and then submitted it just to get familiar with SUMO a bit.

This is the one based on Paul's work for HTTPS-First: https://support.mozilla.org/en-US/kb/https-first/history#preview
And this is a more generic one that I want to link to from the preferences, for people who are wondering why they are getting upgraded: https://support.mozilla.org/en-US/kb/https-upgrades/history#preview

I asked my colleagues to review and that's why I didn't request an official review yet.

Flags: needinfo?(fbraun)

Hi, Simon,
I've been with Mozilla Support since the beginning. If you want to get more familiar with writing and editing SUMO KB articles, see this article: https://support.mozilla.org/en-US/kb/writing-guide-knowledge-base-articles. Note the article Title section. We try to use sentence-style capitalization in both article and section heading titles :)

Some feedback about the connection upgrades article, generally I think it reads quite well and gives a good overview.

  • This may be a bit late, but the slug https-upgrades in the URL is a bit confusing. That is the name of a standards proposal for the behavior we call "HTTPS-First". Maybe connection-upgrades would be better, as that also seems to be the actual title of the support article.
  • Today, most websites support HTTPS connections so this should only cause problems in exceptional cases. sounds like a website not supporting HTTPS already is a "problem", which is not the case. Perhaps reword that a bit.
  • If the browser cannot know that the web server supports HTTPS connections. It can still attempt an upgrade, since HTTPS is widely supported this is often successful. Did you mean to put a comma in between those sentences?

Thank you, Alice! Could you please check if the changes I made are what you were looking for? And it seems I cannot change the title or slug of the article that Lucas created.

Flags: needinfo?(alice.wyman)

Simon, I'm assuming that HTTPS-First is the feature name so it should be written as-is in the article title and content.

I could change the title for the proposed new article https://support.mozilla.org/en-US/kb/https-first to either "HTTPS-First upgrades to secure connections" or "HTTPS-First - Upgrades to secure connections" to remove unneeded capitalization. I would also change "Secure Site" to "Secure site" in the second heading and make a few other edits but I don't know if that's the article that will be used here.

As for the https://support.mozilla.org/en-US/kb/https-upgrades article title and slug, only KB reviewers can change the article title and slug, after an article is approved. See https://support.mozilla.org/en-US/kb/edit-knowledge-base-article#w_edit-description-reviewers-only
I'll leave that to Lucas since it involves in-product links.

Flags: needinfo?(alice.wyman) → needinfo?(lsiebert)

Revision id: 291434 looks good for the generic article!

Given that this is a bug I am working on - when will a draft be ready for me to look at and get into Kitsune?

(from comment #18)

As for the https://support.mozilla.org/en-US/kb/https-upgrades article title and slug, only KB reviewers can change the article title and slug, after an article is approved. See https://support.mozilla.org/en-US/kb/edit-knowledge-base-article#w_edit-description-reviewers-only
I'll leave that to Lucas since it involves in-product links.

The title of the article that Lucas created is now Firefox connection upgrades - HTTP to HTTPS. See the discussion here on the changes made to the article title: https://support.mozilla.org/en-US/kb/https-upgrades/discuss/12772

(In reply to Lucas Siebert from comment #9)

In-product redirects
Desktop in-product link: https://support.mozilla.org/1/firefox/%VERSION%/%OS%/%LOCALE%/https-upgrades
Android in-product link: https://support.mozilla.org/1/mobile/%VERSION%/%OS%/%LOCALE%/https-upgrades-mobile
Placeholder article: https://support.mozilla.org/kb/https-upgrades
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

Lucas, could you make sure that we can also use this form of link for the HTTPS-First article? That is needed for Bug 1907518, and right now https://support.mozilla.org/1/firefox/136.0a1/Linux/en-US/https-first displays an 404 error.

Also, is it still possible to change the slug for the other article from https-upgrades to connection-upgrades? If not, that is also okay.

Can we get a sentence at the end of the first paragraph of the https-first article that points to the connection-upgrades article?
Something like "There are other technical reasons that may impact how Firefox is upgrading connections" pointing to https://support.mozilla.org/en-US/kb/https-upgrades at the bottom

(Please someone redirect me if this is not the best place to ask :))

Flags: needinfo?(lsiebert)

(In reply to Frederik Braun [:freddy] from comment #25)

Can we get a sentence at the end of the first paragraph of the https-first article that points to the connection-upgrades article?
Something like "There are other technical reasons that may impact how Firefox is upgrading connections" pointing to https://support.mozilla.org/en-US/kb/https-upgrades at the bottom

I added a Related content section to the end of the article. Lucas, can you review? See https://support.mozilla.org/en-US/kb/https-first/history

Status: RESOLVED → REOPENED
Resolution: FIXED → ---

No feedback from Lucas so I approved my revision to https://support.mozilla.org/en-US/kb/https-first/ and marked it ready to localize.

Flags: needinfo?(lsiebert)
Status: REOPENED → RESOLVED
Closed: 9 months ago → 8 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.