Home
About
Blog
Products
Forum
Support
Contact
Sunbelt Computer Software
PL/B Language Development and Support
Home
About
Blog
Products
Forum
Support
Contact
Style guide and content model - GitHub Docs
Skip to main content
GitHub Docs
Version:
Free, Pro, & Team
Search or ask Copilot
Search or ask
Copilot
Select language: current language is English
Search or ask Copilot
Search or ask
Copilot
Open menu
Open Sidebar
Contribute to GitHub Docs
/
Style guide and content model
Home
Contribute to GitHub Docs
Writing for GitHub Docs
Best practices for GitHub Docs
Documentation philosophy
Documentation fundamentals
Content design principles
Write content to be translated
Make content findable
Versioning documentation
Markdown and Liquid
YAML frontmatter
Create reusable content
Create screenshots
Create diagrams
Create tool switchers
Configure redirects
Change an article's title
Annotate code examples
Templates
Style guide and content model
Style guide
About the content model
Contents of an article
Conceptual content type
Reference content type
How-to content type
Troubleshooting content type
Release note content type
Quickstart content type
Tutorial content type
Combining multiple types
Collaborate on GitHub Docs
About contributing
Using Git
Using the TODOCS placeholder
Using the content linter
Label reference
Your working environment
Working in a codespace
Create a local environment
Troubleshooting your environment
Contribute to GitHub Docs
/
Style guide and content model
Style guide and content model
Learn about how we keep GitHub's documentation consistent, easy to follow, and maintainable.
Style guide
About the content model
Contents of a GitHub Docs article
Conceptual content type
Reference content type
How-to content type
Troubleshooting content type
Release note content type
Quickstart content type
Tutorial content type
About combining multiple content types
