From fd8299e1d124bc7a7c75d92da7d4e4334c4a999f Mon Sep 17 00:00:00 2001 From: Alya Abbott Date: Fri, 31 Oct 2025 15:45:07 -0700 Subject: [PATCH] help: Extend guidelines on changing org policies. --- starlight_help/src/content/docs/moving-to-zulip.mdx | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/starlight_help/src/content/docs/moving-to-zulip.mdx b/starlight_help/src/content/docs/moving-to-zulip.mdx index 0e311630aa..db629a3680 100644 --- a/starlight_help/src/content/docs/moving-to-zulip.mdx +++ b/starlight_help/src/content/docs/moving-to-zulip.mdx @@ -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