Built-in language support

docmd and its official plugins (Search, Threads, etc.) ship with built-in translations for common languages. When you configure a supported locale, all system text — search placeholders, navigation labels, theme toggles — is automatically translated.

For unsupported languages or custom phrasing, the system falls back to English. You can override any string per locale.

Custom UI strings

Use the translations property on any locale to override system text:

export default {
  i18n: {
    default: 'en',
    locales: [
      { id: 'en', label: 'English' },
      {
        id: 'ar',
        label: 'العربية',
        dir: 'rtl',
        translations: {
          onThisPage: 'في هذه الصفحة',
          previous: 'السابق',
          next: 'التالي',
          search: 'بحث',
          toggleTheme: 'تبديل المظهر',
          editThisPage: 'تعديل هذه الصفحة',
          selectLanguage: 'اختر اللغة',
          selectVersion: 'اختر الإصدار',
          fallbackMessage: 'هذه الصفحة غير متاحة بعد باللغة {active}. عرض اللغة الافتراضية ({default}).'
        }
      }
    ]
  }
}

The merge order is: system translations → plugin translations → your config translations. Your config always wins.

Available keys

The fallbackMessage key supports {active} and {default} placeholders, replaced with locale labels at build time.

SEO and hreflang

docmd automatically generates <link rel="alternate" hreflang="..."> tags for every page across all locales. The default locale also receives the x-default hreflang value.

<!-- Generated automatically on every page -->
<link rel="alternate" hreflang="en" href="/">
<link rel="alternate" hreflang="x-default" href="/">
<link rel="alternate" hreflang="hi" href="/hi/">
<link rel="alternate" hreflang="zh" href="/zh/">

No configuration is required — these tags are injected into every page when i18n is enabled.