codeforboston / codeforboston/maple

i18n Text Translations: publish components

Open
#1,141 2 comments 0 reactions 1 assignee Claimed by @hanboyu View on GitHub
good first issue i18n Public Launch
Dominant language
TypeScript
Stars
56
Forks
175
Avg merge
2d 5h
Merged PRs (30d)
13

Description

Files:

components | Publish/Panel | ArchiveTestitmonyConfirmation
-- | -- | --
components | Publish/Panel | ctas
components | Publish/Panel | ThankYouModal
components | Publish/Panel | YourTestimony
components | Publish | ChooseStance
components | Publish | content
components | Publish | ProgressBar
components | Publish | PublishInfo
components | Publish | PublishTestimony
components | Publish | QuickInfo
components | Publish | SelectLegislators
components | Publish | SelectRecipients
components | Publish | SendEmailButton
components | Publish | ShareTestimony
components | Publish | SubmitTestimony
components | Publish | SyncStatus
components | Publish | TestimonyPreview
components | Publish | WriteTestimony

- 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.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.