Skip to content

Proposal: Korean (한국어) Translation of Official Documentation #18124

@rororoach

Description

@rororoach

Summary

Hermes Agent is gaining significant traction in the Korean developer community. I'd like to propose (and volunteer for) translating the official Hermes Agent documentation into Korean to make it more accessible to Korean-speaking users.

Motivation

  • Hermes has a growing user base in Korea, but the language barrier makes onboarding harder for non-English speakers.
  • Korean developers actively discuss Hermes on local forums, Discord, and social media, but the lack of Korean docs limits deeper adoption.
  • A Korean translation would lower the entry barrier and help grow the Korean Hermes community.

What I'm Proposing

  1. Translate the official documentation — starting with the user guide and key reference pages from https://hermes-agent.nousresearch.com/docs
  2. Hosting — I'm open to the team's preferred approach:
    • A docs/ko/ directory in this repo (if the team accepts community translations)
    • A separate repo under NousResearch (e.g., hermes-agent-ko-docs)
    • Or any other structure the maintainers prefer
  3. Scope — I suggest starting with the most-visited pages (installation, configuration, CLI reference, skills overview) and expanding incrementally.

Questions for the Team

  • Are you open to community-maintained translations?
  • Do you have a preferred structure or workflow for localized docs?
  • Should translations be reviewed by a second Korean speaker before merging?
  • Are there existing i18n plans I should align with?

About Me

I'm an active Hermes user in Korea. I've been using Hermes Agent for daily development workflows and have a good understanding of the tool's architecture and user experience.

I'm happy to discuss this further here or on Discord. Thanks for building Hermes — it's an amazing tool!

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Low — cosmetic, nice to havetype/docsDocumentation improvements

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions