Your browser doesn't support the features required by impress.js, so you are presented with a simplified version of this presentation.
For the best experience please use the latest Chrome, Safari or Firefox browser.
Microsoft OneWeek 2015 Hackthon: Markdown.MAML
This is PowerShell help system
This is the file that represent it
MAML is xml-based help format for PowerShell modules.
To edit MAML file you use separate program.
PowerShell Command help editor
You found an issue in Microsoft or 3rd party documentation.
What's your options?
If it's Microsoft documentation
- open connect bug
- shoot an email to MVP discussion list
- complain on twitter
If 3rd party
AND has project page
AND open source
THEN you can CONTRIBUTE.
- One more program to install and learn.
- Requires import-export.
- You source control output of the program, not a source code.
- Not simple.
- Not scalable.
If you are the module developer, it's your duty: you have to edit your documentation.
We want to address it
We want simple workflow
with 0 setup
To allow community easily contribute to ANY PowerShell documentation
We defined Markdown schema to author documentation
Markdown is easy to read and edit
It already renders by collaborative services (GitHub.com, VisualStudio.com, BitBucket.com)
and modern text editors (SublimeText, VSCode)
You generate MAML from Markdown as a build-step
You add Markdown to the source control and remove MAML from it
Build reports errors (if any) during Markdown -> MAML transformation
You can edit such documentation on GitHub in minutes, right in the browser
We dramatically simplify documentation story
To make PowerShell comunity more productive and vibrant
Use a spacebar or arrow keys to navigate