sveltejs / sveltejs/kit

Add a page on Internationalization to the docs

Open
#12,160 1 comment 20 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

documentation
Dominant language
JavaScript
Stars
20.8k
Forks
2.3k
Avg merge
1d 16h
Merged PRs (30d)
156

Description

Describe the problem

Internationalization is clearly very important to SvelteKit & the community, as shown by the

Despite this, when you currently search "i18n" on kit.svelte.dev you get no results.

Screenshot 2024-04-24 at 14 44 28

IMO, this goes counter to Svelte's "simple questions should have simple answers" ethos.

Describe the proposed solution

Add a Page to the documentation on Internationalization that outlines:

  • The current state of development
    • Why SvelteKit does not yet offer i18n out of the box
    • The goals for a first-party i18n solution
    • Where to contribute to the discussion
  • Which i18n solutions SvelteKit users can use today

This would give people a quick overview of the state of affairs & give them a starting-off point

Alternatives considered

do nothing

Importance

nice to have

Additional Information

As someone who has built several i18n libraries I obviously place higher importance on i18n than most people. Perhaps others don't place the same importance on i18n & are fine with the current state.

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.

Research direction

Start by reviewing the existing SvelteKit documentation and the linked issues #1274 and #553 to understand the current i18n discussion. Create a page covering why i18n is not built in, first-party goals, contribution paths, and solutions available today; it is done when users can find this overview by searching the docs for “i18n”.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.