Files
zulip/help/include/tips-for-creating-streams.md
Lauryn Menard dedea23745 help-docs: Move help center documentation to top level directory.
These files are not Jinja2 templates, so there's no reason that they needed
to be inside `templates/zerver`. Moving them to the top level reflects their
importance and also makes it feel nicer to work on editing the help center content, 
without it being unnecessary buried deep in the codebase.
2023-01-25 14:08:29 -08:00

821 B

  • It's often best to start with just a few streams, and add more as needed. For small teams, you can start with the default streams and go from there.

  • For large organizations, we recommend using a consistent naming scheme, like #marketing/<name> or #mk/<name> for all streams pertaining to the marketing team, #help/<team name> for <team name>'s internal support stream, etc.

  • A #zulip help stream can be useful for providing internal Zulip support and answering questions about Zulip.

  • For open source projects or other volunteer organizations, consider adding default streams like #announce for announcements, #new members for new members to introduce themselves and be welcomed, and #help so that there's a clear place users stopping by with just a single question can post.