LogoLogo
HomeBlogResources
  • README
  • Design
    • Awesome Design Tools
      • Awesome Design Tools
    • Awesome-UI-Templates
      • README-en
    • awesome-design-systems
      • Awesome Design System
    • Awesome Figma
      • Awesome Figma
    • awesome-styleguides
      • README-en
    • awesome-typography
      • Awesome Typography
    • awesome-ui
      • README-en
    • Awesome UX Design Styleguides
      • Awesome UX Design Styleguides
    • awesome-ux-designer
      • README-en
      • Reading list
    • awesome-ux
      • README-en
    • Awesome Webflow
      • webflow-masterclass
        • Webflow + Firebase用戶認證
    • webflow-masterclass
      • Webflow + Firebase用戶認證
  • Devops
    • Awesome SaaS boilerplate
    • Free for Dev
    • Mega Awesome List
    • Awesome-WordPress-Plugins
      • Awesome WordPress Plugins List
    • Awesome Wordpress Plugin List
    • Awesome CMS
    • awesome-flutter-cn
    • awesome-headless-cms
      • readme-en
    • Awesome-jamstack-resources
      • Awesome-jamstack-resources
    • Awesome Laravel
      • Awesome Laravel
    • awesome-list
      • The awesome manifesto
      • Contributor Covenant Code of Conduct
      • Contribution Guidelines
      • Creating Your Own List
      • pull_request_template
      • Media
    • Awesome Minio
    • awesome-react
      • README-en
    • Awesome Stack
      • Awesome Stacks
    • Awesome UI component library
      • Awesome UI component library
    • awesome-uikit
      • README-en
    • awesome-vercel
      • Awesome Vercel (Previously ZEIT )
    • Awesome WooCommerce
      • Awesome WooCommerce
    • Awesome WordPress
      • Awesome WordPress
    • Awesome Wordpress Developer Tools
      • Awesome WP Developer Tools
  • Marketing
    • Awesome ADTech
      • Awesome AdTech
    • awesome-discord-communities
      • Contributor Covenant Code of Conduct
      • CONTRIBUTING
      • FAQ
      • Server Badges and Tags
      • .github
        • ISSUE_TEMPLATE
          • custom
        • ISSUE_TEMPLATE
          • issue--exisiting-community
        • ISSUE_TEMPLATE
    • HubSpot CMS Boilerplate
      • HubSpot CMS Boilerplate
    • Awesome HubSpot
    • Awesome Marketing
    • awesome-seo
    • marketing-for-engineers
      • README-en
    • Tech-Marketer
  • Nocode
    • Awesome NoCode / LowCode
      • readme-en
  • Server
    • Awesome Cloudflare
      • Awesome Cloudflare
    • Awesome-Selfhosted
      • Awesome-Selfhosted
  • shopify
    • Awesome Shopify
      • Awesome Shopify
    • Shopify Awesome 真棒!
      • Awesome Shopify
  • Tools
    • Awesome VS Code
    • Awesome Mac
      • Awesome Mac
      • editor-plugin-zh
      • editor-plugin
    • Awesome Nomad
      • Awesome Nomad
    • Awesome-notion
      • Awesome Notion (Eng)
    • awesome-tools-for-startups
      • Awesome list of FREE tools Startups should be using
  • web3
    • Blockchain-stuff
      • CONTRIBUTE
    • Blockchain-stuff
    • Web3.0_Vault-main
    • Web3.0_Vault-main
      • basics
    • awesome-discord-communities
      • Contributor Covenant Code of Conduct
      • CONTRIBUTING
      • FAQ
      • Server Badges and Tags
      • .github
        • ISSUE_TEMPLATE
          • custom
        • ISSUE_TEMPLATE
          • issue--exisiting-community
        • ISSUE_TEMPLATE
    • awesome-ethereum
    • awesome-solidity-gh-pages
      • Contributor Covenant Code of Conduct
      • Contribution Guidelines
      • PULL_REQUEST_TEMPLATE
    • Awesome Web3
      • Awesome Web3 Code of Conduct
      • Contribution Guidelines
      • PULL_REQUEST_TEMPLATE
    • free-Web3-resources
      • Contributor Covenant Code of Conduct
    • free-Web3-resources
      • Contributing Guidelines
    • free-Web3-resources
    • free-Web3-resources
      • Intro to Solidity
    • free-Web3-resources
      • 200-days-of-Web3
    • free-Web3-resources
    • free-Web3-resources
    • Free Web3 Resources
    • free-Web3-resources
      • .github
    • free-Web3-resources
      • .github
        • ISSUE_TEMPLATE
    • free-Web3-resources
      • .github
        • ISSUE_TEMPLATE
    • Web3.0_Vault-main
    • web3together-main
      • CODE_OF_CONDUCT
      • sessions
        • Getting Started in Smart Contract Development with Solidity
    • free-Web3-resources
      • .github
        • PULL_REQUEST_TEMPLATE
    • free-Web3-resources
      • .github
        • ISSUE_TEMPLATE
          • bug_report
    • free-Web3-resources
      • .github
        • ISSUE_TEMPLATE
          • feature_request
  • webgl
    • Awesome-threejs
      • docs
        • Hellow Three.js 之 三维空间中观察物体的方法--照相机
        • 创建自己的全景图
        • Hellow Three.js 之 创建各种几何形状
        • hello-light-pro
        • Hellow Three.js 之 光影之谜
        • Hellow Three.js 之 加载外部3D模型
        • Hellow Three.js 之 给创建的物体赋予材质
        • hello-obj-mtl
        • P5
        • Hellow Three.js 之 有趣的着色器
        • Hellow Three.js 之 运动物体的性能监测
        • Hellow Three.js 之 让物体动起来
        • Hello Three.js 之 Hello world!
        • what-webgl
        • glsl
          • GLSL 中文手册
          • OpenGL GLSL 语法和函数详解
          • The book of shaders 记录
          • 各种 Shaders 效果
      • demo
        • 有趣的 three.js Demo
          • Decorative WebGL Backgrounds
          • Infinite Tubes
          • The Aviator
        • P5.js Demo
        • Learning-Threejs
          • learning-threejs
        • Learning-Threejs
          • master
            • learning-threejs
        • Learning-Threejs
          • master
            • learning-threejs
        • Learning-Threejs
          • master
            • learning-threejs
        • Learning-Threejs
          • master
            • learning-threejs
        • Learning-Threejs
          • master
            • learning-threejs
        • Learning-Threejs
          • master
            • learning-threejs
        • Learning-Threejs
          • master
            • learning-threejs
        • Learning-Threejs
          • master
            • learning-threejs
        • Learning-Threejs
          • master
            • learning-threejs
        • Learning-Threejs
          • master
            • learning-threejs
        • Learning-Threejs
          • master
            • learning-threejs
        • Learning-Threejs
          • master
            • assets
              • models
                • ogre
                  • ogro
    • awesome-threejs
      • README-en
      • Contributor Covenant Code of Conduct
      • Contribution Guidelines
    • Awesome WebGL
      • CONTRIBUTING
      • Awesome WebGL
      • Contributor Covenant Code of Conduct
      • Libraries
        • CONTRIBUTING
      • Libraries
        • WebGL Libraries - Features
      • Libraries
        • WebGL Libraries - File Size
      • Awesome WebGL - Libaries/Frameworks
  • AI
    • ChatGPT 中文指南
    • 生成式 AI 項目、工具、藝術作品和模型的精選列表
    • 精選 GPT-4 指南
    • ChatGPT 工具收錄
      • Awesome ChatGPT
    • ChatGPT 中文調教指南
    • GPT 開放原始碼項目合集
    • ChatGPT 應用收藏
    • Awesome OpenAI - 超酷的 OpenAI 蒐藏
      • Awesome-openAI
    • Awesome GPT-3 應用集
      • Awesome GPT-3
    • ChatGPT 提示指令庫
      • Awesome ChatGPT Prompts
  • SaaS
    • awesome-saas-boilerplates
Powered by GitBook
On this page
  • Contribution Guidelines
  • Add Community
  • Format WebP
  • Issues
  • Review Policy
  • Attribution
Export as PDF
  1. Marketing
  2. awesome-discord-communities

CONTRIBUTING

PreviousContributor Covenant Code of ConductNextFAQ

Last updated 2 years ago

Contribution Guidelines

By participating in this project you agree to follow the contributor code of conduct. From here on, the word server and community will be used interchangeably and will mean the same thing.

  • Add Community

  • Format WebP

  • Issues

  • Review Policy

Add Community

To include a community to the list, fork this project and add your server under a section or subsection, or you can include a new section if need be, then create a pull request. Make sure your proposal meets these requirements below, if you've Python installed you can take advantage of this script.

✅ Each community follows this template

<img align="left" height="94px" width="94px" alt="Server Icon" src="<static url of the image>"/>

[__Community Name__](url of invite link) [<img height="16px" width="16px" alt="Official Badge" src="images/badges/official.webp">](badges.md#official-identification-badge) [<img height="16px" width="16px" alt="Reddit Badge" src="images/badges/reddit.webp">](badges.md#reddit-badge) [<img height="16px" width="16px" alt="Homepage URL" src="images/badges/homepage.webp">](url of server homepage) [<img height="16px" width="16px" alt="Git Repository" src="images/badges/git.webp">](url of server git repository) \
Notable Channels: `#most-important-channel-1`, `#most-important-channel-2`, `#most-important-channel-3`, `#most-important-channel-4`, `#most-important-channel-5`, `#least-important-channel` \
Language: English, Deutsch, 日本語

✅ Community icon is optimized with WebP, with 75% lossy quality, and at least 128x128 pixel in resolution with moderate PPI

✅ Community name does not contain any emoji (discouraged)

✅ Invite link is permanent, generated from Discord platform itself, or URL whose domain is owned by you that eventually with or without captcha verification redirects to Discord invite page. No third-party URL domain allowed that isn't owned by your community, this includes link shorteners.

  • Allowed: https://discord.com/invite/123abc by community A

  • Allowed: https://b-community.com/discord-invite by community B when B owns b-community.com domain

  • Not Allowed: https://discord-links.com/community-c-invite by community C when C doesn't own discord-links.com domain

✅ Badges are properly placed and aligned

  • If you're unsure about whether a badge applies to your community, leave it excluded. After PR submission, a reviewer will let you know about missing badges, or ask the reviewer.

✅ Notable Channels contain the most important and active channels, no off-topic or informational channels, and does not necessarily take up too much space.

  • #announcements, #rules, #roles, etc., are informational channels and common across all communities, therefore they shouldn't be included.

  • #general, #chat, #tech-talk, etc., casual conversation channels can be included if they aren't meant for off-topic discussions.

  • Support channels: #help, #support, #beginners, etc., should be included. If there are multiple support channels with character suffix/prefix, e.g.: #help-1, #help-2, #help-3 -- instead of including them all, just enter #help. But if the suffixes present clear distinction between their topics, i.e., #help-software, #help-hardware -- software and hardware represent two different topics, then both of them can be included.

  • Channels that have barely any activity shouldn't be included, even if they're on-topic. E.g., if #help-software has regular activity, but #help-hardware has little to no activity, then only #help-software should be included.

  • Off-topic channels: #off-topic, #water-cooler, #random, #memes, etc., shouldn't be included.

  • Moderation channels, bot channels, feedback channels shouldn't be included.

  • Events or events discussion channels can be included.

✅ Language only contains spoken written languages that the community has active channels for

  • English: If only English language is encouraged

  • English, Deutsch, español: If there are active channels for all three languages

  • Deutsch: If only German language is encouraged

  • Don't include languages that has little to no conversation activity in any channel

✅ Moderation team is regularly active

✅ Community is active on a daily or semiweekly basis

✅ All public channels follow Discord community guidelines and ToS

Format WebP

Awesome Discord Communities list hosts the server icon images in its own repository. This allows reduced time to cache and faster rendition by the browser. Discord hosts the icon files as png which can take quite a lot of space and make the README page a lot heavier. Thus, webp was adopted. You can convert your png/jpg icon in the any of the following ways:

Easy WebP Conversion: Drop or paste your png/jpg icon on Sqoosh. Squoosh is open-source and does image compression on the client-side. Once loaded, by default, the original image preview is on the left side of the draggable vertical bar, and the compressed image preview is on the right. From the right 'Compress' sidebar select 'WebP', and drag the 'Quality' slider to 75. You can now download the image.

CLI WebP Conversion: If you prefer command line WebP conversion, you can use native cwebp by Google. It does require installing the library to your system. Use -q option with value 75.

Issues

If you've found an issue with an existing server or have a suggestion to make to improve this list, feel free to file an issue here.

Review Policy

Review policy is meant for reviewers, not necessarily for contributors. There is no real metric provided by Discord that can be used by anyone to evaluate a server. However, a maintainer will manually review the community for a period of time (1-4 days) before it can be accepted.

As an initial requirement, only technical or technology-related communities are considered. A community that is meant for people to hang out with no real active support channel will not be considered as technical. There are certain categories a technical community can be attributed to. Generic, Niche, and Project. There are a few distinct requirements for each of them.

Niche servers are the opposite of Generics, they're geared toward a smaller domain. The required minimum age is six months. Communities related to cryptocurrencies are often prone to the risk of getting hacked, for this reason, for now, only open-source owned official cryptocurrency servers will be allowed.

Project servers are part of associated communities of open-source projects or content creators (e.g., Twitch streamers, YouTube creators). Since the activity and growth of the server depend on the creators' contents, they can be accepted as soon as there is daily or semiweekly activity. If you maintain an open-source project you might also be interested in Discord's own open-source recognition.

Attribution

Icon mockup is made by Darius Dan.

try to address multiple-technical-domains-in-one instead of a single specific domain, i.e., a server that offers support for all programming languages vs. a server that offers Java only. These communities are most likely to attract a lot of people in a short period, and more likely to be short-lived as it gets more and more difficult to maintain over time. For this reason, a stricter requirement, a generic server needs to be at least a year old with active moderation and messaging activity on a daily basis (excluding the off-topic channels). This specific precondition affects generic servers only.

Render Screenshot
Web Conversion
Generic servers