Running communications for a small community comes with a particular kind of exhaustion. There are never enough writers, and there is certainly no spare capacity to write every announcement twice — once in Japanese, once in English. So the updates thin out, or one language quietly gets left behind. We were no exception.
On our site, publishing a single GitHub Release now automatically creates a paired Japanese and English article. The only human work is writing the release notes in an agreed format. And when a translation has not been written, the machine does not invent one: the English article is published, and the Japanese one waits as a draft for a human translator. “Never fabricate a translation” is a design principle, not an afterthought.
Today we published this mechanism as a methods document with its reference implementation:
▶ RumiCar-group/RumiCar-ReleaseNotes-Guide
The mechanism itself has been running quietly for a while. But over the course of releasing PhotoStrip, VideoLoop and the AutoPost Guide, we have grown used to putting our ways of working out in the open — so we decided to start publishing not just the new machinery, but the older pieces that have been doing their jobs in the background. This is the first of those.
The motivation is simple. Every manual step that a mechanism absorbs is time handed back to the activity itself. If another understaffed community can use this record as a stepping stone — spending their hours on what they do rather than on announcing it twice — that is exactly what we hoped for. And we set no boundaries on who: schools, companies, commercial use, anyone is welcome (MIT license; it is the record of one working example, offered without warranty).
The documentation is bilingual. Even if you never need this particular pipeline, we hope one fact travels: a small team can keep publishing in multiple languages — if it builds itself the machinery.