You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Status Desktop and probably Status Mobile we'll be using hardcoded URLs to take the user to a specific help page, depending on app context. For example in Status Desktop there's a button to open this URL in an external browser: https://help.status.im/en/status-communities/about-the-control-node-in-status-communities.
Please note the en language is hardcoded in the URL because the help pages does not support multiple languages. This means a user won't be able to see the proper web page even if multi-language support will be available post MVP because English is hardcoded in the URL.
Generally speaking it's harder to bring updates to the desktop app user as opposed to the web user and there's a chance some app users can't benefit from multi-language documentation even if it will become available.
The proposed solution to this is to have the ability to use a help URL without specifying the language and to get redirected to a specific language based on the system/browser settings.
@prichodko, @marcelines, @felicio I'd appreciate some thoughts on this. Is it something worth considering when moving the documentation pages to the new domain?
Regarding language support for Status Help, the MVP version is English-only, and we don't plan to include new languages until 2024, earliest. However, considering we'll have new languages AND that URLs are hardcoded in Status desktop, it may be a good idea to think about that now. I leave this decision up to you, @prichodko; I know the list of priorities is pilling up quickly.
The discussion here will provide some context: status-im/status-desktop#11430 (comment)
Motivation
In Status Desktop and probably Status Mobile we'll be using hardcoded URLs to take the user to a specific help page, depending on app context. For example in Status Desktop there's a button to open this URL in an external browser: https://help.status.im/en/status-communities/about-the-control-node-in-status-communities.
Please note the
en
language is hardcoded in the URL because the help pages does not support multiple languages. This means a user won't be able to see the proper web page even if multi-language support will be available post MVP because English is hardcoded in the URL.Generally speaking it's harder to bring updates to the desktop app user as opposed to the web user and there's a chance some app users can't benefit from multi-language documentation even if it will become available.
The proposed solution to this is to have the ability to use a help URL without specifying the language and to get redirected to a specific language based on the system/browser settings.
Eg:
No support for multi-language:
https://help.status.im/status-communities/about-the-control-node-in-status-communities will redirect to https://help.status.im/en/status-communities/about-the-control-node-in-status-communities
Multi-language support enabled:
https://help.status.im/status-communities/about-the-control-node-in-status-communities will redirect to
https://help.status.im/[user language]/status-communities/about-the-control-node-in-status-communities
The text was updated successfully, but these errors were encountered: