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

Translate whale/whale-cli into Italian (it)

Open Beginner friendly
  • Is something wrong?
#472 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation, localization

Research direction

Read wavedoc/en/whale/whale-cli.md with the Korean canonical source, then create wavedoc/it/whale/whale-cli.md following the translation rules in docs/translation-contributing.md. Preserve metadata, identifiers, examples, code blocks, and links while translating the complete prose into Italian. Run the three listed checks and review the diff; done means the checks pass and only this document is changed.

Written by the indexing model from the issue text.

Description

difficulty: beginner documentation good first issue help wanted localization

Translate Whale command reference into Italian. This task covers one document.

Acceptance criteria
  • Translate the title, summary, and complete prose, including tables, exercises, and answers where present.
  • Set locale: it; preserve the source's shared metadata, example IDs, fenced code/commands/output, and API identifiers.
  • Use Latin script with normal Italian spelling and diacritics. Keep a single it locale without regional variants.
  • Keep documentation links under /docs/it/ and verify heading links. Missing translations may use the English fallback.
  • Run the checks below and review technical meaning against the source. Limit the PR to this document and reference this issue.
python3 tools/check-doc-translations.py --locale it
python3 tools/check-doc-examples.py --links-only
git diff --check
Dominant language
Go
Stars
1
Forks
7
Avg merge
4h 19m
Merged PRs (30d)
34

Getting set up

We have not checked this project's setup files yet. 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 wavefnd/wave-platform

All issues in wavefnd/wave-platform

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.