mirror of
https://github.com/zulip/zulip.git
synced 2025-11-02 13:03:29 +00:00
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.
4.5 KiB
4.5 KiB
Support the Zulip project
{!supporting-zulip-motivation.md!}
The Zulip community (which includes you!) is a huge part of what makes Zulip successful. If you appreciate Zulip, there are many different ways you can support the project. Some of these will only take a few minutes of your time, but still make a big difference.
- Support Zulip financially: Sponsoring Zulip helps fund free Zulip Cloud Standard hosting for hundreds of open source projects, research communities, and other worthy organizations.
- Help others find Zulip: As a business that's growing sustainably without venture capital funding, Zulip cannot afford splashy ad campaigns to compete with giant corporations like Salesforce (Slack) and Microsoft (Teams). Zulip depends on users and other members of the community to spread the word about the difference that using Zulip's organized team chat has made for you or your organization.
- Help improve Zulip: Zulip is developed by a vibrant open-source community, and there are many ways to contribute even without writing a single line of code.
Support Zulip financially
You can sponsor Zulip through the GitHub sponsors program (preferred), on Patreon, or on Open Collective.
Help others find Zulip
- Link to Zulip from your organization's website. In addition to providing information for anyone browsing your website, this helps people find Zulip in Google and other search engines.
- List your organization in the Zulip communities directory. Browsing open communities helps folks see how others are using Zulip, and learn best practices.
- Star Zulip on GitHub. There are four main repositories: server/web, mobile, desktop, and Python API.
- Review Zulip on product comparison websites, such as G2 and Software Advice. Organizations rely on review sites more and more when choosing software for their team, and sharing your experience with Zulip (good or bad) helps them evaluate whether Zulip might work for their needs.
- Subscribe to our blog, and share our posts.
- Mention Zulip on social media, or like and retweet Zulip's tweets, or retoot Zulip's toots.
- Share your Zulip story on your blog, or get it posted on the Zulip website (contact support@zulip.com to learn more).
- Tell your friends and colleagues about your Zulip experience.
Help improve Zulip
- Report issues, including both feature requests and bug reports. Many improvements to the Zulip app start with a user's suggestion.
- Give feedback if you are evaluating or using Zulip.
- Translate Zulip into your language. Zulip has been translated into over 25 languages by an amazing group of volunteers, and you can help expand, improve, and maintain the translation for your language, or start working on a language that hasn't been covered yet.
- Contribute code to the Zulip open-source project. To make it easy for contributors from a variety of backgrounds to get started, we have invested into making Zulip’s code uniquely readable, well tested, and easy to modify.