Repository navigation
docs: a README that tells each feature with its own Store screenshot - #55
Merged
Merged
Conversation
…rch terms people use for a browser picker
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 README follows the same layout as Tisty's. The Store hero goes at the top, followed by a list of why people choose LinkUnbound and the sections Why I Built This and Who Is This For. Each feature has its own subsection with its screenshot: the picker, rules, browsers and profiles, settings and privacy. Headings and image descriptions use the words people search for when looking for a browser picker. Two picker captures that nothing used any more are removed.