Add Chinese translations for various documentation files including fe…#858
Add Chinese translations for various documentation files including fe…#858illright merged 8 commits intofeature-sliced:masterfrom
Conversation
…atures, community, branding, and guides. Introduce new sections for understanding, migration, and tech usage with frameworks like Next.js and Electron.
There was a problem hiding this comment.
Pull Request Overview
This pull request adds comprehensive Chinese translations for Feature-Sliced Design documentation, covering a wide range of documentation files including reference materials, guides, examples, migration instructions, and technology-specific usage guides. The PR introduces new Chinese localization infrastructure with navbar and footer translations, along with extensive documentation for core concepts, practical guides, and framework integrations.
- Adds complete Chinese localization infrastructure including navbar and footer translations
- Translates core reference documentation for layers, slices/segments, and public APIs
- Includes comprehensive guides covering migration, examples, and technology integrations
- Provides Chinese translations for framework-specific usage guides (Next.js, Electron, React Query, etc.)
Reviewed Changes
Copilot reviewed 67 out of 67 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
| package.json | Adds Chinese locale support with new start script |
| i18n/zh/docusaurus-theme-classic/ | Provides Chinese translations for UI navigation elements |
| i18n/zh/docusaurus-plugin-content-docs/current/reference/ | Translates core FSD reference documentation |
| i18n/zh/docusaurus-plugin-content-docs/current/guides/ | Translates practical guides and examples |
| i18n/zh/docusaurus-plugin-content-docs/current/guides/tech/ | Provides Chinese versions of technology-specific integration guides |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
|
|
||
| The independence of slices is enforced by the [import rule on layers][layers--import-rule]: | ||
|
|
||
| > _A module (file) in a slice can only import other slices when they are located on layers strictly below._ |
There was a problem hiding this comment.
This English text should be translated to Chinese to maintain consistency with the rest of the document.
| > _A module (file) in a slice can only import other slices when they are located on layers strictly below._ | |
| > _slice 中的模块（文件）只能导入位于更低层级的其他 slice。_ |
|
|
||
| Inside a slice, the code could be organized in any way that you want. That doesn't pose any issues as long as the slice provides a good public API for other slices to use it. This is enforced with the **public API rule on slices**: | ||
|
|
||
| > _Every slice (and segment on layers that don't have slices) must contain a public API definition._ |
There was a problem hiding this comment.
This English text should be translated to Chinese to maintain consistency with the rest of the document.
| > _Every slice (and segment on layers that don't have slices) must contain a public API definition._ | |
| > _每个 slice（以及没有 slices 的 layer 上的 segment）都必须包含一个公共 API 定义。_ |
|
|
||
| > _Every slice (and segment on layers that don't have slices) must contain a public API definition._ | ||
| > | ||
| > _Modules outside of this slice/segment can only reference the public API, not the internal file structure of the slice/segment._ |
There was a problem hiding this comment.
This English text should be translated to Chinese to maintain consistency with the rest of the document.
| > _Modules outside of this slice/segment can only reference the public API, not the internal file structure of the slice/segment._ | |
| > _该 slice/segment 之外的模块只能引用其公共 API，不能引用 slice/segment 的内部文件结构。_ |
| 6. Entities | ||
| 7. Shared | ||
|
|
||
| You don't have to use every layer in your project — only add them if you think it brings value to your project. Typically, most frontend projects will have at least the Shared, Pages, and App layers. |
There was a problem hiding this comment.
This English text should be translated to Chinese to maintain consistency with the rest of the document.
| You don't have to use every layer in your project — only add them if you think it brings value to your project. Typically, most frontend projects will have at least the Shared, Pages, and App layers. | |
| 您不必在项目中使用所有的层——只有在您认为它们对项目有价值时才添加。通常，大多数前端项目至少会包含 Shared、Pages 和 App 这几个层。 |
|
|
||
| You don't have to use every layer in your project — only add them if you think it brings value to your project. Typically, most frontend projects will have at least the Shared, Pages, and App layers. | ||
|
|
||
| In practice, layers are folders with lowercase names (for example, `📁 shared`, `📁 pages`, `📁 app`). Adding new layers is _not recommended_ because their semantics are standardized. |
There was a problem hiding this comment.
This English text should be translated to Chinese to maintain consistency with the rest of the document.
| In practice, layers are folders with lowercase names (for example, `📁 shared`, `📁 pages`, `📁 app`). Adding new layers is _not recommended_ because their semantics are standardized. | |
| 实际上，层就是以小写命名的文件夹（例如，`📁 shared`、`📁 pages`、`📁 app`）。不建议添加新的层，因为它们的语义已经被标准化。 |
|
|
||
| 方法论的新版本（[v2][ext-v2]）旨在**消除这些缺点，同时保留该方法的现有优势**。 | ||
|
|
||
| Since 2018, [has also developed][ext-fdd-issues] another similar methodology - [**feature-driven**][ext-fdd], which was first announced by [Oleg Isonen][ext-kof]. |
There was a problem hiding this comment.
This English text should be translated to Chinese to maintain consistency with the rest of the document.
| Since 2018, [has also developed][ext-fdd-issues] another similar methodology - [**feature-driven**][ext-fdd], which was first announced by [Oleg Isonen][ext-kof]. | |
| 自 2018 年以来，[也发展了][ext-fdd-issues]另一种类似的方法论——[**feature-driven**][ext-fdd]，最早由 [Oleg Isonen][ext-kof] 宣布。 |
…g guides and examples. Enhance clarity and consistency in terminology across sections related to UI decomposition, API requests, and authentication processes.
illright
left a comment
illright
left a comment
There was a problem hiding this comment.
Could you please remove the files that are still in English? Docusaurus provides automatic fallbacks already, so there's no need to keep duplicated content in two locales
…eeds-driven, and tech usage documentation. Enhance clarity and consistency in terminology across various sections, ensuring better understanding for users.
…ections. Update titles and labels for clarity, ensuring consistency across various documentation files.
|
I have updated all the files to Chinese and verified them locally. |
There was a problem hiding this comment.
Pull Request Overview
Copilot reviewed 68 out of 68 changed files in this pull request and generated no new comments.
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
|
Thanks! There seems to be a build error still, could you also address that please? |
|
@liuwei1025, since the conflicts hadn’t been fixed for a while, I went ahead and resolved them in i18n.js and updated the locale settings in package.json. |
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
…atures, community, branding, and guides. Introduce new sections for understanding, migration, and tech usage with frameworks like Next.js and Electron.
Background
Add Chinese translation.
Changelog