In our current implementation, loose lists and tight lists look the same
visually. Loose lists are lists with blank lines between list items, and
the contents of a list item should be enclosed in a paragraph tag in
that case. For unordered lists, paragraph tags have a bottom margin in
starlight and thus looses lists look much more spaced out than tight
lists.
That is not the behaviour we had in mind while writing the
documentation, the reason we had all these loose lists is to make the
documentation easy to write and read. So we attempt to remove all the
blank lines and fix the problem at source. Since paragraph tags are used
for other purposes in a list in starlight, it won't be a wise decision
to let the source be as is and just change things in css, other expected
behaviours might break in that case. See this topic for more details:
https://chat.zulip.org/#narrow/channel/19-documentation/topic/new.20help.20center.3A.20regressions/near/2226084
All the changes were made by a one-off script which has not been
commited to the repo. The script wasn't perfect and could not decide
between blank lines that make a list loose vs blank lines necessary for
a sub-list or a code block inside a list item. A manual review of all
the changes was done before making this commit to ensure that no
unintended changes were made to the help center files.
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 delete a topic 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/1549
Part of #34748.
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.
