How to Sync Translations for New Features?

Current Issue

Raised in https://github.com/processing/p5.js-web-editor/pull/3656 by @cassiano!

When new features are added, the English text often gets merged before translations are in place. This leads to inconsistencies where:

• Some UI elements remain untranslated until someone notices and adds them later.
• Tests that depend on translation keys may fail or be harder to maintain.

Questions for Discussion

• Should new features be blocked from merging until at least the base translation keys are added?
• How do we want to handle updates when translations for all languages aren’t ready yet? For example, do we want to first merge with English placeholders and track missing translations separately? Or should werequire at least key/value stubs for all supported languages?
• Can we automate parts of this workflow (protentially utilizing https://github.com/processing/p5.js-web-editor/issues/3609)?

Start by reading the discussion in PR 3656 and the related issue 3609. Compare the proposed approaches for base keys, placeholders, supported-language stubs, and automation; the work is done when the project has an agreed translation-sync workflow and its implementation scope is defined.