mirror of
https://github.com/zulip/zulip.git
synced 2025-10-31 03:53:50 +00:00
7ce87c66ac
In our current implementation, loose lists and tight lists look the same visually. Loose lists are lists with blank lines between list items, and the contents of a list item should be enclosed in a paragraph tag in that case. For unordered lists, paragraph tags have a bottom margin in starlight and thus looses lists look much more spaced out than tight lists. That is not the behaviour we had in mind while writing the documentation, the reason we had all these loose lists is to make the documentation easy to write and read. So we attempt to remove all the blank lines and fix the problem at source. Since paragraph tags are used for other purposes in a list in starlight, it won't be a wise decision to let the source be as is and just change things in css, other expected behaviours might break in that case. See this topic for more details: https://chat.zulip.org/#narrow/channel/19-documentation/topic/new.20help.20center.3A.20regressions/near/2226084 All the changes were made by a one-off script which has not been commited to the repo. The script wasn't perfect and could not decide between blank lines that make a list loose vs blank lines necessary for a sub-list or a code block inside a list item. A manual review of all the changes was done before making this commit to ensure that no unintended changes were made to the help center files.
35 lines
1.4 KiB
Markdown
35 lines
1.4 KiB
Markdown
# Create channels
|
|
|
|
{!create-channels-intro.md!}
|
|
|
|
## How to create a channel
|
|
|
|
{!create-a-channel-instructions.md!}
|
|
|
|
## Tips for creating channels
|
|
|
|
* 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
|
|
|
|
* [Moving to Zulip](/help/moving-to-zulip)
|
|
* [Channel permissions](/help/channel-permissions)
|
|
* [Set default channels for new users](/help/set-default-channels-for-new-users)
|
|
* [Getting started with Zulip](/help/getting-started-with-zulip)
|