mirror of
https://github.com/zulip/zulip.git
synced 2025-10-26 09:34:02 +00:00
dedea23745
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.
18 lines
821 B
Markdown
18 lines
821 B
Markdown
* 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.
|