Repository navigation
docs: complete bilingual adoption and product homepage paths - #318
Merged
Merged
Conversation
Preserve concurrent runtime work and existing technical owners. Clarify current platform/release scope, first use, data recovery, privacy and free/paid availability. Customer navigation points to usage rather than internal launch hypotheses. Validation: static links, HTML/script syntax, public release asset names and browser previews. No runtime acceptance is claimed. Source: eaaf341 Family policy read: df8680858012e8960d85410ff96c0332dca71827
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.
Give new English- and Chinese-speaking users one adoption path from the homepage and README: framework fit, first useful application, platform maturity, compatibility, upgrades and support. Keep the existing API/protocol and implementation handoff owners; mobile runtime foundations remain distinct from a delivered application flow.
The documentation commit is based on eaaf341, including the concurrent Apple RVT1 gateway work. No runtime files, dependency pins or acceptance requirements are changed. Language choices on the homepage are real keyboard-operable buttons.
Validation: paired guide links, HTML tag/anchor checks, inline JavaScript syntax and browser preview. This is documentation/site verification, not new three-platform runtime evidence. Family policy read: df8680858012e8960d85410ff96c0332dca71827.