Deal with skill internationalisation
Open
Nobody has claimed this yet.
enhancement
epic
Need UI/UX
Priority: Medium
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 2
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 4
Description
Currently, the skills are only in one language. I propose that :
- a skill can have a FR or a EN text
- the skill will be created with the user locale that creates the skill
- If the skill has only one language, this is the one we display
- Admin will be able to add a translation to the skill via the admin page
Contributor guide
No contributing guide indexed for this repository
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 skill model, skill-creation flow, display logic, and admin page. Trace how the user locale is available when a skill is created and how existing skills are rendered. Done means skills support FR and EN text, use the creator's locale initially, fall back to the available language, and let admins add translations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- full-stack, internationalization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100