Feature Suggestion: Inline Translation Variables for Custom Sections

[rorar]

Hey! Stumbled onto a use case while working with Custom Sections and wanted to share.

The Current Situation

Custom sections are great for free-form content:

• bullet lists,
• timelines,
• free text,
  ... you name it.
  But if you're managing a CV in multiple languages, you quickly run into a repetitive problem: the same content needs to exist in multiple versions, spread across separate sections or datasets.

For example, a membership timeline might look like this in a bullet list:

de

2024 - heute: Mitglied
2023 - 2024: Vorstand, Kassenprüfer
2017 - 2023: Mitglied

en

2024 - present: Member
2023 - 2024: Board member, auditor
2017 - 2023: Member

To get this translated, you'd need separate Custom Sections for each language, which gets tedious fast.

The Idea

What if text in Custom Sections could include inline translation variables?

Something like:

{{mitglied=de:Mitglied|en:member|fr:membre}}

When rendered, it picks the right translation based on the current language. The entered strings also populate a global dictionary; so once you've written {{mitglied=en:member}} somewhere, you can reuse {{mitglied}} anywhere else and it'll auto-fill.

The Hybrid UX

The best of both worlds:

Inline authoring: Write translations right where you need them. The syntax is self-contained, copy-paste friendly, and doesn't require a separate workflow.

Global dictionary: All entered translations are collected in one place (maybe a "Translations" panel in Settings). Edit once, update everywhere. Bulk management for when you want to review or tweak.

Auto-add: If you write {{mitglied}} without translations, it could auto-detect the current language text and prompt to add it to the dictionary.

Possible gap to explore

What if users want to translate a whole text with formatting instead of just a string?

Editor Integration (Future)

If the text editor for Custom Sections ever gets a toolbar with formatting controls (bold, italic, typography, etc.), a "Insert Translation" button could live right there:
Click, pick or create a variable, and it inserts the syntax.
Keeps translation authoring in context without switching contexts.

Technical Pointer

For anyone who wants to explore this, a couple of starting points:

• The rendering pipeline in scripts.js already handles escapeHtml() and renderMarkdown() — that's where variable substitution could hook in
• A new translations table in the DB (key → language → value) would store the dictionary
• Regex to catch {{key|locale:text|locale:text}} and resolve against current locale, falling back to key name if missing

That's the gist. Happy to help test or clarify the use case if this gets picked up!