Internationalize Views Using Existing I18n Setup #141
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
- Replaced hardcoded text with localization using `I18n.t` across views - Improved accessibility and translated placeholders, labels, and buttons - Updated layouts and partials for cleaner and more consistent designs - Enhanced support for multi-language user interfaces
adamswonder
approved these changes
Dec 17, 2025
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.
Summary
This PR internationalizes views only, building on the existing Internationalization implementation in the system.
What changed
Why
The Internationalization framework was already in place; this PR applies it to views to ensure user-facing content is properly localized and easier to maintain.
Testing
?locale=swto URLs to verify Swahili translations?locale=frto URLs to verify French translations