Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

💡 [REQUEST] - Knowledge Base (CMS) Translation Support #804

Open
medchedli opened this issue Feb 28, 2025 · 0 comments
Open

💡 [REQUEST] - Knowledge Base (CMS) Translation Support #804

medchedli opened this issue Feb 28, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@medchedli
Copy link
Contributor

medchedli commented Feb 28, 2025

Summary

This feature request proposes adding support for translating the content stored within the Hexabot's knowledge base (CMS). This would enable users to create and manage multilingual knowledge bases, significantly enhancing the chatbot's ability to provide accurate and relevant responses to users in different languages.

Currently, Hexabot's GenAI custom block relies on the knowledge base content to provide context for its responses. However, if the knowledge base is only available in a single language, the chatbot's effectiveness is limited when interacting with users who speak other languages.

Basic Example

  • Content Field Translation: Allow users to create and manage translations for individual content fields within the CMS (e.g., title, content, keywords).
  • Language Selection: Implement a language selection mechanism within the CMS interface to allow users to specify the language of each translation.
  • Translation Management UI: Provide a user-friendly interface for managing translations, including features for adding, editing, and deleting translations.
  • Integration with Translation Services (Optional): Consider integrating with external translation APIs (e.g., Google Translate, DeepL) to automate the translation process.
  • Language detection: allow the bot to detect the user language and use the appropriate translation of the CMS to provide the context to the LLM.
  • Fallback Mechanism: Implement a fallback mechanism to handle cases where a translation is not available for a specific language. For example, the chatbot could default to the primary language or display a message indicating that the content is not available in the requested language.

Drawbacks

  • Implementation complexity of managing multilingual content.
  • Cost of integrating with external translation services (if applicable).
  • Maintaining translation consistency.
@medchedli medchedli added the enhancement New feature or request label Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant