# Building communities documentation Learn best practices for moderating and setting up collaborative, safe, and effective communities using GitHub's community-tested tools. ## Recommended * [Setting guidelines for repository contributors](/en/enterprise-server@3.21/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors) You can create guidelines to communicate how people should contribute to your project. * [Configuring issue templates for your repository](/en/enterprise-server@3.21/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository) You can customize the templates that are available for contributors to use when they open new issues in your repository. * [Creating a pull request template for your repository](/en/enterprise-server@3.21/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository) When you add a pull request template to your repository, project contributors will automatically see the template's contents in the pull request body. * [About wikis](/en/enterprise-server@3.21/communities/documenting-your-project-with-wikis/about-wikis) You can host documentation for your repository in a wiki, so that others can use and contribute to your project. * [Managing disruptive comments](/en/enterprise-server@3.21/communities/moderating-comments-and-conversations/managing-disruptive-comments) You can hide, edit, or delete comments on issues, discussions, pull requests, and commits. * [Creating a default community health file](/en/enterprise-server@3.21/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file) You can create default community health files, such as CONTRIBUTING and CODE\_OF\_CONDUCT. Default files will be used for any repository owned by the account that does not contain its own file of that type. ## Articles * [Setting guidelines for repository contributors](/en/enterprise-server@3.21/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors) You can create guidelines to communicate how people should contribute to your project. * [Adding a license to a repository](/en/enterprise-server@3.21/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository) You can include an open source license in your repository to make it easier for other people to contribute. * [Adding support resources to your project](/en/enterprise-server@3.21/communities/setting-up-your-project-for-healthy-contributions/adding-support-resources-to-your-project) You can create a SUPPORT file to let people know about ways to get help with your project. * [Creating a default community health file](/en/enterprise-server@3.21/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file) You can create default community health files, such as CONTRIBUTING and CODE\_OF\_CONDUCT. Default files will be used for any repository owned by the account that does not contain its own file of that type. * [About issue and pull request templates](/en/enterprise-server@3.21/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates) With issue and pull request templates, you can customize and standardize the information you'd like contributors to include when they open issues and pull requests in your repository. * [Configuring issue templates for your repository](/en/enterprise-server@3.21/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository) You can customize the templates that are available for contributors to use when they open new issues in your repository. * [Syntax for issue forms](/en/enterprise-server@3.21/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms) You can define different input types, validations, default assignees, and default labels for your issue forms. * [Syntax for GitHub's form schema](/en/enterprise-server@3.21/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema) You can use GitHub's form schema to configure forms for supported features. * [Creating a pull request template for your repository](/en/enterprise-server@3.21/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository) When you add a pull request template to your repository, project contributors will automatically see the template's contents in the pull request body. * [Common validation errors when creating issue forms](/en/enterprise-server@3.21/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms) You may see some of these common validation errors when creating, saving, or viewing issue forms. * [Managing disruptive comments](/en/enterprise-server@3.21/communities/moderating-comments-and-conversations/managing-disruptive-comments) You can hide, edit, or delete comments on issues, discussions, pull requests, and commits. * [Locking conversations](/en/enterprise-server@3.21/communities/moderating-comments-and-conversations/locking-conversations) Repository owners and collaborators, and people with write access to a repository, can lock conversations on issues, pull requests, and commits permanently or temporarily to defuse a heated interaction. * [Archive pull requests](/en/enterprise-server@3.21/communities/moderating-comments-and-conversations/archive-pull-requests) Repository administrators can archive a pull request to remove it from public view, providing a moderation option between leaving a pull request up and permanently deleting it. * [Tracking changes in a comment](/en/enterprise-server@3.21/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment) You can view the edit history of a comment or delete sensitive information from the edit history of a comment. * [About wikis](/en/enterprise-server@3.21/communities/documenting-your-project-with-wikis/about-wikis) You can host documentation for your repository in a wiki, so that others can use and contribute to your project. * [Adding or editing wiki pages](/en/enterprise-server@3.21/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages) You can add and edit wiki pages directly on GitHub or locally using the command line. * [Creating a footer or sidebar for your wiki](/en/enterprise-server@3.21/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki) You can add a custom sidebar or footer to your wiki to provide readers with more contextual information. * [Editing wiki content](/en/enterprise-server@3.21/communities/documenting-your-project-with-wikis/editing-wiki-content) You can add images and links to content in your wiki, and use some supported MediaWiki formats. * [Viewing a wiki's history of changes](/en/enterprise-server@3.21/communities/documenting-your-project-with-wikis/viewing-a-wikis-history-of-changes) Because wikis are Git repositories, every change you make is a commit that you can view. * [Changing access permissions for wikis](/en/enterprise-server@3.21/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis) Only repository collaborators can edit a public repository's wiki by default, but you can allow anyone with an account on GitHub.com to edit your wiki. * [Disabling wikis](/en/enterprise-server@3.21/communities/documenting-your-project-with-wikis/disabling-wikis) You can disable your repository's wiki.