GitBook
Language support for UI elements. #291
Replies: 2 comments
-
|
This feature will be very useful. I can't use Gibook for documents that I want to create in my local language. When the content is in a different language and the interface components are in a different language, it looks amateurish. Also, I think the views on SEO are quite justified. There should be a simple interface where we can localize the text of the interface components. At least I think it would not be difficult to quickly add Latin languages to Gitbook in line with the requests. |
Beta Was this translation helpful? Give feedback.
-
|
I hope this support is added soon. The documentation I wrote is written in a language not supported by the GitBook UI, and the UI is not localized, so it may look amateurish, as @say-borusan 's commented. There is also the issue of SEO, as mentioned in the text. My document is lagging behind in search results! |
Beta Was this translation helpful? Give feedback.
-
While the existing functionality to publish multiple versions and to handle translations via GitHub actions is fine, it has room for enhancement, especially in terms of user experience (UX) and search engine optimization (SEO).
Current Limitations:
<html lang="en">, which can detrimentally affect SEO.Proposed Feature:
Custom Translation for UI Elements
Allow users to provide custom translations for specific UI elements (basically a custom map for translation keys).
Since the number of UI elements that require translation isn't extensive, this feature would be manageable for end-users to implement.
The Impact:
Beta Was this translation helpful? Give feedback.
All reactions