PUBLISHING INFRASTRUCTURE / AI TRANSLATION
Multilingual WordPress publishing without another translation subscription
PolyTrans began as a way to translate a large WordPress publication without paying a platform fee for every word. It connects to the AI provider selected by the operator, so cost follows actual model use rather than a separate translation subscription.
The idea came from an editor colleague at Trans.info. I implemented and developed the tool myself, using my own experience of the publishing process; the editorial and development teams provided feedback and loud encouragement as it grew.
Production work across the Trans.eu ecosystem expanded the plugin into scheduling, editorial review, post-processing and communication between separate WordPress installations. As models improved, the solution became more effective, but its value came from fitting the process rather than from using a model by itself.
THE PROBLEM
Large multilingual publications need durable translations, language relationships and editorial control. They should not lose content or workflow ownership when a third-party subscription ends.
THE WORKFLOW
A source post can be translated by one provider and passed through another step for terminology, tone, SEO fields or structural cleanup. Status and review information return to the editorial environment.
THE ROLE
PolyTrans did not grow in a vacuum. The editorial and development teams did not implement the tool for me, but their questions, observations and loud encouragement helped test whether each decision fit real work. That is different from having a large team at the keyboard: I owned the code, while people using the process supplied context.
THE RESULT
PolyTrans has supported multilingual work around trans.info, trans.eu, TFC and TFF, across more than ten language editions and four AI providers. The integrations differ where the publishing properties differ, while the core orchestration remains reusable.
Use an existing AI account and pay for actual consumption.
Keep review, status and publication inside the tools editors already use.
Translated posts and their relationships remain under the publisher's control.
Add model or deterministic steps for terminology, metadata and cleanup.
A solo implementation can grow with observations from editorial and development teams.
PolyTrans runs as publishing infrastructure inside WordPress and connects to the AI provider chosen by the operator. There is no separate per-word platform subscription.
Yes. Sender, translator and receiver roles can be split between installations when the publishing architecture requires it.
No. I led the idea, implementation and development myself. AI models became part of a more effective process over time, but they did not replace decisions about statuses, review and integration with the existing WordPress setup.
KNOWLEDGE BASE
AI · TOOL CHOICE
Compare AI with a simple script, cron, SaaS, and APIs while accounting for the cost of mistakes and future maintenance.
Read the article →
LEGACY · SAFE DEVELOPMENT
Learn the order of an old-application takeover: access, startup, behavior, backup, safe change, and only then a rewrite decision.
Read the article →
COLLABORATION · SCALE AND DEVOPS
See why user count is not a developer headcount formula and when a one-person studio is enough.
Read the article →
MULTILINGUAL PUBLISHING
We can map the content, review and publication path first, then connect the models and WordPress properties that belong in it.
Discuss a publishing system