Languages and translation

A multilingual Collection uses configured language directories to keep related articles together. Translating an article creates a target-language draft; it does not publish the article or change the source version.

Check the Collection languages

The translation action is available for Markdown and MDX entries when the Collection has another configured language. Review the Collection’s language configuration before translating. Targets come from that configuration, so a language must be added there before it can be selected.

If Translate article is missing, check that you opened a document rather than a JSON/YAML resource, that another Collection language is configured, and that you have editing access.

Translate an article

1. Save the latest source changes.
2. Open the article’s actions in the Content list and choose Translate article.
3. Select a target language and check the destination shown in the dialog.
4. Start translation. When it finishes, Prosefly opens the translated draft for review.

Translation works with the complete Markdown or MDX source. It is intended to preserve frontmatter keys, code, imports, components, URLs, and media paths while translating the authored text. Check those details and the translation before publishing.

The source article remains unchanged. Writing and translation use the same organization AI credits.

When a translation already exists

The dialog shows the existing target path and warns that continuing will replace its unpublished edits. Close the dialog if you want to keep that draft. Continue only after reviewing what will be replaced.

If the source or destination changes while translation runs, Prosefly may ask you to review the current state again before applying the result. Reopen the translation action to recover an existing task rather than starting another translation unnecessarily.

Review related language drafts

Edit the translated draft for terminology, tone, links, and locale-specific information. Publication review groups related language drafts so you can inspect the source and translation together. Confirm every included file before publishing; translation itself never creates a Git commit.

See Publishing to Git for commit and pull request workflows.