-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Localize content (description, footer, etc.) on status pages #2784
Comments
Yes I am talking about the part you provided the screenshot for. In my opinion a Statuspage is visited by multiple (thousands) people all around the world. For an Website / Service that is available world-wide and thus translated to many different languages aswell, it would be nice to give context in different languages. The current "Workaround" is setting up multiple Statuspages with different default languages (living under different subdomains). The problem with this one is, that you have to schedule an downtime in all of those instances or one of the regions would have different information than other. Still I want to thank you for your reply @CommanderStorm - great work with Kuma! |
Yea, setting up multiple status pages for this sounds like a lot of work… Getting this done will require #2196 and/or #1643 first, as the status page is not quite synced with the current locale (see #3487) and do not have a concept of multiple locales. |
thats absolutely no worries. If it happens, it happens. If it does not reach main or is "worth" enough, that's no problem either. Just wanted to raise this issue / feature request because I think that I am not the only one thinking of that. Let's see what happens, cheers! |
🏷️ Feature Request Type
UI Feature
🔖 Feature description
There should be a possibility in the UI to localize description, footer, title, etc.
This would easily implement as a additional feature (completely optional), because the status page itself is already localized. It would just add the possibility to display different content specific to the language that has been „guessed" by uptime-kuma.
If this feature is somewhat relevant and usefull, I could give implementing it as a feature a try 🤝
Just wanted to make sure to not waste my time on an unwanted implementation
✔️ Solution
There should be some kind of language-explorer in the status page settings where so called „language-keys“ should be defineable, that will be parsed to the guessed language as soon as the page loads.
As I have not looked into an simple implementation for it, it could not say what new ui elements would be needed (maybe some kind of context-menu).
❓ Alternatives
No response
📝 Additional Context
Uptime-Kuma is really great and super well implemented as well as maintained. Having user-defined content localized would elevate the functionality even further.
The text was updated successfully, but these errors were encountered: