[Idea] Switch translations to a single site
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- documentation
Research direction
Start by reading the linked Gatsby translations RFC, then inspect how translated content is organized in the language repositories. The proposed scope covers moving strings into content, removing src/, serving language paths such as reactjs.org/es/docs, and redirecting existing language subdomains; done means those sources and redirects work together.
Written by the indexing model from the issue text.
Description
Right now each translation has its own subdomain (es.reactjs.org, ja.reactjs.org) run as a separate website. This follows the convention of Vue and Angular but has several disadvantages.
- We lose the advantage of single page apps, since switching languages requires you to load a completely new site.
- Each language site doesn't have access to data from other sites, so we can't do things like only showing languages that have been translated in a dropdown.
Since I'm doing work on doing translations for Gatsby, which the site is based on, I'm thinking of doing some work to consolidate all the different translations under one main site.
This work entails:
- Moving all strings to markdown/yaml in
contentand removingsrc/ - Add logic in the main repo to source content from the language repositories and serve them at reactjs.org/es/docs etc.
- Redirect all languages to the main site: e.g. es.reactjs.org to reactjs.org/es
- Dominant language
- JavaScript
- Stars
- 297
- Forks
- 218
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 reactjs/translations.react.dev
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
reactjs/translations.react.dev#374 · 1 reaction ·
-
Nexus multiverse Open
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Nexus multiverse Open
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Nexus multiverse Open
Difficulty 5/5 Over a week Newbie friendliness 10/100
-
Nexus multiverse Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in reactjs/translations.react.dev
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
avniproject/avni-client#2135 ·
-
automated broken-link
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
agent/security hive/hosted-available-lke648397-260827-5n31 security
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
babalae/bettergi-scripts-list#3674 ·
-
A-Release-Notes C-Editing D-Modest S-Ready-For-Implementation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bevyengine/bevy-website#2595 ·