Addresses #638, where a prospective Italian translator asked for clearer
translator onboarding and a way to preview translations in place. The new
guide documents where strings live, the four-file registration path for a
new language, and the Vite HMR dev workflow that already solves the live
preview need. Linked from all three READMEs alongside CONTRIBUTING.md.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Collapses the line-continuation form (`docker run ... \\n -v ... \\n caorushizi/mediago:3.5.0`)
into one line across README.md / README.jp.md so all three language
READMEs match (zh was already single-line). Makes the command easier
to copy-paste — readers don't have to deal with trailing backslashes
that some terminals / browsers mangle when highlighting.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The CI workflow mirrors every built image to Docker Hub
(`caorushizi/mediago`), but the install lists in README (zh/en/jp)
and docs (guides / changelog for all three languages) only mentioned
GHCR. Most users default to Docker Hub, so they would miss the
simpler pull path.
Switch every Docker row into a two-line form showing both registries
explicitly:
- [**Docker Hub**](https://hub.docker.com/r/caorushizi/mediago): docker run ... caorushizi/mediago:3.5.0
- **GHCR**: docker run ... ghcr.io/caorushizi/mediago:3.5.0
Docker Hub appears first (shorter image name, more familiar to most
users) and its label is a link to the Hub page. GHCR is kept as a
second bullet for users who prefer it or are already authenticated.
The README feature-section (`🐳 Docker deployment`) code block was
also switched to the unqualified `caorushizi/mediago:3.5.0` form so
the showcase command defaults to Docker Hub, with a prose note that
the same image lives on GHCR too.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The three READMEs had drifted into a dev-first shape — the first screen
of each started with pnpm / install commands before telling end users
what the product actually does — and the Japanese version had fallen
behind (outdated commands, no v3.5.x downloads, screenshots pointing
at an external CDN rather than the in-repo images).
Rework all three around the v3.5.0 user-friendly feature story and
move the developer setup into its own file:
- Unified skeleton across zh/en/jp: header badges → one-sentence pitch →
six feature sections (browser extension · YouTube / 1000+ sites ·
OpenClaw Skill · HTTP API · in-app format conversion · Docker +
LAN) → screenshots → v3.5.0 downloads (+ BT Panel one-click) →
v3.5.0 highlights → tech-stack badge row → acknowledgements →
disclaimer → link to CONTRIBUTING.
- Header elements preserved verbatim: nav links, language switcher,
MediaGo Pro / Try Now banners, downloads / stars / forks / GitCode /
Trendshift badges, 4 screenshots, BT Panel one-click deployment,
the full 5-point disclaimer.
- Tech-stack prose list compressed to a single row of shields.io
badges (React / Electron / Vite / TypeScript / Tailwind / shadcn/ui /
Go / Ant Design).
- Acknowledgements gain aria2 (now powering direct downloads after the
gopeed swap).
- README.jp.md specifically: fixed four `static.ziying.site/images/*`
references to use the in-repo `./images/*` (matching zh/en); replaced
the outdated v3.0.0-only download block with v3.5.0; added the
English-language switcher link that was missing from the header.
- README.md/zh.md: dropped the v3.0.0 changelog block (history lives
on GitHub Releases) and the "Quick Start" / "Running locally" pnpm
command blocks.
New file: `CONTRIBUTING.md`. English only — prerequisites, repo layout,
a short list of the commands contributors actually type (deps:download
/ dev:electron / dev:server / pack:electron / release:electron / check),
Conventional Commits note, PR guidance. Each README ends with a one-
line pointer to it in the local language.
No product behaviour change.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
y2hlbg