For mobile features that were documented and implemented for the legacy
React Native app, adds back a tabbed block for mobile with a note to
use the web app instructions in a mobile device browser, and with a
link to the Flutter GitHub issues tracking implementing the feature in
the new mobile app.
If the feature is a mobile only feature, then adds the link to the
Flutter GitHub issue in a warning note.
The ability to change the language setting is not yet implemented
for the initial launch of the Flutter mobile app, so we remove
the legacy React Native app instructions.
Deletes static/images/help/mobile-chevron-left.svg as it is no
longer used.
This feature is tracked in:
https://github.com/zulip/zulip-flutter/issues/1139
Part of #34748.
Renames CSS rule that styles Zulip UI icons in the help center
so that it makes sense to use it regardless of whether we are
documenting a mobile or desktop/web feature.
- Documents how to figure out whether the Zulip font supports a
language and what to do about unsupported languages, providing
links to official font / browser documentation rather than
step-by-step instructions in case the instructions change.
Fixes#26986.
This includes changing the URL to #settings/preferences, with a
transparent redirect so that existing links, like the one from Welcome
Bot, continue to work.
Rename the 'language-time' title to 'General'. As the 'language-time'
section no longer exists, replace the 'lang-time-settings' classname
with the 'general-settings' classname in the 'settings_display.js' file.
Updated the 'change-the-time-format.md' and 'change-your-language.md'
documentation files to reflect these changes.
To pass the puppeteer_test Replaced the 'lang-time-settings-status'
classname to 'general-settings-status' inside 'settings.test.ts' file.
These files are not Jinja2 templates, so there's no reason that they needed
to be inside `templates/zerver`. Moving them to the top level reflects their
importance and also makes it feel nicer to work on editing the help center content,
without it being unnecessary buried deep in the codebase.
