asgardeo/javascript

[UMBRELLA ☂️] chore: expand Language Support (`i18n`) for Better Global Accessibility

Open

#145 opened on Sep 14, 2025

View on GitHubContributor guide
 (17 comments) (0 reactions) (0 assignees)TypeScript (65 forks)auto 404
@asgardeo/i18nType/Improvementaccessibilitygood first issueumbrella

Repository metrics

Stars
 (18 stars)
PR merge metrics
 (PR metrics pending)

Description

[!Important] Contributors for this task should be native speakers or have professional fluency in the target language to ensure accurate, culturally appropriate translations.

[!Note] This issue can be taken by multiple contributors! Please comment below with the language you would like to contribute with.

Current Limitation

Currently, the Asgardeo JavaScript SDK only supports English 🇺🇸 by default. We need to add comprehensive language support to improve internationalization coverage for React UI components.

🌍 How to Contribute

To contribute a language:

  1. Comment below with the language you'd like to contribute (e.g., "I'd like to contribute Spanish translations")
  2. We'll assign you to that specific language in the table below
  3. You can work on your language independently

Language Support Status

Please check the Sub-issues section 👇

Please select the package issue is related to

@asgardeo/javascript

Version

current

Reporter Checklist

  • I have searched the existing issues and this is not a duplicate.
  • I have provided all the necessary information.
  • I have verified the improvement is not available in the latest version of the package.

Contributor guide

Research direction
Select a language from the sub issues, clone the repo, locate the i18n translation files (likely in a locales folder), and add the new language translations following the existing format. Ensure translations are accurate and culturally appropriate.
Tech stack
javascripttypescriptreact
Domain
frontend
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90