I’m struggling a bit with multi language setups and content synchronisation.
When using good old fields, everything works quite well. Empty translations are replaced with default languages and so on. This works as long as you start from the default language then translate the page.
But for more complex fields such as layouts, blocks and structure, offering modular content, it quickly gets more complicated and you have to double-edit every single language using finger & brain power.
IMO there should be better options/workflows to translate content and keep the data structure in sync on both languages.
- In a structure field storing sets of url+title, adding an url in one language should also add the structure entry in the other languages. The url should be synced between languages (non translateable), while the title should be translateable.
- In a layout field, I decide to add a row with some text. I’d like the row to also appear (empty) on the other languages.
- Adding or removing a block, I’d like the same action to be performed on other languages.
- In a tags field I’d like to have the same set of tags across translations, but still allow translation of their text labels.
I guess I’m not the only one encountering such multi language content issues.
What solutions have you found for keeping content-structure and content-translations in sync ?
To me it feels a bit like the new blocks and layouts have broken the easy translation logic that Kirby used to have, making them an unreliable choice in multilanguage setups.
Are there any plans on the Kirby side to improve translations of modular content fields. ?