{"meta":{"title":"Style guide and content model","intro":"Learn about how we keep GitHub's documentation consistent, easy to follow, and maintainable.","product":"Contribute to GitHub Docs","breadcrumbs":[{"href":"/en/contributing","title":"Contribute to GitHub Docs"},{"href":"/en/contributing/style-guide-and-content-model","title":"Style guide and content model"}],"documentType":"category"},"body":"# Style guide and content model\n\nLearn about how we keep GitHub's documentation consistent, easy to follow, and maintainable.\n\n## Links\n\n* [Style guide](/en/contributing/style-guide-and-content-model/style-guide)\n\n  Follow this guide to make sure GitHub's documentation stays consistent and follows clear patterns that our readers can understand.\n\n* [About the content model](/en/contributing/style-guide-and-content-model/about-the-content-model)\n\n  The content model describes the structure and types of content that we publish.\n\n* [Contents of a GitHub Docs article](/en/contributing/style-guide-and-content-model/contents-of-a-github-docs-article)\n\n  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.\n\n* [Concepts content type](/en/contributing/style-guide-and-content-model/concepts-content-type)\n\n  People most often use conceptual content when they are learning about something new to them.\n\n* [Reference content type](/en/contributing/style-guide-and-content-model/reference-content-type)\n\n  Reference content provides detailed information that people need while they are actively using a feature.\n\n* [How-to content type](/en/contributing/style-guide-and-content-model/how-to-content-type)\n\n  Explain how to complete a task using GitHub products and features.\n\n* [Troubleshooting content type](/en/contributing/style-guide-and-content-model/troubleshooting-content-type)\n\n  Troubleshooting content includes built-in errors we expect people to encounter, common problems reported to support, and situations people might encounter while completing tasks.\n\n* [Release note content type](/en/contributing/style-guide-and-content-model/release-note-content-type)\n\n  Release notes enable readers to understand and prepare for the user-facing changes in each release of GitHub's versioned enterprise products.\n\n* [Get started content type](/en/contributing/style-guide-and-content-model/get-started-content-type)\n\n  Get started content provides the minimal essential information to use a product or feature.\n\n* [Quickstart content type](/en/contributing/style-guide-and-content-model/quickstart-content-type)\n\n  Quickstarts are best for people who want instructions quickly without lengthy explanations of how something works or why they would want to use it.\n\n* [Tutorial content type](/en/contributing/style-guide-and-content-model/tutorial-content-type)\n\n  Tutorials are useful when someone has a basic understanding of the product and is interested in extending their understanding to solve a specific problem\n\n* [About combining multiple content types](/en/contributing/style-guide-and-content-model/about-combining-multiple-content-types)\n\n  You can combine multiple content types in a single article to help people complete complex tasks."}