i18n: translate the Color Studio
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 70/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- nextjs, typescript
- Domain
- frontend, internationalization
Research direction
Start with the message catalogs in lib/i18n/messages/en.ts and es.ts, and read how useI18n() provides t() and plural() in components/layout/locale-provider.tsx. Then find the hard-coded strings in components/colors/ (tabs, aria labels, toasts) and move each one behind t() with a key in both catalogs. Done when no literal UI strings remain in components/colors/, Spanish has every key, and pnpm test passes; generated CSS and token names stay in English.
Written by the indexing model from the issue text.
Description
Summary
Translate the Color Studio (palette, shades, gradient, contrast and export tabs) into the existing locales.
Where to look
lib/i18n/messages/en.tsandes.ts: the message catalogscomponents/layout/locale-provider.tsx:useI18n()givest()andplural()- CONTRIBUTING.md, "Translating the interface"
components/colors/
Behaviour
- Leave generated output (CSS, token names, file contents) in English; translate only the interface.
Acceptance criteria
- Every visible string, aria label and toast in
components/colors/usest(). - Spanish is complete;
pnpm testpasses. - Lighthouse accessibility stays at 100 in both languages.
Getting started: fork the repo, then pnpm install and pnpm dev (Node 22+, pnpm 11, no API keys). Before opening a PR, run pnpm typecheck && pnpm test && pnpm lint && pnpm format:check && pnpm check:dashes && pnpm build. See CONTRIBUTING.md and the first contribution walkthrough.
Everything needed is in the repository. This doesn't need maintainer access, secrets or paid services. Comment below to claim it, and ask questions here any time.
- Dominant language
- TypeScript
- Stars
- 11
- Forks
- 3
- Avg merge
- 4h 2m
- Merged PRs (30d)
- 75
Getting set up
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.
More from yakew7/DesignHub
-
area: projects difficulty: medium enhancement help wanted performance v2.0.0
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
area: backgrounds difficulty: hard enhancement help wanted performance v2.0.0
Difficulty 4/5 3-5 days Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
dependencies difficulty: easy enhancement help wanted v2.0.0
Difficulty 4/5 3-5 days Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
area: mockups area: social difficulty: medium enhancement help wanted performance v2.0.0
Difficulty 4/5 3-5 days Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
area: ui difficulty: medium enhancement help wanted performance v2.0.0
Difficulty 4/5 3-5 days Newbie friendliness 68/100
Maintainers usually reply within 1 day
All issues in yakew7/DesignHub
Similar issues
-
category::task code priority::normal
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
e0ipso/strikethroo#145 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
cocos/cocos-docs#3333 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
RevenueCat/react-native-purchases#2079 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
RevenueCat/purchases-hybrid-common#2039 ·
Maintainers usually reply within 1 day
-
agent-reported area/react bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day