Skip to content

Conversation

@crimx
Copy link
Contributor

@crimx crimx commented Sep 17, 2025

Summary by CodeRabbit

  • 文档
    • 优化英文与中文界面文案,整体更简洁直观。
    • 更新首页“使用场景/如何使用”标题与副标题,强调按需求智能推荐工具。
    • 精炼多媒体处理、AI 图像编辑、AI 编码、拖拽手册、ZIP/EPUB/PDF/数据分析等模块描述,突出能力与操作指引。
    • Create、社区分享与指南相关标题/副标题用语更凝练。
    • “Get Started”提示更新为“Start Using OOMOL Today”。

@coderabbitai
Copy link

coderabbitai bot commented Sep 17, 2025

📝 Walkthrough

Walkthrough

本次变更仅修改了 i18n/en/code.json 与 i18n/zh-CN/code.json 的现有文案内容,未新增或删除键,数据结构不变。主要集中于 HOME.Scenes.* 及相关模块(如 Create、CommunityShare、Guide、GetStartedPrompt)的标题与描述,将较长叙述改为更简短的动作式表述;多媒体处理场景强调 FFmpeg 能力;包含 AI 图像编辑、AI 编码、拖拽说明、ZIP 处理、TXT 转 EPUB、PDF 处理、数据分析等场景的描述精简与重写。

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

  • 范围:2 个 i18n JSON 文件,仅字符串内容改写
  • 异质性:低,重复性高、模式一致
  • 逻辑密度:无代码逻辑,仅文案更新
  • 评审要点:核对语义准确性与占位符/键名未变即可

Pre-merge checks

✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed 标题 "refactor(i18n): update landing page descriptions" 采用了 (): 格式且全部为英文,scope 为 i18n,满足格式要求;标题明确描述了对 i18n/en 与 i18n/zh-CN 中着陆页描述字符串的更新,且与提供的变更摘要一致,因此与变更内容高度匹配并通过检查。

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.


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

Comment @coderabbitai help to get the list of available commands and usage tips.

@cloudflare-workers-and-pages
Copy link

Deploying oomol-com with  Cloudflare Pages  Cloudflare Pages

Latest commit: dd45f1b
Status: ✅  Deploy successful!
Preview URL: https://7bc80c62.oomol-com.pages.dev
Branch Preview URL: https://home-i18n.oomol-com.pages.dev

View logs

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
i18n/en/code.json (1)

1-1123: 修复 CI 校验脚本:替换 if ! 写法以避免在部分 shell/CI 环境中报错

执行输出包含 "/bin/bash: line 13: !: command not found",虽随后显示 "✅ Keys match.",但说明当前写法可能在部分环境中失败并产生假通过。将脚本改为更稳健的实现:

#!/usr/bin/env bash
set -euo pipefail

# 1) 验证 JSON 语法
jq -e . i18n/en/code.json >/dev/null
jq -e . i18n/zh-CN/code.json >/dev/null

# 2) 比较两语言的键路径(包含所有 message/description 等标量路径)
jq -r 'paths(scalars) | join(".")' i18n/en/code.json    | sort > /tmp/en.keys
jq -r 'paths(scalars) | join(".")' i18n/zh-CN/code.json | sort > /tmp/zh.keys

echo "Diffing keys between en and zh-CN..."
if diff -u /tmp/en.keys /tmp/zh.keys; then
  echo "✅ Keys match."
else
  echo "❌ Key mismatch detected between en and zh-CN." >&2
  exit 1
fi
🧹 Nitpick comments (14)
i18n/zh-CN/code.json (8)

49-53: 文案更顺,但可与英文版保持措辞一致

建议用“描述你的需求”以贴合英文“Describe what you need”,顺带统一品牌主语位置。

-    "message": "告诉 OOMOL 你的需求,智能助手将为你匹配并推荐合适的工具。"
+    "message": "描述你的需求,OOMOL 智能助手将为你匹配并推荐合适的工具。"

64-71: 标题与英文不完全对齐,内文可进一步简洁有力

  • 标题可简化为“多媒体处理”,与英文“Media Processing”一致。
  • 内文去冗并改为“基于 FFmpeg”的更常见搭配。
-    "message": "多媒体编辑处理"
+    "message": "多媒体处理"
-    "message": "集成 FFmpeg 的多媒体编辑工具包,支持视频剪辑、格式转换、音频处理等多种功能,让多媒体创作变得高效且轻松。"
+    "message": "基于 FFmpeg 的多媒体工具包,支持视频剪辑、格式转换、音频处理等,让创作更高效轻松。"

79-80: 精简句式以提升可读性

当前句子略长,建议压缩信息密度。

-    "message": "基于文本指令,利用 AI 大模型实现图像的编辑与转换,包括对象更改、场景调整及创意效果应用,满足多样化的图像处理需求。"
+    "message": "用文本指令驱动大模型进行图像编辑与转换:对象替换、场景调整、创意特效等。"

115-116: 术语更口语化一点

“涵盖…各类操作”略显书面,可更自然。

-    "message": "专业 ZIP 压缩包处理工具包,涵盖压缩、解压、加密、编码转换等各类 ZIP 文件操作。"
+    "message": "专业 ZIP 工具包,支持压缩、解压、加密、编码转换等常见操作。"

124-125: 避免堆叠修饰词,读起来更顺

-    "message": "将 TXT 格式文本文件转换为优雅排版设计的 EPUB 电子书。"
+    "message": "将 TXT 文本转换为排版优雅的 EPUB 电子书。"

133-134: 去重“处理”词汇,结构更紧凑

-    "message": "功能强大的 PDF 处理工具包,涵盖合并、分割等基础操作,以及 OCR、表单填写、安全管理等高级功能,满足各种 PDF 处理需求。"
+    "message": "功能强大的 PDF 工具包,支持合并、分割等基础操作,以及 OCR、表单填写与安全管理等高级功能。"

142-143: 更口语的结尾表达

-    "message": "使用 AI 分析表格数据,并根据用户需求以自定义格式输出图表。"
+    "message": "使用 AI 分析表格数据,并按需输出自定义图表。"

256-256: 疑似笔误:“即用即用”应为“开箱即用”

虽然本 PR 未改动该行,但属于用户可见文案问题,建议顺手修正。

-    "message": "即用即用"
+    "message": "开箱即用"
i18n/en/code.json (6)

53-54: Remove optional comma for tighter copy

Reads more naturally without the comma.

-    "message": "Describe what you need, and OOMOL’s intelligent assistant will recommend the right tools for you."
+    "message": "Describe what you need and OOMOL’s intelligent assistant will recommend the right tools for you."

89-90: Tighten sentence, reduce repetition

-    "message": "With AI Vibe Coding, just describe what you need — AI will automatically generate complete workflows and nodes, letting you build powerful AI tools quickly and easily, no programming required."
+    "message": "Describe what you need—AI Vibe Coding automatically generates complete workflows and nodes, so you can build powerful AI tools fast. No coding required."

116-117: Trim tail for brevity

-    "message": "A professional ZIP archive toolkit covering compression, extraction, encryption, encoding conversion, and a variety of ZIP file operations."
+    "message": "A professional ZIP archive toolkit for compression, extraction, encryption, and encoding conversion."

134-135: Active phrasing

-    "message": "A comprehensive PDF toolkit that supports merging, splitting, OCR, form filling, security management, and more."
+    "message": "A comprehensive PDF toolkit for merging, splitting, OCR, form filling, security management, and more."

143-144: Micro-tweak for flow

-    "message": "Analyze tabular data with AI and generate customized charts based on your needs."
+    "message": "Analyze tabular data with AI and generate customized charts to your needs."

227-228: 术语一致性:Publish/Release/Share 表述建议统一

当前 “Publish and Share”(Line 227)与 “Release and Share”(Line 290)含义接近但用词不同,建议统一一处用法,避免导航/跳转时的认知分裂;同时与 zh-CN“社区与分享/发现 AI 工具”对齐策略请确认。

Also applies to: 290-294

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e092868 and dd45f1b.

📒 Files selected for processing (2)
  • i18n/en/code.json (13 hunks)
  • i18n/zh-CN/code.json (7 hunks)
🔇 Additional comments (6)
i18n/en/code.json (6)

65-72: LGTM: concise and clear; FFmpeg called out correctly

No issues; matches zh 语义(建议 zh 标题同步为“多媒体处理”)。


80-81: LGTM: clear benefits-first phrasing


98-99: LGTM


125-126: LGTM


197-198: LGTM


380-381: LGTM

@Cheerego7 Cheerego7 merged commit f2b027d into main Sep 17, 2025
4 checks passed
@Cheerego7 Cheerego7 deleted the home-i18n branch September 17, 2025 11:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants