Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[Idea] Switch translations to a single site

未关闭
#122 0 条评论 2 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
javascript
领域
documentation

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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 content and removing src/
  • 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
主要语言
JavaScript
星标
299
派生
218
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

reactjs/translations.react.dev 的其他 Issue

查看 reactjs/translations.react.dev 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。