Translation your desk can sign off.
Your articles in five languages, inside your own workflow. Quotes stay exact, attributions stay intact, and nothing reaches the site until an editor approves it.
Meridian CMS, running
One Hebrew original, five approved translations.
Where generic translation fails
It costs you in the quotes, the register, and what nobody checked.
Misquoted sources
A generic engine rewrites quotes and paraphrases attributions. One wrong word inside quotation marks is a correction.
A flattened voice
Hedged reporting comes back definitive. The standards your desk set do not survive the round trip.
Nothing checks it
Standard tools translate and ship. Nobody reads the output against the original before it goes live.
What publication-grade means
Not fluent. Safe to put your masthead on.
Quotes stay exact
Quotes, attributions and legal text sit in protected zones the model cannot rewrite.
Caution survives
Allegedly stays allegedly. Hedges, qualifiers and register carry into every language.
Facts are checked
Numbers, dates and names are verified against the source, and anything that moved is flagged.
Inside the CMS you already use
Publishing fires a webhook. Only the paragraphs that changed are retranslated, then published or held for review.
- WordPress and headless CMS webhooks
- React and Next.js SDK for interface strings
- A proxy for legacy systems, with no code changes
- The HebrewCore REST API for anything custom
Talk to sales
Your languages, your daily volume, the platform you publish on.
What happens next
- A reply from a person, not an autoresponder
- A scoped proposal for your languages and volume
- A walkthrough on your own content
- One named contact for the whole engagement
Serving a public in several languages?
The same engine runs behind ministries, municipalities and agencies.