Context
The README is available in English (README.md) and Korean (README.ko.md).
This issue adds a Japanese translation, README.ja.md.
Beginner-friendly — no code, just translation following the existing pattern.
It's larger than a UI-string task, so take your time.
What to do
-
Create README.ja.md by translating README.md into Japanese. Keep the same structure, headings, tables, images, and links.
-
Update the language switcher at the top of every README file so each lists all available languages (bold = current language, others linked). In README.ja.md, Japanese is bold.
Example switcher for README.ja.md:
<a href="README.md">English</a> | <a href="README.ko.md">한국어</a> | <b>日本語</b>
And add | <a href="README.ja.md">日本語</a> to the switcher in README.md and README.ko.md.
Keep as-is (do not translate)
- Code blocks, commands, env var names, and file paths.
- The "Deploy with Vercel" button and URLs.
- GitHub status badge labels (
Private/Public, etc.) if referenced.
Acceptance criteria
Comment below to claim this — we'll assign it to avoid duplicate work.
Context
The README is available in English (
README.md) and Korean (README.ko.md).This issue adds a Japanese translation,
README.ja.md.Beginner-friendly — no code, just translation following the existing pattern.
It's larger than a UI-string task, so take your time.
What to do
Create
README.ja.mdby translatingREADME.mdinto Japanese. Keep the same structure, headings, tables, images, and links.Update the language switcher at the top of every README file so each lists all available languages (bold = current language, others linked). In
README.ja.md, Japanese is bold.Example switcher for
README.ja.md:And add
| <a href="README.ja.md">日本語</a>to the switcher inREADME.mdandREADME.ko.md.Keep as-is (do not translate)
Private/Public, etc.) if referenced.Acceptance criteria
README.ja.mdmirrorsREADME.mdin structure and contentnpm run format:checkpasses (Prettier formats Markdown)Comment below to claim this — we'll assign it to avoid duplicate work.