mirror of
https://github.com/status-im/status-web.git
synced 2025-02-27 19:50:53 +00:00
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>
63 lines
3.8 KiB
Markdown
63 lines
3.8 KiB
Markdown
---
|
|
id: 29
|
|
revision: '0'
|
|
language: en
|
|
title: Create a Status Community
|
|
---
|
|
|
|
:::info
|
|
Currently, you can only create and administer communities using the Status desktop app.
|
|
[Download Status desktop :octicons-desktop-download-16:][status-web-download]
|
|
:::
|
|
|
|
A [Status Community][about-status-communities] is a place where you can connect and communicate with people who share your interests. Communities are ideal for those with a passion or hobby, study groups, gaming communities, professional network groups, or creators looking to generate income from their content without intermediaries.
|
|
|
|
As a community owner, you can create open communities or [restrict community access using tokens][set-up-a-private-community], control [membership approval][set-up-your-community-s-approval-options] and organize discussion groups in [channels][create-a-channel]. Owners have complete control over their community and are responsible for maintaining its rules.
|
|
|
|
## Create a community
|
|
|
|
=== "Desktop"
|
|
|
|
1. From the navigation sidebar, click :desktop-communities: **Communities**.
|
|
1. On top of the content area, click **Create community**.
|
|
1. Add a **name** and a **short description** of your community.
|
|
1. Optionally, add a **logo**, **banner**, **colour** palette and **tags**. You can [customize these settings](#customize-your-community) at any time.
|
|
1. Configure [additional community settings](#configure-additional-settings).
|
|
1. Click **Next** to complete the [information about your community](#describe-your-community-and-its-rules).
|
|
1. Click **Create community**.
|
|
|
|
## Configure additional settings
|
|
|
|
You can configure these community settings:
|
|
|
|
| Setting | Description |
|
|
| :------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
| **Community history service** | Status Communities store up to 30 days of chat history by default. When this option is checked, community members can see messages older than 30 days. |
|
|
| **Request to join required** | Community owners must manually approve each join request if this setting is checked. This option applies to [open and private][about-status-communities] communities. |
|
|
| **Any member can pin a message** | Any community member can [pin messages][pin-a-message] when this setting is checked. If the setting is unchecked, only the community owner can pin messages. |
|
|
|
|
:::info
|
|
The Community history service uses the [BitTorrent peer-to-peer network :octicons-tab-external-16:][bittorrent-peer-to-peer-network] to store and retrieve community messages older than 30 days. Status uses a decentralized network and does not store this information.
|
|
:::
|
|
|
|
## Describe your community and its rules
|
|
|
|
=== "Desktop"
|
|
|
|
1. In the **Community introduction and rules**, introduce your community to new members and describe the community guidelines.
|
|
1. In the **Leaving community message**, write the message sent to members leaving your community.
|
|
1. Click **Create community** if you haven't already.
|
|
|
|
## Customize your community
|
|
|
|
After you create a community, you can customize its settings at any time.
|
|
|
|
=== "Desktop"
|
|
|
|
1. From the navigation sidebar, click your community.
|
|
1. On top of the channel sidebar, click your community logo.
|
|
1. Click :desktop-overview: **Overview**.
|
|
1. Expand the window and click **Edit Community**.
|
|
1. Edit your community look-and-feel, [additional settings](#configure-additional-settings) or [community rules](#describe-your-community-and-its-rules).
|
|
1. Click **Save changes**.
|