Repository navigation
Guide users through the public portal and QR backups; prepare v2.0.0 - #6
Merged
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
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 now directs visitors to the public EvPortal link and walks them through saving car shortcuts on a phone, editing them there and sending them back by QR. It explains Add versus Restore, uses the actual button labels and retains a small contribution link. Local setup, deployment and SEO instructions remain in the contributor documentation. The French usage guide follows the same user-focused approach.
Add the 2.0.0 changelog and document the annotated-tag/release convention. The application and root lockfile already declare version 2.0.0; runtime files and generated pages are unchanged. The stable v2.0.0 tag and GitHub release will point to the merged commit after the checks and Pages deployment succeed.
Validation: documentation paths and translated button labels reviewed against the interface; generated SEO check and whitespace check pass. No application behavior changed.