Repository navigation
Add BeatGEO interface languages, multilingual READMEs and cover - #15
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.
Add a persistent English/Chinese interface switch across setup, monitoring, settings and reports, while preserving collected answers and user-entered content. Introduce English, Chinese, Japanese, German and Korean READMEs and the approved dark cover illustrating brand mentions and website citations.
Validation: Biome passed. The implementation acceptance recorded in docs/beat-geo/validation.md includes web type checks, 568 web unit tests, production build, two language-switch browser regressions, and nine inspected brand routes. These are prior implementation checks; the final cover revision changes images only. CI will also run workspace quality and isolated PostgreSQL integration checks.
No database migration, model call, deployment or upstream publishing workflow is introduced.