paulmataruso/zulip
1
0
Fork 0
mirror of https://github.com/zulip/zulip.git synced 2025-10-23 04:52:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

help: Remove single use macro tips-for-creating-channels.md.

Browse Source 
Having these single use macros exist was not intentional.
This commit is contained in:
Shubham Padia
2025-05-22 06:49:25 +00:00
committed by Tim Abbott
parent 0d168ff7bb
commit 0c131cf624
2 changed files with 20 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
help/create-channels.md
View File

@@ -8,7 +8,26 @@
## Tips for creating channels
{!tips-for-creating-channels.md!}
* It's often best to start with just a few channels, and add more as
needed. For small teams, you can start with the default channels
and go from there.
* A channel's name can be in any language, and can include spaces, punctuation,
and Unicode emoji. For large organizations, we recommend using a consistent naming
scheme, like `#marketing/<name>` or `#mk/<name>` for all channels
pertaining to the marketing team, `#help/<team name>` for
`<team name>`'s internal support channel, etc.
* You can [pin reference information](/help/pin-information), such as important
messages or topics, and external references, in the
[description](/help/view-channel-information#view-channel-description) for a
channel.
* For open source projects or other volunteer organizations, consider
adding default channels 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.
## Related articles

20
help/include/tips-for-creating-channels.md
View File

@@ -1,20 +0,0 @@
* It's often best to start with just a few channels, and add more as
needed. For small teams, you can start with the default channels
and go from there.
* A channel's name can be in any language, and can include spaces, punctuation,
and Unicode emoji. For large organizations, we recommend using a consistent naming
scheme, like `#marketing/<name>` or `#mk/<name>` for all channels
pertaining to the marketing team, `#help/<team name>` for
`<team name>`'s internal support channel, etc.
* You can [pin reference information](/help/pin-information), such as important
messages or topics, and external references, in the
[description](/help/view-channel-information#view-channel-description) for a
channel.
* For open source projects or other volunteer organizations, consider
adding default channels 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.