Skip to content
Dirk Ertner Digital Consulting

All examples

Automatic article translation

Default: Google Cloud Translation Basic. An operator-provided API key has not yet been configured. No translation has therefore been requested here or presented as a completed result.

Initial setup

The operator must configure the approved Grav languages, private job storage outside all webroots and their own Google Cloud key. The key belongs in the server-side environment; the configuration contains only the reference env:ARTICLE_TRANSLATOR_GOOGLE_KEY. A missing key does not cause another service to be used instead.

Workflow in Admin2

  1. Open Article Translator and select the source language, target languages, articles and provider.
  2. Read the privacy notice and explicitly approve sending the selected texts.
  3. Use Create translation job to create a job and Generate drafts to generate drafts.
  4. Review the source text and translation draft side by side; edit the editorial text fields as needed.
  5. Use Save reviewed draft to save the reviewed draft.
  6. Only use Approve and create translation to create the approved language version; publication remains a separate editorial step.

Costs and privacy

Google Cloud Translation offers a limited monthly free allowance. According to the official pricing, NMT text translation currently includes 500,000 characters per month in the monthly credit. This is not an unlimited free API. Other users of the same Cloud project can also consume this allowance; operators must monitor project quotas and billing.

According to Google's data usage notice, content sent to the Cloud Translation API is not used to train or improve its translation features. The API is still an external service: permissions and privacy requirements must be addressed before submission. A global Basic endpoint does not guarantee processing exclusively within a particular region. Pricing and provider information was checked on 24 October 2026.

Deliberate limitations

Originals are retained. Existing target files are not overwritten. Changed sources prevent approval of an outdated draft. Technical structures, Twig, code and links are conservatively protected; complete link texts also remain unchanged in this version. There is neither full automatic localization of every component nor automatic publication.