Skip to content

docs: route SUPPORT.md at the two orientation threads, and stop claiming Q&A is empty - #2350

Merged
laurentiu021 merged 1 commit into
mainfrom
docs/support-qa-claim
Sep 18, 2026
Merged

laurentiu021 merged 1 commit into
mainfrom
docs/support-qa-claim

Conversation

@laurentiu021

Copy link
Copy Markdown
Owner

Why

Seeding a Q&A thread made a sentence in SUPPORT.md false: "nobody has asked anything there yet". That is a live count written into prose, so it was going to expire the moment the thing it described succeeded. Reworded to something that cannot expire rather than patched with a new number.

What changed

Checks

Refs #1665

…ing Q&A is empty

Seeding a Q&A thread made a sentence in this file false, which is the point worth
recording: "nobody has asked anything there yet" is a live count written into prose,
so it was going to expire the moment the thing it described succeeded. Replaced with
something that cannot — "quiet enough that a question gets an answer rather than
being buried" — rather than patched with a new number.

Two threads now cover the same ground this file does, so it links them at the top:
Start here is the same routing plus what to expect and how long it takes, and
Roadmap answers the three recurring ones (unsigned download, no telemetry, no Store
build). Linking them from the docs also means they route people whether or not they
are pinned, which matters because pinning a discussion is a web-UI-only action.

The SmartScreen row gains the Q&A thread beside the README anchor, for readers who
would rather have it as a question and an answer than as a section.
@laurentiu021
laurentiu021 merged commit 12d211d into main Sep 18, 2026
6 checks passed
@laurentiu021
laurentiu021 deleted the docs/support-qa-claim branch September 18, 2026 06:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant