Global Configuration

Translation Strategy

At least one translation strategy must be configured. Pick one below – the strategy option selects which one runs.

Available Properties

Set global defaults that apply to both view buttons and sections. These can be overridden in individual blueprints. The following configuration sets DeepL as the translation strategy and defines global defaults for field types, title translation, slug translation, confirmation dialogs, and KirbyTags translation:

return [
    'johannschopplich.content-translator' => [
        // Translation strategy
        'DeepL' => [
            'apiKey' => 'your-deepl-api-key'
        ],

        // Global default properties for view buttons and sections
        'fieldTypes' => [
            'blocks',
            'text',
            'textarea'
        ],
        'title' => true,
        'slug' => true,
        'kirbyTags' => [
            'link' => ['text', 'title'],
            'image' => ['alt', 'caption'],
            'file' => ['text', 'title']
        ]
    ]
];

Every view button and section property except label, systemPrompt, and theme can be set here as a project-wide default; the View Button & Section Configuration page describes each one. systemPrompt becomes ai.systemPrompt; label and theme stay in the blueprint. Everything below exists only globally.

strategy Mixed

Selects the translation strategy explicitly. Accepts a string preset, a closure, or a Strategy instance. Without this option the plugin uses the deprecated translateFn if one is configured, and DeepL otherwise.

The Panel follows this option: a closure or Strategy instance enables the translation buttons without a DeepL.apiKey, and 'ai' makes AI translation the only strategy on offer – with a single strategy there is nothing to pick, so no dialog renders.

return [
    'johannschopplich.content-translator' => [
        'strategy' => 'deepl', // or 'ai'
    ]
];

return [
    'johannschopplich.content-translator' => [
        'strategy' => function (string $text, string $target, ?string $source): string {
            return myTranslateApi($text, $target, $source);
        },
    ]
];

use App\Translation\MyApiStrategy;

return [
    'johannschopplich.content-translator' => [
        'strategy' => new MyApiStrategy(),
    ]
];

batchConcurrency Integer

In batch translation mode, multiple languages are translated in parallel to improve performance. By default, up to 2 translations are processed concurrently to avoid hitting API rate limits.

Lower it to 1 when the provider returns rate limit errors – the languages then translate one after another:

return [
    'johannschopplich.content-translator' => [
        'batchConcurrency' => 1
    ]
];

ai.systemPrompt String

When using AI translation, you can replace the built-in system prompt with a custom one. Set it globally or override it per blueprint.

return [
    'johannschopplich.content-translator' => [
        'ai' => [
            'systemPrompt' => 'You are a medical translator. Preserve clinical terminology and abbreviations.'
        ]
    ]
];