[kevinwu98]

Summary

Adds 18 informational Knowledge Base articles and updates 3 live ones. Each article opens with a direct, quotable answer, cites primary sources, and keeps General Translation to one section after the neutral answer.

New articles

• Internationalization: detect-user-language, find-hardcoded-strings, i18n-key-naming, internationalization-vs-localization, language-switcher, localize-ios-app, make-website-multilingual, pseudo-localization
• Locale formatting: icu-message-format, right-to-left-css
• Multilingual SEO: locale-routing-seo, multilingual-url-structure, what-is-hreflang
• Translation: is-ai-translation-accurate, translate-json-files, translate-markdown-files, translate-srt-subtitles
• Workflow tools: what-is-a-translation-management-system

Updated live articles

• multilingual-nextjs-seo: uses prefixDefaultLocale: true throughout and builds the canonical, hreflang, noindex, and sitemap from one record of each page's published locales. It shows the <head> and sitemap output of a real build, including a page with a missing translation.
• multilingual-app-launch-checklist: retitled to "Localization testing checklist for multilingual apps". General Translation notes are consolidated into one section, FAQs that duplicated other articles are removed, and a sample release record is added.
• general-translation-vs-tms: retitled, with a neutral summary and Crowdin's hourly GitHub sync default (cited). Customer name-drops and Enterprise plugs are removed.
• Link text on the Crowdin, Lokalise, Phrase, Smartling, Symfony Translation, and Transifex comparisons now matches the new general-translation-vs-tms title.

Search and answer-engine work

• Titles use searched wording, and descriptions state the answer within about 155 characters.
• Summaries answer the title first and keep their key qualifications.
• 19 answer sections use question headings, such as "Should you redirect visitors by browser language?"
• Each shared topic has one owning article; other articles keep a short line and link to it. For example, the order of language signals lives in locale-routing-seo, hreflang rules in what-is-hreflang, and plurals in icu-message-format.
• Neutral tables and sections contain no product rows.
• Planned locale-codes and translate-android-strings articles were dropped because they competed with /docs/platform/core/guides/locale-codes and /docs/cli/reference/formats/android-strings-files. Links point to those docs pages instead.

Validation

• validate-kb (52 articles), validate-links, validate-reference-links, and validate-unsafe-html pass.
• Quotes and claims attributed to Google, MDN, W3C, WCAG, RFCs, Apple, Android, Tailwind, Crowdin, React Native, and WMT25 were checked against the live sources. The SOC 2 Type 2 and ISO 27001 claim matches the trust portal.
• Executed examples, with output shown in the articles:
  • Next.js 16.4.2 with gt-next 11.4.14: the routing redirects, <head> tags, noindex, and sitemap.
  • i18next 26.5.3: namespace lookups, and Polish plural selection with and without the few and many keys.
  • The SRT checker on the Spanish and German inputs now shown in the article.
  • Chrome 155: physical vs. logical margins in right-to-left text.
  • The TypeScript-aware ESLint config in find-hardcoded-strings.
• getTextInfo() browser support was checked against @mdn/browser-compat-data.

Limits

• Local checks used Node.js 24; CI runs Node.js 22.
• The Polish example strings were written for the article and haven't been reviewed by a native speaker.
• No live translation API call, full Android build, or Xcode run was made for this revision.
• Tests don't establish translation quality, search rankings, or AI-answer citations; measure those after publication.
• docs/en-US/cli/quickstart.mdx still says the CLI needs Node.js 20, but the published gt package declares no engines field. That docs page is outside this PR.

🤖 Generated with Claude Code

[cursor]

Stale comment

Risk: medium. I left a non-blocking comment and did not approve this PR because 21 new public Knowledge Base articles are above the low-risk, small-blast-radius bar. Human review is needed, and no reviewers were assigned.

  

_{Sent by Cursor Approval Agent: Pull Request Router}

[cursor]

Stale comment

Risk: medium. I left a non-blocking comment and did not approve this PR because 21 new public Knowledge Base articles are above the low-risk, small-blast-radius bar. Human review is needed, and no reviewers were assigned.

  

_{Sent by Cursor Approval Agent: Pull Request Router}

[cursor]

Stale comment

Risk: medium. I left a non-blocking comment and did not approve this PR because 21 new public Knowledge Base articles are above the low-risk, small-blast-radius bar. Human review is needed, and no reviewers were assigned.

  

_{Sent by Cursor Approval Agent: Pull Request Router}

[cursor]

Stale comment

Risk: medium. I left a non-blocking comment and did not approve this PR because 21 new public Knowledge Base articles are above the low-risk, small-blast-radius bar. Human review is needed, and no reviewers were assigned.

  

_{Sent by Cursor Approval Agent: Pull Request Router}

[cursor]

Stale comment

Risk: medium. I left a non-blocking comment and did not approve this PR because 18 new and 3 updated public Knowledge Base articles are above the low-risk, small-blast-radius bar. Human review is needed, and no reviewers were assigned.

  

_{Sent by Cursor Approval Agent: Pull Request Router}

[cursor]

Risk: medium. I left a non-blocking comment and did not approve this PR because 18 new and 3 updated public Knowledge Base articles are above the low-risk, small-blast-radius bar. Human review is needed, and no reviewers were assigned.

  

_{Sent by Cursor Approval Agent: Pull Request Router}