docs: refine public README badges and release links#27
Merged
Conversation
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
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.
Change Type
Summary
Refined the public README presentation for the
.public.viewer-saverrelease snapshot.Changes included:
build passingandMaintained? yesContributions welcomeand aligned the badge set to a cleaner 5-badge rowReleaseslink so users can find the latest public build more easilyReleaseslink into theLive Demosection for a more natural placementThis makes the README feel cleaner and helps users find the right download location without overloading the top section.
Related Issue
Fixes #
Testing
Notes:
README.mdandREADME-KR.mdrender cleanly after the update.Review Notes
Please focus review on:
Releaseslink placement in theLive Demosection is more natural than the previous top-of-file placement