Internationalization (i18n) & Localization Support

Quackback should support multiple languages so teams can collect feedback from users across different locales.

Problem

The UI and public feedback portal are English-only, limiting adoption for companies with a global user base.

Proposed Solution

• Let admins configure supported languages for their portal (board titles, categories, status labels, UI chrome).
• Auto-detect locale from the browser's Accept-Language header, with a manual override.
• Store translatable strings as JSON resource bundles so self-hosted operators can contribute or customize translations.
• Respect the host application's locale in the SDK and embeddable widget.
• Support RTL layouts for languages like Arabic and Hebrew.

Why It Matters

Many open-source tools lose out to commercial alternatives simply because they lack localization. Adding i18n early keeps Quackback competitive for international teams and aligns with the community-driven, self-hosted model where contributors can submit locale packs.