> For the complete documentation index, see [llms.txt](https://docs.premsoft.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.premsoft.de/en/plugins/blog/translations.md).

# Translations

PremsBlog is multilingual end-to-end: your **default language** holds the master copy of an article, every other language only contains the translations — with an automatic fallback to the default language for any field you leave empty.

## What is translatable

* **Articles**: title, subtitle, short description, content (the complete visual layout), meta title and meta description.
* **Categories**: name.
* **Tags**: name.
* **Authors**: description (bio).

Admin fields like the internal name, status, email or an author's first and last name are **deliberately not translatable** — they identify the record consistently across every language.

## How the fallback works

If you leave a field empty in a translation, the shop automatically shows the value from the default language. You don't need to translate everything — only translate what should actually be different. The rest stays visible because the default-language value is filled in automatically.

## In the administration

When you switch to another language in the top right, three things happen:

1. **Required fields** are not enforced in the translation language. You can save the translation without filling in e.g. the title.
2. **Field placeholders** show the default-language value as a hint. You see immediately what will appear in the shop if you leave the translation empty.
3. **The article structure** (sections, blocks, order) is **locked** and can only be changed in the default language. Content (texts, headlines, image alt texts, …) stays editable.

This keeps the article structure consistent across every language — you only translate the content.

## In the shop

Texts appear automatically in the language of the chosen sales channel. Fields with no translation are shown in the default language. The visitor doesn't notice anything.

## Example: an article in several languages

1. **Create the article in the default language** (e.g. German) — fill in internal name, title and status, build the content in the editor, save.
2. **Switch the language** (e.g. to English).
3. Only translatable fields are editable now. The stage editor is structurally locked. Whatever you leave empty falls back to the German version in the shop.
4. **Save**. Done.

## Languages per sales channel

Every sales channel in Shopware can offer a different set of languages. PremsBlog respects this automatically — articles appear with the translations available in that channel.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.premsoft.de/en/plugins/blog/translations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.