Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://docs.github.com/en/contributing below:

Contributing to GitHub Docs documentation

Select language: current language is English

Open menu

Open Sidebar

• Contribute to 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

  • Use videos

  • Create reusable content

  • Create screenshots

  • Create diagrams

  • Create tool switchers

  • Configure redirects

  • Change an article's title

  • Annotate code examples

  • Templates

• • Style guide

  • About the content model

  • Contents of an article

  • About topics

  • Conceptual content type

  • Referential content type

  • Procedural content type

  • Troubleshooting content type

  • Release note content type

  • Quickstart content type

  • Tutorial content type

  • Combining multiple types

• • About contributing

  • Using Git

  • Using the TODOCS placeholder

  • Using the content linter

  • Label reference

• • Working in a codespace

  • Create a local environment

  • Troubleshooting your environment

Learn about how the GitHub Docs team creates documentation and how you can contribute.

• Best practices for GitHub Docs

  Follow these best practices to create documentation that's user-friendly and easy to understand.

• 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

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

• About contributing to GitHub Docs

  You can contribute to GitHub Docs content in several ways.

• Best practices for GitHub Docs
• About GitHub's documentation philosophy
• About GitHub's documentation fundamentals
• Content design principles
• Writing content to be translated
• Making content findable in search
• Versioning documentation
• Using Markdown and Liquid in GitHub Docs
• Using YAML frontmatter
• Using videos in GitHub Docs
• Creating reusable content
• Creating screenshots
• Creating diagrams for GitHub Docs
• Creating tool switchers in articles
• Configuring redirects
• Changing an article's title
• Annotating code examples
• Templates

• Style guide
• About the content model
• Contents of a GitHub Docs article
• About topics
• Conceptual content type
• Referential content type
• Procedural content type
• Troubleshooting content type
• Release note content type
• Quickstart content type
• Tutorial content type
• About combining multiple content types

• About contributing to GitHub Docs
• Using Git on GitHub Docs
• Using the TODOCS placeholder to leave notes
• Using the content linter
• Label reference

• Working on GitHub Docs in a codespace
• Creating a local environment
• Troubleshooting your environment

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4