KamoCRM

Say which locales each public article is really translated into

FeatureKBService
Shipped
11 செப்டம்பர், 2026 அன்று 7:16 PM UTC
Author
Kamo
Commit
6f016ad

The marketing site's sitemap now lists every language version of every help-center, documentation and API-reference article, and each article page names the others as its hreflang alternates. Neither could tell a translation from an echo: TranslateService answers directions it has no provider for with the English source, so the sw and ta rows repeat the English title and body word for word (measured 2026-09-11). Naming those would point search engines at pages that canonical back to English. Tree nodes and single reads now carry `locales`: the locales whose title or body differs from the English article. The body alone is enough - an Arabic row can keep the English title over a translated body. Computed in one query per request by KbTranslatedLocalesService, which reads through the EntityManager so no shared-library release is needed.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing