mirror of
https://github.com/runkids/skillshare.git
synced 2026-11-20 20:34:19 +00:00
The doctor --json output gained a `suggestions` field (see eb99118d), but the web Health Check page silently dropped it. Render the remediation suggestions under each check's expandable detail block.
- Add optional `suggestions` to the DoctorCheck type
- Render suggestions list in CheckRow; make rows expandable when only suggestions are present
- Add `doctor.suggestions` i18n key across all 11 locales
Dashboard Translations
The dashboard uses one JSON file per locale in ui/src/i18n/locales/.
Files
en.jsonis the canonical source of keys.- Every other locale must contain exactly the same keys.
- Run the UI test suite after editing translations; the parity test checks missing keys, extra keys, and placeholder mismatches.
Key Style
- Use dot-separated keys grouped by area, for example
layout.nav.dashboardorapi.error.not_found. - Keep keys stable. Rename a key only when updating every locale and all call sites.
- Prefer reusable labels under
common.*only when the same text means the same thing in every context.
Tone
- Keep translations natural and conversational, as if they are product UI copy a user sees while working.
- Be concise. Labels should fit buttons, nav items, badges, and dialogs without wrapping awkwardly.
- Avoid stiff literal translations, internal engineering phrasing, jokes, and slang.
- For errors, explain what happened in plain language. Keep raw technical details in placeholders or fallback text.
Placeholders
- Use named placeholders with braces:
Updated {name}. - Placeholder names must match across every locale.
- Do not translate placeholder names.
Do Not Translate
- Product and command names such as
skillshare,skillshare ui, Git, and CodeMirror. - User-owned data: file paths, skill names, repo names, branch names, commit messages, audit rule messages, and terminal output.
- API codes such as
target.not_found; translate the text mapped to those codes instead.