How to translate items added via "Edit Custom Section" and Theme <head>?

תמיכה
1

Hello everyone,

I am trying to make my forum fully compatible with multiple languages, but I am not sure how to translate the custom text elements I have added to the UI.

image
image1372×529 29.8 KB

As you can see in the screenshot:

  1. Left Sidebar: I added several custom links (e.g., “Küresel Liderlik Tablosu”, “RSS Beslemesi”) using the “Edit Custom Section” feature.
  2. Top Navigation: I added custom menu items (e.g., “Gündem”, “Etkinlikler”) by inserting code into the <head> section via Themes.

Currently, all of these are hardcoded in one language. What is the best practice for localizing these specific additions? Is there a way to use translation keys so they automatically adapt to the user’s selected interface language?

Any guidance or examples would be greatly appreciated. Thank you!

2

There is a feature request for #1 here: Feature request: make it possible to translate custom sidebar links and sections. So I don’t think it’s currently possible. You can vote on it to show that it matters to you.
That said, I know custom badges can be translated via the rails console, but I haven’t tried if that also works for the sidebar. In case you want to try it, it was explained here: How can badges and groups be localized (multilingual)? - #8 by nat

Theme components support localization. There is a short guide about it here:

I usually prefer to look at examples. There are lots of theme components in Customization > Theme component. I think Topic Status Filter is a quite simple one. Custom Top Navigation Links might be a helpful example too. It’s closer to what you want to do, but it doesn’t support localizable links, because combining that with them being configurable is difficult.
I don’t know if something similar is possible directly in the <head> section.

3

Thanks for the info! I actually tried the Custom Top Navigation Links component, but it caused that section to not show up at all on mobile. That’s why I ended up using <head> injection instead.