Content blocks in translated articles

A content block carries its own translations. Understanding which language a reader gets prevents a half-translated article.

A content block carries its own translations. Understanding which language a reader gets prevents a half-translated article.

Translate a block

1. Open the content block.
2. Add a translation and choose the language.
3. Write the translated text.
4. Save.

Every article using the block now shows that language to readers reading in it.

The rule that matters

A block shows the translation for the reader's language. Where none exists, it falls back to the default language.

So an untranslated block inside a translated article produces one paragraph in the wrong language, in the middle of otherwise correct text. It looks like a mistake, and it is one people rarely notice from the editing side.

Translate blocks before the articles

Blocks are shared, so translating one fixes it everywhere at once. Doing that first means every article you translate afterwards is complete when you publish it.

Check them after a change

Editing the source language of a block does not touch its translations, and nothing marks them as outdated. Where the change is substantive, update every translation in the same sitting.

Keep blocks self-contained

A block that reads as a complete paragraph translates cleanly. One written to continue the sentence before it does not, because word order differs between languages and the join breaks.

See also

• Creating and inserting a content block
• Translating an article
• What happens to an untranslated article