Welcome to the docs.microsoft.com (a.k.a. Docs) Contributor Guide!

About this guide

Here you'll find all of the information you need to contribute to Docs articles, by using Microsoft's Open Publishing Services (OPS) platform and supporting tools and processes.

The Table of Contents to your left is designed to be used in step-wise order, from top to bottom. Many of the topics can also serve as reference content, which you may want to save as a favorite/bookmark in your browser. Also note that there are several links to other sites, which will take you to pages that are off of the Docs.Microsoft.Com domain and outside of this guide.

QuickStart to propose an article change

If you don't have time to digest the entire guide or install tools, and just need to make a minor contribution, here are the essentials:

  1. If you don't already have one, create a GitHub account.
  2. Use the minor/infrequent contributor workflow to submit your contribution via a GitHub pull request.
  3. Docs articles are written in a markup language called Markdown. If you need help, see How to use Markdown.

When you have time, we recommend that you return and complete the Overview and setup and "Contribute to content" sections.

Additional ways to contribute to Docs.Microsoft.Com content

You can also contribute to Docs.Microsoft.Com content and community in the following ways:

  • Submit article feedback/questions directly in an article. There are 2 ways of doing this, both of which require you to first set up a Livefyre account:
    • General comments can be provided by using the "Comments" feature at the bottom of the article page
    • Context-specific comments can be embedded next to the related sentence, by hovering the text and clicking the floating "sidenote" caption icon in the right margin
  • Submit or vote for site suggestions on the Docs.microsoft.com User Voice site
  • Participate in community discussion, such as Stack Overflow, Microsoft TechNet or MSDN forums, or a Yammer group.


If you have suggestions for contributions, or have questions about this guide, please use the Livefyre comments section on this page, or send an email to the Docs Core Team.