[10k]: Internationalization framework

[widal001]

Description

Implement an internationalization framework (to support multiple languages) we believe can scale as the site scales.

Invest early in this. It is much easier to build internationalization in from the beginning than it is to add support for it to an existing codebase.

Dependencies

• [10k]: Front-end planning #49
• [30k]: Content management system (CMS) #75

Sub-Tasks

• TODO

Definition of Done

• TODO

[lucasmbrown-usds]

Let's check in with @andycochran and @acouch et al to see about the right order of operations for this. Does it make sense to build the i18n framework into the foundational UI before we add any other content? Sometimes it's harder to add i18n later to an existing site. But I defer to y'all!

[andycochran]

Very likely we can get this one for free. Tho we haven't discussed frontend planning with the group yet, one solution Nava has been thinking of and discussing internally would include i18n out-of-the-box.

[acouch]

@lucasmbrown-usds We have a template that includes Next.js i18n routing. Agree it would be preferable to include that in the initial front-end setup #110 .

[lucasmbrown-usds]

Awesome, great news @andycochran @acouch !

[acouch]

We have adopted an i18n library for the front-end. It is documented here: https://github.com/HHS/grants-equity/blob/main/documentation/frontend/internationalization.md