codeforboston/maple

i18n Text Translations: auth components

Open

#1139 aperta il 10 mag 2023

Vedi su GitHub
 (1 commento) (0 reazioni) (1 assegnatario)TypeScript (168 fork)auto 404
Public Launchgood first issuei18n

Metriche repository

Star
 (56 star)
Metriche merge PR
 (Metriche PR in attesa)

Descrizione

Files:

components auth forgotPassword
components auth OrgSignUpModal
components auth ProfileTypeModal
components auth SignInModal
components auth SignInWithButton
components auth SignOut
components auth SocialSignOnButton
components auth StartModal
components auth TermsOfServiceModal
components auth UserSignUpModal
components auth VerifyEmailModal
  • Move user-visible text from these section into json files in the public/locales/en folder; use the next-i18next 'useTranslation' hook to connect the text from the json files
  • You'll decide how to group and name your text in a way that makes sense for your section by default, make separate json files following the structure of the project pages/folders, but feel free to diverge from that if needed.
  • make sure to get titles, headers, buttons, labels, and alt text
  • Put common words, labels, etc in the common.json file
  • At this time, don’t worry about translating content on the files in the pages folder itself at this time, but you will need to update these files to include the json files you created.
  • some pages may have already been extracted more or less into files next to or near the component files, usually with the same file name with 'content' on the end. That text needs to be moved as above, and it's up to you what to do with the content file.

Guida contributor