Welcome to the open source documentation of Microsoft Windows Server. Contributing to open source is more than just providing updates, it's also letting us know when there is an issue.
There are two separate locations where we keep Windows Server technical content. One of the locations is public (windowsserverdocs) while the other is private (windowsserverdocs-pr). Who you are determines which location you contribute to:
-
I'm not a Microsoft employee. As a non-Microsoft employee, you must contribute to the public location. For information about how to do that, see the Contributing to Windows Server technical documentation article.
-
I'm a Microsoft employee. As a Microsoft employee, you have options, based on what you're trying to do:
-
Create a brand-new article. To create a brand-new article, you must create and set up your GitHub account and tools, fork and clone the windowsserverdocs-pr repo, set up your remote branch, create the article, and finally create a new pull request for approval and publishing. For these instructions, see the Create new Windows Server articles using GitHub and Visual Studio Code article.
-
Make large changes to an existing article. To make substantial changes to an existing article, you can follow the instructions in the Edit an existing Windows Server article using GitHub and Visual Studio Code article.
-
Make minor changes to an existing article. To make minor changes to an existing article, you can follow the instructions in the Update existing Windows Server articles using a web browser and GitHub article.
-
These repos are actively managed and includes the source for Windows Server content published to docs.microsoft.com:
For info on how to use Markdown on Docs.microsoft.com topics, see Docs markdown reference. The publicly accessible version of this content is here: Public Docs markdown reference.
Please refer to LICENSE, LICENSE-CODE and ThirdPartyNotices for all Licensing information.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.