Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Translation] Add Translation to Documentation

Open
  • Is something wrong?
#29 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
documentation, localization

Research direction

No files, tests, or entry points are named. First obtain maintainer guidance on whether Chinese translations are accepted, which documentation is in scope, and what collaboration and maintenance workflow to use. Completion criteria cannot be defined until that scope and process are agreed.

Written by the indexing model from the issue text.

Description

Hello Obsidian Team,

I hope this message finds you well. I am writing to request your permission to contribute translations of the existing documentation into Chinese. As your repository is widely used by developers from various regions , I believe that providing documentation in multiple languages will enhance the user experience and increase the accessibility of your project.

Please let me know if Obsidian team are open to this idea, and if so, how you would like to proceed. I am more than willing to collaborate with other contributors to ensure that the CN translation are accurate and up-to-date. Additionally, I will be happy to provide ongoing support in maintaining the translated documentation as the project evolves.

It would be fantastic if you could provide some guidelines, steps, or collaboration models for us to work together on this. This way, we can ensure a smooth process and maintain consistency throughout the translated documentation.

Thank you for considering this request, and I look forward to your response.

Best regards,

Bon

Dominant language
JavaScript
Stars
530
Forks
174
Avg merge
3d 3h
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from obsidianmd/obsidian-developer-docs

All issues in obsidianmd/obsidian-developer-docs

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.