CodeCow/zulip
1
0
Fork 0
mirror of https://github.com/zulip/zulip.git synced 2026-07-09 21:21:47 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

help: Extend guidelines on changing org policies.

Browse Source
This commit is contained in:
Alya Abbott 2025-10-31 15:45:07 -07:00 committed by Tim Abbott
parent 62a086b60f
commit fd8299e1d1
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
starlight_help/src/content/docs/moving-to-zulip.mdx
View File

@ -150,13 +150,17 @@ conversations:
[inbox](/help/inbox) together with all the features of a modern chat app,
like instant delivery of messages, emoji reactions, typing notifications,
@-mentions, and more.
* Using Zulip, you can discuss complex topics and make decisions with input
from all stakeholders, without the overhead of scheduling meeting. Are
there standing meetings you might not need?
* Because Zulip further organizes messages into conversations labeled with
[topics](/help/introduction-to-topics), there is generally no need to create
dedicated channels for specific projects.
* With conversations organized by topic, you can review prior discussions to
understand past work, explanations, and decisions — your chat history
becomes a knowledge base. Should it be standard practice to link to Zulip
conversations from docs, issue trackers, etc. for additional context?
* Using Zulip, you can discuss complex topics and make decisions with input
from all stakeholders, without the overhead of scheduling meeting. Are
there standing meetings you might not need? For example, stand-ups can be
replaced with dedicated check-in topics for each team member.
## Prepare users for the transition