Add support for i18n

Open
#6,156 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
frontend, internationalization

Research direction

The issue names no files, tests, entry points, supported locales, or translation scope. Start by mapping the frontend's user-facing text and any existing localization approach, then clarify the intended language coverage and integration boundaries. Done should be defined by an agreed scope and verifiable localized UI behavior.

Written by the indexing model from the issue text.

Description

Enhancement

Please consider add support for i18n

Dominant language
TypeScript
Stars
738
Forks
407
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linode/manager

All issues in linode/manager

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.