Restore the dry privacy copy, and keep the FAQ in step - #57
Merged
Conversation
The privacy lede had become a summary of the whole page. Put the two-sentence lede back, keep the version-check facts, and stop the FAQ and changelog from naming GitHub as the check host or claiming no stable release exists.
Release notes are PR markdown dumped into a pre block. Render headings, lists, code, and links, and join the 72-column wraps. Split the privacy version-check wall into what the user can do and what the request sends.
Expanded release notes ran into the next version. They now sit in an indented, quieter panel so the version row stays the landmark. The privacy version-check is a short lead-in plus the four steps as bullets.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The privacy lede had become a summary of the whole page. That was the update-check work in #47: the facts belonged, the extra reassurance did not.
This puts the two-sentence lede back (telemetry, then what the page is), keeps the version-check facts in shorter sentences, and names the hosts the client actually talks to. The home page now reads stable.json first, so the website section says that instead of claiming every download click hits api.github.com.
The FAQ and changelog had the same drift: they still named GitHub as the check host, and they still said no stable release exists. Both are now false. The FAQ account answer now points at this site, and the changelog no-JS note no longer pretends 0.9.5 is not out.
Home, Guide, Compare, Contribute, Shortcuts, and the import format are left alone. Home is the campaign, Guide is the session stories; the others were already in this voice.