TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Re: Microsoft Manual of Style vs. github.com/MicrosoftDocs/microsoft-style-guide
Subject:Re: Microsoft Manual of Style vs. github.com/MicrosoftDocs/microsoft-style-guide From:Robert Lauriston <robert -at- lauriston -dot- com> To:TECHWR-L Writing <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Thu, 16 Aug 2018 12:28:55 -0700
microsoft-style-guide is a GitHub project. It contains the source code
and Markdown content for docs.microsoft.com/en-us/style-guide.
Any GitHub user can fork the microsoft-style-guide project, make
additions or corrections, and submit a pull request.
The Microsoft Manual of Style was produced using InDesign.
On Thu, Aug 16, 2018 at 11:34 AM, Lauren <lauren -at- writeco -dot- net> wrote:
> They say they have always used GitHub but now they are using it for feedback
> and issues. You can't just go in to GitHub and write or edit for Microsoft.
> Whether comments are posted on Git or sent through email, all the public can
> do is comment. They are trying to attract millennials.
> On 8/16/2018 11:12 AM, Tony Chung wrote:
>> I think what we need to take away is that this manual is a public project
>> on github, which opens up all opportunities for branching, pull requests,
>> and even forking of the same documentation project. I don't know if MS
>> intended for such decentralization, but that's what they've opened
>> themselves up to. They might have purchased github as a way to centralize
>> their source, but git as a source control lends itself to
>> The fact MicrosoftDocs is the project owner of multiple repositories shows
>> that there is some attempt for developers to add documentation at the same
>> time as they are building features. And they are probably looking for
>> git-savvy tech writers to submit pull requests to improve their docs. If I
>> were a techcom student, between contracts, or passionate about some of the
>> technology I might check with the project owners if they would accept pull
>> requests from the outside.
>> To date, the most successful attempt at documentation-by-community that
>> I've heard about is FlossManuals: http://en.flossmanuals.net/
>> Seeing that the Microsoft Writing Style Guide is in need of editorial
>> support, if you've got the interest and/or time, it couldn't hurt to take
>> up git.
> Visit TechWhirl for the latest on content technology, content strategy and
> content development | http://techwhirl.com
> You are currently subscribed to TECHWR-L as robert -at- lauriston -dot- com -dot-
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and
> Looking for articles on Technical Communications? Head over to our online
> magazine at http://techwhirl.com
> Looking for the archived Techwr-l email discussions? Search our public
> email archives @ http://techwr-l.com/archives
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com