Fix: Homepage Translations Not Displaying Properly#164
Merged
Conversation
|
@ankitjhagithub21 is attempting to deploy a commit to the gyanthakur's projects Team on Vercel. A member of the Team first needs to authorize it. |
There was a problem hiding this comment.
Great job, @ankitjhagithub21! Thanks for creating the pull request.
Soon the maintainers/owner will review it and provide you with feedback/suggestions.
Make sure to star this awesome repository and follow the account!
Gyanthakur
approved these changes
Oct 19, 2025
|
The latest updates on your projects. Learn more about Vercel for GitHub.
💡 Enable Vercel Agent with $100 free credit for automated AI reviews |
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.
📝 Description
This pull request fixes the issue where translation keys (e.g.,
homepage.hero_title,homepage.hero_description) were displayed instead of their corresponding translated values on the homepage.✨ What Was Happening
Previously, the homepage was rendering translation keys directly because the localization setup was incomplete and not integrated properly with the page components.
💡 What Was Done
next-intlfor handling internationalization.next-intlprovider in the app layout to wrap all pages.messages/directory.useTranslations('homepage')for fetching localized strings.Fixes: #163
🔍 Type of Change
✅ Checklist
📸 Screenshots (Before & After)
❌ Before
Translations displayed as raw keys:
✅ After
Translations are correctly rendered using localized text:
💬 Additional Comments
next-intlacross the app, improving scalability for future translations.enandfrlocales.