From 454a9004871917b212056ec2f8cc6b555054fe02 Mon Sep 17 00:00:00 2001 From: Tim Abbott Date: Sun, 25 Jul 2021 22:04:26 -0700 Subject: [PATCH] docs: Replace chat-zulip-org page with /developer-community/. --- CONTRIBUTING.md | 8 +- README.md | 4 +- docs/contributing/chat-zulip-org.md | 127 --------------------- docs/contributing/code-reviewing.md | 2 +- docs/contributing/gsoc-ideas.md | 6 +- docs/contributing/index.rst | 1 - docs/development/setup-advanced.md | 2 +- docs/development/setup-vagrant.md | 8 +- docs/index.rst | 6 +- docs/overview/release-lifecycle.md | 4 +- docs/production/install-existing-server.md | 2 +- docs/production/install.md | 2 +- docs/production/requirements.md | 2 +- docs/production/security-model.md | 2 +- docs/production/settings.md | 2 +- docs/production/upgrade-or-modify.md | 4 +- docs/subsystems/performance.md | 2 +- docs/testing/linters.md | 2 +- docs/translating/translating.md | 4 +- templates/zerver/faq.html | 2 +- templates/zerver/footer.html | 2 +- templates/zerver/for-research.html | 2 +- templates/zerver/for/communities.md | 2 +- templates/zerver/for/tum-case-study.md | 2 +- templates/zerver/hello.html | 2 +- templates/zerver/help/contact-support.md | 2 +- templates/zerver/landing_nav.html | 2 +- 27 files changed, 39 insertions(+), 167 deletions(-) delete mode 100644 docs/contributing/chat-zulip-org.md diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index e27092fd3d..765758089f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -5,11 +5,11 @@ Welcome to the Zulip community! ## Community The -[Zulip community server](https://zulip.readthedocs.io/en/latest/contributing/chat-zulip-org.html) +[Zulip community server](https://zulip.com/developer-community/) is the primary communication forum for the Zulip community. It is a good place to start whether you have a question, are a new contributor, are a new user, or anything else. Make sure to read the -[community norms](https://zulip.readthedocs.io/en/latest/contributing/chat-zulip-org.html#community-norms) +[community norms](https://zulip.com/developer-community/#community-norms) before posting. The Zulip community is also governed by a [code of conduct](https://zulip.readthedocs.io/en/latest/code-of-conduct.html). @@ -58,7 +58,7 @@ contributor. It's long, but don't worry about doing all the steps perfectly; no one gets it right the first time, and there are a lot of people available to help. * First, make an account on the - [Zulip community server](https://zulip.readthedocs.io/en/latest/contributing/chat-zulip-org.html), + [Zulip community server](https://zulip.com/developer-community/), paying special attention to the community norms. If you'd like, introduce yourself in [#new members](https://chat.zulip.org/#narrow/stream/95-new-members), using @@ -206,7 +206,7 @@ is, the best place to post issues is [#issues](https://chat.zulip.org/#narrow/stream/9-issues) (or [#mobile](https://chat.zulip.org/#narrow/stream/48-mobile) or [#desktop](https://chat.zulip.org/#narrow/stream/16-desktop)) on the -[Zulip community server](https://zulip.readthedocs.io/en/latest/contributing/chat-zulip-org.html). +[Zulip community server](https://zulip.com/developer-community/). This allows us to interactively figure out what is going on, let you know if a similar issue has already been opened, and collect any other information we need. Choose a 2-4 word topic that describes the issue, explain the issue diff --git a/README.md b/README.md index 5c7f0fb62c..16d2f7a37c 100644 --- a/README.md +++ b/README.md @@ -25,7 +25,7 @@ largest and fastest growing open source group chat project. Click on the appropriate link below. If nothing seems to apply, join us on the -[Zulip community server](https://zulip.readthedocs.io/en/latest/contributing/chat-zulip-org.html) +[Zulip community server](https://zulip.com/developer-community/) and tell us what's up! You might be interested in: @@ -52,7 +52,7 @@ You might be interested in: * **Checking Zulip out**. The best way to see Zulip in action is to drop by the - [Zulip community server](https://zulip.readthedocs.io/en/latest/contributing/chat-zulip-org.html). We + [Zulip community server](https://zulip.com/developer-community/). We also recommend reading Zulip for [open source](https://zulip.com/for/open-source/), Zulip for [companies](https://zulip.com/for/companies/), or Zulip for diff --git a/docs/contributing/chat-zulip-org.md b/docs/contributing/chat-zulip-org.md deleted file mode 100644 index 7a0b08d469..0000000000 --- a/docs/contributing/chat-zulip-org.md +++ /dev/null @@ -1,127 +0,0 @@ -# The chat.zulip.org community - -[https://chat.zulip.org](https://chat.zulip.org/) is the primary communication -forum for the Zulip community. - -You can go through the simple signup process at that link, and then -you will soon be talking to core Zulip developers and other users. To -get help in real time, you will have the best luck finding core -developers roughly between 17:00 UTC and 6:00 UTC, but the sun never -sets on the Zulip community. Most questions get a reply within -minutes to a few hours, depending on the time of day. - -## Community norms - -* Send test messages to - [#test here](https://chat.zulip.org/#narrow/stream/7-test-here) or - as a PM to yourself to avoid disturbing others. -* When asking for help, provide the details needed for others to help - you. E.g. include the full traceback in a code block (not a - screenshot), a link to the code or a WIP PR you're having trouble - debugging, etc. -* Ask questions on streams rather than PMing core contributors. - You'll get answers faster since other people can help, and it makes - it possible for other developers to learn from reading the discussion. -* Use @-mentions sparingly. Unlike IRC or Slack, in Zulip, it's - usually easy to see which message you're replying to, so you don't - need to mention your conversation partner in every reply. - Mentioning other users is great for timely questions or making sure - someone who is not online sees your message. -* Converse informally; there's no need to use titles like "Sir" or "Madam". -* Use - [gender-neutral language](https://en.wikipedia.org/wiki/Gender-neutral_language). - For example, avoid using a pronoun like her or his in sentences like - "Every developer should clean [their] keyboard at least once a week." -* Follow the community [code of conduct](../code-of-conduct.md). -* Participate! Zulip is a friendly and welcoming community, and we - love meeting new people, hearing about what brought them to Zulip, - and getting their feedback. If you're not sure where to start, - introduce yourself and your interests in - [#new members](https://chat.zulip.org/#narrow/stream/95-new-members), - using your name as the topic. - -## High traffic community - -The chat.zulip.org community sends several thousand messages every -single week, about half of them to streams that we have included in -the default streams for new users for discoverability. Keeping up -with **everything** happening in the Zulip project is both difficult -and rarely a useful goal. - -To make the best use of your time, we highly recommend that you -unsubscribe from streams that you aren't interested in, and mute -streams that are only of occasional interest. - -## This is a bleeding edge development server - -The chat.zulip.org server is frequently deployed off of `master` from -the Zulip Git repository, so please point out anything you notice that -seems wrong! We catch many bugs that escape code review this way. - -The chat.zulip.org server is a development and testing server, not a -production service, so don't use it for anything mission-critical, -secret/embarrassing, etc. - -## Streams - -There are a few streams worth highlighting that are relevant for -everyone, even non-developers: - -* [#announce](https://chat.zulip.org/#narrow/stream/1-announce) is for - announcements and discussions thereof; we try to keep traffic there - to a minimum. -* [#feedback](https://chat.zulip.org/#narrow/stream/137-feedback) is for - posting feedback on Zulip. -* [#design](https://chat.zulip.org/#narrow/stream/101-design) is where we - discuss UI and feature design and collect feedback on potential design - changes. We love feedback, so don't hesitate to speak up! -* [#user community](https://chat.zulip.org/#narrow/stream/138-user-community) is - for Zulip users to discuss their experiences using and adopting Zulip. -* [#production help](https://chat.zulip.org/#narrow/stream/31-production-help) - is for production environment related discussions. -* [#test here](https://chat.zulip.org/#narrow/stream/7-test-here) is - for sending test messages without inconveniencing other users :). - We recommend muting this stream when not using it. - -There are dozens of streams for development discussions in the Zulip -community (e.g. one for each app, etc.); check out the -[Streams page](https://chat.zulip.org/#streams/all) to see the -descriptions for all of them. Relevant to almost everyone are these: - -* [#checkins](https://chat.zulip.org/#narrow/stream/65-checkins) is for - progress updates on what you're working on and its status; usually - folks post with their name as the topic. Everyone is welcome to - participate! -* [#development help](https://chat.zulip.org/#narrow/stream/49-development-help) - is for asking for help with any Zulip server/web app development work - (use the app streams for help working on one of the apps). -* [#code review](https://chat.zulip.org/#narrow/stream/91-code-review) - is for getting feedback on your work. We encourage all developers - to comment on work posted here, even if you're new to the Zulip - project; reviewing other PRs is a great way to develop experience, - and even just manually testing a proposed new feature and posting - feedback is super helpful. -* [#documentation](https://chat.zulip.org/#narrow/stream/19-documentation) - is where we discuss improving Zulip's user, sysadmin, and developer - documentation. -* [#translation](https://chat.zulip.org/#narrow/stream/58-translation) is - for discussing Zulip's translations. -* [#learning](https://chat.zulip.org/#narrow/stream/92-learning) is for - posting great learning resources one comes across. - -There are also official private streams, including large ones for -established community contributors (and for GSoC mentors), and small -streams where Kandra Labs staff can discuss customer support, -production server operations, and security issues. Because our -community values are to work in the open, these private streams are -relatively low traffic. - -## Searching for past conversations - -When [searching][] for previous discussions of a given topic, we -recommend using the `streams:public keyword` set of operators. This -will search the full history of public streams in the organization for -`keyword` (including messages sent before you joined and on public -streams you're not subscribed to). - -[searching]: https://zulip.com/help/search-for-messages diff --git a/docs/contributing/code-reviewing.md b/docs/contributing/code-reviewing.md index 8cdc159433..2720f80724 100644 --- a/docs/contributing/code-reviewing.md +++ b/docs/contributing/code-reviewing.md @@ -15,7 +15,7 @@ this?". Good choices include Alternatively, posting a message in [#code-review](https://chat.zulip.org/#narrow/stream/91-code-review) on [the Zulip -development community server](../contributing/chat-zulip-org.md), would +development community server](https://zulip.com/developer-community/), would help in reaching out to a wider group of reviewers. Either way, please be patient and mindful of the fact that it isn't possible to provide a quick reply always, but that the reviewer would get to it sooner or later. diff --git a/docs/contributing/gsoc-ideas.md b/docs/contributing/gsoc-ideas.md index fd2a32d966..3bf6d6d489 100644 --- a/docs/contributing/gsoc-ideas.md +++ b/docs/contributing/gsoc-ideas.md @@ -81,7 +81,7 @@ tasks that are great for first-time contributors. Use to get your Zulip development environment set up and to find your first issue. If you have any trouble, please speak up in [#GSoC](https://chat.zulip.org/#narrow/stream/14-GSoC) on -[the Zulip development community server](../contributing/chat-zulip-org.md) +[the Zulip development community server](https://zulip.com/developer-community/) (use your name as the topic). ## Application tips, and how to be a strong candidate @@ -127,7 +127,7 @@ application deadline. We are more interested in candidates if we see them submitting good contributions to Zulip projects, helping other applicants on GitHub and on -[chat.zulip.org](../contributing/chat-zulip-org.md), +[chat.zulip.org](https://zulip.com/developer-community/), learning from our suggestions, [trying to solve their own obstacles and then asking well-formed questions](https://blogs.akamai.com/2013/10/you-must-try-and-then-you-must-ask.html), @@ -171,7 +171,7 @@ part on who is a good fit for the needs of each student as well as technical expertise as well as who has available time during the summer. You can reach us via [#GSoC](https://chat.zulip.org/#narrow/stream/14-GSoC) on [the Zulip -development community server](../contributing/chat-zulip-org.md), +development community server](https://zulip.com/developer-community/), (compose a new stream message with your name as the topic). Zulip operates under group mentorship. That means you should diff --git a/docs/contributing/index.rst b/docs/contributing/index.rst index b3e8597b56..e233722bd4 100644 --- a/docs/contributing/index.rst +++ b/docs/contributing/index.rst @@ -8,7 +8,6 @@ Code contribution guide version-control code-style code-reviewing - chat-zulip-org zulipbot-usage accessibility bug-reports diff --git a/docs/development/setup-advanced.md b/docs/development/setup-advanced.md index c37df21f39..6bc0a8da82 100644 --- a/docs/development/setup-advanced.md +++ b/docs/development/setup-advanced.md @@ -263,7 +263,7 @@ expected. As with other installation methods, please visit [#provision help][provision-help] in the [Zulip development community -server](../contributing/chat-zulip-org.md) if you need help. +server](https://zulip.com/developer-community/) if you need help. [provision-help]: https://chat.zulip.org/#narrow/stream/21-provision-help diff --git a/docs/development/setup-vagrant.md b/docs/development/setup-vagrant.md index 8591b8f99a..b3e203a8a9 100644 --- a/docs/development/setup-vagrant.md +++ b/docs/development/setup-vagrant.md @@ -27,7 +27,7 @@ errors](#troubleshooting-and-common-errors). If that doesn't help, please visit [#provision help](https://chat.zulip.org/#narrow/stream/21-provision-help) in the [Zulip development community -server](../contributing/chat-zulip-org.md) for real-time help or +server](https://zulip.com/developer-community/) for real-time help or [file an issue](https://github.com/zulip/zulip/issues). When reporting your issue, please include the following information: @@ -319,7 +319,7 @@ documented in the [Troubleshooting and common errors](#troubleshooting-and-common-errors) section. If that doesn't help, please visit [#provision help](https://chat.zulip.org/#narrow/stream/21-provision-help) -in the [Zulip development community server](../contributing/chat-zulip-org.md) for +in the [Zulip development community server](https://zulip.com/developer-community/) for real-time help. On Windows, you will see the message `The system cannot find the path @@ -460,7 +460,7 @@ After provisioning, you'll want to If you run into any trouble, [#provision help](https://chat.zulip.org/#narrow/stream/21-provision-help) in the [Zulip development community -server](../contributing/chat-zulip-org.md) is a great place to ask for +server](https://zulip.com/developer-community/) is a great place to ask for help. #### Rebuilding the development environment @@ -558,7 +558,7 @@ If these solutions aren't working for you or you encounter an issue not documented below, there are a few ways to get further help: * Ask in [#provision help](https://chat.zulip.org/#narrow/stream/21-provision-help) - in the [Zulip development community server](../contributing/chat-zulip-org.md). + in the [Zulip development community server](https://zulip.com/developer-community/). * [File an issue](https://github.com/zulip/zulip/issues). When reporting your issue, please include the following information: diff --git a/docs/index.rst b/docs/index.rst index 75fef090ff..5fcfe10db4 100644 --- a/docs/index.rst +++ b/docs/index.rst @@ -20,9 +20,9 @@ Welcome! Zulip's documentation is split into four parts: Zulip has well over 150,000 words of documentation. If you can't find what you're looking for, please `let us know -`__! Further information on the -Zulip project and its features can be found at `https://www.zulip.com -`__. +`__! Further information on the +Zulip project and its features can be found at `https://zulip.com +`__. This site contains our installation and contributor documentation. If this is your first time here, you may want to start with `Production diff --git a/docs/overview/release-lifecycle.md b/docs/overview/release-lifecycle.md index 38aaa0c1a8..45a5a50d2b 100644 --- a/docs/overview/release-lifecycle.md +++ b/docs/overview/release-lifecycle.md @@ -179,7 +179,7 @@ do not have any of these priority labels. We welcome participation from our user community in influencing the Zulip roadmap. If a bug or missing feature is causing significant pain for you, we'd love to hear from you, either in -[chat.zulip.org](../contributing/chat-zulip-org.md) or on the relevant +[chat.zulip.org](https://zulip.com/developer-community/) or on the relevant GitHub issue. Please an include an explanation of your use case: such details can be extremely helpful in designing appropriately general solutions, and also helps us identify cases where an existing solution @@ -229,7 +229,7 @@ independently as needed. [electron]: https://www.electronjs.org/ [upgrading-to-master]: ../production/upgrade-or-modify.html#upgrading-to-master [os-upgrade]: ../production/upgrade-or-modify.html#upgrading-the-operating-system -[chat-zulip-org]: ../contributing/chat-zulip-org.md +[chat-zulip-org]: https://zulip.com/developer-community/ [fork-zulip]: ../production/upgrade-or-modify.html#modifying-zulip [zulip-server]: https://github.com/zulip/zulip diff --git a/docs/production/install-existing-server.md b/docs/production/install-existing-server.md index fdd3b80d82..d66cd80fec 100644 --- a/docs/production/install-existing-server.md +++ b/docs/production/install-existing-server.md @@ -98,5 +98,5 @@ We don't provide a convenient way to uninstall a Zulip server. Most of the limitations are things we'd accept a pull request to fix; we welcome contributions to shrink this list of gotchas. Chat with us -in the [chat.zulip.org community](../contributing/chat-zulip-org.md) if you're +in the [chat.zulip.org community](https://zulip.com/developer-community/) if you're interested in helping! diff --git a/docs/production/install.md b/docs/production/install.md index 43b7f66238..b680c6d75d 100644 --- a/docs/production/install.md +++ b/docs/production/install.md @@ -176,6 +176,6 @@ out! Please provide details like the full traceback from the bottom of `/var/log/zulip/errors.log` in your report (ideally in a [code block][code-block]). -[chat-zulip-org]: ../contributing/chat-zulip-org.md +[chat-zulip-org]: https://zulip.com/developer-community/ [production-help]: https://chat.zulip.org/#narrow/stream/31-production-help [code-block]: https://zulip.com/help/code-blocks diff --git a/docs/production/requirements.md b/docs/production/requirements.md index e5a7b535f1..ee52673827 100644 --- a/docs/production/requirements.md +++ b/docs/production/requirements.md @@ -191,7 +191,7 @@ installing Zulip with a dedicated database server. accounts) per (1M messages to public streams). * **Example:** When the - [chat.zulip.org](../contributing/chat-zulip-org.md) community server + [chat.zulip.org](https://zulip.com/developer-community/) community server had 12K user accounts (~300 daily actives) and 800K messages of history (400K to public streams), it was a default configuration single-server installation with 16GB of RAM, 4 cores (essentially diff --git a/docs/production/security-model.md b/docs/production/security-model.md index 90b2f0d47b..b3532c0ef4 100644 --- a/docs/production/security-model.md +++ b/docs/production/security-model.md @@ -4,7 +4,7 @@ This section attempts to document the Zulip security model. It likely does not cover every issue; if there are details you're curious about, please feel free to ask questions in [#production help](https://chat.zulip.org/#narrow/stream/31-production-help) on the -[Zulip community server](../contributing/chat-zulip-org.md) (or if you +[Zulip community server](https://zulip.com/developer-community/) (or if you think you've found a security bug, please report it to security@zulip.com so we can do a responsible security announcement). diff --git a/docs/production/settings.md b/docs/production/settings.md index 7c1f6c9fe4..aa191e9517 100644 --- a/docs/production/settings.md +++ b/docs/production/settings.md @@ -32,7 +32,7 @@ to each new major release. Since Zulip's settings file is a Python script, there are a number of other things that one can configure that are not documented; ask on -[chat.zulip.org](../contributing/chat-zulip-org.md) +[chat.zulip.org](https://zulip.com/developer-community/) if there's something you'd like to do but can't figure out how to. ## Specific settings diff --git a/docs/production/upgrade-or-modify.md b/docs/production/upgrade-or-modify.md index 6a1352e599..b0e784968e 100644 --- a/docs/production/upgrade-or-modify.md +++ b/docs/production/upgrade-or-modify.md @@ -185,7 +185,7 @@ If you need help and don't have a support contract, you can visit [#production help](https://chat.zulip.org/#narrow/stream/31-production-help) in the [Zulip development community -server](../contributing/chat-zulip-org.md) for best-effort help. +server](https://zulip.com/developer-community/) for best-effort help. Please include the relevant error output from the above logs in a [Markdown code block](https://zulip.com/help/code-blocks) @@ -510,7 +510,7 @@ modified version of Zulip, please be responsible about communicating that fact: * Ideally, you'd reproduce the issue in an unmodified version (e.g. on -[chat.zulip.org](../contributing/chat-zulip-org.md) or +[chat.zulip.org](https://zulip.com/developer-community/) or [zulip.com](https://zulip.com)). * Where that is difficult or you think it's very unlikely your changes are related to the issue, just mention your changes in the issue report. diff --git a/docs/subsystems/performance.md b/docs/subsystems/performance.md index 0fd43d7c7a..04b50ac1ce 100644 --- a/docs/subsystems/performance.md +++ b/docs/subsystems/performance.md @@ -33,7 +33,7 @@ of load profiles: etc. have large numbers of users, many of whom are idle. (Many of the others likely stopped by to ask a question, got it answered, and then didn't need the community again for the next year). Our own - [chat.zulip.org](../contributing/chat-zulip-org.md) is a good + [chat.zulip.org](https://zulip.com/developer-community/) is a good example for this, with more than 15K total user accounts, of which only several hundred have logged in during the last few weeks. Zulip has many important optimizations, including [soft diff --git a/docs/testing/linters.md b/docs/testing/linters.md index 26634f8320..0b1e583ba3 100644 --- a/docs/testing/linters.md +++ b/docs/testing/linters.md @@ -91,7 +91,7 @@ extreme cases, but often it can be a simple matter of writing your code in a slightly different style to appease the linter. If you have problems getting something to lint, you can submit an unfinished PR and ask the reviewer to help you work through the lint problem, or you -can find other people in the [Zulip Community](../contributing/chat-zulip-org.md) +can find other people in the [Zulip Community](https://zulip.com/developer-community/) to help you. Also, bear in mind that 100% of the lint code is open source, so if you diff --git a/docs/translating/translating.md b/docs/translating/translating.md index aed92aeb98..5f1e30ec0a 100644 --- a/docs/translating/translating.md +++ b/docs/translating/translating.md @@ -21,7 +21,7 @@ These are the steps you should follow if you want to help translate Zulip: 1. Join [#translation][translation-stream] in the [Zulip development -community server](../contributing/chat-zulip-org.md), and say hello. +community server](https://zulip.com/developer-community/), and say hello. That stream is also the right place for any questions, updates on your progress, reporting problematic strings, etc. @@ -87,7 +87,7 @@ Some useful tips for your translating journey: - When in doubt, ask for context in [#translation](https://chat.zulip.org/#narrow/stream/58-translation) in - the [Zulip development community server](../contributing/chat-zulip-org.md). + the [Zulip development community server](https://zulip.com/developer-community/). - If there are multiple possible translations for a term, search for it in the *Concordance* tool (the button with a magnet in the top right corner). diff --git a/templates/zerver/faq.html b/templates/zerver/faq.html index 1eac9a8bf4..7616420e07 100644 --- a/templates/zerver/faq.html +++ b/templates/zerver/faq.html @@ -121,7 +121,7 @@

Stop by the - Zulip + Zulip community server to see Zulip in action and chat with the developers, tweet @zulip, or diff --git a/templates/zerver/footer.html b/templates/zerver/footer.html index 164276a3dc..5e589025ae 100644 --- a/templates/zerver/footer.html +++ b/templates/zerver/footer.html @@ -12,7 +12,7 @@

{{ _("Help & community") }}

diff --git a/templates/zerver/for/communities.md b/templates/zerver/for/communities.md index ff15adb32d..5ff3db5991 100644 --- a/templates/zerver/for/communities.md +++ b/templates/zerver/for/communities.md @@ -117,7 +117,7 @@ Zulip’s topic-based threading model solves the problems described above: ## Try Zulip today! You can see Zulip in action in our own [chat.zulip.org -community](https://zulip.readthedocs.io/en/latest/contributing/chat-zulip-org.html), which sends +community](/developer-community/), which sends thousands of messages a week. We often get feedback from contributors around the world that they love how responsive Zulip’s project leaders are in public Zulip conversations. We are able to achieve this despite diff --git a/templates/zerver/for/tum-case-study.md b/templates/zerver/for/tum-case-study.md index 71890a2c85..795da7a8c3 100644 --- a/templates/zerver/for/tum-case-study.md +++ b/templates/zerver/for/tum-case-study.md @@ -84,5 +84,5 @@ and [research](/for/research)! [tum-ranking]: https://www.in.tum.de/en/the-department/profile-of-the-department/facts-figures/facts-and-figures-2020/ -[chat-zulip-org]: https://zulip.readthedocs.io/en/latest/contributing/chat-zulip-org.html +[chat-zulip-org]: /developer-community/ [zulip-4-blog]: https://blog.zulip.com/2021/05/13/zulip-4-0-released/ diff --git a/templates/zerver/hello.html b/templates/zerver/hello.html index 24a9e00498..431576c3b9 100644 --- a/templates/zerver/hello.html +++ b/templates/zerver/hello.html @@ -358,7 +358,7 @@ from all around the world. With 160,000 words of developer documentation, a high quality code base, and a - welcoming community, + welcoming community, it’s easy to extend or tweak Zulip.

diff --git a/templates/zerver/help/contact-support.md b/templates/zerver/help/contact-support.md index 6d1a405ea1..58f39c4f67 100644 --- a/templates/zerver/help/contact-support.md +++ b/templates/zerver/help/contact-support.md @@ -25,7 +25,7 @@ We love hearing feedback! Please reach out if you have feedback, questions, or just want to brainstorm how to make Zulip work for your organization. -[chat-zulip-org]: https://zulip.readthedocs.io/en/latest/contributing/chat-zulip-org.html +[chat-zulip-org]: /developer-community/ ## Billing and commercial questions diff --git a/templates/zerver/landing_nav.html b/templates/zerver/landing_nav.html index 729d687e8f..4d563d7c72 100644 --- a/templates/zerver/landing_nav.html +++ b/templates/zerver/landing_nav.html @@ -89,7 +89,7 @@ Help center

  • - + Community chat