Contribute to Docs like a Microsoft Insider
summary
Shows the exact workflow: fork and clone the windows-powershell docs repo, create a working branch, push and open a PR to main (never live), use the GitHub CLI to check out PRs locally, and rely on automated checks and a preview URL before merge. Recommends the learn authoring pack and the Alt-Q reflow extension to keep lines <=100 chars, mentions an auto-merge 20% rule, notes daily syncs (PowerShell repo ~3 PM Pacific) and demonstrates fixing a bad example and adding it to the Remove cmdlet.
AI-written summary · about
chapters (17)
- 0:00Contributing to Microsoft Docs
- 1:30Why contribute to docs
- 2:59Getting started with guides
- 5:59Quick fixes with GitHub edit
- 7:13Docs repository structure
- 11:29PowerShell module browser
- 14:19Git workflow for docs
- 17:56Live editing in GitHub
- 23:54Reviewing pull requests
- 27:06Applying changes from PR
- 33:55Preview changes before merge
- 34:18Learn Authoring Pack setup
- 38:16Markdown for Azure
- 39:20Reflow Markdown extension
- 44:41New docs ideas
- 45:48Blog posts on Microsoft Docs
- 46:10Key takeaways and next steps
related talks
46mContribute to Docs Like A Microsoft Insider
39mBecome a Contributor to Microsoft Docs
39mOpen Docs, Open Collaboration: Building Better Documentation with Community PRs
35mHelping Your Community Contribute to Developer Documentation
05mdocs.microsoft.com Needs You!
43m'ProTalking' Your Way into Open Source
12mWhat's new for Developers on Windows to enhance Developer Productivity
27mTaking code to next level with Open Source (Git & Github)