Add messaging to components around i18n support so users are aware of what's "translated"
Open
Nobody has claimed this yet.
engineering
raccoon-gang
- Dominant language
- JavaScript
- Stars
- 140
- Forks
- 100
- Avg merge
- 1h 3m
- Merged PRs (30d)
- 30
Description
- Mark a component as internationalized (i18n supported) in the markdown frontmatter so its available in Gatsby's GraphQL layer.
- In the "Settings" sheet, read the i18n-supported component list to display a tooltip of which components are supported by the language switcher.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the component markdown frontmatter consumed by Gatsby's GraphQL layer and the Settings sheet's language-switcher UI. Mark supported components in the frontmatter and use that list for the tooltip; done means the GraphQL data is available and the Settings sheet identifies which components are supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- frontend, internationalization
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100