i18n(zh-CN): update Chinese UI strings by jenxi · Pull Request #135 · withstudiocms/docs

jenxi · 2025-06-03T12:19:29Z

Description

Adds Chinese translation config and update Chinese UI strings
Adds Chinese docs pages

Summary by CodeRabbit

New Features
- Added support for Simplified Chinese language throughout the application.
- Introduced Chinese translations for UI labels, messages, sidebar navigation, and documentation.
- Enabled Simplified Chinese as an available language option in the language selector.
- Published new Chinese-language guides including quick start, environment variables, and tutorial indexes.

add Chinese translation config and update Chinese UI strings

Created files for Chinese pages

Added zh-CN

coderabbitai · 2025-06-03T12:19:37Z

Walkthrough

The changes enable Simplified Chinese (zh-CN/zh-cn) as a supported locale across the project. This includes uncommenting Chinese locale entries in configuration files, updating the available translations list, and adding new JSON files with Chinese translations for UI and sidebar navigation labels. Additionally, new Chinese documentation pages for guides and environment variables have been added.

Changes

Files/Paths	Change Summary
astro.config.mts, lunaria.config.ts	Uncommented and enabled Simplified Chinese locale entries in configuration objects/arrays.
src/starlight-sidebar/availTranslations.ts	Added 'zh-cn' to the array of available translations.
src/content/i18n/zh-CN.json	Added new file with 49 key-value pairs for UI and message translations in Simplified Chinese.
src/starlight-sidebar/zh-cn.json	Added new file with sidebar navigation labels translated into Simplified Chinese.
src/content/docs/zh-cn/guides/index.mdx	Added new Chinese documentation index page organizing StudioCMS guides.
src/content/docs/zh-cn/start-here/environment-variables.mdx	Added new Chinese documentation on environment variables for StudioCMS.
src/content/docs/zh-cn/start-here/getting-started.mdx	Added new comprehensive Chinese quick start guide for StudioCMS.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant App
    participant LocaleConfig
    participant TranslationFiles

    User->>App: Selects Chinese locale
    App->>LocaleConfig: Loads 'zh-cn' locale configuration
    App->>TranslationFiles: Loads zh-CN.json and zh-cn.json
    App-->>User: Displays UI and sidebar in Simplified Chinese

Possibly related PRs

i18n(ko-KR): update sidebar #43: Adds Korean locale support and translations, similar in localization scope but for a different language.
i18n(de): start German translation; key-values translated #46: Enables German locale by uncommenting and adding translations, closely related in modifying locale configurations and translation files.
i18n(es): translate /guides/index.mdx #115: Adds Spanish localized guides index page, related by adding localized documentation for the same guides content.

Suggested reviewers

Adammatthiesen

Poem

🐇
A hop and a skip, a locale anew,
Now Chinese words join our language crew!
Sidebars and buttons, all dressed up to see,
欢迎, dear friends, to our global spree!
With each translation, our world grows wide—
Let’s code together, side by side!
🌏✨

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fcfa013 and 7da7bb4.

📒 Files selected for processing (1)

src/content/docs/zh-cn/start-here/getting-started.mdx (1 hunks)

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: ArmandPhilippot
PR: withstudiocms/docs#130
File: src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-17.mdx:1-11
Timestamp: 2025-04-26T12:29:17.995Z
Learning: When reviewing translations in the withstudiocms/docs repository, compare with the corresponding English version as the source of truth, not with other files in the same target language. French translations should maintain structural parity with their English counterparts.

src/content/docs/zh-cn/start-here/getting-started.mdx (1)

Learnt from: ArmandPhilippot
PR: withstudiocms/docs#130
File: src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-17.mdx:1-11
Timestamp: 2025-04-26T12:29:17.995Z
Learning: When reviewing translations in the withstudiocms/docs repository, compare with the corresponding English version as the source of truth, not with other files in the same target language. French translations should maintain structural parity with their English counterparts.

🪛 Gitleaks (8.26.0)

src/content/docs/zh-cn/start-here/getting-started.mdx

62-62: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

🔇 Additional comments (2)

src/content/docs/zh-cn/start-here/getting-started.mdx (2)

15-15: Link locale casing now matches directory – looks good.
The href uses /zh-cn/…, consistent with the folder name under src/content/docs/zh-cn.

341-347: Anchors Verified in environment-variables.mdx
The headings for @astrojs/db (“数据库连接参数”) and @studiocms-auth (“加密密钥”) produce the slugs astrojsdb-数据库连接参数 and studiocms-auth-加密密钥, which exactly match the link targets. No changes required.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Explain this complex logic.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai explain this code block.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and explain its main purpose.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai generate docstrings to generate docstrings for this PR.
@coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

coderabbitai

Actionable comments posted: 13

🧹 Nitpick comments (49)

src/content/docs/zh-cn/package-catalog/studiocms-plugins/studiocms-markdoc.mdx (3)

13-15: Remove unused imports
The Steps, Tabs, and TabItem components are imported but never used in this document. Please remove them to avoid clutter and potential bundle size impact.

22-25: Consider using <Steps> for consistency
Since you’ve imported the Starlight Steps component, you could replace the plain numbered list with a <Steps> component to match other integration docs. This would improve visual consistency across the docs.

28-36: Ensure code block is properly fenced and highlights match

Verify there is a closing set of triple backticks (\```) after the example.

Check that the {2, 6} highlight range corresponds to the intended lines in the snippet.

src/content/docs/zh-cn/guides/index.mdx (1)

15-17: Clarify non-link bullet or convert to plain text
The second item under “升级指南” is a standalone sentence (“更多版本特定指南请查看侧边栏导航”) but is formatted as a list item. Consider moving it outside the list or indenting it as subtext to avoid confusion.

src/content/docs/zh-cn/package-catalog/studiocms-plugins/studiocms-mdx.mdx (3)

13-15: Remove unused imports
The Steps, Tabs, and TabItem components are imported but not used. Please remove them to keep the document lean.

22-25: Optional: Switch to <Steps> for step-by-step UI
To maintain a consistent look with other plugin docs, you could render the installation steps using the imported Steps component instead of a Markdown list.

28-36: Check code block termination and highlights

Ensure there’s a closing triple-backtick after the snippet.

Verify the {2, 6} highlighting matches the intended lines in the example.

src/content/docs/zh-cn/config-reference/image-service.mdx (2)

9-9: Remove unused ReadMore import
The ReadMore component is imported but never used in this document. Please delete the import to prevent dead code.

11-11: Minor grammar polish
The heading “StudioCMS 集成配置选项架构参考” could read more naturally as “StudioCMS 集成配置选项的架构参考”。 Consider adding “的” for smoother Chinese.

src/content/docs/zh-cn/utils/rendering.mdx (1)

21-23: Normalize indentation to spaces.
Line 21 uses a tab character for indentation, while the rest of the snippet uses spaces. For readability and consistency, replace tabs with two spaces throughout this code block.

src/content/docs/zh-cn/package-catalog/studiocms-plugins/studiocms-wysiwyg.mdx (1)

1-11: Check frontmatter for sidebar ordering.
The sidebar field only defines a badge; it might be beneficial to add an order property to control the position of this plugin in the package catalog sidebar, matching patterns in other plugin docs.

src/content/docs/zh-cn/package-catalog/community-plugins/web-vitals.mdx (1)

23-27: Remove or re-enable the commented <Steps> wrapper.
The <Steps> component is commented out around your tab content. Either remove these commented lines for clarity or re-enable <Steps> to maintain consistency with other plugin docs.

src/content/docs/zh-cn/guides/contributing/getting-started.mdx (2)

26-27: Remove placeholder comment.
The comment {/* 链接 */} appears to be leftover—consider removing it to clean up the MDX content.

10-14: Polish translation tone (optional).
Consider refining “感谢您投入时间贡献我们的项目！” to a more natural phrasing like “感谢您抽出时间为我们的项目做出贡献！”， which may read smoother in Chinese.
src/content/docs/zh-cn/guides/upgrade/version-guides/0-1-0-beta-16.mdx (1)
42-42: Add space before link in ReadMore component.
For better readability in Chinese, insert a space before the link reference:
-<ReadMore>详细了解 CLI 新功能请参阅[命令行工具文档][cli-docs]</ReadMore>
+<ReadMore>详细了解 CLI 新功能请参阅 [命令行工具文档][cli-docs]</ReadMore>
src/content/docs/zh-cn/index.mdx (3)
24-25: Remove unused import of Youtube.
The Youtube component is imported but never used. Either integrate it (e.g., use <Youtube id="…"/>) or remove the import:
-import Youtube from '~/components/Youtube.astro';
31-31: Unify quotation marks in JSX attributes.
Mixing single and double quotes can be confusing. For example:
-<Card title="StudioCMS 演示" icon='seti:video'>
+<Card title="StudioCMS 演示" icon="seti:video">
 ...
-<LinkButton 
-  href='https://chat.studiocms.dev' 
+<LinkButton 
+  href="https://chat.studiocms.dev" 
Also applies to: 77-84

52-52: Consistent Markdown reference label casing.
The link text uses [Turso] but the label is defined as [turso]. While CommonMark is case-insensitive, consistent casing improves readability. Consider:
-需要 libSQL 数据库？请了解 [Turso][turso]。
+[Turso]: https://tur.so/studiocms
→ change to uppercase [Turso]: … or lowercase both.

Also applies to: 91-93
src/content/docs/zh-cn/config-reference/included-integrations.mdx (2)
9-10: Remove unused ReadMore import.
Since ReadMore isn’t used in this document, you can safely delete:
-import ReadMore from '~/components/ReadMore.astro';
4-4: Refine front matter description for clarity.
Consider adjusting the description to use backticks for code identifiers and natural Chinese phrasing:
-description: "StudioCMSOptions IncludedIntegrations 参考文档"
+description: "`StudioCMSOptions.includedIntegrations` 配置项参考文档"
src/content/docs/zh-cn/package-catalog/studiocms-plugins/studiocms-blog.mdx (1)
13-14: Ensure consistent semicolons and quoting.
The first import is missing a semicolon, and the <PackageManagers> attributes mix single quotes. For consistency:
-import { PackageManagers } from 'starlight-package-managers'
+import { PackageManagers } from 'starlight-package-managers';

-   <PackageManagers pkg="studiocms" type='run' args='add @studiocms/blog' />
+   <PackageManagers pkg="studiocms" type="run" args="add @studiocms/blog" />
Also applies to: 24-24
src/content/docs/zh-cn/config-reference/overrides.mdx (2)

1-7: Refine the page title for clarity
The frontmatter title: "配置覆盖" could be more idiomatic as “覆盖配置” to match terminology in other docs.

95-95: Adjust heading level for Best Practices
Change the “### 最佳实践：” heading to “## 最佳实践” so it aligns with other top-level sections on this page.
src/content/docs/zh-cn/config-reference/index.mdx (3)
11-11: Refine the main heading wording
“StudioCMS 集成配置选项架构参考” reads a bit clunky; consider “StudioCMS 配置选项架构参考”或“StudioCMS 配置参考指南”以提升可读性。

36-38: Clarify dbStartPage description
“项目初始化页面 - 用于首次设置时创建数据库配置。”中的“项目初始化页面”可能引起歧义，建议改为“数据库启动页”或“数据库设置页面”。

16-16: Add punctuation to default values comment
建议在代码注释末尾添加全角冒号，将
// 以下为默认值示例
改为
// 以下为默认值示例：
src/content/docs/zh-cn/config-reference/sdk.mdx (3)
3-5: Standardize the acronym casing
将 description: "StudioCMSOptions sdk 参考文档" 中的 sdk 修改为大写 SDK，保持与标题一致：
- description: "StudioCMSOptions sdk 参考文档"
+ description: "StudioCMSOptions SDK 参考文档"
11-11: Refine the main heading wording
“StudioCMS 集成配置选项架构参考”可优化为“StudioCMS SDK 缓存配置参考”或“StudioCMS SDK 配置指南”，以突出本页主题。

80-91: Annotate advanced example for consistency
高级缓存示例缺少 twoslash 和标题信息。建议如下：
- ```ts
+ ```ts twoslash title="高阶缓存配置示例"
  // 高级缓存配置示例（仅适用于Enterprise版本）
  cacheConfig: {
      lifetime: '10m',
      strategy: 'stale-while-revalidate', // 后台更新策略
      types: {
          api: '5m',
          database: '10m',
          assets: '24h'
      }
  }
</blockquote></details>
<details>
<summary>src/content/docs/zh-cn/config-reference/default-frontend-config.mdx (3)</summary><blockquote>

`11-11`: **Refine the main heading wording**  
“StudioCMS 集成配置选项架构参考”建议改为“StudioCMS 默认前端配置参考”以更聚焦页面内容。

---

`26-28`: **Enhance type description clarity**  
将 "`favicon` 是用于设置网站图标路径的字符串。" 调整为更标准的表述，例如：  
```md
`favicon` 是用于设置网站图标路径的字符串类型。
95-99: Normalize indentation in HeadConfig example
HeadConfig 代码示例中缩进混用制表符和空格，建议统一为两个空格（或四个空格）。
src/content/docs/zh-cn/guides/contributing/code-contributions.mdx (2)
15-18: Clarify the "解决现有问题" section title
建议将 “解决现有问题” 改为 “查找并解决现有问题” 以更清晰地传达上下文。

30-31: Enhance step clarity by linking .prototools
第 2 步提及 [.prototools] 文件，建议在文本中添加直接链接：
- **安装或更新 Node.js 和 pnpm**，版本需符合 [`.prototools`](https://github.com/withstudiocms/studiocms/blob/main/.prototools) 中的要求
src/content/docs/zh-cn/start-here/why-studioCMS.mdx (1)

9-15: Consider adding a table of contents.
For consistency with longer locale pages (e.g., the CLI guide), you might include a tableOfContents section in the frontmatter to enable in-page navigation.

src/content/docs/zh-cn/how-it-works/cli.mdx (2)

5-9: YAML frontmatter indentation.
Nested keys under sidebar are indented by 3 spaces. While valid, using a 2-space indent (as in other docs) improves readability and consistency.

28-44: Code block syntax highlighting.
The CLI examples use “log”. Consider switching these to “bash” or “```sh” so that syntax highlighting better matches shell commands.

src/content/docs/zh-cn/plugins/index.mdx (1)

214-215: Heading and type name mismatch.
The section heading AuthProvider does not match the code snippet type AuthProviders. Update the heading to AuthProviders for consistency.

src/content/docs/zh-cn/config-reference/dashboard.mdx (3)

9-9: Remove unused import.
The ReadMore component is imported but never used in this document. Please remove the import to avoid dead code.

48-54: Property name casing mismatch.
The heading ## \DashboardRouteOverride`should reflect the actual propertydashboardRouteOverride` (camelCase). Please adjust the heading.

3-5: Enhance description formatting.
In the frontmatter description, consider marking dashboardConfig with backticks (\dashboardConfig``) to clearly denote the config key.

src/content/docs/zh-cn/guides/upgrade/version-guides/0-1-0-beta-17.mdx (1)

10-10: Remove unused import.
import ReadMore is declared but never used in this guide. Please remove it for clarity.

src/content/docs/zh-cn/package-catalog/studiocms-plugins/studiocms-devapps.mdx (1)

22-49: Optional: Improve list nesting within TabItem

Inside <TabItem> components, the numbered lists and code fences are not indented. For more predictable MDX list rendering, consider indenting list items and their code blocks by two spaces to ensure they render as nested lists under the TabItem.

src/content/docs/zh-cn/start-here/environment-variables.mdx (1)

5-7: Nitpick: Align frontmatter indentation

In the YAML frontmatter, order: 2 is indented by three spaces under sidebar:. For consistency with other MDX files, please use two spaces for indentation under sidebar:.
src/content/docs/zh-cn/guides/upgrade/version-guides/0-1-0-beta-18.mdx (1)
49-54: Nitpick: Specify Aside type for consistency

The <Aside> block for the security reminder lacks a type attribute. Other docs use type="note". Consider adding type="note" for a consistent warning style:
-<Aside title="安全提醒">
+<Aside type="note" title="安全提醒">
src/content/docs/zh-cn/guides/database/sqld-server.mdx (1)

13-14: Improve phrasing of “关于”

LanguageTool suggests that "了解更多关于 sqld 的信息" can be smoothed to "了解更多有关 sqld 的信息" or rephrased at the sentence start. Please adjust for more natural Chinese.

🧰 Tools

🪛 LanguageTool

[uncategorized] ~13-~13: “关于”组成的介词短语必需位于句首，或请改用"对于"代替。
Context: ...MS 项目。通过[官方文档][sql-docs]了解更多关于 sqld 的信息 ## 先决条件 - [Dock...

(wb2)
src/content/docs/zh-cn/plugins/extended.mdx (1)
12-14: Add missing semicolons for consistency
The import statements in MDX should consistently end with semicolons, matching other docs.
-import ReadMore from '~/components/ReadMore.astro'
+import ReadMore from '~/components/ReadMore.astro';
-import { FileTree } from '@astrojs/starlight/components'
+import { FileTree } from '@astrojs/starlight/components';
src/content/docs/zh-cn/guides/contributing/translations.mdx (1)
24-27: Inconsistent admonition syntax
This file mixes :::tip MDX admonitions, whereas other docs use the <Aside> component. For uniform rendering, prefer:
<Aside type="tip" title="无法访问 Discord？">
  …内容…
</Aside>
-:::tip[无法访问 Discord？]
-我们依然欢迎您的参与！请在 GitHub 上为[文档](https://github.com/withstudiocms/docs/issues/new/choose)或[核心包](https://github.com/withstudiocms/studiocms/issues/new/choose)创建新问题提问。
-:::
+<Aside type="tip" title="无法访问 Discord？">
+  我们依然欢迎您的参与！请在 GitHub 上为[文档](https://github.com/withstudiocms/docs/issues/new/choose)或[核心包](https://github.com/withstudiocms/studiocms/issues/new/choose)创建新问题提问。
+</Aside>
src/content/docs/zh-cn/start-here/getting-started.mdx (1)
1-7: Consider adding a top-level heading
The frontmatter sets title: 快速入门指南, but the content starts at level-2 headings. For better accessibility and consistency, insert:
# 快速入门指南
directly beneath the frontmatter.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fc423f0 and 1ae4231.

📒 Files selected for processing (41)

astro.config.mts (1 hunks)
lunaria.config.ts (1 hunks)
src/content/docs/zh-cn/config-reference/dashboard.mdx (1 hunks)
src/content/docs/zh-cn/config-reference/default-frontend-config.mdx (1 hunks)
src/content/docs/zh-cn/config-reference/image-service.mdx (1 hunks)
src/content/docs/zh-cn/config-reference/included-integrations.mdx (1 hunks)
src/content/docs/zh-cn/config-reference/index.mdx (1 hunks)
src/content/docs/zh-cn/config-reference/overrides.mdx (1 hunks)
src/content/docs/zh-cn/config-reference/sdk.mdx (1 hunks)
src/content/docs/zh-cn/guides/contributing/code-contributions.mdx (1 hunks)
src/content/docs/zh-cn/guides/contributing/getting-started.mdx (1 hunks)
src/content/docs/zh-cn/guides/contributing/translations.mdx (1 hunks)
src/content/docs/zh-cn/guides/database/sqld-server.mdx (1 hunks)
src/content/docs/zh-cn/guides/index.mdx (1 hunks)
src/content/docs/zh-cn/guides/upgrade/release-notes.md (1 hunks)
src/content/docs/zh-cn/guides/upgrade/version-guides/0-1-0-beta-16.mdx (1 hunks)
src/content/docs/zh-cn/guides/upgrade/version-guides/0-1-0-beta-17.mdx (1 hunks)
src/content/docs/zh-cn/guides/upgrade/version-guides/0-1-0-beta-18.mdx (1 hunks)
src/content/docs/zh-cn/how-it-works/cli.mdx (1 hunks)
src/content/docs/zh-cn/how-it-works/index.mdx (1 hunks)
src/content/docs/zh-cn/how-it-works/restapi.mdx (1 hunks)
src/content/docs/zh-cn/how-it-works/sdk.mdx (1 hunks)
src/content/docs/zh-cn/index.mdx (1 hunks)
src/content/docs/zh-cn/package-catalog/community-plugins/web-vitals.mdx (1 hunks)
src/content/docs/zh-cn/package-catalog/index.mdx (1 hunks)
src/content/docs/zh-cn/package-catalog/studiocms-plugins/studiocms-blog.mdx (1 hunks)
src/content/docs/zh-cn/package-catalog/studiocms-plugins/studiocms-devapps.mdx (1 hunks)
src/content/docs/zh-cn/package-catalog/studiocms-plugins/studiocms-markdoc.mdx (1 hunks)
src/content/docs/zh-cn/package-catalog/studiocms-plugins/studiocms-mdx.mdx (1 hunks)
src/content/docs/zh-cn/package-catalog/studiocms-plugins/studiocms-wysiwyg.mdx (1 hunks)
src/content/docs/zh-cn/plugins/extended.mdx (1 hunks)
src/content/docs/zh-cn/plugins/index.mdx (1 hunks)
src/content/docs/zh-cn/start-here/configuration.mdx (1 hunks)
src/content/docs/zh-cn/start-here/environment-variables.mdx (1 hunks)
src/content/docs/zh-cn/start-here/gallery.mdx (1 hunks)
src/content/docs/zh-cn/start-here/getting-started.mdx (1 hunks)
src/content/docs/zh-cn/start-here/why-studioCMS.mdx (1 hunks)
src/content/docs/zh-cn/utils/rendering.mdx (1 hunks)
src/content/i18n/zh-cn.json (1 hunks)
src/starlight-sidebar/availTranslations.ts (1 hunks)
src/starlight-sidebar/zh-cn.json (1 hunks)

🧰 Additional context used

🪛 Biome (1.9.4)

src/starlight-sidebar/zh-cn.json

[error] 1-1: End of file expected