Case study Utility Plugin

Lubinik Translation

Utility Plugin

Lubinik Translation is a manual multilingual layer for Lubinik sites. It stores translated values through predictable language suffixes and handles posts, CPT fields, options, menus, shortcode manager labels, taxonomies, forms, sliders, and SEO values.

  • Translation

Inside

StackTranslation
Pluginslubinik-seo-light
01

Problem

Multilingual content in Lubinik does not live only inside post content. It can live in meta fields, options, sliders, menus, taxonomies, forms, shortcode manager settings, SEO fields, and addon-specific structures. A generic translation plugin does not automatically know those custom places.

02

Solution

The translation plugin owns the runtime and admin machinery, while addons and plugins can declare their own translation maps in `config/languages/lubinik-translation.json`. It keeps the default language at root and uses language-prefixed routes for alternatives.

03

Results

Translation rules stay explicit and controlled. Addons can define what is translatable without modifying the translation plugin itself, which matches Lubinik's broader "engine here, rules there" pattern.