Add README.zh-TW.md: Add README Translation in Traditional Chinese

[bbss000]

I adds a Traditional Chinese (zh-TW) version of the README file, providing localized documentation for users and contributors.

Summary by CodeRabbit

• Documentation
  • Added Traditional Chinese localized README to improve accessibility and support for Chinese-speaking users worldwide
  • Includes comprehensive project documentation with self-hosting deployment instructions and procedures
  • Details architecture overview, technology stack information, and setup requirements
  • Provides license information, contribution guidelines, and analytics configuration setup commands
  • Features convenient deployment buttons and all relevant resource links for users

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

A new Traditional Chinese (zh-TW) localized README file was added to the Cap project, containing documentation about self-hosting, monorepo architecture, licensing, contributions, and analytics without modifying any existing code or logic.

Changes

Cohort / File(s)	Summary
Documentation Localization README.zh-TW.md	Added new Traditional Chinese README with project overview, self-hosting instructions, monorepo structure, licensing, contribution guidelines, and Tinybird analytics documentation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

• Verify accuracy and completeness of Traditional Chinese translation
• Check consistency with English README structure and information
• Validate all links and references are functional and properly formatted
• Confirm no sensitive information or credentials are exposed

Possibly related issues

• Is Traditional Chinese documentation welcome? (and which file to start with) #1398: Directly addresses the proposal to add Traditional Chinese (zh-TW) documentation, with this PR implementing the README.zh-TW.md file as suggested.

Poem

🐰 A README in Traditional script so fine,
Cap's wisdom in Chinese does align,
Documentation blooms across the land,
More voices heard, more hearts understand,
East meets West with every line.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding a Traditional Chinese translation of the README file (README.zh-TW.md). It is specific, clear, and directly reflects the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a292974 and 85c53a7.

📒 Files selected for processing (1)

• README.zh-TW.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

README.zh-TW.md

[uncategorized] ~71-~71: 您的意思是“"不"驟”？
Context: ...rd.co）。在執行 analytics:setup` 之前，請務必了解部署步驟具破壞性所帶來的影響並確認你能接受。

(BU)

🪛 markdownlint-cli2 (0.18.1)

README.zh-TW.md

5-5: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

6-6: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

7-7: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

13-13: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

23-23: Images should have alternate text (alt text)

(MD045, no-alt-text)

---

40-40: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3

(MD001, heading-increment)

🔇 Additional comments (3)

README.zh-TW.md (3)

40-40: Verify heading level structure.

The markdown linter flagged an unexpected heading level jump at line 40 (MD001). The section "應用（Apps）:" appears as a level 3 heading (###), but should likely be a level 2 (##) to maintain proper hierarchy after the "Monorepo 應用架構" h2 heading.

Please verify the intended heading structure. If line 40 should be a subsection, apply this diff:

-### 應用（Apps）：
+## 應用（Apps）：

Alternatively, if this should remain a level 3 heading, ensure the context level 2 heading precedes it without intermediate levels.

---

64-70: Verify analytics section wording for clarity.

The analytics description at lines 64-70 is dense and contains complex nested instructions. Consider verifying that the wording accurately reflects the intended process, particularly around the tb login step and the destructive-operations warning.

Line 68 especially warrants review for clarity around the consequence of deployment ("它會把 Tinybird 工作區同步到 scripts/analytics/tinybird 定義的資源，並移除該工作區中任何其他的資料來源/管線。").

---

1-70: Localization quality and content coverage look solid.

The Traditional Chinese translation maintains good structure, provides all necessary information for self-hosting, architecture understanding, and contribution guidelines. The file successfully adapts the original README for a zh-TW audience.

[coderabbitai]

🛠️ Refactor suggestion | 🟠 Major

Replace hard tabs with spaces.

Markdown linting best practices require spaces instead of hard tabs (MD010 violation). These tabs appear at the start of indented lines in the header section.

Apply this diff to replace hard tabs with spaces:

-	<h1 align="center"><b>Cap</b></h1>
+  <h1 align="center"><b>Cap</b></h1>
-	<p align="center">
+  <p align="center">
-		Loom 的開源替代方案
+    Loom 的開源替代方案
-		<a href="https://cap.so/download">macOS 與 Windows</a>
+    <a href="https://cap.so/download">macOS 與 Windows</a>

Also applies to: 6-6, 7-7, 13-13

🧰 Tools

🪛 markdownlint-cli2 (0.18.1)

5-5: Hard tabs
Column: 1

(MD010, no-hard-tabs)

🤖 Prompt for AI Agents

In README.zh-TW.md around lines 5 to 5 (also apply to lines 6, 7 and 13),
replace the hard tab characters at the start of the header and those indented
lines with spaces to comply with MD010; edit each affected line to remove
leading tabs and use the equivalent number of spaces (preferably 2 or 4,
matching project style) so headers and indented lines are space-indented instead
of tab-indented.

[curtis618]

As a Traditional Chinese user, I have reviewed the translated README.zh-TW.md and can confirm that there are no problems.

[curtis618]

I have confirmed that there are no problems in README.zh-TW.md .