Style guide and content model

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

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

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.

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

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

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

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 notes enable readers to understand and prepare for the user-facing changes in each release of GitHub's versioned enterprise products.

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

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

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

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