# Style guide and content model

Learn about how we keep GitHub's documentation consistent, easy to follow, and maintainable.

## Links

* [Style guide](/en/enterprise-server@3.22/contributing/style-guide-and-content-model/style-guide)

  Follow this guide to make sure GitHub's documentation stays consistent and follows clear patterns that our readers can understand.

* [About the content model](/en/enterprise-server@3.22/contributing/style-guide-and-content-model/about-the-content-model)

  The content model describes the structure and types of content that we publish.

* [Contents of a GitHub Docs article](/en/enterprise-server@3.22/contributing/style-guide-and-content-model/contents-of-a-github-docs-article)

  Every article includes a few standard elements, and may include conditional or optional elements. We also use a standard order for content within an article.

* [Concepts content type](/en/enterprise-server@3.22/contributing/style-guide-and-content-model/concepts-content-type)

  People most often use conceptual content when they are learning about something new to them.

* [Reference content type](/en/enterprise-server@3.22/contributing/style-guide-and-content-model/reference-content-type)

  Reference content provides detailed information that people need while they are actively using a feature.

* [How-to content type](/en/enterprise-server@3.22/contributing/style-guide-and-content-model/how-to-content-type)

  Explain how to complete a task using GitHub products and features.

* [Troubleshooting content type](/en/enterprise-server@3.22/contributing/style-guide-and-content-model/troubleshooting-content-type)

  Troubleshooting content includes built-in errors we expect people to encounter, common problems reported to support, and situations people might encounter while completing tasks.

* [Release note content type](/en/enterprise-server@3.22/contributing/style-guide-and-content-model/release-note-content-type)

  Release notes enable readers to understand and prepare for the user-facing changes in each release of GitHub's versioned enterprise products.

* [Get started content type](/en/enterprise-server@3.22/contributing/style-guide-and-content-model/get-started-content-type)

  Get started content provides the minimal essential information to use a product or feature.

* [Quickstart content type](/en/enterprise-server@3.22/contributing/style-guide-and-content-model/quickstart-content-type)

  Quickstarts are best for people who want instructions quickly without lengthy explanations of how something works or why they would want to use it.

* [Tutorial content type](/en/enterprise-server@3.22/contributing/style-guide-and-content-model/tutorial-content-type)

  Tutorials are useful when someone has a basic understanding of the product and is interested in extending their understanding to solve a specific problem

* [About combining multiple content types](/en/enterprise-server@3.22/contributing/style-guide-and-content-model/about-combining-multiple-content-types)

  You can combine multiple content types in a single article to help people complete complex tasks.