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.
Adds mobile-camera and mobile-image to shared icons.
Deletes static/images/help/mobile-camera-icon.svg,
static/images/help/mobile-image-icon.svg, and
static/images/help/mobile-paperclip.svg as they are no
longer used.
Part of #34748.
The ability to "share to Zulip" from Android apps is not yet implemented
for the initial launch of the Flutter mobile app, so we remove
the legacy React Native app instructions.
This feature is tracked in:
https://github.com/zulip/zulip-flutter/issues/52
Part of #34748.
Note that the link in zulip_update_announcements.py is not updated
so that the content in the source code reflects what users actually
received in the update announcement message.
- Make page title more general.
- Document new option for animated image previews.
- Split instructions for showing different preview types.
- Update intro.
- Changes page title to View images and videos.
- Tweaks intro paragraph and adds desktop/web instructions.
- Splits out browsing other images in the view into its own section.
- Updates page to describe interactions with videos too.
- Tweaks documentation on other pages.
Fixes#27801.
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.
- Replaces the "Via Markdown" tab with "Via drag-and-drop", and
modifies the instructions to explain that you can drag and drop
anywhere in the app, whether or not the compose box is open.
- Adds "Via paste" tab for the copy-pasting instructions.
Fixes#26894.
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.
