docs(i18n): introduce global localization and multi-language framework#1613
Open
omiaydin1 wants to merge 1 commit into
Open
docs(i18n): introduce global localization and multi-language framework#1613omiaydin1 wants to merge 1 commit into
omiaydin1 wants to merge 1 commit into
Conversation
Collaborator
🟡 Heimdall Review Status
|
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
2 participants
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.
What changed? Why?
This PR adds
i18n-LOCALIZATION.mdto introduce a global localization framework. Base is expanding rapidly worldwide, and developer hubs in regions like Turkey, LATAM, and Asia need a structured way to translate core documentation. This framework prevents repository clutter by setting clear guidelines for automated i18n/localization subdirectories.Notes to reviewers
This is an initial documentation blueprint designed to organize community-driven translations. It includes formatting standards and technical guidelines to maintain code integrity across different languages.
How has it been tested?
The Markdown file layout, formatting, and link structures have been verified to render properly on GitHub.