Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implementation of Automated i18n for OpenIM Website #1442

Closed
cubxxw opened this issue Nov 20, 2023 — with Slack · 7 comments
Closed

Implementation of Automated i18n for OpenIM Website #1442

cubxxw opened this issue Nov 20, 2023 — with Slack · 7 comments
Labels
feature Categorizes issue or PR as related to a new feature. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
Milestone

Comments

Copy link
Contributor

cubxxw commented Nov 20, 2023

Body:

We propose to implement an automated internationalization (i18n) design for the OpenIM website, inspired by Databend's i18n practices. Key components include:

  • Website Building & Hosting: Use Docusaurus and Netlify for website development and hosting (Docusaurus, Netlify).
  • Localization Management: Employ Crowdin for localization management (Crowdin).
  • Docusaurus Configuration: Set up locales in docusaurus.config.js.
  • Crowdin Configuration: Create a crowdin.yml file for project settings and file mappings.
  • GitHub Actions: Automate file synchronization for translations.
  • Vercel Integration: Use Vercel for building the site with downloaded translations (Vercel).
  • Machine Translation: Optionally, integrate machine translation tools via Crowdin.
  • Maintenance: Regular updates and management of translations.

Details can be found in Databend's i18n report: Databend i18n Practices

This approach ensures a streamlined, cost-effective, and developer-friendly i18n process for our website.

@cubxxw cubxxw added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. feature Categorizes issue or PR as related to a new feature. labels Nov 20, 2023 — with Slack
@cubxxw cubxxw added this to the v3.5 milestone Nov 20, 2023 — with Slack
@kubbot
Copy link
Contributor

kubbot commented Nov 20, 2023

This issue is available for anyone to work on. Make sure to reference this issue in your pull request. ✨ Thank you for your contribution! ✨
Join slack 🤖 to connect and communicate with our developers.
If you wish to accept this assignment, please leave a comment in the comments section: /accept.🎯

@cubxxw
Copy link
Contributor Author

cubxxw commented Nov 20, 2023

@cubxxw
Copy link
Contributor Author

cubxxw commented Nov 20, 2023

@kubbot
Copy link
Contributor

kubbot commented Jan 20, 2024

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@kubbot
Copy link
Contributor

kubbot commented Feb 18, 2024

This issue was closed because it has been stalled for 7 days with no activity.

@kubbot kubbot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 18, 2024
@cubxxw cubxxw reopened this Feb 19, 2024
@kubbot
Copy link
Contributor

kubbot commented Apr 19, 2024

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@kubbot
Copy link
Contributor

kubbot commented Apr 28, 2024

This issue was closed because it has been stalled for 7 days with no activity.

@kubbot kubbot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Categorizes issue or PR as related to a new feature. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
Projects
None yet
Development

No branches or pull requests

2 participants