b88f7e73da
* setup md/mdx * add test page * setup mdx provider * Add breadcrumbs * links -> routes * add information box * add more remark plugins * text InformationBox * setup contentlayer * add testing docs folder * setup docs static generation * add ssg to blog too * add Shortcut component * add SearchButton * add hook for keyboard shortcuts * update main docs page * update main learn page content * side-bar -> sidebar-menu * rename docs pages * add heading anchors, use new components * add table of contents to docs * move styling to breadcrumbs * cleanup markdown examples * change slugify fn * update getting-started.md * add highlight matches component * update learn pages * rename website InformationBox to Admonition * ?enable user-select * add static helpers to epics * simplify components structure * update insights layout * add link tree utils * add search engine * update docs import * update contenlayer * add docs indexer * support code block highlighting * search index * fix types * remove supporting files * update tree builder * make build work * update docs * update label * update toc * add config.json * update menu * search index import * learn -> help * fix md file * update toc * fix code snippets * add help index route * remove testing files * add original docs * migrate getting started * migrate messaging-and-web3-browser docs * migrate network-nodes-and-statistics docs * handle empty content * add navigation config * wip * migrate status-wallet docs * migrate to new admonitions format * migrate your-profile-and-preferences docs * migrate part of status-communities docs * mv * rm log * index * fix lint * fix warn * fix title * fix docs layout * udpate next.config * use lowercase lang * generate contentlayer types before typechecking * update docs images * update help routes --------- Co-authored-by: Felicio Mununga <felicio@users.noreply.github.com>
4.0 KiB
| id | revision | language | title |
|---|---|---|---|
| 287 | 0 | en | Channels: your quick start guide |
In [Status Communities][how-to-use-communities-your-quick-start-guide], you have access to dedicated spaces called channels. Channels bring the right people and information together for any project or topic. A channel conversation focuses on specific topics, and you can join and leave the conversation anytime.
As a community owner, you can use channels to break down a large community into smaller, more focused sub-groups. With Status, you can [configure channel permissions][configure-channel-permissions] based on token ownership. For example, you can make a public channel private or view-only by only allowing holders of specific tokens to join or post.
:::tip To add channels to your community, check out [Create a channel][create-a-channel]. :::
{/* [image](image) */}
=== ":mobile-one: Community information" Information about the community, such as the number of members, active users or the main community topics.
=== ":mobile-two: Channel categories" Community owners can group related channels into [categories][create-a-channel]. This is especially useful for communities with a lot of channels.
=== ":mobile-three: Channels list" The list of available channels in a community. [Private channels][configure-channel-permissions] have a :mobile-locked-lock: lock icon next to the channel name.
Public and private channels
All members in a [Status Community][how-to-use-communities-your-quick-start-guide] can browse and join public channels. For private channels, you must [meet the token requirements][understand-token-requirements-in-channels] to join the channel. To maintain access to private channels, hold the required tokens at all times.
:::info Messages in [private communities][how-to-use-communities-your-quick-start-guide] and private channels are always end-to-end encrypted. :::
{/* [image](image) */}
=== ":mobile-one: Public channel" All community members can join public channels. When you join a community, you automatically get access to these channels.
=== ":mobile-two: Private channel" Private channels have a :mobile-locked-lock: lock icon next to the channel name. To access these channels, you need to [meet the token requirements][understand-token-requirements-in-channels]. To maintain access, keep holding the required tokens.
Channel information
{/* [image](image) */}
=== ":mobile-one: Channel information" You can see the channel name and permissions here. Private channels have a :mobile-locked-lock: lock icon. From this area, you can select :mobile-more-options: More options to view more details about the channel, such as channel members, permissions or notifications.
=== ":mobile-two: Pinned message area" Channel members can [pin messages][pin-a-message] to this area, such as announcements, FAQ or channel rules.
=== ":mobile-three: Channel feed" This area shows the channel activity, including messages, photos, reactions or links.
=== ":mobile-four: Message field" From here, you can send messages to channel members with [text][send-and-read-messages], [images][share-images-in-status] or emojis, as well as [audio messages][send-an-audio-message].
The #general channel
The #general channel is created by default when you [create a community][create-a-status-community]. You can use this channel for various purposes, including sharing news, discussing community policies and events or making announcements.
This channel works like any other channel. As a community administrator, here's how you can make this channel more helpful:
- Don't rename the channel. The #general channel is widely recognized and understood in communities. Renaming the channel may confuse members.
- [Set up permissions][configure-channel-permissions] to restrict who can post in #general. This removes noise from the channel and keeps it on topic.
- Use the #general channel to [pin messages][pin-a-message] describing FAQs, community rules or other information relevant to your community.