Translated Mintlify Docs into Chinese 🇨🇳, Spanish 🇪🇸, and French 🇫🇷

[ErnestM1234]

Translated Mintlify Docs into Chinese 🇨🇳, Spanish 🇪🇸, and French 🇫🇷

• Almost all files in this PR are translated markdown files in the /zh, /fr, and /es routes.

Outside of these new translation files:

• Added gt.config.json which determines i18n settings. For example, whether en is prefixed to the page url in the default language.
• Added a GitHub workflow file (.github/workflows/translate.yml) which will update translations on every commit to main.
• Edited docs.json to include localized sidebars under navigation and redirects.

Next steps

Setting up continuous translation:

• To enable continuous translation, add your project ID and an API key as GitHub variables. You can generate these on the Dashboard.
• Then in GitHub, navigate to Settings > Security > Secrets and Variables > Actions under Repository Secrets. Add the new environment variables as GT_PROJECT_ID and GT_API_KEY.
• After these are added, merge the PR, and everything will be set up.

Troubleshooting

Failing to execute action:

• Make sure your action is enabled: In GitHub, under organization settings, navigate to Settings > Code, planning, and automation > Actions > General > Policies, and select Allow all actions and reusable workflows or add generaltranslation/translate@* to Allow enterprise, and select non-enterprise, actions and reusable workflows. Finally, click save.

Failing to create a PR:

• Make sure your action has permissions: In GitHub, under organization settings, navigate to Settings > Code, planning, and automation > Actions > General > Workflow permissions (at the bottom), check Allow GitHub Actions to create and approve pull requests. Finally, click save.

---

For Reviewers

When reviewing documentation PRs, please consider:

✅ Technical accuracy

• Code examples work as written
• Commands and configurations are correct
• Links resolve to the right destinations
• Prerequisites and requirements are accurate

✅ Clarity and completeness

• Instructions are clear and easy to follow
• Steps are in logical order
• Nothing important is missing
• Examples help illustrate the concepts

✅ User experience

• A new user could follow these docs successfully
• Common gotchas or edge cases are addressed
• Error messages or troubleshooting guidance is helpful