7ce87c66ac
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.
3.5 KiB
Contact support
We're here to help! This page will guide you to the best way to reach us.
Zulip community
The primary communication forum for the Zulip community is the Zulip server hosted at chat.zulip.org. Users and administrators of Zulip organizations stop by to ask questions, offer feedback, and participate in product design discussions.
Everyone is welcome to sign up and participate — we love hearing from our users! Please see the Zulip development community guide for detailed instructions on how to join the community, community norms and where to ask your questions or give feedback.
Support requests
-
For support requests regarding your Zulip Cloud organization, you can request interactive chat support in the Zulip development community, or email Zulip support.
- Response time: Usually within 1-3 business days, or within one business day for paid customers.
-
For support requests regarding your self-hosted server:
- Business and Enterprise plan customers can request interactive
chat support in the Zulip development community,
or email Zulip support. Phone support is
available for Enterprise customers upon request.
- Response time: Usually within one business day.
- Free and Community plan customers can ask for help in the Zulip development community. You will usually get a friendly reply within 1-3 business days.
- Business and Enterprise plan customers can request interactive
chat support in the Zulip development community,
or email Zulip support. Phone support is
available for Enterprise customers upon request.
Sales, billing, and partnerships
For sales, billing, partnerships, and other commercial questions, contact sales@zulip.com. Response time: Usually within one business day.
Product feedback
Your feedback helps us make Zulip better for everyone! Please reach out if you have questions, suggestions, or just want to brainstorm how to make Zulip work for your organization.
- There are several
ways
to report possible bugs.
- Response time: Usually within 1-3 business days in the Zulip development community or by email, or within one week on GitHub.
- You can request
features
or share
feedback.
Many improvements to the Zulip app start with a user's suggestion.
- Response time: Usually within 1-3 business days in the Zulip development community or by email, or within one week on GitHub.
- To report issues or share feedback privately, contact
feedback@zulip.com. This works well if you'd like
to include details about your organization that shouldn't be posted in public.
- Response time: Usually within 1-3 business days.