Localize category topic templates

Contribute Functie
1

Problem

Discourse’s Content Localization (manual and automatic via Discourse AI) does a great job localizing topic titles, posts, category names and category descriptions. However, category topic templates(categories.topic_template) cannot be localized. In multilingual communities, the composer prefill always appears in the site’s default language — for everyone.

Current behavior

  • CategoryLocalization stores name and description per locale (the Localizable concern provides “multi-locale name/description support” for Topic/Post/Category).
  • The composer always uses the unlocalized topic_template, regardless of the member’s interface locale.

Proposed solution

  • Add topic_template to CategoryLocalization (including the admin localization editor UI).
  • When a member opens the composer in a category, use the template matching their interface locale, with a fallback to the category’s default template if no localization exists.
  • The same gap applies to the newer per-category form templates: they can differ between categories, but there is no locale-aware variant within one category — multilingual setups would have to split their community into separate per-language categories to work around it.

Use case

We run a bilingual community (German default, English via automatic AI translation). Some categories provide structured composer templates with checklist items and an [event] block for the built-in date picker. English-speaking members currently get a German-only template. Our workaround is a single bilingual template (each label duplicated as “German / English” on one line), which works, but it is clunky for both editors and members and doubles the composer content.

Related

  • #32464 (localized categories route) — same localization surface, categories.
1 like