-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Task]: Setup i18n with next-intl #1657
Comments
This approach was taken care of in #1760 |
Noting from @rylew1 comment on #1760 (comment) that we could add the metadata to the layout once we are using the page strings. |
I started this locally, will try and push a branch before cob. |
I have this working, needs a lot of clean up https://github.com/HHS/simpler-grants-gov/tree/acouch/issue-acouch-i18n/frontend |
## Summary Fixes #1657 ### Time to review: __30 mins__ ## Changes proposed Enables next-intl to enable translation for app pages. This sets up next-intl and enables it for the search page and app not found page. This adds one other app component. There are three which will be removed for #1361 . ## Context for reviewers The strings being declared and injected is still ugly and not addressed with this, but will be fixed with #1361 . The `[locale]` folder has not been setup yet b/c it took over the full routing for the site. That folder will be setup in #1361 .
Summary
setup i18n with next-intl
Acceptance criteria
Internationalization works on app router pages
The text was updated successfully, but these errors were encountered: